diff --git a/i2p2www/translations/gl/LC_MESSAGES/get-involved.po b/i2p2www/translations/gl/LC_MESSAGES/get-involved.po new file mode 100644 index 00000000..d407c5bd --- /dev/null +++ b/i2p2www/translations/gl/LC_MESSAGES/get-involved.po @@ -0,0 +1,4101 @@ +# Galician translations for I2P. +# Copyright (C) 2016 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# Uberius Crypto , 2016 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2016-07-02 04:51+0000\n" +"PO-Revision-Date: 2016-10-20 01:23+0000\n" +"Last-Translator: Uberius Crypto \n" +"Language-Team: Galician (http://www.transifex.com/otf/I2P/language/gl/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 1.3\n" + +#: i2p2www/pages/site/get-involved/donate.html:2 +#: i2p2www/pages/site/get-involved/index.html:82 +msgid "Donate" +msgstr "Doar" + +#: i2p2www/pages/site/get-involved/donate.html:4 +msgid "" +"Thank you for your interest in contributing to I2P!\n" +"The details of how you\n" +"can make your contribution are provided below." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:10 +msgid "Tax Status" +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:11 +msgid "" +"I2P is not incorporated.\n" +"Your contributions are probably not tax-deductible.\n" +"If you would like to discuss a large contribution, please contact eche|on." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:17 +msgid "Stickers" +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:18 +msgid "" +"While supplies last, we offer I2P stickers to those who donate enough\n" +"to cover PayPal fees and postage from the U.S.\n" +"You must include \"stickers please\" and your address in the Paypal " +"comments.\n" +"For other payment methods, follow up with an email to eche|on\n" +"with the subject \"stickers please\", your payment information, and your " +"address." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:25 +msgid "Please allow 30-60 days for delivery." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:30 +#, python-format +msgid "" +"As of %(date)s, eche|on has been running a\n" +"%(cointype)s account for the I2P project.\n" +"ATTENTION! The address changed on 02-20-2014. ATTENTION!\n" +"If you'd like to donate using %(cointype)s, just transfer your\n" +"desired amount of coins to the account %(account)s\n" +"and leave eche|on a note if you'd like your donation to be\n" +"mentioned on the I2P webpage." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:42 +#: i2p2www/pages/site/get-involved/donate.html:59 +#: i2p2www/pages/site/get-involved/donate.html:75 +msgid "For easy usage, use the QR code below!" +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:47 +#, python-format +msgid "" +"As of %(date)s, eche|on has been running a\n" +"%(cointype)s account for the I2P project.\n" +"ATTENTION! The address changed 02-20-2014. ATTENTION!\n" +"If you'd like to donate using %(cointype)s, just transfer your\n" +"desired amount of coins to the account %(account)s\n" +"and leave eche|on a note if you'd like your donation to be\n" +"mentioned on the I2P webpage." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:64 +#, python-format +msgid "" +"As of %(date)s, Meeh has been running a\n" +"%(cointype)s account for the I2P project.\n" +"If you'd like to donate using %(cointype)s, just transfer your\n" +"desired amount of coins to the account %(account)s\n" +"and leave Meeh a note if you'd like your donation to be\n" +"mentioned on the I2P webpage." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:80 +#, python-format +msgid "" +"As of %(date)s, echelon has been running a\n" +" %(cointype)s account for the I2P project.\n" +" If you'd like to donate using %(cointype)s, just transfer your\n" +" desired amount of coins to the account %(account)s\n" +" and leave echelon a note if you'd like your donation to be\n" +" mentioned on the I2P webpage." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:94 +#, python-format +msgid "" +"We accept most altcoins, just ask Meeh. Other altcoins can be converted " +"and exchanged for a crypto currency we currently support. Please send a " +"mail to \"%(account)s\" for a such donation." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:101 +#, python-format +msgid "You can donate direct via PayPal to the account \"%(account)s\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:107 +msgid "One time donation:" +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:121 +msgid "Donate 10 €/month for 12 months:" +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:129 +#: i2p2www/pages/site/get-involved/donate.html:141 +#: i2p2www/pages/site/get-involved/donate.html:153 +#: i2p2www/pages/site/get-involved/donate.html:165 +msgid "I2P donation " +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:135 +msgid "Donate 20 €/month for 12 months:" +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:147 +msgid "Donate 30 €/month for 12 months:" +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:159 +msgid "Donate 50 €/month for 12 months:" +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:174 +msgid "Flattr this" +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:179 +msgid "" +"If you want to keep more or less anonymous, the option to send money via " +"mail is also available. But it is less secure\n" +"as the envelope can be lost on the way to us." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:183 +#, python-format +msgid "" +"If you'd like to donate via snail mail, send an email to %(email)s\n" +" and you'll receive an email with instructions detailing how to proceed." +msgstr "" + +#: i2p2www/pages/site/get-involved/donate.html:188 +#, python-format +msgid "" +"In the meantime, feel free to take a look at the generous donations that " +"have been\n" +"given in support of the I2P Project at the hall of fame." +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:2 +msgid "Get Involved!" +msgstr "Involúcrate!" + +#: i2p2www/pages/site/get-involved/index.html:4 +msgid "We need your help!" +msgstr "Precisámo-la túa axuda!" + +#: i2p2www/pages/site/get-involved/index.html:5 +msgid "" +"To get involved, please feel free to join us on the #i2p-dev IRC channel " +"(on\n" +"irc.freenode.net, irc.oftc.net, or within I2P on irc.echelon.i2p, " +"irc.dg.i2p or irc.postman.i2p)." +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:9 +#, python-format +msgid "" +"If you're interested in joining our team, please" +" get in\n" +"touch as we're always looking for eager contributors!" +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:13 +msgid "" +"We need help in many areas, and you don't need to know Java to " +"contribute!\n" +"Here's a list to help get you started!" +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:18 +msgid "Spread the Word!" +msgstr "Difunde a palabra!" + +#: i2p2www/pages/site/get-involved/index.html:19 +msgid "" +"Tell people about I2P on forums, blogs, and comments to articles.\n" +"Fix up the Wikipedia article about I2P in your language.\n" +"Tell your friends." +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:24 +msgid "Testing" +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:25 +#, python-format +msgid "" +"Run the latest builds from monotone\n" +"and report results on #i2p or as bugs on Trac." +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:30 +msgid "Documentation" +msgstr "Documentación" + +#: i2p2www/pages/site/get-involved/index.html:31 +msgid "" +"Help fix the parts of the website that are outdated or incomplete.\n" +"Translate pages into other languages." +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:35 +msgid "Pictures" +msgstr "Imaxes" + +#: i2p2www/pages/site/get-involved/index.html:36 +msgid "Make some more pictures, fix the old ones on the website" +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:39 +msgid "Content" +msgstr "Contido" + +#: i2p2www/pages/site/get-involved/index.html:40 +msgid "Make an eepsite! Add some content! Contribute to the community!" +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:43 +msgid "Services" +msgstr "Servizos" + +#: i2p2www/pages/site/get-involved/index.html:44 +msgid "" +"Run a service on an eepsite. It could be a proxy, a forum, a tracker,\n" +"a naming service, a search engine, an eepsite monitor... many of these\n" +"aren't that hard." +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:49 +msgid "Applications" +msgstr "Aplicacións" + +#: i2p2www/pages/site/get-involved/index.html:50 +#, python-format +msgid "" +"Write or port applications for I2P! There's some guidelines and\n" +"a list of ideas on the applications page." +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:54 +msgid "Coding" +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:55 +#, python-format +msgid "" +"There's plenty to do if you know Java or are ready to learn.\n" +"Check for open tickets on Trac\n" +"or the TODO list on %(zzz)s for\n" +"some ideas on where to start.\n" +"See the new developer's guide for details." +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:64 +msgid "Translation" +msgstr "Tradución" + +#: i2p2www/pages/site/get-involved/index.html:65 +#, python-format +msgid "" +"Help translate the website and the software into your language.\n" +"See the new translator's guide for details." +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:69 +msgid "Analysis" +msgstr "Análise" + +#: i2p2www/pages/site/get-involved/index.html:70 +#, python-format +msgid "" +"Study or test the code to look for vulnerabilities.\n" +"Both anonymity vulnerabilities from the various\n" +"threat models,\n" +"and DOS and other weaknesses due to securities holes,\n" +"need researching." +msgstr "" + +#: i2p2www/pages/site/get-involved/index.html:77 +msgid "Reseeding" +msgstr "Resementando" + +#: i2p2www/pages/site/get-involved/index.html:78 +#, python-format +msgid "" +"Set up a reseed server for new routers to bootstrap from.\n" +"Detailed instructions are on our reseed server " +"page." +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:2 +msgid "Roadmap" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:3 +msgid "May 2016" +msgstr "Maio de 2016" + +#: i2p2www/pages/site/get-involved/roadmap.html:193 +#: i2p2www/pages/site/get-involved/roadmap.html:206 +#, python-format +msgid "" +"Reachability Mapping / handle peers partially reachable / enhanced restricted routes" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:196 +#: i2p2www/pages/site/get-involved/roadmap.html:209 +msgid "Full restricted routes" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:197 +#: i2p2www/pages/site/get-involved/roadmap.html:210 +msgid "Tunnel mixing and padding" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:198 +#: i2p2www/pages/site/get-involved/roadmap.html:211 +msgid "User defined message delays" +msgstr "" + +#: i2p2www/pages/site/get-involved/roadmap.html:214 +#, python-format +msgid "" +"Please see the TODO list for more detailed info " +"about some of these tasks." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:2 +msgid "I2P Project Targets" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:5 +#: i2p2www/pages/site/get-involved/todo.html:47 +msgid "Core functionality" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:7 +#: i2p2www/pages/site/get-involved/todo.html:50 +msgid "NetworkDB and profile tuning and ejection policy for large nets" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:11 +#: i2p2www/pages/site/get-involved/todo.html:74 +msgid "Security / anonymity" +msgstr "Seguridade / Anonimato" + +#: i2p2www/pages/site/get-involved/todo.html:13 +#: i2p2www/pages/site/get-involved/todo.html:77 +msgid "Full blown n-hop restricted routes with optional trusted links" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:16 +#: i2p2www/pages/site/get-involved/todo.html:96 +msgid "Hashcash for routerIdentity, destination, and tunnel request" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:19 +#: i2p2www/pages/site/get-involved/todo.html:125 +msgid "Advanced tunnel operation (batching/mixing/throttling/padding)" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:22 +#: i2p2www/pages/site/get-involved/todo.html:162 +msgid "Stop & go mix w/ garlics & tunnels" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:26 +#: i2p2www/pages/site/get-involved/todo.html:176 +msgid "Performance" +msgstr "Rendemento" + +#: i2p2www/pages/site/get-involved/todo.html:31 +#, python-format +msgid "" +"Note: This page is not up-to-date.\n" +"See the roadmap for current plans." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:36 +#, python-format +msgid "" +"Below is a more detailed (yet still incomplete) discussion of the major " +"areas\n" +"of future development on the core I2P network, spanning the plausibly " +"planned\n" +"releases. This does not include stego transports, porting to wireless " +"devices,\n" +"or tools to secure the local machine, nor does it include client " +"applications\n" +"that will be essential in I2P's success. There are probably other things " +"that\n" +"will come up, especially as I2P gets more peer review, but these are the " +"main\n" +"'big things'. See also the roadmap. Want to " +"help?\n" +"Get involved!" +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:53 +msgid "" +"Within the current network database and profile management " +"implementation, \n" +"we have taken the liberty of some practical shortcuts. For instance, we \n" +"don't have the code to drop peer references from the K-buckets, as we \n" +"don't have enough peers to even plausibly fill any of them, so instead, \n" +"we just keep the peers in whatever bucket is appropriate. Another example" +" \n" +"deals with the peer profiles - the memory required to maintain each " +"peer's \n" +"profile is small enough that we can keep thousands of full blown profiles" +" \n" +"in memory without problems. While we have the capacity to use trimmed \n" +"down profiles (which we can maintain 100s of thousands in memory), we \n" +"don't have any code to deal with moving a profile from a \"minimal " +"profile\" \n" +"to a \"full profile\", a \"full profile\" to a \"minimal profile\", or to" +" simply \n" +"eject a profile altogether. It just wouldn't be practical to write that \n" +"code yet, since we aren't going to need it for a while." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:68 +msgid "" +"That said, as the network grows we are going to want to keep these " +"considerations \n" +"in mind. We will have some work to do, but we can put it off for later." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:80 +msgid "" +"The restricted route functionality described before was simply a " +"functional \n" +"issue - how to let peers who would not otherwise be able to communicate \n" +"do so. However, the concept of allowing restricted routes includes " +"additional \n" +"capabilities. For instance, if a router absolutely cannot risk " +"communicating \n" +"directly with any untrusted peers, they can set up trusted links through" +" \n" +"those peers, using them to both send and receive all of its messages. \n" +"Those hidden peers who want to be completely isolated would also refuse \n" +"to connect to peers who attempt to get them to (as demonstrated by the \n" +"garlic routing technique outlined before) - they can simply take the " +"garlic \n" +"clove that has a request for delivery to a particular peer and tunnel \n" +"route that message out one of the hidden peer's trusted links with " +"instructions \n" +"to forward it as requested." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:99 +#, python-format +msgid "" +"Within the network, we will want some way to deter people from consuming" +" \n" +"too many resources or from creating so many peers to mount a Sybil \n" +"attack. Traditional techniques such as having a peer see who is " +"requesting \n" +"a resource or running a peer aren't appropriate for use within I2P, as \n" +"doing so would compromise the anonymity of the system. Instead, we want \n" +"to make certain requests \"expensive\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:107 +msgid "" +"Hashcash is one technique that \n" +"we can use to anonymously increase the \"cost\" of doing certain " +"activities, \n" +"such as creating a new router identity (done only once on installation)," +" \n" +"creating a new destination (done only once when creating a service), or \n" +"requesting that a peer participate in a tunnel (done often, perhaps 2-300" +" \n" +"times per hour). We don't know the \"correct\" cost of each type of " +"certificate \n" +"yet, but with some research and experimentation, we could set a base " +"level \n" +"that is sufficiently expensive while not an excessive burden for people \n" +"with few resources." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:118 +msgid "" +"There are a few other algorithms that we can explore for making those \n" +"requests for resources \"nonfree\", and further research on that front is" +" \n" +"appropriate." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:128 +#, python-format +msgid "" +"To powerful passive external observers as well as large colluding " +"internal \n" +"observers, standard tunnel routing is vulnerable to traffic analysis " +"attacks \n" +"- simply watching the size and frequency of messages being passed between" +" \n" +"routers. To defend against these, we will want to essentially turn some \n" +"of the tunnels into its own mix cascade - delaying messages received at \n" +"the gateway and passing them in batches, reordering them as necessary, \n" +"and injecting dummy messages (indistinguishable from other \"real\" " +"tunnel \n" +"messages by peers in the path). There has been a significant amount of \n" +"research \n" +"on these algorithms that we can lean on prior to implementing the various" +" \n" +"tunnel mixing strategies." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:141 +msgid "" +"In addition to the anonymity aspects of more varied tunnel operation, \n" +"there is a functional dimension as well. Each peer only has a certain \n" +"amount of data they can route for the network, and to keep any particular" +" \n" +"tunnel from consuming an unreasonable portion of that bandwidth, they \n" +"will want to include some throttles on the tunnel. For instance, a tunnel" +" \n" +"may be configured to throttle itself after passing 600 messages (1 per \n" +"second), 2.4MB (4KBps), or exceeding some moving average (8KBps for the \n" +"last minute). Excess messages may be delayed or summarily dropped. With \n" +"this sort of throttling, peers can provide ATM-like QoS support for their" +" \n" +"tunnels, refusing to agree to allocate more bandwidth than the peer has \n" +"available." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:154 +msgid "" +"In addition, we may want to implement code to dynamically reroute tunnels" +" \n" +"to avoid failed peers or to inject additional hops into the path. This \n" +"can be done by garlic routing a message to any particular peer in a " +"tunnel \n" +"with instructions to redefine the next-hop in the tunnel." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:165 +msgid "" +"Beyond the per-tunnel batching and mixing strategy, there are further \n" +"capabilities for protecting against powerful attackers, such as allowing" +" \n" +"each step in a garlic routed path to define a delay or window in which \n" +"it should be forwarded on. This would enable protections against the long" +" \n" +"term intersection attack, as a peer could send a message that looks " +"perfectly \n" +"standard to most peers that pass it along, except at any peers where the" +" \n" +"clove exposed includes delay instructions." +msgstr "" + +#: i2p2www/pages/site/get-involved/todo.html:177 +#, python-format +msgid "" +"Performance related improvements are listed on the\n" +"Performance page." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:2 +msgid "Bounty Arabic translation of webpage and router console" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:3 +#: i2p2www/pages/site/get-involved/bounties/index.html:118 +msgid "Arabic translation" +msgstr "Tradución ó árabe" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:6 +msgid "" +"To improve I2P usage and attract more people\n" +"into I2P echelon set out this bounty for translation\n" +"of the I2P web page and I2P router console into Arabic." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:12 +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:12 +msgid "This bounty is set into 2 subparts:" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:14 +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:14 +msgid "Part 1 is translation of the webpage." +msgstr "A parte 1 é a tradución da páxina web." + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:17 +msgid "" +"For collecting the bounty of 20 BTC you need to translate the following " +"pages:" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:25 +msgid "This job was done by hamada and the bounty of 20 BTC was paid to hamada." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:27 +msgid "" +"Part 2 is the translation of the router console. The router console was\n" +"partly translated and the bounty of 80 BTC was paid to hamada." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/arabic-trans.html:34 +msgid "Judge is echelon." +msgstr "O xuiz é echelon." + +#: i2p2www/pages/site/get-involved/bounties/btc-client.html:2 +msgid "Bounty creating a I2P native Bitcoin client" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/btc-client.html:3 +msgid "BTC I2P native client" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/btc-client.html:6 +msgid "" +"For a future of I2P and attract more people\n" +"into I2P this bounty is to create a I2P native Bitcoin client. \n" +"It should integrate with other client via the I2P network and via " +"gateways to\n" +"the existant bitcoin network." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/btc-client.html:15 +msgid "" +"Judge is psychonaut who donated the first 30 € to this bounty.\n" +"Bounty was almost fullfilled with btci2p, only a small\n" +"part of creating a plugin is leftover. User giv has been paid for the " +"work." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:2 +msgid "Bounty datastorage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:3 +msgid "datastore" +msgstr "almacenaxe de datos" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:6 +msgid "" +"To improve I2P's usage and to be independent of routers \n" +"online status we want a datastorage as a extension to I2P.\n" +"Like in Freenet the datastorage should be distributed and every\n" +"participating node should be able to configure his options.\n" +"The files should be saved in chunks and at least 2-3 times to\n" +"obtain redundancy. Usage of storage space should be auto balanced.\n" +"As it is a extra application, it should work flawless within I2P and\n" +"cooperate nice with the I2P router. Maybe a integration within the\n" +"webpage/router could be done." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:17 +msgid "" +"This bounty cooperates with the 2 other bounties \"frost for I2P\" and \n" +"\"eepsites in datastorage\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:21 +msgid "" +"The frost for I2P datastorage bounty is paid for a frost like program \n" +"with which files/messages are stored into database and got from database." +"\n" +"It needs to work with a GUI." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:26 +msgid "" +"The eepsite served out of I2P datastorage extends a I2P router to send\n" +"out eepsites out of the I2P datastorage. All files for eepsites need to " +"be\n" +"saved inside of datastorage and are taken from it.\n" +"Extension:\n" +"For better integration all datastorage participants could serve that " +"eepsite." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/datastore.html:36 +msgid "" +"For bounties to be declared done and paid, we need the program AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" +"free to distribute)." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:2 +msgid "Bounty I2P package in Debian and Ubuntu mirrors" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:3 +msgid "I2P Ubuntu/Debian package" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/deb-pack.html:6 +msgid "" +"For the future of I2P and in order to attract more people\n" +"to I2P, this bounty was set for including an I2P package into the Ubuntu " +"and Debian \n" +"archive mirrors.\n" +"To claim this bounty, the I2P router package needs to be available from\n" +"Ubuntu and Debian archive mirrors and Debian bug \n" +"448638 \n" +"needs to be closed successfully." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/i2phex.html:2 +msgid "Bounty I2PHex code implementation" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/i2phex.html:3 +msgid "i2phex code implementation" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/i2phex.html:6 +msgid "" +"To improve I2P usage and attract more people\n" +"into I2PHex P2P ArneBab setout the bounty for implementing actual\n" +"Phex code onto I2PHex." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:2 +msgid "Bounties for I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:5 +msgid "" +"While we always gratefully accept any contributions of code, \n" +"documentation, and the like, there are other ways to help I2P move \n" +"forward. As with any open source project, our goals would be achieved " +"more \n" +"rapidly if we were able to support all of our contributors to work on \n" +"I2P full time. However, as with any open source project, that's not a \n" +"possibility. Instead, we are making use of a bounty system, whereby \n" +"anyone can get support for working on something that people want \n" +"implemented, and people who want to contribute to I2P can be assured that" +" \n" +"their support goes to what they care about." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:17 +msgid "" +"We are also keeping open the ability for people who want to support I2P \n" +"but don't have strong feelings about the bounties available. Those " +"people\n" +"can simply put their trust in the I2P team to do what we feel is best by\n" +"donating to a catch-all general fund that will be used as deemed \n" +"necessary - allocated to various bounties, covering incidentals (hosting," +" \n" +"etc), and the like." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:26 +msgid "Current bounties" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:29 +#: i2p2www/pages/site/get-involved/bounties/index.html:84 +#: i2p2www/pages/site/get-involved/bounties/index.html:104 +msgid "Name" +msgstr "Nome" + +#: i2p2www/pages/site/get-involved/bounties/index.html:29 +#: i2p2www/pages/site/get-involved/bounties/index.html:84 +#: i2p2www/pages/site/get-involved/bounties/index.html:104 +msgid "Status" +msgstr "Estado" + +#: i2p2www/pages/site/get-involved/bounties/index.html:29 +#: i2p2www/pages/site/get-involved/bounties/index.html:84 +msgid "Judge" +msgstr "Xuiz" + +#: i2p2www/pages/site/get-involved/bounties/index.html:29 +#: i2p2www/pages/site/get-involved/bounties/index.html:84 +msgid "Dev" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:29 +#: i2p2www/pages/site/get-involved/bounties/index.html:84 +msgid "Bounty" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:31 +msgid "Frost for I2P datastorage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:32 +#: i2p2www/pages/site/get-involved/bounties/index.html:39 +#: i2p2www/pages/site/get-involved/bounties/index.html:46 +#: i2p2www/pages/site/get-involved/bounties/index.html:53 +#: i2p2www/pages/site/get-involved/bounties/index.html:74 +#: i2p2www/pages/site/get-involved/bounties/index.html:94 +msgid "Proposal in development" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:34 +#: i2p2www/pages/site/get-involved/bounties/index.html:41 +#: i2p2www/pages/site/get-involved/bounties/index.html:48 +#: i2p2www/pages/site/get-involved/bounties/index.html:55 +#: i2p2www/pages/site/get-involved/bounties/index.html:76 +#: i2p2www/pages/site/get-involved/bounties/index.html:89 +msgid "vacant" +msgstr "vacante" + +#: i2p2www/pages/site/get-involved/bounties/index.html:38 +msgid "Eepsites served out of I2P datastorage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:45 +msgid "Backporting Phex code onto I2PHex" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:52 +msgid "I2P package in Debian and Ubuntu mirrors" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:59 +msgid "Bitcoin client for I2P" +msgstr "Cliente de Bitcoin para I2P" + +#: i2p2www/pages/site/get-involved/bounties/index.html:60 +msgid "Done, phase of verification" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:66 +msgid "Unit tests and Multi-router Simulation" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:67 +msgid "Partly done, partly in work, partly still open" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:81 +msgid "Hold bounties, set on hold due to jrandom AWOL and missing funding" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:86 +msgid "Bundling bounties" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:87 +msgid "Proposed" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:101 +msgid "Claimed bounties" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:104 +msgid "Dev team" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:106 +msgid "Make I2P IPv6 native" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:113 +msgid "Setting up a SILC server" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:123 +msgid "Datastore over I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:128 +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:3 +msgid "Russian translation" +msgstr "Tradución ó ruso" + +#: i2p2www/pages/site/get-involved/bounties/index.html:133 +msgid "Swarming file transfer" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:138 +msgid "Streaming library window size" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:143 +msgid "IRC connect time monitor" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/index.html:148 +msgid "Unit tests (part 1)" +msgstr "Tests de unidades (parte 1ª)" + +#: i2p2www/pages/site/get-involved/bounties/index.html:160 +msgid "" +"Dev lists anyone who may already be working on the bounty - collaboration" +" is\n" +"preferred, so if you're interested in working on it, please contact one " +"of the\n" +"people listed!" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/ipv6.html:2 +msgid "Bounty I2P IPv6 native" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/ipv6.html:3 +msgid "native IPv6 I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/ipv6.html:6 +msgid "" +"For a future of I2P and attract more people\n" +"into I2P I withdrawal the vuze bounty and offer a IPv6 bounty.\n" +"To claim this bounty, the I2P router needs to run full on native\n" +"IPv6 connections like it does on IPv4." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/ipv6.html:23 +#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:20 +msgid "" +"For bounties to be declared done and paid, we need the plugin AND the " +"source.\n" +"Source and code need to be licensed under a free license (free to change " +"and \n" +"free to distribute)." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/netdb.html:2 +msgid "NetDB Backend" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/netdb.html:3 +msgid "netDB backend" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/netdb.html:7 +msgid "" +"The current NetDB implementation (namely the FloodFill system)\n" +"needs to be extended with another backend to improve reliability,\n" +"reduce attack surface and solve the scalability issue for the \n" +"coming years." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/netdb.html:14 +msgid "" +"A solution likely based on a DHT will be investigated and \n" +"finally implemented." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:2 +msgid "Bounty russian translation of webpage and router console" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:6 +msgid "" +"To improve I2P usage and attract more people\n" +"into I2P a anonymous donator set out the bounty for translation\n" +"of the I2P web page and I2P router console into russian language." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:17 +msgid "" +"For collecting the bounty of $115 USD you need to translate the following" +" pages:" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:30 +msgid "" +"Part 2 is the translation of the router console. The whole router console" +" needs\n" +"to be translated to collect the bounty of $115 USD." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/russian-trans.html:37 +msgid "Judge is the russian donor." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:2 +msgid "Bounty migrate I2P IRC to SILC" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:3 +msgid "I2P silc server" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:7 +msgid "" +"For a future of I2P and attract more people\n" +"into I2P this bounty is to setup and host a I2P SILC server. \n" +"This will allow people to send files over their messaging servers and " +"have intrinsic security built into the protocol." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:12 +msgid "" +"A silc server needs to be set up and run for at least 3 month time to get" +" payed. \n" +"A second server should be set up, too." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:16 +msgid "" +"Bounty was withdrawn and money donated to returningnovice and general " +"fund." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/silc.html:22 +msgid "Judge is An Anonymous Secret Society, society@mail.i2p." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:2 +#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:3 +msgid "Syndie development" +msgstr "Desdenvolvemento de Syndie" + +#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:7 +msgid "" +"Beside of I2P we want to encourage users\n" +"to care more about anonymity and security. As I2P is a low \n" +"latency network with its natural limits, the software SYNDIE\n" +"can overcome some of these limits and provide better anonymity\n" +"for people who really need it." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:14 +msgid "" +"For our bad sake the syndie project was out of development for \n" +"quite a long time yet (5 years). To get a fresh and new built \n" +"with needed bugfixes we set out this bounty. Also syndie needs\n" +"some enhancements and a better GUI for users to work with it.\n" +"Current bounty sum is 50 Bitcoin." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/syndie-2012.html:22 +msgid "" +"The latest Syndie coding rally did improve the situation of the\n" +"Syndie package dramatically. A new Syndie package with bugfixes\n" +"was created and made available on different webpages.\n" +"As a result of this work, the bounty sum was reduced and\n" +"the withdrawn money moved to the IPv6 bounty." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:2 +msgid "Bounty unittests" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:3 +msgid "unit test" +msgstr "test de unidades" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:7 +msgid "" +"To improve I2P's maintainability, we want to have a solid set of\n" +"automated unit tests for the critical code. While we do have some\n" +"unit tests at the moment, they are ad-hoc and partly unfinished. \n" +"This bounty is for someone to check the existing tests and move over\n" +"old ones to jUnit, automate their execution, extend them to provide \n" +"better code coverage, and publish the report online. Its a massive \n" +"effort, but can be broken down into phases, listed below (phase 2 \n" +"must occur first, but further phases may happen in any order).\n" +"As this needs some reading of code, it is the best start point for\n" +"new devs to get a good overview of I2P code and coding. A good job\n" +"for college students, interns or anyone who is just interested." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:20 +msgid "" +"Take care! Jobs and bounties shuffled a bit!\n" +"Phase 6,7 and 8 are still open!" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:26 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:40 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:55 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:66 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:77 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:88 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:101 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:112 +#, python-format +msgid "Phase %(phase)s:" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:27 +msgid "CI jenkins and IRC bot" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:28 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:42 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:57 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:68 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:79 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:90 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:103 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:114 +#, python-format +msgid "Bounty: %(euro)s €" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:29 +msgid "server runs and this section is blocked" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:31 +msgid "" +"To collect this bounty, a continuous integration server (Jenkins,\n" +"old name was Hudson) must be set up and a connected IRC bot needs \n" +"to set up in the channel #i2p-dev on IRC2p network to print out\n" +"results of build tests.
\n" +"The server needs to be run long term." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:41 +msgid "Check existing SDK tests" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:43 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:69 +msgid "paid to str4d" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:45 +#, python-format +msgid "" +"To collect this bounty, the existing SDK tests must be checked \n" +"and made to work again. The need to be integrated into the ant \n" +"build scripts (\"ant test\"), and tied in with a code coverage tool (e.g." +" \n" +"Clover). The ant script\n" +"must be capable of generating test status results as a web page, \n" +"which will be published online." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:56 +msgid "SDK test coverage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:58 +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:80 +msgid "paid to unittests dev team" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:60 +msgid "" +"To collect this bounty, the automated unit tests of the SDK \n" +"(i2p/core/java/src) must work again." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:67 +msgid "Router test migration" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:71 +msgid "" +"As with phase 2, the existing unit tests for the router must be\n" +"moved over to the automated system." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:78 +msgid "Router test coverage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:82 +msgid "" +"To collect this bounty, the automated unit tests of the router \n" +"(i2p/router/java/src) must work again." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:89 +msgid "Streaming lib tests" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:94 +msgid "" +"To collect this bounty, a new set of unit tests must meet a \n" +"measured code coverage of 90% of the streaming lib \n" +"(i2p/apps/ministreaming/ and i2p/apps/streaming/)." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:102 +msgid "Unit tests coverage" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:106 +msgid "" +"To collect this bounty, all above unit tests must meet the 100%\n" +"coverage marker (except for log statements)." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:113 +msgid "MultiRouter simulation" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:115 +msgid "will be split in more sub-tasks" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:117 +msgid "" +"To collect this bounty, the existing in-memory multi-router\n" +"simulation must be checked, made work again and extend to simulate\n" +"lots of routers in memory on a single machine. This bounty will\n" +"be split in more fine grained subworks." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/unit-tests.html:126 +msgid "" +"Judge on all these works is the donor and donor decides if a phase is\n" +"called succesfull done and money can be paid." +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:2 +msgid "Bounty I2P vuze plugin" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:3 +msgid "vuze plugin" +msgstr "" + +#: i2p2www/pages/site/get-involved/bounties/vuze-plugin.html:6 +msgid "" +"To improve I2P usage and attract more people\n" +"into I2P torrent P2P I setout the bounty for a working I2P vuze\n" +"plugin.\n" +"The plugin needs to be official and submitted to vuze for publication\n" +"on their webpage/repository for plugins.\n" +"It should be easy to install and configured, work smooth and flawless.\n" +"Configuration should be friendly to starters and made easy to be " +"anonymous.\n" +"It should work with *.b32.i2p destinations as with signed (516++ bits) \n" +"destinations." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:2 +msgid "Application Development" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:3 +msgid "May 2013" +msgstr "Maio de 2013" + +#: i2p2www/pages/site/get-involved/develop/applications.html:7 +#: i2p2www/pages/site/get-involved/develop/applications.html:15 +msgid "Why write I2P-specific code?" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:8 +#: i2p2www/pages/site/get-involved/develop/applications.html:101 +msgid "Important concepts" +msgstr "Conceptos importantes" + +#: i2p2www/pages/site/get-involved/develop/applications.html:9 +#: i2p2www/pages/site/get-involved/develop/applications.html:189 +msgid "Development options" +msgstr "Opcións de desenvolvemento" + +#: i2p2www/pages/site/get-involved/develop/applications.html:10 +#: i2p2www/pages/site/get-involved/develop/applications.html:302 +msgid "Start developing - a simple guide" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:17 +#, python-format +msgid "" +"There are multiple ways to use applications in I2P.\n" +"Using I2PTunnel,\n" +"you can use regular applications without needing to program explicit I2P " +"support.\n" +"This is very effective for client-server scenario's,\n" +"where you need to connect to a single website.\n" +"You can simply create a tunnel using I2PTunnel to connect to that " +"website, as shown in Figure 1." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:25 +msgid "" +"If your application is distributed, it will require connections to a " +"large amount of peers.\n" +"Using I2PTunnel, you will need to create a new tunnel for each peer you " +"want to contact,\n" +"as shown in Figure 2.\n" +"This process can of course be automated, but running a lot of I2PTunnel " +"instances creates a large amount of overhead.\n" +"In addition, with many protocols you will need to force everyone to \n" +"use the same set of ports for all peers - e.g. if you want to reliably " +"run DCC \n" +"chat, everyone needs to agree that port 10001 is Alice, port 10002 is " +"Bob, port \n" +"10003 is Charlie, and so on, since the protocol includes TCP/IP specific " +"information\n" +"(host and port)." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:36 +msgid "" +"General network applications often send a lot of additional data that " +"could be used to identify users.\n" +"Hostnames, port numbers, time zones, character sets, etc. are often sent " +"without informing the user.\n" +"As such, designing the network protocol specifically with anonymity in " +"mind\n" +"can avoid compromising user identities." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:42 +msgid "" +"There are also efficiency considerations to review when determining how " +"to \n" +"interact on top of I2P. The streaming library and things built on top of" +" it\n" +"operate with handshakes similar to TCP, while the core I2P protocols " +"(I2NP and I2CP)\n" +"are strictly message based (like UDP or in some instances raw IP). The " +"important\n" +"distinction is that with I2P, communication is operating over a long fat " +"network - \n" +"each end to end message will have nontrivial latencies, but may contain " +"payloads \n" +"of up to several KB. An application that needs a simple request and " +"response can get rid\n" +"of any state and drop the latency incurred by the startup and teardown " +"handshakes\n" +"by using (best effort) datagrams without having to worry about MTU " +"detection or \n" +"fragmentation of messages." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:56 +#: i2p2www/pages/site/get-involved/develop/applications.html:58 +msgid "" +"Creating a server-client connection using I2PTunnel only requires " +"creating a single tunnel." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:58 +msgid "Figure 1:" +msgstr "Figura 1:" + +#: i2p2www/pages/site/get-involved/develop/applications.html:63 +#: i2p2www/pages/site/get-involved/develop/applications.html:65 +msgid "" +"Setting up connections for a peer-to-peer applications requires a very " +"large amount of tunnels." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:65 +msgid "Figure 2:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:69 +msgid "In summary, a number of reasons to write I2P-specific code:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:73 +msgid "" +"Creating a large amount of I2PTunnel instances consumes a non-trivial " +"amount of resources,\n" +"which is problematic for distributed applications (a new tunnel is " +"required for each peer)." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:77 +msgid "" +"General network protocols often send a lot of additional data that can be" +" used to identify users.\n" +"Programming specifically for I2P allows the creation of a network " +"protocol\n" +"that does not leak such information, keeping users anonymous and secure." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:82 +msgid "" +"Network protocols designed for use on the regular internet can be " +"inefficient\n" +"on I2P, which is a network with a much higher latency." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:89 +#, python-format +msgid "" +"I2P supports a standard plugins interface for" +" developers\n" +"so that applications may be easily integrated and distributed." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:95 +msgid "" +"Applications written in Java and accessible/runnable\n" +"using an HTML interface via the standard webapps/app.war\n" +"may be considered for inclusion in the i2p distribution." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:103 +msgid "There are a few changes that require adjusting to when using I2P:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:107 +msgid "Destination ~= host+port" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:109 +msgid "" +"An application running on I2P sends messages from and receives messages " +"to a\n" +"unique cryptographically secure end point - a \"destination\". In TCP or" +" UDP\n" +"terms, a destination could (largely) be considered the equivalent of a " +"hostname\n" +"plus port number pair, though there are a few differences." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:117 +msgid "" +"An I2P destination itself is a cryptographic construct - all data sent to" +" one is \n" +"encrypted as if there were universal deployment of IPsec with the " +"(anonymized)\n" +"location of the end point signed as if there were universal deployment of" +" DNSSEC." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:122 +msgid "" +"I2P destinations are mobile identifiers - they can be moved from one I2P " +"router\n" +"to another (or it can even \"multihome\" - operate on multiple routers at" +"\n" +"once). This is quite different from the TCP or UDP world where a single " +"end point (port)\n" +"must stay on a single host." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:129 +msgid "" +"I2P destinations are ugly and large - behind the scenes, they contain a " +"2048 bit ElGamal\n" +"public key for encryption, a 1024 bit DSA public key for signing, and a " +"variable size \n" +"certificate, which may contain proof of work or blinded data." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:134 +#, python-format +msgid "" +"There are existing ways to refer to these large and ugly destinations by " +"short\n" +"and pretty names (e.g. \"irc.duck.i2p\"), but those techniques do not " +"guarantee\n" +"globally uniqueness (since they're stored locally in a database on each " +"person's machine)\n" +"and the current mechanism is not especially scalable nor secure (updates " +"to the host list are\n" +"managed using \"subscriptions\" to naming services).\n" +"There may be some secure, human readable, scalable, and globally \n" +"unique, naming system some day, but applications shouldn't depend upon it" +" being in place,\n" +"since there are those who don't think such a beast is possible.\n" +"Further information on the naming system is " +"available." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:148 +#, python-format +msgid "" +"While most applications do not need to distinguish protocols and ports,\n" +"I2P does support them. Complex applications may specify a " +"protocol,\n" +"from port, and to port, on a per-message basis, to multiplex traffic on\n" +"a single destination.\n" +"See the datagram page for details.\n" +"Simple applications operate by listening for \"all protocols\" on \"all " +"ports\" of a destination." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:157 +msgid "Anonymity and confidentiality" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:159 +msgid "" +"I2P has transparent end to end encryption\n" +"and authentication for all data passed over the network - if Bob sends to" +" Alice's destination,\n" +"only Alice's destination can receive it, and if Bob is using the " +"datagrams or streaming \n" +"library, Alice knows for certain that Bob's destination is the one who " +"sent the data." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:166 +msgid "" +"Of course, I2P transparently anonymizes the\n" +"data sent between Alice and Bob, but it does nothing to anonymize the " +"content of what they\n" +"send. For instance, if Alice sends Bob a form with her full name, " +"government IDs, and \n" +"credit card numbers, there is nothing I2P can do. As such, protocols and" +" applications should \n" +"keep in mind what information they are trying to protect and what " +"information they are willing\n" +"to expose." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:175 +msgid "I2P datagrams can be up to several KB" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:177 +#, python-format +msgid "" +"Applications that use I2P datagrams (either raw or repliable ones) can " +"essentially be thought\n" +"of in terms of UDP - the datagrams are unordered, best effort, and " +"connectionless - but unlike\n" +"UDP, applications don't need to worry about MTU detection and can simply " +"fire off large datagrams.\n" +"While the upper limit is nominally 32 KB, the message is fragmented for " +"transport, thus dropping\n" +"the reliability of the whole. Datagrams over about 10 KB are not " +"currently recommended.\n" +"See the datagram page for details.\n" +"For many applications, 10 KB of data is sufficient for an\n" +"entire request or response, allowing them to transparently operate in I2P" +" as a UDP-like \n" +"application without having to write fragmentation, resends, etc." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:191 +msgid "" +"There are several means of sending data over I2P, each with their own " +"pros and cons.\n" +"The streaming lib is the recommended interface, used by the majority of " +"I2P applications." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:196 +msgid "Streaming Lib" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:197 +#, python-format +msgid "" +"The full streaming library is now the " +"standard\n" +"interface. It allows programming using TCP-like sockets, as explained in " +"the Streaming development guide." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:203 +#, python-format +msgid "" +"BOB is the Basic Open Bridge,\n" +"allowing an application in any language to make streaming connections \n" +"to and from I2P. At this point in time it lacks UDP support, but UDP " +"support\n" +"is planned in the near future. BOB also contains several tools, such as \n" +"destination key generation, and verification that an address conforms to" +" \n" +"I2P specifications. Up to date info and applications that use BOB can be" +" \n" +"found at this eepsite." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:216 +msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is recommended." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:217 +#, python-format +msgid "" +"SAM is the Simple Anonymous Messaging protocol, " +"allowing an\n" +"application written in any language to talk to a SAM bridge through a " +"plain TCP socket and have\n" +"that bridge multiplex all of its I2P traffic, transparently coordinating " +"the encryption/decryption\n" +"and event based handling. SAM supports three styles of operation:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:224 +msgid "" +"streams, for when Alice and Bob want to send data to each other reliably " +"and in order" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:227 +msgid "" +"repliable datagrams, for when Alice wants to send Bob a message that Bob " +"can reply to" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:230 +msgid "" +"raw datagrams, for when Alice wants to squeeze the most bandwidth and " +"performance as possible,\n" +"and Bob doesn't care whether the data's sender is authenticated or not " +"(e.g. the data transferred\n" +"is self authenticating)" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:236 +msgid "" +"SAM V3 aims at the same goal as SAM and SAM V2, but does not require\n" +"multiplexing/demultiplexing. Each I2P stream is handled by its own socket" +" between the application\n" +"and the SAM bridge. Besides, datagrams can be sent and received by the " +"application through datagram\n" +"communications with the SAM bridge." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:243 +#, python-format +msgid "" +"SAM V2 is a new version used by imule\n" +"that fixes some of the problems in SAM.\n" +"
\n" +"SAM V3 is used by imule since version 1.4.0." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:251 +msgid "" +"The I2PTunnel application allows applications to build specific TCP-like " +"tunnels to peers \n" +"by creating either I2PTunnel 'client' applications (which listen on a " +"specific port and connect\n" +"to a specific I2P destination whenever a socket to that port is opened) " +"or I2PTunnel 'server'\n" +"applications (which listen to a specific I2P destination and whenever it " +"gets a new I2P \n" +"connection it outproxies to a specific TCP host/port). These streams are" +" 8-bit clean, and are\n" +"authenticated and secured through the same streaming library that SAM " +"uses, but there is a \n" +"nontrivial overhead involved with creating multiple unique I2PTunnel " +"instances, since each have\n" +"their own unique I2P destination and their own set of tunnels, keys, etc." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:263 +msgid "" +"I2P supports a SOCKS V4 and V5 proxy.\n" +"Outbound connections work well. Inbound (server) and UDP functionality " +"may be incomplete\n" +"and untested." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:270 +msgid "Removed" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:271 +msgid "" +"There used to be a simple \"ministreaming\" library,\n" +"but now ministreaming.jar contains only the interfaces for the full " +"streaming library." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:276 +msgid "Datagrams" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:277 +msgid "Recommended for UDP-like applications" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:278 +#, python-format +msgid "" +"The Datagram library allows sending UDP-" +"like packets.\n" +"It's possible to use:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:283 +msgid "Repliable datagrams" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:284 +msgid "Raw datagrams" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:288 +msgid "Not recommended" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:289 +#, python-format +msgid "" +"I2CP itself is a language independent protocol, " +"but to implement an I2CP library \n" +"in something other than Java there is a significant amount of code to be " +"written (encryption routines, \n" +"object marshalling, asynchronous message handling, etc). While someone " +"could write an I2CP library in \n" +"C or something else, it would most likely be more useful to use the C SAM" +" library instead." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:296 +msgid "Web Applications" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:297 +msgid "" +"I2P comes with the Jetty webserver, and configuring to use the Apache " +"server instead is straightforward.\n" +"Any standard web app technology should work." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:303 +msgid "" +"Developing using I2P requires a working I2P installation and a " +"development environment of your own choice.\n" +"If you are using Java, you can start development with the streaming library or datagram library.\n" +"Using another programming language, SAM or BOB can be used." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:309 +msgid "Developing with the streaming library" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:311 +msgid "" +"The following example shows how to create TCP-like client and server " +"applications\n" +"using the streaming library." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:316 +msgid "This will require the following libraries in your classpath:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:320 +msgid "The streaming library itself" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:321 +msgid "Factory and interfaces for the streaming library" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:322 +msgid "Standard I2P classes, data structures, API, and utilities" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:325 +msgid "" +"You can fetch these from an I2P installation, or add the following " +"dependencies\n" +"from Maven Central:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:334 +msgid "" +"Network communication requires the usage of I2P network sockets.\n" +"To demonstrate this, we will create an application where a client can " +"send text messages to a server,\n" +"who will print the messages and send them back to the client. In other " +"words, the server will function as an echo." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:339 +msgid "" +"We will start by initializing the server application. This requires " +"getting an I2PSocketManager\n" +"and creating an I2PServerSocket.\n" +"We will not provide the I2PSocketManagerFactory with the saved keys for " +"an existing Destination,\n" +"so it will create a new Destination for us.\n" +"So we will ask the I2PSocketManager for an I2PSession, so we can find out" +" the Destination that\n" +"was created, as we will need to copy and paste that information later so " +"the client can connect to us." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:370 +msgid "Code example 1: initializing the server application." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:372 +msgid "" +"Once we have an I2PServerSocket, we can create I2PSocket instances to " +"accept connections from clients.\n" +"In this example, we will create a single I2PSocket instance, that can " +"only handle one client at a time.\n" +"A real server would have to be able to handle multiple clients.\n" +"To do this, multiple I2PSocket instances would have to be created, each " +"in separate threads.\n" +"Once we have created the I2PSocket instance, we read data, print it and " +"send it back to the client.\n" +"The bold code is the new code we add." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:456 +msgid "Code example 2: accepting connections from clients and handling messages." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:460 +msgid "" +"When you run the above server code, it should print something like this " +"(but without the line endings, it should just be\n" +"one huge block of characters):" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:474 +msgid "" +"This is the base64-representation of the server Destination. The client " +"will need this string to reach the server." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:478 +msgid "" +"Now, we will create the client application. Again, a number of steps are " +"required for initialization.\n" +"Again, we will need to start by getting an I2PSocketManager.\n" +"We won't use an I2PSession and an I2PServerSocket this time.\n" +"Instead, we will use the server Destination string to start our " +"connection.\n" +"We will ask the user for the Destination string, and create an I2PSocket " +"using this string.\n" +"Once we have an I2PSocket, we can start sending and receiving data to and" +" from the server." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:562 +msgid "" +"Code example 3: starting the client and connecting it to the server " +"application." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:564 +msgid "" +"Finally, you can run both the server and the client application.\n" +"First, start the server application. It will print a Destination string " +"(like shown above).\n" +"Next, start the client application. When it requests a Destination " +"string, you can enter the string printed by the server.\n" +"The client will then send 'Hello I2P!' (along with a newline) to the " +"server, who will print the message and send it back to the client." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:570 +msgid "Congratulations, you have successfully communicated over I2P!" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:574 +msgid "Existing Applications" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:575 +msgid "Contact us if you would like to contribute." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:596 +msgid "Application Ideas" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:598 +msgid "NNTP server - there have been some in the past, none at the moment" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:601 +msgid "" +"Jabber server - there have been some in the past, and there is one at the" +" moment, with access to the public internet" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:604 +msgid "PGP Key server and/or proxy" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:607 +msgid "" +"Content Distribution / DHT applications - resurrect feedspace,\n" +"port dijjer, look for alternatives" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:611 +msgid "Help out with Syndie development" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:614 +msgid "" +"Web-based applications - The sky is the limit for hosting web-server-" +"based\n" +"applications such as blogs, pastebins, storage, tracking, feeds, etc.\n" +"Any web or CGI technology such as Perl, PHP, Python, or Ruby will work." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/applications.html:619 +msgid "" +"Resurrect some old apps, several previously in the i2p source package -\n" +"bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping, feedspace" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:2 +msgid "I2P Developer's MTN Keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:4 +msgid "" +"Monotone servers used by the I2P project require two types of keys to be " +"used." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:8 +msgid "" +"Commit Keys to sign changes checked-in to the " +"respository; and" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:9 +msgid "" +"Transport Keys to push changes to remote " +"servers." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:12 +#, python-format +msgid "" +"Everyone that uses Monotone to checkout the I2P codebase will need to\n" +"import the\n" +"developer commit keys, but only Monotone \n" +"server operators will need to import the transport keys." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:19 +msgid "Developer Commit keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:284 +msgid "Developer Transport Keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/developers-keys.html:285 +#, python-format +msgid "" +"Note: Transport keys are only needed for setting up a\n" +"Monotone server." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/license-agreements.html:2 +msgid "License Agreements" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/license-agreements.html:5 +#, python-format +msgid "For more information see the licenses page." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/license-agreements.html:8 +msgid "" +"Following is a monotonerc file defining the current trust list.\n" +"Developers must use this file in ~/.monotone/monotonerc or\n" +"_MTN/montonerc in their i2p.i2p workspace." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/license-agreements.html:17 +msgid "Agreements" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:2 +msgid "I2P Software Licenses" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:4 +#, python-format +msgid "" +"As required by our\n" +"threat model (among other reasons), the \n" +"software developed to support the anonymous communication \n" +"network we call I2P must be freely available, open source, \n" +"and user modifiable. To meet these criteria, we make use of\n" +"a variety of legal and software engineering techniques so\n" +"as to remove as many barriers to entry for those considering\n" +"making use of or contributing to the I2P effort." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:15 +msgid "" +"While the information below may be more confusing than just simply \n" +"stating \"I2P is BSD\", \"I2P is GPL\", or \"I2P is public domain\",\n" +"the short answer to the question \"How is I2P licensed?\" is this:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:21 +msgid "All software bundled in the I2P distributions will allow:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:23 +msgid "use without fee" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:24 +msgid "" +"use with no restrictions on how, when, where, why, or by whom is running " +"it" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:25 +msgid "access to the source code without fee" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:26 +msgid "modifications to the source" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:29 +msgid "" +"Most of the software guarantees much more - the ability of anyone " +"to \n" +"distribute the modified source however they choose. However, not all of " +"the \n" +"software bundled provides this freedom - the GPL restricts the ability of" +" \n" +"developers who wish to integrate I2P with their own applications that are" +" not \n" +"themselves open source applications. While we applaud the noble goals of" +" \n" +"increasing the resources in the commons, I2P is best served by removing " +"any\n" +"barriers that stand in the way of its adoption - if a developer " +"considering whether\n" +"they can integrate I2P with their application has to stop and check with " +"their lawyer,\n" +"or conduct a code audit to make sure their own source can be released as " +"GPL-compatible,\n" +"we lose out." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:42 +msgid "Component licenses" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:43 +msgid "" +"The I2P distribution contains several resources, reflecting the " +"partitioning of \n" +"the source code into components. Each component has its own license, " +"which all \n" +"developers who contribute to it agree to - either by explicitly declaring" +" the release\n" +"of code committed under a license compatible with that component, or by " +"implicitly\n" +"releasing the code committed under the component's primary license. Each" +" of these \n" +"components has a lead developer who has the final say as to what license " +"is compatible\n" +"with the component's primary license, and the I2P project manager has the" +" final say as\n" +"to what licenses meet the above four guarantees for inclusion in the I2P " +"distribution." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:56 +msgid "Component" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:57 +msgid "Source path" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:58 +msgid "Resource" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:59 +msgid "Primary license" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:60 +msgid "Alternate licenses" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:61 +msgid "Lead developer" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:275 +msgid "GPL + java exception" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:276 +#, python-format +msgid "" +"While it may be redundant, just for clarity the\n" +"GPL'ed code included within\n" +"I2PTunnel and other apps must be released under the GPL with an " +"additional \"exception\"\n" +"explicitly authorizing the use of Java's standard libraries:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:292 +msgid "" +"All source code under each component will by default be licensed under " +"the\n" +"primary license, unless marked otherwise in the code. All of the above " +"is\n" +"summary of the license terms - please see the specific license for the " +"component\n" +"or source code in question for authoritative terms. Component source " +"locations and\n" +"resource packaging may be changed if the repository is reorganized." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:300 +msgid "Website content" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:308 +msgid "Commit privileges" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:309 +#, python-format +msgid "" +"Developers may push changes to a distributed monotone repository if you\n" +"receive permission from the person running that repository.\n" +"See the Monotone Page for details." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:315 +msgid "" +"However, to have changes included in a release, developers\n" +"must be trusted by the release manager (currently zzz).\n" +"In addition, they must explicitly agree with the above terms to be " +"trusted.\n" +"That means that they must send one of the release managers a signed " +"message affirming that:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:322 +msgid "" +"Unless marked otherwise, all code I commit is implicitly licensed under\n" +"the component's primary license" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:326 +msgid "" +"If specified in the source, the code may be explicitly licensed under one" +"\n" +"of the component's alternate licenses" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:330 +msgid "" +"I have the right to release the code I commit under the terms I\n" +"am committing it" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/licenses.html:336 +#, python-format +msgid "" +"If anyone is aware of any instances where the above conditions are not " +"met,\n" +"please contact the component lead and/or an I2P release manager with " +"further\n" +"information.\n" +"See developers' license agreements." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:2 +msgid "Release Signing Key" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:4 +msgid "Releases 0.7.6 and later are signed by zzz. His current public key is:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:190 +msgid "Releases from 0.9.9 could be signed by str4d. His current public key is:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:563 +msgid "str4d has signed the following releases:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:571 +msgid "Releases 0.7.6 through 0.9.12 were signed by zzz with the following key:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/release-signing-key.html:607 +msgid "" +"Releases 0.6.1.31 through 0.7.5 were signed by Complication. His public " +"key is:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/security-key.html:2 +msgid "Security GPG Key" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/security-key.html:4 +msgid "Following is the GPG key for the security@geti2p.net email address:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:2 +msgid "Signed Developer Keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:4 +msgid "" +"Keys for zzz, Complication and welterde are provided clearsigned. The key" +" for jrandom must be\n" +"verified differently, since he's away, and only left a binary detached\n" +"signature for his key." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:10 +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:16 +msgid "Monotone keys for zzz" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:11 +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:47 +msgid "Monotone keys for welterde" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:12 +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:79 +msgid "Monotone keys for Complication" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:13 +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:114 +msgid "Monotone keys for jrandom" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:14 +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:169 +msgid "Others" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:17 +msgid "" +"Tip: To find zzz's GPG key, on his eepsite locate the key " +"`0xA76E0BED`, with\n" +"the name `zzz@mail.i2p` and the fingerprint `4456 EBBE C805 63FE 57E6 " +"B310 4155\n" +"76BA A76E 0BED`." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:49 +msgid "" +"Tip: To find welterde's GPG key, on public keyservers locate the " +"key\n" +"`0x62E011A1`, with the name `welterde@arcor.de` and the fingerprint `6720" +" FD81\n" +"3872 6DFC 6016 64D1 EBBC 0374 62E0 11A1`." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:81 +msgid "" +"Tip: To find Complication's GPG key, on his eepsite locate the key" +"\n" +"`0x79FCCE33`, with the name `complication@mail.i2p` and the fingerprint " +"`73CF\n" +"2862 87A7 E7D2 19FF DB66 FA1D FC6B 79FC CE33`." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:116 +msgid "" +"Tip: To find jrandom's GPG key for Syndie releases, on public " +"keyservers locate\n" +"the key `0x393F2DF9`, with the name `syndie-dist-key@i2p.net` and the\n" +"fingerprint `AE89 D080 0E85 72F0 B777 B2ED C2FA 68C0 393F 2DF9`." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:122 +msgid "" +"Jrandom had to leave unexpectedly in the end of 2007. His commit key was\n" +"deployed in the Syndie Monotone repository, in a file named `mtn-" +"committers`.\n" +"That file also had a GPG signature, `mtn-committers.sig`, but it was a " +"binary\n" +"detached signature. I am going to supply both files in GPG ASCII-armoured" +" form\n" +"below." +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:130 +msgid "" +"First, the file `mtn-committers` containing jrandom's Monotone key. Save " +"as\n" +"`mtn-committers.asc` and unpack it using `gpg --output mtn-committers " +"--dearmor\n" +"mtn-committers.asc`:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:151 +msgid "" +"Now the file `mtn-committers.sig`, containing the GPG signature. Save as\n" +"`mtn-committers.sig.asc` and unpack it using `gpg --output mtn-" +"committers.sig\n" +"--dearmor mtn-committers.sig.asc`. Use it to verify the above supplied\n" +"`mtn-committers` file:" +msgstr "" + +#: i2p2www/pages/site/get-involved/develop/signed-keys.html:170 +#, python-format +msgid "" +"Some of the developers have included their Monotone keys in their signed license agreement." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:2 +msgid "Developer Guidelines and Coding Style" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:3 +msgid "April 2016" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:5 +#, python-format +msgid "Read the new developers guide first." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:9 +msgid "Basic Guidelines and Coding Style" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:11 +msgid "" +"Most of the following should be common sense for anybody who has worked " +"on open source or in a commercial\n" +"programming envrionment.\n" +"The following applies mostly to the main development branch i2p.i2p.\n" +"Guidelines for other branches, plugins, and external apps may be " +"substantially different;\n" +"check with the appropriate developer for guidance." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:19 +msgid "Community" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:21 +msgid "" +"Please don't just \"write code\". If you can, participate in other " +"development activities, including:\n" +"development discussions and support on IRC, zzz.i2p, and forum.i2p; " +"testing;\n" +"bug reporting and responses; documentation; code reviews; etc." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:26 +msgid "" +"Active devs should be available periodically on IRC #i2p-dev.\n" +"Be aware of the current release cycle.\n" +"Adhere to release milestones such as feature freeze, tag freeze, and\n" +"the checkin deadline for a release." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:35 +msgid "Release Cycle" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:36 +msgid "" +"Our normal release cycle is 6-10 weeks.\n" +"Following are the approximate deadlines within a typical 8-week cycle.\n" +"Actual deadlines for each release are set by the lead developer." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:43 +msgid "1-2 days after previous release: Checkins to trunk are allowed." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:46 +msgid "" +"2-3 weeks after previous release: Deadline to propagate major changes " +"from other branches to trunk." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:49 +msgid "4-5 weeks before release: Deadline to request new home page links." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:52 +msgid "3-4 weeks before release: Feature freeze. Deadline for major new features." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:55 +msgid "" +"2-3 weeks before release: Hold project meeting to review new home page " +"link requests, if any." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:58 +msgid "" +"7-10 days before release: String freeze. No more changes to translated " +"(\"tagged\") strings.\n" +"Push strings to Transifex, announce translation deadline on Transifex." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:62 +msgid "" +"7-10 days before release: Feature deadline. Bug fixes only after this " +"time. No more features, refactoring or cleanup." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:65 +msgid "" +"3-4 days before release: Translation deadline. Pull translations from " +"Transifex and check in." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:68 +msgid "" +"2-3 days before release: Checkin deadline. No checkins after this time " +"without the permission of the release builder." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:71 +msgid "Hours before release: Code review deadline." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:80 +msgid "" +"Have a basic understanding of distributed source control systems, even if" +" you haven't\n" +"used monotone before. Ask for help if you need it.\n" +"Once pushed, checkins are forever, there is no undo. Please be careful.\n" +"If you have not used monotone before, start with baby steps.\n" +"Check in some small changes and see how it goes." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:87 +msgid "" +"Test your changes before checking them in.\n" +"If you prefer the checkin-before-test development model,\n" +"use your own development branch (e.g. i2p.i2p.yourname.test)\n" +"and propagate back to i2p.i2p once it is working well.\n" +"Do not break the build. Do not cause regressions.\n" +"In case you do (it happens), please do not vanish for a long period after" +"\n" +"you push your change." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:96 +msgid "" +"If your change is non-trivial, or you want people to test it and need " +"good test reports\n" +"to know whether your change was tested or not, add a checkin comment to " +"history.txt\n" +"and increment the build revision in RouterVersion.java." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:101 +msgid "" +"Ensure that you have the latest monotonerc file in _MTN.\n" +"Do not check in on top of untrusted revisions." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:105 +msgid "" +"Ensure that you 'mtn pull' and 'mtn update' to the latest revision before" +" you check in and push.\n" +"If you inadvertently diverge, merge and push as soon as possible.\n" +"Don't routinely make others merge for you.\n" +"Yes, we know that monotone says you should push and then merge,\n" +"but in our experience, in-workspace merge works just as well as in-" +"database merge,\n" +"without creating a merge revision." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:113 +msgid "" +"Do not check in major changes into the main i2p.i2p branch late in the " +"release cycle.\n" +"If a project will take you more than a couple days, create your own " +"branch in monotone\n" +"and do the development there so you do not block releases." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:120 +msgid "Coding Style" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:122 +msgid "" +"Coding style throughout most of the code is 4-spaces for indentation. Do " +"not use tabs.\n" +"Do not reformat code. If your IDE or editor wants to reformat everything," +" get control of it.\n" +"Yes, we know 4 spaces is a pain, but perhaps you can configure your " +"editor appropriately.\n" +"In some places, the coding style is different.\n" +"Use common sense. Emulate the style in the file you are modifying." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:129 +msgid "" +"All new public and package-private classes and methods require Javadocs. " +"Add @since release-number.\n" +"Javadocs for new private methods are desirable." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:133 +msgid "" +"Classes in core/ (i2p.jar) and portions of i2ptunnel are part of our " +"official API.\n" +"There are several out-of-tree plugins and other applications that rely on" +" this API.\n" +"Be careful not to make any changes that break compatibility.\n" +"Don't add methods to the API unless they are of general utility.\n" +"Javadocs for API methods should be clear and complete.\n" +"If you add or change the API, also update the documentation on the " +"website (i2p.www branch)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:141 +msgid "" +"Tag strings for translation where appropriate.\n" +"Don't change existing tagged strings unless really necessary, as it will " +"break existing translations.\n" +"Do not add or change tagged strings after the \"tag freeze\" in the " +"release cycle so that\n" +"translators have a chance to update before the release." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:147 +msgid "" +"Use generics and concurrent classes where possible. I2P is a highly " +"multi-threaded application." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:150 +msgid "" +"Be familiar with common Java pitfalls that are caught by findbugs.\n" +"Run 'ant findbugs' to learn more." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:154 +msgid "" +"We require Java 7 to build and run I2P.\n" +"Do not use Java 8 classes or methods anywhere.\n" +"Do not use Java 7 or 8 classes or methods in embedded subsystems (core, " +"router, mstreaming, streaming, i2ptunnel),\n" +"as Android and embedded applications require only Java 6. All classes " +"must be available in Android API 9.\n" +"Java 7 language features are acceptable in these subsystems if supported " +"by the current version\n" +"of the Android SDK and they compile to Java 6-compatible code." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:162 +msgid "" +"Explicitly convert between primitive types and classes;\n" +"don't rely on autoboxing/unboxing." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:166 +msgid "Don't use URL. Use URI." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:169 +msgid "" +"Don't catch Exception. Catch RuntimeException and checked exceptions " +"individually." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:172 +msgid "" +"Don't use String.getBytes() without a UTF-8 charset argument. You may " +"also use DataHelper.getUTF8() or DataHelper.getASCII()." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:175 +msgid "" +"Always specify a UTF-8 charset when reading or writing files. The " +"DataHelper utilities may be helpful." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:178 +msgid "" +"Always specify a locale (for example Locale.US) when using " +"String.toLowerCase() or String.toUpperCase().\n" +"Do not use String.equalsIgnoreCase(), as a locale cannot be specified." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:182 +msgid "Don't use String.split(). Use DataHelper.split()." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:185 +msgid "Ensure that InputStreams and OutputStreams are closed in finally blocks." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:188 +msgid "" +"Use {} for all for and while blocks, even if only one line.\n" +"If you use {} for either the if, else, or if-else block, use it for all " +"blocks.\n" +"Put \"} else {\" on a single line." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:193 +msgid "Specify fields as final wherever possible." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:196 +msgid "" +"Don't store I2PAppContext, RouterContext, Log, or any other references to" +" router or context items in static fields." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:199 +msgid "Don't start threads in constructors. Use I2PAppThread instead of Thread." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:204 +msgid "Licenses" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:206 +msgid "" +"Only check in code that you wrote yourself.\n" +"Before checking in any code or library jars from other sources,\n" +"justify why it is necessary,\n" +"verify the license is compatible,\n" +"and obtain approval from the lead developer." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:213 +msgid "" +"If you do obtain approval to add external code or jars,\n" +"and binaries are available in any Debian or Ubuntu package,\n" +"you must implement build and packaging options to use the external " +"package instead.\n" +"Checklist of files to modify:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:221 +msgid "" +"For any images checked in from external sources,\n" +"it is your responsibility to first verify the license is compatible.\n" +"Include the license and source information in the checkin comment." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:228 +msgid "Bugs" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:230 +#, python-format +msgid "" +"Managing Trac tickets is everybody's job, please help.\n" +"Monitor %(trac)s for tickets you have been assigned or can help with.\n" +"Assign, categorize, comment on, fix, or close tickets if you can." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:235 +msgid "" +"New developers should start by fixing a bug.\n" +"Search for bugs with the 'easy' keyword on trac.\n" +"When you have a fix, attach your patch to the ticket and add the keyword " +"'review-needed'.\n" +"Do not close the ticket until it's been successfully reviewed and you've " +"checked your changes in.\n" +"Once you've done this smoothly for a couple of tickets, you may follow " +"the normal procedure below." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/dev-guidelines.html:242 +msgid "" +"Close a ticket when you think you've fixed it.\n" +"We don't have a test department to verify and close tickets.\n" +"If you arent sure you fixed it, close it and add a note saying\n" +"\"I think I fixed it, please test and reopen if it's still broken\".\n" +"Add a comment with the dev build number or revision and set\n" +"the milestone to the next release." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:2 +msgid "Using an IDE with I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:4 +msgid "" +"The main I2P development branch (i2p.i2p) has been set up to" +" enable developers to easily set up two of the commonly-used IDEs for " +"Java development: Eclipse and NetBeans." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:10 +msgid "" +"The main I2P development branches (i2p.i2p and branches from" +" it) contain .project and .classpath Eclipse files, to enable the branch " +"to be easily set up in Eclipse." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:16 +msgid "" +"Check out the I2P branch into some directory (e.g. " +"$HOME/dev/i2p.i2p)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:20 +msgid "" +"Open Eclipse and create a new Workspace, based in the directory that the " +"I2P branch was checked out to." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:24 +msgid "" +"Select \"File - Import...\" and then under \"General\" select \"Existing " +"Projects into Workspace\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:28 +msgid "" +"For \"Select root directory:\" choose the directory that the I2P branch " +"was checked out to." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:32 +msgid "If necessary, click \"Refresh\" to refresh the list of projects." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:36 +msgid "Select every project in the list, and click \"Finish\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:40 +msgid "" +"Done! Your workspace should now contain all projects within the I2P " +"branch, and their build dependencies should be correctly set up." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/ides.html:48 +msgid "" +"The main I2P development branches (i2p.i2p and branches from" +" it) contain NetBeans project files." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:2 +msgid "Monotone Guide" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:6 +msgid "Operating a Monotone client" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:8 +#: i2p2www/pages/site/get-involved/guides/monotone.html:61 +msgid "Generating Monotone keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:9 +msgid "Trust and initializing your repository" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:10 +#: i2p2www/pages/site/get-involved/guides/monotone.html:194 +msgid "Obtaining and deploying developers' keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:11 +#: i2p2www/pages/site/get-involved/guides/monotone.html:225 +msgid "Setting up trust evaluation hooks" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:12 +#: i2p2www/pages/site/get-involved/guides/monotone.html:266 +msgid "" +"Pulling the i2p.i2p, i2p.www and " +"i2p.syndie branches" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:13 +#: i2p2www/pages/site/get-involved/guides/monotone.html:312 +msgid "Verifying that trust evaluation works" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:14 +#: i2p2www/pages/site/get-involved/guides/monotone.html:361 +msgid "Checking out a working copy of the latest version" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:15 +#: i2p2www/pages/site/get-involved/guides/monotone.html:388 +msgid "Updating your working copy to the latest version" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:19 +#: i2p2www/pages/site/get-involved/guides/monotone.html:418 +msgid "Operating a Monotone Server" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:21 +msgid "Obtaining and deploying developers’ transport keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:22 +#: i2p2www/pages/site/get-involved/guides/monotone.html:428 +msgid "Granting push and pull access" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:23 +#: i2p2www/pages/site/get-involved/guides/monotone.html:473 +msgid "Running Monotone in server mode" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:24 +#: i2p2www/pages/site/get-involved/guides/monotone.html:498 +msgid "Differences under Debian GNU/Linux" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:32 +#, python-format +msgid "" +"This is a revised version of Complication's original\n" +" guide detailing the use of Monotone in I2P development.\n" +" For basic instructions see the quick-start " +"guide." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:40 +#, python-format +msgid "" +"I2P has a distributed development model. The source code is replicated " +"across\n" +" independently administered Monotone (\"MTN\") repositories.\n" +" Developers with commit rights are able to push their changes to the " +"repository\n" +" (a license agreement needs to be " +"signed\n" +" before commit rights are granted)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:50 +msgid "" +"Some of Monotone's noteworthy qualities are: distributed\n" +" version control, cryptographic authentication, access control, its " +"small size, having few\n" +" dependencies, storage of projects in a compressed SQLite database file," +" and\n" +" having the ability to resume interrupted synchronization attempts." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:59 +msgid "Operating a Monotone Client" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:64 +msgid "" +"A transport key grants you the ability to push your changes to a Monotone" +" repository server.\n" +" In order to commit code into Monotone (in essence signing your code), a" +" commit key is also needed.\n" +" None of the public Monotone servers on I2P currently require a key in " +"order to read (or pull) the source code." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:72 +msgid "" +"Without a transport key, one cannot:\n" +" " +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:83 +msgid "" +"Without a commit key, one cannot:\n" +" " +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:92 +msgid "" +"If you only intend to retrieve code from MTN, feel free to skip to the\n" +" next section. " +"If you want\n" +" to generate keys, read the following." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:100 +msgid "" +"By convention keys are named like an e-mail addresses, but a " +"corresponding e-mail\n" +" address does not need to exist. For example, your keys might be named:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:111 +msgid "" +"Monotone stores keys under $HOME/.monotone/keys in " +"text files which\n" +" are named identically to the keys. For example:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:121 +msgid "" +"To generate transport and commit keys, enter the following commands at a " +"prompt:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:131 +msgid "" +"Monotone will prompt you for a password to protect your keys. You are " +"very strongly encouraged to set a password\n" +" for the commit key. Many users will leave an empty password for the " +"transport key, especially those running a\n" +" Monotone server." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:139 +msgid "Trust, and initializing your repository" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:143 +msgid "" +"Monotone's security model helps to ensure that nobody can easily " +"impersonate a developer without\n" +" it being noticed. Since developers can make mistakes and become " +"compromised,only manual review can\n" +" ensure quality of code. Monotone's trust model will ensure that you " +"read the right diffs. It does\n" +" not replace reading diffs." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:153 +msgid "" +"A Monotone repository is a single file (a compressed SQLite database) " +"which contains all of the project's source code and history." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:159 +msgid "" +"After importing the " +"developers' keys into Monotone and\n" +" setting up trust " +"evaluation hooks,\n" +" Monotone will prevent untrusted code from being checked out into your " +"workspace.\n" +" There are commands available to clean untrusted code from your " +"workspace but in practice they've not been\n" +" needed due to the push access policies in place." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:169 +msgid "" +"A repository can hold many branches. For example, our repository holds " +"the\n" +" following main branches:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:174 +msgid "The I2P router and associated programs" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:175 +msgid "The I2P project website" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:176 +msgid "Syndie, a distributed forums tool" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:181 +msgid "" +"By convention, the I2P Monotone repository is named i2p.mtn." +" Before pulling\n" +" source code from servers, a database for your repository will need to " +"be initialized.\n" +" To initialize your local repository, change into the directory that you" +" want the\n" +" i2p.mtn file and branch directories to be stored and issue" +" the following\n" +" command:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:197 +msgid "" +"Keys which developers use to commit code are essential for trust " +"evaluation in\n" +" Monotone. The other developers' transport keys are only required for " +"Monotone server operators.\n" +" " +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:204 +#, python-format +msgid "" +"Developers' commit keys are provided GPG-signed on another page." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:210 +#, python-format +msgid "" +"To import developers' keys after verifying their authenticity, copy all of the keys into a new\n" +" file. Create this file (e.g. keys.txt) in the same " +"directory where i2p.mtn is located. Import the keys with the" +" command:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:220 +msgid "" +"Note: Never add keys to " +"$HOME/.monotone/keys manually." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:228 +msgid "" +"The default Monotone trust policy is way too lax for our requirements: " +"every committer is trusted by default.\n" +" That is not acceptable for I2P development." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:235 +msgid "" +"Change into the directory $HOME/.monotone and open " +"the file\n" +" monotonerc with a text editor. Copy and paste the " +"following two functions into this file:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:244 +msgid "" +"The first function determines an intersection between two sets, in our " +"case a\n" +" revision's signers and trusted signers." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:251 +msgid "" +"The second function determines trust in a given revision, by calling the " +"first\n" +" function with \"signers\" and \"trusted\" as arguments. If the " +"intersection is\n" +" null, the revision is not trusted. If the intersection is not empty, " +"the\n" +" revision is trusted. Otherwise, the revision is not trusted." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:260 +msgid "" +"More information about Trust Evaluation Hooks can be found in the official Monotone " +"documentation." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:268 +msgid "" +"I2P is shipped with a pre-configured tunnel pointing to the project " +"Monotone server. Ensure that the tunnel has been started\n" +" within I2PTunnel before" +" attempting to pull the source code from 127.0.0.1:8998." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:275 +msgid "" +"Enter the directory where you initialized i2p.mtn. Depending" +" on whether you\n" +" want only I2P sources, or also sources for the I2P website and Syndie, " +"you can\n" +" perform the pull operation in different ways." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:283 +msgid "If you only want I2P sources:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:292 +msgid "If you want all branches:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:298 +msgid "" +"If the transfer aborts before completing sucessfully, simply repeating " +"the pull command will resume the transfer." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:304 +msgid "" +"Pulling in the above examples is done anonymously by specifying an empty " +"transport key.\n" +" If everyone pulls anonymously it will be harder for an attacker who " +"gains control of the server\n" +" to selectively provide some people with tampered data." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:315 +msgid "To verify that trust evaluation works:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:319 +msgid "Make a backup of your monotonerc file." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:320 +msgid "" +"Modify monotonerc by setting the trusted_signers " +"variable in the following way:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:326 +msgid "" +"With monotonerc configured as above, Monotone will no" +" longer trust any committers. Confirm this by changing into the\n" +"directory where i2p.mtn was created and attempt a checkout " +"of the I2P branch:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:336 +msgid "" +"A directory named i2p.i2p should not appear. You " +"should encounter many\n" +" error messages like:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:353 +msgid "" +"If you are satisfied with results, restore the backup of\n" +" monotonerc that was created above. If you didn't create a " +"backup\n" +" as advised, re-read Setting up trust evaluation hooks." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:364 +msgid "" +"If you already have a branch checked out, skip to the next\n" +" section." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:371 +msgid "" +"Change into the directory where i2p.mtn is located. Over " +"there issue:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:380 +msgid "" +"The checkout should complete without error messages and a directory named" +"\n" +" i2p.i2p should appear in the current directory. " +"Congratulations! You have\n" +" successfully checked out the latest I2P sources, ready to be compiled." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:391 +msgid "" +"If you haven't done this already, pull fresh code from the server to your" +" local\n" +" Monotone repository. To accomplish this, change into the directory " +"where\n" +" i2p.mtn is located and issue:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:402 +msgid "Now change into your i2p.i2p directory, and over there issue:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:411 +msgid "" +"As long as there were no errors…Congratulations! You have " +"successfully updated to the latest I2P sources. They\n" +" should be ready to compile." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:420 +msgid "Obtaining and deploying developers' transport keys" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:423 +msgid "" +"As a server operator you may want to grant push access to certain " +"developers." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:431 +msgid "By default the Monotone server denies all access." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:437 +msgid "To grant pull access to all clients, set the following in" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:449 +msgid "" +"No one will not be able to push code to your server without permission " +"being explicitly granted. To grant push access:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:455 +msgid "" +"Add the name of the user's transport key to\n" +"$HOME/.monotone/write-permissions, such as\n" +"
\n"
+"    zzz-transport@mail.i2p\n"
+"    complication-transport@mail.i2p\n"
+"
\n" +"with one key per line." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:466 +msgid "" +"Import the transport key(s) into your database. The procedure for " +"importing transport keys is the same as for\n" +"importing commit keys, which is described in the section Obtaining and deploying " +"developers' keys." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:476 +msgid "" +"A separate database should be used for your Monotone server because " +"monotone will lock the database while it is served to others.\n" +" Make a copy of your development database, then start the server with:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:483 +msgid "" +"If your key is protected with a passphrase, Monotone may request the " +"passphrase\n" +" when the first client connects. You can work around this by connecting " +"making the first client connection to your server\n" +" (or by clearing the password for your transport key)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:491 +msgid "" +"For your server to be accessible for others over I2P, you will need to " +"create a\n" +" server tunnel for it. Use the \"Standard\" tunnel type and \"Bulk\" " +"profile." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:501 +msgid "" +"Debian (amongst other distributions) has integrated Monotone into their\n" +" framework of daemons/services. Although Monotone servers can still be " +"run\n" +" \"the ordinary way\" on Debian systems, doing it the \"Debian way\" may" +" be more straightforward." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/monotone.html:509 +msgid "" +"Permissions are granted by editing the files\n" +" /etc/monotone/read-permissions and\n" +" /etc/monotone/write-permissions. You'll also need to edit\n" +" /etc/default/monotone to enable monotone to start at boot " +"or to\n" +" customize the host, port, or database location." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:2 +msgid "New Developer's Guide" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:5 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:31 +msgid "Basic study" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:6 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:45 +msgid "Getting the I2P code" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:8 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:52 +msgid "The easy way: Git" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:9 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:72 +msgid "The proper way: Monotone" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:11 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:138 +msgid "Building I2P" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:12 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:159 +msgid "Development ideas" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:13 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:167 +msgid "Making the results available" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:14 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:188 +msgid "Get to know us!" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:15 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:194 +msgid "Translations" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:16 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:200 +msgid "Tools" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:21 +msgid "" +"\n" +"So you want to start work on I2P? Great!\n" +"Here's a quick guide to getting started\n" +"on contributing to the website or the software, doing development or " +"creating translations." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:26 +#, python-format +msgid "" +"\n" +"Not quite ready for coding?\n" +"Try getting involved first." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:33 +msgid "" +"Basic development on the I2P router or the embedded applications uses " +"Java as the main development language.\n" +"If you don't have experience with Java, you can always have a look at Thinking in Java." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:37 +#, python-format +msgid "" +"Study the how intro,\n" +"the other \"how\" documents,\n" +"the tech intro,\n" +"and associated documents.\n" +"These will give you a good overview of how I2P is structured and what " +"different things it does." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:47 +msgid "" +"For development on the I2P router or the embedded applications,\n" +"there are two ways to get the source code:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:54 +#, python-format +msgid "Install Git." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:57 +#, python-format +msgid "Get the code from the GitHub mirror:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:64 +#: i2p2www/pages/site/get-involved/guides/new-developers.html:122 +msgid "Remarks" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:65 +#, python-format +msgid "" +"The Git repository is currently a read-only mirror. If you wish to use it" +" for\n" +"development, you will need to submit patches to our " +"issue\n" +"tracker. We can accept GitHub pull requests, but they must be " +"processed\n" +"manually by turning them into patches anyway." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:74 +msgid "" +"Install monotone.\n" +"Monotone is a version control system.\n" +"We use it because it allows us to keep track of who does what changes to " +"the source code (and for a lot of complicated things, but 'keeping track " +"of changes' is the basic idea)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:79 +msgid "" +"Skim over the monotone tutorial," +" to make sure you understand the concepts." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:83 +msgid "" +"If you want to remain anonymous, you need to do an additional step, to " +"set up a connection to a monotone server over I2P:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:86 +#, python-format +msgid "" +"Enable the i2ptunnel client tunnel on port " +"8998 pointing to mtn.i2p2.i2p." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:90 +msgid "" +"Pick a directory where you want to put all your I2P files, and create a " +"monotone database:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:93 +msgid "" +"Define the trust list by creating ~/.monotone/monotonerc (or" +" _MTN/monotonerc in the i2p.i2p workspace) with the " +"following contents:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:98 +#, python-format +msgid "" +"Copy and paste the developer's commit keys " +"into a new file (e.g. keys.txt) in the same directory\n" +" that i2p.mtn is in. Import the keys into your database " +"with 
      mtn -d i2p.mtn read < keys.txt
" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:102 +msgid "" +"Pull the I2P sources to your machine. This may take a long time, " +"especially if you are doing this over I2P!" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:104 +msgid "Anonymously:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:107 +msgid "Non-anonymously:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:109 +msgid "" +"Alternatively, instead of 'mtn.i2p2.de', you can also download from mtn" +".i2p-projekt.de." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:116 +msgid "" +"All the sources are now present on your machine, in the database file. To" +" make them available in a directory, you need to check them out:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:118 +msgid "" +"The above command creates a directory i2p.i2p, which contains all of the " +"I2P sources." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:123 +msgid "" +"\n" +"To download the website files instead of the I2P source files, use " +"'i2p.www' instead of 'i2p.i2p'." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:126 +msgid "" +"The initial pull may take several hours using the tunnel.\n" +"If it fails after a partial pull, simply rerun it, it will start where it" +" left off.\n" +"If you are in a hurry, use the non-anonymous access." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:131 +#, python-format +msgid "" +"A full list of branches, including i2p.i2p and i2p.www can be found on viewmtn." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:134 +#, python-format +msgid "" +"A long explanation about using monotone is available on the monotone page." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:140 +#, python-format +msgid "" +"To compile the code, you need the Sun Java Development Kit 6 or higher, " +"or equivalent JDK\n" +"(Sun JDK 6 strongly recommended) and\n" +"Apache ant\n" +"version 1.7.0 or higher.\n" +"If you go are working on the main I2P code, you can go into the i2p.i2p " +"directory and run 'ant' to see the build options." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:148 +msgid "" +"To build or work on console translations, you need\n" +"the xgettext, msgfmt, and msgmerge tools from the\n" +"GNU gettext package." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:154 +#, python-format +msgid "" +"For development on new applications,\n" +"see the application development guide." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:160 +#, python-format +msgid "" +"See zzz's TODO lists,\n" +"this website's TODO list or\n" +"Trac\n" +"for ideas." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:169 +#, python-format +msgid "" +"See the bottom of the licenses page " +"for\n" +"commit privilege requirements. You need these to put code into i2p.i2p " +"(not required for the website!)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:174 +msgid "Short version of how to generate and use keys if you plan to commit:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:176 +msgid "use an empty passphrase" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:177 +msgid "enter a passphrase" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:178 +#, python-format +msgid "" +"send this to a mtn repo operator to get " +"push privileges" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:179 +#, python-format +msgid "" +"send this to a release manager to get " +"commit privileges - not required for website" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:180 +msgid "check in with this key" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:181 +msgid "push with this key" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:183 +#, python-format +msgid "Long version: see the monotone page." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:189 +#, python-format +msgid "" +"The developers hang around on IRC. They can be reached on the Freenode " +"network, OFTC, and on the I2P internal networks. The usual place to look " +"is #i2p-dev. Join the channel and say hi!\n" +"We also have additional guidelines for regular" +" developers." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:195 +#, python-format +msgid "" +"Website and router console translators: See the New Translator's Guide\n" +"for next steps." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:201 +msgid "" +"I2P is open source software that is mostly developed using open sourced\n" +"toolkits. The I2P project recently acquired a license for the YourKit " +"Java\n" +"Profiler. Open source projects are eligible to receive a free license " +"provided\n" +"that YourKit is referenced on the project web site. Please get in touch " +"if you\n" +"are interested in profiling the I2P codebase." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-developers.html:209 +#, python-format +msgid "" +"YourKit is kindly supporting open source projects with its full-featured " +"Java Profiler.\n" +"YourKit, LLC is the creator of innovative and intelligent tools for " +"profiling\n" +"Java and .NET applications. Take a look at YourKit's leading software " +"products:\n" +"YourKit Java Profiler and\n" +"YourKit .NET Profiler." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:2 +msgid "New Translator's Guide" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:4 +msgid "Here's a very quick guide to getting started." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:6 +msgid "How to Translate the Website" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:8 +#, python-format +msgid "" +"Translation of the website is done with .po files. The easiest way by far" +" to\n" +"translate the website is to sign up for an account at \n" +"Transifex and request to join a translation" +" team. \n" +"Alternatively it can be done \"the old way\" as outlined below." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:17 +#: i2p2www/pages/site/get-involved/guides/new-translators.html:82 +msgid "Preparation" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:19 +#: i2p2www/pages/site/get-involved/guides/new-translators.html:84 +#, python-format +msgid "" +"Come to #i2p-dev on irc and talk to people.\n" +"Claim the language -\n" +"To make sure other coworkers don't bump onto the files you are working " +"on,\n" +"please update the translation status on this wiki " +"page." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:25 +#, python-format +msgid "" +"Follow the new developer's guide,\n" +"Including the installation of monotone,\n" +"checking out i2p.www branch, and generate your own monotone keys.\n" +"It is not required that you sign a dev agreement." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:33 +msgid "" +"Create files:\n" +"If the file for your language does not exist yet:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:38 +msgid "" +"Run \"./extract-messages.sh\" to generate a " +"messages.pot in the base directory.\n" +"Edit the header of this file, then run \"./init-new-po.sh " +"locale\" to generate the file\n" +"i2p2www/translations/locale/LC_MESSAGES/messages.po. " +"\"mtn add\" this file." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:43 +msgid "" +"Edit i2p2www/pages/global/lang.html and add a line for your " +"language (copy an existing line)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:46 +msgid "" +"Add a flag image file to i2p2www/static/images/flags/ for " +"the menu (copy from the router)." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:52 +msgid "" +"Edit files:\n" +"Edit i2p2www/translations/locale/LC_MESSAGES/messages.po.\n" +"To work with .po files efficiently, you may wish to use POEdit" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:58 +#: i2p2www/pages/site/get-involved/guides/new-translators.html:151 +msgid "" +"Check in:\n" +"\"mtn pull\", \"mtn update\". Then check in by " +"\"mtn ci -k yourname@mail.i2p file1 file2 ...\"\n" +"This collects the diff info of your changed file into your local repo. " +"Then \"mtn sync mtn.i2p2.de -k yourname-transport@mail.i2p " +"i2p.i2p\".\n" +"This synchronizes your local repo with the repo on the target machine." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:65 +#: i2p2www/pages/site/get-involved/guides/new-translators.html:158 +msgid "Repeat. Check in often. Don't wait until it is perfect." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:72 +msgid "How to Translate the Router Console" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:74 +#, python-format +msgid "" +"The easiest way by far to translate the router console is to sign up for " +"an account at \n" +"Transifex and request to join a translation" +" team. \n" +"Alternatively it can be done \"the old way\" as outlined below." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:90 +#, python-format +msgid "" +"Follow the new developer's guide,\n" +"including the installation of monotone and the gettext tools,\n" +"checking out i2p.i2p branch, and generate your own monotone keys." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:95 +msgid "Generate your own gpg key and sign the dev agreement." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:101 +msgid "" +"Before starting a console translation, better help translate some i2p " +"webpages first.\n" +"At least an i2p homepage in your language would be great." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:106 +msgid "" +"What to translate:\n" +"There are about 15 files in the i2p.i2p branch that needs translation:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:132 +msgid "" +"Where xx is your language code like fr/de/ch/zh/...\n" +"There may be or may not be files with your lang code. If not, you can " +"create your own. by copying and renaming other language files you know " +"with your own lang code." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:137 +msgid "" +"Create files:\n" +"If the file for your language does not exist yet, copy another language " +"file to a new file foo_xx.bar for your language.\n" +"Then \"mtn add\" the file.\n" +"After creating a .po file, edit the headers. Then run \"ant " +"distclean poupdate\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:144 +msgid "" +"Start to work:\n" +"Edit the HTML files with any text editor.\n" +"Be sure not to use an editor in HTML mode that reformats everything.\n" +"To work with .po files efficiently, you may wish to use POEdit" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:163 +msgid "" +"As you can see, it's not that difficult.\n" +"If you have questions about the meaning of the terms in the console, ask " +"in #i2p-dev on IRC." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:169 +msgid "FAQ" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:171 +msgid "" +"Q: Why do I have to install monotone, Java, jsp, learn about .po files " +"and html, etc.? Why can't I just do a translation and email it to you?" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:175 +msgid "A: Several reasons:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:178 +#, python-format +msgid "" +"You might be interested in translating via Transifex. Request to join a " +"translation team here." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:182 +msgid "" +"We don't have anybody who has time to accept manual contributions and " +"submit them to our source control system on your behalf. Even if we did, " +"it doesn't scale." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:186 +msgid "" +"Maybe you are thinking translation is a one-step process. It isn't. You " +"can't do it all at once. You will make mistakes. You need to test it and " +"tweak it to make it look right before you submit it. Developers " +"will update or add to the English text, thus requiring a translation " +"update." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:190 +msgid "" +"Having translators use a source control system directly provides " +"authentication and accountablility - we know who is doing what, and we " +"can track changes, and revert them if necessary." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:194 +msgid "" +".po files are not difficult. If you don't want to work directly with " +"them, we recommend 'poedit'." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:198 +msgid "" +"HTML files are not difficult. Just ignore the html stuff and translate " +"the text." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:202 +msgid "" +"Installing and using monotone is not that difficult. Several of the " +"translators and other contributors to I2P are non-programmers, and they " +"use monotone regularly. Monotone is simply a source control system, it is" +" not about \"coding\"." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:206 +msgid "" +"Our items to translate are not \"documents\". They are html files and po " +"files, with a specific format and character encoding (UTF-8) that must be" +" maintained, and not corrupted by email programs or other methods of " +"transfer." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:210 +msgid "" +"We looked at 'pootle' as a front-end for translators. It didn't work " +"well, needed an administrator, and a pootle-based process would suffer " +"from a number of the above flaws." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:215 +msgid "" +"In summary:\n" +"Yes, we know it is somewhat of a hurdle to get started. It's really the " +"only possible way we can do it. Give it a try, it really isn't that hard." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:220 +msgid "More Information" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/new-translators.html:221 +#, python-format +msgid "" +"The #i2p-dev channel on IRC, or the translation forum on %(zzz)s." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:2 +msgid "How to Set up a Reseed Server" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:3 +msgid "February 2016" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:6 +msgid "Overview" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:8 +msgid "" +"Thank you for volunteering to run an I2P reseed server.\n" +"\"Reseeding\" is our term for bootstrapping new routers into the network." +"\n" +"New routers fetch a bundle of peer references, or \"router infos\", from " +"one or more of a hardcoded list of HTTPS URLs." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:14 +msgid "Requirements" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:16 +msgid "" +"At its simplest, a reseed server consists of a Java I2P router, an HTTPS " +"web server,\n" +"and some scripts that periodically gather router infos from the router,\n" +"bundle and sign them into a custom file format, and deliver these files " +"over HTTPS.\n" +"In practice, it's a bit more complex, and a reseed operator must be " +"fairly competent and attentive.\n" +"A reseed server is not appropriate for a residential internet connection." +" The complexities include:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:25 +msgid "" +"You must have a secure SSL setup with either a self-signed certificate or" +" a cert that chains up to a standard CA" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:28 +msgid "" +"The SSL configuration must conform to current best practices on allowed " +"ciphers and protocols, and the CN/SAN host name must match the URL" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:31 +msgid "" +"The scripts are designed to deliver different router info bundles to " +"different requestors for network diversity" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:34 +msgid "" +"The scripts are designed to deliver the same bundle to the same repeated " +"requestor to prevent scraping" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:37 +msgid "" +"The reseed servers are under periodic attacks and DDoS attempts, and from" +" other buggy I2P implementations and botnets.\n" +"This necessitates that you run fail2ban or an equivalent solution." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:43 +msgid "Information Required" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:45 +msgid "" +"When your setup is complete and ready for testing, we will need the HTTPS" +" URL,\n" +"the SSL public key certificate, and the \"su3\" bundle public key.\n" +"After testing is complete, these will be added to the hardcoded entries " +"in the Java and C++ routers in the next release,\n" +"and you will start seeing traffic.\n" +"We also will need your email address so we may continue to contact you " +"about reseed administration issues.\n" +"The email will not be made public but will be known to the other reseed " +"operators.\n" +"You should expect that your nick or name and its association with that " +"URL or IP will become public." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:55 +msgid "Privacy Policy" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:57 +msgid "" +"A reseed operator is a trusted role in the network.\n" +"While we do not yet have a formal privacy policy, you must ensure the " +"privacy of our users\n" +"by not publicizing logs or IPs found in those logs, except as necessary " +"to discuss administration issues with the I2P reseed team." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:63 +msgid "Financial Support" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:65 +msgid "" +"Modest financial support may be available to those running reseed " +"servers.\n" +"This support would be in partial reimbursement for your server costs.\n" +"Support will not be paid in advance and will probably not cover all your " +"expenses.\n" +"Support is only available to those who have been running reseed servers " +"in good standing for several months, and is based on actual need." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:72 +msgid "" +"If you would like to discuss support, please contact echelon and CC: " +"backup." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:77 +msgid "Getting Started" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:79 +msgid "" +"Our reseed coordinator is \"backup\" and he may be contacted at " +"backup@mail.i2p or backup at i2pmail.org.\n" +"Unfortunately, he is not generally on IRC. The reseed setup is somewhat " +"specialized, and you should direct most questions to him." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:84 +msgid "" +"For actual implementation, details below. In summary, there are two " +"solutions we have to offer:" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:89 +msgid "" +"A Go implementation that includes the web server and all the scripts. " +"This is the recommended solution." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:93 +msgid "" +"An older PHP implementation plus some shell scripts. The PHP goes into a " +"web server that you must set up separately." +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:98 +msgid "" +"For further information, read the information at the following links, and" +" then contact backup.\n" +"Thank you!" +msgstr "" + +#: i2p2www/pages/site/get-involved/guides/reseed.html:113 +msgid "Detailed Instructions" +msgstr "" + diff --git a/i2p2www/translations/gl/LC_MESSAGES/misc.po b/i2p2www/translations/gl/LC_MESSAGES/misc.po new file mode 100644 index 00000000..5da75fe7 --- /dev/null +++ b/i2p2www/translations/gl/LC_MESSAGES/misc.po @@ -0,0 +1,1231 @@ +# Galician translations for I2P. +# Copyright (C) 2016 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# Uberius Crypto , 2016 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2016-04-02 00:09+0000\n" +"PO-Revision-Date: 2016-10-17 17:04+0000\n" +"Last-Translator: Uberius Crypto \n" +"Language-Team: Galician (http://www.transifex.com/otf/I2P/language/gl/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 1.3\n" + +#: i2p2www/pages/site/misc/clt.html:2 +msgid "I2P at CLT and PetCon 2009.1" +msgstr "I2P en CLT e PetCon 2009.1" + +#: i2p2www/pages/site/misc/clt.html:4 +msgid "" +"Members of I2P will held a talk at CLT and PetCon 2009.1\n" +"Two members of the I2P team will be at two forthcoming Linux day and " +"security convention." +msgstr "" +"Os membros de I2P darán unha conferencia en CLT e en PetCon 2009.1\n" +"Dous membros do equipo I2P estarán nas dúas seguintes convencións do día " +"de Linux e seguridade." + +#: i2p2www/pages/site/misc/clt.html:9 +#, python-format +msgid "" +"On 14th march of 2009 there will be a short talk about general " +"introduction to I2P at the Chemnitz Linux Tag " +"2009 hold by echelon.\n" +"Echelon and some other members of the I2P family will attend to the Linux" +" meeting the whole two days (Saturday and Sunday) and will be " +"recognizable as I2P family members. Meet them, ask them your questions, " +"show them your props! Show your support!" +msgstr "" + +#: i2p2www/pages/site/misc/clt.html:14 +#, python-format +msgid "" +"Just 10 days later the Privacy and Data Security " +"convention in Dresden will take place.\n" +"Again, echelon will attend this event and hold a short talk about general" +" introduction to I2P. Another talk about the profiling by the I2P clients" +" will be held." +msgstr "" + +#: i2p2www/pages/site/misc/cvs.html:4 +#, python-format +msgid "" +"The I2P sourcecode was kept in a CVS repository. Nowadays it is kept in a" +" Monotone repository.\n" +"For those who aren't very familiar with CVS, there is a\n" +"fantastic book " +"on the\n" +"subject (developers only need to deal with the first chapter - \"An " +"Overview of\n" +"CVS\", as subsequent chapters go into some nasty details very few ever " +"need to\n" +"touch)." +msgstr "" + +#: i2p2www/pages/site/misc/cvs.html:31 +msgid "" +"Humorous quote from WinCVS: \"Did you know... Never experiment with new " +"CVS\n" +"commands on your working repository. Create a sample module instead.\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:2 +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:4 +msgid "I2PTunnel migration" +msgstr "Migración dos túneles I2P" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:6 +msgid "" +"After upgrading to the new architecture, you'll have to do a \n" +"little work to get your old I2PTunnel-driven servers running. \n" +"Lets walk through a simple example. For an eepsite with the \n" +"old clientApp configuration, you had:" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:16 +msgid "To provide that same functionality on the new web architecture:" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:18 +#, python-format +msgid "Jump to %(url)s" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:19 +msgid "Click on Add new: [Server tunnel] \"GO\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:21 +msgid "For the name: \"eepsite\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:22 +msgid "For the description: \"My eepsite, isn't it pretty?\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:23 +msgid ">For the target host:" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:24 +msgid "For the target port:" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:25 +msgid "" +"For the private key file: path to \"myWebPriv.dat\"
\n" +"(it is recommended to copy that .dat to your new install dir)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:29 +msgid "Check the \"Start automatically?\" checkbox" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:30 +msgid "Click \"Save\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:32 +msgid "It will come back saying:" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:39 +msgid "" +"That's it! Creating a new I2PTunnel server works the same way too, " +"except you\n" +"don't need to \"copy the old file\", obviously. Behind the scenes, it is" +" all driven\n" +"by the i2ptunnel.config file, which you may modify " +"externally (if you do,\n" +"hit \"Reload config\" on the I2PTunnel web page, which will tear down all" +" of your \n" +"existing tunnels and rebuild new ones)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-migration.html:47 +msgid "" +"Note that you WILL need to wait until your router is integrated\n" +"into the network before you are able to use the /i2ptunnel/ web\n" +"interface. It will say \"Please be patient\" if you try to \n" +"beforehand, which means that it is still trying to build the \n" +"necessary I2PTunnel sessions it has been configured to create." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:2 +msgid "I2PTunnel services" +msgstr "Servizos do túnel I2P" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:4 +msgid "Below is quick copy of aum's eepsite deployment guide." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:8 +msgid "1. - Deploy a local server" +msgstr "1 - Desprega un servidor local" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:10 +msgid "" +"For simplicity's sake, we will walk through the setup of a web server; " +"however, this procedure is the same regardless what protocol of servers " +"and/or clients you are setting up." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:13 +msgid "" +"I recommend the Tiny Httpd web server, thttpd, (windows version available" +" on site) although you can use anything that you feel comfortable with." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:16 +msgid "" +"Another more robust option would be to use EasyPHP, which is also open " +"source. It comes with PHP, PHPmyadmin, mySQL, and Apache web server. For " +"newbies who have no experience setting up and hosting content over " +"servers, see the hosting page for help." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:19 +msgid "" +"With the web server you've chosen, configure it to listen on a port of " +"your choice, and serve its documents from a directory of your choice. For" +" this example, we'll assume port 10880." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:22 +msgid "" +"Make sure your firewall is set up so that you cannot receive incoming " +"connections on this port (which would breach your anonymity)." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:25 +msgid "" +"Test the webserver, by pointing your normal browser (the one with the " +"\"direct connection\") at http://localhost:10880 (changing the 10880 to the " +"port number you have chosen)." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:28 +msgid "" +"Once your webserver is working, and you can access it locally with your " +"browser, continue to the next step." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:33 +msgid "2 - Generate an I2P Destination Keypair" +msgstr "Xerar un par de chaves de destino I2P" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:35 +msgid "" +"I2P does not deal in IP addresses. To protect your anonymity, it deals in" +" unique addresses called destination keys." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:38 +msgid "" +"A destination key works a lot like a regular IP address, except that it " +"can't be traced to your IP address or physical location. When users place" +" a request to speak with you, your gateways are the ones that answer for " +"you. So the requesting user can only know the IP address of your " +"gateways. However, gateways don't know your IP address, because gateways " +"are the last nodes on your tunnels, and you anonymously create tunnels by" +" way of garlic routing. (So gateways are like puppets that can't see " +"their masters, and everyone communicates through these puppets)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:41 +msgid "" +"To deploy a server on I2P, you create a destination keypair. You use the " +"private key to authenticate your server when connecting it to I2P, and " +"you make the public key (aka destination key) known publicly, so others " +"can connect to your server. (indirectly, through your gateways)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:44 +msgid "Each service you run on I2P requires a different keypair." +msgstr "Cada servizo que lances en I2P require un par de chaves diferente." + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:47 +msgid "" +"To generate your keypair, type the command: java -jar " +"lib/i2ptunnel.jar -nogui -e \"genkeys myWebPrivKey.dat " +"myWebPubKey.dat\" (all on one line)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:50 +msgid "" +"In windows, to generate your keypair, type the command: java -jar " +"lib/i2ptunnel.jar -nogui -e \"genkeys myWebPrivKey.dat " +"myWebPubKey.dat\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:53 +msgid "" +"The filenames myWebPrivKey.dat and " +"myWebPubKey.dat are arbitrary - choose whatever you want " +"here, as long as you understand your own choices." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:56 +msgid "" +"We now need to export your public key into base64 format, which you will " +"share with others." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:59 +msgid "" +"To convert your myWebPubKey.dat file into shareable base64, type the " +"command java -cp lib/i2p.jar net.i2p.data.Base64 encode " +"myWebPubKey.dat > myWebPubKey.txt (all on one line)." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:62 +msgid "" +"This file you have just generated, myWebPubKey.txt, contains" +" a long base64 string (516 chars at last count), which we call a " +"destination key. All you need to know about this string for now is that " +"it allows remote clients to uniquely pinpoint and connect to your server," +" just the same way as an IP address allows remote machines to pinpoint " +"and connect to your machine." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:65 +msgid "" +"However, in contrast to an IP address, there is no way to trace your " +"machine's physical location - even though your server can be addressed " +"via I2P, your IP address cannot be traced or associated with this " +"destination key." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:70 +msgid "3 - Open a 'Tunnel' from I2P To Your Server" +msgstr "3 - Abre un 'Túnel' dende I2p ó teu servidor" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:72 +msgid "" +"For clients elsewhere in I2P to be able to access your server, you must " +"run a 'bridge' or 'tunnel', which takes connections from these clients " +"and forwards them to your local server." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:75 +msgid "" +"To activate such a tunnel, type the command java -jar " +"lib/i2ptunnel.jar -nogui -e \"server localhost 10880 " +"myWebPrivKey.dat\" (all one line)." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:78 +msgid "" +"If you used different filenames or port number earlier on, change these " +"accordingly" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:81 +msgid "" +"Windows users, remember to replace apostrophes with double quotes. Thus: " +"java -jar lib/i2ptunnel.jar -nogui -e \"server localhost 10880 " +"myWebPrivKey.dat\"" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:84 +msgid "" +"Within a few seconds, the 'tunnel' should now be active, and remote " +"clients should be able to reach your server anonymously. Remember to let " +"your router \"warm up\" before opening clients to it." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:89 +msgid "4 - Update Your hosts.txt File " +msgstr "4 - Actualiza o teu arquivo hosts.txt" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:91 +msgid "" +"To test your own server locally, you'll need to create an entry in your " +"hosts.txt file, so I2P can translate the simple URL you place in the " +"browser's address bar into the full public key text needed to find your " +"server." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:94 +msgid "" +"Edit your hosts.txt, and add the line myserver.i2p=blahblahblah, where " +"myserver.i2p is an I2P 'domain' you want to associate with your site, and" +" the blahblahblah is the text of the base64 public key you created " +"earlier in the file myWebPubKey.txt" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:97 +msgid "" +"With this in place, you and others can reach your server with the simple " +"domain name myserver.i2p in the browser's address bar." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:102 +msgid "5 - Surf Your Site Within I2P" +msgstr "5 - Navega polo teu sitio dentro de I2P" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:104 +msgid "" +"Using your secondary browser - the one you earlier configured to use " +"localhost:4444 as a proxy - point this browser to the address http://myserver.i2p" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:107 +msgid "You should see the main page of your webserver come up." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:112 +msgid "6 - Create a Local Client Tunnel Connection " +msgstr "6 - Crea unha conexión de túnel local" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:114 +msgid "We now have to think beyond just web servers." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:117 +msgid "" +"As you grow into I2P and get more of a 'feel' for it, you will want to " +"use all manner of servers and clients." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:120 +msgid "" +"The beauty of I2P is that it allows standard Internet clients and servers" +" for most protocols to be transparently 'tunneled' through the anonymous " +"network." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:123 +msgid "" +"You can run mailservers/clients, nameservers/clients, newsservers/clients" +" - almost anything at all - perhaps even FTP in passive mode." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:126 +msgid "" +"Now, we'll create a client tunnel. This is like the server tunnel we " +"created earlier, but works in reverse. It listens to a port on your local" +" machine; your local client connects to this port; the connection gets " +"forwarded through I2P to the service on the other end." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:129 +msgid "" +"To open your client tunnel for your server, type the command java " +"-jar lib/i2ptunnel.jar -nogui -e \"config localhost 7654\" -e \"client " +"10888 textofbase64key\" (all one line)." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:132 +msgid "" +"The port 10888 is arbitrary - it just needs to be something other than " +"the physical port your server is listening on." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:135 +msgid "" +"textofbase64key is simply the contents of the public key text file " +"myWebPubKey.txt, reproduced fully on one line (alternately, instead of " +"textofbase64key, you can specify the name from your hosts.txt - e.g. " +"myserver.i2p)" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:138 +msgid "" +"Within a minute or two of launching this command, the client tunnel from " +"your local machine into I2P will be open and ready for use." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:141 +msgid "" +"Point your regular web browser (ie, not the one you configured to use " +"localhost:4444), and point it to http://localhost:10888" +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:144 +msgid "" +"Verify that the main page of your server eventually comes up in your " +"browser." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:147 +msgid "" +"You use the same procedure for using any local client program to access a" +" remote I2P server - just get the base64 public key (called destination " +"key) of the remote server, choose a local port to connect to the remote " +"server, open the tunnel, and just connect with your client to your " +"heart's content." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:152 +msgid "7 - Share your server details with others" +msgstr "7 - Comparte os detalles do teu servidor con outros/as" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:154 +msgid "" +"Using an anonymous medium (eg the one of the I2P IRC servers or ugha's " +"wiki), post your domain name (eg www.mynick.i2p as well as your destination key. " +"Others will then be able to reach your server remotely, without either of" +" you jeopardizing your anonymity." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:157 +msgid "" +"Remember, you can go to What's on I2P and find the latest public keys " +"linked to their URL. You should also post your own public key and URL " +"their. However, you will want to do this anonymously, of course. " +"Drupal.i2p.net is currently, as of this writing, only accessible from the" +" net. So, to access the outside WWW anonymously from inside of I2P, you " +"will need to start up your script called startSquid. Do it the same way " +"you have been doing these other scripts. Reconfigure your browser to " +"proxy on localhost:5555, as defined in the script, and when the script " +"has generated it's keys, you can access the squid proxy. Put any WWW URL " +"(such as Google or this i2p site) into your browser's address bar and you" +" will be surfing the World Wide Web anonymously. Now you can safely post " +"your public key, and no one can detect your IP address." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:162 +msgid "8 - Write Some Scripts To Handle All This Menial Nonsense" +msgstr "8 - Escribe algún script para manexar todas istas parvadas" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:164 +msgid "" +"It would drive most people crazy, going through all these steps every " +"time one sets up an I2P server, and/or deploys a client." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:167 +msgid "" +"Aum's website http://www.freenet.org.nz/i2p/ has a script called " +"setupServer.py which automates all this nonsense into one simple command " +"line . But I respect that people's tastes in user interfaces differ, and " +"trying to write something which satisfies everyone's needs usually " +"results in something so complex that it turns into newbie-repellent." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:170 +msgid "" +"So please feel free to use and/or customize setupServer.py to taste, or " +"write your own in Python or another language." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:173 +msgid "" +"Also, you may want to write a script which handles the startup of the I2P" +" Router, the eepProxy, plus any and all tunnels you are using. I've got " +"such a script called startEverything.sh, which gets launched at system " +"startup. (Be sure to search this site for template scripts to automate " +"your I2P commands. If I create a page for one, I'll try to remember to " +"link it here." +msgstr "" + +#: i2p2www/pages/site/misc/i2ptunnel-services.html:176 +msgid "Exercise for Windows users - port setupServer.py into a MS-DOS .BAT file." +msgstr "" + +#: i2p2www/pages/site/misc/invisiblenet.html:2 +msgid "Old Documents" +msgstr "Documentos antigos" + +#: i2p2www/pages/site/misc/invisiblenet.html:5 +msgid "" +"Following is a list of documents originally on www.invisiblenet.net/i2p/ " +"and\n" +"rescued via the\n" +"Wayback Machine.\n" +"They are quite dated and may or may not be accurate.\n" +"However, the I2CP and I2NP documents in particular have some good " +"information." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:3 +msgid "August 2011" +msgstr "Agosto de 2011" + +#: i2p2www/pages/site/misc/jbigi.html:6 +msgid "Overview" +msgstr "Vista Xeral" + +#: i2p2www/pages/site/misc/jbigi.html:7 +msgid "" +"Using JNI (Java Native Interface), a bit of C code (thanks ugha!), a " +"little\n" +"manual work and a piece of chewing gum we have made several\n" +"cryptography operations quite a bit faster." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:13 +#, python-format +msgid "" +"The speedup comes from the super-fast\n" +"GNU MP Bignum library (libgmp).\n" +"We use a single function from libgmp -\n" +"mpz_powm()\n" +"as a replacement for the\n" +"Java Math library's BigInteger modPow().\n" +"As modPow() is a significant computational portion of many crypto " +"operations, this is of significant benefit." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:25 +#, python-format +msgid "" +"The standard I2P installation includes about 20 versions of the library " +"for different platforms,\n" +"each about 50KB, inside the jbigi.jar file.\n" +"The initialization of the JBigI library, including CPU identification, " +"selection, and extraction\n" +"of the correct loadable module, is handled by the\n" +"NativeBigInteger class.\n" +"If no module is available for the current platform, the standard\n" +"Java Math library's BigInteger modPow()\n" +"is used." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:38 +msgid "Rebuilding and Testing JBigI" +msgstr "Reconstruindo e probando JBigI" + +#: i2p2www/pages/site/misc/jbigi.html:39 +msgid "" +"Following are the instructions to build a new jbigi library for your own " +"platform\n" +"and testing its performance." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:42 +msgid "Requirements" +msgstr "Requerimentos" + +#: i2p2www/pages/site/misc/jbigi.html:43 +msgid "" +"This works on Linux, and with a few changes in build.sh probably also on\n" +"other platforms. FreeBSD has also been reported to work too. On Kaffee " +"the\n" +"speedup is very small, because it already uses native BitInteger " +"internally.\n" +"Blackdown seems to cause strange errors. Because you are going to do\n" +"compilation, you need JDK; JRE won't work." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:50 +msgid "" +"The required code is available in monotone database and the latest source" +" tarball. " +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:51 +msgid "" +"The GNU MP Bignum library (libgmp) needs to be installed, if it isn't\n" +"included in your OS / distribution or installed already, it can be " +"received from\n" +"http://gmplib.org/#DOWNLOAD. " +"Even if you\n" +"have already installed it as binary, it might still be worth a try to " +"compile\n" +"GMP yourself, since then it will be able to use the specific instructions" +" of\n" +"your processor. The latest GMP may also\n" +"be used instead of GMP 5.0.2, but it hasn't been tested by us." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:61 +msgid "Step-by-step instructions" +msgstr "Instruccións paso a paso" + +#: i2p2www/pages/site/misc/jbigi.html:63 +msgid "" +"Look at your running " +"environment on the logs.jsp page.\n" +"There should be one of two status messages for JBigI - either" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:66 +msgid "Locally optimized native BigInteger loaded from the library path" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:68 +msgid "or" +msgstr "ou" + +#: i2p2www/pages/site/misc/jbigi.html:70 +msgid "Native BigInteger library jbigi not loaded - using pure java" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:71 +msgid "" +"If the native BitInteger library was NOT loaded, you definitely need to\n" +"compile your own.\n" +"Certain platforms, such as OS X, OpenSolaris, and 64-bit systems,\n" +"may require you to compile your own library.\n" +"If the BigInteger library was loaded, do at least the next step to see\n" +"what your performance is." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:78 +msgid "" +"Look on http://localhost:7657/stats.jsp" +"\n" +"to see what the lifetime average values for " +"crypto.elGamal.decrypt and\n" +"crypto.elGamal.encrypt are. The numbers are times in " +"milliseconds. Copy these somewhere so you can compare\n" +"them later on.\n" +"The network average for encrypt time is about 20ms.\n" +"If your encrypt time is less than 50ms for a relatively new processor, or" +" less than 100ms\n" +"for an older processor, and the native BigInteger library was loaded, you" +" are probably fine." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:87 +#, python-format +msgid "" +"Get the latest released source code of I2P from\n" +"the download page, or get the cutting-edge " +"source\n" +"out of the monotone database mtn.i2p2.de" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:92 +msgid "Inside the source tree change directory to: core/c/jbigi" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:93 +msgid "" +"Read the README file.\n" +"If you have a /usr/lib/libgmp.so file, you do not have to download GMP.\n" +"Use the 'dynamic' argument to build.sh.\n" +"Otherwise, you must download GMP version 5.0.2 from\n" +"from http://gmplib.org/#DOWNLOAD, " +"saving it to gmp-5.0.2.tar.bz2.\n" +"If you decide to use a newer version, change the VER= line in " +"core/c/jbigi/build.sh." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:101 +msgid "" +"Take a look at build.sh, if your JAVA_HOME\n" +"environment variable is set and you are using Linux then it might just " +"work.\n" +"Otherwise change the settings. Remember, you need the Java SDK installed." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:106 +msgid "" +"Run build.sh (if you downloaded GMP) or\n" +"build.sh dynamic (if you have /usr/lib/libgmp.so).
\n" +"Maybe the build spewed out some errors of missing jni.h and jni_md.h " +"files.\n" +"Either copy these files from your java install into the " +"core/c/jbigi/jbigi/include/ directory,\n" +"or fix $JAVA_HOME.
\n" +"You can run the build.sh from the core/c/ " +"directory which will\n" +"build all available jbigi libs into a jbigi.jar.
\n" +"A file named libjbigi.so should be created in the current\n" +"directory. If this doesn't happen and/or you get errors then please " +"report\n" +"them." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:118 +msgid "" +"Follow the instructions in core/c/README to install the library and run\n" +"the speed test.\n" +"Read the final lines of the speed test's output for some additional\n" +"info, it will be something like this:" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:128 +msgid "" +"If the native is indeed 5-7x faster (or more) then it looks all good. If " +"not, please report." +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:129 +msgid "Copy libjbigi.so to your i2p directory" +msgstr "" + +#: i2p2www/pages/site/misc/jbigi.html:130 +msgid "Restart your I2P programs." +msgstr "Reinicia os teus programas de I2P" + +#: i2p2www/pages/site/misc/jbigi.html:131 +msgid "" +"On http://localhost:7657/stats.jsp" +"\n" +"the crypto.elGamal.decrypt and " +"crypto.elGamal.encrypt\n" +"should be a lot faster." +msgstr "" + +#: i2p2www/pages/site/misc/jrandom-awol.html:2 +msgid "Jrandom's Announcement" +msgstr "" + +#: i2p2www/pages/site/misc/jrandom-awol.html:4 +msgid "" +"The following message was received in mid-November 2007. We have no " +"further information\n" +"on jrandom's status." +msgstr "" + +#: i2p2www/pages/site/misc/jrandom-awol.html:9 +#, python-format +msgid "" +"Subsequently, in an unrelated incident, the hosting company for\n" +"all *.i2p.net servers (except forum.i2p.net) suffered a power outage\n" +"on January 13, 2008, and the i2p.net servers did not fully return to " +"service.\n" +"As only jrandom has the credentials required to restore service,\n" +"and he could not be contacted,\n" +"we moved all public services to www.i2p2.de\n" +"and related subdomains." +msgstr "" + +#: i2p2www/pages/site/misc/jrandom-awol.html:19 +#, python-format +msgid "" +"Approximately two months later, for unrelated reasons,\n" +"forum.i2p.net was moved to %(forum)s." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:2 +#: i2p2www/pages/site/misc/manual-wrapper.html:4 +msgid "Manually Installing the Java Wrapper" +msgstr "A instalar manualmente o Java Wrapper" + +#: i2p2www/pages/site/misc/manual-wrapper.html:6 +#, python-format +msgid "" +"The installation package for the I2P router" +" comes\n" +"with a Java wrapper for the most common architectures. If your system is " +"not\n" +"supported by our installer—or if you want to update the wrapper to " +"a\n" +"newer version—the following steps describe installing the wrapper " +"manually." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:14 +msgid "" +"Check Tanuki Software's download" +" page\n" +"for your platform. Is your platform listed? If so, you're in\n" +"luck! Download the most recent version of the Community Edition for your " +"OS and\n" +"CPU and move to the next step." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:20 +msgid "" +"If your platform does not have an already compiled wrapper available, you" +"\n" +"may be able to compile it yourself. If you are willing to have a go at " +"it, move\n" +"on to compiling the wrapper for your system." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:27 +msgid "Using existing binaries" +msgstr "A usar binarios existentes" + +#: i2p2www/pages/site/misc/manual-wrapper.html:28 +msgid "In the steps below, $I2P means the location I2P was installed to." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:36 +#: i2p2www/pages/site/misc/manual-wrapper.html:64 +msgid "Try to start I2P using $I2P/i2prouter start" +msgstr "Intenta arrincar I2P usando $I2P/i2prouter start" + +#: i2p2www/pages/site/misc/manual-wrapper.html:37 +#: i2p2www/pages/site/misc/manual-wrapper.html:65 +msgid "tail -f /tmp/wrapper.log and look for any problems." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:39 +#: i2p2www/pages/site/misc/manual-wrapper.html:67 +msgid "" +"If this did not work you'll need to use runplain.sh to start" +" I2P." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:43 +msgid "Compiling from source" +msgstr "A compilar dende o código fonte" + +#: i2p2www/pages/site/misc/manual-wrapper.html:44 +msgid "" +"These steps worked to compile the wrapper for use on a mipsel system " +"running Debian. The steps will need to be altered for " +"your system." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:48 +msgid "" +"Download the source archive for the community version of the wrapper from" +" wrapper download" +" page." +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:49 +msgid "Extract the tarball" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:51 +msgid "" +"Set environment variables ANT_HOME and " +"JAVA_HOME. For example, in Debian:" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:54 +msgid "" +"Since there isn't a Makefile for Mipsel, we'll make a copy of an already " +"existing makefile:" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:56 +msgid "Now we can attempt to compile the wrapper:" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:57 +msgid "use ./build64.sh if you have a 64bit CPU and JVM" +msgstr "" + +#: i2p2www/pages/site/misc/manual-wrapper.html:58 +msgid "Copy the wrapper into its proper place:" +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:4 +msgid "" +"Here's an outline and rationale for a minimal WWW proxy app for use over " +"I2P." +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:8 +msgid "" +"HTTP operation over I2P using I2PTunnel. When the base SocketLibrary\n" +"is out, the only significant difference will be the 'wrapRequest' and\n" +"'unwrapRequest' will functionally be placed in the socketLibrary, not\n" +"in the router (but later versions of the SocketLibrary will be able to\n" +"use selective ACK and large window sizes, allowing more ACKs to be\n" +"skipped)" +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:47 +msgid "" +"An optimized form, designed to handle only 128KB [1] files and pages, can" +"\n" +"operate significantly faster:" +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:71 +msgid "" +"The difference in network load and latency is significant - this is\n" +"essentially a UDP version of HTTP. On the normal web, we can't really do" +" that,\n" +"since most HTTP requests and responses are orders of magnitude larger " +"than UDP\n" +"packets functionally support, but in I2P, messages can be large. The " +"savings\n" +"for the network load comes from the fact that we don't need to send any " +"ACK\n" +"messages - rather than the earlier wrap/unwrap request (that bundles a\n" +"DataMessage with a DeliveryStatusMessage to provide guaranteed delivery)," +" the\n" +"MinWWW proxy deals with resends (if necessary - in I2PTunnel today, there" +" are no\n" +"resends)." +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:83 +msgid "" +"The data that the MinWWW proxy and server need to wrap is trivial - when " +"the\n" +"proxy wants to send \"GET /\", it prepends it with the I2P Destination " +"sending\n" +"the request, followed by a 4 byte request ID. The MinWWW server receives" +" those\n" +"requests, contacts the appropriate HTTPD, sends the request, waits for " +"the\n" +"response, and sends a reply to the MinWWW proxy containing the response,\n" +"prefixed with the original request ID. That response is taken and passed" +" back\n" +"to the browser and the connection is closed." +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:93 +msgid "" +"In addition, the MinWWW proxy can choose the MinWWW server to use from a\n" +"list, going through some round robin or other algorithm, so that there " +"are\n" +"multiple outproxies merged transparently. The bandwidth required for " +"running\n" +"one of these outproxies is also greatly reduced, since it will only " +"handle 128KB\n" +"files (aka no one is going to be downloading porn, warez, etc)." +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:101 +msgid "" +"The functionality /is/ limited, but 128KB of data is a lot for a single " +"HTTP\n" +"request or response. The above diagrams are also unrealistic in their " +"hops -\n" +"ROUTERA will really never talk directly to ROUTERB. ROUTERA will send " +"each\n" +"of the messages through two additional outbound routers, then forwarded " +"to\n" +"two additional inbound routers to ROUTERB, so the lag there is " +"significant -\n" +"while the above only saves 11 steps, 8 of those steps need to traverse " +"the\n" +"entire tunnel path (4+ remote hops each time when tunnels are 2 remote " +"hops\n" +"in each stretch), leaving MinWWW with only two full traversals (one for " +"the\n" +"request, one for the response), instead of 10." +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:113 +msgid "" +"Implementing the MinWWW proxy and server should be fairly easy - read an " +"HTTP\n" +"request from the client fully (perhaps only start out with HTTP GET, " +"leaving\n" +"HTTP POST for later), wrap the message, and wait for the response. The " +"server\n" +"in turn simply needs to parse the request to either open a socket or URL," +"\n" +"send the request, wait for the response, and send it back through the " +"network.\n" +"If someone were to implement this, it would be Good :)" +msgstr "" + +#: i2p2www/pages/site/misc/minwww.html:122 +msgid "" +"[1] Why 128KB files? Currently I2CP allows functionally arbitrary " +"message\n" +"size, but that's going to be going away since it involves either " +"excessive memory\n" +"overhead on intermediary routers, or additional implementation details to" +"\n" +"handle. I2PTunnel is currently limited to 128KB and hasn't been a " +"burden,\n" +"so perhaps it could be increased to 256KB when the I2CP spec is updated)" +msgstr "" + +#: i2p2www/pages/site/misc/myi2p.html:4 +msgid "" +"There has been discussion about a distributed blogging application for a " +"few\n" +"months now called \"MyI2P\". While the original discussions were lost, " +"we were \n" +"able to retrieve a Google cache\n" +"of it. It isn't pretty, but it includes the basic overview and some " +"discussion\n" +"that ensued." +msgstr "" + +#: i2p2www/pages/site/misc/myi2p.html:12 +#, python-format +msgid "" +"The application itself is not yet implemented, and the ideas behind it " +"have \n" +"been made less ambitious over time, but they are still valid and the " +"current \n" +"plan is to have the core MyI2P functionality " +"available \n" +"along side the I2P 1.0 release. That will include a distributed address " +"book\n" +"to enable secure, distributed, and human readable naming by sacrificing " +"the \n" +"need for global uniqueness - basically everyone has their own local " +"address book \n" +"and can 'subscribe' to other people's address books, letting MyI2P " +"periodically\n" +"retrieve new name to destination mappings (leaving conflicts up to the " +"user to\n" +"resolve). In addition to the address book, there will be a distributed " +"blogging\n" +"system using a reduced and secured subset of \n" +"bbcode to " +"essentially\n" +"provide an anonymous LiveJournal with\n" +"a 'friends list' and transparent access control (authenticated by the I2P" +"\n" +"datagrams with rules defined based on the " +"address book)." +msgstr "" + +#: i2p2www/pages/site/misc/myi2p.html:29 +msgid "" +"Additional functionality, such as integration with a DHT backing store or" +" \n" +"swarming file transfers for 'attachments' can be added later. Email may " +"or may\n" +"not get in the first pass either, though its implementation is " +"essentially just\n" +"a blog entry with private access, so perhaps some UI designer can come up" +" with\n" +"something. Exporting the data to RSS or access through ATOM will be an " +"option \n" +"down the road as well." +msgstr "" + +#: i2p2www/pages/site/misc/ratestats.html:2 +#: i2p2www/pages/site/misc/ratestats.html:5 +msgid "RateStat list" +msgstr "Lista RateStat" + +#: i2p2www/pages/site/misc/ratestats.html:6 +msgid "I2P enables the collection of a wide range of rates." +msgstr "" + +#: i2p2www/pages/site/misc/ratestats.html:7 +msgid "" +"The list was gathered using the following command in the top directory of" +" the branch i2p.i2p:" +msgstr "" + +#: i2p2www/pages/site/misc/ratestats.html:10 +msgid "All options aren't needed, but it works." +msgstr "" + +#: i2p2www/pages/site/misc/transition-guide.html:4 +#, python-format +msgid "" +"The I2P sourcecode is kept in several distributed monotone repositories.\n" +"See the\n" +"Monotone website for information\n" +"on monotone.\n" +"See\n" +"this forum post on i2p " +"monotone\n" +"for more information on how to get started and check out the source " +"anonymously.\n" +"There is also a quick-start guide on the\n" +"new developer's page." +msgstr "" + +#: i2p2www/pages/site/misc/transition-guide.html:16 +msgid "" +"If you want to get the source non-anonymously, pull from the public " +"server mtn.welterde.de.\n" +"The i2p source code branch is \"i2p.i2p\"." +msgstr "" + +#: i2p2www/pages/site/misc/transition-guide.html:21 +msgid "Guide" +msgstr "Guía" + +#: i2p2www/pages/site/misc/transition-guide.html:22 +msgid "" +"\n" +"The following is a detailed guide by Complication." +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:2 +msgid "How to Upgrade from 0.6.1.30 and Earlier" +msgstr "Como actualizar dende a versión 0.6.1.30 e anteriores" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:6 +msgid "Upgrading from 0.6.1.30 and Earlier Releases" +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:8 +#, python-format +msgid "" +"Since i2p's lead developer\n" +"has gone AWOL,\n" +"we do not have his update signing key or access to\n" +"www.i2p[.net] or dev.i2p[.net].\n" +"Complication and zzz have generated new signing keys, and they and Amiga " +"are providing\n" +"update file hosting. These changes must be configured in your router to " +"take effect." +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:17 +msgid "" +"Make the following configuration changes and your router will " +"automatically install\n" +"the latest release." +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:22 +#, python-format +msgid "" +"We recommend the automated process as it will verify the key of the " +"signed update file.\n" +"If you do not make these changes,\n" +"you may manually download the i2pupdate.zip file from\n" +"the download page." +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:34 +#, python-format +msgid "Change the News URL to: %(url)s" +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:38 +msgid "" +"Select ONE of the following new Update URLs at random and enter it into " +"the Update URL box: " +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:43 +msgid "Check the box \"Update through the eepProxy?\"" +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:44 +msgid "Click \"Save\"" +msgstr "Preme en \"Gardar\"" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:51 +msgid "Add the following line:" +msgstr "Engade a seguinte liña:" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:55 +msgid "Click \"Apply\"" +msgstr "Preme en \"Aplicar\"" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:58 +msgid "" +"You are now ready to automatically receive the release update file,\n" +"either by setting your update policy to \"download and install\" or by " +"clicking on the\n" +"\"update available\" link when it appears." +msgstr "" + +#: i2p2www/pages/site/misc/upgrade-0.6.1.30.html:65 +#, python-format +msgid "" +"If you would like to verify the trusted update keys, they are also\n" +"posted and signed here.\n" +"Thank you for your support during this transition. For help please " +"contact us on #i2p." +msgstr "" + diff --git a/i2p2www/translations/gl/LC_MESSAGES/priority.po b/i2p2www/translations/gl/LC_MESSAGES/priority.po new file mode 100644 index 00000000..61b3d31d --- /dev/null +++ b/i2p2www/translations/gl/LC_MESSAGES/priority.po @@ -0,0 +1,2504 @@ +# Galician translations for I2P. +# Copyright (C) 2016 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# Uberius Crypto , 2016 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2016-07-02 04:51+0000\n" +"PO-Revision-Date: 2016-10-20 01:15+0000\n" +"Last-Translator: Uberius Crypto \n" +"Language-Team: Galician (http://www.transifex.com/otf/I2P/language/gl/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 1.3\n" + +#: i2p2www/pages/blog/category.html:2 +msgid "Blog Category" +msgstr "Categoría do Blogue" + +#: i2p2www/pages/blog/category.html:4 +#, python-format +msgid "I2P Blog ATOM Feed for Category: %(category)s" +msgstr "" + +#: i2p2www/pages/blog/index.html:2 i2p2www/pages/blog/post.html:3 +#: i2p2www/pages/global/nav.html:78 +msgid "Blog" +msgstr "Blogue" + +#: i2p2www/pages/blog/index.html:4 i2p2www/pages/site/index.html:80 +msgid "I2P Blog ATOM Feed" +msgstr "" + +#: i2p2www/pages/blog/index.html:18 +#, python-format +msgid "Posted %(date)s by %(author)s" +msgstr "" + +#: i2p2www/pages/blog/latest.html:5 +msgid "More blog posts…" +msgstr "" + +#: i2p2www/pages/blog/post.html:12 +msgid "Posted:" +msgstr "Publicado:" + +#: i2p2www/pages/blog/post.html:13 +msgid "Author:" +msgstr "Autor/a:" + +#: i2p2www/pages/downloads/debian.html:4 +msgid "Debian I2P Packages" +msgstr "Paquetes Debian I2P" + +#: i2p2www/pages/downloads/debian.html:6 +msgid "" +"The Debian packages\n" +"have been tested and should work on x86/x86_64 platforms running:" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:11 +msgid "Ubuntu (Precise 12.04 and newer)" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:13 +msgid "Debian Linux (Wheezy and newer)" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:17 +#, python-format +msgid "" +"The I2P packages may work on systems not listed above. Please " +"report any issues\n" +"with these packages on Trac at\n" +"https://trac.i2p2.de." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:23 +msgid "" +"Option 1: Recent versions of Ubuntu and its " +"derivatives (Try this if you're not using Debian)" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:24 +msgid "Option 2: Debian (including Debian-derivatives)" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:27 +msgid "" +"Instructions for Ubuntu 12.04 Precise Pangolin (and newer) and " +"derivatives like Linux Mint & Trisquel" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:28 +msgid "Adding the PPA via the command line and installing I2P" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:31 +msgid "Open a terminal and enter:" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:33 +msgid "" +"This command will add the PPA to /etc/apt/sources.list.d and fetch the\n" +"gpg key that the repository has been signed with. The GPG key ensures\n" +"that the packages have not been tampered with since being built." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:40 +msgid "Notify your package manager of the new PPA by entering:" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:42 +msgid "" +"This command will retrieve the latest list of software from each\n" +"repository that is enabled on your system, including the I2P PPA that\n" +"was added with the earlier command." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:48 +msgid "You are now ready to install I2P!" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:52 +msgid "Adding the PPA Using Synaptic" +msgstr "A engadi-lo PPA usando Synaptic" + +#: i2p2www/pages/downloads/debian.html:55 +msgid "" +"Open Synaptic (System -> Administration -> Synaptic Package " +"Manager)." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:60 +msgid "" +"Once Synaptic opens, select Repositories from the " +"Settings menu." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:65 +msgid "" +"Click the Other Sources tab and click Add. Paste " +"ppa:i2p-maintainers/i2p into the APT-line field and click " +"Add Source. Click the Close button then " +"Reload." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:70 +msgid "" +"In the Quick Filter box, type in i2p and press enter. When " +"i2p is returned in the results list, right click " +"i2p and select Mark for Installation. After doing " +"so you may see a Mark additional required changes? popup. If so," +" click Mark then Apply." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:76 +msgid "" +"After the installation process completes you can move on to the next\n" +"part of starting I2P and configuring " +"it for your system." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:81 +msgid "Instructions for Debian" +msgstr "Instruccións para Debian" + +#: i2p2www/pages/downloads/debian.html:85 +msgid "" +"Note: The steps below should be performed with root access (i.e., " +"switching\n" +"user to root with \"su\" or by prefixing each command with \"sudo\")." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:90 +#, python-format +msgid "Add lines like the following to %(file)s." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:111 +#, python-format +msgid "" +"Download the key used to sign the repository" +" and add it to apt:" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:118 +msgid "Notify your package manager of the new repository by entering" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:120 +msgid "" +"This command will retrieve the latest list of software from every\n" +"repository enabled on your system, including the I2P repository added in " +"step\n" +"1." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:126 +msgid "" +"You are now ready to install I2P! Installing the i2p-keyring" +"\n" +"package will ensure that you receive updates to the repository's GPG key." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:133 +msgid "" +"After the installation process completes you can move on to the next part" +" of starting I2P and configuring it " +"for your system." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:137 +#: i2p2www/pages/downloads/post-install.html:1 +msgid "Post-install work" +msgstr "Tarefas post-instalación" + +#: i2p2www/pages/downloads/debian.html:139 +msgid "" +"Using these I2P packages the I2P router can be started in the following\n" +"three ways:" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:145 +msgid "" +""on demand" using the i2prouter script. Simply run " +""i2prouter\n" +"start" from a command prompt. (Note: Do " +"not use\n" +"sudo or run it as root!)" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:152 +msgid "" +""on demand" without the java service wrapper\n" +"(needed on non-Linux/non-x86 systems) by running \"i2prouter-" +"nowrapper\".\n" +"(Note: Do not\n" +"use sudo or run it as root!)" +msgstr "" + +#: i2p2www/pages/downloads/debian.html:160 +msgid "" +"as a service that automatically runs when your system boots, even\n" +"before logging in. The service can be enabled with \"dpkg-" +"reconfigure\n" +"i2p\" as root or using sudo. This is the recommended means of " +"operation." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:168 +msgid "" +"When installing for the first time, please remember to adjust your " +"NAT/firewall\n" +"if you can. The ports to forward can be found on the \n" +"network configuration page in the router console. If guidance with " +"respect to forwarding ports is needed,\n" +"you may find portforward.com to be" +" helpful." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:175 +msgid "" +"Please review and adjust the bandwidth settings on the\n" +"configuration page,\n" +"as the default settings of 96 KB/s down / 40 KB/s up are fairly " +"conservative." +msgstr "" + +#: i2p2www/pages/downloads/debian.html:181 +#: i2p2www/pages/downloads/post-install.html:34 +#, python-format +msgid "" +"If you want to reach eepsites via your browser, have a look on the browser proxy setup page for an easy " +"howto." +msgstr "" + +#: i2p2www/pages/downloads/list.html:6 i2p2www/pages/downloads/select.html:15 +#: i2p2www/pages/global/nav.html:3 +msgid "Download" +msgstr "Descargar" + +#: i2p2www/pages/downloads/list.html:14 +msgid "Source package" +msgstr "" + +#: i2p2www/pages/downloads/list.html:15 i2p2www/pages/downloads/list.html:156 +msgid "Automatic updates" +msgstr "Actualizacións automáticas" + +#: i2p2www/pages/downloads/list.html:16 +msgid "Manual updates" +msgstr "" + +#: i2p2www/pages/downloads/list.html:21 +msgid "Dependency" +msgstr "Dependencia" + +#: i2p2www/pages/downloads/list.html:22 +#, python-format +msgid "" +"\n" +"Java Runtime Version 7 or higher.\n" +"(Oracle,\n" +"OpenJDK, or\n" +"IcedTea\n" +"Java Version 7 or 8 recommended,\n" +"except Raspberry Pi: Oracle JDK 8 for ARM,\n" +"PowerPC: IBM Java SE 7 or 8)\n" +"
\n" +"Determine your installed Java version here\n" +"or type java -version at your command prompt.\n" +msgstr "" + +#: i2p2www/pages/downloads/list.html:42 i2p2www/pages/downloads/list.html:44 +msgid "Release Notes" +msgstr "" + +#: i2p2www/pages/downloads/list.html:46 +msgid "Change Log" +msgstr "" + +#: i2p2www/pages/downloads/list.html:48 +msgid "Debian Change Log" +msgstr "" + +#: i2p2www/pages/downloads/list.html:50 +msgid "Android Change Log" +msgstr "" + +#: i2p2www/pages/downloads/list.html:55 +msgid "Clean installs" +msgstr "" + +#: i2p2www/pages/downloads/list.html:59 +msgid "Download that file and run it." +msgstr "" + +#: i2p2www/pages/downloads/list.html:65 +#, python-format +msgid "" +"Download that file and double-click it (if that works) or\n" +" type java -jar i2pinstall_%(i2pversion)s.jar in a " +"terminal to run the\n" +" installer.\n" +" You may be able to right-click and select\n" +" "Open with Java"." +msgstr "" + +#: i2p2www/pages/downloads/list.html:73 i2p2www/pages/downloads/list.html:89 +msgid "Command line (headless) install:" +msgstr "" + +#: i2p2www/pages/downloads/list.html:74 +#, python-format +msgid "" +"Download the %(i2pversion)s OSX graphical installer file above and\n" +" run java -jar i2pinstall_%(i2pversion)s.jar -console " +"from the command line." +msgstr "" + +#: i2p2www/pages/downloads/list.html:81 +#, python-format +msgid "" +"Download that file and double-click it (if that works) or\n" +" type java -jar i2pinstall_%(i2pversion)s.jar in a " +"terminal to run the\n" +" installer.\n" +" On some platforms you may be able to right-click and select\n" +" "Open with Java"." +msgstr "" + +#: i2p2www/pages/downloads/list.html:90 +#, python-format +msgid "" +"Download the graphical installer file above and\n" +" run java -jar i2pinstall_%(i2pversion)s.jar -console " +"from the command line." +msgstr "" + +#: i2p2www/pages/downloads/list.html:98 +msgid "Packages for Debian & Ubuntu are available." +msgstr "" + +#: i2p2www/pages/downloads/list.html:104 +msgid "" +"Requires Android 2.3 (Gingerbread) or higher. If you earlier installed\n" +" I2P, you need to reinstall because we have also changed the release" +" keys." +msgstr "" + +#: i2p2www/pages/downloads/list.html:108 +msgid "512 MB RAM minimum; 1 GB recommended." +msgstr "512 MB RAM como mínimo; 1 GB recomendado." + +#: i2p2www/pages/downloads/list.html:111 +msgid "" +"The release and dev versions of the I2P APK are not compatible, as they\n" +" are signed by zzz and str4d respectively. Uninstall one before " +"installing\n" +" the other." +msgstr "" + +#: i2p2www/pages/downloads/list.html:120 +#, python-format +msgid "" +"Alternately, you can fetch the source from monotone\n" +" or via Git from git.repo.i2p or Github.\n" +"
\n" +" Run (tar xjvf i2psource_%(i2pversion)s.tar.bz2 ; cd " +"i2p-%(i2pversion)s ; ant pkg) then either\n" +" run the GUI installer or headless install as above." +msgstr "" + +#: i2p2www/pages/downloads/list.html:130 +#, python-format +msgid "" +"Android source is in monotone\n" +" and on Github.\n" +" Android builds require the I2P source.\n" +" See the documentation in the Android source for additional build " +"requirements and instructions." +msgstr "" + +#: i2p2www/pages/downloads/list.html:141 +#, python-format +msgid "" +"The files are signed by %(signer)s,\n" +"whose key is here." +msgstr "" + +#: i2p2www/pages/downloads/list.html:150 +msgid "Updates from earlier releases:" +msgstr "" + +#: i2p2www/pages/downloads/list.html:152 +msgid "Both automatic and manual upgrades are available for the release." +msgstr "" + +#: i2p2www/pages/downloads/list.html:157 +msgid "" +"If you are running 0.7.5 or later, your router should detect the\n" +"new release. To upgrade simply click the 'Download Update' button on your" +" router console\n" +"when it appears." +msgstr "" + +#: i2p2www/pages/downloads/list.html:163 +msgid "" +"Since 0.9.23, some releases are signed by str4d, whose signing key has " +"been in the router\n" +"since 0.9.9. Routers older than 0.9.9 will fail to verify update files " +"signed by str4d,\n" +"and will need to be manually updated using the process below." +msgstr "" + +#: i2p2www/pages/downloads/list.html:174 +msgid "" +"Download that file to your I2P\n" +" installation directory and rename as i2pupdate.zip.\n" +" (alternately, you can get the source as above and run \"ant " +"updater\", then copy the\n" +" resulting i2pupdate.zip to your I2P installation directory). You do" +" \n" +" NOT need to unzip that file." +msgstr "" + +#: i2p2www/pages/downloads/list.html:183 +msgid "Click \"Restart\"" +msgstr "" + +#: i2p2www/pages/downloads/list.html:188 +msgid "Grab a cup of coffee and come back in 11 minutes" +msgstr "Vai por unha taza de café e volta en 11 minutos" + +#: i2p2www/pages/downloads/list.html:195 +#, python-format +msgid "" +"The file is signed by %(signer)s,\n" +"whose key is here." +msgstr "" + +#: i2p2www/pages/downloads/list.html:201 +msgid "Previous Releases" +msgstr "" + +#: i2p2www/pages/downloads/list.html:203 +#, python-format +msgid "" +"Previous releases are available on Google " +"Code\n" +"and Launchpad\n" +"and within the I2P network on %(echelon)s." +msgstr "" + +#: i2p2www/pages/downloads/post-install.html:3 +msgid "" +"After running the installer on windows, simply click on the \"Start I2P\"" +" button\n" +"which will bring up the router console,\n" +"which has further instructions." +msgstr "" + +#: i2p2www/pages/downloads/post-install.html:9 +msgid "" +"On Unix-like systems, I2P can be started as a service\n" +"using the \"i2prouter\" script, located in the directory you selected for" +" I2P.\n" +"Changing to that directory in a console and issuing \"sh i2prouter " +"status\"\n" +"should tell you the router's status. The arguments \"start\", \"stop\" " +"and \"restart\"\n" +"control the service. The router console\n" +"can be accessed at its usual location.\n" +"For users on OpenSolaris and other systems for which the wrapper (i2psvc)" +" is not supported,\n" +"start the router with \"sh runplain.sh\" instead." +msgstr "" + +#: i2p2www/pages/downloads/post-install.html:20 +#, python-format +msgid "" +"When installing for the first time, please remember to adjust your " +"NAT/firewall\n" +"if you can, bearing in mind the Internet-facing ports I2P uses,\n" +"described here among other ports.\n" +"If you have successfully opened your port to inbound TCP, also enable " +"inbound TCP on the\n" +"configuration page." +msgstr "" + +#: i2p2www/pages/downloads/post-install.html:28 +msgid "" +"Also, please review and adjust the bandwidth settings on the\n" +"configuration page,\n" +"as the default settings of 96 KBps down / 40 KBps up are fairly slow." +msgstr "" + +#: i2p2www/pages/downloads/redirect.html:2 +msgid "Downloading..." +msgstr "A descargar..." + +#: i2p2www/pages/downloads/redirect.html:8 +#, python-format +msgid "" +"Your download will begin shortly. If it doesn't start within 5 seconds, " +"click here." +msgstr "" + +#: i2p2www/pages/downloads/select.html:2 i2p2www/pages/downloads/select.html:4 +msgid "Mirror selection" +msgstr "" + +#: i2p2www/pages/downloads/select.html:5 +msgid "File:" +msgstr "Arquivo:" + +#: i2p2www/pages/downloads/select.html:10 +msgid "Any mirror" +msgstr "" + +#: i2p2www/pages/global/bounty.html:19 +msgid "" +"To claim the bounty the author must not be paid by other organizations\n" +"or teams for this work (e.g. GSoC students are not valid)." +msgstr "" + +#: i2p2www/pages/global/bounty.html:29 +#, python-format +msgid "" +"Bounty amounts may be increased by further donations. Do\n" +"you think these are important? Add in your " +"donation, \n" +"marking the amount for the %(donatename)s bounty!" +msgstr "" + +#: i2p2www/pages/global/error_404.html:3 +msgid "Not found" +msgstr "Non atopado" + +#: i2p2www/pages/global/error_404.html:9 +msgid "" +"Yep... the resource, you were searching for, is named differently, " +"doesn't exist or was removed." +msgstr "" + +#: i2p2www/pages/global/error_500.html:5 +msgid "Server error" +msgstr "Erro do servidor" + +#: i2p2www/pages/global/error_500.html:13 +msgid "500 Server error" +msgstr "Erro do servidor 500" + +#: i2p2www/pages/global/error_500.html:17 +msgid "Umm... the server encountered some sort of error." +msgstr "" + +#: i2p2www/pages/global/footer.html:17 i2p2www/pages/global/nav.html:126 +msgid "Donate" +msgstr "Doar" + +#: i2p2www/pages/global/layout.html:35 +msgid "Skip navigation" +msgstr "" + +#: i2p2www/pages/global/layout.html:38 +msgid "I2P Logo" +msgstr "Logo I2P" + +#: i2p2www/pages/global/layout.html:38 i2p2www/pages/site/index.html:3 +msgid "The Invisible Internet Project" +msgstr "O Proxecto da Internet Invisible" + +#: i2p2www/pages/global/layout.html:80 +#, python-format +msgid "" +"This page was last updated in %(lastupdated)s and is accurate for router " +"version %(accuratefor)s." +msgstr "" + +#: i2p2www/pages/global/layout.html:84 +#, python-format +msgid "This page was last updated in %(lastupdated)s." +msgstr "" + +#: i2p2www/pages/global/layout.html:88 +#, python-format +msgid "This page is accurate for router version %(accuratefor)s." +msgstr "" + +#: i2p2www/pages/global/macros:25 +msgid "Previous" +msgstr "" + +#: i2p2www/pages/global/macros:40 +msgid "Next" +msgstr "" + +#: i2p2www/pages/global/macros:53 +msgid "Posted in" +msgstr "" + +#: i2p2www/pages/global/nav.html:4 +msgid "About" +msgstr "" + +#: i2p2www/pages/global/nav.html:6 +msgid "Introduction to I2P" +msgstr "Introdución a I2P" + +#: i2p2www/pages/global/nav.html:7 +msgid "Comparisons" +msgstr "" + +#: i2p2www/pages/global/nav.html:9 +msgid "Overview of comparisons" +msgstr "" + +#: i2p2www/pages/global/nav.html:13 +msgid "Other anonymous networks" +msgstr "" + +#: i2p2www/pages/global/nav.html:16 +msgid "Documentation" +msgstr "Documentación" + +#: i2p2www/pages/global/nav.html:18 +msgid "Documentation index" +msgstr "Índice da documentación" + +#: i2p2www/pages/global/nav.html:19 +msgid "How does it work?" +msgstr "Como funciona?" + +#: i2p2www/pages/global/nav.html:21 +msgid "Gentle intro" +msgstr "" + +#: i2p2www/pages/global/nav.html:22 +msgid "Tech intro" +msgstr "" + +#: i2p2www/pages/global/nav.html:23 +msgid "Threat model" +msgstr "" + +#: i2p2www/pages/global/nav.html:24 +msgid "Garlic routing" +msgstr "" + +#: i2p2www/pages/global/nav.html:25 +msgid "Network database" +msgstr "" + +#: i2p2www/pages/global/nav.html:26 +msgid "Tunnel routing" +msgstr "" + +#: i2p2www/pages/global/nav.html:27 +msgid "Peer selection" +msgstr "Selección de Par" + +#: i2p2www/pages/global/nav.html:28 +msgid "Cryptography" +msgstr "Criptografía" + +#: i2p2www/pages/global/nav.html:29 +msgid "ElGamal/AES+SessionTags" +msgstr "" + +#: i2p2www/pages/global/nav.html:32 +msgid "Specifications" +msgstr "Especificacións" + +#: i2p2www/pages/global/nav.html:33 +msgid "Proposals" +msgstr "" + +#: i2p2www/pages/global/nav.html:34 +msgid "API" +msgstr "" + +#: i2p2www/pages/global/nav.html:40 +msgid "Streaming library" +msgstr "" + +#: i2p2www/pages/global/nav.html:41 +msgid "Datagrams" +msgstr "Datagramas" + +#: i2p2www/pages/global/nav.html:45 i2p2www/pages/global/nav.html:109 +msgid "Applications" +msgstr "Aplicacións" + +#: i2p2www/pages/global/nav.html:47 +msgid "Supported applications" +msgstr "Aplicacións soportadas" + +#: i2p2www/pages/global/nav.html:48 +msgid "Bittorrent" +msgstr "Bittorrent" + +#: i2p2www/pages/global/nav.html:51 +msgid "Protocols" +msgstr "Protocolos" + +#: i2p2www/pages/global/nav.html:53 +msgid "Protocol stack" +msgstr "" + +#: i2p2www/pages/global/nav.html:58 +msgid "Transports" +msgstr "" + +#: i2p2www/pages/global/nav.html:60 +msgid "Transport layer overview" +msgstr "" + +#: i2p2www/pages/global/nav.html:65 +msgid "Tunnels" +msgstr "Túneles" + +#: i2p2www/pages/global/nav.html:67 +msgid "Tunnel implementation" +msgstr "" + +#: i2p2www/pages/global/nav.html:68 +msgid "Unidirectional tunnels" +msgstr "Túneles unidireccionais" + +#: i2p2www/pages/global/nav.html:69 +msgid "Old implementation" +msgstr "" + +#: i2p2www/pages/global/nav.html:72 +msgid "Naming and addressbook" +msgstr "" + +#: i2p2www/pages/global/nav.html:73 +msgid "Plugins" +msgstr "Plugins" + +#: i2p2www/pages/global/nav.html:74 +msgid "Reseed" +msgstr "" + +#: i2p2www/pages/global/nav.html:77 +msgid "Team" +msgstr "Equipo" + +#: i2p2www/pages/global/nav.html:79 +msgid "Hall of Fame" +msgstr "" + +#: i2p2www/pages/global/nav.html:80 +msgid "Academic papers and peer review" +msgstr "" + +#: i2p2www/pages/global/nav.html:82 +msgid "Presentations, tutorials and articles" +msgstr "" + +#: i2p2www/pages/global/nav.html:83 +msgid "Contact us" +msgstr "" + +#: i2p2www/pages/global/nav.html:84 i2p2www/pages/site/links.html:2 +msgid "Links" +msgstr "Ligazóns" + +#: i2p2www/pages/global/nav.html:85 +msgid "Impressum" +msgstr "" + +#: i2p2www/pages/global/nav.html:88 +msgid "Help" +msgstr "Axuda" + +#: i2p2www/pages/global/nav.html:90 +msgid "FAQ" +msgstr "PUF" + +#: i2p2www/pages/global/nav.html:91 +msgid "How to browse I2P" +msgstr "" + +#: i2p2www/pages/global/nav.html:92 +msgid "Glossary" +msgstr "Glosario" + +#: i2p2www/pages/global/nav.html:93 +msgid "Performance" +msgstr "Rendemento" + +#: i2p2www/pages/global/nav.html:94 i2p2www/pages/site/contact.html:43 +msgid "Forums" +msgstr "Foros" + +#: i2p2www/pages/global/nav.html:95 +msgid "Verify I2P" +msgstr "Verificar I2P" + +#: i2p2www/pages/global/nav.html:97 +msgid "Release signing keys" +msgstr "" + +#: i2p2www/pages/global/nav.html:98 +msgid "Signed keys" +msgstr "Chaves firmadas dixitalmente" + +#: i2p2www/pages/global/nav.html:99 +msgid "Developers keys" +msgstr "" + +#: i2p2www/pages/global/nav.html:104 +msgid "Volunteer" +msgstr "" + +#: i2p2www/pages/global/nav.html:106 +msgid "Get involved!" +msgstr "" + +#: i2p2www/pages/global/nav.html:107 +msgid "Develop" +msgstr "Desenvolver" + +#: i2p2www/pages/global/nav.html:110 +msgid "Licenses" +msgstr "Licencias" + +#: i2p2www/pages/global/nav.html:111 +msgid "Bug tracker" +msgstr "" + +#: i2p2www/pages/global/nav.html:114 +msgid "Academic research" +msgstr "Investigación académica" + +#: i2p2www/pages/global/nav.html:115 +msgid "Open research questions" +msgstr "" + +#: i2p2www/pages/global/nav.html:116 +msgid "Guides" +msgstr "Guía" + +#: i2p2www/pages/global/nav.html:118 +msgid "New developers" +msgstr "Novos desenvolvedores" + +#: i2p2www/pages/global/nav.html:119 +msgid "Using an IDE with I2P" +msgstr "" + +#: i2p2www/pages/global/nav.html:120 +msgid "Developer guidelines and coding style" +msgstr "" + +#: i2p2www/pages/global/nav.html:121 +msgid "Monotone" +msgstr "" + +#: i2p2www/pages/global/nav.html:122 +msgid "New translators" +msgstr "Novos tradutores" + +#: i2p2www/pages/global/nav.html:125 +msgid "Bounties" +msgstr "" + +#: i2p2www/pages/global/nav.html:127 +msgid "Meetings" +msgstr "Encontros" + +#: i2p2www/pages/global/nav.html:128 +msgid "Roadmap" +msgstr "" + +#: i2p2www/pages/global/nav.html:129 +msgid "Task list" +msgstr "" + +#: i2p2www/pages/global/nav.html:132 +msgid "Language" +msgstr "Idioma" + +#: i2p2www/pages/meetings/index.html:2 +msgid "Logs of past I2P meetings" +msgstr "" + +#: i2p2www/pages/meetings/index.html:4 +msgid "I2P Meetings ATOM Feed" +msgstr "" + +#: i2p2www/pages/meetings/index.html:7 +#, python-format +msgid "" +"Regularly scheduled project meetings are held on the first Tuesday of " +"every month at 8 PM UTC.\n" +"Anyone can schedule and\n" +"run a meeting, by posting the agenda in\n" +"the meetings forum." +msgstr "" + +#: i2p2www/pages/meetings/index.html:14 +#, python-format +msgid "" +"If you have something to discuss, please find the developers on IRC in " +"#i2p-dev.\n" +"Status updates from developers are also " +"available." +msgstr "" + +#: i2p2www/pages/meetings/show.html:2 +#, python-format +msgid "I2P Development Meeting %(id)s" +msgstr "" + +#: i2p2www/pages/meetings/show.html:10 +msgid "Full IRC Log" +msgstr "" + +#: i2p2www/pages/papers/list.html:28 +msgid "By topic" +msgstr "Por asunto" + +#: i2p2www/pages/papers/list.html:34 +msgid "By date" +msgstr "Por data" + +#: i2p2www/pages/papers/list.html:40 +msgid "By author" +msgstr "Por autor/a" + +#: i2p2www/pages/papers/list.html:69 +#, python-format +msgid "" +"Please send new or corrected entries to\n" +"%(email)s.
\n" +"If you can, please format them as BibTeX; see our\n" +"BibTeX source page for examples.
\n" +"Remember to include URLs if possible:\n" +"offline papers are less useful." +msgstr "" + +#: i2p2www/pages/papers/list.html:80 +#, python-format +msgid "" +"The source code for this page was adapted from\n" +"Free Haven's anonymity bibliography." +msgstr "" + +#: i2p2www/pages/site/contact.html:2 +msgid "Contact" +msgstr "Contacto" + +#: i2p2www/pages/site/contact.html:4 +msgid "Email" +msgstr "Correo" + +#: i2p2www/pages/site/contact.html:5 +msgid "" +"Please do not use these email addresses for support requests.\n" +"These are not public email lists.\n" +"We do not provide help via email." +msgstr "" + +#: i2p2www/pages/site/contact.html:25 +msgid "" +"Our primary IRC network is the Irc2P network within I2P; a default tunnel" +" to this network is set up with new router installs.\n" +" We are also present on multiple standard networks like OFTC,\n" +" EIN and Freenode.\n" +" All I2P-related channels on all these network are linked to the main " +"channels on Irc2P via relay bots." +msgstr "" + +#: i2p2www/pages/site/contact.html:33 +msgid "Channel list:" +msgstr "Lista de canles:" + +#: i2p2www/pages/site/contact.html:35 +msgid "General i2p discussion and help channel" +msgstr "" + +#: i2p2www/pages/site/contact.html:36 +msgid "Offtopic" +msgstr "" + +#: i2p2www/pages/site/contact.html:37 +msgid "Development talk" +msgstr "Conversa sobre desenvolvemento" + +#: i2p2www/pages/site/contact.html:38 +msgid "Purple I2P (I2Pd) Development talk" +msgstr "" + +#: i2p2www/pages/site/contact.html:39 +msgid "Abscond browser bundle discussion and development" +msgstr "" + +#: i2p2www/pages/site/contact.html:44 +#, python-format +msgid "" +"Most of the discussion about I2P's development happens on the I2P developer forum. This is usually the best" +" place to start with inquiries, if the dev IRC channel is inactive." +msgstr "" + +#: i2p2www/pages/site/contact.html:48 +msgid "Mailing lists" +msgstr "Listaxes de correo" + +#: i2p2www/pages/site/contact.html:49 +msgid "" +"I2P does have a mailing list, but it is rarely used as the current small " +"team of developers prefer to communicate via IRC or the developer forum. " +"This may change in future." +msgstr "" + +#: i2p2www/pages/site/contact.html:54 +msgid "Subscribing" +msgstr "" + +#: i2p2www/pages/site/contact.html:55 +msgid "" +"To subscribe to a mailing list, go to the list information page (linked " +"below) and fill out the form. I2P-internal email addresses " +"(foobar@mail.i2p) can be used." +msgstr "" + +#: i2p2www/pages/site/contact.html:59 +msgid "Unsubscribing" +msgstr "" + +#: i2p2www/pages/site/contact.html:60 +msgid "" +"To unsubscribe from a mailing list or edit your subscription options, go " +"to the list information page (linked below) and enter your subscription " +"email address." +msgstr "" + +#: i2p2www/pages/site/contact.html:64 +msgid "Lists" +msgstr "Listas" + +#: i2p2www/pages/site/contact.html:67 i2p2www/pages/site/contact.html:71 +msgid "Archive" +msgstr "" + +#: i2p2www/pages/site/contact.html:68 +msgid "I2P developer discussions - anything related to development of I2P" +msgstr "" + +#: i2p2www/pages/site/contact.html:72 +msgid "" +"General I2P discussion - anything that doesn't fit in a different list " +"goes here" +msgstr "" + +#: i2p2www/pages/site/contact.html:78 +msgid "" +"You don't like mailing lists? Then this is for you. All mailing lists are" +" available via NNTP as well." +msgstr "" + +#: i2p2www/pages/site/contact.html:83 +msgid "Group-List-mapping:" +msgstr "" + +#: i2p2www/pages/site/contact.html:88 +msgid "Servers:" +msgstr "Servidores:" + +#: i2p2www/pages/site/faq.html:2 +msgid "Frequently Asked Questions" +msgstr "Preguntas Usualmente Formuladas" + +#: i2p2www/pages/site/faq.html:6 +msgid "General" +msgstr "Xeral" + +#: i2p2www/pages/site/faq.html:8 i2p2www/pages/site/faq.html:52 +msgid "What systems will I2P run on?" +msgstr "" + +#: i2p2www/pages/site/faq.html:9 +msgid "Whats an \"eepsite\" and how do I configure my browser so I can use them?" +msgstr "" + +#: i2p2www/pages/site/faq.html:10 i2p2www/pages/site/faq.html:265 +msgid "My router has very few active peers, is this OK?" +msgstr "" + +#: i2p2www/pages/site/faq.html:11 i2p2www/pages/site/faq.html:500 +msgid "What do the Active x/y numbers mean in the router console?" +msgstr "" + +#: i2p2www/pages/site/faq.html:12 i2p2www/pages/site/faq.html:227 +msgid "" +"My active peers / known peers / participating tunnels / connections / " +"bandwidth vary dramatically over time! Is anything wrong?" +msgstr "" + +#: i2p2www/pages/site/faq.html:13 i2p2www/pages/site/faq.html:350 +msgid "Is using an outproxy safe?" +msgstr "É seguro usar un outproxy?" + +#: i2p2www/pages/site/faq.html:14 i2p2www/pages/site/faq.html:376 +msgid "Most of the eepsites within I2P are down?" +msgstr "" + +#: i2p2www/pages/site/faq.html:15 i2p2www/pages/site/faq.html:529 +msgid "What ports does I2P use?" +msgstr "" + +#: i2p2www/pages/site/faq.html:16 +msgid "Why is I2P listening for connections on port 32000?" +msgstr "" + +#: i2p2www/pages/site/faq.html:17 i2p2www/pages/site/faq.html:63 +msgid "I think I found a bug, where can I report it?" +msgstr "" + +#: i2p2www/pages/site/faq.html:18 i2p2www/pages/site/faq.html:109 +msgid "What happened to *.i2p.net? What happened to jrandom? Is I2P dead?" +msgstr "" + +#: i2p2www/pages/site/faq.html:19 i2p2www/pages/site/faq.html:847 +msgid "I have a question!" +msgstr "" + +#: i2p2www/pages/site/faq.html:21 +msgid "Setup" +msgstr "" + +#: i2p2www/pages/site/faq.html:23 i2p2www/pages/site/faq.html:234 +msgid "" +"My router has been up for several minutes and has zero or very few " +"connections" +msgstr "" + +#: i2p2www/pages/site/faq.html:24 i2p2www/pages/site/faq.html:392 +msgid "Why is I2P so slow?" +msgstr "" + +#: i2p2www/pages/site/faq.html:25 i2p2www/pages/site/faq.html:80 +msgid "" +"I'm missing lots of hosts in my addressbook. What are some good " +"subscription links?" +msgstr "" + +#: i2p2www/pages/site/faq.html:26 i2p2www/pages/site/faq.html:385 +msgid "How do I set up my own eepsite?" +msgstr "" + +#: i2p2www/pages/site/faq.html:27 i2p2www/pages/site/faq.html:418 +msgid "Bittorrent / I2PSnark / Azureus I2P Plugin Questions?" +msgstr "" + +#: i2p2www/pages/site/faq.html:28 i2p2www/pages/site/faq.html:425 +msgid "How do I connect to IRC within I2P?" +msgstr "" + +#: i2p2www/pages/site/faq.html:29 i2p2www/pages/site/faq.html:283 +msgid "I can't access regular Internet sites through I2P." +msgstr "" + +#: i2p2www/pages/site/faq.html:30 i2p2www/pages/site/faq.html:298 +msgid "I can't access https:// or ftp:// sites through I2P." +msgstr "" + +#: i2p2www/pages/site/faq.html:31 i2p2www/pages/site/faq.html:508 +msgid "Is it possible to use I2P as a SOCKS proxy?" +msgstr "" + +#: i2p2www/pages/site/faq.html:32 i2p2www/pages/site/faq.html:491 +msgid "How do I configure my browser?" +msgstr "" + +#: i2p2www/pages/site/faq.html:33 i2p2www/pages/site/faq.html:436 +msgid "" +"How can I access the web console from my other machines or password " +"protect it?" +msgstr "" + +#: i2p2www/pages/site/faq.html:34 i2p2www/pages/site/faq.html:476 +msgid "How can I use applications from my other machines?" +msgstr "" + +#: i2p2www/pages/site/faq.html:35 i2p2www/pages/site/faq.html:750 +msgid "How do I reseed manually?" +msgstr "" + +#: i2p2www/pages/site/faq.html:36 i2p2www/pages/site/faq.html:126 +msgid "My router is using too much CPU?!?" +msgstr "" + +#: i2p2www/pages/site/faq.html:38 +msgid "Misconception" +msgstr "" + +#: i2p2www/pages/site/faq.html:40 i2p2www/pages/site/faq.html:368 +msgid "" +"How do I access IRC, BitTorrent, or other services on the regular " +"Internet?" +msgstr "" + +#: i2p2www/pages/site/faq.html:41 +msgid "" +"Is my router an \"exit node\"(outproxy) to the regular Internet? I don't " +"want it to be." +msgstr "" + +#: i2p2www/pages/site/faq.html:42 i2p2www/pages/site/faq.html:190 +msgid "" +"I am opposed to certain types of content. How do I keep from " +"distributing, storing, or accessing them?" +msgstr "" + +#: i2p2www/pages/site/faq.html:44 +msgid "Errors and Their Solutions" +msgstr "" + +#: i2p2www/pages/site/faq.html:46 i2p2www/pages/site/faq.html:786 +msgid "" +"I'm using FreeBSD and when I start I2P I receive an error about " +"libm.so.4!" +msgstr "" + +#: i2p2www/pages/site/faq.html:47 +msgid "" +"In wrapper.log I see an error stating Protocol family " +"unavailable when I2P is loading" +msgstr "" + +#: i2p2www/pages/site/faq.html:53 i2p2www/pages/site/faq.html:64 +#: i2p2www/pages/site/faq.html:81 i2p2www/pages/site/faq.html:110 +#: i2p2www/pages/site/faq.html:127 i2p2www/pages/site/faq.html:191 +#: i2p2www/pages/site/faq.html:228 i2p2www/pages/site/faq.html:235 +#: i2p2www/pages/site/faq.html:266 i2p2www/pages/site/faq.html:275 +#: i2p2www/pages/site/faq.html:284 i2p2www/pages/site/faq.html:299 +#: i2p2www/pages/site/faq.html:351 i2p2www/pages/site/faq.html:369 +#: i2p2www/pages/site/faq.html:377 i2p2www/pages/site/faq.html:386 +#: i2p2www/pages/site/faq.html:393 i2p2www/pages/site/faq.html:419 +#: i2p2www/pages/site/faq.html:426 i2p2www/pages/site/faq.html:437 +#: i2p2www/pages/site/faq.html:477 i2p2www/pages/site/faq.html:484 +#: i2p2www/pages/site/faq.html:492 i2p2www/pages/site/faq.html:501 +#: i2p2www/pages/site/faq.html:509 i2p2www/pages/site/faq.html:530 +#: i2p2www/pages/site/faq.html:738 i2p2www/pages/site/faq.html:751 +#: i2p2www/pages/site/faq.html:787 i2p2www/pages/site/faq.html:819 +#: i2p2www/pages/site/faq.html:848 +msgid "link" +msgstr "" + +#: i2p2www/pages/site/faq.html:54 +#, python-format +msgid "" +"While I2P has been reported to run PCs as meagre as a low-end Pentium II " +"with 64 MB of RAM, you'll have a much better experience on a Pentium III " +"(or better) with 128MB of RAM (or more). A chart " +"comparing the performance of the various JREs can be found at %(chart)s, but in short: it's at all possible, use" +" Sun/Oracle Java or OpenJDK." +msgstr "" + +#: i2p2www/pages/site/faq.html:58 +msgid "" +"I2P has been tested on Windows, Linux, FreeBSD (see the note below), OSX, and OpenSolaris. There is work " +"underway to bring I2P to the Android platform." +msgstr "" + +#: i2p2www/pages/site/faq.html:66 +msgid "Here are some places, pick one or more." +msgstr "" + +#: i2p2www/pages/site/faq.html:72 +msgid "Discuss with the developers on IRC in #i2p-dev" +msgstr "" + +#: i2p2www/pages/site/faq.html:76 +msgid "Please include relevant information from the router logs and wrapper logs." +msgstr "" + +#: i2p2www/pages/site/faq.html:82 +msgid "" +"The default subscription is to http://www.i2p2.i2p/hosts.txt which is " +"updated rarely.\n" +"If you don't have another subscription, you may often have to use " +"\"jump\" links which\n" +"is annoying." +msgstr "" + +#: i2p2www/pages/site/faq.html:88 +msgid "" +"Here are some other public addressbook subscription links. You may wish " +"to add one or two\n" +"to your susidns " +"subscription list.\n" +"You don't need to add all of them, as they sync with each other " +"periodically.\n" +"The links using a cgi-bin application employ various strategies to " +"minimize\n" +"the number of duplicate addresses delivered, so they should be more " +"efficient.\n" +"Note that subscribing to a hosts.txt service is an act of \"trust\", as a" +" malicious\n" +"subscription could give you incorrect addresses. So think about whether " +"you\n" +"want to trust any of these.\n" +"The operators of these services may have various policies for listing " +"hosts.\n" +"Presence on this list does not imply endorsement." +msgstr "" + +#: i2p2www/pages/site/faq.html:111 +msgid "" +"Jrandom was the lead developer of I2P and\n" +"Syndie for several years.\n" +"We do not know if or when jrandom will return.\n" +"The *.i2p.net domains were left in a non-functioning state after a power\n" +"outage at the hosting company." +msgstr "" + +#: i2p2www/pages/site/faq.html:119 +#, python-format +msgid "" +"See this page for jrandom's parting message " +"and additional information\n" +"on the migration of *.i2p.net to this website." +msgstr "" + +#: i2p2www/pages/site/faq.html:124 +msgid "I2P remains in active development." +msgstr "" + +#: i2p2www/pages/site/faq.html:128 +msgid "There are many possible causes of high CPU usage. Here is a checklist:" +msgstr "" + +#: i2p2www/pages/site/faq.html:133 +msgid "" +"Try to use either OpenJDK or Sun/Oracle Java if it's available for your " +"system. You can check \n" +"which version of java you have installed by typing java " +"-version at a \n" +"command/shell prompt. Performance tends to suffer with other " +"implementations of java." +msgstr "" + +#: i2p2www/pages/site/faq.html:140 +msgid "" +"Are you running a BitTorrent client over I2P? Try reducing the number of " +"torrents, the bandwidth limits,\n" +"or try turning it off completely to see if that helps." +msgstr "" + +#: i2p2www/pages/site/faq.html:146 +msgid "" +"Are your bandwidth limits set too high? It is possible that too much " +"traffic is going through your\n" +"I2P router and it is overloaded. Try reducing the setting for share " +"bandwidth percentage on the configuration page." +msgstr "" + +#: i2p2www/pages/site/faq.html:151 +msgid "" +"Make sure that you're running the latest version of I2P to get the " +"benefits of increased performance and bug fixes." +msgstr "" + +#: i2p2www/pages/site/faq.html:156 +msgid "" +"Has enough memory been set aside for use by I2P? Look at the memory graph" +" on the graphs page to see\n" +"if the memory usage is \"pegged\"—the JVM is spending most of its " +"time in\n" +"garbage collection. Increase the setting " +"wrapper.java.maxmemory in the file " +"wrapper.config." +msgstr "" + +#: i2p2www/pages/site/faq.html:163 +msgid "" +"Is the CPU usage simply higher than you would like, or is it pegged at " +"100% for a long time?\n" +"If it's pegged, this could be a bug. Look in the logs for clues." +msgstr "" + +#: i2p2www/pages/site/faq.html:169 +#, python-format +msgid "" +"You may be using the Java-based BigInteger library instead of the native " +"version,\n" +"especially if you are running on a new or unusual OS or hardware " +"(OpenSolaris, mipsel, etc.).\n" +"See the jbigi page for instructions on\n" +"diagnosing, building, and testing methods." +msgstr "" + +#: i2p2www/pages/site/faq.html:177 +msgid "" +"If your native jbigi library is working fine, the biggest user of\n" +"CPU may be routing traffic for participating tunnels. This uses CPU\n" +"because at each hop a layer of encryption must be decoded.\n" +"You can limit participating traffic in two ways - by reducing the\n" +"share bandwidth on\n" +"confignet.jsp,\n" +"or by setting router.maxParticipatingTunnels=nnn on\n" +"configadvanced.jsp." +msgstr "" + +#: i2p2www/pages/site/faq.html:192 +msgid "" +"Hmm. I2P is an anonymous network, so that's a tricky one.\n" +"I2P is designed to withstand censorship, providing a means for everyone " +"to communicate freely. \n" +"The best way to keep your PC free of (encrypted) traffic that you dislike" +" is to not use I2P.\n" +"Freedom of speech has some costs.\n" +"But let's address your question in three parts:" +msgstr "" + +#: i2p2www/pages/site/faq.html:201 +msgid "" +"Distribution - All traffic on I2P is encrypted in multiple layers." +" You don't know\n" +"a message's contents, source, or destination.\n" +"All traffic you route is internal to the I2P network, you are not an exit node (outproxy).\n" +"Your only alternative is to refuse to route\n" +"any traffic, by setting your share bandwidth or maximum " +"participating tunnels to 0 (see above).\n" +"It would be nice if you didn't do this, you should help the network by " +"routing traffic for others.\n" +"Over 95% of users route traffic for others." +msgstr "" + +#: i2p2www/pages/site/faq.html:212 +msgid "" +"Storage - I2P does not do distributed storage of content. You must" +" be thinking of\n" +"Freenet.\n" +"Nobody's content is being stored on your computer by running I2P." +msgstr "" + +#: i2p2www/pages/site/faq.html:219 +msgid "" +"Access - If there are some eepsites you don't like, don't go " +"there.\n" +"Or, use a blocking proxy like Privoxy or some type of \"net nanny\"." +msgstr "" + +#: i2p2www/pages/site/faq.html:229 +msgid "" +"No. This is normal.\n" +"All routers adjust dynamically to changing network conditions and demands." +msgstr "" + +#: i2p2www/pages/site/faq.html:236 +msgid "" +"You may need to reseed your I2P router. With recent versions of I2P you " +"can go to http://localhost:7657/configreseed" +" and click the Save Changes and Reseed Now button. If this " +"method doesn't work—or you're using a very old version—you " +"may need to reseed manually." +msgstr "" + +#: i2p2www/pages/site/faq.html:239 +msgid "" +"The reseed URL changed a few years ago. If this is your first install and" +" you have installed\n" +"an old (0.6.1.30 or earlier) release, or\n" +"you have not run I2P in a long time, you must change the URL and then\n" +"click \"Reseed\" on the console to find other routers.\n" +"After your router is running,\n" +"on configadvanced.jsp," +"\n" +"add the line i2p.reseedURL=http://netdb.i2p2.de/\n" +"OR i2p.reseedURL=http://i2pdb.tin0.de/netDb/ (either should " +"work),\n" +"then click \"Apply\", then click the \"reseed\" link on the left." +msgstr "" + +#: i2p2www/pages/site/faq.html:250 +#, python-format +msgid "" +"This works if you are running 0.6.1.27 or later.\n" +"If you are running release 0.6.1.31 or later, you probably don't need to " +"do this.\n" +"If you are running release 0.6.1.26 or earlier, either follow the\n" +"manual reseed instructions below\n" +"or install the latest release.\n" +"Possible alternate method - add\n" +"wrapper.java.additional.5=-Di2p.reseedURL=http://netdb.i2p2.de/\n" +"to wrapper.config, shutdown the router completely, then start again, then" +" click \"reseed\".\n" +"Let us know if this works." +msgstr "" + +#: i2p2www/pages/site/faq.html:261 +#, python-format +msgid "" +"...but you *really* should upgrade to " +"the latest version." +msgstr "" + +#: i2p2www/pages/site/faq.html:267 +msgid "" +"If your router has 10 or more active peers, everything is fine. Changes " +"in releases 0.6.1.31 and 0.6.1.32 improved the\n" +"efficiency of the router and effectively reduced the number of active " +"peers.\n" +"The router should maintain connections to a few peers at all " +"times.\n" +"The best way to stay \"better-connected\" to the network is to share more bandwidth." +msgstr "" + +#: i2p2www/pages/site/faq.html:274 +msgid "" +"Is my router an \"exit node\" to the regular Internet? I don't want it to" +" be." +msgstr "" + +#: i2p2www/pages/site/faq.html:276 +msgid "" +"No. Unlike Tor,\n" +"\"exit nodes\" or \"outproxies\" are not an inherent part of the network." +"\n" +"Only volunteers who set up and run separate applications will relay " +"traffic to the regular Internet.\n" +"There are very, very few of these." +msgstr "" + +#: i2p2www/pages/site/faq.html:285 +msgid "" +"See above. There are very few HTTP \"outproxies\", they are not an " +"inherent part of the network,\n" +"and they may not be up.\n" +"In addition, the old outproxies squid.i2p, true.i2p, and krabs.i2p have " +"vanished.\n" +"The only outproxy at the moment is false.i2p.\n" +"To use it, edit your i2ptunnel " +"settings for eepProxy\n" +"and set your outproxy list to 'false.i2p' (only).\n" +"Then stop and restart the eepProxy.\n" +"If it doesn't work, the outproxy is not up. It is not I2P's fault.\n" +"If your primary reason to use an anonymous network is to anonymously " +"access sites\n" +"on the regular Internet, you should probably try Tor." +msgstr "" + +#: i2p2www/pages/site/faq.html:300 +msgid "" +"Within I2P, there is no need for HTTPS, as all traffic is encrypted end-" +"to-end.\n" +"FTP is not supported for technical reasons." +msgstr "" + +#: i2p2www/pages/site/faq.html:304 +msgid "" +"There are no FTP \"outproxies\" to the Internet—it may not even be " +"possible to set up one.\n" +"Any other kind of outproxy may work if it's set up with a standard " +"tunnel. \n" +"If you would like to set up some type of outproxy, carefully research the" +" potential risks.\n" +"The I2P community may or may not be able to help with the technical " +"aspects, feel free to ask." +msgstr "" + +#: i2p2www/pages/site/faq.html:310 +msgid "" +"As explained several times above, any existing outproxy isn't a core part" +" of the network.\n" +"They are services run by individuals and they may or may not\n" +"be operational at any given time." +msgstr "" + +#: i2p2www/pages/site/faq.html:315 +msgid "" +"Update: Thanks to the work of h2ik, there is an https outproxy " +"available for use via I2P. Starting with I2P 0.8.4 the tunnel is " +"configured out of the box.
\n" +"In case the https outproxy is not available in your version of I2P, you " +"can add it easily by doing the following:" +msgstr "" + +#: i2p2www/pages/site/faq.html:321 +msgid "" +"Open i2p tunnel " +"manager. Scroll down to the bottom." +msgstr "" + +#: i2p2www/pages/site/faq.html:326 +msgid "" +"Choose CONNECT from New Client Tunnel dropdown list, click " +"Create" +msgstr "" + +#: i2p2www/pages/site/faq.html:331 +#, python-format +msgid "" +"In the new page, name and describe your new https tunnel as" +" you like.\n" +"The Access Point is your local port for the new https proxy " +"recommended port's 4445.\n" +"Outproxy should be the outproxy's .i2p address which supports " +"https. \n" +"See this forum post of h2ik's for the " +"address. \n" +"Make sure Shared Client, Delay Connect, AutoStart " +"are checked.\n" +"Other options should be left at the defaults. Click Save. In tunnel " +"manger, click the Start button next to your new tunnel." +msgstr "" + +#: i2p2www/pages/site/faq.html:341 +msgid "" +"In firefox, click through " +"Tools>Options>Advanced>Network>Setting." +"\n" +"Untick Use this proxy for all protocol, set SSL proxy: to " +"localhost:4445." +msgstr "" + +#: i2p2www/pages/site/faq.html:346 +msgid "Done." +msgstr "" + +#: i2p2www/pages/site/faq.html:352 +#, python-format +msgid "" +"\n" +"This is a question that only you can answer because the correct answer " +"depends on your behaviours, your\n" +"threat model, and how much you trust the " +"outproxy operator." +msgstr "" + +#: i2p2www/pages/site/faq.html:356 +msgid "" +"Like Tor, I2P does not magically encrypt the Internet.\n" +"You are vulnerable to snooping by the outproxy operators.\n" +"The Tor" +" FAQ\n" +"does a good job of explaining this." +msgstr "" + +#: i2p2www/pages/site/faq.html:362 +#, python-format +msgid "" +"In addition, you may be vulnerable to collusion between the outproxy " +"operator\n" +"and operators of other I2P services, if you use the same tunnels " +"(\"shared clients\").\n" +"There is additional discussion about this on %(zzz)s." +msgstr "" + +#: i2p2www/pages/site/faq.html:370 +msgid "" +"Unless an outproxy has been set up for the service you want to connect " +"to, this cannot be done.\n" +"There are only three types of outproxies running right now: HTTP, HTTPS, " +"and email. Note that there is not a SOCKS outproxy.\n" +"If this type of service is required, try Tor." +msgstr "" + +#: i2p2www/pages/site/faq.html:378 +#, python-format +msgid "" +"If you consider every eepsite that has ever been created, yes, most of " +"them are down.\n" +"People and eepsites come and go.\n" +"A good way to get started in I2P is check out a list of eepsites that are" +" currently up.\n" +"%(eepstatus)s tracks active eepsites." +msgstr "" + +#: i2p2www/pages/site/faq.html:387 +msgid "" +"Click on the Website link\n" +"at the top of your router console for instructions." +msgstr "" + +#: i2p2www/pages/site/faq.html:394 +msgid "" +"Why are downloads, torrents, web browsing, and everything else so slow on" +" I2P?\n" +"The encryption and routing within the I2P network adds a substantial " +"amount of overhead and limits bandwidth.\n" +"Anonymity isn't free." +msgstr "" + +#: i2p2www/pages/site/faq.html:399 +msgid "" +"In addition, you and everybody else probably need to increase your " +"bandwidth limits.\n" +"Two key settings are the inbound and outbound bandwidth limiters on\n" +"the configuration page.\n" +"With the default settings of 32KBps you will generally get no better than" +" 15KBps data transfer in I2PSnark.\n" +"Increasing the settings (but keeping within your actual connection " +"limitations)\n" +"will increase the potential transfer rate for I2PSnark and all other " +"applications." +msgstr "" + +#: i2p2www/pages/site/faq.html:407 +msgid "" +"Also, do you have sufficient share bandwidth configured to allow " +"participating tunnels\n" +"to route through your router? Believe it or not, allowing participating " +"traffic\n" +"keeps you well-integrated in the network and helps your own transfer " +"speeds." +msgstr "" + +#: i2p2www/pages/site/faq.html:412 +#, python-format +msgid "" +"I2P is a work in progress. Lots of improvements and fixes are being " +"implemented, and\n" +"generally speaking, running the latest release will help your " +"performance.\n" +"If you haven't, install the latest " +"release." +msgstr "" + +#: i2p2www/pages/site/faq.html:420 +#, python-format +msgid "" +"See the\n" +"I2P Bittorrent FAQ" +msgstr "" + +#: i2p2www/pages/site/faq.html:427 +msgid "" +"\n" +"A tunnel to the main IRC server within I2P, Irc2P, is created when I2P is" +" installed (see\n" +"the I2PTunnel " +"configuration page),\n" +"and is automatically started when the I2P router starts. To connect to " +"it, tell your IRC\n" +"client to connect to localhost 6668. XChat-like client users" +" can create a\n" +"new network with the server localhost/6668 (remember to tick" +" "Bypass\n" +"proxy server" if you have a proxy server configured)." +msgstr "" + +#: i2p2www/pages/site/faq.html:438 +msgid "" +"For security purposes, the router's admin console by default only listens" +"\n" +"for connections on the local interface. However, with a little hacking,\n" +"you can make it reachable remotely:" +msgstr "" + +#: i2p2www/pages/site/faq.html:446 +msgid "" +"Open ~/.i2p/clients.config and replace
\n" +"clientApp.0.args=7657 ::1,127.0.0.1 ./webapps/
\n" +"with
\n" +"clientApp.0.args=7657 0.0.0.0 ./webapps/" +msgstr "" + +#: i2p2www/pages/site/faq.html:454 +msgid "" +"Go to http://localhost:7657/configui" +"\n" +"and add a console username and password if desired." +msgstr "" + +#: i2p2www/pages/site/faq.html:460 +msgid "" +"Go to http://localhost:7657/index.jsp" +"\n" +"and hit \"Graceful restart\", which restarts the JVM and reloads the " +"client applications" +msgstr "" + +#: i2p2www/pages/site/faq.html:467 +msgid "" +"After that fires up, you should now be able to reach your console " +"remotely. Reload the router at\n" +"http://127.0.0.1:7657 and you will be prompted for the username and " +"password you specified in step 2\n" +"above if your browser supports the authentication popup. Note: the\n" +"0.0.0.0 above specifies an interface, not a network " +"or netmask. 0.0.0.0\n" +"means \"bind to all interfaces\", so it can be reachable on " +"127.0.0.1:7657 as well as\n" +"any LAN/WAN IP." +msgstr "" + +#: i2p2www/pages/site/faq.html:478 +msgid "" +"By default, the router I2CP interface (port 7654) binds to address " +"127.0.0.1. To bind to 0.0.0.0, set the\n" +"router advanced configuration option " +"i2cp.tcp.bindAllInterfaces=true and restart." +msgstr "" + +#: i2p2www/pages/site/faq.html:483 +msgid "Whats an \"eepsite\"?" +msgstr "" + +#: i2p2www/pages/site/faq.html:485 +msgid "" +"An eepsite is a website that is hosted anonymously - you can access it by" +"\n" +"setting your web browser's HTTP proxy to use the web proxy (typically it\n" +"listens on localhost port 4444), and browsing to the site." +msgstr "" + +#: i2p2www/pages/site/faq.html:493 +#, python-format +msgid "" +"The proxy config for different browsers is on a \n" +"separate page with screenshots. More advanced configs with external " +"tools\n" +"are possible but could introduce leaks in your setup." +msgstr "" + +#: i2p2www/pages/site/faq.html:502 +msgid "" +"x is the number of peers you've sent or received a message from\n" +"successfully in the last minute, y is the number of peers seen in the " +"last\n" +"hour or so." +msgstr "" + +#: i2p2www/pages/site/faq.html:510 +msgid "" +"The SOCKS proxy is working as of release 0.7.1. SOCKS 4/4a/5 are " +"supported.\n" +"There is no SOCKS outproxy so it is of limited use." +msgstr "" + +#: i2p2www/pages/site/faq.html:514 +msgid "" +"In addition, many applications leak sensitive\n" +"information that could identify you on the Internet. I2P only filters\n" +"connection data, but if the program you intend to run sends this\n" +"information as content, I2P has no way to protect your anonymity. For\n" +"example, some mail applications will send the IP address of the machine\n" +"they are running on to a mail server. There is no way for I2P to filter\n" +"this, thus using I2P to 'socksify' existing applications is possible, but" +"\n" +"extremely dangerous." +msgstr "" + +#: i2p2www/pages/site/faq.html:524 +#, python-format +msgid "" +"If you would like more information on the socks proxy application anyway," +"\n" +"there are some helpful hints on the socks page." +msgstr "" + +#: i2p2www/pages/site/faq.html:531 +msgid "" +"Okay, here's a rundown of the default ports (everything is configurable\n" +"through various settings, of course):" +msgstr "" + +#: i2p2www/pages/site/faq.html:540 +msgid "" +"Internet-facing ports\n" +"Note: New installs as of release 0.7.8 do not use port 8887; they select " +"a random port\n" +"between 9000 and 31000 when the program is run for the first time.\n" +"The selected port is shown on the router configuration page." +msgstr "" + +#: i2p2www/pages/site/faq.html:548 +msgid "" +"Outbound UDP from the random port noted on the configuration page to " +"arbitrary remote UDP ports, allowing replies\n" +" " +msgstr "" + +#: i2p2www/pages/site/faq.html:553 +msgid "" +"Outbound TCP from random high ports to arbitrary remote TCP ports\n" +" " +msgstr "" + +#: i2p2www/pages/site/faq.html:558 +msgid "" +"(optional, but recommended) Inbound UDP to the port noted on configuration page from " +"arbitrary locations\n" +" " +msgstr "" + +#: i2p2www/pages/site/faq.html:563 +msgid "" +"(optional, but recommended) Inbound TCP to the port noted on configuration page from " +"arbitrary locations
\n" +"Inbound TCP may be disabled on the configuration page." +msgstr "" + +#: i2p2www/pages/site/faq.html:569 +msgid "" +"Outbound UDP on port 123, allowing replies
\n" +"This is necessary for I2P's internal time sync (via SNTP - \n" +"querying a random SNTP host in pool.ntp.org or another\n" +"server you specify)" +msgstr "" + +#: i2p2www/pages/site/faq.html:580 +msgid "" +"Local I2P ports, listening only to local connections by default,\n" +"except where noted:" +msgstr "" + +#: i2p2www/pages/site/faq.html:586 +msgid "" +"1900: UPnP SSDP UDP multicast listener.\n" +"Cannot be changed. Binds to all interfaces.\n" +"May be disabled on confignet.jsp." +msgstr "" + +#: i2p2www/pages/site/faq.html:593 +msgid "" +"2827: BOB bridge, a higher level socket API for clients\n" +"Disabled by default.\n" +"May be enabled/disabled on configclients.jsp.\n" +"May be changed in the bob.config file." +msgstr "" + +#: i2p2www/pages/site/faq.html:601 +msgid "" +"4444: HTTP proxy\n" +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" + +#: i2p2www/pages/site/faq.html:608 +msgid "" +"4445: HTTPS proxy\n" +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" + +#: i2p2www/pages/site/faq.html:615 +msgid "" +"6668: IRC proxy\n" +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" + +#: i2p2www/pages/site/faq.html:622 +msgid "" +"7652: UPnP HTTP TCP event listener.\n" +"Binds to the LAN address.\n" +"May be changed with advanced config i2np.upnp.HTTPPort=nnnn.\n" +"May be disabled on confignet.jsp." +msgstr "" + +#: i2p2www/pages/site/faq.html:630 +msgid "" +"7653: UPnP SSDP UDP search response listener.\n" +"Binds to all interfaces.\n" +"May be changed with advanced config i2np.upnp.SSDPPort=nnnn.\n" +"May be disabled on confignet.jsp." +msgstr "" + +#: i2p2www/pages/site/faq.html:638 +msgid "" +"7654: I2P Client Protocol port, used by client apps.\n" +"May be changed to a different port on\n" +"configclients.jsp" +"\n" +"but this is not recommended.\n" +"May be to bind to a different interface or all interfaces, or disabled, " +"on\n" +"configclients.jsp." +msgstr "" + +#: i2p2www/pages/site/faq.html:648 +msgid "" +"7655: UDP for SAM bridge, a higher level socket API for clients\n" +"Only opened when a SAM V3 client requests a UDP session.\n" +"May be enabled/disabled on configclients.jsp.\n" +"May be changed in the clients.config file with the SAM command line " +"option sam.udp.port=nnnn." +msgstr "" + +#: i2p2www/pages/site/faq.html:656 +msgid "" +"7656: SAM bridge, a higher level socket API for clients\n" +"Disabled by default for new installs as of release 0.6.5.\n" +"May be enabled/disabled on configclients.jsp.\n" +"May be changed in the clients.config file." +msgstr "" + +#: i2p2www/pages/site/faq.html:664 +msgid "" +"7657: Your router console\n" +"May be disabled in the clients.config file.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces in that file." +msgstr "" + +#: i2p2www/pages/site/faq.html:671 +msgid "" +"7658: Your eepsite\n" +"May be disabled in the clients.config file.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces in the jetty.xml file." +msgstr "" + +#: i2p2www/pages/site/faq.html:678 +msgid "" +"7659: Outgoing mail to smtp.postman.i2p\n" +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" + +#: i2p2www/pages/site/faq.html:685 +msgid "" +"7660: Incoming mail from pop.postman.i2p\n" +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" + +#: i2p2www/pages/site/faq.html:692 +msgid "" +"8998: mtn.i2p2.i2p (Monotone - disabled by default)\n" +"May be disabled or changed on the i2ptunnel page in the router " +"console.\n" +"May also be configured to be bound to a specific interface or all " +"interfaces." +msgstr "" + +#: i2p2www/pages/site/faq.html:699 +msgid "" +"31000: Local connection to the wrapper control channel port.\n" +"Outbound to 32000 only, does not listen on this port.\n" +"Starts at 31000 and will increment until 31999 looking for a free port.\n" +"To change, see the\n" +"wrapper documentation.\n" +"For more information see below." +msgstr "" + +#: i2p2www/pages/site/faq.html:709 +msgid "" +"32000: Local control channel for the service wrapper.\n" +"To change, see the\n" +"wrapper documentation.\n" +"For more information see below." +msgstr "" + +#: i2p2www/pages/site/faq.html:721 +msgid "" +"The local I2P ports and the I2PTunnel ports do not need to be reachable " +"from \n" +"remote machines, but *should* be reachable locally. You can also create" +" \n" +"additional ports for I2PTunnel instances via " +"http://localhost:7657/i2ptunnel/ \n" +"(and in turn, would need to get your firewall to allow you local access, " +"but \n" +"not remote access, unless desired)." +msgstr "" + +#: i2p2www/pages/site/faq.html:729 +msgid "" +"So, to summarize, nothing needs to be reachable by unsolicited remote " +"peers, but\n" +"if you can configure your NAT/firewall to allow inbound UDP and TCP the " +"outbound facing port, you'll" +"\n" +"get better performance. You will also need to be able to send outbound " +"UDP packets\n" +"to arbitrary remote peers (blocking IPs randomly with something like " +"PeerGuardian\n" +"only hurts you - don't do it)." +msgstr "" + +#: i2p2www/pages/site/faq.html:737 +msgid "Why is I2P listening on port 32000?" +msgstr "" + +#: i2p2www/pages/site/faq.html:739 +msgid "" +"The Tanuki java service wrapper that we use opens this port—bound " +"to localhost—in order \n" +"to communicate with software running inside the JVM. When the JVM is " +"launched it is given a key \n" +"so it can connect to the wrapper. After the JVM establishes its " +"connection \n" +"to the wrapper, the wrapper refuses any additional connections." +msgstr "" + +#: i2p2www/pages/site/faq.html:745 +msgid "" +"More information can be found in the \n" +"wrapper documentation." +msgstr "" + +#: i2p2www/pages/site/faq.html:752 +msgid "" +"An I2P router only needs to be seeded once, to join the network for the " +"first time.\n" +"Reseeding is nothing more than sending plain HTTP GET requests\n" +"to fetch a directory listing and download multiple \"routerInfo\" files\n" +"from a predefined reseed URL." +msgstr "" + +#: i2p2www/pages/site/faq.html:759 +msgid "" +"A typical symptom of a failed reseed is the \"Known\" indicator\n" +"(on the left sidebar of the router console) displaying a very small value" +"\n" +"(often less than 5) which does not increase. This can occur, among other " +"things,\n" +"if your firewall limits outbound traffic, and blocked the reseed request." +msgstr "" + +#: i2p2www/pages/site/faq.html:766 +msgid "To reseed an I2P router manually, do the following:" +msgstr "" + +#: i2p2www/pages/site/faq.html:769 +msgid "Stop your I2P router" +msgstr "" + +#: i2p2www/pages/site/faq.html:772 +msgid "" +"Open http://netdb.i2p2.de/ using a " +"web browser" +msgstr "" + +#: i2p2www/pages/site/faq.html:775 +msgid "Save a dozen \"routerInfo\" files to your I2P \"netDb\" directory" +msgstr "" + +#: i2p2www/pages/site/faq.html:782 +msgid "Start your I2P router" +msgstr "" + +#: i2p2www/pages/site/faq.html:789 +msgid "" +"When trying to start the router using \"i2prouter start\", you may see " +"output like the following:" +msgstr "" + +#: i2p2www/pages/site/faq.html:794 +msgid "" +"\n" +"In order to be inclusive and try to ensure that I2P will run on as many " +"systems \n" +"as possible, up until I2P 0.8.9 we used a java wrapper \n" +"compiled for FreeBSD 6.x. If you're receiving this error you most likely " +"are missing the necessary compatibility libraries.\n" +"These libraries may be installed by performing the following steps:" +msgstr "" + +#: i2p2www/pages/site/faq.html:802 +msgid "" +"Switch to the root user with su or log in as " +"root." +msgstr "" + +#: i2p2www/pages/site/faq.html:808 +#, python-format +msgid "" +"If you cannot install these compatibility libraries (or do not want to), " +"other\n" +"possibilities would be to compile the wrapper for your\n" +"system, starting I2P with the runplain.sh script, or you" +" can\n" +"replace the wrapper with one from the source tarball." +msgstr "" + +#: i2p2www/pages/site/faq.html:814 +msgid "" +"For the 0.8.9 release of I2P, the wrapper was upgraded to v3.5.12 and " +"compiled on systems running FreeBSD 7.2." +msgstr "" + +#: i2p2www/pages/site/faq.html:818 +msgid "" +"In wrapper.log I see an error that states \"Protocol " +"family unavailable\" when loading the Router Console" +msgstr "" + +#: i2p2www/pages/site/faq.html:820 +msgid "" +"Often this error will occur with any network enabled java software on " +"some systems that are configured to use IPv6 by default. There are a few " +"ways to solve this:" +msgstr "" + +#: i2p2www/pages/site/faq.html:825 +msgid "" +"On Linux based systems, you can echo 0 > " +"/proc/sys/net/ipv6/bindv6only" +msgstr "" + +#: i2p2www/pages/site/faq.html:827 +msgid "Look for the following lines in wrapper.config." +msgstr "" + +#: i2p2www/pages/site/faq.html:831 +msgid "" +"If the lines are there, uncomment them by removing the \"#\"s. If the " +"lines are not there, add them without the \"#\"s." +msgstr "" + +#: i2p2www/pages/site/faq.html:834 +msgid "" +"Another option would be to remove the ::1 from " +"~/.i2p/clients.config" +msgstr "" + +#: i2p2www/pages/site/faq.html:838 +msgid "" +"WARNING: For any changes to wrapper.config " +"to take effect, you must completely\n" +"stop the router and the wrapper. Clicking Restart on your\n" +"router console will NOT reread this file! You must\n" +"click Shutdown, wait 11 minutes, then start I2P." +msgstr "" + +#: i2p2www/pages/site/faq.html:849 +#, python-format +msgid "" +"Great! Find us on IRC irc.freenode.net #i2p or post to\n" +"the forum and we'll post it here (with\n" +"the answer, hopefully)." +msgstr "" + +#: i2p2www/pages/site/impressum.html:4 +msgid "German laws" +msgstr "" + +#: i2p2www/pages/site/index.html:2 +msgid "I2P Anonymous Network" +msgstr "" + +#: i2p2www/pages/site/index.html:4 +msgid "" +"Anonymous peer-to-peer distributed communication layer built with open " +"source tools and designed to run any traditional Internet service such as" +" email, IRC or web hosting." +msgstr "" + +#: i2p2www/pages/site/index.html:9 +msgid "What does I2P do for you?" +msgstr "" + +#: i2p2www/pages/site/index.html:10 +msgid "" +"The I2P network provides strong privacy protections for communication " +"over the Internet. Many activities that would risk your privacy on the " +"public Internet can be conducted anonymously inside I2P." +msgstr "" + +#: i2p2www/pages/site/index.html:11 +#, python-format +msgid "Get I2P %(version)s" +msgstr "" + +#: i2p2www/pages/site/index.html:15 +msgid "What is I2P?" +msgstr "" + +#: i2p2www/pages/site/index.html:17 +msgid "" +"I2P is an anonymous overlay network - a network within a network. It is " +"intended to protect communication from dragnet surveillance and " +"monitoring by third parties such as ISPs.\n" +msgstr "" + +#: i2p2www/pages/site/index.html:20 +msgid "" +"I2P is used by many people who care about their privacy: activists, " +"oppressed people, journalists and whistleblowers, as well as the average " +"person.\n" +msgstr "" + +#: i2p2www/pages/site/index.html:23 +msgid "" +"No network can be \"perfectly anonymous\". The continued goal of I2P is " +"to make attacks more and more difficult to mount. Its anonymity will get " +"stronger as the size of the network increases and with ongoing academic " +"review.\n" +msgstr "" + +#: i2p2www/pages/site/index.html:26 +msgid "" +"I2P is available on desktops, embedded systems (like the Raspberry Pi) " +"and Android phones. Help spread the word!\n" +msgstr "" + +#: i2p2www/pages/site/index.html:30 +msgid "Read more…" +msgstr "" + +#: i2p2www/pages/site/index.html:35 +msgid "What can you do with I2P?" +msgstr "" + +#: i2p2www/pages/site/index.html:38 +#, python-format +msgid "" +"Email: Integrated web mail interface," +" plugin for serverless email." +msgstr "" + +#: i2p2www/pages/site/index.html:43 +#, python-format +msgid "" +"Web browsing: Anonymous " +"websites, gateways to and from the public Internet." +msgstr "" + +#: i2p2www/pages/site/index.html:48 +#, python-format +msgid "" +"Blogging and forums: " +"Blogging and Syndie plugins." +msgstr "" + +#: i2p2www/pages/site/index.html:53 +#, python-format +msgid "" +"Website hosting: Integrated" +" anonymous web server." +msgstr "" + +#: i2p2www/pages/site/index.html:58 +#, python-format +msgid "" +"Real-time chat: Instant " +"messaging and IRC clients." +msgstr "" + +#: i2p2www/pages/site/index.html:63 +#, python-format +msgid "" +"File sharing: ED2K and " +"Gnutella clients, integrated BitTorrent client." +msgstr "" + +#: i2p2www/pages/site/index.html:68 +#, python-format +msgid "" +"Decentralized file " +"storage: Tahoe-LAFS distributed filesystem plugin." +msgstr "" + +#: i2p2www/pages/site/index.html:73 +#, python-format +msgid "More supported applications…" +msgstr "" + +#: i2p2www/pages/site/index.html:81 +msgid "News & Updates" +msgstr "" + +#: i2p2www/pages/site/links.html:4 +msgid "Recommended Links & Resources" +msgstr "" + +#: i2p2www/pages/site/links.html:5 +#, python-format +msgid "" +"See also the page with\n" +"links to presentations, videos, and tutorials about" +" I2P." +msgstr "" + +#: i2p2www/pages/site/links.html:12 +msgid "I2P on the web" +msgstr "" + +#: i2p2www/pages/site/links.html:20 +msgid "Friends of I2P" +msgstr "" + +#: i2p2www/pages/site/links.html:35 +msgid "More Projects and Documentation" +msgstr "" + +#: i2p2www/pages/site/links.html:45 +msgid "Press" +msgstr "" + +#: i2p2www/pages/site/links.html:49 +msgid "Boards, newssite, others" +msgstr "" + +#: i2p2www/pages/site/links.html:53 +msgid "Very Old Stuff" +msgstr "" + diff --git a/i2p2www/translations/it/LC_MESSAGES/blog.po b/i2p2www/translations/it/LC_MESSAGES/blog.po new file mode 100644 index 00000000..4a0b5e16 --- /dev/null +++ b/i2p2www/translations/it/LC_MESSAGES/blog.po @@ -0,0 +1,6142 @@ +# Italian translations for I2P. +# Copyright (C) 2016 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# Giuseppe Pignataro , 2014 +# khanjant , 2015 +# Sebastiano Pistore , 2015-2016 +# Jacopo Tumminello , 2014 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2016-07-02 11:09+0000\n" +"PO-Revision-Date: 2016-11-02 11:49+0000\n" +"Last-Translator: Sebastiano Pistore \n" +"Language-Team: Italian (http://www.transifex.com/otf/I2P/language/it/)\n" +"Plural-Forms: nplurals=2; plural=(n != 1)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=utf-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Generated-By: Babel 1.3\n" + +#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:24 +#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:11 +#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:25 +#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:12 +#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:12 +#: i2p2www/blog/2012/05/02/0.9-Release.rst:17 +#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:12 +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:16 +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:16 +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:26 +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:19 +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:19 +msgid "Files are available on the `download page`_." +msgstr "I file sono disponibili nella `Pagina download`_." + +#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:28 +#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:15 +#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:29 +#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:16 +#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:16 +#: i2p2www/blog/2012/05/02/0.9-Release.rst:21 +#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:16 +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:20 +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:20 +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:30 +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:23 +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:23 +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:39 +msgid "`download page`" +msgstr "`pagina di download`" + +#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:30 +#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:17 +#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:31 +#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:18 +#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:19 +#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:18 +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:22 +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:22 +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:32 +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:25 +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:79 +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:45 +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:13 +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:101 +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:26 +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:48 +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:34 +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:35 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:65 +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:29 +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:37 +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:32 +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:38 +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:36 +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:43 +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:27 +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:30 +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:44 +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:36 +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:34 +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:73 +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:53 +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:35 +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:54 +msgid "RELEASE DETAILS" +msgstr "DETTAGLIA DELLA RELEASE" + +#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:32 +#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:19 +#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:33 +#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:40 +#: i2p2www/blog/2012/05/02/0.9-Release.rst:50 +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:24 +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:24 +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:34 +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:103 +msgid "Major Changes" +msgstr "Cambiamenti Maggiori" + +#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:44 +#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:24 +#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:43 +#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:55 +#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:47 +#: i2p2www/blog/2012/05/02/0.9-Release.rst:58 +#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:43 +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:32 +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:30 +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:39 +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:81 +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:54 +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:112 +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:34 +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:51 +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:40 +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:41 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:76 +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:39 +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:50 +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:35 +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:51 +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:55 +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:53 +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:30 +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:40 +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:57 +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:52 +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:42 +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:80 +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:63 +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:47 +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:71 +msgid "Bug Fixes" +msgstr "Bug Fixes" + +#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:54 +#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:30 +#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:47 +#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:69 +#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:63 +#: i2p2www/blog/2012/05/02/0.9-Release.rst:68 +#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:54 +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:41 +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:36 +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:51 +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:43 +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:94 +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:63 +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:19 +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:118 +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:52 +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:99 +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:49 +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:47 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:87 +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:49 +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:57 +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:42 +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:60 +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:68 +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:65 +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:38 +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:49 +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:75 +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:65 +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:50 +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:89 +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:76 +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:53 +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:83 +msgid "Other" +msgstr "Altro" + +#: i2p2www/blog/2011/10/11/0.8.9-Release.rst:73 +#: i2p2www/blog/2011/10/20/0.8.10-Release.rst:36 +#: i2p2www/blog/2011/11/08/0.8.11-Release.rst:51 +#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:82 +#: i2p2www/blog/2012/02/27/0.8.13-Release.rst:75 +#: i2p2www/blog/2012/05/02/0.9-Release.rst:96 +#: i2p2www/blog/2012/07/30/0.9.1-Release.rst:76 +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:52 +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:56 +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:67 +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:56 +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:110 +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:79 +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:30 +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:129 +#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:27 +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:76 +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:64 +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:59 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:104 +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:62 +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:73 +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:52 +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:76 +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:86 +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:81 +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:61 +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:69 +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:101 +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:75 +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:56 +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:115 +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:105 +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:76 +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:96 +msgid "SHA256 Checksums:" +msgstr "SHA256 Checksum:" + +#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:39 +msgid "Major changes" +msgstr "Cambiamenti maggiori" + +#: i2p2www/blog/2012/01/06/0.8.12-Release.rst:47 +msgid "Wrapper Update" +msgstr "Aggiornamento wrapper" + +#: i2p2www/blog/2012/05/02/0.9-Release.rst:23 +msgid "Update Info" +msgstr "Dettagli dell'aggiornamento" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:2 +msgid "0.9.2 Release" +msgstr "Release 0.9.2" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:7 +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:9 +msgid "" +"0.9.2 includes extensive low-level changes to improve the performance and" +" efficiency of the router. We have updated our UPnP library, to hopefully" +" make UPnP work for more people. I2PSnark now has DHT support, but it is " +"not yet enabled by default, as we plan to do more testing during the " +"upcoming 0.9.3 development cycle." +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:12 +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:12 +msgid "" +"As usual, there's also lots of bug fixes in this release, so updating is " +"recommended." +msgstr "" +"Come al solito ci sono molti bug risolti in questa release, ed è quindi " +"raccomandato aggiornare." + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:26 +msgid "" +"SSU: Fix several problems in our UDP transport, to improve efficiency and" +" reliability for connection setup. Also improve defenses against various " +"types of bad input." +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:27 +msgid "" +"UPnP: Updated our library to fix several issues, should work for more " +"routers now" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:28 +msgid "" +"Transport: Improve performance in both our TCP and UDP transports, to " +"benefit high-bandwidth routers" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:29 +msgid "" +"Crypto: The thresholds and number of ElGamal/AES Session Tags delivered " +"are now much more flexible, which should lessen protocol overhead and " +"reduce stalls caused by dropped tags." +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:30 +msgid "" +"I2PSnark: Add DHT support, not yet enabled by default, will do further " +"testing and plan to enable by default in 0.9.3." +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:34 +msgid "" +"Fix various issues affecting memory usage and performance on high-" +"bandwidth routers" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:35 +msgid "Fix problems in UDP for routers using a reduced-MTU connection, e.g. a VPN" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:36 +msgid "Fix i2psnark bug that prevented a completion announcement to the tracker" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:37 +msgid "Fix a lock contention problem in i2ptunnel" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:38 +msgid "Fix some OSX installation issues" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:39 +msgid "Remove uses of direct byte buffers that may have been leaking" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:43 +msgid "Reduce overhead in network messages" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:44 +msgid "Add \"universal\" theme support" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:45 +msgid "Theme updates" +msgstr "Aggiornamento temi" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:46 +msgid "Add a jbigi library for Raspberry Pi" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:47 +msgid "New Scala unit test framework" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:48 +msgid "Translation updates for Czech, Dutch, German, and Greek" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:49 +msgid "Update wrapper to 3.5.15 (new installs and PPA only)" +msgstr "" + +#: i2p2www/blog/2012/09/21/0.9.2-Release.rst:50 +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:53 +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:63 +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:53 +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:108 +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:77 +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:127 +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:74 +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:62 +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:57 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:100 +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:58 +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:70 +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:49 +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:83 +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:78 +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:58 +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:66 +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:96 +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:72 +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:53 +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:112 +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:97 +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:68 +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:88 +msgid "Update GeoIP data (new installs and PPA only)" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:2 +msgid "0.9.3 Release" +msgstr "Release 0.9.3" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:7 +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:9 +msgid "" +"0.9.3 includes extensive low-level changes to the queueing of messages in" +" the router. We implement the CoDel Active Queue Management (AQM) " +"algorithm. We also unify the queueing and priority mechanisms in the " +"transports to aid diagnosis and reduce network latency. Work continues " +"on fixing UDP transport bugs and making UDP more resistant to attacks. " +"There are more changes to improve the performance of the router and " +"reduce its memory usage. Also, we enable i2psnark's DHT support, " +"introduced last release, by default." +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:26 +msgid "Active Queue Management" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:27 +msgid "Priority queues" +msgstr "Code di prorità" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:28 +msgid "I2PSnark DHT: Several bug fixes, enable by default." +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:32 +msgid "" +"Several SSU fixes including memory leak, and better handling of routers " +"behind firewalls that change UDP ports; additional defenses for malicious" +" packets." +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:33 +msgid "Fix piece selection (rarest-first) bugs in i2psnark" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:34 +msgid "Fix bug causing multiple browsers to open at startup" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:38 +msgid "Improvements in caching" +msgstr "Miglioramento gestione della cache" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:39 +msgid "Several synchronization fixes and lock contention reduction" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:40 +msgid "Major reduction in SSU buffers memory use" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:41 +msgid "" +"Fix streaming connection timeout back to 1 minute, was inadvertently " +"changed to 5 minutes; set i2ptunnel server read timeout to 5 minutes, was" +" unlimited" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:42 +msgid "Improved defenses in i2ptunnel for \"darkloris\"" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:43 +msgid "More validation at torrent creation in i2psnark" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:44 +msgid "Several parameter changes in SSU to improve throughput" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:45 +msgid "" +"New event log for major events including restarts; show multiple restart " +"lines on graphs" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:46 +msgid "Remove duplicate messages from logs" +msgstr "Rimozione dei messaggi duplicati dai log" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:47 +msgid "Don't respond to blocked streaming connections with a reset, just drop" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:48 +msgid "Remove all uses of inefficient SimpleTimer" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:49 +msgid "More checks for valid IPs and ports entered in console" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:50 +msgid "Fix bug that wasted a lot of entropy" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:51 +msgid "Translation updates: Italian, Portuguese, Spanish, Swedish" +msgstr "" + +#: i2p2www/blog/2012/10/27/0.9.3-Release.rst:52 +msgid "Add non-NIO configuration in jetty.xml, recommended for Java 5" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:2 +msgid "0.9.4 Release" +msgstr "Release 0.9.4" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:7 +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:9 +msgid "" +"0.9.4 includes a fix for a network capacity bug, introduced in 0.9.2, " +"that was reducing network performance and reliability. It also includes " +"major changes in the in-network update system, and adds the capability to" +" update via in-network torrents." +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:13 +msgid "" +"We fixed several bugs in the i2psnark DHT implementation that was " +"introduced\n" +"last release. For those of you using console or http proxy passwords,\n" +"we converted to the more-secure digest method and improved the security " +"for console forms." +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:19 +msgid "" +"For those of you already running development builds, your router should " +"automatically\n" +"update to 0.9.4-0 using the new in-network torrent facility.\n" +"For those running 0.9.3-0, you will update normally using in-network " +"HTTP, and\n" +"we will have more information for you when we release 0.9.5." +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:36 +msgid "" +"Big rework of the update system; Preliminary support for updates via " +"i2psnark" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:37 +msgid "Add per-destination outbound priorities" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:41 +msgid "" +"Fix major bug that reduced SSU connection limits which reduced tunnel " +"build success rates" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:42 +msgid "Fix bug with external I2CP that prevented some external apps from working" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:43 +msgid "Fixed several bugs in i2psnark DHT" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:44 +msgid "Fixed bug in i2psnark PEX that inflated peer counts" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:45 +msgid "Handle dropped I2CP messages better" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:46 +msgid "Reduce overhead of I2CP messages" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:47 +msgid "Enforce max size in transport outbound message queues" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:48 +msgid "Fixes for Windows eepget.bat (new installs and PPA only)" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:49 +msgid "Fix a bug that would drop messages of exactly 512 bytes in SSU" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:53 +msgid "" +"More performance improvements, memory reduction, and object churn " +"reduction" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:54 +msgid "Better detection of network disconnections" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:55 +msgid "Further improvements in the SSU transport" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:56 +msgid "Add console password form" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:57 +msgid "" +"Convert http proxy and console from basic to digest authentication for " +"added security" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:58 +msgid "" +"Improved verification of console form submissions, using jsp sessions. " +"Cookies may now be required on forms, except when the console password is" +" enabled" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:59 +msgid "" +"Initial work on new interfaces to manage applications started via " +"clients.config" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:60 +msgid "Increase minimum peer port to 1024" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:61 +msgid "Increase granularity of bandwidth limiter for smoother transmissions" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:62 +msgid "" +"Translation updates: Chinese, French, German, Italian, Polish, " +"Portuguese, Swedish, and Ukrainian" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:64 +msgid "Update wrapper to 3.5.16 (new installs and PPA only)" +msgstr "" + +#: i2p2www/blog/2012/12/17/0.9.4-Release.rst:65 +msgid "New ARMv6 wrapper for Raspberry Pi" +msgstr "Nuovo wrapper ARMv6 per Raspeberry Pi" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:2 +msgid "0.9.5 Release" +msgstr "Release 0.9.5" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:7 +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:9 +msgid "" +"0.9.5 includes bug fixes and defenses for some issues and vulnerabilities" +" that are being investigated by researchers at UCSB. We continue to work " +"with them on additional improvements. This is a good opportunity to " +"remind the community that while our network continues to grow rapidly, it" +" is still relatively small. There may be multiple weaknesses or bugs that" +" could compromise your anonymity. Help us grow the network by spreading " +"the word and contributing where you can." +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:13 +#, python-format +msgid "" +"In this upgrade cycle, a random 1%(pc)s of routers, (plus all routers " +"running a\n" +"development build) will attempt to update via the experimental in-network" +" bittorrent\n" +"with i2psnark. If this doesn't work, it should fall back to standard in-" +"network HTTP update." +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:27 +msgid "Defenses and Bug Fixes" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:29 +msgid "Fix router bug causing lockup when using iMule" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:30 +msgid "Recognize, handle, reject duplicate tunnel IDs" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:31 +msgid "Fix changing of the log file name" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:32 +msgid "Prevent hashcode attack in session tags" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:33 +msgid "Add build request throttler based on previous hop" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:34 +msgid "Limit concurrent next-hop lookups" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:35 +msgid "Catch exceptions storing nonces in console" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:36 +msgid "Fix saving graph settings in console" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:37 +msgid "Fix eepget generation of URLs when not proxied" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:38 +msgid "" +"Encrypt database lookup messages end-to-end when sent through exploratory" +" tunnels" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:39 +msgid "Don't use multiple floodfills from the same /16 in a query" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:40 +msgid "Randomize delay before verifying floodfill store" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:41 +msgid "Increase number of floodfills" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:45 +msgid "Improve support for mobile browsers" +msgstr "Migliorato il supporto ai browser mobile" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:46 +msgid "Partial defenses for UCSB attacks" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:47 +msgid "Add announce list support to i2psnark" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:48 +msgid "Jetty: upgrade Apache Tomcat to 6.0.36" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:49 +msgid "Split router info files into multiple subdirectories" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:50 +msgid "Add IP to hostname mapping option in SOCKS" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:51 +msgid "Improve PRNG seeding" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:52 +msgid "" +"Translation updates: French, German, Hungarian, Italian, Norwegian, " +"Polish, Portuguese, Russian, Swedish" +msgstr "" + +#: i2p2www/blog/2013/03/08/0.9.5-Release.rst:54 +msgid "Update wrapper to 3.5.17 (new installs and PPA only)" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:2 +msgid "0.9.6 Release" +msgstr "Release 0.9.6" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:7 +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:9 +msgid "" +"0.9.6 includes bug fixes and an update from Jetty 6.1.26 (2010-11-10) to " +"Jetty 7.6.10 (2013-03-12). See below for important information on the " +"Jetty update. The Jetty 7 series is actively maintained and we plan to " +"stay current with it in future I2P releases." +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:13 +msgid "" +"Most users will update via HTTP. Those running development builds will " +"attempt to update via the\n" +"experimental in-network bittorrent with i2psnark. We've fixed some bugs " +"that will enable more users\n" +"to update via torrent in the 0.9.7 update cycle." +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:25 +msgid "Important fix for Windows Eepsites, first install 0.9.5 only" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:27 +msgid "" +"If you first installed I2P with version 0.9.5, on Windows only, we " +"recommend that you follow the\n" +"following instructions to fix your eepsite location **before** you update" +" to 0.9.6.\n" +"Only original installations of 0.9.5-0 on Windows are affected by this " +"issue. If your router version\n" +"is 0.9.5-0-win1, you already have the fix and need not take any action." +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:34 +msgid "See `this page`_ for instructions." +msgstr "Consulta `questa pagina`_ per le istruzioni." + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:38 +msgid "`this page`" +msgstr "`questa pagina`" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:40 +msgid "Jetty 7 Migration Details" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:42 +msgid "" +"For most people, the update should just work. If you have multiple Jetty " +"eepsites,\n" +"OR have made changes to jetty.xml or other Jetty configuration files, " +"including changing the port\n" +"from 7658, you MUST take manual action AFTER updating." +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:48 +msgid "" +"After update, the router will migrate your jetty.xml files to the new " +"Jetty 7 format." +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:50 +msgid "" +"The migration resets the port to 7658. If you have more than one Jetty " +"eepsite, OR your eepsite\n" +" is NOT on port 7658, OR you have made other modifications to jetty.xml " +"(for example changing the\n" +" listen address from 127.0.0.1 to 0.0.0.0), you MUST edit the jetty.xml " +"file for each eepsite to fix them up\n" +" after updating, and restart again." +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:55 +msgid "" +"**The following files will be backed up with a ".jetty6" suffix" +" and then migrated.**\n" +"If you have made local changes, you may have to edit them manually and " +"restart.\n" +"See http://wiki.eclipse.org/Jetty for assistance in configuring Jetty 7." +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:69 +msgid "Plugins" +msgstr "Plugin" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:71 +msgid "Most plugins should work fine with Jetty 7." +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:75 +msgid "" +"The I2PControl and zzzot plugins must be updated. Your router should " +"download and install the new versions shortly after starting 0.9.6." +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:77 +msgid "If a plugin does not work, please contact the maintainer for that plugin." +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:83 +msgid "Several bugs with Windows installation (see above)" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:84 +msgid "Fix default form action in i2ptunnel" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:85 +msgid "Fix links on iframed console pages" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:86 +msgid "Better detection of 64-bit Windows to prevent crashes by systray" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:87 +msgid "Fix bug preventing router update via torrent" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:88 +msgid "Several SSU fixes for NATs that change UDP ports" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:89 +msgid "" +"Ignore unsupported IPs in RouterInfos when selecting an address (prep for" +" IPv6)" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:90 +msgid "" +"Ignore unused option bits in Database Lookup Message (prep for requesting" +" encrypted response)" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:91 +msgid "Fix HTTP proxy error response for malformed URIs" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:92 +msgid "Recognize UPnP devices without port forwarding capability" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:96 +msgid "Jetty 7.6.10 (see above for migration information)" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:97 +msgid "Limit page size in i2psnark" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:98 +msgid "Add data directory and page size configuration to i2psnark" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:99 +msgid "Support multiple i2psnark instances" +msgstr "Supporto ad istanze multiple di i2psnark" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:100 +msgid "Piece size adjustments in i2psnark" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:101 +msgid "Add more graphing support for combined bandwidth graph" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:102 +msgid "Block b32.i2p supercookies" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:103 +msgid "Allow stopping clients on /configclients" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:104 +msgid "Check for nonce count replays in HTTP client" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:105 +msgid "Support SASL authentication in IRC proxy" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:106 +msgid "Several cleanups and minor fixes in the update manager" +msgstr "" + +#: i2p2www/blog/2013/05/28/0.9.6-Release.rst:107 +msgid "Translation updates: German, Portuguese, Russian, Spanish, and Swedish" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:2 +msgid "0.9.7 Release" +msgstr "Release 0.9.7" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:7 +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:9 +msgid "0.9.7 includes significant bug fixes and improvements." +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:11 +msgid "" +"For the first time, class 'N' routers (those with a minimumum of 128 " +"KBytes/sec of shared bandwidth)\n" +"will automatically become floodfill (previously it was only 'O' routers " +"with 256 KBps). This will\n" +"increase the floodfill population for additional resistance to certain " +"attacks (see below). Floodfill routers\n" +"don't consume much additional bandwidth, but they do tend to use " +"additional memory and concurrent\n" +"connections. If you do not wish your router to become floodfill, set the " +"advanced configuration\n" +"router.floodfillParticipant=false ." +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:20 +#, python-format +msgid "" +"As we think the last release fixed the experimental update-via-torrent " +"bugs, 3%(pc)s of routers should\n" +"update over in-network bittorrent this cycle." +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:25 +msgid "" +"Plugin update checks, possibly broken for several releases, are fixed. " +"Your plugins should once again\n" +"auto-update after updating the router." +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:30 +msgid "" +"We fixed a major streaming timer bug that contributed to frequent IRC " +"disconnects." +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:34 +msgid "" +"This release contains additional mitigations for the `\"practical " +"attacks\" paper`_.\n" +"However, we have a lot more work to do to resist Sybil attacks on the " +"floodfills, and resist\n" +"traffic analysis at the gateways and endpoints of exploratory tunnels.\n" +"It's a good reminder for everybody that our network is still relatively " +"small and vulnerable.\n" +"We don't currently recommend any uses that would put anybody in serious " +"jeopardy.\n" +"We'll keep working to improve it... please keep working to spread the " +"word. A bigger network is a better network." +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:43 +msgid "`\"practical attacks\" paper`" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:47 +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:15 +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:107 +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:28 +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:36 +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:37 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:67 +msgid "Anonymity Improvements" +msgstr "Miglioramenti all'anonimato" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:49 +msgid "End-to-end encryption of responses to leaseset lookups" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:50 +msgid "Expand floodfill pool by enabling class 'N' floodfills" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:51 +msgid "Randomize padding inside encrypted SSU packets" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:52 +msgid "Preparation for better SSU protocol obfuscation" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:56 +msgid "Fix newer lease sets not getting stored or published" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:57 +msgid "" +"Fix classpath bug when used with 4-year-old installations, causing the " +"console not to start" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:58 +msgid "Fix addressbook database bug preventing update of the reverse index" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:59 +msgid "" +"Fix i2psnark bug that changed the infohash of torrents created by Robert " +"and fetched via magnet link" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:60 +msgid "Fix version checking for plugins" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:61 +msgid "" +"Fix a streaming timer bug causing frequent IRC disconnects (also affects " +"other close-on-idle tunnels)" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:65 +msgid "Don't install as a service on Windows by default" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:66 +msgid "Reduce transport idle timeouts" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:67 +msgid "Reduce tunnels on idle in i2psnark" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:68 +msgid "Change default in i2ptunnel GUI to 3 hops" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:69 +msgid "IE 10 support" +msgstr "Supporto IE 10" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:70 +msgid "" +"Individual expiration times in leases, for efficiency on destinations " +"with a high number of tunnels" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:71 +msgid "Low-level encryption and XOR speedups" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:72 +msgid "Jetty 7.6.11" +msgstr "Jetty 7.6.11" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:73 +msgid "Tomcat 6.0.37" +msgstr "Tomcat 6.0.37" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:74 +msgid "Translation updates: Chinese, French, German, Portuguese, Russian, Spanish" +msgstr "" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:75 +msgid "New Turkish translation" +msgstr "Nuova traduzione turca" + +#: i2p2www/blog/2013/07/15/0.9.7-Release.rst:76 +msgid "Wrapper 3.5.19 (new installs and PPA only)" +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:2 +msgid "0.9.7.1 Release" +msgstr "Reelase 0.9.7.1" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:7 +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:9 +msgid "" +"This unscheduled release disables the RouterInfo verification messages " +"that were used in the attack published in the UCSB paper, which should " +"make correlating a LeaseSet and a Router much more difficult. We have " +"also included a limited number of other fixes listed below. Our 0.9.8 " +"release, which will include IPv6 support, is still on-schedule for late " +"September." +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:11 +msgid "As usual, we recommend that all users update to this release." +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:17 +msgid "Disable RouterInfo verification messages" +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:21 +msgid "Extend inbound tunnel expiration" +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:22 +msgid "i2prouter: bashism fix" +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:23 +msgid "i2psnark: increase max piece size, mime type updates" +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:24 +msgid "New reseed host" +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:25 +msgid "New update hosts, thanks Meeh and dg" +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:26 +msgid "Streaming: RTO changes" +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:27 +msgid "Updater: Increase update-via-torrent to 30 percent" +msgstr "" + +#: i2p2www/blog/2013/08/10/0.9.7.1-Release.rst:28 +msgid "UPnP fix for some hardware" +msgstr "Risolti problemi compatibilità UPnP con diversi dispositivi hardware" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:2 +msgid "0.9.8 Release" +msgstr "Release 0.9.8" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:7 +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:9 +msgid "" +"0.9.8 includes the long-awaited support for IPv6. It's enabled by " +"default, but of course you need a public IPv6 address to use it. " +"Configuration is on the 'network' configuration tab in your console. We " +"also have anonymity improvements including padding of SSU packets and " +"longer router private keys." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:11 +#, python-format +msgid "30%(pc)s of you will update via in-network torrent in this update cycle." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:13 +msgid "IPv6 Details" +msgstr "Dettagli su IPv6" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:15 +msgid "" +"IPv6 is enabled and preferred by default. If you have a public IPv6 " +"address \n" +"and you are connecting to another router with a published IPv6 address, " +"it will \n" +"connect via IPv6. There is a new IPv6 configuration section on /confignet" +" in \n" +"the router console. If IPv6 is causing problems you may disable it there." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:22 +msgid "" +"As a part of the IPv6 development effort, I2P now supports multiple \n" +"published IP addresses. If you have multiple public IP addresses (IPv4, " +"IPv6, \n" +"or both), you may enable or disable them individually on /confignet. The" +" \n" +"default is to use the first IPv4 and IPv6 addresses it discovers. If you " +"have \n" +"multiple addresses you should review the configuration on /confignet and " +"adjust \n" +"it if necessary.\n" +"Note that while you may enable multiple IPv4 and IPv6 addresses on " +"/confignet,\n" +"we recommend that you use only one IPv4 and one IPv6 address. There are\n" +"bugs still to be fixed with multiple addresses of each type." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:34 +msgid "" +"While IPv6 support was designed and developed over several years, it has" +" \n" +"only been tested by a limited number of users and is still beta. If you " +"do have \n" +"a public IPv6 address, please monitor your router and the logs for " +"problems, \n" +"and disable it necessary. Please report any bugs on \n" +"http://trac.i2p2.i2p." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:42 +msgid "Rekeying Details" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:44 +msgid "" +"For those of you running I2P on faster hardware (generally, 64-bit x86) " +"the \n" +"router will generate a new identity using longer keys. This will " +"substantially \n" +"reduce your participating traffic for 48 hours or more, while your router" +" \n" +"re-integrates into the network. Due to the new keys, the large number of" +" \n" +"torrent updates, and the recent network growth, we expect substantial \n" +"disruption to the network for a week or more after the update is " +"released. \n" +"Please be patient and things should start to improve after a few days." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:54 +msgid "" +"These changes may result in higher CPU usage for some of you. We're doing" +" \n" +"our best to increase efficiency, but stronger security generally requires" +" more \n" +"computation. Performance may also be poor during the first week\n" +"due to the network churn.\n" +"We will evaluate the network performace before deciding whether to\n" +"change the key length on slower hardware in a future release." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:63 +msgid "" +"We are experiencing rapid network growth in the last few weeks, which is" +" \n" +"causing a bit of a bumpy ride for some, especially on weekends. However, " +"the \n" +"network is still performing fairly well, so keep spreading the word." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:69 +msgid "More Changes Coming" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:71 +msgid "" +"We're in the initial stages of desiging major changes to strengthen our \n" +"crypto. Stronger crypto will use more CPU and it may possibly \n" +"require a Java 7 JRE at a minimum. We understand your desire to run I2P " +"on low-power \n" +"and/or older hardware. We're working hard to minimize the impacts, but " +"some \n" +"loss of performance is inevitable. In addition, Java 5 and 6 are no " +"longer \n" +"supported by Oracle. Now is a good time to upgrade to Java 7. Any change " +"in \n" +"minimum requirements will be announced well in advance." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:81 +msgid "New Website" +msgstr "Nuovo sito web" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:83 +msgid "" +"After a heroic effort by str4d, the new website preview is available at \n" +"http://i2hq.srv.i2p2.de. We hope to see it go live at \n" +"https://geti2p.net and http://www.i2p2.i2p soon. Please \n" +"contribute to the new website translations on Transifex, especially the \n" +"website_priority resource." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:91 +msgid "Community Participation" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:93 +msgid "" +"In early August, hottuna and zzz attended DEFCON 21 in Las Vegas.\n" +"Last weekend, echelon attended the CTS IV conference in Berlin and\n" +"psi attended the Tahoe-LAFS hackfest at GNU 30 in Cambridge, Mass.\n" +"Several of us will be at 30C3 in Hamburg late this year.\n" +"It's great to see people participating at these events and representing " +"I2P." +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:105 +msgid "IPv6 support for both NTCP and SSU" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:109 +msgid "SSU protocol obfuscation by adding random padding" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:110 +msgid "Longer encryption and DH private keys for users on faster platforms" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:114 +msgid "Fix I2PTunnel / I2CP locking and duplicates (partial)" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:115 +msgid "Fix translation of HTTP proxy error pages" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:116 +msgid "Fix occasional runtime exception in NTCP" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:120 +msgid "Big rework of transport code to accommodate multiple addresses and IPv6" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:121 +msgid "Streaming: Improved recovery from lost acks, other fixes" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:122 +msgid "Use Transifex for translation of initial news and HTTP proxy error pages" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:123 +msgid "" +"Translation updates: Chinese, French, German, Portuguese, Russian, " +"Swedish, Turkish" +msgstr "" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:124 +msgid "New Romanian translation" +msgstr "Nuova traduzione in romeno" + +#: i2p2www/blog/2013/09/30/0.9.8-Release.rst:126 +msgid "Wrapper 3.5.20 (new installs and PPA only)" +msgstr "" + +#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:2 +msgid "0.9.8.1 Release" +msgstr "Release 0.9.8.1" + +#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:7 +#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:9 +msgid "" +"0.9.8.1 fixes a problem with updating to 0.9.8 on Windows for some " +"people. New installs and non-Windows platforms are not affected, however " +"all platforms will automatically update even if running 0.9.8." +msgstr "" + +#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:11 +msgid "" +"See the `Trac ticket`_ for details and workarounds. See\n" +"`the 0.9.8 release notes`_ for information on IPv6 and other changes." +msgstr "" + +#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:16 +msgid "" +"Due to recent attacks, logins are disabled on `Trac`_ and new " +"registrations are\n" +"disabled on `zzz.i2p`_. Until those services are restored, please report " +"all\n" +"bugs on IRC freenode or IRC2P #i2p-dev." +msgstr "" + +#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:22 +msgid "`Trac ticket`" +msgstr "" + +#: i2p2www/blog/2013/10/02/0.9.8.1-Release.rst:23 +msgid "`the 0.9.8 release notes`" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:2 +msgid "0.9.9 Release" +msgstr "Release 0.9.9" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:7 +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:9 +msgid "" +"0.9.9 fixes a number of bugs in the netdb, streaming, and i2ptunnel, and " +"starts work on a year-long plan to increase the strength of the " +"cryptographic signing algorithms used in the router, and support multiple" +" algorithms and key lengths simultaneously. Automatic update files will " +"now be signed with 4096-bit RSA keys." +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:11 +msgid "" +"We now support SSL between your router and your servers for security.\n" +"See `this development thread`_ for more information." +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:16 +msgid "`this development thread`" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:18 +msgid "" +"As usual, we recommend that you update to this release.\n" +"The best way to maintain security and help the network is to run the " +"latest release.\n" +"Several members of the I2P team will be at 30C3 in Hamburg this year.\n" +"Come say hello and ask for an I2P sticker.\n" +"Thanks to everyone for their support this year." +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:30 +msgid "Don't build client tunnels through zero-hop exploratory tunnels" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:31 +msgid "New \"su3\" file support using stronger keys" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:32 +msgid "Use su3 for updates" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:36 +msgid "Issues with losing data when closing streams" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:37 +msgid "Fix various streaming connection limit issues" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:38 +msgid "Issues with resource usage of closed connections" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:39 +msgid "Clean up timer threads in close-on-idle tunnels" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:40 +msgid "Several other streaming fixes" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:41 +msgid "Reject more non-public IPv6 addresses" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:42 +msgid "Fix IPv6 GeoIP" +msgstr "Corretto IPv6 GeoIP" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:43 +msgid "Fix peer selection in first minutes after startup" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:44 +msgid "Several I2PTunnel bug fixes" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:45 +msgid "Fix major i2psnark DHT bug that prevented magnets from working well" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:46 +msgid "" +"Fix client tunnels that fail due to name resolution failure at startup, " +"particularly with b32 hostnames" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:47 +msgid "Fix changing client i2ptunnel target list" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:48 +msgid "" +"Fix major bugs preventing reception of encrypted responses to leaseset " +"lookups and verifies" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:49 +msgid "Fix bad links on some i2psnark buttons in Opera and text-mode browsers" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:50 +msgid "Fix NPE in Susimail" +msgstr "Corretto NPE di SusiMail" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:54 +msgid "Start work on supporting stronger signing keys in the router" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:55 +msgid "Reduce thread usage for HTTP Server tunnels" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:56 +msgid "Auto-stop update torrent after some time" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:57 +msgid "Add ability to stop webapp via console" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:58 +msgid "New POST throttler in HTTP server tunnel" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:59 +msgid "Improve connection throttling" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:60 +msgid "More work to reduce number of connections" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:61 +msgid "Re-enable router info expiration job" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:62 +msgid "" +"Extend router info expiration and other changes to reduce load on " +"floodfills" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:63 +msgid "Support multiple servers through a single server tunnel" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:64 +msgid "Support specification of server port in i2ptunnel clients" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:65 +msgid "Add support for SSL connections from i2ptunnel to external server" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:66 +msgid "SSL and crypto code refactoring" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:67 +msgid "i2psnark storage code refactoring" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:68 +msgid "New destination cache" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:69 +msgid "Lots of code cleanup and resolution of findbugs warnings" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:70 +msgid "New Japanese translation (partial)" +msgstr "Nuova traduzione in Giapponese (parziale)" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:71 +msgid "" +"Translation updates: French, German, Italian, Romanian, Russian, Spanish," +" Swedish, and others" +msgstr "" + +#: i2p2www/blog/2013/12/07/0.9.9-Release.rst:73 +msgid "Wrapper 3.5.22 (new installs and PPA only)" +msgstr "" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:1 +msgid "" +"=====================\n" +"Syndie 1.105b Release\n" +"=====================" +msgstr "" +"=====================\n" +"Release di Syndie 1.105b\n" +"=====================" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:9 +msgid "Update to HSQLDB 2.3.1" +msgstr "Aggiornato a HSQLDB 2.3.1" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:11 +msgid "" +"This is the first stable release since February 2013.\n" +"It is essentially the same as 1.104b-7-rc, with some translation updates." +msgstr "" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:16 +msgid "" +"All binaries and source packages are at `syndie.de`_ and `syndie.i2p`_.\n" +"Plugins are available at `plugins.i2p`_ and `stats.i2p`_." +msgstr "" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:21 +msgid "" +"For those of you upgrading from 1.103b, you will find syndie startup and " +"shutdown much faster due to the new version of HSQLDB." +msgstr "" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:25 +msgid "" +"If you have a large database or an identity you wish to preserve,\n" +"you may wish to back up your entire ~/.syndie directory before you start." +"\n" +"The upgrade process does make its own backup, however you may find it " +"easier to use your own backup if the upgrade fails." +msgstr "" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:31 +msgid "" +"Upgrades from 1.103b may fail for some people due to database corruption " +"due to bugs in the old HSQLDB.\n" +"Unfortunately, we don't know how to fix it.\n" +"Your alternatives are to start over with a clean database, or stay with " +"1.103b forever.\n" +"Sorry about that." +msgstr "" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:43 +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:29 +msgid "" +"As usual, we recommend that you update to this release.\n" +"The best way to maintain security and help the network is to run the " +"latest release." +msgstr "" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:56 +msgid "GUI Improvements and Fixes" +msgstr "" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:72 +msgid "Syndication" +msgstr "" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:83 +msgid "Database" +msgstr "Database" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:104 +msgid "New translations" +msgstr "Nuove traduzioni" + +#: i2p2www/blog/2014/01/21/Syndie-1.105b-Release.rst:105 +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:60 +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:56 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:99 +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:57 +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:69 +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:72 +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:82 +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:77 +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:57 +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:65 +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:95 +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:71 +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:52 +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:111 +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:96 +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:67 +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:87 +msgid "Translation updates" +msgstr "Aggiornamenti traduzione" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:1 +msgid "" +"==============\n" +"0.9.10 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.10\n" +"==============" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:9 +msgid "" +"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more " +"difficult for an attacker to correlate a Destination with a Router." +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:11 +msgid "" +"0.9.10 changes the mechanism for doing LeaseSet lookups, making it more " +"difficult for an attacker\n" +"to correlate a Destination with a Router. It also fixes character " +"encoding bugs in susimail,\n" +"and includes lots of other bug fixes and translation updates.\n" +"Most of you will update via torrent, using the new \"su3\" update format " +"with stronger keys." +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:18 +msgid "" +"We recently attended `30C3`_ and `Real World Crypto`_, making several new" +"\n" +"connections and formulating `big plans`_ for 2014. Thanks to those who\n" +"supported our attendance with their `donations`_!" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:26 +msgid "`big plans`" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:27 +msgid "`donations`" +msgstr "`donazioni`" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:38 +msgid "Use client tunnels for LeaseSet lookups" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:42 +msgid "" +"Flood netdb stores to new location before midnight to prevent lookup " +"fails after midnight" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:43 +msgid "Fix setting I2CP host/port in BOB" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:44 +msgid "Fix several character encoding issues in susimail" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:45 +msgid "Fix StandardServerSocket.close()" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:46 +msgid "Fix exception in PrivateKeyFile" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:47 +msgid "Fixes in RouterInfo expiration task" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:51 +msgid "Tweaks to reduce number of peer connections" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:52 +msgid "Several threading fixes to reduce blocking in the timer queues" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:53 +msgid "Disable streaming ping handling for clients" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:54 +msgid "Use i2psnark's Kademlia library for the router netdb also" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:55 +msgid "" +"Increase outbound exploratory default to 2 + 0-1 hops, part of gradual " +"increase to 3 hops in/out" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:56 +msgid "More findbugs fixes" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:57 +msgid "Streaming library refactoring" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:58 +msgid "Support country-specific translations" +msgstr "" + +#: i2p2www/blog/2014/01/22/0.9.10-Release.rst:59 +msgid "New Brazilian Portuguese translation" +msgstr "Nuova traduzione in Portoghese brasiliano" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:1 +msgid "" +"==============\n" +"0.9.11 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.11\n" +"==============" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:9 +msgid "" +"0.9.11 adds support for outproxy plugins, improves lease set lookup " +"security, and reduces memory usage." +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:11 +#, python-format +msgid "" +"0.9.11 continues improving LeaseSet lookup and storage to prevent an " +"attacker\n" +"from correlating a Destination with a Router. It adds support for the\n" +"%(orchid)s outproxy plugin which is available at %(url)s. There is a\n" +"reduction in memory usage due to fixes in the transports. We have some " +"I2CP\n" +"protocol improvements that will provide better lookup facilities and\n" +"authorization protection for external clients. Of course, there's also " +"the\n" +"usual collection of bug fixes. All users should update." +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:21 +msgid "" +"This may be the last release that works with Java 5, which is very old " +"and\n" +"unsupported. If you are using a Java 5 or 6 runtime, we strongly " +"recommend that\n" +"you upgrade to Java 7." +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:30 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:30 +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:17 +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:32 +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:30 +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:37 +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:21 +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:24 +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:29 +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:25 +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:24 +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:67 +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:47 +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:29 +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:48 +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." +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:39 +msgid "More leaseset handling improvements" +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:43 +msgid "Fix NPE after client shutdown" +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:44 +msgid "Fix wrapper log encoding on logs page" +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:45 +msgid "Streaming ping and I2Ping fixes" +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:49 +msgid "Add support for Orchid plugin" +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:50 +msgid "Add HTTPS support to HTTP client proxy" +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:51 +msgid "New I2CP support for hostname lookups by external clients" +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:52 +msgid "" +"Stricter I2CP authorization enforcement of external clients (incompatible" +" change)" +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:53 +msgid "Increase default inbound exploratory tunnel length variance" +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:54 +msgid "Big reduction in memory usage by transports" +msgstr "" + +#: i2p2www/blog/2014/02/08/0.9.11-Release.rst:55 +msgid "All in-net updates via torrent" +msgstr "" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:1 +msgid "" +"=========================\n" +"Malware at i2pbrowser.net\n" +"=========================" +msgstr "" +"=========================\n" +"Malware su i2pbrowser.net\n" +"=========================" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:8 +msgid "" +"The site i2pbrowser.net is a fake I2P website mirror serving up malware " +"for Windows." +msgstr "" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:10 +msgid "" +"We have recently been made aware of the existence of i2pbrowser.net. This" +"\n" +"website copies our homepage and download page, and attempts to trick " +"users into\n" +"downloading Windows malware." +msgstr "" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:16 +msgid "" +"There are several indicators that point to i2pbrowser.net being a malware" +" site:" +msgstr "" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:20 +msgid "The domain was registered on February 10th, 2014." +msgstr "" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:21 +msgid "" +"The download URLs for Windows, Mac OSX, Linux, Android etc. all link to " +"the same .exe file." +msgstr "" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:22 +msgid "The .exe is only 741 KB; the official Windows installer for I2P is 13 MB." +msgstr "" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:24 +msgid "" +"We have not examined the malware ourselves, but it does not appear to be " +"very\n" +"sophisticated; it is not integrated into or bundled with the I2P " +"software.\n" +"Information security expert `Lance James`_ posted `a tweet`_ labelling it" +" as\n" +"\"a standard dark comet rat\"." +msgstr "" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:31 +msgid "" +"Spread the word. The only official download locations for I2P are linked " +"on our\n" +"`download page`_. All I2P download packages are GPG-signed by the\n" +"`release signing key`_." +msgstr "" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:38 +msgid "`a tweet`" +msgstr "`un tweet`" + +#: i2p2www/blog/2014/02/16/i2pbrowser-malware.rst:40 +msgid "`release signing key`" +msgstr "" + +#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:1 +msgid "" +"================================================================\n" +"Search Engine DuckDuckGo Awards Invisible Internet Project $5000\n" +"================================================================" +msgstr "" +"================================================================\n" +"Search Engine DuckDuckGo Awards Invisible Internet Project $5000\n" +"================================================================" + +#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:10 +msgid "" +"Search engine `DuckDuckGo`_ `donates`_ $5000 to the `Invisible Internet " +"Project`_ (I2P) in their open source donation program." +msgstr "" + +#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:12 +msgid "" +"**Somewhere, NH** -- Internet search company `DuckDuckGo`_ `donates`_\n" +"$5000 to the `Invisible Internet Project`_ (I2P) as part of their yearly " +"open-source\n" +"donation program. The award was granted on the basis of `nominations`_ by" +" members of the public\n" +"on the DuckDuckGo community portal. With an emphasis on privacy, " +"DuckDuckGo provides a search\n" +"engine which does not track its users or store personal data. I2P is an " +"anonymous network intended to\n" +"protect individuals from dragnet surveillance regularly performed by ISPs" +" and governments." +msgstr "" + +#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:21 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:42 +msgid "" +"This marks the single largest donation ever received by I2P and reflects " +"a growing interest in\n" +"privacy and security by the Internet community. The funding will help I2P" +" to reach more users, expand\n" +"development, and audit the code. It will also enable I2P developers to " +"attend conferences, such\n" +"as the `Real-World Cryptography`_ conference in New York City, where the " +"developers met and\n" +"collaborated with cryptography experts pursuant to I2P's goals of " +"providing anonymity to the\n" +"public." +msgstr "" + +#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:30 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:51 +msgid "" +"I2P thanks Gabriel Weinberg and DuckDuckGo for the generous donation,\n" +"and the I2P community for its support in the `nominations`_." +msgstr "" + +#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:35 +msgid "" +"For more information about I2P, visit `our web site`_ or follow us `on " +"Twitter`_." +msgstr "" + +#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:39 +msgid "`donates`" +msgstr "" + +#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:42 +msgid "`our web site`" +msgstr "`il nostro sito`" + +#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:43 +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:59 +msgid "`nominations`" +msgstr "" + +#: i2p2www/blog/2014/03/12/press-release-ddg-donation.rst:45 +msgid "`on Twitter`" +msgstr "`su Twitter`" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:1 +msgid "" +"==============\n" +"0.9.12 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.12\n" +"==============" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:10 +msgid "0.9.12 adds support for ECDSA and updates to Jetty 8" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:12 +msgid "" +"I2P now requires Java 6 or higher.\n" +"We strongly recommend that you upgrade to Java 7.\n" +"If you are still using Java 5, you must upgrade your Java before " +"installing I2P 0.9.12." +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:18 +msgid "" +"0.9.12 adds preliminary support for ECDSA-signed Destinations.\n" +"It contains several fixes for the handling of Delivery Status Messages " +"(acknowledgements)\n" +"and those messages are now end-to-end encrypted for increased security." +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:24 +msgid "" +"We have upgraded to Jetty 8.\n" +"Jetty 8 is almost identical to Jetty 7, so there are no complex " +"configuration file conversions as there have been in past Jetty upgrades." +"\n" +"No manual changes should be necessary." +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:35 +msgid "" +"In early March, Internet search company `DuckDuckGo`_ `donated`_\n" +"$5000 to the `Invisible Internet Project` (I2P) as part of their yearly " +"open-source\n" +"donation program. The award was granted on the basis of `nominations`_ by" +" members of the public\n" +"on the DuckDuckGo community portal." +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:56 +msgid "`donated`" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:69 +msgid "Encrypt Delivery Status Messages" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:70 +msgid "Add preliminary support for ECDSA-signed Destinations" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:71 +msgid "Add check for replayed NTCP session requests" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:72 +msgid "Add throttling and blocking checks to streaming ping processing" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:78 +msgid "Fix RouterInfo exchange in NTCP" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:79 +msgid "Extend timeout for Delivery Status Messages" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:80 +msgid "Drop streaming messages from recently closed connections" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:81 +msgid "Fix restarts on Raspberry Pi" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:82 +msgid "Restore profileOrganizer.sameCountryBonus advanced config" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:83 +msgid "Fix for jwebcache and i2phex" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:89 +msgid "Jetty 8.1.14.v20131031; Java 6 now required" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:90 +msgid "Reduce target connection count again to reduce tunnel reject rate further" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:91 +msgid "Add rate limit for outbound connections at tunnel endpoints" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:92 +msgid "Add optional inproxy blocking in i2ptunnel" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:93 +msgid "Use SSU session key for relay request/response when available" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:94 +msgid "Include HTTP POST data in SYN packet" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:95 +msgid "Add getopt library for better argument processing" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:96 +msgid "More removal of Jetty dependencies" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:97 +msgid "Remove MD5 code, use Java libraries instead" +msgstr "" + +#: i2p2www/blog/2014/03/31/0.9.12-Release.rst:98 +msgid "Change the default addressbook subscription URL" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:1 +msgid "" +"==============\n" +"0.9.13 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.13\n" +"==============" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:10 +msgid "0.9.13 with SusiMail improvements and fixes for firewalled routers" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:12 +msgid "" +"0.9.13 includes fixes for firewalled routers, netdb lookup improvements, " +"and a big SusiMail update.\n" +"Of course, there's also the usual collection of bug fixes and translation" +" updates." +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:22 +msgid "" +"zzz has updated his GPG keys, and the release files are signed with his\n" +"new keys. His new key fingerprint is:" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:31 +msgid "SusiMail" +msgstr "SusiMail" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:33 +msgid "Many UI improvements" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:34 +msgid "Implement local storage of messages" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:35 +msgid "Add offline mode" +msgstr "Aggiunta modalità offline" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:36 +msgid "Messages now deleted on server after download" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:37 +msgid "Several backend POP3 and SMTP speedups and fixes" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:41 +msgid "NetDB lookup fixes" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:42 +msgid "Fix transition from not-firewalled to firewalled" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:43 +msgid "Fix plugin uninstall on Windows" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:44 +msgid "SSU locking fixes" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:45 +msgid "Fix rapid republishing of SSU addresses" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:46 +msgid "IRC client exception fixes" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:47 +msgid "Fix changing HTTP outproxy configuration without restarting tunnel" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:51 +msgid "New i2ptunnel server option for unique local address per-client" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:52 +msgid "Warn in i2ptunnel on duplicate client ports" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:53 +msgid "Update HTTP User-Agent to match TBB" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:54 +msgid "Extend SSU establishment retransmission timer" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:55 +msgid "Use constant-time method for HMAC verification" +msgstr "" + +#: i2p2www/blog/2014/05/22/0.9.13-Release.rst:56 +msgid "New translation: Slovak" +msgstr "Nuova traduzione: Slovacco" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:1 +msgid "" +"==============\n" +"0.9.14 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.14\n" +"==============" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:10 +msgid "0.9.14 includes critical security fixes" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:12 +msgid "" +"0.9.14 includes critical fixes for XSS and remote execution " +"vulnerabilities reported by Exodus Intelligence.\n" +"As an added precaution, we have disabled several advanced configuration " +"features in the router console,\n" +"including installation of new plugins.\n" +"We plan to re-enable these in a future release after additional review." +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:19 +msgid "" +"Due to I2P library changes, I2P-Bote users must upgrade their plugin to " +"version 0.2.10 to work with I2P 0.9.14.\n" +"Your router should update the plugin automatically after the router " +"restarts." +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:24 +msgid "" +"The release also contains several bug fixes in i2ptunnel, i2psnark, and " +"other areas,\n" +"and updates to the latest Jetty, Tomcat, and Wrapper.\n" +"We've also implemented a faster and more secure method for reseeding.\n" +"Of course, there's also the usual collection of minor bug fixes and " +"translation updates." +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:31 +msgid "" +"You must update to this release immediately. The best way to\n" +"maintain security and help the network is to run the latest release." +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:39 +msgid "Security Fixes" +msgstr "Sistemati dei problemi di sicurezza" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:41 +msgid "Fix several XSS issues" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:42 +msgid "Disable changing news feed URL from UI" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:43 +msgid "Disable plugin install" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:44 +msgid "Disable setting unsigned update URL from UI" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:45 +msgid "Disable clients.config editing from the UI" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:46 +msgid "Add Content-Security-Policy and X-XSS-Protection headers" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:47 +msgid "Disable unused ExecNamingService (thx joernchen of Phenoelit)" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:52 +msgid "Fix tunnel building so it doesn't get \"stuck\" on a single pool" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:53 +msgid "Reject participating tunnels when hidden" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:54 +msgid "" +"Several i2psnark improvements and fixes (GUI and DHT), including changes " +"for better compatibility with Vuze" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:59 +msgid "" +"Reseeding now fetches a signed zip file containing router infos for " +"security and speed" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:60 +msgid "Use JVM's AES implementation if it is faster" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:61 +msgid "More advanced options shown in the i2ptunnel edit pages" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:62 +msgid "" +"Per-message reliabilitiy settings in I2CP and error propagation back from" +" router to client" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:63 +msgid "Lots of findbugs fixes and cleanups" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:64 +msgid "Support signature types in SAM, bump rev to 3.1" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:65 +msgid "New event log page in console" +msgstr "" + +#: i2p2www/blog/2014/07/26/0.9.14-Release.rst:68 +msgid "Wrapper 3.5.25 (new installs and PPA only)" +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:1 +msgid "" +"================\n" +"0.9.14.1 Release\n" +"================" +msgstr "" +"================\n" +"Reelase 0.9.14.1\n" +"================" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:10 +msgid "0.9.14.1 includes i2psnark and console fixes" +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:12 +msgid "" +"0.9.14.1 includes fixes for the \"Add Torrent\" form in i2psnark and some" +" other web forms.\n" +"We've restored the ability to install plugins via the console, but you " +"must first edit your router.config file\n" +"(in ~/.i2p/ or /var/lib/i2p/i2p-config/ or %APPDATA%\\I2P\\) to add the " +"line routerconsole.enablePluginInstall=true.\n" +"Other rarely-used advanced features that were removed in 0.9.14 may be " +"restored by adding the line routerconsole.advanced=true." +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:19 +msgid "" +"As usual, if configured with the default \"Download and Verify\", the " +"router will automatically download the update and display a button to " +"restart.\n" +"However, due to a bug in 0.9.14, if your update is configured for " +"\"Notify only\", the download button will not be displayed.\n" +"You must change your configuration to \"Download and Verify\" or " +"\"Download, Verify, and Restart\" to update." +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:25 +msgid "" +"If you are still running 0.9.13 or older, we recommend that you update to" +" this release as soon as possible.\n" +"If you don't often check your router console, please consider changing " +"your configuration to \"Download, Verify, and Restart\"\n" +"to ensure you are always running the latest release." +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:37 +msgid "Fix i2psnark add torrent form" +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:38 +msgid "Fix iptunnel custom options form" +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:39 +msgid "Fix update download buttons" +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:44 +msgid "Restore all console features if routerconsole.advanced=true" +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:45 +msgid "Restore plugin install if routerconsole.enablePluginInstall=true" +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:46 +msgid "Restpre client adds/changes if routerconsole.enableClientChange=true" +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:47 +msgid "" +"Plugin signing keys are now whitelisted unless " +"routerconsole.allowUntrustedPlugins=true" +msgstr "" + +#: i2p2www/blog/2014/08/09/0.9.14.1-Release.rst:48 +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:71 +msgid "More escaping and cleanups in forms and messages" +msgstr "" + +#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:1 +msgid "" +"==============================\n" +"The birth of Privacy Solutions\n" +"==============================" +msgstr "" +"==============================\n" +"Nascita di Privacy Solutions\n" +"==============================" + +#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:10 +msgid "Organization launch" +msgstr "" + +#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:14 +msgid "" +"Hello all!\n" +"\n" +"Today we announce the Privacy Solutions project, a new organization that " +"develops and maintains I2P software. Privacy Solutions includes several " +"new development efforts designed to enhance the privacy, security, and " +"anonymity for users, based on I2P protocols and technology.\n" +"\n" +"These efforts include\n" +"\n" +"1) The Abscond browser bundle.\n" +"2) The i2pd C++ router project.\n" +"3) The \"BigBrother\" I2P network monitoring project.\n" +"4) The Anoncoin crypto-coin project.\n" +"5) The Monero crypto-coin project.\n" +"\n" +"Privacy Solutions' initial funding was provided by the supporters of the " +"Anoncoin and Monero projects. Privacy Solutions is a Norway-based non-" +"profit type of organization registered within the Norwegian government " +"registers. ( Kind of like US 501(c)3. )\n" +"\n" +"Privacy Solutions plans to apply for funding from the Norwegian goverment" +" for network research, because of BigBrother (We'll get back to what that" +" is) and the coins that are planned to use low-latency networks as " +"primary transport layer. Our research will support advances in software " +"technology for anonymity, security, and privacy.\n" +"\n" +"\n" +"First a little bit about the Abscond Browser Bundle. This was first a " +"one-man project by Meeh, but later on friends started sending patches, " +"the project is now trying to create the same easy access to I2P as Tor " +"has with their browser bundle. Our first release isn't far away, it's " +"just some gitian script tasks left, including setup of the Apple " +"toolchain. But again we will add monitoring with PROCESS_INFORMATION (A C" +" struct keeping vital proces information about an process) from the Java " +"instance to check on I2P before we declare it stable. I2pd will also " +"switch with the Java version once it's ready, and there is no point in " +"shipping a JRE in the bundle anymore. You can read more about the Abscond" +" Browser Bundle at https://hideme.today/dev" +msgstr "" + +#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:36 +msgid "" +"We would also like to inform of the current status of i2pd. I2pd supports" +" bi-directional streaming now, that allows to use not only HTTP but long-" +"lived communication channels. Instant IRC support has been added. I2pd " +"users are able to use it same way as Java I2P for access to I2P IRC " +"network. I2PTunnel is one of key features of I2P network, allowing non-" +"I2P applications communicate transparently. That's why it's vital feature" +" for i2pd and one of key milestones." +msgstr "" + +#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:40 +msgid "" +"At last, if you are familiar with I2P you probably know about " +"Bigbrother.i2p, which is a metrics system Meeh made over a year back. " +"Recently we noticed that Meeh actually have 100Gb of non-duplicated data " +"from nodes reporting in since initial launch. This will also be moved to " +"Privacy Solutions and be rewritten with a NSPOF backend. With this we " +"will aslo start using the Graphite ( http://graphite.wikidot.com/screen-" +"shots ). This will give us a great overview over the network without " +"privacy issues for our end users. The clients filter all data except " +"country, router hash and success rate on tunnel buildings. The name of " +"this service is as always a little joke from Meeh." +msgstr "" + +#: i2p2www/blog/2014/08/15/The-privacy-solutions-project.rst:47 +msgid "" +"We have shorted down a bit of the news here, if you're interested in more" +" information please visit https://blog.privacysolutions.no/\n" +"We're still under construction and more content will come!\n" +"\n" +"\n" +"\n" +"For further information contact: press@privacysolutions.no\n" +"\n" +"\n" +"\n" +"\n" +"Best regards,\n" +"\n" +"Mikal \"Meeh\" Villa" +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:1 +msgid "" +"=============================================\n" +"Android test release on Google Play in Norway\n" +"=============================================" +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:10 +msgid "" +"I2P Android and Bote have been released on Google Play in Norway, as a " +"test run for a future worldwide release." +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:12 +msgid "" +"I2P Android has existed for over three years. In that time, it has " +"evolved from\n" +"a simple test project into a usable, useful Android port of the I2P " +"router. Our\n" +"eventual goal has been to release I2P Android on Google Play, to make it " +"easier\n" +"for users to discover, install and use I2P on their Android devices. " +"After much\n" +"work improving the user interface, fixing bugs and testing, we think that" +" I2P\n" +"Android is finally ready to go where the users are." +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:21 +msgid "" +"Initially, we are only releasing to Android users in Norway, as a test " +"run. I2P\n" +"Android will have far more exposure on Google Play than it has ever had " +"before,\n" +"and there will be bugs and usability issues that we need to fix. It will " +"be much\n" +"easier (and less stressful!) to respond to feedback if we only need to " +"deal with\n" +"reports from hundreds of users instead of thousands (already orders of " +"magnitude\n" +"more feedback than we have ever had)." +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:30 +msgid "" +"Simultaneously we are making the first public release of Bote, an Android" +" port\n" +"of `I2P-Bote`_. Bote is private, distributed, secure email, made easy. It" +" runs\n" +"on top of the I2P network, and while it works as a standalone app, it " +"will use\n" +"the I2P Android app by default if installed. As with I2P Android, we are\n" +"initially only releasing Bote to Android users in Norway." +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:38 +msgid "" +"The apps are being released on Google Play by `The Privacy Solutions " +"Project`_.\n" +"See their `blog post`_ for further information, and links to the Google " +"Play\n" +"page for Norway users." +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:44 +msgid "" +"As lead developer for I2P Android and Bote, I look forward to your " +"comments. You\n" +"are the people who will be using them, and your perspectives will help me" +" craft\n" +"simple, intuitive apps that make privacy accessible to everyone." +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:51 +msgid "`The Privacy Solutions Project`" +msgstr "`The Privacy Solutions Project`" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:52 +msgid "`blog post`" +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:54 +msgid "Website release details" +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:56 +msgid "" +"We have also updated I2P Android on the website to match the release " +"candidate\n" +"deployed in Norway. This version will be updated with changes as we " +"respond to\n" +"feedback from Norwegian users, heading towards our next stable release." +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:62 +msgid "" +"Please note that we have upgraded the Android API to 9. This means that " +"Froyo\n" +"Android 2.2 will not be supported anymore; the minimum requirement is now" +"\n" +"Gingerbread Android 2.3." +msgstr "" + +#: i2p2www/blog/2014/08/23/Android-test-release-on-Google-Play-in-Norway.rst:68 +msgid "" +"Also note that if you have an earlier version of I2P Android, you will " +"need to\n" +"uninstall and reinstall because we have changed the release keys. Further" +"\n" +"information about this will be provided in a subsequent blog post." +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:1 +msgid "" +"==============\n" +"0.9.15 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.15\n" +"==============" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:10 +msgid "0.9.15 includes Ed25519 crypto and many fixes" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:12 +msgid "" +"0.9.15 adds preliminary support for Ed25519 EdDSA signatures.\n" +"It includes a new persistent configuration backend for i2psnark and fixes" +" several issues with i2psnark's handling of file names.\n" +"There are several improvements to speed up SAM.\n" +"Plugins now support stronger signatures in the su3 file format.\n" +"Plugin installation via the console, which was disabled in 0.9.14, is re-" +"enabled." +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:20 +msgid "" +"We have supported ECDSA signatures since 0.9.12, and we would like to " +"start using ECDSA by default.\n" +"Unfortunately, some of you are still running older I2P versions, and for " +"others,\n" +"their distribution or Java runtime does not support ECDSA. Red Hat\n" +"(RHEL, Fedora) distributions are reported to be missing ECDSA.\n" +"Some have fixed the Java issues by upgrading from Java 6 to Java 7;\n" +"others have had success with installing the \"unlimited strength policy " +"files\".\n" +"We've added information about missing crypto to the log file and the " +"/logs page in the console.\n" +"After you update to 0.9.15, please check if you are missing ECDSA " +"support, and attempt to fix it if necessary.\n" +"This is particularly important for those that run popular eepsites and " +"services." +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:41 +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:39 +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:46 +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:32 +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:46 +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:38 +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:36 +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:75 +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:55 +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:37 +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:56 +msgid "Changes" +msgstr "Modifiche" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:43 +msgid "Add support for Ed25519 signatures" +msgstr "Aggiunto il supporto per le firme Ed25519" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:44 +msgid "" +"i2psnark move to separate config file for each torrent to better support " +"per-torrent settings" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:45 +msgid "Add i2psnark support for data outside the i2psnark/ directory" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:46 +msgid "Enable stronger signatures (su3 format) for plugins" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:47 +msgid "Speed up SSU introductions by responding to hole punch messages" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:48 +msgid "Several improvements in SAM efficiency" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:53 +msgid "Form submission fixes in the console and i2psnark" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:54 +msgid "Streaming fixes for long signatures" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:55 +msgid "i2psnark fixes for file name character mapping when seeding" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:56 +msgid "I2PTunnel fixes stopping client tunnels" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:57 +msgid "I2PTunnel fix updating options on a running delay-open client tunnel" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:62 +msgid "Re-enable plugin installation via the console, removed in 0.9.14" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:63 +msgid "i2psnark now remembers uploaded count across restarts" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:64 +msgid "i2psnark increase max piece size to 8 MB" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:65 +msgid "i2psnark several UI fixes" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:66 +msgid "Prohibit SSU peer test requests unless a connection is established" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:67 +msgid "" +"i2ptunnel add support for local SSL connections for standard and IRC " +"client tunnels" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:68 +msgid "Console and log warnings for unavailable crypto" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:69 +msgid "" +"More consistent routing for Delivery Status Messages to reduce network " +"connections" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:70 +msgid "Disable external entities in UPnP XML parser" +msgstr "" + +#: i2p2www/blog/2014/09/20/0.9.15-Release.rst:73 +msgid "Update GeoIP data (in both new installs and updates)" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:1 +msgid "" +"==============\n" +"0.9.16 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.16\n" +"==============" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:10 +msgid "0.9.16 includes crypto migration and many fixes" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:12 +msgid "" +"0.9.16 is a significant step forward in our plan to migrate\n" +"from DSA to ECDSA and then EdDSA cryptographic signatures,\n" +"and makes several other changes to increase your anonymity and security.\n" +"Client tunnels for standard, IRC, and SOCKS IRC will use ECDSA signatures" +" by default.\n" +"In addition, we've fixed a large number of serious bugs, including " +"console lockups." +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:20 +msgid "" +"Changes in router data structures will require i2pcontrol plugin users to" +" update to version 0.0.9." +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:24 +msgid "" +"If you run an eepsite or a service and you are not running a recent " +"release,\n" +"or your Java or OS does not support ECDSA (as noted in the logs and on " +"the /logs page in the console),\n" +"please fix the issue as soon as possible or your users will soon be " +"unable to connect." +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:41 +msgid "Add support for stronger Router Info signatures" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:42 +msgid "Encrypt RI lookups and responses on faster boxes" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:43 +msgid "" +"Require I2CP authorization for all messages when enabled (requires 0.9.11" +" or higher client)" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:44 +msgid "Disable SSLv3 and older ciphers for reseeding and other uses of SSL" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:45 +msgid "" +"Use ECDSA by default for i2ptunnel IRC, SOCKS-IRC, and standard client " +"tunnels" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:46 +msgid "Don't prefer floodfills in some countries" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:47 +msgid "" +"New column sorting, set-all priority buttons, and upload ratio display in" +" i2psnark" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:48 +msgid "Increase i2psnark tunnel default to 3 hops" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:49 +msgid "" +"Implement bundling of multiple fragments in a single SSU message for " +"efficiency" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:50 +msgid "New add-to-addressbook links on netdb leaseset page" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:51 +msgid "" +"Implement I2NP DatabaseLookupMessage search type field to improve lookup " +"efficiency" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:58 +msgid "CPUID fixes and updates for recent processors" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:59 +#, python-format +msgid "i2psnark fix magnet links with %(pc)s-encoding" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:60 +#, python-format +msgid "" +"Improve handling of SSU socket closing out from under us (hopefully fix " +"100%(pc)s CPU)" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:61 +msgid "SSU bitfield handling fixes" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:62 +msgid "Fix HTTP header issues in i2psnark" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:63 +msgid "Fix rare NPE when building garlic message" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:64 +msgid "Fix console lockups (hopefully)" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:65 +msgid "Fix i2ptunnel js confirm-delete" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:70 +msgid "" +"Move router data structures from i2p.jar to router.jar (breaks i2pcontrol" +" plugin)" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:71 +msgid "" +"New router keys now stored in router.keys.dat (eepPriv.dat format) " +"instead of router.keys" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:72 +msgid "Improve handling of unsupported encryption throughout" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:73 +msgid "More error checking of client I2CP messages by the router" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:74 +msgid "Initial work on hooks for pluggable transports" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:75 +msgid "Enforce request timestamp in tunnel build messages" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:76 +msgid "" +"Re-enable message status in streaming, but treat no leaseset as a soft " +"failure for now" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:77 +msgid "Return unused DH keypairs to the pool for efficiency" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:78 +msgid "Raise failsafe tagset limit and improve deletion strategy when hit" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:79 +msgid "" +"Change eepsite Jetty threadpool and queue configuration (new installs " +"only)" +msgstr "" + +#: i2p2www/blog/2014/11/01/0.9.16-Release.rst:80 +msgid "NTCP establishment refactoring in prep for NTCP2 and PT" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:1 +msgid "" +"==============\n" +"0.9.17 Release\n" +"==============" +msgstr "" +"==============\n" +"Reelase 0.9.17\n" +"==============" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:10 +msgid "0.9.17 with more crypto migration and many fixes" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:12 +msgid "" +"0.9.17 is primarily a bugfix release, but it also continues our migration" +" to stronger cryptographic signatures." +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:16 +msgid "" +"We have moved the news feed system used for the news on your console and " +"the latest router version indication\n" +"to a signed format using RSA 4096-bit keys for enhanced security." +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:21 +msgid "" +"New eepsites and servers will be ECDSA-signed by default, if ECDSA is " +"available.\n" +"There is now a warning in the console sidebar if ECDSA is not available.\n" +"For RedHat users, we have reports of successful installs of the " +"BouncyCastle Provider (bcprov) jar to add ECDSA support." +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:27 +msgid "" +"We've fixed several serious bugs, including an SSU packet corruption " +"problem,\n" +"and a SAM bug affecting i2p-messenger and other SAM applications.\n" +"There are several fixes for the preliminary ECDSA router signatures added" +" in the last release but not yet enabled." +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:33 +msgid "" +"Many of us will be attending 31C3 in Hamburg in December. Stop by our " +"table and say hi!" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:48 +msgid "Signed news" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:49 +msgid "ECDSA default for new server tunnels" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:50 +msgid "Reseeding now SSL-only by default" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:55 +msgid "Fix SSU sending corrupt ack-only packets with partial bitfields" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:56 +msgid "Fix SSU inbound connection fail from non-DSA router" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:57 +msgid "Don't select incompatible peers if we are a non-DSA router" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:58 +msgid "Fix EdDSA signature verification bug" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:59 +msgid "" +"Set I2NP lookup type flags in all cases, not just when a reply tunnel is " +"used" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:60 +msgid "Stop i2ptunnel server acceptor thread after close" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:61 +msgid "Fix bug preventing some plugins from stopping completely" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:62 +msgid "Fix SAM v3 bug causing failures in incoming connections" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:67 +msgid "Add a warning in the console sidebar if ECDSA not supported" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:68 +msgid "Log warnings for Java 6 that we will eventually require Java 7" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:69 +msgid "Don't let proxied routers auto-floodfill" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:70 +msgid "Don't resend SSU acks that are too old" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:71 +msgid "Don't publish direct info in SSU address if introducers are required" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:72 +msgid "New default opentrackers in i2psnark" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:73 +msgid "Add support for specifiying data directory per-torrent in i2psnark" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:74 +msgid "Changes in streaming accept() error behavior" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:75 +msgid "Minor blockfile format changes" +msgstr "" + +#: i2p2www/blog/2014/11/30/0.9.17-Release.rst:76 +msgid "" +"New option for persistent random key to preserve peer ordering across " +"restarts" +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:1 +msgid "" +"====================\n" +"Android app releases\n" +"====================" +msgstr "" +"====================\n" +"Rilasci della app Android\n" +"====================" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:10 +msgid "" +"I2P Android 0.9.17 and Bote 0.3 have been released on the website, Google" +" Play and F-Droid." +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:12 +msgid "" +"It has been some time since I last posted updates about our Android " +"development,\n" +"and several I2P releases have gone by without any matching Android " +"releases.\n" +"At last, the wait is over!" +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:18 +msgid "" +"New app versions\n" +"----------------" +msgstr "" +"Nuove versioni della app\n" +"----------------" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:23 +msgid "" +"New versions of I2P Android and Bote have been released! They can be " +"downloaded\n" +"from these URLs:" +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:31 +msgid "" +"The main change in these releases is the transition to Android's new " +"Material\n" +"design system. Material has made it much easier for app developers with, " +"shall\n" +"we say, \"minimalist\" design skills (like myself) to create apps that " +"are nicer\n" +"to use. I2P Android also updates its underlying I2P router to the just-" +"released\n" +"version 0.9.17. Bote brings in several new features along with many " +"smaller\n" +"improvements; for example, you can now add new email destinations via QR " +"codes." +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:40 +msgid "" +"As I mentioned in `my last update`_, the release key that signs the apps " +"has\n" +"changed. The reason for this was because we needed to change the package " +"name\n" +"of I2P Android. The old package name (``net.i2p.android.router``) had " +"already\n" +"been taken on Google Play (we still don't know who was using it), and we " +"wanted\n" +"to use the same package name and signing key for all distributions of I2P" +"\n" +"Android. Doing so means that a user could initially install the app from " +"the I2P\n" +"website, and then later if the website was blocked they could upgrade it " +"using\n" +"Google Play. Android OS considers an application to be completely " +"different when\n" +"its package name changes, so we took the opportunity to increase the " +"strength of\n" +"the signing key." +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:53 +msgid "The fingerprint (SHA-256) of the new signing key is:" +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:63 +msgid "`my last update`" +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:65 +msgid "" +"Google Play\n" +"-----------" +msgstr "" +"Google Play\n" +"-----------" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:70 +msgid "" +"A few months ago we `released`_ both I2P Android and Bote on Google Play " +"in\n" +"Norway, to test the release process there. We are pleased to announce " +"that both\n" +"apps are now being released globally by `Privacy Solutions`_. The apps " +"can be\n" +"found at these URLs:" +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:80 +msgid "" +"The global release is being done in several stages, starting with the " +"countries\n" +"for which we have translations. The notable exception to this is France; " +"due to\n" +"import regulations on cryptographic code, we are unable yet to distribute" +" these\n" +"apps on Google Play France. This is the same issue that has affected " +"other apps\n" +"like TextSecure and Orbot." +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:88 +msgid "`released`" +msgstr "`rilasciato`" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:90 +msgid "`I2P on Google Play`" +msgstr "`I2P su Google Play`" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:91 +msgid "`Bote on Google Play`" +msgstr "`Bote su Google Play`" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:93 +msgid "" +"F-Droid\n" +"-------" +msgstr "" +"F-Droid\n" +"-------" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:98 +msgid "" +"Don't think we have forgotten about you, F-Droid users! In addition to " +"the two\n" +"locations above, we have set up our own F-Droid repository. If you are " +"reading\n" +"this post on your phone, `click here`_ to add it to F-Droid (this only " +"works in\n" +"some Android browsers). Or, you can manually add the URL below to your " +"F-Droid\n" +"repository list:" +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:108 +msgid "" +"If you would like to manually verify the fingerprint (SHA-256) of the " +"repository\n" +"signing key, or type it in when adding the repository, here it is:" +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:117 +msgid "" +"Unfortunately the I2P app in the main F-Droid repository has not been " +"updated\n" +"because our F-Droid maintainer has disappeared. We hope that by " +"maintaining this\n" +"binary repository, we can better support our F-Droid users and keep them\n" +"up-to-date. If you have already installed I2P from the main F-Droid " +"repository,\n" +"you will need to uninstall it if you want to upgrade, because the signing" +" key\n" +"will be different. The apps in our F-Droid repository are the same APKs " +"that are\n" +"provided on our website and on Google Play, so in future you will be able" +" to\n" +"upgrade using any of these sources." +msgstr "" + +#: i2p2www/blog/2014/12/01/Android-app-releases.rst:128 +msgid "`click here`" +msgstr "`clicca qui`" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1 +msgid "" +"================\n" +"31C3 trip report\n" +"================" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9 +msgid "" +"CCC has always been a productive time for us, and 31C3 was no exception. " +"Here is a summary of our various meetings and discussions." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20 +msgid "" +"We were, for the second year in a row, at a great location in the " +"Congress, in\n" +"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square " +"has\n" +"really increased our visibility and helped many people find us. Thanks to" +" Noisy\n" +"Square and the 31C3 organizers for a great Congress." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29 +msgid "" +"We also thank Gabriel Weinberg and his fabulous search engine " +"`DuckDuckGo`_ for\n" +"their support of open source anonymity tools and their `generous " +"contribution`_\n" +"to I2P in 2014. Funding from DuckDuckGo and others helped support our " +"attendance\n" +"at CCC. This is the primary annual meetup for I2P developers and it is " +"critical\n" +"to our success." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38 +msgid "`generous contribution`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40 +msgid "" +"Discussions with others\n" +"=======================" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48 +msgid "" +"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved " +"himself\n" +"and the project from TU Munich to `Inria`_ in France. He has a large " +"number of\n" +"`open positions`_. This is a great opportunity to get paid to work on " +"open\n" +"source anonymity tools, we encourage everybody to contact him about it." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57 +msgid "`open positions`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59 +msgid "" +"The prospect of an invigorated GNUnet with a large amount of new funding " +"is\n" +"quite interesting. We discussed more ways to work together. In early " +"2014, we\n" +"worked hard to understand the GnuNet DNS replacement, but we were unable " +"to\n" +"figure out a good fit for it in I2P. One of his new ideas is a " +"distributed,\n" +"anonymous statistics gathering subsystem, for detecting problems or " +"attacks on\n" +"the network. We'd definitely be interested in that." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68 +msgid "" +"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems " +"draft`_.\n" +"A new, greatly simplified version 3 was posted in December. The prospects" +" for\n" +"approval remain unclear. The best way to monitor or participate in the\n" +"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to " +"do so\n" +"on our side, and also give Hellekin a new point-of-contact for this topic." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76 +msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77 +msgid "`IETF DNSOP WG mailing list`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79 +msgid "" +"We apologized to Christian for not being organized enough to have a talk " +"at his\n" +"`We Fix The Net assembly`_. One of our biggest failures as a project is " +"our\n" +"seeming inability to submit talks at conferences. We'll have to do better" +" in the\n" +"new year." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86 +msgid "`We Fix The Net assembly`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91 +msgid "" +"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in " +"with\n" +"other anonymity tools into this new Debian \"superpackage\" of some sort," +" and\n" +"would love to get I2P into Debian in 2015. He claims the process is now " +"easy,\n" +"just `follow the instructions`_. We said that's funny, we've been\n" +"`stuck in the process for over 7 years`_." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99 +msgid "`follow the instructions`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100 +msgid "`stuck in the process for over 7 years`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102 +msgid "" +"He said, well, try the new process, it works great, should be no problem " +"at all\n" +"if your package is in good shape. The people in Debian that run this " +"process are\n" +"eager volunteers who want nothing more than to get more packages in. We " +"said our\n" +"package is indeed in fantastic shape, and we would try out the new " +"process as\n" +"soon as possible. If all this is true, we will be in the next Debian " +"release in\n" +"late 2015. This would be very very cool." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:114 +msgid "" +"We had a nice discussion with BitingBird of Tails. They are very happy " +"with our\n" +"rapid response to the `vulnerability disclosure`_ last summer, resulting " +"in our\n" +"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and " +"they\n" +"took `great offense`_ to that and the lack of private notification. We " +"thanked\n" +"them for taking the heat and fighting back." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:122 +msgid "`vulnerability disclosure`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123 +msgid "`0.9.14 release`" +msgstr "`release 0.9.14`" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124 +msgid "`great offense`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:126 +msgid "" +"BitingBird also handles support, and she tells us the number one issue is" +" how\n" +"long I2P takes to start up and be useful for browsing I2P sites. Her " +"standard\n" +"answer is \"wait ten more minutes\" and that seems to be effective. I2P " +"is\n" +"particularly slow to startup on Tails since it does not persist peer data" +" by\n" +"default. It would be nice to change that, but there's also things we can " +"do on\n" +"the I2P side to make things start faster. Expect some improvement in our " +"0.9.18\n" +"release." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:139 +msgid "" +"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The " +"upcoming\n" +"Tor Hidden Services changes mean that their keys will no longer fit into " +"a\n" +"portion of an IPv6 address, and he was working on a solution. We reminded" +" him\n" +"that this has always been the case for I2P (with \"GarliCat\"), that it's" +" not a\n" +"new problem. He pointed us to `a presentation`_ of his proposal. It " +"involves\n" +"storing an extra record in the hidden service directory (equivalent of a\n" +"leaseset I2P's network database). It wasn't completely clear how this " +"would\n" +"work, or if we would consider it abuse of the netDb. We'll follow up with" +" him\n" +"as he gets further." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:152 +msgid "`a presentation`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:154 +msgid "" +"New users\n" +"---------" +msgstr "" +"Nuovi utenti\n" +"---------" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:159 +msgid "" +"We spent hours and hours explaining I2P to people stopping by our table. " +"Some\n" +"had heard of I2P before, some had not; everybody had heard of Tor and had" +" at\n" +"least a vague idea of what hidden services are. As usual, introducing " +"people to\n" +"I2P was a struggle. By the end of the Congress, we became convinced that " +"a part\n" +"of the problem was a difference in terminology. Back 12 years ago, when " +"I2P and\n" +"Tor were both getting started, we each came up with terms for the various" +" parts\n" +"of our systems. Today, the Tor terminology such as \"hidden service\" is\n" +"well-understood and commonplace. The I2P terminology such as \"eepsite\" " +"is\n" +"neither. We agreed to review our documentation, router console, and other" +" places\n" +"for opportunities to simplify it and use common terms." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:172 +msgid "" +"I2P project topics\n" +"------------------" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:177 +msgid "" +"* *Spending money:* We discussed several ways to effectively use our " +"resources\n" +" in 2015, including more hardware for testing and development. Also, we " +"plan to\n" +" increase reimbursement levels for conference attendees." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:183 +msgid "" +"* *Toronto meetup:* CCC is such a productive time for us, and it seems " +"that a\n" +" second meetup in the year would be quite helpful. We have proposed it " +"for\n" +" August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. " +"It\n" +" would include developer meetings together with presentations and " +"tutorials,\n" +" all open to the public. We are attempting to gauge interest and " +"research\n" +" possible venues. If you are considering attending, please let us know " +"by\n" +" `tweeting @i2p`_ or posting `on the dev forum thread`_." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:193 +msgid "" +"* We discussed Meeh's workload and the state of the various services he " +"is\n" +" running. We made some plans to reduce his load and have some other " +"people help\n" +" out." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:199 +msgid "" +"* We reviewed our critieria for placing links to `i2pd`_ on our download " +"page.\n" +" We agreed that the only remaining item is to have a nice page on the\n" +" `Privacy Solutions web site`_ or elsewhere with binary packages for " +"Windows,\n" +" Linux, and Mac, and source packages. It's not clear who is responsible " +"for\n" +" building the packages and where the \"official\" version is. Once " +"there's an\n" +" established process for building and signing packages and an official " +"place to\n" +" put them, we're ready to link to it. If it is not feasible to host it " +"on the\n" +" Privacy Solutions website, we will discuss alternatives with orignal,\n" +" including possible migration to our download servers." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:211 +msgid "" +"* Lots of people coming by the table asked if we had a non-Java version. " +"It was\n" +" great to finally answer \"yes\" and we're eager to get the word out and" +" get more\n" +" users, testers, and developers on it." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:217 +msgid "" +"* `Vuze`_ continues to make good progress on their I2P integration. We " +"look\n" +" forward to working with them in the new year on a managed rollout to " +"more\n" +" users." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:223 +msgid "" +"* We discussed the state of Meeh's and Sindu's reseed servers. They made " +"several\n" +" improvements while at the congress and are investigating migration to\n" +" `Matt Drollette's Go implementation`_. The security and reliability of " +"our\n" +" reseed servers is vital to new users and network operation. `User " +"'backup'`_\n" +" is doing a great job monitoring and managing the pool of reseed servers." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:231 +msgid "" +"* We agreed to purchase a second root server for development, testing, " +"and\n" +" services. Echelon will be adminstering it. Contact him if you would " +"like a VM." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:236 +msgid "" +"* We reiterated that we have funds available to purchase test hardware,\n" +" especially for Windows and Mac. Talk to echelon for details." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:241 +msgid "" +"* We met with Welterde about the state of his services including his\n" +" `open tracker`_. These services are not being adequately maintained and" +" will\n" +" soon become inaccessible due to crypto changes if they are not " +"upgraded. He\n" +" committed to upgrading them soon." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:248 +msgid "" +"* We met lots of people interested in our `Android app`_. We passed " +"several\n" +" ideas and bug reports back to str4d. We plan to make a big push to give" +" the\n" +" app some development love early in the year." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:254 +msgid "" +"* Regrettably, we didn't get to see too many talks at the Congress, as we" +" were\n" +" so busy meeting with people. We plan to catch up and `watch them " +"online`_. As\n" +" usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's " +"talk was\n" +" great. We hear that the cryptography talks were good as well." +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:261 +msgid "`Toronto Crypto`" +msgstr "`Toronto Crypto`" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262 +msgid "`tweeting @i2p`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263 +msgid "`on the dev forum thread`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:266 +msgid "`Privacy Solutions web site`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:270 +msgid "`Matt Drollette's Go implementation`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271 +msgid "`User 'backup'`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:273 +msgid "`open tracker`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:275 +msgid "`Android app`" +msgstr "" + +#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:277 +msgid "`watch them online`" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:1 +msgid "" +"==============\n" +"0.9.18 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.18\n" +"==============" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:10 +msgid "0.9.18 with performance improvements and bug fixes" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:12 +msgid "" +"0.9.18 contains several bug fixes and performance improvements.\n" +"We have shortened the startup time, and reduced latency throughout our " +"network protocols.\n" +"We've increased the default connection limits for the fastest routers,\n" +"and reduced the thread usage in i2ptunnel.\n" +"UPnP fixes should improve handling of external device changes.\n" +"CPU usage in high-bandwidth routers may be reduced thanks to some NTCP " +"fixes." +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:32 +msgid "Fix parsing of ECDSA address helper in HTTP client proxy" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:33 +msgid "Fix news last-modified processing which prevented notification of update" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:34 +msgid "Improve handling of UPnP device changes" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:35 +msgid "Don't hang at startup forever waiting for entropy" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:36 +msgid "Possible fixes for high CPU usage in NTCP" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:40 +msgid "Publish router info faster when address costs change" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:41 +msgid "Start i2ptunnel 90s sooner" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:42 +msgid "Accept tunnels 10m sooner" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:43 +msgid "Increase exploratory tunnel quantity during initial exploration" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:44 +msgid "Latency reductions in several places" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:45 +msgid "" +"Add startup browser configuration with advanced config " +"routerconsole.browser" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:46 +msgid "Persistent leaseset keys to eliminate correlation with restart" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:47 +msgid "Faster unchoking of new peers in i2psnark" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:48 +msgid "More aggressive throttling of lookups at floodfills" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:49 +msgid "Tunnel build request record refactoring" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:50 +msgid "Reduce thread usage in i2ptunnel" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:51 +msgid "Add i2ptunnel server option for multihomed sites" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:52 +msgid "Disallow some common I2P application ports as router ports" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:53 +msgid "Increase connection limits for fast routers" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:54 +msgid "Add Save-As button for SusiMail messages" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:55 +msgid "Use 'hidden service' terminology in the console" +msgstr "" + +#: i2p2www/blog/2015/02/22/0.9.18-Release.rst:56 +msgid "Encrypted netdb lookups for 32-bit x86" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:1 +msgid "" +"==============\n" +"0.9.19 Release\n" +"==============" +msgstr "" +"==============\n" +"Reelase 0.9.19\n" +"==============" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:10 +msgid "0.9.19 with performance improvements and bug fixes" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:12 +msgid "" +"0.9.19 has several fixes and improvements for floodfill performance.\n" +"Many of you saw high CPU usage after 0.9.18 was released.\n" +"This was caused by a combination of increased encryption usage, the big " +"influx of Vuze users into the network,\n" +"reduced floodfills due to tighter performance requirements, and some " +"longstanding bugs.\n" +"Things should be a lot better after most of the network has updated.\n" +"As always, the best way to reduce CPU usage is to lower your bandwidth " +"limits." +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:20 +msgid "" +"We've also added new ways to reseed manually, and to generate a reseed " +"file you can easily share with others who need it.\n" +"See the reseed configuration page in the router console for more " +"information." +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:34 +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:48 +msgid "Floodfill performance improvements" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:35 +msgid "Easier ways to reseed manually from a file or URL" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:36 +msgid "New way to export reseed data for others" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:37 +msgid "Support for installing plugin from file" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:42 +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:59 +msgid "Fixes for high CPU usage in floodfills" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:43 +msgid "i2ptunnel locking fixes" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:44 +msgid "Fixes for read timeout handling in streaming" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:45 +msgid "Fix changing i2psnark data directory on Windows" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:46 +msgid "Fix multiple SSL outproxies in HTTP client" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:51 +msgid "Update to UPnP library version 3.0" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:52 +msgid "Improve tracking of floodfill lookup success" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:53 +msgid "Direct router info lookups if connected to floodfill" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:54 +msgid "Auto-adjustment of i2psnark tunnel quantity" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:55 +msgid "Increase exploratory tunnel quantity when floodfill" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:56 +msgid "Increase min and default bandwidth for i2psnark" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:57 +msgid "Improved strategies for dropping jobs on high job lag to prevent overload" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:58 +msgid "Drop tunnel build requests on high job lag" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:59 +msgid "Increase allowed clock skew in I2CP" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:60 +msgid "New HTTP error page when the server resets the connection" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:61 +msgid "Require ECDSA support for floodfill" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:62 +msgid "Republish router info faster when capabilities change" +msgstr "" + +#: i2p2www/blog/2015/04/12/0.9.19-Release.rst:63 +msgid "Better feedback in console for reseed errors" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:1 +msgid "" +"==============\n" +"0.9.20 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.20\n" +"==============" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:10 +msgid "0.9.20 with performance improvements and bug fixes" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:12 +msgid "" +"0.9.20 contains many important bug fixes, and several changes to increase" +" floodfill capacity in the network." +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:16 +msgid "" +"Routers configured for 32-64 KB of shared bandwidth may now become " +"floodfill,\n" +"and routers configured for 512 KB or more of shared bandwidth will have " +"higher connection limits.\n" +"These changes may cause your router to use more resources.\n" +"If the router becomes too busy, the best way to reduce usage is to lower " +"the bandwidth settings in your console.\n" +"If that doesn't help, you may now disable automatic floodfill on the " +"advanced configuration page in the console." +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:24 +msgid "" +"We're hopeful that these changes will increase network capacity and " +"performance,\n" +"and reduce the congestion that's been affecting the network the last " +"three months." +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:34 +msgid "" +"Finally, we're excited to announce our first-ever I2P meetup, in Toronto " +"August 15-16.\n" +"There will be lots of presentations and tutorials. All are welcome.\n" +"For more information, see the `announcement`_." +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:49 +msgid "Add support for address book export" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:50 +msgid "Add support for SSL in HTTP server tunnel" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:51 +msgid "Allow class 'M' (64-128 KBps share bandwidth) to become floodfill" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:52 +msgid "" +"Raise connection limits for new classes 'P' (512-2000 KBps share " +"bandwidth) and 'X' (over 2000 KBps)" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:53 +msgid "Add support for signed development builds" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:60 +msgid "Clock skew fixes" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:61 +msgid "Fixes and configuration for when IPv4 is firewalled but IPv6 still works" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:62 +msgid "Locking fixes for i2ptunnel clients to prevent hangs at startup" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:63 +msgid "Verify hostnames when reseeding" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:64 +msgid "Fix deletion of config files for deleted torrents in i2psnark" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:65 +msgid "Fix hangs fetching proxy.i2p local resources via Privoxy" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:66 +msgid "Fixes for duplicate shared clients" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:67 +msgid "Fix for occasional page truncation in HTTP client" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:68 +msgid "Fixes for handling corrupted SSU packets" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:69 +msgid "Fix closing of SAM sessions when I2P session closes" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:70 +msgid "Fix bugs in handling streaming resets" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:77 +msgid "Reduce NTCP threads" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:78 +msgid "Eliminate SimpleScheduler threads" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:79 +msgid "Add continent-based NTP servers as fallbacks for country-based ones" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:80 +msgid "Remove all default non-SSL reseed hosts" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:81 +msgid "Disable fallback to non-su3 reseeding" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:82 +msgid "Several fixes in streaming for better \"loopback\" performance" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:83 +msgid "Reduce latency in i2ptunnel" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:84 +msgid "Add a larger Bloom filter for very high bandwidth and memory" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:85 +msgid "" +"Add Bloom filter warning when configured for high bandwidth but not " +"enough memory" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:86 +msgid "Reduce max netdb search depth to reduce floodfill load" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:87 +msgid "Improved header processing and error handling in i2ptunnel HTTP server" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:88 +msgid "" +"Better error handling and user feedback when HTTP client tunnel is " +"disabled" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:89 +msgid "More changes to improve floodfill capacity" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:90 +msgid "New configuration for forcing IPv4 (only) to firewalled on /confignet" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:91 +msgid "New configuration for floodfill on /configadvanced" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:92 +msgid "Show separate IPv4 and IPv6 status in summary bar when appropriate" +msgstr "" + +#: i2p2www/blog/2015/06/02/0.9.20-Release.rst:93 +msgid "Better handling of corrupt SSU packets" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:1 +msgid "" +"==============\n" +"Toronto Meetup\n" +"==============" +msgstr "" +"==============\n" +"Meetup di Toronto\n" +"==============" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:10 +msgid "I2P Meetup in Toronto on August 15-16." +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:12 +msgid "" +"The I2P team is proud to announce that we are going to host a meetup in " +"Toronto on August 15-16.\n" +"A number of members of our community will be attending and are going to " +"host talks, workshops and discussions about and relating to I2P. This " +"event is not just for I2P people though, it's meant for everyone." +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:17 +msgid "" +"If you're curious about I2P, interested in privacy/cryptography/anonymity" +" or just want to come by and talk to us, please do. This is an event for " +"everyone. If you're not familiar with any of these topics, come by anyway" +" and we'll show you how I2P works and what you can do with it.\n" +"\n" +"The event is entirely free, you don't need to sign up or register." +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:23 +msgid "" +"The meetup couldn't have been arranged without our friends at `Toronto " +"Crypto `_ which have been helping us organize" +" the event, and our friends at `Hacklab `_ which are" +" providing us with a very nice space." +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:27 +#: i2p2www/blog/2015/07/16/I2PCon.rst:126 +msgid "If you have any questions, feel free to contact us on `@geti2p`_." +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:34 +#: i2p2www/blog/2015/07/16/I2PCon.rst:38 +msgid "" +"Details\n" +"=======" +msgstr "" +"Dettagli\n" +"=======" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:39 +#: i2p2www/blog/2015/07/16/I2PCon.rst:57 +msgid "" +"Location\n" +"--------" +msgstr "" +"Percorso\n" +"--------" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:44 +msgid "`Hacklab `_ at 1266 Queen Street West, Toronto." +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:48 +msgid "" +"Day 1, August 15 - 3PM\n" +"----------------------" +msgstr "" +"Giorno 1, 15 agosto - 3PM\n" +"----------------------" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:53 +msgid "" +"The focus will be on an introduction to topics surrounding I2P, privacy " +"and anonymity online. People of all backgrounds and knowledge levels are " +"welcome to attend." +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:57 +msgid "I2P Presentation" +msgstr "Presentazione di I2P" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:58 +msgid "Crypto party introduction" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:59 +msgid "Crypto party" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:61 +msgid "" +"The crypto party will contain a number of stations where " +"privacy/anonymity software will be demoed. The goal is to provide people " +"with the tools they need to communicate securely." +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:65 +msgid "`Vuze/I2P`_ - Downloading torrents anonymously" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:66 +msgid "`Veracrypt`_ - Encrypt your data" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:67 +msgid "`I2PBote`_ - Anonymous decentralized email" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:68 +msgid "Your station idea here" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:70 +msgid "" +"We're currently looking for help staffing the stations. If you want to " +"help out, you can! Bring a monitor/laptop and run a station. The station " +"could be any of the ones listed above, or any other privacy/anonymity " +"related one you would like to run. Please contact us at `@geti2p`_ if " +"you're interested." +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:79 +msgid "" +"Day 2, August 16 - 1PM\n" +"----------------------" +msgstr "" +"Giorno 2, 16 agosto - 1PM\n" +"----------------------" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:84 +msgid "" +"The focus will be on in-depth topics surrounding I2P, the roadmap and " +"development. Anyone is welcome to attend, but the content will be " +"somewhat technical." +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:88 +msgid "I2P Technical presentation" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:89 +msgid "Technical discussion" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:90 +msgid "I2P App Dev Into" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:91 +msgid "I2PD presentation" +msgstr "" + +#: i2p2www/blog/2015/06/02/Toronto-Meetup.rst:92 +msgid "I2P on Android" +msgstr "I2P su Android" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:1 +msgid "" +"======\n" +"I2PCon\n" +"======" +msgstr "" +"======\n" +"I2PCon\n" +"======" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:10 +msgid "I2PCon will be in Toronto on August 15-16." +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:13 +msgid "" +"I2PCon is the first event of its kind. It has two short term goals. Where" +" the\n" +"first one is to provide the general public with an event where knowledge " +"about\n" +"privacy and privacy concerns can be obtained. The second goal is to " +"further the\n" +"I2P project and its community. This will take the shape of technical " +"discussions\n" +"about cryptography, anonymity and I2P centric topics." +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:21 +msgid "" +"There is a larger and more long-term goal of this event, and it is to " +"build a\n" +"commnutiy of privacy-conscious individuals. By connecting people who " +"recognize\n" +"the importance of privacy, we would like to provide a forum where this " +"community\n" +"can grow." +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:28 +msgid "" +"The idea for this event was first spawned by our wonderful friends at\n" +"`Toronto Crypto`_. The venue and everything relating to it is provided by" +"\n" +"`Hacklab`_. Without either of them this event would not have been " +"possible, so\n" +"thank you both." +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:43 +msgid "" +"Cost\n" +"----" +msgstr "" +"Costo\n" +"----" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:48 +msgid "" +"I2PCon is entirely free to attend! We ask you to register `here`_, to " +"give us\n" +"an estimate of how many people will be attending. No identifying " +"information has\n" +"to be given in order to register, but if you have any concerns, please " +"let us\n" +"know." +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:55 +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:45 +msgid "`here`" +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:62 +msgid "`Hacklab`_ at 1266 Queen Street West, Unit #6, Toronto." +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:66 +msgid "" +"Venue\n" +"-----" +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:71 +msgid "Power and WiFi access will be provided by `Hacklab`_." +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:76 +msgid "" +"Schedule\n" +"========" +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:81 +msgid "" +"Day 1, August 15\n" +"----------------" +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:98 +msgid "" +"Day 2, August 16\n" +"----------------" +msgstr "" + +#: i2p2www/blog/2015/07/16/I2PCon.rst:121 +msgid "" +"I'm confused and would like some answers\n" +"========================================" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:1 +msgid "" +"==============\n" +"0.9.21 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.21\n" +"==============" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:10 +msgid "0.9.21 with performance improvements and bug fixes" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:12 +msgid "" +"0.9.21 contains several changes to add capacity to the network, increase " +"the efficiency of the floodfills,\n" +"and use bandwidth more effectively.\n" +"We have migrated the shared clients tunnels to ECDSA signatures and added" +" a DSA fallback\n" +"using the new \"multisession\" capability for those sites that don't " +"support ECDSA." +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:19 +msgid "" +"The speakers and the schedule of the I2PCon in Toronto 2015 have been " +"announced.\n" +"Have a look on the `I2PCon page`_ for details.\n" +"Reserve your seat on `Eventbrite`_." +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:40 +msgid "Add multisession support for dual-signature crypto on the same tunnels" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:41 +msgid "Use multisession for shared clients" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:42 +msgid "Increase default outbound bandwidth limit to 60 KBps" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:43 +msgid "Increase default maximum participating tunnels" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:44 +msgid "" +"Floodfills will send database store acks directly if connected, for " +"efficiency" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:45 +msgid "Set TCP keepalive on I2CP and SAM sockets" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:46 +msgid "More efficient decompression in HTTP proxy, use less threads" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:47 +msgid "Add support for fast extensions in i2psnark" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:48 +msgid "i2psnark only autostarts torrents that were running previously" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:49 +msgid "Add support for translated console news" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:54 +msgid "SSU fixes to compete better with NTCP for bandwidth when limited" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:55 +msgid "Fixes to prevent SSU stalls" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:56 +msgid "" +"Wait for outbound tunnels before sending first leaseset to client, to " +"prevent dropping first message" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:57 +msgid "Clean up resources correctly when SAM stops" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:58 +msgid "Better error handling and notification when HTTP proxy is not running" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:59 +msgid "More i2ptunnel fixes at startup and shutdown of tunnels" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:60 +msgid "Fix total_size in i2psnark metadata message" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:61 +msgid "Restore dates in console news headers" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:62 +msgid "Several I2CP fixes" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:67 +msgid "Use same session for naming lookups in I2PSocketEepGet" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:68 +msgid "Increase max bandwidth to 16 MBps, add larger Bloom filter" +msgstr "" + +#: i2p2www/blog/2015/07/31/0.9.21-Release.rst:69 +msgid "" +"New floodfills will send their info to nearby floodfills to speed " +"integration" +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:1 +msgid "" +"============================\n" +"I2PCon: Mission Accomplished\n" +"============================" +msgstr "" +"============================\n" +"I2PCon: Missione completata\n" +"============================" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:10 +msgid "I2PCon: Mission Accomplished" +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:13 +msgid "" +"I2PCon has been a giant success. For us, the I2P contributors, it " +"represents a\n" +"leap forward in terms of what we're capable of pulling off as a " +"community, how we\n" +"communicate the usecases of I2P and reach out to privacy conscious " +"individuals.\n" +"\n" +"By arranging this event, we've also grown our community. People who've " +"previously\n" +"only lurked on our irc channels, or run our software or possibly hadn't " +"even heard\n" +"of I2P are now a part of our comminuty.\n" +"\n" +"This event has been our first active step towards building a large and " +"inclusive\n" +"community, and as such it's been great success." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:27 +msgid "" +"Minutiae\n" +"========\n" +"On day 2 we had two short discussion sessions. A more general discussion " +"and a roadmapping discussion.\n" +"\n" +"The minutiae can be found here: `I2P Roadmap session minutiae`_ and `I2P " +"Discussion session minutiae`_." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:36 +msgid "" +"Photos\n" +"======" +msgstr "" +"Foto\n" +"======" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:44 +msgid "The learn how to setup I2P crypto party station" +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:49 +msgid "The learn how use I2P and Vuze party station" +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:54 +msgid "David Dagons wonderful talk" +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:56 +msgid "" +"Thanks\n" +"======" +msgstr "" +"Ringraziamenti\n" +"======" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:61 +msgid "" +"We've had some wonderful speakers, from both inside- and outside of our " +"community.\n" +"\n" +"`David Dagon`_ talked to us about the way forward and how I2P could " +"handle potential abuse.\n" +"\n" +"`Lance James`_ - the creator of our predecessor iip - said Hi and gave us" +" his thoughts about how far I2P has come.\n" +"\n" +"`Nick Johnston`_ gave us a wonderful talk about why privacy matters and " +"why you should care." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:71 +msgid "" +"I would also like to thank the speakers from our community. `psi`_, " +"`@str4d`_ and `zzz`_ who all had\n" +"wonderful talks. Improving our ability to inform people about I2P is " +"something that\n" +"is going to be important for us going forward." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:77 +msgid "" +"I would like to thank `Sadie`_ and Siew for helping us out with marketing" +" and graphics.\n" +"Without you I2PCon would've been a very different event." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:82 +msgid "" +"I would like to thank `@chlorelium`_ and `Hacklab`_ for being the most " +"wonderful of hosts." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:86 +msgid "" +"I would like to thank `@darknetj`_, P and `@hizeena`_ of `Toronto " +"Crypto`_ for their help during the event." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:90 +msgid "" +"I would like to thank `@z3r0fox`_ for doing a wonderful job with the AV " +"and doing all of the post-production\n" +"work for the videos of all the talks." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:95 +msgid "" +"I would like to thank `@killyourtv_i2p`_ for hosting a very popular " +"crypto party station." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:99 +msgid "" +"Thanks to our new favorite journalist `@robinlevinson`_, for showing an " +"interest in our cause and\n" +"educating yourself about the technologies involved." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:104 +msgid "" +"Thanks for all the pizza `@Panago_Pizza`_, it keept us going. You very " +"much made this event better." +msgstr "" + +#: i2p2www/blog/2015/08/20/I2PCon_Mission_Accomplished.rst:108 +msgid "" +"Finally I would like to thank everyone else who just showed up to the " +"event and helped out in any way\n" +"they could.\n" +"ComradeNosebleed, LazyGravy, `cacapo`_, Xmz, ZeroRax, `echelon`_, it was " +"most excellent to hang out\n" +"with you." +msgstr "" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:1 +msgid "" +"==============\n" +"0.9.22 Release\n" +"==============" +msgstr "" +"==============\n" +"Release 0.9.22\n" +"==============" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:10 +msgid "0.9.22 with bug fixes and start of Ed25519 migration" +msgstr "" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:12 +msgid "" +"0.9.22 contains fixes for i2psnark getting stuck before completion, and " +"begins the migration of router infos to new, stronger Ed25519 signatures." +"\n" +"To reduce network churn, your router will have only a small probability " +"of converting to Ed25519 at each restart.\n" +"When it does rekey, expect to see lower bandwidth usage for a couple of " +"days as it reintegrates into the network with its new identity.\n" +"If all goes well, we will accelerate the rekeying process in the next " +"release." +msgstr "" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:19 +msgid "" +"I2PCon Toronto was a big success!\n" +"All the presentations and videos are listed on the `I2PCon page`_." +msgstr "" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:30 +msgid "`I2PCon page`" +msgstr "" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:38 +msgid "Start migration to Ed25519 router info signatures" +msgstr "" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:39 +msgid "Convert i2psnark destinations to Ed25519 signatures" +msgstr "" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:44 +msgid "" +"Fix i2psnark getting stuck before download complete, and not deleting " +"temp files" +msgstr "" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:45 +msgid "" +"Fix starting of torrents added by copying torrent file to i2psnark " +"directory" +msgstr "" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:46 +msgid "Fix UPnP 'content not allowed in trailing section' error" +msgstr "" + +#: i2p2www/blog/2015/09/12/0.9.22-Release.rst:47 +msgid "Fix excluded SSL ciphers in console" +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:1 +msgid "" +"==================\n" +"Community Outreach\n" +"==================" +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:10 +msgid "A start to more frequent community status reports." +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:12 +msgid "Meta" +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:14 +msgid "" +"Greetings!\n" +"This is the first in a long series of blogs to help the community see " +"what is happening in the I2P community.\n" +"Since many awesome events are happening *inside* the network, we think it" +" will be worthwhile to talk about some of activities here." +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:20 +msgid "A Call for Feedback" +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:22 +msgid "" +"Let's face it -- our console needs improvement.\n" +"Our site could use an update as well.\n" +"We are looking for feedback on how to improve the usability of I2P for " +"new and existing users!" +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:28 +msgid "" +"Any and all feedback is welcome.\n" +"Please contact `@GetI2P`_, `@str4d`_, or `@YrB1rd`_.\n" +"If you don't feel comfortable using Twitter, we are always available via " +"the in-network IRC channel.\n" +"You don't have to be a long time user.\n" +"We want to hear from all sorts of people!" +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:40 +msgid "Developer Meeting Synopsis" +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:42 +msgid "" +"On 03 November there was an I2P developer meeting (`log`_).\n" +"This meeting focused on adding new links to the router console, " +"preparation for CCC, finding a replacement for forum.i2p, and website " +"improvements." +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:49 +msgid "" +"The consensus was to not add dogecoindark.i2p.\n" +"There are concerns about usability due to many images being included on " +"the page.\n" +"Exchanged.i2p is conditionally added, as long as the maintainer adds a " +"disclaimer on the site.\n" +"I2Pwiki.i2p (a backup of ugha.i2p, an older wiki) was accepted, as was " +"lenta.i2p (a russian news site)." +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:56 +msgid "" +"str4d proposed blocking off the \\*.i2p.i2p namespace so they can be used" +" for developer's services.\n" +"He also suggested a more formalized technical proposal system, with more " +"prominence on the main website." +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:61 +msgid "" +"The I2P Team is going to be in Hamburg, Germany for the 32nd Chaos " +"Computer Congress.\n" +"More details are to come on this, but we can promise there will be " +"stickers." +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:66 +msgid "General Announcements" +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:68 +msgid "Thank you to `TorontoCrypto`_ for hosting the newest I2P reseed server!" +msgstr "" + +#: i2p2www/blog/2015/11/15/Community-Outreach.rst:74 +msgid "" +"Translation deadline Thursday, 12 November, translators please update. " +"All translations are done via `Transifex`_ ." +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:1 +msgid "" +"==============\n" +"0.9.23 Release\n" +"==============" +msgstr "" +"==============\n" +" Release 0.9.23\n" +"==============" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:10 +msgid "" +"0.9.23 contains a variety of bug fixes, and some minor improvements in " +"I2PSnark" +msgstr "" +"La versione 0.9.23 risolve diversi bug; inoltre apporta alcuni piccoli " +"miglioramenti ad I2PSnark." + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:12 +msgid "" +"Hello I2P! This is the first release signed by me (str4d), after 49 " +"releases\n" +"signed by zzz. This is an important test of our redundancy for all " +"things,\n" +"including people." +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:18 +msgid "" +"Housekeeping\n" +"============" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:23 +msgid "" +"My signing key has been in router updates for over two years (since " +"0.9.9), so\n" +"if you are on a recent version of I2P this update should be just as easy " +"as\n" +"every other update. However, if you are running an older version than " +"0.9.9, you\n" +"will first need to manually update to a recent version. Update files for " +"recent\n" +"versions `can be downloaded here`_, and instructions on how to manually " +"update\n" +"`are provided here`_. Once you have manually updated, your router will " +"then find\n" +"and download the 0.9.23 update as usual." +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:33 +msgid "`can be downloaded here`" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:35 +msgid "`are provided here`" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:37 +msgid "" +"If you installed I2P via a package manager, you are not affected by the " +"change,\n" +"and can update as usual." +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:42 +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:12 +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:12 +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:19 +msgid "" +"Update details\n" +"==============" +msgstr "" +"Dettagli dell'aggiornamento\n" +"==============" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:47 +msgid "" +"The migration of RouterInfos to new, stronger Ed25519 signatures is going" +" well,\n" +"with at least half of the network already estimated to have rekeyed. This" +"\n" +"release accelerates the rekeying process. To reduce network churn, your " +"router\n" +"will have a small probability of converting to Ed25519 at each restart. " +"When it\n" +"does rekey, expect to see lower bandwidth usage for a couple of days as " +"it\n" +"reintegrates into the network with its new identity." +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:56 +msgid "" +"Note that this will be the last release to support Java 6. Please update " +"to\n" +"Java 7 or 8 as soon as possible. We are already working to make I2P " +"compatible\n" +"with the upcoming Java 9, and some of that work is in this release." +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:62 +msgid "" +"We have also made some minor improvements in I2PSnark, and added a new " +"page in\n" +"the routerconsole for viewing older news items." +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:77 +msgid "Accelerate transition to Ed25519" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:82 +msgid "" +"Fix some bugs soft restarting after a large clock shift (e.g. resume) " +"(but more to do)" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:83 +msgid "" +"Fix streaming retransmission timers that were dying, and related timer " +"bugs" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:84 +msgid "Fix streaming connections rejected while tunnel is opening" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:85 +msgid "Fix rare i2psnark and UPnP deadlocks" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:86 +msgid "Fix lifetime participating bandwidth display in console" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:91 +msgid "Increase default outbound exploratory tunnel length to 3" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:92 +msgid "" +"Use max of 2 not-failing peers in exploratory tunnels to improve build " +"success" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:93 +msgid "Add support for hostnames prefixed with \"www.\"" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:94 +msgid "" +"Store news feed items separately on disk, show on new /news page, limit " +"display on home page to 2" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:95 +msgid "Increase probability of rekeying to EdDSA" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:96 +msgid "Detect for broken ECDSA support in Gentoo" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:97 +msgid "Console: Add a Java 6 warning, this is the last release to support Java 6" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:98 +msgid "Changes to prepare for Java 9 compatibility" +msgstr "Cambiamenti per preparare compatibilità con Java 9" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:99 +msgid "" +"Pass Accept-Encoding header through client and server proxies, to allow " +"end-to-end compression" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:102 +msgid "Increase piece size, piece count, and file count limits" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:103 +msgid "Save added and completed times" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:104 +msgid "Save magnet parameters across restart" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:105 +msgid "Don't delete .torrent file on errors at startup, rename to .torrent.BAD" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:106 +msgid "Add recheck, start, stop buttons on details pages" +msgstr "" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:107 +msgid "Add option to disable \"smart sort\"" +msgstr "Aggiunta opzione per disabilitare lo \"smart sort\"" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:109 +msgid "Speed up IP address validation" +msgstr "Validazione indirizzi IP più rapida" + +#: i2p2www/blog/2015/11/19/0.9.23-Release.rst:110 +msgid "Separate streaming blacklists for ECDSA and EdDSA" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:1 +msgid "" +"=========\n" +"CCC Recap\n" +"=========" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:10 +msgid "CCC!" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:12 +msgid "" +"Attending: Sadie, Colin, lazygravy, zzz, hottuna, kytv, cacapo, and " +"eche|on." +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:16 +msgid "" +"Start\n" +"=====\n" +"The project has had another successful year at CCC.\n" +"We would like to thank the volunteers at `32C3`_ for all of their help in" +" organizing this event and for being accommodating hosts for us.\n" +"Many I2P contributors were able to attend this year's Congress due to " +"many of the generous donations from supporters like you to the project.\n" +"If you would like to fund I2P, please see `our donation page`_ for more " +"information." +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:25 +msgid "`32C3`" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:26 +msgid "`our donation page`" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:28 +msgid "" +"Just like previous years we were located in Noisy Square, located near " +"the EFF's table.\n" +"This proved to be an ideal spot for us as our table was almost always " +"busy with current and new users who were interested in I2P, many of whom " +"we wouldn't have otherwise had the ability to talk to." +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:62 +msgid "" +"Reseed Status\n" +"=============" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:67 +msgid "Let's get more reseeds!" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:71 +msgid "" +"If you don't know what a reseed server is, it is first the connection new" +" routers use to find peers.\n" +"There was a lot of discussion around the current status of the reseed " +"network right now.\n" +"As always, more reseed operators are needed!\n" +"If you would like to strengthen the reseed infrastructure, (or if you're " +"talented with Go) email `backup -at- i2pmail.org`_." +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:78 +msgid "`backup -at- i2pmail.org`" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:80 +msgid "" +"Sybil Detection (beta)\n" +"======================" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:85 +msgid "" +"Due to the decentralized nature of I2P detecting Sybil attacks is not as " +"straight forward as on other networks (i.e. Tor).\n" +"To mitigate this zzz has been working on a new router-based Sybil " +"detection tool.\n" +"To be brief, the tool runs in the router, and collects information on " +"floodfills your router is currently aware of.\n" +"Currently the tool is mainly collecting a baseline and does not act on " +"any of the information it is collecting.\n" +"Expect to see a writeup on this more as 0.9.25 or 0.9.26 approaches, as " +"it is still in active development" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:93 +msgid "" +"Development Meeting\n" +"===================" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:98 +msgid "" +"On the 30th we held an in person `meeting`_ at our table.\n" +"The meeting focused on organizationally preparing for more project " +"management, and public relations (both from Sadie)." +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:103 +msgid "`meeting`" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:105 +msgid "" +"We discussed how much of the work done on I2P is lost in the commits and " +"there is not much to see for our users.\n" +"To remedy this lazygravy plans on preparing a series of posts explaining " +"some technical topics in I2P.\n" +"The initial ideas that we discussed writing posts on are what encrypted " +"lease sets are, why different tunnel types are needed, and some " +"observations seen in `I2Spy`_.\n" +"But these are just the start and we would like to hear feedback on topics" +" we should write about!" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:112 +msgid "`i2spy`" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:114 +msgid "" +"Meeting (Future)\n" +"================" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:119 +msgid "There will be a `another meeting`_ on 2 Feburary 2016 to discuss:" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:123 +msgid "Review of assigned tasks from 30 December meeting" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:124 +msgid "Project meeting plan for 2016" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:125 +msgid "GMP 6 readiness" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:126 +msgid "A proposal for a code of conduct" +msgstr "" + +#: i2p2www/blog/2016/01/23/32C3.rst:128 +msgid "`another meeting`" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:1 +msgid "" +"==============\n" +"0.9.24 Release\n" +"==============" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:10 +msgid "0.9.24 contains a variety of bug fixes and performance enhancements" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:17 +msgid "" +"0.9.24 contains a new version of SAM (v3.2) and numerous bug fixes and " +"efficiency improvements.\n" +"Note that this release is the first to require Java 7.\n" +"Please update to Java 7 or 8 as soon as possible.\n" +"Your router will not automatically update if you are using Java 6." +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:24 +msgid "" +"To prevent the problems caused by the ancient commons-logging library, we" +" have removed it.\n" +"This will cause very old I2P-Bote plugins (0.2.10 and below, signed by " +"HungryHobo) to crash if they have IMAP enabled.\n" +"The recommended fix is to replace your old I2P-Bote plugin with the " +"current one signed by str4d.\n" +"For more details, see `this post`_." +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:31 +msgid "`this post`" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:33 +msgid "" +"We had a great `32C3 Congress`_ and are making good progress on our 2016 " +"project plans.\n" +"Echelon gave a talk on I2P's history and current status, and his slides " +"are `available here`_ (pdf).\n" +"Str4d attended `Real World Crypto`_ and gave a talk on our crypto " +"migration, his slides are `here`_ (pdf)." +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:39 +msgid "`32C3 Congress`" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:41 +msgid "`available here`" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:43 +msgid "`Real World Crypto`" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:57 +msgid "Java 7 now required" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:58 +msgid "" +"SAM 3.2, with several new advanced features, command parser improvements," +" and lots of bug fixes" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:59 +msgid "Router Family" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:60 +msgid "Commons logging removed" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:65 +msgid "Fix HTML escaping in the console plugin table" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:66 +msgid "Fix rare deadlocks in the router" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:67 +msgid "Fix the tunnel build Bloom filter" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:68 +msgid "" +"Don't remove tunnel on next-hop failure indication from transport, it " +"isn't reliable" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:69 +msgid "Fix formatting in summary bar to prevent overflow" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:70 +msgid "Fix console links in i2ptunnel error pages when on nonstandard host/port" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:71 +msgid "" +"Don't query floodfills whose version is too old to support encrypted " +"replies" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:72 +msgid "Reduce out-of-order delivery in SSU" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:73 +msgid "Fix a rare NPE in the tunnel build handler" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:78 +msgid "Listen for Windows Service shutdown events to shutdown cleanly" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:79 +msgid "Fix some IPv6 issues on Windows" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:80 +msgid "Change Jetty request logging from b64 to b32" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:81 +msgid "" +"New 'family' indication in netdb, don't use two of the same family in a " +"tunnel" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:82 +msgid "New overview picture in SusiDNS" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:83 +msgid "Close connection faster if it's for a rejected tunnel request" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:84 +msgid "Use SSU extended options field for session request message" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:85 +msgid "Request introduction in the SSU extended options" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:86 +msgid "" +"Don't offer to introduce unless requested, to introduce only those that " +"need it" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:87 +msgid "Experimental Sybil analysis tool, requires routerconsole.advanced=true" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:88 +msgid "Persist some profile netdb stats that weren't being saved" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:89 +msgid "Memory reduction and other efficiency improvements throughout" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:90 +msgid "Increase several limits in i2psnark" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:91 +msgid "New streaming unit tests" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:92 +msgid "Fix some SSU stats on /peers to be consistent with NTCP" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:93 +msgid "Change default sig type for new i2ptunnels to Ed25519" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:94 +msgid "Increase router rekey probability at startup again" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:95 +msgid "New Chinese (Taiwan) translation" +msgstr "" + +#: i2p2www/blog/2016/01/27/0.9.24-Release.rst:102 +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:73 +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:93 +msgid "`Full list of fixed bugs`" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:1 +msgid "" +"==============\n" +"0.9.25 Release\n" +"==============" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:10 +msgid "0.9.25 contains SAM 3.3, QR codes, and bug fixes" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:17 +msgid "" +"0.9.25 contains a major new version of SAM, v3.3, to support " +"sophisticated multiprotocol applications.\n" +"It adds QR codes for sharing hidden service addresses with others,\n" +"and \"identicon\" images for visually distinguishing addresses." +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:23 +msgid "" +"We've added a new \"router family\" configuration page in the console,\n" +"to make it easier to declare that your group of routers is run by a " +"single person.\n" +"There are several changes to increase the capacity of the network and " +"hopefully improve tunnel build success." +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:39 +msgid "Display of identicons and QR codes in address book and i2ptunnel" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:40 +msgid "SAM v3.3 with advanced features" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:41 +msgid "Configuration page for router family" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:42 +msgid "Custom icons for plugins" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:43 +msgid "Internal implementation of self-signed certificate generation" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:44 +msgid "Add i2ptunnel http server options to block by referer or user-agent" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:49 +msgid "IRC server tunnel default fix to help reliability" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:50 +msgid "Don't wait until a lease expires to switch to a new on" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:55 +msgid "Preliminary support for certificate revocations" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:56 +msgid "Preliminary support for storing EdDSA and ElGamal keys in keystores" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:57 +msgid "More efficient signing and verification with EdDSA" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:58 +msgid "Increase default connection limits" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:59 +msgid "Increase default inbound bandwidth" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:60 +msgid "Increase max files per torrent in i2psnark" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:61 +msgid "Add more sanity checks to detect bad system clock" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:62 +msgid "Improve news styling in console" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:63 +msgid "Improve certificate blacklist implementation" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:64 +msgid "Faster disconnect after publishing router info to floodfill" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:65 +msgid "Smooth out the dropping of idle SSU sessions" +msgstr "" + +#: i2p2www/blog/2016/03/22/0.9.25-Release.rst:66 +msgid "Add X-Content-Type-Options headers in console" +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:1 +msgid "" +"==============\n" +"I2P Summer Dev\n" +"==============" +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:10 +msgid "" +"We are pleased to announce that this summer, I2P will be embarking on a " +"development program aimed at improving the privacy software ecosystem for" +" both developers and users." +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:12 +msgid "" +"Over the last few years, the need for users to be in control of their own" +" data\n" +"has become increasingly apparent. Some excellent progress had been made " +"in this\n" +"regard with the rise of messaging apps like Signal_, and file storage " +"systems\n" +"like Tahoe-LAFS_. The ongoing work of `Let's Encrypt`_ to bring HTTPS to " +"the\n" +"whole world is steadily gaining traction." +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:20 +msgid "" +"But building privacy and anonymity into applications is not trivial. Much" +" of the\n" +"software people use every day was not designed to be privacy-preserving, " +"and the\n" +"tools developers have available are generally not easy to work with. The\n" +"recently-published OnionScan_ survey gives some insight into just how " +"easy it is\n" +"for even technical users to mis-configure their services, completely " +"undermining\n" +"their intentions." +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:35 +msgid "" +"Helping developers help their users\n" +"===================================" +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:40 +msgid "" +"We are pleased to announce that this summer, I2P will be embarking on a\n" +"development program aimed at improving the privacy software ecosystem. " +"Our goal\n" +"is to make life easier both for developers wanting to leverage I2P in " +"their\n" +"applications, and for users trying to configure and run their apps " +"through I2P." +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:47 +msgid "We will be focusing our time this summer into three complementary areas:" +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:51 +msgid "" +"June: APIs\n" +"----------" +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:56 +msgid "" +"In June, we will be updating the various libraries that exist for " +"interfacing\n" +"with I2P. We have made significant progress this year on extending our " +"SAM_ API\n" +"with additional features, such as support for datagrams and ports. We " +"plan to\n" +"make these features easily accessible in our C++ and Python libraries." +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:63 +msgid "" +"We will also soon be making it much easier for Java and Android " +"developers to\n" +"add I2P support to their applications. Stay tuned!" +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:70 +msgid "" +"July: Apps\n" +"----------" +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:75 +msgid "" +"In July we will be working with applications that have expressed interest" +" in\n" +"adding support for I2P. There are some really neat ideas being developed " +"in the\n" +"privacy space right now, and we want to help their communities leverage " +"over a\n" +"decade of research and development on peer-to-peer anonymity. Extending " +"these\n" +"applications to work natively over I2P is a good step forward for " +"usability, and\n" +"in the process will improve how these applications think about and handle" +" user\n" +"information." +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:85 +msgid "" +"August: Plugins\n" +"---------------" +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:90 +msgid "" +"Finally, in August we will turn out attention to the apps we bundle " +"inside I2P,\n" +"and the wider array of plugins. Some of these are due for some love, to " +"make\n" +"them more user-friendly - as well as fix any outstanding bugs! We hope " +"that\n" +"longtime I2P supporters will enjoy the outcome of this work." +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:98 +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:124 +msgid "" +"Take part in Summer Dev!\n" +"========================" +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:103 +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:129 +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" +" usable\n" +"websites or interfaces, or writing guides for users: come and chat with " +"us on\n" +"IRC or Twitter! We are always happy to \"see\" new \"faces\" in our " +"community, both\n" +"inside and outside I2P. We'll be sending I2P stickers out to all new\n" +"contributors taking part (or possibly other pending I2P goodies)!" +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:112 +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:138 +msgid "" +"Likewise, if you are an application developer who wants a hand with " +"integrating\n" +"I2P, or even just to chat about the concepts or details: get in touch! If" +" you\n" +"want to get involved in our July Apps month, contact `@GetI2P`_, `@i2p`_ " +"or\n" +"`@str4d`_ on Twitter. You can also find us in #i2p-dev on OFTC or " +"FreeNode." +msgstr "" + +#: i2p2www/blog/2016/06/01/I2P-Summer-Dev.rst:119 +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:145 +msgid "" +"We'll be posting here as we go, but you can also follow our progress, and" +" share\n" +"your own ideas and work, with the hashtag `#I2PSummer`_ on Twitter. Bring" +" on the\n" +"summer!" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:1 +msgid "" +"==============\n" +"0.9.26 Release\n" +"==============" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:10 +msgid "" +"0.9.26 contains crypto updates, Debian packaging improvements, and bug " +"fixes" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:12 +msgid "" +"I2P is now a proposed site on Stack Exchange!\n" +"Please `commit to using it`_ so the beta phase can begin." +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:17 +msgid "`commit to using it`" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:24 +msgid "" +"0.9.26 contains a major upgrade to our native crypto library,\n" +"a new addressbook subscription protocol with signatures,\n" +"and major improvements to the Debian/Ubuntu packaging." +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:30 +msgid "" +"For crypto, we have upgraded to GMP 6.0.0, and added support for newer " +"processors,\n" +"which will speed up crypto operations considerably.\n" +"Also, we are now using constant-time GMP functions to prevent side-" +"channel attacks.\n" +"For caution, the GMP changes are enabled for new installs and " +"Debian/Ubuntu builds only;\n" +"we will include them for in-net updates in the 0.9.27 release." +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:38 +msgid "" +"For Debian/Ubuntu builds, we have added dependencies on several packages," +"\n" +"including Jetty 8 and geoip, and removed the equivalent bundled code." +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:43 +msgid "" +"There's a collection of bug fixes also, including a fix for a timer bug\n" +"that caused instability and performance degradations over time." +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:58 +msgid "" +"GMP 6.0.0 and jbigi/jcpuid native libraries, enabling significant " +"speedups on newer architectures, and constant-time crypto operations " +"(new installs and Debian/Ubuntu builds only, will include in the updates " +"in the next release, 0.9.27)" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:59 +msgid "Addressbook subscription protocol, enabling signed addressbook updates" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:60 +msgid "Generate signed authentication strings for subscriptions in i2ptunnel" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:61 +msgid "" +"Enhance hosts blockfile format to allow for multiple destinations per " +"entry" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:62 +msgid "Use system GeoIP database when available" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:63 +msgid "" +"Remove systray4j.jar from non-Windows installers and Debian/Ubuntu " +"packages" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:64 +msgid "" +"Remove multiple external libraries from Debian/Ubuntu builds, and add " +"dependencies on: geoip-database, gettext-base, libgetopt-java, " +"libjetty8-java, libservlet3.0-java, glassfish-javaee" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:65 +msgid "" +"Store CRLs received in the news feed, to distribute key revocations when " +"necessary" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:66 +msgid "" +"Enhancements to the desktopgui system tray feature, to be enabled by " +"default in next release" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:67 +msgid "Wrapper 3.5.29 (new non-Windows installs only)" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:73 +msgid "" +"Fix periodic timers not firing after a backwards OS clock shift, which " +"caused widespread instability and gradual deterioration" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:74 +msgid "" +"Fix wrapper on FreeBSD 10 (new installs only, see ticket #1118 for manual" +" fix)" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:75 +msgid "Fix NPE on hostname lookup failure in SOCKS 4a" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:76 +msgid "" +"Fix setting JAVA_HOME on Mac OS X (new installs only, see ticket #1783 " +"for manual fix)" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:77 +msgid "Fix UTF-8 console passwords, and partial fix for usernames" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:78 +msgid "Fix router family configuration form" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:79 +msgid "Fix NTP sending random data in some fields that should be zero" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:85 +msgid "More verification of received NTP packets" +msgstr "" + +#: i2p2www/blog/2016/06/07/0.9.26-Release.rst:86 +msgid "" +"Rework resource bundle generation for 20x speedup in build time (requires" +" gettext version 0.19)" +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:1 +msgid "" +"====================\n" +"I2P on Maven Central\n" +"====================" +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:10 +msgid "The I2P client libraries are now available on Maven Central!" +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:12 +msgid "" +"We're nearly half-way into the APIs month of Summer Dev, and making great" +"\n" +"progress on a number of fronts. I'm happy to announce that the first of " +"these is\n" +"complete: the I2P client libraries are now available on Maven Central!" +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:18 +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:47 +msgid "" +"This should make it much simpler for Java developers to use I2P in their\n" +"applications. Instead of needing to obtain the libraries from a current " +"install,\n" +"they can simply add I2P to their dependencies. Upgrading to new versions " +"will\n" +"similarly be much easier." +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:26 +msgid "" +"How to use them\n" +"===============" +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:31 +msgid "There are two libraries that you need to know about:" +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:35 +msgid "The core I2P APIs; you can use these to send individual datagrams." +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:36 +msgid "A TCP-like set of sockets for communicating over I2P." +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:38 +msgid "" +"Add one or both of these to your project's dependencies, and you're good " +"to go!" +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:66 +msgid "" +"For other build systems, see the Maven Central pages for the `core`_ and\n" +"`streaming`_ libraries." +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:71 +msgid "" +"Android developers should use the `I2P Android client library`_, which " +"contains\n" +"the same libraries along with Android-specific helpers. I'll be updating " +"it soon\n" +"to depend on the new I2P libraries, so that cross-platform applications " +"can work\n" +"natively with either I2P Android or desktop I2P." +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:80 +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:62 +msgid "`I2P Android client library`" +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:83 +msgid "" +"Get hacking!\n" +"============" +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:88 +msgid "" +"See our `application development`_ guide for help getting started with " +"these\n" +"libraries. You can also chat with us about them in #i2p-dev on IRC. And " +"if you\n" +"do start using them, let us know what you're working on with the hashtag\n" +"`#I2PSummer`_ on Twitter!" +msgstr "" + +#: i2p2www/blog/2016/06/13/I2P-on-Maven-Central.rst:95 +msgid "application development" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:1 +msgid "" +"========================\n" +"Summer Dev roundup: APIs\n" +"========================" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:12 +msgid "" +"Summer Dev is in full swing: we've been busy greasing wheels, sanding " +"edges, and\n" +"tidying the place up. Now it's time for our first roundup, where we bring" +" you up\n" +"to speed on the progress we are making!" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:18 +msgid "" +"\n" +"But first, a big thank you to `Elio Qoshi`_ and `ura`_ for designing us " +"the\n" +"fantastic logo you see above. It adds a cheerful personality to our " +"development\n" +"program (and is going to look great on t-shirts)." +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:27 +msgid "" +"APIs month\n" +"==========" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:32 +msgid "" +"Our goal for this month was to \"blend in\" - to make our APIs and " +"libraries work\n" +"within the existing infrastructure of various communities, so that " +"application\n" +"developers can work with I2P more efficiently, and users don't need to " +"worry\n" +"about the details." +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:42 +msgid "" +"The I2P client libraries are now available on `Maven Central`_! See our\n" +"`previous blog post`_ for full details.\n" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:54 +msgid "" +"The `I2P Android client library`_ has also been updated to use the new " +"I2P\n" +"libraries. This means that cross-platform applications can work natively " +"with\n" +"either I2P Android or desktop I2P." +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:61 +msgid "`previous blog post`" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:69 +msgid "" +"The `Twisted`_ plugin ``txi2p`` now supports in-I2P ports, and will work\n" +"seamlessly over local, remote, and port-forwarded `SAM APIs`_. See its\n" +"`documentation`_ for usage instructions, and report any issues on " +"`GitHub`_." +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:77 +msgid "" +"The first (beta) version of ``i2psocket`` has been released! This is a " +"direct\n" +"replacement for the standard Python ``socket`` library that extends it " +"with I2P\n" +"support over the `SAM API`_. See its `GitHub page`_ for usage " +"instructions, and\n" +"to report any issues." +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:87 +msgid "`documentation`" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:89 +msgid "`GitHub page`" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:91 +msgid "" +"Other progress\n" +"--------------" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:96 +msgid "" +"zzz has been hard at work on Syndie, getting a headstart on Plugins " +"month. You can follow his progress on `the development forum thread`_." +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:98 +msgid "" +"psi has been creating an I2P test network using i2pd, and in the process " +"has found and fixed several i2pd bugs that will improve its compatibility" +" with Java I2P." +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:100 +msgid "`the development forum thread`" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:102 +msgid "" +"Coming up: Apps month!\n" +"======================" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:107 +msgid "" +"We are excited to be working with `Tahoe-LAFS`_ in July! I2P has for a " +"long time\n" +"been home to one of the `largest public grids`_, using a patched version " +"of\n" +"Tahoe-LAFS. During Apps month we will be helping them with their ongoing " +"work to\n" +"add native support for I2P and Tor, so that I2P users can benefit from " +"all of\n" +"the improvements upstream." +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:115 +msgid "" +"There are several other projects that we will be talking with about their" +" plans\n" +"for I2P integration, and helping with design. Stay tuned!" +msgstr "" + +#: i2p2www/blog/2016/07/02/Summer-Dev-roundup-APIs.draft.rst:121 +msgid "`largest public grids`" +msgstr "" +