forked from I2P_Developers/i2p.www
Updated translation strings
This commit is contained in:
str4d
@@ -17,7 +17,7 @@ msgid ""
|
||||
msgstr ""
|
||||
"Project-Id-Version: I2P\n"
|
||||
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
|
||||
"POT-Creation-Date: 2017-09-08 12:53+0000\n"
|
||||
"POT-Creation-Date: 2018-02-12 00:06+0000\n"
|
||||
"PO-Revision-Date: 2017-12-05 20:12+0000\n"
|
||||
"Last-Translator: French language coordinator <french.coordinator@rbox.me>"
|
||||
"\n"
|
||||
@@ -98,6 +98,8 @@ msgstr "`page des téléchargements`"
|
||||
#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:32
|
||||
#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:56
|
||||
#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:32
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:29
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:30
|
||||
msgid "RELEASE DETAILS"
|
||||
msgstr "DÉTAILS SUR LA VERSION"
|
||||
|
||||
@@ -151,6 +153,8 @@ msgstr "Changements majeurs"
|
||||
#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:48
|
||||
#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:68
|
||||
#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:41
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:37
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:43
|
||||
msgid "Bug Fixes"
|
||||
msgstr "Correctifs de bogues"
|
||||
|
||||
@@ -194,6 +198,8 @@ msgstr "Correctifs de bogues"
|
||||
#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:62
|
||||
#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:82
|
||||
#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:54
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:44
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:74
|
||||
msgid "Other"
|
||||
msgstr "Autre"
|
||||
|
||||
@@ -238,6 +244,8 @@ msgstr "Autre"
|
||||
#: i2p2www/blog/2017/03/04/0.9.29-Windows-Installer-Fix.rst:25
|
||||
#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:102
|
||||
#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:69
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:58
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:104
|
||||
msgid "SHA256 Checksums:"
|
||||
msgstr "Sommes de contrôle SHA256 :"
|
||||
|
||||
@@ -410,6 +418,7 @@ msgstr ""
|
||||
#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:69
|
||||
#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:94
|
||||
#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:60
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:49
|
||||
msgid "Update GeoIP data (new installs and PPA only)"
|
||||
msgstr "Mise à jour des données GeoIP (nouvelles installations et PPA seulement)"
|
||||
|
||||
@@ -1892,6 +1901,8 @@ msgstr "Nouvelles traductions"
|
||||
#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:68
|
||||
#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:93
|
||||
#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:59
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:48
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:94
|
||||
msgid "Translation updates"
|
||||
msgstr "Mises à jour de traduction"
|
||||
|
||||
@@ -2090,6 +2101,8 @@ msgstr ""
|
||||
#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:26
|
||||
#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:50
|
||||
#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:26
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:23
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:24
|
||||
msgid ""
|
||||
"As usual, we recommend that you update to this release. The best way to\n"
|
||||
"maintain security and help the network is to run the latest release."
|
||||
@@ -3277,6 +3290,8 @@ msgstr ""
|
||||
#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:34
|
||||
#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:58
|
||||
#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:34
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:31
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:32
|
||||
msgid "Changes"
|
||||
msgstr "Changements"
|
||||
|
||||
@@ -5991,6 +6006,8 @@ msgstr ""
|
||||
#: i2p2www/blog/2017/03/04/0.9.29-Windows-Installer-Fix.rst:12
|
||||
#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:12
|
||||
#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:12
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:12
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:12
|
||||
msgid ""
|
||||
"Update details\n"
|
||||
"=============="
|
||||
@@ -6535,6 +6552,8 @@ msgstr ""
|
||||
#: i2p2www/blog/2017/02/27/0.9.29-Release.rst:74
|
||||
#: i2p2www/blog/2017/05/03/0.9.30-Release.rst:99
|
||||
#: i2p2www/blog/2017/08/07/0.9.31-Release.rst:66
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:55
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:101
|
||||
msgid "`Full list of fixed bugs`"
|
||||
msgstr ""
|
||||
|
||||
@@ -8363,3 +8382,635 @@ msgstr ""
|
||||
msgid "Locale-independent Jetty directory listing"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:1
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
"==============\n"
|
||||
"0.9.32 Release\n"
|
||||
"=============="
|
||||
msgstr ""
|
||||
"==============\n"
|
||||
"Version 0.9.31\n"
|
||||
"=============="
|
||||
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:10
|
||||
#, fuzzy
|
||||
msgid "0.9.32 with Console Updates"
|
||||
msgstr "0.9.31 avec des mises à jour de la console"
|
||||
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:17
|
||||
msgid ""
|
||||
"0.9.32 contains a number of fixes in the router console and associated "
|
||||
"webapps (addressbook, i2psnark, and susimail).\n"
|
||||
"We have also changed the way we handle configured hostnames for published"
|
||||
" router infos, to eliminate some network enumeration attacks via DNS.\n"
|
||||
"We have added some checks in the console to resist rebinding attacks."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:33
|
||||
msgid "Disallow hostnames in router addresses (proposal 141)"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:34
|
||||
#, fuzzy
|
||||
msgid "Validate Host header in console"
|
||||
msgstr "Ajouter la possibilité d’arrêter une appliWeb par la console"
|
||||
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:39
|
||||
msgid "Numerous console, i2psnark, susidns, and susimail UI fixes"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:40
|
||||
msgid "Fix i2psnark issues with expanding sections in some browsers"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:41
|
||||
#, fuzzy
|
||||
msgid "Debian packaging fixes"
|
||||
msgstr "Corrections de verrouillage SSU"
|
||||
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:46
|
||||
msgid "New benchmarking framework"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2017/11/07/0.9.32-Release.rst:47
|
||||
#, fuzzy
|
||||
msgid "New Indonesian translation"
|
||||
msgstr "Nouvelle traduction Roumaine"
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:1
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
"==============\n"
|
||||
"0.9.33 Release\n"
|
||||
"=============="
|
||||
msgstr ""
|
||||
"==============\n"
|
||||
"Version 0.9.31\n"
|
||||
"=============="
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:10
|
||||
#, fuzzy
|
||||
msgid "0.9.33 with Bug Fixes"
|
||||
msgstr "0.9.29 contient des correctifs de bogues"
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:17
|
||||
msgid ""
|
||||
"0.9.33 contains a large number of bug fixes, including i2psnark, "
|
||||
"i2ptunnel, streaming, and SusiMail.\n"
|
||||
"For those who cannot access the reseed sites directly, we now support "
|
||||
"several types of proxies for reseeding.\n"
|
||||
"We now set rate limits by default in the hidden services manager.\n"
|
||||
"For those that run high-traffic servers, please review and adjust the "
|
||||
"limits as necessary."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:34
|
||||
msgid "DesktopGui: Enable on OSX"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:35
|
||||
msgid "i2ptunnel: Set default rate limits"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:36
|
||||
msgid "Reseeding: Add support for proxies"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:39
|
||||
msgid "new installs only"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:45
|
||||
msgid "Client: Remove key when stopping or disabling encrypted lease set"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:46
|
||||
msgid "Console: Several keyring configuration fixes"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:47
|
||||
msgid "EepGet: Detect and reject redirect to https"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:48
|
||||
msgid "HTTP Proxy: Fix up characters in URLs not escaped by browsers "
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:49
|
||||
msgid "i2psnark: Fix bad completion status on recheck"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:50
|
||||
msgid "i2psnark: Prohibit comments unless name is set"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:51
|
||||
#, fuzzy
|
||||
msgid "i2psnark: Fix crash stopping update torrent"
|
||||
msgstr "Évaluations et commentaires d’i2psnark"
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:52
|
||||
msgid "i2ptunnel: Don't erase messages on refresh in UI"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:53
|
||||
msgid "i2ptunnel: Propagate reset to and from streaming"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:54
|
||||
msgid "i2ptunnel: Add header read timeouts to client proxies"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:55
|
||||
msgid "i2ptunnel: Prevent changing sig type after creating destination"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:56
|
||||
msgid "Jetty: Fix zero length in request log for static content"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:57
|
||||
msgid "Router: Reduce router info lock contention"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:58
|
||||
msgid "Streaming: Fix loopback hangs"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:59
|
||||
msgid "Streaming: Fix bug causing excessive acks"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:60
|
||||
msgid "Streaming: Fix connection close after reset"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:61
|
||||
msgid "SusiMail: Fix several issues when using multiple browser tabs"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:62
|
||||
msgid "SusuMail: Fix bugs corrupting text attachments and large message bodies"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:63
|
||||
msgid "SusiMail: Reject sending messages that exceed server limits"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:64
|
||||
msgid "SusiMail: Reduce chance of crashes sending large attachments"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:65
|
||||
msgid "SusiMail: Subject line encoding fixes"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:66
|
||||
msgid "SusiMail: Fix Cc header"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:67
|
||||
msgid "SusiMail: Fix encoding for attachment file names"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:68
|
||||
msgid "SusiMail: POP3 socket close after failure"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:69
|
||||
msgid "Unit test fixes"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:70
|
||||
msgid "Utils: Use constant-time method to check passwords"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:76
|
||||
msgid "Build: Add partial Gradle support"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:77
|
||||
msgid "Console: Hide or combine aliased tunnels on tunnels pages"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:78
|
||||
msgid "Console: Note encrypted leasesets on netdb page"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:79
|
||||
msgid "Console: Use bandwidth setting for burst bandwidth"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:80
|
||||
msgid "Console: Refactor multipart form handling to use Servlet 3.0 API"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:81
|
||||
msgid "Console: Move most handlers and helpers to the war"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:82
|
||||
msgid "Debian: Xenial build is now separate, Zesty+ matches Buster"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:83
|
||||
msgid ""
|
||||
"Debian: Remove ecj dependency; replace glassfish with libtaglibs where "
|
||||
"able"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:84
|
||||
msgid "Debian: Fix builds for x32"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:85
|
||||
msgid "i2ptunnel: Refactor edit jsps"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:86
|
||||
msgid "i2ptunnel: Message box improvements"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:87
|
||||
msgid "Session Key Manager: Delete excess tag sets"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:88
|
||||
msgid "SOCKS: Move client code to core"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:89
|
||||
msgid ""
|
||||
"Startup: Increase open files ulimit if able, in i2prouter script (new "
|
||||
"installs only)"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:90
|
||||
msgid "SusiMail: UI tweaks and minor fixes"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:91
|
||||
msgid "SusiMail: Use internal sockets to connect to servers"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:92
|
||||
msgid "SusiMail: Encoder refactoring"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:93
|
||||
msgid "SusiMail: State tracking refactoring"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/01/30/0.9.33-Release.rst:95
|
||||
msgid "Update GeoIP data"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:1
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
"===========================\n"
|
||||
"High-level Roadmap for 2018\n"
|
||||
"==========================="
|
||||
msgstr ""
|
||||
"=========================\n"
|
||||
"Malware sur i2pbrowser.net\n"
|
||||
"========================="
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:10
|
||||
msgid ""
|
||||
"2018 will be the year of new protocols, new collaborations, and a more "
|
||||
"refined focus."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:12
|
||||
msgid ""
|
||||
"One of the many things we discussed at 34C3 was what we should focus on "
|
||||
"for the\n"
|
||||
"coming year. In particular, we wanted a roadmap that was clear about what"
|
||||
" we\n"
|
||||
"want to ensure we get done, vs what would be really nice to have, and be "
|
||||
"able to\n"
|
||||
"help onboard newcomers to either category. Here is what we came up with:"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:19
|
||||
msgid ""
|
||||
"Priority: New crypto(graphy!)\n"
|
||||
"-----------------------------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:24
|
||||
msgid ""
|
||||
"Many of the current primitives and protocols still retain their original "
|
||||
"designs\n"
|
||||
"from circa 2005, and need improvement. We have had a number of open "
|
||||
"proposals\n"
|
||||
"for several years with ideas, but forward progress has been slow. We all "
|
||||
"agreed\n"
|
||||
"that this needs to be our top priority for 2018. The core components are:"
|
||||
"\n"
|
||||
"\n"
|
||||
"- New transport protocols (to replace NTCP and SSU). See Prop111_.\n"
|
||||
"- New onion-encryption protocol for building and using tunnels.\n"
|
||||
"- New NetDB datatypes to enable enhanced Destinations. See Prop123_.\n"
|
||||
"- Upgraded end-to-end protocol (replacing ElGamal)."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:39
|
||||
msgid ""
|
||||
"Work on this priority falls into several areas:\n"
|
||||
"\n"
|
||||
"- Writing proposals.\n"
|
||||
"- Writing working implementations of them that we can test.\n"
|
||||
"- Reviewing proposals."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:47
|
||||
msgid ""
|
||||
"We cannot release new protocol specifications across the entire network "
|
||||
"without\n"
|
||||
"work on all of these areas."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:52
|
||||
msgid ""
|
||||
"Nice-to-have: Code reuse\n"
|
||||
"------------------------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:57
|
||||
msgid ""
|
||||
"One of the benefits of starting the above work now, is that over the last"
|
||||
" few\n"
|
||||
"years there have been independent efforts to create simple protocols and\n"
|
||||
"protocol frameworks that achieve many of the aims we have for our own "
|
||||
"protocols,\n"
|
||||
"and have gained traction with the wider community. By leveraging this "
|
||||
"work, we\n"
|
||||
"get a \"force multiplier\" effect:\n"
|
||||
"\n"
|
||||
"- We benefit from protocol designs, security proofs, and code written by "
|
||||
"others,\n"
|
||||
" reducing the amount of work we need to do for the same level of\n"
|
||||
" feature-completeness and security assurances.\n"
|
||||
"\n"
|
||||
"- Work we do can be leveraged by other communities, increasing their "
|
||||
"interest in\n"
|
||||
" collaborating with us, and thinking about I2P as a whole."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:72
|
||||
msgid ""
|
||||
"My proposals in particular will be leveraging the `Noise Protocol "
|
||||
"Framework`_,\n"
|
||||
"and the `SPHINX packet format`_. I have collaborations lined up with "
|
||||
"several\n"
|
||||
"people outside I2P for these!"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:81
|
||||
msgid ""
|
||||
"Priority: Clearnet collaboration\n"
|
||||
"--------------------------------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:86
|
||||
msgid ""
|
||||
"On that topic, we've been slowly building interest over the last six "
|
||||
"months or\n"
|
||||
"so. Across PETS2017, 34C3, and RWC2018, I've had some very good "
|
||||
"discussions\n"
|
||||
"about ways in which we can improve collaboration with the wider "
|
||||
"community. This\n"
|
||||
"is really important to ensure we can garner as much review as possible "
|
||||
"for new\n"
|
||||
"protocols. The biggest blocker I've seen is the fact that the majority of"
|
||||
" I2P\n"
|
||||
"development collaboration currently happens inside I2P itself, which\n"
|
||||
"significantly increases the effort required to contribute."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:96
|
||||
msgid ""
|
||||
"The two priorities in this area are:\n"
|
||||
"\n"
|
||||
"- Set up a project-run development forum that is accessible both inside "
|
||||
"and\n"
|
||||
" outside I2P.\n"
|
||||
"\n"
|
||||
"- Set up mailing lists for review and discussion of proposals (possibly\n"
|
||||
" connected to the above forum)."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:106
|
||||
msgid ""
|
||||
"Other goals which are classed as nice-to-have:\n"
|
||||
"\n"
|
||||
"- Set up a usable git-to-mtn pathway, to enable us to effectively solicit"
|
||||
"\n"
|
||||
" clearnet contributions on GitHub while keeping the canonical dev "
|
||||
"environment\n"
|
||||
" on Monotone.\n"
|
||||
"\n"
|
||||
"- Write a \"position paper\" that accurately explains I2P to academic "
|
||||
"audiences,\n"
|
||||
" and puts it in context with existing literature."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:117
|
||||
msgid ""
|
||||
"I expect that collaborations with people outside I2P will be done "
|
||||
"entirely on\n"
|
||||
"GitHub, for minimal friction."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:122
|
||||
msgid ""
|
||||
"Priority: Preparation for long-lived releases\n"
|
||||
"---------------------------------------------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:127
|
||||
msgid ""
|
||||
"I2P is now in Debian Sid (their unstable repo) which will stablilise in "
|
||||
"around a\n"
|
||||
"year and a half, and has also been pulled into the Ubuntu repository for\n"
|
||||
"inclusion in the next LTS release in April. We are going to start having "
|
||||
"I2P\n"
|
||||
"versions that end up hanging around for years, and we need to ensure we "
|
||||
"can\n"
|
||||
"handle their presence in the network."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:135
|
||||
msgid ""
|
||||
"The primary goal here is to roll out as many of the new protocols as we "
|
||||
"feasibly\n"
|
||||
"can in the next year, to hit the next Debian stable release. For those "
|
||||
"that\n"
|
||||
"require multi-year rollouts, we should incorporate the forward-"
|
||||
"compatability\n"
|
||||
"changes as early as we can."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:142
|
||||
msgid ""
|
||||
"Priority: Pluginization of current apps\n"
|
||||
"---------------------------------------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:147
|
||||
msgid ""
|
||||
"The Debian model encourages having separate packages for separate "
|
||||
"components. We\n"
|
||||
"agreed that decoupling the currently-bundled Java applications from the "
|
||||
"core\n"
|
||||
"Java router would be beneficial for several reasons:\n"
|
||||
"\n"
|
||||
"- It codifies the boundary between the applications and the router.\n"
|
||||
"\n"
|
||||
"- It should make it easier to get these apps running with non-Java "
|
||||
"routers.\n"
|
||||
"\n"
|
||||
"- It would enable third parties to create \"I2P bundles\" containing just"
|
||||
" the\n"
|
||||
" applications they want."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:160
|
||||
msgid ""
|
||||
"In combination with the earlier priorities, this moves the main I2P "
|
||||
"project more\n"
|
||||
"in the direction of e.g. the Linux kernel. We will spend more time "
|
||||
"focusing on\n"
|
||||
"the network itself, leaving third-party developers to focus on "
|
||||
"applications that\n"
|
||||
"use the network (something that is significantly easier to do after our "
|
||||
"work in\n"
|
||||
"the last few years on APIs and libraries)."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:168
|
||||
msgid ""
|
||||
"Nice-to-have: App improvements\n"
|
||||
"------------------------------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:173
|
||||
msgid ""
|
||||
"There are a bunch of app-level improvements that we want to work on, but "
|
||||
"do not\n"
|
||||
"currently have the developer time to do so, given our other priorities. "
|
||||
"This is\n"
|
||||
"an area we would love to see new contributors for! Once the above "
|
||||
"decoupling is\n"
|
||||
"complete, it will be significantly easier for someone to work on a "
|
||||
"specific\n"
|
||||
"application independently of the main Java router."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:181
|
||||
msgid ""
|
||||
"One such application we would love to have help with is I2P Android. We "
|
||||
"will be\n"
|
||||
"keeping it up-to-date with the core I2P releases, and fixing bugs as we "
|
||||
"can, but\n"
|
||||
"there is much that could be done to improve the underlying code as well "
|
||||
"as the\n"
|
||||
"usability."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:188
|
||||
msgid ""
|
||||
"Priority: Susimail and I2P-Bote stabilisation\n"
|
||||
"---------------------------------------------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:193
|
||||
msgid ""
|
||||
"Having said that, we do want to work specifically on Susimail and I2P-"
|
||||
"Bote fixes\n"
|
||||
"in the near term (some of which have landed in 0.9.33). They have had "
|
||||
"less work\n"
|
||||
"over the last few years than other I2P apps, and so we want to spend some"
|
||||
" time\n"
|
||||
"bringing their codebases up to par, and making them easier for new "
|
||||
"contributors\n"
|
||||
"to jump into!"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:201
|
||||
msgid ""
|
||||
"Nice-to-have: Ticket triage\n"
|
||||
"---------------------------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:206
|
||||
msgid ""
|
||||
"We have a large backlog of tickets in a number of I2P subsystems and "
|
||||
"apps. As\n"
|
||||
"part of the above stabilisation effort, we would love to clean up some of"
|
||||
" our\n"
|
||||
"older long-standing issues. More importantly, we want to ensure that our "
|
||||
"tickets\n"
|
||||
"are correctly organised, so that new contributors can find good tickets "
|
||||
"to work\n"
|
||||
"on."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:214
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
"Priority: User support\n"
|
||||
"----------------------"
|
||||
msgstr ""
|
||||
"Jour 2, 16 août - 13h\n"
|
||||
"----------------------"
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:219
|
||||
msgid ""
|
||||
"One aspect of the above we will be focusing on is keeping in touch with "
|
||||
"users\n"
|
||||
"who take the time to report issues. Thank you! The smaller we can make "
|
||||
"the\n"
|
||||
"feedback loop, the quicker we can resolve problems that new users face, "
|
||||
"and the\n"
|
||||
"more likely it is that they keep participating in the community."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:226
|
||||
msgid ""
|
||||
"We'd love your help!\n"
|
||||
"--------------------"
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:231
|
||||
msgid ""
|
||||
"That all looks very ambitious, and it is! But many of the items above "
|
||||
"overlap,\n"
|
||||
"and with careful planning we can make a serious dent in them."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/11/high-level-roadmap.rst:236
|
||||
msgid ""
|
||||
"If you are interested in helping with any of the goals above, come chat "
|
||||
"to us!\n"
|
||||
"You can find us on OFTC and Freenode (#i2p-dev), and Twitter (@GetI2P)."
|
||||
msgstr ""
|
||||
|
||||
#: i2p2www/blog/2018/02/12/bsidesnyc.rst:1
|
||||
#, fuzzy
|
||||
msgid ""
|
||||
"================\n"
|
||||
"I2P at BSidesNYC\n"
|
||||
"================"
|
||||
msgstr ""
|
||||
"===============================\n"
|
||||
"Compte rendu de voyage au 31C3\n"
|
||||
"==============================="
|
||||
|
||||
#: i2p2www/blog/2018/02/12/bsidesnyc.rst:10
|
||||
msgid "Trip report about the I2P meetup at BSidesNYC."
|
||||
msgstr ""
|
||||
|
||||
|
||||
Reference in New Issue
Block a user