Updated translation strings

This commit is contained in:
str4d
2013-06-06 01:56:08 +00:00
parent 06f028663b
commit dd5ca25696
4 changed files with 4 additions and 1781 deletions

View File

@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
"POT-Creation-Date: 2013-06-06 01:26+0000\n"
"POT-Creation-Date: 2013-06-06 01:53+0000\n"
"PO-Revision-Date: 2013-05-24 22:08+0000\n"
"Last-Translator: SteinQuadrat <iaa_1@web.de>\n"
"Language-Team: German "
@ -27880,451 +27880,3 @@ msgstr ""
msgid "Papers and Research"
msgstr ""
#~ msgid "Blog Index"
#~ msgstr ""
#~ msgid "<a href=\"#ubuntu\">Ubuntu</a> (Hardy <em>8.04</em> and newer)"
#~ msgstr ""
#~ msgid ""
#~ "<a href=\"#debian\">Debian Linux</a> (Lenny "
#~ "and newer) &amp; <a "
#~ "href=\"#nonlinux\">kFreeBSD</a> (Wheezy)"
#~ msgstr ""
#~ msgid ""
#~ "Option 2: <a href=\"#debian\">Debian</a> "
#~ "(including systems based on Debian and"
#~ " older versions of Ubuntu)"
#~ msgstr ""
#~ msgid ""
#~ "Instructions for Ubuntu Lucid Lynx (and"
#~ " newer) and derivatives like Linux "
#~ "Mint &amp; Trisquel"
#~ msgstr ""
#~ msgid ""
#~ "For Debian Oldstable (Lenny) and Stable"
#~ " (Squeeze): Add the following entries "
#~ "to <code>/etc/apt/sources.list.d/i2p.list</code>"
#~ msgstr ""
#~ msgid "For Debian Testing (Wheezy) or Unstable (Sid), use the following:"
#~ msgstr ""
#~ msgid ""
#~ "Download the <a href=\"http://ppa.launchpad.net"
#~ "/i2p-maintainers/i2p/ubuntu/pool/main/i/i2p/\">i2p-router</a>"
#~ " package from the <a "
#~ "href=\"http://ppa.launchpad.net/i2p-"
#~ "maintainers/i2p/ubuntu/pool/main/i/i2p/\">PPA</a>."
#~ msgstr ""
#~ msgid ""
#~ "Download that file and double-click it (if that works) or\n"
#~ " type <code>java -jar "
#~ "i2pinstall_0.9.4-1_osx.jar</code> in a terminal "
#~ "to run the\n"
#~ " installer.\n"
#~ " You may be able to right-click and select\n"
#~ " &quot;Open with Java&quot;."
#~ msgstr ""
#~ msgid ""
#~ "Due to <a href=\"%(buglink)s\">a wrapper bug</a>, the 0.9.4 installer\n"
#~ " will <b>NOT</b> work on OS "
#~ "X. Use the fixed 0.9.4-1 OSX "
#~ "installer above."
#~ msgstr ""
#~ msgid ""
#~ "Download the 0.9.4-1 OSX graphical installer file above and\n"
#~ " run <code>java -jar "
#~ "i2pinstall_0.9.4-1_osx.jar -console</code> from the"
#~ " command line."
#~ msgstr ""
#~ msgid "May 2012"
#~ msgstr ""
#~ msgid ""
#~ "The application designer should carefully "
#~ "consider the tradeoff of repliable vs."
#~ " non-repliable\n"
#~ "datagrams. Also, the datagram size will"
#~ " affect reliability, due to tunnel "
#~ "fragmentation into 1KB\n"
#~ "tunnel messages. The more message "
#~ "fragments, the more likely that one "
#~ "of them will be dropped\n"
#~ "by an intermediate hop. Messages larger"
#~ " than a few KB are not "
#~ "recommended."
#~ msgstr ""
#~ msgid ""
#~ "The standard I2CP protocol number for"
#~ " datagrams is 17. Applications may or"
#~ " may not choose to set the\n"
#~ "protocol in the I2CP header. It is not set by default.\n"
#~ "It must be set to demultiplex "
#~ "datagram and streaming traffic received "
#~ "on the same Destination."
#~ msgstr ""
#~ msgid ""
#~ "There is no method within the "
#~ "datagram API to specify whether it "
#~ "is non-repliable (raw)\n"
#~ "or repliable. The application should be"
#~ " designed to expect the appropriate "
#~ "type.\n"
#~ "The I2CP protocol number or port "
#~ "could also be used by the "
#~ "application to\n"
#~ "indicate datagram type."
#~ msgstr ""
#~ msgid ""
#~ "Lookups are not encrypted and thus "
#~ "are vulnerable to snooping by the "
#~ "outbound endpoint\n"
#~ "(OBEP) of the client tunnel."
#~ msgstr ""
#~ msgid ""
#~ "As the requesting router does not "
#~ "reveal itself, there is no recipient "
#~ "public key for the floodfill router "
#~ "to\n"
#~ "encrypt the reply with. Therefore, the"
#~ " reply is exposed to the inbound "
#~ "gateway (IBGW)\n"
#~ "of the inbound exploratory tunnel.\n"
#~ "An appropriate method of encrypting the"
#~ " reply is a topic for future "
#~ "work."
#~ msgstr ""
#~ msgid ""
#~ "As for regular lookups, the reply is unencrypted,\n"
#~ "thus exposing the reply to the "
#~ "inbound gateway (IBGW) of the reply "
#~ "tunnel, and\n"
#~ "an appropriate method of encrypting the"
#~ " reply is a topic for future "
#~ "work.\n"
#~ "As the IBGW for the reply is "
#~ "one of the gateways published in "
#~ "the LeaseSet,\n"
#~ "the exposure is minimal."
#~ msgstr ""
#~ msgid "Expiration is currently unused, always null (all zeroes))"
#~ msgstr ""
#~ msgid "November 2011"
#~ msgstr ""
#~ msgid ""
#~ "When a new update file specification "
#~ "is defined, it should use a larger"
#~ "\n"
#~ "DSA signature, and the signature should cover the version.\n"
#~ "A file format version number might be a good idea too."
#~ msgstr ""
#~ msgid ""
#~ "The network will eventually grow too large for update over HTTP.\n"
#~ "The built-in BitTorrent client, "
#~ "i2psnark, may be used as a "
#~ "distributed update method.\n"
#~ "This development effort was started in"
#~ " 2009 but is on hold until it"
#~ " is required."
#~ msgstr ""
#~ msgid ""
#~ "The transport system delivers <a "
#~ "href=\"%(i2np)s\">I2NP messages</a>. The transport"
#~ " selected for any message is\n"
#~ "independent of the application-layer protocol (TCP or UDP)."
#~ msgstr ""
#~ msgid ""
#~ "Also, the existing transports will be"
#~ " enhanced to support multiple addresses "
#~ "within a single transport,\n"
#~ "including IPV6 addresses. Currently, a "
#~ "transport may only advertise a single"
#~ " IPV4 address."
#~ msgstr ""
#~ msgid "October 2012"
#~ msgstr ""
#~ msgid ""
#~ "As of router version 0.8.12,\n"
#~ "two MTU values are used: 620 and 1484.\n"
#~ "The MTU value is adjusted based on"
#~ " the percentage of packets that are"
#~ " retransmitted."
#~ msgstr ""
#~ msgid ""
#~ "For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
#~ "the payload portion after the 28-byte IP/UDP header is a multiple of\n"
#~ "16 bytes, for encryption purposes.\n"
#~ "This calculation is for IPv4 only. "
#~ "While the protocol as specified supports"
#~ " IPv6\n"
#~ "addresses, IPv6 is not yet implemented."
#~ msgstr ""
#~ msgid ""
#~ "For our bad sake the syndie project is 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 100 Bitcoin."
#~ msgstr ""
#~ 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 32KB. 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 under 32KB."
#~ msgstr ""
#~ msgid ""
#~ "I2P destinations are mobile identifiers "
#~ "- they can be moved from one "
#~ "I2P router\n"
#~ "to another (or with some special "
#~ "software, it can even 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 ""
#~ msgid ""
#~ "I2P destinations are ugly and large "
#~ "- behind the scenes, they contain "
#~ "a 2048bit ElGamal\n"
#~ "public key for encryption, a 1024bit "
#~ "DSA public key for signing, and a"
#~ " variable size \n"
#~ "certificate, which may contain proof of work or blinded data."
#~ msgstr ""
#~ 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 at the moment those techniques "
#~ "do not guarantee\n"
#~ "globally uniqueness (since they're stored "
#~ "locally at each person's machine as "
#~ "\"hosts.txt\")\n"
#~ "and the current mechanism is not "
#~ "especially scalable nor secure (updates "
#~ "to one host file are\n"
#~ "manually managed within Monotone, and as"
#~ " such, anyone with commit rights on"
#~ " the repository can\n"
#~ "change the destinations). 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"
#~ "<a href=\"%(naming)s\">Further information on "
#~ "the naming system</a> is available."
#~ msgstr ""
#~ msgid ""
#~ "A useful thing to remember is that"
#~ " 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 ""
#~ msgid ""
#~ "Of course, another useful thing to "
#~ "remember is that 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 ""
#~ msgid "I2P datagrams can be up to 32KB"
#~ msgstr ""
#~ 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 32KB datagrams\n"
#~ "(31KB when using the repliable kind)."
#~ " For many applications, 32KB 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 ""
#~ msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is beta."
#~ msgstr ""
#~ 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 "
#~ "8bit 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 ""
#~ msgid ""
#~ "It was possible to write I2P "
#~ "applications in Java using the "
#~ "ministreaming library.\n"
#~ "However, the Streaming library has "
#~ "superceded this, and provides better "
#~ "functionality."
#~ msgstr ""
#~ msgid ""
#~ "Development using the streaming library "
#~ "requires the following libraries in your"
#~ " classpath:"
#~ msgstr ""
#~ msgid "the streaming library itself."
#~ msgstr ""
#~ msgid ""
#~ "the ministreaming library is used as "
#~ "the base for the streaming library."
#~ msgstr ""
#~ msgid ""
#~ "some standard I2P classes (like the "
#~ "Destination class) are very convenient "
#~ "when developing."
#~ msgstr ""
#~ msgid ""
#~ "We will start by initializing the "
#~ "server application. This requires getting "
#~ "an I2PSocketManager\n"
#~ "and creating an I2PServerSocket.\n"
#~ "In addition, we will ask the "
#~ "I2PSocketManager for an I2PSession, so "
#~ "we can find out the Destination we"
#~ " use."
#~ msgstr ""
#~ msgid "Existing Applications in Development"
#~ msgstr ""
#~ msgid "Contact us if you would like to help."
#~ msgstr ""
#~ msgid ""
#~ "Download manager / eepget scheduler -\n"
#~ "We use eepget to fetch lots of "
#~ "things reliably over i2p, and there's"
#~ " already an\n"
#~ "implementation of a sequential download "
#~ "manager (net.i2p.util.EepGetScheduler),\n"
#~ "but there isn't any sort of user"
#~ " interface to it. A web based "
#~ "UI would be\n"
#~ "great."
#~ msgstr ""
#~ msgid ""
#~ "Content Distribution / DHT applications "
#~ "- help out with <a "
#~ "href=\"http://%(feedspace)s\">feedspace</a>,\n"
#~ "port dijjer, look for alternatives"
#~ msgstr ""
#~ msgid ""
#~ "Resurrect some old apps - in the i2p source package -\n"
#~ "bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping"
#~ msgstr ""

View File

@ -12,7 +12,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
"POT-Creation-Date: 2013-06-06 01:26+0000\n"
"POT-Creation-Date: 2013-06-06 01:53+0000\n"
"PO-Revision-Date: 2013-06-03 10:50+0000\n"
"Last-Translator: trolly <trolly@fastmail.fm>\n"
"Language-Team: Spanish "
@ -30744,468 +30744,3 @@ msgstr "Los enlaces mas nuevos se encuentran en el encabezado de la página."
msgid "Papers and Research"
msgstr "Documentos e investigación"
#~ msgid "Blog Index"
#~ msgstr ""
#~ msgid "<a href=\"#ubuntu\">Ubuntu</a> (Hardy <em>8.04</em> and newer)"
#~ msgstr ""
#~ msgid ""
#~ "<a href=\"#debian\">Debian Linux</a> (Lenny "
#~ "and newer) &amp; <a "
#~ "href=\"#nonlinux\">kFreeBSD</a> (Wheezy)"
#~ msgstr ""
#~ msgid ""
#~ "Option 2: <a href=\"#debian\">Debian</a> "
#~ "(including systems based on Debian and"
#~ " older versions of Ubuntu)"
#~ msgstr ""
#~ msgid ""
#~ "Instructions for Ubuntu Lucid Lynx (and"
#~ " newer) and derivatives like Linux "
#~ "Mint &amp; Trisquel"
#~ msgstr ""
#~ msgid ""
#~ "For Debian Oldstable (Lenny) and Stable"
#~ " (Squeeze): Add the following entries "
#~ "to <code>/etc/apt/sources.list.d/i2p.list</code>"
#~ msgstr ""
#~ msgid "For Debian Testing (Wheezy) or Unstable (Sid), use the following:"
#~ msgstr ""
#~ msgid ""
#~ "Download the <a href=\"http://ppa.launchpad.net"
#~ "/i2p-maintainers/i2p/ubuntu/pool/main/i/i2p/\">i2p-router</a>"
#~ " package from the <a "
#~ "href=\"http://ppa.launchpad.net/i2p-"
#~ "maintainers/i2p/ubuntu/pool/main/i/i2p/\">PPA</a>."
#~ msgstr ""
#~ msgid ""
#~ "Download that file and double-click it (if that works) or\n"
#~ " type <code>java -jar "
#~ "i2pinstall_0.9.4-1_osx.jar</code> in a terminal "
#~ "to run the\n"
#~ " installer.\n"
#~ " You may be able to right-click and select\n"
#~ " &quot;Open with Java&quot;."
#~ msgstr ""
#~ "Descargue el archivo y pulse dos veces sobre él (si funciona) o\n"
#~ " escriba <code>java -jar "
#~ "i2pinstall_0.9.4-1_osx.jar</code> en una terminal"
#~ " para ejecutar \n"
#~ " el instalador.\n"
#~ " Debería poder pulsar botón derecho sobre el archivo y seleccionar\n"
#~ " &quot;Abrir con Java&quot;."
#~ msgid ""
#~ "Due to <a href=\"%(buglink)s\">a wrapper bug</a>, the 0.9.4 installer\n"
#~ " will <b>NOT</b> work on OS "
#~ "X. Use the fixed 0.9.4-1 OSX "
#~ "installer above."
#~ msgstr ""
#~ "Debido a un <a href=\"%(buglink)s\">error "
#~ "en el wrapper</a>, el instalador de "
#~ "0.9.4 \n"
#~ " <b>NO<b> funcionará en OS X. "
#~ "Use el instalador 0.9.4-1OSX ya "
#~ "arreglado."
#~ msgid ""
#~ "Download the 0.9.4-1 OSX graphical installer file above and\n"
#~ " run <code>java -jar "
#~ "i2pinstall_0.9.4-1_osx.jar -console</code> from the"
#~ " command line."
#~ msgstr ""
#~ "Descargue el instalador gráfico 0.9.4-1 "
#~ "OSX y ejecute <code>java -jar "
#~ "i2pinstall_0.9.4-1_osx.jar -console</code> en la "
#~ "terminal."
#~ msgid "May 2012"
#~ msgstr ""
#~ msgid ""
#~ "The application designer should carefully "
#~ "consider the tradeoff of repliable vs."
#~ " non-repliable\n"
#~ "datagrams. Also, the datagram size will"
#~ " affect reliability, due to tunnel "
#~ "fragmentation into 1KB\n"
#~ "tunnel messages. The more message "
#~ "fragments, the more likely that one "
#~ "of them will be dropped\n"
#~ "by an intermediate hop. Messages larger"
#~ " than a few KB are not "
#~ "recommended."
#~ msgstr ""
#~ msgid ""
#~ "The standard I2CP protocol number for"
#~ " datagrams is 17. Applications may or"
#~ " may not choose to set the\n"
#~ "protocol in the I2CP header. It is not set by default.\n"
#~ "It must be set to demultiplex "
#~ "datagram and streaming traffic received "
#~ "on the same Destination."
#~ msgstr ""
#~ msgid ""
#~ "There is no method within the "
#~ "datagram API to specify whether it "
#~ "is non-repliable (raw)\n"
#~ "or repliable. The application should be"
#~ " designed to expect the appropriate "
#~ "type.\n"
#~ "The I2CP protocol number or port "
#~ "could also be used by the "
#~ "application to\n"
#~ "indicate datagram type."
#~ msgstr ""
#~ msgid ""
#~ "Lookups are not encrypted and thus "
#~ "are vulnerable to snooping by the "
#~ "outbound endpoint\n"
#~ "(OBEP) of the client tunnel."
#~ msgstr ""
#~ msgid ""
#~ "As the requesting router does not "
#~ "reveal itself, there is no recipient "
#~ "public key for the floodfill router "
#~ "to\n"
#~ "encrypt the reply with. Therefore, the"
#~ " reply is exposed to the inbound "
#~ "gateway (IBGW)\n"
#~ "of the inbound exploratory tunnel.\n"
#~ "An appropriate method of encrypting the"
#~ " reply is a topic for future "
#~ "work."
#~ msgstr ""
#~ msgid ""
#~ "As for regular lookups, the reply is unencrypted,\n"
#~ "thus exposing the reply to the "
#~ "inbound gateway (IBGW) of the reply "
#~ "tunnel, and\n"
#~ "an appropriate method of encrypting the"
#~ " reply is a topic for future "
#~ "work.\n"
#~ "As the IBGW for the reply is "
#~ "one of the gateways published in "
#~ "the LeaseSet,\n"
#~ "the exposure is minimal."
#~ msgstr ""
#~ msgid "Expiration is currently unused, always null (all zeroes))"
#~ msgstr ""
#~ msgid "November 2011"
#~ msgstr ""
#~ msgid ""
#~ "When a new update file specification "
#~ "is defined, it should use a larger"
#~ "\n"
#~ "DSA signature, and the signature should cover the version.\n"
#~ "A file format version number might be a good idea too."
#~ msgstr ""
#~ msgid ""
#~ "The network will eventually grow too large for update over HTTP.\n"
#~ "The built-in BitTorrent client, "
#~ "i2psnark, may be used as a "
#~ "distributed update method.\n"
#~ "This development effort was started in"
#~ " 2009 but is on hold until it"
#~ " is required."
#~ msgstr ""
#~ msgid ""
#~ "The transport system delivers <a "
#~ "href=\"%(i2np)s\">I2NP messages</a>. The transport"
#~ " selected for any message is\n"
#~ "independent of the application-layer protocol (TCP or UDP)."
#~ msgstr ""
#~ msgid ""
#~ "Also, the existing transports will be"
#~ " enhanced to support multiple addresses "
#~ "within a single transport,\n"
#~ "including IPV6 addresses. Currently, a "
#~ "transport may only advertise a single"
#~ " IPV4 address."
#~ msgstr ""
#~ msgid "October 2012"
#~ msgstr ""
#~ msgid ""
#~ "As of router version 0.8.12,\n"
#~ "two MTU values are used: 620 and 1484.\n"
#~ "The MTU value is adjusted based on"
#~ " the percentage of packets that are"
#~ " retransmitted."
#~ msgstr ""
#~ msgid ""
#~ "For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
#~ "the payload portion after the 28-byte IP/UDP header is a multiple of\n"
#~ "16 bytes, for encryption purposes.\n"
#~ "This calculation is for IPv4 only. "
#~ "While the protocol as specified supports"
#~ " IPv6\n"
#~ "addresses, IPv6 is not yet implemented."
#~ msgstr ""
#~ msgid ""
#~ "For our bad sake the syndie project is 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 100 Bitcoin."
#~ msgstr ""
#~ 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 32KB. 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 under 32KB."
#~ msgstr ""
#~ msgid ""
#~ "I2P destinations are mobile identifiers "
#~ "- they can be moved from one "
#~ "I2P router\n"
#~ "to another (or with some special "
#~ "software, it can even 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 ""
#~ msgid ""
#~ "I2P destinations are ugly and large "
#~ "- behind the scenes, they contain "
#~ "a 2048bit ElGamal\n"
#~ "public key for encryption, a 1024bit "
#~ "DSA public key for signing, and a"
#~ " variable size \n"
#~ "certificate, which may contain proof of work or blinded data."
#~ msgstr ""
#~ 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 at the moment those techniques "
#~ "do not guarantee\n"
#~ "globally uniqueness (since they're stored "
#~ "locally at each person's machine as "
#~ "\"hosts.txt\")\n"
#~ "and the current mechanism is not "
#~ "especially scalable nor secure (updates "
#~ "to one host file are\n"
#~ "manually managed within Monotone, and as"
#~ " such, anyone with commit rights on"
#~ " the repository can\n"
#~ "change the destinations). 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"
#~ "<a href=\"%(naming)s\">Further information on "
#~ "the naming system</a> is available."
#~ msgstr ""
#~ msgid ""
#~ "A useful thing to remember is that"
#~ " 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 ""
#~ msgid ""
#~ "Of course, another useful thing to "
#~ "remember is that 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 ""
#~ msgid "I2P datagrams can be up to 32KB"
#~ msgstr ""
#~ 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 32KB datagrams\n"
#~ "(31KB when using the repliable kind)."
#~ " For many applications, 32KB 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 ""
#~ msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is beta."
#~ msgstr ""
#~ 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 "
#~ "8bit 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 ""
#~ msgid ""
#~ "It was possible to write I2P "
#~ "applications in Java using the "
#~ "ministreaming library.\n"
#~ "However, the Streaming library has "
#~ "superceded this, and provides better "
#~ "functionality."
#~ msgstr ""
#~ msgid ""
#~ "Development using the streaming library "
#~ "requires the following libraries in your"
#~ " classpath:"
#~ msgstr ""
#~ msgid "the streaming library itself."
#~ msgstr ""
#~ msgid ""
#~ "the ministreaming library is used as "
#~ "the base for the streaming library."
#~ msgstr ""
#~ msgid ""
#~ "some standard I2P classes (like the "
#~ "Destination class) are very convenient "
#~ "when developing."
#~ msgstr ""
#~ msgid ""
#~ "We will start by initializing the "
#~ "server application. This requires getting "
#~ "an I2PSocketManager\n"
#~ "and creating an I2PServerSocket.\n"
#~ "In addition, we will ask the "
#~ "I2PSocketManager for an I2PSession, so "
#~ "we can find out the Destination we"
#~ " use."
#~ msgstr ""
#~ msgid "Existing Applications in Development"
#~ msgstr ""
#~ msgid "Contact us if you would like to help."
#~ msgstr ""
#~ msgid ""
#~ "Download manager / eepget scheduler -\n"
#~ "We use eepget to fetch lots of "
#~ "things reliably over i2p, and there's"
#~ " already an\n"
#~ "implementation of a sequential download "
#~ "manager (net.i2p.util.EepGetScheduler),\n"
#~ "but there isn't any sort of user"
#~ " interface to it. A web based "
#~ "UI would be\n"
#~ "great."
#~ msgstr ""
#~ msgid ""
#~ "Content Distribution / DHT applications "
#~ "- help out with <a "
#~ "href=\"http://%(feedspace)s\">feedspace</a>,\n"
#~ "port dijjer, look for alternatives"
#~ msgstr ""
#~ msgid ""
#~ "Resurrect some old apps - in the i2p source package -\n"
#~ "bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping"
#~ msgstr ""

View File

@ -9,7 +9,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
"POT-Creation-Date: 2013-06-06 01:26+0000\n"
"POT-Creation-Date: 2013-06-06 01:53+0000\n"
"PO-Revision-Date: 2013-06-05 09:51+0000\n"
"Last-Translator: Boxoa590\n"
"Language-Team: French "
@ -28229,419 +28229,3 @@ msgstr ""
msgid "Papers and Research"
msgstr ""
#~ msgid "Blog Index"
#~ msgstr "Index du blog"
#~ msgid "For Debian Testing (Wheezy) or Unstable (Sid), use the following:"
#~ msgstr "Pour Debian Testing (Wheezy) ou instable (Sid), utilisez ce qui suit :"
#~ msgid ""
#~ "Download the <a href=\"http://ppa.launchpad.net"
#~ "/i2p-maintainers/i2p/ubuntu/pool/main/i/i2p/\">i2p-router</a>"
#~ " package from the <a "
#~ "href=\"http://ppa.launchpad.net/i2p-"
#~ "maintainers/i2p/ubuntu/pool/main/i/i2p/\">PPA</a>."
#~ msgstr ""
#~ "Téléchargez le paquetage <a "
#~ "href=\"http://ppa.launchpad.net/i2p-"
#~ "maintainers/i2p/ubuntu/pool/main/i/i2p/\">i2p-router</a> "
#~ "depuis le <a href=\"http://ppa.launchpad.net/i2p-"
#~ "maintainers/i2p/ubuntu/pool/main/i/i2p/\">PPA</a>."
#~ msgid ""
#~ "Due to <a href=\"%(buglink)s\">a wrapper bug</a>, the 0.9.4 installer\n"
#~ " will <b>NOT</b> work on OS "
#~ "X. Use the fixed 0.9.4-1 OSX "
#~ "installer above."
#~ msgstr ""
#~ msgid ""
#~ "Download the 0.9.4-1 OSX graphical installer file above and\n"
#~ " run <code>java -jar "
#~ "i2pinstall_0.9.4-1_osx.jar -console</code> from the"
#~ " command line."
#~ msgstr ""
#~ msgid "May 2012"
#~ msgstr ""
#~ msgid ""
#~ "The application designer should carefully "
#~ "consider the tradeoff of repliable vs."
#~ " non-repliable\n"
#~ "datagrams. Also, the datagram size will"
#~ " affect reliability, due to tunnel "
#~ "fragmentation into 1KB\n"
#~ "tunnel messages. The more message "
#~ "fragments, the more likely that one "
#~ "of them will be dropped\n"
#~ "by an intermediate hop. Messages larger"
#~ " than a few KB are not "
#~ "recommended."
#~ msgstr ""
#~ msgid ""
#~ "The standard I2CP protocol number for"
#~ " datagrams is 17. Applications may or"
#~ " may not choose to set the\n"
#~ "protocol in the I2CP header. It is not set by default.\n"
#~ "It must be set to demultiplex "
#~ "datagram and streaming traffic received "
#~ "on the same Destination."
#~ msgstr ""
#~ msgid ""
#~ "There is no method within the "
#~ "datagram API to specify whether it "
#~ "is non-repliable (raw)\n"
#~ "or repliable. The application should be"
#~ " designed to expect the appropriate "
#~ "type.\n"
#~ "The I2CP protocol number or port "
#~ "could also be used by the "
#~ "application to\n"
#~ "indicate datagram type."
#~ msgstr ""
#~ msgid ""
#~ "Lookups are not encrypted and thus "
#~ "are vulnerable to snooping by the "
#~ "outbound endpoint\n"
#~ "(OBEP) of the client tunnel."
#~ msgstr ""
#~ msgid ""
#~ "As the requesting router does not "
#~ "reveal itself, there is no recipient "
#~ "public key for the floodfill router "
#~ "to\n"
#~ "encrypt the reply with. Therefore, the"
#~ " reply is exposed to the inbound "
#~ "gateway (IBGW)\n"
#~ "of the inbound exploratory tunnel.\n"
#~ "An appropriate method of encrypting the"
#~ " reply is a topic for future "
#~ "work."
#~ msgstr ""
#~ msgid ""
#~ "As for regular lookups, the reply is unencrypted,\n"
#~ "thus exposing the reply to the "
#~ "inbound gateway (IBGW) of the reply "
#~ "tunnel, and\n"
#~ "an appropriate method of encrypting the"
#~ " reply is a topic for future "
#~ "work.\n"
#~ "As the IBGW for the reply is "
#~ "one of the gateways published in "
#~ "the LeaseSet,\n"
#~ "the exposure is minimal."
#~ msgstr ""
#~ msgid "Expiration is currently unused, always null (all zeroes))"
#~ msgstr ""
#~ msgid "November 2011"
#~ msgstr ""
#~ msgid ""
#~ "When a new update file specification "
#~ "is defined, it should use a larger"
#~ "\n"
#~ "DSA signature, and the signature should cover the version.\n"
#~ "A file format version number might be a good idea too."
#~ msgstr ""
#~ msgid ""
#~ "The network will eventually grow too large for update over HTTP.\n"
#~ "The built-in BitTorrent client, "
#~ "i2psnark, may be used as a "
#~ "distributed update method.\n"
#~ "This development effort was started in"
#~ " 2009 but is on hold until it"
#~ " is required."
#~ msgstr ""
#~ msgid ""
#~ "The transport system delivers <a "
#~ "href=\"%(i2np)s\">I2NP messages</a>. The transport"
#~ " selected for any message is\n"
#~ "independent of the application-layer protocol (TCP or UDP)."
#~ msgstr ""
#~ msgid ""
#~ "Also, the existing transports will be"
#~ " enhanced to support multiple addresses "
#~ "within a single transport,\n"
#~ "including IPV6 addresses. Currently, a "
#~ "transport may only advertise a single"
#~ " IPV4 address."
#~ msgstr ""
#~ msgid "October 2012"
#~ msgstr ""
#~ msgid ""
#~ "As of router version 0.8.12,\n"
#~ "two MTU values are used: 620 and 1484.\n"
#~ "The MTU value is adjusted based on"
#~ " the percentage of packets that are"
#~ " retransmitted."
#~ msgstr ""
#~ msgid ""
#~ "For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
#~ "the payload portion after the 28-byte IP/UDP header is a multiple of\n"
#~ "16 bytes, for encryption purposes.\n"
#~ "This calculation is for IPv4 only. "
#~ "While the protocol as specified supports"
#~ " IPv6\n"
#~ "addresses, IPv6 is not yet implemented."
#~ msgstr ""
#~ msgid ""
#~ "For our bad sake the syndie project is 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 100 Bitcoin."
#~ msgstr ""
#~ 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 32KB. 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 under 32KB."
#~ msgstr ""
#~ msgid ""
#~ "I2P destinations are mobile identifiers "
#~ "- they can be moved from one "
#~ "I2P router\n"
#~ "to another (or with some special "
#~ "software, it can even 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 ""
#~ msgid ""
#~ "I2P destinations are ugly and large "
#~ "- behind the scenes, they contain "
#~ "a 2048bit ElGamal\n"
#~ "public key for encryption, a 1024bit "
#~ "DSA public key for signing, and a"
#~ " variable size \n"
#~ "certificate, which may contain proof of work or blinded data."
#~ msgstr ""
#~ 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 at the moment those techniques "
#~ "do not guarantee\n"
#~ "globally uniqueness (since they're stored "
#~ "locally at each person's machine as "
#~ "\"hosts.txt\")\n"
#~ "and the current mechanism is not "
#~ "especially scalable nor secure (updates "
#~ "to one host file are\n"
#~ "manually managed within Monotone, and as"
#~ " such, anyone with commit rights on"
#~ " the repository can\n"
#~ "change the destinations). 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"
#~ "<a href=\"%(naming)s\">Further information on "
#~ "the naming system</a> is available."
#~ msgstr ""
#~ msgid ""
#~ "A useful thing to remember is that"
#~ " 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 ""
#~ msgid ""
#~ "Of course, another useful thing to "
#~ "remember is that 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 ""
#~ msgid "I2P datagrams can be up to 32KB"
#~ msgstr ""
#~ 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 32KB datagrams\n"
#~ "(31KB when using the repliable kind)."
#~ " For many applications, 32KB 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 ""
#~ msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is beta."
#~ msgstr ""
#~ 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 "
#~ "8bit 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 ""
#~ msgid ""
#~ "It was possible to write I2P "
#~ "applications in Java using the "
#~ "ministreaming library.\n"
#~ "However, the Streaming library has "
#~ "superceded this, and provides better "
#~ "functionality."
#~ msgstr ""
#~ msgid ""
#~ "Development using the streaming library "
#~ "requires the following libraries in your"
#~ " classpath:"
#~ msgstr ""
#~ msgid "the streaming library itself."
#~ msgstr ""
#~ msgid ""
#~ "the ministreaming library is used as "
#~ "the base for the streaming library."
#~ msgstr ""
#~ msgid ""
#~ "some standard I2P classes (like the "
#~ "Destination class) are very convenient "
#~ "when developing."
#~ msgstr ""
#~ msgid ""
#~ "We will start by initializing the "
#~ "server application. This requires getting "
#~ "an I2PSocketManager\n"
#~ "and creating an I2PServerSocket.\n"
#~ "In addition, we will ask the "
#~ "I2PSocketManager for an I2PSession, so "
#~ "we can find out the Destination we"
#~ " use."
#~ msgstr ""
#~ msgid "Existing Applications in Development"
#~ msgstr ""
#~ msgid "Contact us if you would like to help."
#~ msgstr ""
#~ msgid ""
#~ "Download manager / eepget scheduler -\n"
#~ "We use eepget to fetch lots of "
#~ "things reliably over i2p, and there's"
#~ " already an\n"
#~ "implementation of a sequential download "
#~ "manager (net.i2p.util.EepGetScheduler),\n"
#~ "but there isn't any sort of user"
#~ " interface to it. A web based "
#~ "UI would be\n"
#~ "great."
#~ msgstr ""
#~ msgid ""
#~ "Content Distribution / DHT applications "
#~ "- help out with <a "
#~ "href=\"http://%(feedspace)s\">feedspace</a>,\n"
#~ "port dijjer, look for alternatives"
#~ msgstr ""
#~ msgid ""
#~ "Resurrect some old apps - in the i2p source package -\n"
#~ "bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping"
#~ msgstr ""

View File

@ -9,7 +9,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: https://trac.i2p2.de/\n"
"POT-Creation-Date: 2013-06-06 01:26+0000\n"
"POT-Creation-Date: 2013-06-06 01:53+0000\n"
"PO-Revision-Date: 2013-04-27 23:10+0000\n"
"Last-Translator: Martin Svensson <digitalmannen@gmail.com>\n"
"Language-Team: Swedish (Sweden) "
@ -27684,451 +27684,3 @@ msgstr ""
msgid "Papers and Research"
msgstr ""
#~ msgid "Blog Index"
#~ msgstr ""
#~ msgid "<a href=\"#ubuntu\">Ubuntu</a> (Hardy <em>8.04</em> and newer)"
#~ msgstr ""
#~ msgid ""
#~ "<a href=\"#debian\">Debian Linux</a> (Lenny "
#~ "and newer) &amp; <a "
#~ "href=\"#nonlinux\">kFreeBSD</a> (Wheezy)"
#~ msgstr ""
#~ msgid ""
#~ "Option 2: <a href=\"#debian\">Debian</a> "
#~ "(including systems based on Debian and"
#~ " older versions of Ubuntu)"
#~ msgstr ""
#~ msgid ""
#~ "Instructions for Ubuntu Lucid Lynx (and"
#~ " newer) and derivatives like Linux "
#~ "Mint &amp; Trisquel"
#~ msgstr ""
#~ msgid ""
#~ "For Debian Oldstable (Lenny) and Stable"
#~ " (Squeeze): Add the following entries "
#~ "to <code>/etc/apt/sources.list.d/i2p.list</code>"
#~ msgstr ""
#~ msgid "For Debian Testing (Wheezy) or Unstable (Sid), use the following:"
#~ msgstr ""
#~ msgid ""
#~ "Download the <a href=\"http://ppa.launchpad.net"
#~ "/i2p-maintainers/i2p/ubuntu/pool/main/i/i2p/\">i2p-router</a>"
#~ " package from the <a "
#~ "href=\"http://ppa.launchpad.net/i2p-"
#~ "maintainers/i2p/ubuntu/pool/main/i/i2p/\">PPA</a>."
#~ msgstr ""
#~ msgid ""
#~ "Download that file and double-click it (if that works) or\n"
#~ " type <code>java -jar "
#~ "i2pinstall_0.9.4-1_osx.jar</code> in a terminal "
#~ "to run the\n"
#~ " installer.\n"
#~ " You may be able to right-click and select\n"
#~ " &quot;Open with Java&quot;."
#~ msgstr ""
#~ msgid ""
#~ "Due to <a href=\"%(buglink)s\">a wrapper bug</a>, the 0.9.4 installer\n"
#~ " will <b>NOT</b> work on OS "
#~ "X. Use the fixed 0.9.4-1 OSX "
#~ "installer above."
#~ msgstr ""
#~ msgid ""
#~ "Download the 0.9.4-1 OSX graphical installer file above and\n"
#~ " run <code>java -jar "
#~ "i2pinstall_0.9.4-1_osx.jar -console</code> from the"
#~ " command line."
#~ msgstr ""
#~ msgid "May 2012"
#~ msgstr ""
#~ msgid ""
#~ "The application designer should carefully "
#~ "consider the tradeoff of repliable vs."
#~ " non-repliable\n"
#~ "datagrams. Also, the datagram size will"
#~ " affect reliability, due to tunnel "
#~ "fragmentation into 1KB\n"
#~ "tunnel messages. The more message "
#~ "fragments, the more likely that one "
#~ "of them will be dropped\n"
#~ "by an intermediate hop. Messages larger"
#~ " than a few KB are not "
#~ "recommended."
#~ msgstr ""
#~ msgid ""
#~ "The standard I2CP protocol number for"
#~ " datagrams is 17. Applications may or"
#~ " may not choose to set the\n"
#~ "protocol in the I2CP header. It is not set by default.\n"
#~ "It must be set to demultiplex "
#~ "datagram and streaming traffic received "
#~ "on the same Destination."
#~ msgstr ""
#~ msgid ""
#~ "There is no method within the "
#~ "datagram API to specify whether it "
#~ "is non-repliable (raw)\n"
#~ "or repliable. The application should be"
#~ " designed to expect the appropriate "
#~ "type.\n"
#~ "The I2CP protocol number or port "
#~ "could also be used by the "
#~ "application to\n"
#~ "indicate datagram type."
#~ msgstr ""
#~ msgid ""
#~ "Lookups are not encrypted and thus "
#~ "are vulnerable to snooping by the "
#~ "outbound endpoint\n"
#~ "(OBEP) of the client tunnel."
#~ msgstr ""
#~ msgid ""
#~ "As the requesting router does not "
#~ "reveal itself, there is no recipient "
#~ "public key for the floodfill router "
#~ "to\n"
#~ "encrypt the reply with. Therefore, the"
#~ " reply is exposed to the inbound "
#~ "gateway (IBGW)\n"
#~ "of the inbound exploratory tunnel.\n"
#~ "An appropriate method of encrypting the"
#~ " reply is a topic for future "
#~ "work."
#~ msgstr ""
#~ msgid ""
#~ "As for regular lookups, the reply is unencrypted,\n"
#~ "thus exposing the reply to the "
#~ "inbound gateway (IBGW) of the reply "
#~ "tunnel, and\n"
#~ "an appropriate method of encrypting the"
#~ " reply is a topic for future "
#~ "work.\n"
#~ "As the IBGW for the reply is "
#~ "one of the gateways published in "
#~ "the LeaseSet,\n"
#~ "the exposure is minimal."
#~ msgstr ""
#~ msgid "Expiration is currently unused, always null (all zeroes))"
#~ msgstr ""
#~ msgid "November 2011"
#~ msgstr ""
#~ msgid ""
#~ "When a new update file specification "
#~ "is defined, it should use a larger"
#~ "\n"
#~ "DSA signature, and the signature should cover the version.\n"
#~ "A file format version number might be a good idea too."
#~ msgstr ""
#~ msgid ""
#~ "The network will eventually grow too large for update over HTTP.\n"
#~ "The built-in BitTorrent client, "
#~ "i2psnark, may be used as a "
#~ "distributed update method.\n"
#~ "This development effort was started in"
#~ " 2009 but is on hold until it"
#~ " is required."
#~ msgstr ""
#~ msgid ""
#~ "The transport system delivers <a "
#~ "href=\"%(i2np)s\">I2NP messages</a>. The transport"
#~ " selected for any message is\n"
#~ "independent of the application-layer protocol (TCP or UDP)."
#~ msgstr ""
#~ msgid ""
#~ "Also, the existing transports will be"
#~ " enhanced to support multiple addresses "
#~ "within a single transport,\n"
#~ "including IPV6 addresses. Currently, a "
#~ "transport may only advertise a single"
#~ " IPV4 address."
#~ msgstr ""
#~ msgid "October 2012"
#~ msgstr ""
#~ msgid ""
#~ "As of router version 0.8.12,\n"
#~ "two MTU values are used: 620 and 1484.\n"
#~ "The MTU value is adjusted based on"
#~ " the percentage of packets that are"
#~ " retransmitted."
#~ msgstr ""
#~ msgid ""
#~ "For both MTU values, it is desirable that (MTU % 16) == 12, so that\n"
#~ "the payload portion after the 28-byte IP/UDP header is a multiple of\n"
#~ "16 bytes, for encryption purposes.\n"
#~ "This calculation is for IPv4 only. "
#~ "While the protocol as specified supports"
#~ " IPv6\n"
#~ "addresses, IPv6 is not yet implemented."
#~ msgstr ""
#~ msgid ""
#~ "For our bad sake the syndie project is 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 100 Bitcoin."
#~ msgstr ""
#~ 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 32KB. 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 under 32KB."
#~ msgstr ""
#~ msgid ""
#~ "I2P destinations are mobile identifiers "
#~ "- they can be moved from one "
#~ "I2P router\n"
#~ "to another (or with some special "
#~ "software, it can even 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 ""
#~ msgid ""
#~ "I2P destinations are ugly and large "
#~ "- behind the scenes, they contain "
#~ "a 2048bit ElGamal\n"
#~ "public key for encryption, a 1024bit "
#~ "DSA public key for signing, and a"
#~ " variable size \n"
#~ "certificate, which may contain proof of work or blinded data."
#~ msgstr ""
#~ 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 at the moment those techniques "
#~ "do not guarantee\n"
#~ "globally uniqueness (since they're stored "
#~ "locally at each person's machine as "
#~ "\"hosts.txt\")\n"
#~ "and the current mechanism is not "
#~ "especially scalable nor secure (updates "
#~ "to one host file are\n"
#~ "manually managed within Monotone, and as"
#~ " such, anyone with commit rights on"
#~ " the repository can\n"
#~ "change the destinations). 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"
#~ "<a href=\"%(naming)s\">Further information on "
#~ "the naming system</a> is available."
#~ msgstr ""
#~ msgid ""
#~ "A useful thing to remember is that"
#~ " 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 ""
#~ msgid ""
#~ "Of course, another useful thing to "
#~ "remember is that 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 ""
#~ msgid "I2P datagrams can be up to 32KB"
#~ msgstr ""
#~ 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 32KB datagrams\n"
#~ "(31KB when using the repliable kind)."
#~ " For many applications, 32KB 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 ""
#~ msgid "SAM is not recommended. SAM V2 is okay, SAM V3 is beta."
#~ msgstr ""
#~ 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 "
#~ "8bit 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 ""
#~ msgid ""
#~ "It was possible to write I2P "
#~ "applications in Java using the "
#~ "ministreaming library.\n"
#~ "However, the Streaming library has "
#~ "superceded this, and provides better "
#~ "functionality."
#~ msgstr ""
#~ msgid ""
#~ "Development using the streaming library "
#~ "requires the following libraries in your"
#~ " classpath:"
#~ msgstr ""
#~ msgid "the streaming library itself."
#~ msgstr ""
#~ msgid ""
#~ "the ministreaming library is used as "
#~ "the base for the streaming library."
#~ msgstr ""
#~ msgid ""
#~ "some standard I2P classes (like the "
#~ "Destination class) are very convenient "
#~ "when developing."
#~ msgstr ""
#~ msgid ""
#~ "We will start by initializing the "
#~ "server application. This requires getting "
#~ "an I2PSocketManager\n"
#~ "and creating an I2PServerSocket.\n"
#~ "In addition, we will ask the "
#~ "I2PSocketManager for an I2PSession, so "
#~ "we can find out the Destination we"
#~ " use."
#~ msgstr ""
#~ msgid "Existing Applications in Development"
#~ msgstr ""
#~ msgid "Contact us if you would like to help."
#~ msgstr ""
#~ msgid ""
#~ "Download manager / eepget scheduler -\n"
#~ "We use eepget to fetch lots of "
#~ "things reliably over i2p, and there's"
#~ " already an\n"
#~ "implementation of a sequential download "
#~ "manager (net.i2p.util.EepGetScheduler),\n"
#~ "but there isn't any sort of user"
#~ " interface to it. A web based "
#~ "UI would be\n"
#~ "great."
#~ msgstr ""
#~ msgid ""
#~ "Content Distribution / DHT applications "
#~ "- help out with <a "
#~ "href=\"http://%(feedspace)s\">feedspace</a>,\n"
#~ "port dijjer, look for alternatives"
#~ msgstr ""
#~ msgid ""
#~ "Resurrect some old apps - in the i2p source package -\n"
#~ "bogobot, pants, proxyscript, q, stasher, socks proxy, i2ping"
#~ msgstr ""