kytv/I2P_Website
1
0
Fork 0
forked from I2P_Developers/i2p.www
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
28c12c4430d9d63364b4690a837d5bfd5e5b05f7
I2P_Website/i2p2www/translations/es/LC_MESSAGES/about.po

2561 lines
97 KiB
Plaintext
Raw Normal View History

Migrated translations to split gettext domains
2013-07-15 11:31:41 +00:00
# Spanish translations for I2P.
# Copyright (C) 2013 ORGANIZATION
# This file is distributed under the same license as the I2P project.
#
# Translators:
# Adolfo Jayme Barrientos <fitoschido@ubuntu.com>, 2013
# Daniel Mustieles <daniel.mustieles@gmail.com>, 2013
# m1xxy <m1xxy@mail.i2p>, 2011
# olivertrash <oliver.trasshh@gmail.com>, 2013
# strel <strelnic@gmail.com>, 2013
# trolly, 2013
msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
"POT-Creation-Date: 2013-07-15 11:24+0000\n"
"PO-Revision-Date: 2013-07-11 10: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/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 <em>Advanced</em>, then click on the "
"<em>Network</em>\n"
"tab. In the <em>Connections</em> 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 <em>Avanzado</em>, entonces pulse en "
"la pestaña <em>Red</em>. En la sección de <em>Conexiones</em>, 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 <em>Connection Settings</em> window, click the circle next to "
"<em>Manual\n"
" proxy configuration</em>, 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 <em>Configuración de Conexiones</em>, pulse el círculo "
"junto a <em>Configuración manual del proxy</em>, 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 <em>Settings</em> menu, select <em>Configure Konqueror</em>. 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 <em>Setup</em> box."
msgstr ""
"Desde el menú de <em>Configuración</em>, seleccione <em>Configurar "
"Konqueror</em>. 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 "
"<em>Configurar</em>."
#: 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 <em>New</em> button in the Exceptions section. Enter"
"\n"
"localhost and click OK. Click the <em>New</em> 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 <em>Nuevo</em> en la "
"sección de Excepciones. Escriba localhost y pulse Aceptar. Pulse otra vez"
" el botón <em>Nuevo</em> 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 ""
"<b>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.</b>"
msgstr ""
"<b>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.</b>"
#: i2p2www/pages/site/about/browser-config.html:83
msgid ""
"By default, I2P comes with two outproxies configured: "
"<code>false.i2p</code>\n"
"(an HTTP-only proxy) and <code>outproxyng.h2ik.i2p</code> (an HTTPS proxy"
"\n"
"routed through Tor."
msgstr ""
"Por defecto I2P viene con 2 outproxies configurados: "
"code>false.i2p</code> (un proxy HTTP sólo) y "
"<code>outproxyng.h2ik.i2p</code> (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 <a href=\"http://%(tpb)s\">%(tpb)s</a>. "
"Eepsites\n"
"that are accessible via .i2p addresses are also not allowed via the "
"outproxies.\n"
"As a convenience, <code>False.i2p</code> 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 <a "
"href=\"http://%(tpb)s\">%(tpb)s</a>. Las eepsites accesible en I2P "
"también están bloqueadas a través de los outproxies. Por comodidad, "
"<code>False.i2p</code> bloquea servidores de publicidad."
#: i2p2www/pages/site/about/browser-config.html:101
msgid ""
"<a href=\"https://www.torproject.org\">Tor</a> is good application to use"
" as an\n"
"outproxy to the Internet."
msgstr ""
"<a href=\"https://www.torproject.org\">Tor</a> 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'<small>s</small> 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 &euro; and %(btcval)s BTC"
msgstr "%(euroval)s &euro; 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 &euro;"
msgstr "%(euroval)s &euro;"
#: 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: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 <a "
"href=\"mailto:%(echelon)s\">echelon</a>\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 <a "
"href=\"mailto:%(echelon)s\">echelon</a> 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: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"
"<a href=\"http://en.wikipedia.org/wiki/Internet_Protocol\">IP</a>), but "
"there is a \n"
"library available to allow reliable streaming communication on top of it "
"(a la \n"
"<a "
"href=\"http://en.wikipedia.org/wiki/Transmission_Control_Protocol\">TCP</a>)."
" \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 <a "
"href=\"http://en.wikipedia.org/wiki/Public_key_encryption\">public "
"keys</a>)."
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 <a "
"href=\"http://en.wikipedia.org/wiki/Internet_Protocol\">IP</a>), pero "
"existe una librería disponible que permite la comunicación segura sobre "
"él (a la <a "
"href=\"http://en.wikipedia.org/wiki/Transmission_Control_Protocol\">TCP</a>)."
" 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 <a "
"href=\"http://en.wikipedia.org/wiki/Public_key_encryption\">claves "
"públicas</a>)."
#: 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 \"<a "
"href=\"%(tunnelrouting)s\">tunnels</a>\" - 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 <a "
"href=\"%(tunnelrouting)s\">túneles</a>\" 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 \"<a href=\"%(netdb)s\">network \n"
"database</a>\" - a custom structured <a "
"href=\"http://en.wikipedia.org/wiki/Distributed_hash_table\">\n"
"distributed hash table (DHT)</a> based off the \n"
"<a href=\"http://en.wikipedia.org/wiki/Kademlia\"> Kademlia "
"algorithm</a>. 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 \"<a href=\"%(netdb)s\">base de datos distribuida de la "
"red</a>\" - unas <a "
"href=\"http://en.wikipedia.org/wiki/Distributed_hash_table\"> tablas de "
"hash distribuidas propia (DHT) </a>basada en el <a "
"href=\"http://en.wikipedia.org/wiki/Kademlia\">algoritmo Kademlia</a>. "
"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 <a href=\"%(docs)s\">available</a>."
msgstr ""
"Tiene <a href=\"%(docs)s\">disponibles</a> 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"
"(\"<a href=\"%(i2ptunnel)s\">I2PTunnel</a>\") 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 (\"<a "
"href=\"%(i2ptunnel)s\">I2PTunnel</a>\") 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"
"<a href=\"http://www.bittorrent.com/\">BitTorrent</a>), a \n"
"distributed data store (a la <a "
"href=\"https://freenetproject.org/\">Freenet</a> / \n"
"<a href=\"http://mnetproject.org/\">MNet</a>), and a blogging system (a "
"fully \n"
"distributed <a href=\"http://www.livejournal.com/\">LiveJournal</a>), 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"
"<a href=\"http://www.bittorrent.com/\">BitTorrent</a>), almacenamiento de"
" datos distribuido (a la <a "
"href=\"https://freenetproject.org/\">Freenet</a> /<a "
"href=\"http://mnetproject.org/\">MNet</a>), y un sistema de blogs "
"totalmente distribuido <a "
"href=\"http://www.livejournal.com/\">LiveJournal</a>, 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 <a href=\"http://www.squid-cache.org/\">squid</a> 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 <a href=\"http://www.squid-"
"cache.org/\">squid</a>, 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 <a href=\"%(team)s\">team</a> is an open group, "
"welcome to all \n"
"who are interested in <a href=\"%(volunteer)s\">getting involved</a>, and"
" all of \n"
"the code is <a href=\"%(licenses)s\">open source</a>. 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"
"<a href=\"%(sam)s\">simple socket based API</a> 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 <a href=\"%(roadmap)s\">roadmap</a> "
"describes \n"
"our schedule."
msgstr ""
"El <a href=\"%(team)s\">equipo</a> de desarrollo de I2P es un grupo "
"abierto, todos los que estén interesados son bienvenidos a <a "
"href=\"%(volunteer)s\">involucrarse</a> en el proyecto, y todo el código "
"es <a href=\"%(licenses)s\">libre</a>. 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 <a "
"href=\"%(sam)s\"> API simple</a> 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 <a "
"href=\"%(roadmap)s\">hoja de ruta</a> 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 <a "
"href=\"%(papers)s\">here</a>."
msgstr ""
"Los siguientes enlaces son presentaciones, vídeos y tutoriales sobre I2P."
" Los enlaces para investigación sobre I2P están disponibles <a "
"href=\\\"%(papers)s\\\">aquí</a>."
#: 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 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"
"<a href=\"%(mp3)s\">MP3 audio</a>\n"
"<a href=\"%(transcript)s\">transcript</a>\n"
"Lance James (0x90), February 2002."
msgstr ""
"IIP Presentación en CodeCon <a href=\\\"%(mp3)s\\\">MP3 audio</a> <a "
"href=\\\"%(transcript)s\\\">transcripción</a> Lance James (0x90), Febrero"
" 2002."
#: i2p2www/pages/site/about/media.html:27
#, python-format
msgid ""
"IIP Presentation at ToorCon\n"
"<a href=\"%(mp3)s\">MP3 audio</a>\n"
"<a href=\"%(slides)s\">slides</a>\n"
"Lance James (0x90), September 2002."
msgstr ""
"IIP Presentación en ToorCon <a href=\\\"%(mp3)s\\\">MP3 audio</a> <a "
"href=\\\"%(slides)s\\\">diapositivas</a> Lance James (0x90), Septiembre "
"2002."
#: i2p2www/pages/site/about/media.html:35
#, python-format
msgid ""
"<a href=\"%(video)s\">To Be or I2P</a>\n"
"(Youtube Video)\n"
"An introduction into anonymous communication with I2P.\n"
"<a href=\"%(pdf)s\">To Be or I2P (PDF presentation)</a>,\n"
"Jens Kubieziel, 24C3 Berlin, December 28, 2007."
msgstr ""
"<a href=\\\"%(video)s\\\">To Be or I2P</a> (Youtube Video) Una "
"introducción a las comunicaciones anónimas con I2P. <a "
"href=\\\"%(pdf)s\\\">To Be or I2P (PDF presentation)</a>, Jens Kubieziel,"
" 24C3 Berlin, Diciembre 28, 2007."
#: i2p2www/pages/site/about/media.html:44
#, python-format
msgid ""
"<a href=\"%(video)s\">Video of I2P talk at Chemnitz Linux Tag</a>,\n"
"Lars Schimmer,\n"
"March 14-15, 2009"
msgstr ""
"<a href=\\\"%(video)s\\\">Vídeo de charla I2P en Chemnitz Linux Tag</a>, "
"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"
"<a href=\"%(mp3)s\">MP3 audio</a>"
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\\\". <a "
"href=\\\"%(mp3)s\\\">MP3 audio</a>"
#: i2p2www/pages/site/about/media.html:56
#, python-format
msgid ""
"<a href=\"%(link)s\">Into the I2P Darknet: Welcome to Cipherspace</a>\n"
"Adrian Crenshaw. Schmoocon Firetalk, January 2011"
msgstr ""
"<a href=\\\"%(link)s\\\">Into the I2P Darknet: Welcome to Cipherspace</a>"
" Adrian Crenshaw. Schmoocon Firetalk, Enero 2011"
#: i2p2www/pages/site/about/media.html:61
#, python-format
msgid ""
"<a href=\"%(link)s\">Using techhnology to advance liberty</a>\n"
"(Youtube Video)\n"
"Eric Johnson.\n"
"<a href=\"http://agora.io/etienne\">Agora I/O Unconference</a>, March 27,"
" 2011.\n"
"I2P covered from 10:00 to 20:00 in the video."
msgstr ""
"<a href=\\\"%(link)s\\\">Usando la tecnología para mejorar la "
"libertad</a> (Youtube Vídeo) Eric Johnson. <a "
"href=\\\"http://agora.io/etienne\\\">Agora I/O Unconference</a>, Marzo "
"27, 2011. I2P desde 10:00 a 20:00 en el vídeo."
#: i2p2www/pages/site/about/media.html:69
#, python-format
msgid ""
"<a href=\"%(pdf)s\">The Bright side of darknets</a>, FOSSCOMM Patras May "
"2011"
msgstr ""
"<a href=\"%(pdf)s\">The Bright side of darknets</a>, FOSSCOMM Patras Mayo"
" 2011"
#: i2p2www/pages/site/about/media.html:73
#, python-format
msgid ""
"<a href=\"%(link)s\">Common Darknet Weaknesses</a>\n"
"(Youtube Video)\n"
"Adrian Crenshaw, <a href=\"http://aide.marshall.edu/\">AIDE</a>, July "
"11-15, 2011."
msgstr ""
"<a href=\"%(link)s\">Common Darknet Weaknesses</a>⏎ (Vídeo en Youtube)⏎ "
"Adrian Crenshaw, <a href=\"http://aide.marshall.edu/\">AIDE</a>, Julio "
"11-15, 2011"
#: i2p2www/pages/site/about/media.html:79
#, python-format
msgid ""
"<a href=\"%(link)s\">I2P / Tor Workshop Notes</a>\n"
"Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011."
msgstr ""
"<a href=\"%(link)s\">I2P / Tor Workshop Notes</a>⏎ Adrian Crenshaw. DEF "
"CON 19, Las Vegas, Agosto 6, 2011."
#: i2p2www/pages/site/about/media.html:84
#, python-format
msgid ""
"<a href=\"%(live)s\">Cipherspaces/Darknets: An Overview Of Attack "
"Strategies -\n"
"DEF CON Live version (Youtube Video)</a>,\n"
"<a href=\"%(studio)s\">\"Studio\" version (Youtube Video)</a>,\n"
"<a href=\"%(slides)s\">Slides (ppt)</a>\n"
"Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011."
msgstr ""
"<a href=\"%(live)s\">Cipherspaces/Darknets: An Overview Of Attack "
"Strategies -⏎ DEF CON Vesión en vivo (Vídeo de Youtube)</a>,⏎ <a "
"href=\"%(studio)s\">versión de \"estudio\" (Youtube Video)</a>,⏎ <a "
"href=\"%(slides)s\">Slides (ppt)</a>⏎ Adrian Crenshaw. DEF CON 19, Las "
"Vegas, Agosto 7, 2011."
#: i2p2www/pages/site/about/media.html:94
msgid ""
"<a href=\"http://0x375.org/\">Modern cipherspace ecosystems</a>, 0x375 "
"0x06 4/11/2011"
msgstr ""
"<a href=\"http://0x375.org/\">Modern cipherspace ecosystems</a>, 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 ""
"<a href=\"%(link)s\">I2P Windows Tutorial</a>\n"
"(Youtube Video)\n"
"This guide will show you how to install I2P in Windows XP.\n"
"By <a href=\"http://telecomix.org/\">Telecomix</a>"
msgstr ""
"<a href=\"%(link)s\">I2P Windows Tutorial</a> (Youtube Video)⏎ Esta guía "
"le mostrará cono instalar I2P en Windows. Por <a "
"href=\"http://telecomix.org/\">Telecomix</a>"
#: i2p2www/pages/site/about/media.html:111
#, python-format
msgid ""
"<a href=\"%(link)s\">I2P Debian Tutorial</a>\n"
"(Youtube Video)\n"
"This will guide you through how to install I2P on a Debian Linux System.\n"
"By <a href=\"http://telecomix.org/\">Telecomix</a>"
msgstr ""
"<a href=\"%(link)s\">I2P Debian Tutorial</a>⏎ (Vídeo en Youtube) Esta "
"guía le mostrará como instalar I2P en sistemas basados en Debian. Por <a "
"href=\"http://telecomix.org/\">Telecomix</a>"
#: i2p2www/pages/site/about/media.html:119
#, python-format
msgid ""
"<a href=\"%(link)s\">How to set up anonymous site in I2P</a>\n"
"(Youtube Video)\n"
"How to set up an anonymous web site in I2P.\n"
"By <a href=\"http://telecomix.org/\">Telecomix</a>"
msgstr ""
"<a href=\"%(link)s\">How to set up anonymous site in I2P</a>⏎ (Vídeo en "
"Youtube) Como configurar una web anónima en I2P. Por <a "
"href=\"http://telecomix.org/\">Telecomix</a>"
#: i2p2www/pages/site/about/media.html:126
#, python-format
msgid ""
"<a href=\"%(link)s\">I2P Tutorial Mac OS X</a>\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 <a href=\"http://telecomix.org/\">Telecomix</a>"
msgstr ""
"<a href=\"%(link)s\">I2P Tutorial Mac OS X</a>⏎ (Vídeo en Youtube) Un "
"tutorial de como ejecutar I2P en os X y como conectar a "
"irc.telecomix.i2p. Por <a href=\"http://telecomix.org/\">Telecomix</a>"
#: i2p2www/pages/site/about/media.html:133
#, python-format
msgid ""
"<a href=\"%(link)s\">Felix Atari explains the basic principles of I2P</a>"
"\n"
"(Youtube Video)\n"
"Agent Felix Atari of the Telecomix Crypto Munitions Bureau.\n"
"By <a href=\"http://telecomix.org/\">Telecomix</a>"
msgstr ""
"<a href=\"%(link)s\">Felix Atari explains the basic principles of I2P</a>"
" (Vídeo en Youtube) Agent Felix Atari of the Telecomix Crypto Munitions "
"Bureau. Por <a href=\"http://telecomix.org/\">Telecomix</a>"
#: i2p2www/pages/site/about/media.html:140
#, python-format
msgid ""
"<a href=\"%(link)s\">How to get onto I2P, the anonymous P2P Darknet "
"(Windows Install)</a>\n"
"(Youtube Video)\n"
"This tutorial shows how to install and configure software needed to "
"access I2P."
msgstr ""
"<a href=\"%(link)s\">How to get onto I2P, the anonymous P2P Darknet "
"(Windows Install)</a> (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 ""
"<a href=\"%(link)s\">How to connect to I2P</a>\n"
"(Youtube Video)\n"
"How to install I2P on Ubuntu."
msgstr ""
"<a href=\"%(link)s\">How to connect to I2P</a> (Vídeo en Youtube) Como "
"instalar I2P en Ubuntu."
#: i2p2www/pages/site/about/media.html:152
#, python-format
msgid ""
"<a href=\"%(link)s\">Installing the I2P darknet software in Linux</a>\n"
"(Video)\n"
"Adrian Crenshaw.\n"
"January 2011"
msgstr ""
"<a href=\"%(link)s\">Installing the I2P darknet software in Linux</a>⏎ "
"(Vídeo)⏎ Adrian Crenshaw.⏎ Enero 2011"
#: i2p2www/pages/site/about/media.html:159
#, python-format
msgid ""
"<a href=\"%(link)s\">Short garlic routing animation</a>\n"
"(Youtube Video)\n"
"Adrian Crenshaw.\n"
msgstr ""
"<a href=\"%(link)s\">Short garlic routing animation</a> (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"
"<a href=\"%(link1)s\">Part 1</a>\n"
"<a href=\"%(link2)s\">Part 2</a>\n"
"July 26, 2002."
msgstr ""
"0x90 Entrevistado por DistributedCity <a href=\"%(link1)s\">Parte 1</a> "
"<a href=\"%(link2)s\">Parte 2</a> Julio 26, 2002."
#: i2p2www/pages/site/about/media.html:178
#, python-format
msgid ""
"0x90 Interviewed by El Pais\n"
"(original in Spanish)\n"
"<a href=\"%(link)s\">English translation</a>\n"
"October 31, 2002."
msgstr ""
"0x90 Entrevistado por El Pais (original en Castellano) <a "
"href=\"%(link)s\">Traducción al inglés</a> Octubre 31, 2002."
#: i2p2www/pages/site/about/media.html:185
#, python-format
msgid ""
"<a href=\"%(link)s\">2003 Business Week article referencing "
"invisiblenet</a>"
msgstr ""
"<a href=\"%(link)s\">2003 Business Week article referencing "
"invisiblenet</a>"
#: i2p2www/pages/site/about/media.html:189
#, python-format
msgid ""
"<a href=\"%(link)s\">Netzwelt.de article about being anonymous in the "
"Internet</a>\n"
"(German)\n"
"November 2007."
msgstr ""
"<a href=\"%(link)s\">Artículo del Netzwelt.de sobre como permanecer "
"anónimos en Internet</a> (Alemán) Noviembre 2007."
#: i2p2www/pages/site/about/media.html:195
#, python-format
msgid ""
"<a href=\"%(link)s\">zzz interviewed by gulli.com</a>\n"
"March 2009\n"
"<a href=\"%(german)s\">German translation</a>\n"
"<a href=\"%(russian)s\">Russian translation</a>"
msgstr ""
"<a href=\"%(link)s\">zzz entrevistado por gulli.com</a>⏎ Marzo 2009⏎ <a "
"href=\"%(german)s\">traducción en alemán</a> <a "
"href=\"%(russian)s\">traducción en ruso</a>"
#: i2p2www/pages/site/about/media.html:204
#, python-format
msgid ""
"<a href=\"%(mp3)s\">zzz interviewed on the InfoSec Daily Podcast Ep. 454 "
"(mp3)</a>\n"
"August 18, 2011"
msgstr ""
"<a href=\"%(mp3)s\">zzz entrevistado en el podcast diario de InfoSec Ep."
" 454 (mp3)</a>⏎ Agosto 18, 2011"
#: i2p2www/pages/site/about/media.html:209
#, python-format
msgid ""
"<a href=\"%(link)s\">I2P - Anonymity for the Masses</a>,\n"
"Jonathan Cox,\n"
"November 11, 2011."
msgstr ""
"<a href=\"%(link)s\">I2P - Anonymity for the Masses</a>,⏎ Jonathan Cox,⏎ "
"Noviembre 11, 2011."
#: i2p2www/pages/site/about/media.html:215
#, python-format
msgid ""
"<a href=\"%(mp3)s\">zzz and Lance James interviewed on the InfoSec Daily "
"Podcast Ep. 596 (mp3)</a>\n"
"February 16, 2012"
msgstr ""
"<a href=\"%(mp3)s\">zzz y Lance James entrevistados en el podcast diario "
"de InfoSec Ep. 596 (mp3)</a> 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"
"<a href=\"%(volunteer)s\">Get involved!</a>"
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.<a href=\"%(volunteer)s\">¿Únete!</a>"
#: 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 "<a href=\"http://%(forum)s/\">Forum</a> admin"
msgstr "Administrador del <a href=\"http://%(forum)s/\">Foro</a>"
#: 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 "<a href=\"%(monotone)s\">Monotone</a> guru"
msgstr "Gurú de <a href=\"%(monotone)s\">Monotone</a>"
#: 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
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 "<a href=\"http://%(website)s/\">Webserver</a> admin"
msgstr "Administrador del <a href=\"http://%(website)s/\">servidor web</a>"
#: 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 "<a href=\"http://%(website)s/\">Website</a> admin"
msgstr "Administrador de la <a href=\"http://%(website)s/\">página web</a>"
#: 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
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 "<a href=\"http://%(postman)s/\">I2P mail</a> lead"
msgstr "Encargado de <a href=\"http://%(postman)s/\">I2P mail</a>"
#: 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 "<a href=\"http://%(i2host)s/\">I2Host</a> lead"
msgstr "Encargado del <a href=\"http://%(i2host)s/\">I2Host</a>"
#: 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 "<a href=\"http://%(bob)s/\">BOB</a> lead"
msgstr "Encargado de <a href=\"http://%(bob)s/\">BOB</a>"
#: 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 "<a href=\"http://%(bote)s/\">I2P-Bote</a> lead"
msgstr "Encargado de <a href=\"http://%(bote)s/\">I2P-Bote</a>"
#: i2p2www/pages/site/about/team.html:129
msgid "I2PBote plugin"
msgstr "pluguin I2PBote"
#: i2p2www/pages/site/about/team.html:132
#, python-format
msgid "<a href=\"http://%(bob)s/\">Robert</a> lead"
msgstr "Encargado de <a href=\"http://%(bob)s/\">Robert</a>"
#: 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 "<a href=\"http://%(forum)s/viewforum?f=25\">I2Phex</a> lead"
msgstr "Encargado de <a href=\"http://%(forum)s/viewforum?f=25\">I2Phex</a> "
#: 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 "<a href=\"http://%(forum)s/viewforum?f=21\">I2PSnark</a> lead"
msgstr "Encargado de <a href=\"http://%(forum)s/viewforum?f=21\">I2PSnark</a>"
#: 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 "<a href=\"http://%(forum)s/viewforum?f=30\">iMule</a> lead"
msgstr "Encargado de <a href=\"http://%(forum)s/viewforum?f=30\">iMule</a>"
#: 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 "<a href=\"http://%(forum)s/viewforum?f=29\">Syndie</a> lead"
msgstr "Encargado de <a href=\"http://%(forum)s/viewforum?f=29\">Syndie</a>"
#: i2p2www/pages/site/about/team.html:154
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 "&hellip; and many others"
msgstr "&hellip; y muchas otras"
#: 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 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 <a href=\"%(history)s\">\n"
"Performance History</a>."
msgstr ""
"Para ver las mejoras de rendimiento pasadas vea <a href=\"%(history)s\"> "
"Historial de rendimiento</a>."
#: 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 <a href=\"%(sybilpdf)s\">Sybil</a> 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 <a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> "
"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"
"<a href=\"%(elgamalaes)s#future\">ElGamal/AES+SessionTag page</a>."
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 <a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> \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"
"<a href=\"%(streaming)s#future\">streaming library page</a>."
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 <a href=\"%(performance)s\">Performance</a> "
"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"
"<a href=\"%(modpow)s\">modPow</a>.\n"
"Rather than try to tune this method, we'll call out to\n"
"<a href=\"%(gmp)s\">GNU MP</a> - an insanely fast math library\n"
"(with tuned assembler for many architectures). (<i>Editor: see\n"
"<a href=\"%(jbigi)s\">NativeBigInteger for faster public key "
"cryptography</a></i>)"
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 <i>always</i> 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 <a href=\"%(link)s\">said</a>, 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 "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, 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 <b>yes</b>."
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 <b>sí</b>."
#: 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"
"<a href=\"%(future)s\">Future Performance Improvements</a>."
msgstr ""
"Para futuras mejoras en el rendimiento vea <a href=\"%(future)s\">mejoras"
" futuras en el rendimiento</a>."
Reference in New Issue Copy Permalink