Updated translation strings

This commit is contained in:
str4d
2017-06-01 12:22:11 +00:00
parent 8e33a01514
commit a1b93fc892
27 changed files with 2032 additions and 112 deletions

View File

@ -17,7 +17,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 10:49+0000\n"
"Last-Translator: Ettore Atalan <atalanttore@googlemail.com>\n"
"Language-Team: German (http://www.transifex.com/otf/I2P/language/de/)\n"
@ -5840,6 +5840,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
msgid ""
"Take part in Summer Dev!\n"
"========================"
@ -5875,6 +5876,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
msgid ""
"We'll be posting here as we go, but you can also follow our progress, and"
" share\n"
@ -6894,3 +6896,199 @@ msgstr ""
msgid "Add bash completion scripts to Debian packages"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
#, fuzzy
msgid ""
"================================\n"
"I2P Summer Dev 2017: MOAR Speed!\n"
"================================"
msgstr ""
"==============================\n"
"Die Geburt von Datenschutzlösungen\n"
"=============================="
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
msgid ""
"This year's Summer Dev will be focused on metrics collection and "
"performance improvements for the network."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
msgid ""
"It's that time of year again! We're embarking on our summer development\n"
"programme, where we focus on a particular aspect of I2P to push it "
"forward. For\n"
"the next three months, we'll be encouraging both new contributors and "
"existing\n"
"community members to pick a task and have fun with it!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
msgid ""
"`Last year`_, we focused on helping users and developers leverage I2P, by"
"\n"
"improving API tooling and giving some love to applications that run over "
"I2P.\n"
"This year, we want to improve the user experience by working on an aspect"
" that\n"
"affects everyone: performance."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
msgid "`Last year`"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
msgid ""
"Despite onion-routing networks often being called \"low-latency\" "
"networks, there\n"
"is significant overhead created by routing traffic through additional "
"computers.\n"
"I2P's unidirectional tunnel design means that by default, a round trip "
"between\n"
"two Destinations will involve twelve participants! Improving the "
"performance of\n"
"these participants will help to both reduce the latency of end-to-end\n"
"connections [1]_, and increase the quality of tunnels network-wide."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
msgid ""
"MOAR speed!\n"
"==========="
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
msgid "Our development programme this year will have four components:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
#, fuzzy
msgid ""
"Measure\n"
"-------"
msgstr ""
"Neue Benutzer\n"
"---------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
msgid ""
"We can't tell if we improve performance without a baseline! We'll be "
"creating a\n"
"metrics system for collecting usage and performance data about I2P in a\n"
"privacy-preserving way, as well as porting various benchmarking tools to "
"run\n"
"over I2P (e.g. iperf3_)."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
#, fuzzy
msgid ""
"Optimise\n"
"--------"
msgstr ""
"Adresse\n"
"--------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
msgid ""
"There's a lot of scope for improving the performance of our existing "
"code, to\n"
"e.g. reduce the overhead of participating in tunnels. We will be looking "
"at\n"
"potential improvements to:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
msgid "Cryptographic primitives"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
msgid ""
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
"(Streaming_)"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
msgid "Peer profiling"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
msgid "Tunnel path selection"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
#, fuzzy
msgid ""
"Advance\n"
"-------"
msgstr ""
"F-Droid\n"
"-------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
msgid ""
"We have several open proposals for improving the scalability of the I2P "
"network\n"
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
"will be\n"
"working on these proposals, and begin implementing the finalised ones in "
"the\n"
"various network routers. The more feedback these proposals receive, the "
"sooner\n"
"we can roll them out, and the sooner I2P services can start using them!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
#, fuzzy
msgid ""
"Research\n"
"--------"
msgstr ""
"Neue Benutzer\n"
"---------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
msgid ""
"I2P is a packet-switched network, like the internet it runs on top of. "
"This\n"
"gives us significant flexibility in how we route packets, both for "
"performance\n"
"and privacy. The majority of this flexibility is unexplored! We want to\n"
"encourage research into how various clearnet techniques for improving "
"bandwidth\n"
"can be applied to I2P, and how they might affect the privacy of network\n"
"participants."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
msgid ""
"We have many more ideas for things we'd like to get done in these areas. "
"If\n"
"you're interested in hacking on privacy and anonymity software, designing"
"\n"
"protocols (cryptographic or otherwise), or researching future ideas - "
"come and\n"
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
"into\n"
"our community, both inside and outside the I2P network. We'll also be "
"sending\n"
"I2P stickers out to all new contributors taking part! If you want to chat"
" about\n"
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
" can\n"
"also find us in #i2p-dev on OFTC or Freenode."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
msgid ""
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
" attacks, so it would be reasonable to ask whether improved performance "
"equates to reduced privacy. Some latency can help privacy if applied "
"correctly via random delays or batching (neither of which are currently "
"employed by any general-purpose onion-routing network). However, if a "
"tunnel has uniform overall latency, then traffic confirmation attacks "
"should be just as viable with or without that latency; thus there should "
"be little statistical difference when the latency is reduced uniformly."
msgstr ""

View File

@ -16,7 +16,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 10:49+0000\n"
"Last-Translator: Ettore Atalan <atalanttore@googlemail.com>\n"
"Language-Team: German (http://www.transifex.com/otf/I2P/language/de/)\n"
@ -460,26 +460,26 @@ msgstr "Entwicklungsplan"
msgid "April 2017"
msgstr "April 2017"
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr "Benutzerdefinierte Nachrichtenverzögerungen"
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Greek (http://www.transifex.com/otf/I2P/language/el/)\n"
@ -342,26 +342,26 @@ msgstr ""
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -15,7 +15,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 17:04+0000\n"
"Last-Translator: strel\n"
"Language-Team: Spanish (http://www.transifex.com/otf/I2P/language/es/)\n"
@ -7592,6 +7592,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
msgid ""
"Take part in Summer Dev!\n"
"========================"
@ -7648,6 +7649,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
msgid ""
"We'll be posting here as we go, but you can also follow our progress, and"
" share\n"
@ -8934,3 +8936,202 @@ msgstr ""
msgid "Add bash completion scripts to Debian packages"
msgstr "Añade scripts bash de completado a los paquetes Debian."
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
#, fuzzy
msgid ""
"================================\n"
"I2P Summer Dev 2017: MOAR Speed!\n"
"================================"
msgstr ""
"==========================\n"
"Batida de Summer Dev: APIs\n"
"=========================="
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
msgid ""
"This year's Summer Dev will be focused on metrics collection and "
"performance improvements for the network."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
msgid ""
"It's that time of year again! We're embarking on our summer development\n"
"programme, where we focus on a particular aspect of I2P to push it "
"forward. For\n"
"the next three months, we'll be encouraging both new contributors and "
"existing\n"
"community members to pick a task and have fun with it!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
msgid ""
"`Last year`_, we focused on helping users and developers leverage I2P, by"
"\n"
"improving API tooling and giving some love to applications that run over "
"I2P.\n"
"This year, we want to improve the user experience by working on an aspect"
" that\n"
"affects everyone: performance."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
msgid "`Last year`"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
msgid ""
"Despite onion-routing networks often being called \"low-latency\" "
"networks, there\n"
"is significant overhead created by routing traffic through additional "
"computers.\n"
"I2P's unidirectional tunnel design means that by default, a round trip "
"between\n"
"two Destinations will involve twelve participants! Improving the "
"performance of\n"
"these participants will help to both reduce the latency of end-to-end\n"
"connections [1]_, and increase the quality of tunnels network-wide."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
#, fuzzy
msgid ""
"MOAR speed!\n"
"==========="
msgstr ""
"Tareas domésticas\n"
"============"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
msgid "Our development programme this year will have four components:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
#, fuzzy
msgid ""
"Measure\n"
"-------"
msgstr ""
"Lugar de reunión\n"
"-----"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
msgid ""
"We can't tell if we improve performance without a baseline! We'll be "
"creating a\n"
"metrics system for collecting usage and performance data about I2P in a\n"
"privacy-preserving way, as well as porting various benchmarking tools to "
"run\n"
"over I2P (e.g. iperf3_)."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
#, fuzzy
msgid ""
"Optimise\n"
"--------"
msgstr ""
"Ubicación\n"
"--------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
msgid ""
"There's a lot of scope for improving the performance of our existing "
"code, to\n"
"e.g. reduce the overhead of participating in tunnels. We will be looking "
"at\n"
"potential improvements to:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
msgid "Cryptographic primitives"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
msgid ""
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
"(Streaming_)"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
msgid "Peer profiling"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
msgid "Tunnel path selection"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
#, fuzzy
msgid ""
"Advance\n"
"-------"
msgstr ""
"Lugar de reunión\n"
"-----"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
msgid ""
"We have several open proposals for improving the scalability of the I2P "
"network\n"
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
"will be\n"
"working on these proposals, and begin implementing the finalised ones in "
"the\n"
"various network routers. The more feedback these proposals receive, the "
"sooner\n"
"we can roll them out, and the sooner I2P services can start using them!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
#, fuzzy
msgid ""
"Research\n"
"--------"
msgstr ""
"Nuevos usuarios\n"
"---------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
msgid ""
"I2P is a packet-switched network, like the internet it runs on top of. "
"This\n"
"gives us significant flexibility in how we route packets, both for "
"performance\n"
"and privacy. The majority of this flexibility is unexplored! We want to\n"
"encourage research into how various clearnet techniques for improving "
"bandwidth\n"
"can be applied to I2P, and how they might affect the privacy of network\n"
"participants."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
msgid ""
"We have many more ideas for things we'd like to get done in these areas. "
"If\n"
"you're interested in hacking on privacy and anonymity software, designing"
"\n"
"protocols (cryptographic or otherwise), or researching future ideas - "
"come and\n"
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
"into\n"
"our community, both inside and outside the I2P network. We'll also be "
"sending\n"
"I2P stickers out to all new contributors taking part! If you want to chat"
" about\n"
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
" can\n"
"also find us in #i2p-dev on OFTC or Freenode."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
msgid ""
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
" attacks, so it would be reasonable to ask whether improved performance "
"equates to reduced privacy. Some latency can help privacy if applied "
"correctly via random delays or batching (neither of which are currently "
"employed by any general-purpose onion-routing network). However, if a "
"tunnel has uniform overall latency, then traffic confirmation attacks "
"should be just as viable with or without that latency; thus there should "
"be little statistical difference when the latency is reduced uniformly."
msgstr ""

View File

@ -16,7 +16,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 17:08+0000\n"
"Last-Translator: strel\n"
"Language-Team: Spanish (http://www.transifex.com/otf/I2P/language/es/)\n"
@ -445,7 +445,7 @@ msgstr "Hoja de ruta"
msgid "April 2017"
msgstr "Abril de 2017"
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
@ -455,19 +455,19 @@ msgstr ""
"mejorar los <a href=\"%(todo)s#fullRestrictedRoutes\">ruters "
"restringidos</a>"
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr "Rutas restringidas"
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr "Mezclado y relleno de los túneles"
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr "Mensajes con el retraso definido por los usuarios"
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -16,7 +16,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-31 17:16+0000\n"
"Last-Translator: French language coordinator <french.coordinator@rbox.me>"
"\n"
@ -6777,6 +6777,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
msgid ""
"Take part in Summer Dev!\n"
"========================"
@ -6814,6 +6815,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
msgid ""
"We'll be posting here as we go, but you can also follow our progress, and"
" share\n"
@ -7933,3 +7935,202 @@ msgstr ""
msgid "Add bash completion scripts to Debian packages"
msgstr "Ajout de scripts d'achèvement bash aux paquets Debian"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
#, fuzzy
msgid ""
"================================\n"
"I2P Summer Dev 2017: MOAR Speed!\n"
"================================"
msgstr ""
"============================\n"
"I2PCon : Mission Accomplie\n"
"============================"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
msgid ""
"This year's Summer Dev will be focused on metrics collection and "
"performance improvements for the network."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
msgid ""
"It's that time of year again! We're embarking on our summer development\n"
"programme, where we focus on a particular aspect of I2P to push it "
"forward. For\n"
"the next three months, we'll be encouraging both new contributors and "
"existing\n"
"community members to pick a task and have fun with it!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
msgid ""
"`Last year`_, we focused on helping users and developers leverage I2P, by"
"\n"
"improving API tooling and giving some love to applications that run over "
"I2P.\n"
"This year, we want to improve the user experience by working on an aspect"
" that\n"
"affects everyone: performance."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
msgid "`Last year`"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
msgid ""
"Despite onion-routing networks often being called \"low-latency\" "
"networks, there\n"
"is significant overhead created by routing traffic through additional "
"computers.\n"
"I2P's unidirectional tunnel design means that by default, a round trip "
"between\n"
"two Destinations will involve twelve participants! Improving the "
"performance of\n"
"these participants will help to both reduce the latency of end-to-end\n"
"connections [1]_, and increase the quality of tunnels network-wide."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
#, fuzzy
msgid ""
"MOAR speed!\n"
"==========="
msgstr ""
"Tâche ménagère\n"
"============"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
msgid "Our development programme this year will have four components:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
#, fuzzy
msgid ""
"Measure\n"
"-------"
msgstr ""
"Ressources\n"
"-----"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
msgid ""
"We can't tell if we improve performance without a baseline! We'll be "
"creating a\n"
"metrics system for collecting usage and performance data about I2P in a\n"
"privacy-preserving way, as well as porting various benchmarking tools to "
"run\n"
"over I2P (e.g. iperf3_)."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
#, fuzzy
msgid ""
"Optimise\n"
"--------"
msgstr ""
"Localisation\n"
"--------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
msgid ""
"There's a lot of scope for improving the performance of our existing "
"code, to\n"
"e.g. reduce the overhead of participating in tunnels. We will be looking "
"at\n"
"potential improvements to:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
msgid "Cryptographic primitives"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
msgid ""
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
"(Streaming_)"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
msgid "Peer profiling"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
msgid "Tunnel path selection"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
#, fuzzy
msgid ""
"Advance\n"
"-------"
msgstr ""
"Ressources\n"
"-----"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
msgid ""
"We have several open proposals for improving the scalability of the I2P "
"network\n"
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
"will be\n"
"working on these proposals, and begin implementing the finalised ones in "
"the\n"
"various network routers. The more feedback these proposals receive, the "
"sooner\n"
"we can roll them out, and the sooner I2P services can start using them!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
#, fuzzy
msgid ""
"Research\n"
"--------"
msgstr ""
"Nouveaux utilisateurs\n"
"---------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
msgid ""
"I2P is a packet-switched network, like the internet it runs on top of. "
"This\n"
"gives us significant flexibility in how we route packets, both for "
"performance\n"
"and privacy. The majority of this flexibility is unexplored! We want to\n"
"encourage research into how various clearnet techniques for improving "
"bandwidth\n"
"can be applied to I2P, and how they might affect the privacy of network\n"
"participants."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
msgid ""
"We have many more ideas for things we'd like to get done in these areas. "
"If\n"
"you're interested in hacking on privacy and anonymity software, designing"
"\n"
"protocols (cryptographic or otherwise), or researching future ideas - "
"come and\n"
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
"into\n"
"our community, both inside and outside the I2P network. We'll also be "
"sending\n"
"I2P stickers out to all new contributors taking part! If you want to chat"
" about\n"
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
" can\n"
"also find us in #i2p-dev on OFTC or Freenode."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
msgid ""
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
" attacks, so it would be reasonable to ask whether improved performance "
"equates to reduced privacy. Some latency can help privacy if applied "
"correctly via random delays or batching (neither of which are currently "
"employed by any general-purpose onion-routing network). However, if a "
"tunnel has uniform overall latency, then traffic confirmation attacks "
"should be just as viable with or without that latency; thus there should "
"be little statistical difference when the latency is reduced uniformly."
msgstr ""

View File

@ -14,7 +14,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-31 13:59+0000\n"
"Last-Translator: French language coordinator <french.coordinator@rbox.me>"
"\n"
@ -463,7 +463,7 @@ msgstr "Feuille de route"
msgid "April 2017"
msgstr "Avril 2017"
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
@ -473,19 +473,19 @@ msgstr ""
"accessibles / <a href=\"%(todo)s#fullRestrictedRoutes\">routes "
"restreintes</a> améliorées"
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr "Routes entièrement restreintes"
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr "Mixage (mélange) de tunnel et remplissage"
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr "Retards de message définis par l'utilisateur"
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Galician (http://www.transifex.com/otf/I2P/language/gl/)\n"
@ -342,26 +342,26 @@ msgstr ""
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2014-02-09 19:53+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: he <LL@li.org>\n"
@ -5646,6 +5646,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
msgid ""
"Take part in Summer Dev!\n"
"========================"
@ -5681,6 +5682,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
msgid ""
"We'll be posting here as we go, but you can also follow our progress, and"
" share\n"
@ -6679,3 +6681,183 @@ msgstr ""
msgid "Add bash completion scripts to Debian packages"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
msgid ""
"================================\n"
"I2P Summer Dev 2017: MOAR Speed!\n"
"================================"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
msgid ""
"This year's Summer Dev will be focused on metrics collection and "
"performance improvements for the network."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
msgid ""
"It's that time of year again! We're embarking on our summer development\n"
"programme, where we focus on a particular aspect of I2P to push it "
"forward. For\n"
"the next three months, we'll be encouraging both new contributors and "
"existing\n"
"community members to pick a task and have fun with it!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
msgid ""
"`Last year`_, we focused on helping users and developers leverage I2P, by"
"\n"
"improving API tooling and giving some love to applications that run over "
"I2P.\n"
"This year, we want to improve the user experience by working on an aspect"
" that\n"
"affects everyone: performance."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
msgid "`Last year`"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
msgid ""
"Despite onion-routing networks often being called \"low-latency\" "
"networks, there\n"
"is significant overhead created by routing traffic through additional "
"computers.\n"
"I2P's unidirectional tunnel design means that by default, a round trip "
"between\n"
"two Destinations will involve twelve participants! Improving the "
"performance of\n"
"these participants will help to both reduce the latency of end-to-end\n"
"connections [1]_, and increase the quality of tunnels network-wide."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
msgid ""
"MOAR speed!\n"
"==========="
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
msgid "Our development programme this year will have four components:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
msgid ""
"Measure\n"
"-------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
msgid ""
"We can't tell if we improve performance without a baseline! We'll be "
"creating a\n"
"metrics system for collecting usage and performance data about I2P in a\n"
"privacy-preserving way, as well as porting various benchmarking tools to "
"run\n"
"over I2P (e.g. iperf3_)."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
msgid ""
"Optimise\n"
"--------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
msgid ""
"There's a lot of scope for improving the performance of our existing "
"code, to\n"
"e.g. reduce the overhead of participating in tunnels. We will be looking "
"at\n"
"potential improvements to:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
msgid "Cryptographic primitives"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
msgid ""
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
"(Streaming_)"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
msgid "Peer profiling"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
msgid "Tunnel path selection"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
msgid ""
"Advance\n"
"-------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
msgid ""
"We have several open proposals for improving the scalability of the I2P "
"network\n"
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
"will be\n"
"working on these proposals, and begin implementing the finalised ones in "
"the\n"
"various network routers. The more feedback these proposals receive, the "
"sooner\n"
"we can roll them out, and the sooner I2P services can start using them!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
msgid ""
"Research\n"
"--------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
msgid ""
"I2P is a packet-switched network, like the internet it runs on top of. "
"This\n"
"gives us significant flexibility in how we route packets, both for "
"performance\n"
"and privacy. The majority of this flexibility is unexplored! We want to\n"
"encourage research into how various clearnet techniques for improving "
"bandwidth\n"
"can be applied to I2P, and how they might affect the privacy of network\n"
"participants."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
msgid ""
"We have many more ideas for things we'd like to get done in these areas. "
"If\n"
"you're interested in hacking on privacy and anonymity software, designing"
"\n"
"protocols (cryptographic or otherwise), or researching future ideas - "
"come and\n"
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
"into\n"
"our community, both inside and outside the I2P network. We'll also be "
"sending\n"
"I2P stickers out to all new contributors taking part! If you want to chat"
" about\n"
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
" can\n"
"also find us in #i2p-dev on OFTC or Freenode."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
msgid ""
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
" attacks, so it would be reasonable to ask whether improved performance "
"equates to reduced privacy. Some latency can help privacy if applied "
"correctly via random delays or batching (neither of which are currently "
"employed by any general-purpose onion-routing network). However, if a "
"tunnel has uniform overall latency, then traffic confirmation attacks "
"should be just as viable with or without that latency; thus there should "
"be little statistical difference when the latency is reduced uniformly."
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2014-02-09 19:53+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: he <LL@li.org>\n"
@ -342,26 +342,26 @@ msgstr ""
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Indonesian (http://www.transifex.com/otf/I2P/language/id/)"
@ -430,7 +430,7 @@ msgstr "Roadmap"
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
@ -440,19 +440,19 @@ msgstr ""
"ditingkatkan <a href=\"%(todo)s#fullRestrictedRoutes\">pembatasan "
"rute</a>"
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -11,7 +11,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-17 12:01+0000\n"
"Last-Translator: Sebastiano Pistore <olatusrooc@virgilio.it>\n"
"Language-Team: Italian (http://www.transifex.com/otf/I2P/language/it/)\n"
@ -5766,6 +5766,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
msgid ""
"Take part in Summer Dev!\n"
"========================"
@ -5801,6 +5802,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
msgid ""
"We'll be posting here as we go, but you can also follow our progress, and"
" share\n"
@ -6816,3 +6818,202 @@ msgstr ""
msgid "Add bash completion scripts to Debian packages"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
#, fuzzy
msgid ""
"================================\n"
"I2P Summer Dev 2017: MOAR Speed!\n"
"================================"
msgstr ""
"============================\n"
"I2PCon: Missione completata\n"
"============================"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
msgid ""
"This year's Summer Dev will be focused on metrics collection and "
"performance improvements for the network."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
msgid ""
"It's that time of year again! We're embarking on our summer development\n"
"programme, where we focus on a particular aspect of I2P to push it "
"forward. For\n"
"the next three months, we'll be encouraging both new contributors and "
"existing\n"
"community members to pick a task and have fun with it!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
msgid ""
"`Last year`_, we focused on helping users and developers leverage I2P, by"
"\n"
"improving API tooling and giving some love to applications that run over "
"I2P.\n"
"This year, we want to improve the user experience by working on an aspect"
" that\n"
"affects everyone: performance."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
msgid "`Last year`"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
msgid ""
"Despite onion-routing networks often being called \"low-latency\" "
"networks, there\n"
"is significant overhead created by routing traffic through additional "
"computers.\n"
"I2P's unidirectional tunnel design means that by default, a round trip "
"between\n"
"two Destinations will involve twelve participants! Improving the "
"performance of\n"
"these participants will help to both reduce the latency of end-to-end\n"
"connections [1]_, and increase the quality of tunnels network-wide."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
#, fuzzy
msgid ""
"MOAR speed!\n"
"==========="
msgstr ""
"Come si usa\n"
"==============="
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
msgid "Our development programme this year will have four components:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
#, fuzzy
msgid ""
"Measure\n"
"-------"
msgstr ""
"Nuovi utenti\n"
"---------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
msgid ""
"We can't tell if we improve performance without a baseline! We'll be "
"creating a\n"
"metrics system for collecting usage and performance data about I2P in a\n"
"privacy-preserving way, as well as porting various benchmarking tools to "
"run\n"
"over I2P (e.g. iperf3_)."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
#, fuzzy
msgid ""
"Optimise\n"
"--------"
msgstr ""
"Percorso\n"
"--------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
msgid ""
"There's a lot of scope for improving the performance of our existing "
"code, to\n"
"e.g. reduce the overhead of participating in tunnels. We will be looking "
"at\n"
"potential improvements to:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
msgid "Cryptographic primitives"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
msgid ""
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
"(Streaming_)"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
msgid "Peer profiling"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
msgid "Tunnel path selection"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
#, fuzzy
msgid ""
"Advance\n"
"-------"
msgstr ""
"F-Droid\n"
"-------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
msgid ""
"We have several open proposals for improving the scalability of the I2P "
"network\n"
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
"will be\n"
"working on these proposals, and begin implementing the finalised ones in "
"the\n"
"various network routers. The more feedback these proposals receive, the "
"sooner\n"
"we can roll them out, and the sooner I2P services can start using them!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
#, fuzzy
msgid ""
"Research\n"
"--------"
msgstr ""
"Nuovi utenti\n"
"---------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
msgid ""
"I2P is a packet-switched network, like the internet it runs on top of. "
"This\n"
"gives us significant flexibility in how we route packets, both for "
"performance\n"
"and privacy. The majority of this flexibility is unexplored! We want to\n"
"encourage research into how various clearnet techniques for improving "
"bandwidth\n"
"can be applied to I2P, and how they might affect the privacy of network\n"
"participants."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
msgid ""
"We have many more ideas for things we'd like to get done in these areas. "
"If\n"
"you're interested in hacking on privacy and anonymity software, designing"
"\n"
"protocols (cryptographic or otherwise), or researching future ideas - "
"come and\n"
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
"into\n"
"our community, both inside and outside the I2P network. We'll also be "
"sending\n"
"I2P stickers out to all new contributors taking part! If you want to chat"
" about\n"
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
" can\n"
"also find us in #i2p-dev on OFTC or Freenode."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
msgid ""
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
" attacks, so it would be reasonable to ask whether improved performance "
"equates to reduced privacy. Some latency can help privacy if applied "
"correctly via random delays or batching (neither of which are currently "
"employed by any general-purpose onion-routing network). However, if a "
"tunnel has uniform overall latency, then traffic confirmation attacks "
"should be just as viable with or without that latency; thus there should "
"be little statistical difference when the latency is reduced uniformly."
msgstr ""

View File

@ -14,7 +14,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-17 11:42+0000\n"
"Last-Translator: Sebastiano Pistore <olatusrooc@virgilio.it>\n"
"Language-Team: Italian (http://www.transifex.com/otf/I2P/language/it/)\n"
@ -416,26 +416,26 @@ msgstr "Roadma"
msgid "April 2017"
msgstr "Aprile 2017"
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr "Tunnel mixing e padding"
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr "Messaggio di attesa definito dall'utente"
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2014-05-23 23:34+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Japanese "
@ -5760,6 +5760,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
msgid ""
"Take part in Summer Dev!\n"
"========================"
@ -5795,6 +5796,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
msgid ""
"We'll be posting here as we go, but you can also follow our progress, and"
" share\n"
@ -6832,3 +6834,187 @@ msgstr ""
msgid "Add bash completion scripts to Debian packages"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
#, fuzzy
msgid ""
"================================\n"
"I2P Summer Dev 2017: MOAR Speed!\n"
"================================"
msgstr ""
"=====================\n"
"Syndie 1.105b リリース\n"
"====================="
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
msgid ""
"This year's Summer Dev will be focused on metrics collection and "
"performance improvements for the network."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
msgid ""
"It's that time of year again! We're embarking on our summer development\n"
"programme, where we focus on a particular aspect of I2P to push it "
"forward. For\n"
"the next three months, we'll be encouraging both new contributors and "
"existing\n"
"community members to pick a task and have fun with it!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
msgid ""
"`Last year`_, we focused on helping users and developers leverage I2P, by"
"\n"
"improving API tooling and giving some love to applications that run over "
"I2P.\n"
"This year, we want to improve the user experience by working on an aspect"
" that\n"
"affects everyone: performance."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
msgid "`Last year`"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
msgid ""
"Despite onion-routing networks often being called \"low-latency\" "
"networks, there\n"
"is significant overhead created by routing traffic through additional "
"computers.\n"
"I2P's unidirectional tunnel design means that by default, a round trip "
"between\n"
"two Destinations will involve twelve participants! Improving the "
"performance of\n"
"these participants will help to both reduce the latency of end-to-end\n"
"connections [1]_, and increase the quality of tunnels network-wide."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
msgid ""
"MOAR speed!\n"
"==========="
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
msgid "Our development programme this year will have four components:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
msgid ""
"Measure\n"
"-------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
msgid ""
"We can't tell if we improve performance without a baseline! We'll be "
"creating a\n"
"metrics system for collecting usage and performance data about I2P in a\n"
"privacy-preserving way, as well as porting various benchmarking tools to "
"run\n"
"over I2P (e.g. iperf3_)."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
msgid ""
"Optimise\n"
"--------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
msgid ""
"There's a lot of scope for improving the performance of our existing "
"code, to\n"
"e.g. reduce the overhead of participating in tunnels. We will be looking "
"at\n"
"potential improvements to:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
msgid "Cryptographic primitives"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
msgid ""
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
"(Streaming_)"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
msgid "Peer profiling"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
msgid "Tunnel path selection"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
msgid ""
"Advance\n"
"-------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
msgid ""
"We have several open proposals for improving the scalability of the I2P "
"network\n"
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
"will be\n"
"working on these proposals, and begin implementing the finalised ones in "
"the\n"
"various network routers. The more feedback these proposals receive, the "
"sooner\n"
"we can roll them out, and the sooner I2P services can start using them!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
msgid ""
"Research\n"
"--------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
msgid ""
"I2P is a packet-switched network, like the internet it runs on top of. "
"This\n"
"gives us significant flexibility in how we route packets, both for "
"performance\n"
"and privacy. The majority of this flexibility is unexplored! We want to\n"
"encourage research into how various clearnet techniques for improving "
"bandwidth\n"
"can be applied to I2P, and how they might affect the privacy of network\n"
"participants."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
msgid ""
"We have many more ideas for things we'd like to get done in these areas. "
"If\n"
"you're interested in hacking on privacy and anonymity software, designing"
"\n"
"protocols (cryptographic or otherwise), or researching future ideas - "
"come and\n"
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
"into\n"
"our community, both inside and outside the I2P network. We'll also be "
"sending\n"
"I2P stickers out to all new contributors taking part! If you want to chat"
" about\n"
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
" can\n"
"also find us in #i2p-dev on OFTC or Freenode."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
msgid ""
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
" attacks, so it would be reasonable to ask whether improved performance "
"equates to reduced privacy. Some latency can help privacy if applied "
"correctly via random delays or batching (neither of which are currently "
"employed by any general-purpose onion-routing network). However, if a "
"tunnel has uniform overall latency, then traffic confirmation attacks "
"should be just as viable with or without that latency; thus there should "
"be little statistical difference when the latency is reduced uniformly."
msgstr ""

View File

@ -9,7 +9,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Japanese (http://www.transifex.com/otf/I2P/language/ja/)\n"
@ -343,26 +343,26 @@ msgstr "ロードマップ"
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr "完全に許可されたアクセス"
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Portuguese (http://www.transifex.com/otf/I2P/language/pt/)"
@ -348,26 +348,26 @@ msgstr "Mapa de Desenvolvimento"
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Portuguese (Brazil) "
@ -5771,6 +5771,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
msgid ""
"Take part in Summer Dev!\n"
"========================"
@ -5806,6 +5807,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
msgid ""
"We'll be posting here as we go, but you can also follow our progress, and"
" share\n"
@ -6804,3 +6806,187 @@ msgstr ""
msgid "Add bash completion scripts to Debian packages"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
#, fuzzy
msgid ""
"================================\n"
"I2P Summer Dev 2017: MOAR Speed!\n"
"================================"
msgstr ""
"===============================================\n"
"O nascimento de SOLUÇÕES PARA PRIVACIDADE\n"
"==============================================="
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
msgid ""
"This year's Summer Dev will be focused on metrics collection and "
"performance improvements for the network."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
msgid ""
"It's that time of year again! We're embarking on our summer development\n"
"programme, where we focus on a particular aspect of I2P to push it "
"forward. For\n"
"the next three months, we'll be encouraging both new contributors and "
"existing\n"
"community members to pick a task and have fun with it!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
msgid ""
"`Last year`_, we focused on helping users and developers leverage I2P, by"
"\n"
"improving API tooling and giving some love to applications that run over "
"I2P.\n"
"This year, we want to improve the user experience by working on an aspect"
" that\n"
"affects everyone: performance."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
msgid "`Last year`"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
msgid ""
"Despite onion-routing networks often being called \"low-latency\" "
"networks, there\n"
"is significant overhead created by routing traffic through additional "
"computers.\n"
"I2P's unidirectional tunnel design means that by default, a round trip "
"between\n"
"two Destinations will involve twelve participants! Improving the "
"performance of\n"
"these participants will help to both reduce the latency of end-to-end\n"
"connections [1]_, and increase the quality of tunnels network-wide."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
msgid ""
"MOAR speed!\n"
"==========="
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
msgid "Our development programme this year will have four components:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
msgid ""
"Measure\n"
"-------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
msgid ""
"We can't tell if we improve performance without a baseline! We'll be "
"creating a\n"
"metrics system for collecting usage and performance data about I2P in a\n"
"privacy-preserving way, as well as porting various benchmarking tools to "
"run\n"
"over I2P (e.g. iperf3_)."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
msgid ""
"Optimise\n"
"--------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
msgid ""
"There's a lot of scope for improving the performance of our existing "
"code, to\n"
"e.g. reduce the overhead of participating in tunnels. We will be looking "
"at\n"
"potential improvements to:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
msgid "Cryptographic primitives"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
msgid ""
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
"(Streaming_)"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
msgid "Peer profiling"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
msgid "Tunnel path selection"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
msgid ""
"Advance\n"
"-------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
msgid ""
"We have several open proposals for improving the scalability of the I2P "
"network\n"
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
"will be\n"
"working on these proposals, and begin implementing the finalised ones in "
"the\n"
"various network routers. The more feedback these proposals receive, the "
"sooner\n"
"we can roll them out, and the sooner I2P services can start using them!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
msgid ""
"Research\n"
"--------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
msgid ""
"I2P is a packet-switched network, like the internet it runs on top of. "
"This\n"
"gives us significant flexibility in how we route packets, both for "
"performance\n"
"and privacy. The majority of this flexibility is unexplored! We want to\n"
"encourage research into how various clearnet techniques for improving "
"bandwidth\n"
"can be applied to I2P, and how they might affect the privacy of network\n"
"participants."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
msgid ""
"We have many more ideas for things we'd like to get done in these areas. "
"If\n"
"you're interested in hacking on privacy and anonymity software, designing"
"\n"
"protocols (cryptographic or otherwise), or researching future ideas - "
"come and\n"
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
"into\n"
"our community, both inside and outside the I2P network. We'll also be "
"sending\n"
"I2P stickers out to all new contributors taking part! If you want to chat"
" about\n"
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
" can\n"
"also find us in #i2p-dev on OFTC or Freenode."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
msgid ""
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
" attacks, so it would be reasonable to ask whether improved performance "
"equates to reduced privacy. Some latency can help privacy if applied "
"correctly via random delays or batching (neither of which are currently "
"employed by any general-purpose onion-routing network). However, if a "
"tunnel has uniform overall latency, then traffic confirmation attacks "
"should be just as viable with or without that latency; thus there should "
"be little statistical difference when the latency is reduced uniformly."
msgstr ""

View File

@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Portuguese (Brazil) "
@ -437,26 +437,26 @@ msgstr "Plano de ação"
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr "Rotas totalmente restritas"
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr "Tempo de retardo de mensagens definido pelo usuário"
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -20,7 +20,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-20 20:24+0000\n"
"Last-Translator: Alexander Georgievskiy <galeksandrp@gmail.com>\n"
"Language-Team: Russian (Russia) "
@ -6690,6 +6690,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
msgid ""
"Take part in Summer Dev!\n"
"========================"
@ -6725,6 +6726,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
msgid ""
"We'll be posting here as we go, but you can also follow our progress, and"
" share\n"
@ -7748,3 +7750,202 @@ msgstr ""
msgid "Add bash completion scripts to Debian packages"
msgstr "Добавлены скрипты автодополнения bash в пакеты Debian"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
#, fuzzy
msgid ""
"================================\n"
"I2P Summer Dev 2017: MOAR Speed!\n"
"================================"
msgstr ""
"============================\n"
"I2PCon: Миссия завершена\n"
"============================"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
msgid ""
"This year's Summer Dev will be focused on metrics collection and "
"performance improvements for the network."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
msgid ""
"It's that time of year again! We're embarking on our summer development\n"
"programme, where we focus on a particular aspect of I2P to push it "
"forward. For\n"
"the next three months, we'll be encouraging both new contributors and "
"existing\n"
"community members to pick a task and have fun with it!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
msgid ""
"`Last year`_, we focused on helping users and developers leverage I2P, by"
"\n"
"improving API tooling and giving some love to applications that run over "
"I2P.\n"
"This year, we want to improve the user experience by working on an aspect"
" that\n"
"affects everyone: performance."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
msgid "`Last year`"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
msgid ""
"Despite onion-routing networks often being called \"low-latency\" "
"networks, there\n"
"is significant overhead created by routing traffic through additional "
"computers.\n"
"I2P's unidirectional tunnel design means that by default, a round trip "
"between\n"
"two Destinations will involve twelve participants! Improving the "
"performance of\n"
"these participants will help to both reduce the latency of end-to-end\n"
"connections [1]_, and increase the quality of tunnels network-wide."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
#, fuzzy
msgid ""
"MOAR speed!\n"
"==========="
msgstr ""
"На что следует обратить внимание в первую очередь\n"
"============"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
msgid "Our development programme this year will have four components:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
#, fuzzy
msgid ""
"Measure\n"
"-------"
msgstr ""
"Новые пользователи\n"
"---------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
msgid ""
"We can't tell if we improve performance without a baseline! We'll be "
"creating a\n"
"metrics system for collecting usage and performance data about I2P in a\n"
"privacy-preserving way, as well as porting various benchmarking tools to "
"run\n"
"over I2P (e.g. iperf3_)."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
#, fuzzy
msgid ""
"Optimise\n"
"--------"
msgstr ""
"Расположение\n"
" --------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
msgid ""
"There's a lot of scope for improving the performance of our existing "
"code, to\n"
"e.g. reduce the overhead of participating in tunnels. We will be looking "
"at\n"
"potential improvements to:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
msgid "Cryptographic primitives"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
msgid ""
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
"(Streaming_)"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
msgid "Peer profiling"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
msgid "Tunnel path selection"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
#, fuzzy
msgid ""
"Advance\n"
"-------"
msgstr ""
"F-Droid\n"
"-------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
msgid ""
"We have several open proposals for improving the scalability of the I2P "
"network\n"
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
"will be\n"
"working on these proposals, and begin implementing the finalised ones in "
"the\n"
"various network routers. The more feedback these proposals receive, the "
"sooner\n"
"we can roll them out, and the sooner I2P services can start using them!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
#, fuzzy
msgid ""
"Research\n"
"--------"
msgstr ""
"Новые пользователи\n"
"---------"
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
msgid ""
"I2P is a packet-switched network, like the internet it runs on top of. "
"This\n"
"gives us significant flexibility in how we route packets, both for "
"performance\n"
"and privacy. The majority of this flexibility is unexplored! We want to\n"
"encourage research into how various clearnet techniques for improving "
"bandwidth\n"
"can be applied to I2P, and how they might affect the privacy of network\n"
"participants."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
msgid ""
"We have many more ideas for things we'd like to get done in these areas. "
"If\n"
"you're interested in hacking on privacy and anonymity software, designing"
"\n"
"protocols (cryptographic or otherwise), or researching future ideas - "
"come and\n"
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
"into\n"
"our community, both inside and outside the I2P network. We'll also be "
"sending\n"
"I2P stickers out to all new contributors taking part! If you want to chat"
" about\n"
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
" can\n"
"also find us in #i2p-dev on OFTC or Freenode."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
msgid ""
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
" attacks, so it would be reasonable to ask whether improved performance "
"equates to reduced privacy. Some latency can help privacy if applied "
"correctly via random delays or batching (neither of which are currently "
"employed by any general-purpose onion-routing network). However, if a "
"tunnel has uniform overall latency, then traffic confirmation attacks "
"should be just as viable with or without that latency; thus there should "
"be little statistical difference when the latency is reduced uniformly."
msgstr ""

View File

@ -15,7 +15,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-20 20:09+0000\n"
"Last-Translator: Alexander Georgievskiy <galeksandrp@gmail.com>\n"
"Language-Team: Russian (Russia) "
@ -444,7 +444,7 @@ msgstr "План разработки"
msgid "April 2017"
msgstr "Апрель 2017"
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
@ -453,19 +453,19 @@ msgstr ""
"Отображение доступности / обработка частично доступны узлов / улучшить <a"
" href=\"%(todo)s#fullRestrictedRoutes\">ограниченные маршруты</a>"
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr "Полностью ограниченные маршруты"
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr "Смешивание и изменение размера туннелей"
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr "Задержка сообщений, определяемая пользователем"
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2014-12-02 23:13+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Swedish (Sweden) "
@ -5710,6 +5710,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
msgid ""
"Take part in Summer Dev!\n"
"========================"
@ -5745,6 +5746,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
msgid ""
"We'll be posting here as we go, but you can also follow our progress, and"
" share\n"
@ -6744,3 +6746,183 @@ msgstr ""
msgid "Add bash completion scripts to Debian packages"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
msgid ""
"================================\n"
"I2P Summer Dev 2017: MOAR Speed!\n"
"================================"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
msgid ""
"This year's Summer Dev will be focused on metrics collection and "
"performance improvements for the network."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
msgid ""
"It's that time of year again! We're embarking on our summer development\n"
"programme, where we focus on a particular aspect of I2P to push it "
"forward. For\n"
"the next three months, we'll be encouraging both new contributors and "
"existing\n"
"community members to pick a task and have fun with it!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
msgid ""
"`Last year`_, we focused on helping users and developers leverage I2P, by"
"\n"
"improving API tooling and giving some love to applications that run over "
"I2P.\n"
"This year, we want to improve the user experience by working on an aspect"
" that\n"
"affects everyone: performance."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
msgid "`Last year`"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
msgid ""
"Despite onion-routing networks often being called \"low-latency\" "
"networks, there\n"
"is significant overhead created by routing traffic through additional "
"computers.\n"
"I2P's unidirectional tunnel design means that by default, a round trip "
"between\n"
"two Destinations will involve twelve participants! Improving the "
"performance of\n"
"these participants will help to both reduce the latency of end-to-end\n"
"connections [1]_, and increase the quality of tunnels network-wide."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
msgid ""
"MOAR speed!\n"
"==========="
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
msgid "Our development programme this year will have four components:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
msgid ""
"Measure\n"
"-------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
msgid ""
"We can't tell if we improve performance without a baseline! We'll be "
"creating a\n"
"metrics system for collecting usage and performance data about I2P in a\n"
"privacy-preserving way, as well as porting various benchmarking tools to "
"run\n"
"over I2P (e.g. iperf3_)."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
msgid ""
"Optimise\n"
"--------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
msgid ""
"There's a lot of scope for improving the performance of our existing "
"code, to\n"
"e.g. reduce the overhead of participating in tunnels. We will be looking "
"at\n"
"potential improvements to:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
msgid "Cryptographic primitives"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
msgid ""
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
"(Streaming_)"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
msgid "Peer profiling"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
msgid "Tunnel path selection"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
msgid ""
"Advance\n"
"-------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
msgid ""
"We have several open proposals for improving the scalability of the I2P "
"network\n"
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
"will be\n"
"working on these proposals, and begin implementing the finalised ones in "
"the\n"
"various network routers. The more feedback these proposals receive, the "
"sooner\n"
"we can roll them out, and the sooner I2P services can start using them!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
msgid ""
"Research\n"
"--------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
msgid ""
"I2P is a packet-switched network, like the internet it runs on top of. "
"This\n"
"gives us significant flexibility in how we route packets, both for "
"performance\n"
"and privacy. The majority of this flexibility is unexplored! We want to\n"
"encourage research into how various clearnet techniques for improving "
"bandwidth\n"
"can be applied to I2P, and how they might affect the privacy of network\n"
"participants."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
msgid ""
"We have many more ideas for things we'd like to get done in these areas. "
"If\n"
"you're interested in hacking on privacy and anonymity software, designing"
"\n"
"protocols (cryptographic or otherwise), or researching future ideas - "
"come and\n"
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
"into\n"
"our community, both inside and outside the I2P network. We'll also be "
"sending\n"
"I2P stickers out to all new contributors taking part! If you want to chat"
" about\n"
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
" can\n"
"also find us in #i2p-dev on OFTC or Freenode."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
msgid ""
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
" attacks, so it would be reasonable to ask whether improved performance "
"equates to reduced privacy. Some latency can help privacy if applied "
"correctly via random delays or batching (neither of which are currently "
"employed by any general-purpose onion-routing network). However, if a "
"tunnel has uniform overall latency, then traffic confirmation attacks "
"should be just as viable with or without that latency; thus there should "
"be little statistical difference when the latency is reduced uniformly."
msgstr ""

View File

@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Swedish (Sweden) "
@ -345,26 +345,26 @@ msgstr ""
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -9,7 +9,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Turkish (Turkey) "
@ -344,26 +344,26 @@ msgstr ""
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -9,7 +9,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Ukrainian (Ukraine) "
@ -345,26 +345,26 @@ msgstr ""
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -12,7 +12,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: 2017-05-07 06:31+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Chinese (China) "
@ -377,26 +377,26 @@ msgstr ""
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -5645,6 +5645,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:124
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:114
msgid ""
"Take part in Summer Dev!\n"
"========================"
@ -5680,6 +5681,7 @@ msgstr ""
#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119
#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.rst:145
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:130
msgid ""
"We'll be posting here as we go, but you can also follow our progress, and"
" share\n"
@ -6678,3 +6680,183 @@ msgstr ""
msgid "Add bash completion scripts to Debian packages"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:1
msgid ""
"================================\n"
"I2P Summer Dev 2017: MOAR Speed!\n"
"================================"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:10
msgid ""
"This year's Summer Dev will be focused on metrics collection and "
"performance improvements for the network."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:12
msgid ""
"It's that time of year again! We're embarking on our summer development\n"
"programme, where we focus on a particular aspect of I2P to push it "
"forward. For\n"
"the next three months, we'll be encouraging both new contributors and "
"existing\n"
"community members to pick a task and have fun with it!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:19
msgid ""
"`Last year`_, we focused on helping users and developers leverage I2P, by"
"\n"
"improving API tooling and giving some love to applications that run over "
"I2P.\n"
"This year, we want to improve the user experience by working on an aspect"
" that\n"
"affects everyone: performance."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:26
msgid "`Last year`"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:28
msgid ""
"Despite onion-routing networks often being called \"low-latency\" "
"networks, there\n"
"is significant overhead created by routing traffic through additional "
"computers.\n"
"I2P's unidirectional tunnel design means that by default, a round trip "
"between\n"
"two Destinations will involve twelve participants! Improving the "
"performance of\n"
"these participants will help to both reduce the latency of end-to-end\n"
"connections [1]_, and increase the quality of tunnels network-wide."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:37
msgid ""
"MOAR speed!\n"
"==========="
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:42
msgid "Our development programme this year will have four components:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:46
msgid ""
"Measure\n"
"-------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:51
msgid ""
"We can't tell if we improve performance without a baseline! We'll be "
"creating a\n"
"metrics system for collecting usage and performance data about I2P in a\n"
"privacy-preserving way, as well as porting various benchmarking tools to "
"run\n"
"over I2P (e.g. iperf3_)."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:60
msgid ""
"Optimise\n"
"--------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:65
msgid ""
"There's a lot of scope for improving the performance of our existing "
"code, to\n"
"e.g. reduce the overhead of participating in tunnels. We will be looking "
"at\n"
"potential improvements to:"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:71
msgid "Cryptographic primitives"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:72
msgid ""
"Network transports, both at the link-layer (NTCP_, SSU_) and end-to-end "
"(Streaming_)"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:73
msgid "Peer profiling"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:74
msgid "Tunnel path selection"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:80
msgid ""
"Advance\n"
"-------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:85
msgid ""
"We have several open proposals for improving the scalability of the I2P "
"network\n"
"(e.g. Prop115_, Prop123_, Prop124_, Prop125_, Prop138_, Prop140_). We "
"will be\n"
"working on these proposals, and begin implementing the finalised ones in "
"the\n"
"various network routers. The more feedback these proposals receive, the "
"sooner\n"
"we can roll them out, and the sooner I2P services can start using them!"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:100
msgid ""
"Research\n"
"--------"
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:105
msgid ""
"I2P is a packet-switched network, like the internet it runs on top of. "
"This\n"
"gives us significant flexibility in how we route packets, both for "
"performance\n"
"and privacy. The majority of this flexibility is unexplored! We want to\n"
"encourage research into how various clearnet techniques for improving "
"bandwidth\n"
"can be applied to I2P, and how they might affect the privacy of network\n"
"participants."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:119
msgid ""
"We have many more ideas for things we'd like to get done in these areas. "
"If\n"
"you're interested in hacking on privacy and anonymity software, designing"
"\n"
"protocols (cryptographic or otherwise), or researching future ideas - "
"come and\n"
"chat with us on IRC or Twitter! We are always happy to welcome newcomers "
"into\n"
"our community, both inside and outside the I2P network. We'll also be "
"sending\n"
"I2P stickers out to all new contributors taking part! If you want to chat"
" about\n"
"a specific idea, contact `@GetI2P`_, `@i2p`_ or `@str4d`_ on Twitter. You"
" can\n"
"also find us in #i2p-dev on OFTC or Freenode."
msgstr ""
#: i2p2www/blog/2017/06/01/Summer-Dev-2017-MOAR-Speed.rst:141
msgid ""
"Low-latency onion-routing networks are vulnerable to traffic confirmation"
" attacks, so it would be reasonable to ask whether improved performance "
"equates to reduced privacy. Some latency can help privacy if applied "
"correctly via random delays or batching (neither of which are currently "
"employed by any general-purpose onion-routing network). However, if a "
"tunnel has uniform overall latency, then traffic confirmation attacks "
"should be just as viable with or without that latency; thus there should "
"be little statistical difference when the latency is reduced uniformly."
msgstr ""

View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2017-05-07 06:29+0000\n"
"POT-Creation-Date: 2017-06-01 12:21+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -341,26 +341,26 @@ msgstr ""
msgid "April 2017"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:300
#: i2p2www/pages/site/get-involved/roadmap.html:296
#, python-format
msgid ""
"Reachability Mapping / handle peers partially reachable / enhanced <a "
"href=\"%(todo)s#fullRestrictedRoutes\">restricted routes</a>"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:303
#: i2p2www/pages/site/get-involved/roadmap.html:299
msgid "Full restricted routes"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:304
#: i2p2www/pages/site/get-involved/roadmap.html:300
msgid "Tunnel mixing and padding"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:305
#: i2p2www/pages/site/get-involved/roadmap.html:301
msgid "User defined message delays"
msgstr ""
#: i2p2www/pages/site/get-involved/roadmap.html:313
#: i2p2www/pages/site/get-involved/roadmap.html:309
#, python-format
msgid ""
"Please see the <a href=\"%(todo)s\">TODO</a> list for more detailed info "