From 791de54dca370431355c9b0db11a6afb6fb5c477 Mon Sep 17 00:00:00 2001 From: zzz Date: Fri, 15 May 2020 13:06:49 +0000 Subject: [PATCH] new partial translations --- .../translations/da/LC_MESSAGES/comparison.po | 707 +++++ .../translations/hu/LC_MESSAGES/comparison.po | 707 +++++ .../translations/ja/LC_MESSAGES/comparison.po | 707 +++++ i2p2www/translations/sk/LC_MESSAGES/about.po | 2280 ++++++++++++++++ i2p2www/translations/sq/LC_MESSAGES/about.po | 2397 +++++++++++++++++ 5 files changed, 6798 insertions(+) create mode 100644 i2p2www/translations/da/LC_MESSAGES/comparison.po create mode 100644 i2p2www/translations/hu/LC_MESSAGES/comparison.po create mode 100644 i2p2www/translations/ja/LC_MESSAGES/comparison.po create mode 100644 i2p2www/translations/sk/LC_MESSAGES/about.po create mode 100644 i2p2www/translations/sq/LC_MESSAGES/about.po diff --git a/i2p2www/translations/da/LC_MESSAGES/comparison.po b/i2p2www/translations/da/LC_MESSAGES/comparison.po new file mode 100644 index 00000000..ff6c6cd1 --- /dev/null +++ b/i2p2www/translations/da/LC_MESSAGES/comparison.po @@ -0,0 +1,707 @@ +# Danish translations for I2P. +# Copyright (C) 2018 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2018-08-24 11:47+0000\n" +"PO-Revision-Date: 2018-10-04 00:28+0000\n" +"Last-Translator: erinm\n" +"Language-Team: Danish (http://www.transifex.com/otf/I2P/language/da/)\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/comparison/freenet.html:2 +msgid "I2P Compared to Freenet" +msgstr "" + +#: i2p2www/pages/site/comparison/freenet.html:8 +msgid "" +"Freenet is a fully distributed, peer to peer anonymous publishing " +"network, offering \n" +"secure ways to store data, as well as some approaches attempting to " +"address the loads\n" +"of a flash flood. While Freenet is designed as a distributed data store," +" people have\n" +"built applications on top of it to do more generic anonymous " +"communication, such as \n" +"static websites and message boards." +msgstr "" + +#: i2p2www/pages/site/comparison/freenet.html:16 +#, python-format +msgid "" +"Compared to I2P, Freenet offers some substantial benefits - it is a " +"distributed data\n" +"store, while I2P is not, allowing people to retrieve the content " +"published by others \n" +"even when the publisher is no longer online. In addition, it should be " +"able to \n" +"distribute popular data fairly efficiently. I2P itself does not and will" +" not provide \n" +"this functionality. On the other hand, there is overlap for users who " +"simply want to \n" +"communicate with each other anonymously through websites, message boards," +" file sharing\n" +"programs, etc. There have also been some attempts to develop a " +"distributed data \n" +"store to run on top of I2P,\n" +"(most recently a port of Tahoe-LAFS)\n" +"but nothing is yet ready for general use." +msgstr "" + +#: i2p2www/pages/site/comparison/freenet.html:29 +msgid "" +"However, even ignoring any implementations issues, there are some " +"concerns \n" +"about Freenet's algorithms from both a scalability and anonymity " +"perspective, owing \n" +"largely to Freenet's heuristic driven routing. The interactions of " +"various techniques \n" +"certainly may successfully deter various attacks, and perhaps some " +"aspects of the \n" +"routing algorithms will provide the hoped for scalability. " +"Unfortunately, not much\n" +"analysis of the algorithms involved has resulted in positive results, but" +" there is still\n" +"hope. At the very least, Freenet does provide substantial anonymity " +"against an attacker\n" +"who does not have the resources necessary to analyze it further." +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:2 +msgid "Comparing I2P to other projects" +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:4 +msgid "" +"There are a great many other applications and projects working on " +"anonymous \n" +"communication and I2P has been inspired by much of their efforts. This " +"is not \n" +"a comprehensive list of anonymity resources - both freehaven's \n" +"Anonymity " +"Bibliography\n" +"and GNUnet's related " +"projects\n" +"serve that purpose well. That said, a few systems stand out for further\n" +"comparison. The following have individual comparison pages:" +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:20 +#, python-format +msgid "" +"The following are discussed on the other " +"networks page:" +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:33 +#, python-format +msgid "" +"The content of this page is subject to update, discussion and dispute, " +"and we welcome comments and additions.\n" +"You may contribute an analysis by entering a new " +"ticket on Trac." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:2 +msgid "I2P Compared to Other Anonymous Networks" +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:5 +msgid "The following networks are discussed on this page." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:17 +#, python-format +msgid "" +"Most of the following sections are fairly old, and may not be accurate.\n" +"For an overview of available comparisons, see the\n" +"main network comparisons page.\n" +"You may contribute an analysis by entering a\n" +"new ticket on Trac." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:29 +#, python-format +msgid "" +"RetroShare is a set of peer-to-peer applications running in a\n" +"Friend-to-friend (F2F) network. Each peer of " +"such F2F \n" +"network makes direct IP connections only to authenticated peers " +"(\"friends\") after explicit \n" +"certificates exchange. It can discover unauthenticated peers (e.g. " +"friends of friends), \n" +"but connections to them are relayed over \"friend\" peers for providing " +"privacy and anonymity." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:37 +msgid "" +"RetroShare is designed to build a private network of trusted peers, while" +" I2P is designed \n" +"to be a large-scaled public anonymous network. Recent versions of " +"RetroShare have options to run \n" +"as a public \"darknet\" by using I2P or Tor as a transport. That way all " +"connections are \n" +"anonymized and no trust is required for adding new \"friends\"." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:48 +#, python-format +msgid "" +"Morphmix and Tarzan are both fully distributed, peer to peer networks of" +" \n" +"anonymizing proxies, allowing people to tunnel out through the low " +"latency \n" +"mix network. Morphmix includes some very interesting collusion detection" +" \n" +"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of " +"IP\n" +"addresses to accomplish the same. The two primary differences between \n" +"these systems and I2P are related to I2P's threat model \n" +"and their out-proxy design (as opposed to providing both sender and " +"receiver \n" +"anonymity). There is source code available to both systems, but we are " +"not aware \n" +"of their use outside of academic environments." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:172 +#, python-format +msgid "" +"\n" +"Mixminion and Mixmaster are networks to support anonymous email against a" +" very\n" +"powerful adversary.\n" +"High-latency messaging applications running on top of I2P\n" +"(for example Syndie or I2PBote)\n" +"may perhaps prove adequate to meet the threat\n" +"model of those adversaries, while running in parallel along side the " +"needs of low latency users, to provide\n" +"a significantly larger anonymity set.\n" +"High-latency support within the I2P router itself may or may not be added" +" in a distant future release.\n" +"It is too early to say if I2P will meet the needs of users requiring " +"extreme protection for email." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:184 +msgid "" +"As with Tor and Onion Routing, \n" +"both Mixminion and Mixmaster take the directory based approach as well." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:194 +#, python-format +msgid "" +"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing " +"web requests,\n" +"and as such it has a few centralized nodes (participants in the cascade) " +"that blend\n" +"and mix requests from clients through the sequence of nodes (the cascade)" +" before \n" +"proxying out onto the web. The scope, threat model, and security is " +"substantially \n" +"different from I2P, but for those who don't require significant anonymity" +" but still\n" +"are not satisfied with an Anonymizer-like service, JAP is worth " +"reviewing. One\n" +"caution to note is that anyone under the jurisdiction of the German " +"courts may want\n" +"to take care, as the German Federal Bureau of Criminal Investigation " +"(FBCI) has \n" +"successfully mounted an \n" +"attack \n" +"on the network. Even though the method of this attack was later found to" +" be illegal \n" +"in the German courts, the fact that the data was successfully collected " +"is the \n" +"concern. Courts change their minds based upon circumstance, and this is " +"evidence that \n" +"if a government body or intelligence agency wanted to, they could gather " +"the data, even \n" +"if it may be found inadmissible in some courts later)" +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:216 +#, python-format +msgid "" +"Both of these systems work through the same basic \n" +"antnet routing, providing some degree of\n" +"anonymity based on the threat model of providing plausible deniability " +"against a simple \n" +"non-colluding adversary. With the antnet routing, they first either do a" +" random walk or a \n" +"broadcast search to find some peer with the data or identity desired, and" +" then use a feedback\n" +"algorithm to optimize that found path. This works well for applications " +"that merely want to know \n" +"what other people around them have to offer - \"How are y'all doing\" vs." +" \"Hey Alice, how are you\" - \n" +"you basically get a local cluster of nodes that can share files with and " +"maintain some degree of \n" +"anonymity (though you don't have much control over who is in that group " +"of peers)." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:228 +msgid "" +"However, the algorithm does not scale well at all - if the application " +"wants to speak with a \n" +"particular peer it ends up doing a broadcast search or random walk " +"(though if they are lucky enough\n" +"for that to succeed, the antnet routing should optimize that found " +"connection). This means that \n" +"while these networks can work great at small scales, they are not " +"suitable for large networks where\n" +"someone wants to get in touch with another specific peer. That does not " +"mean that there is no \n" +"value in these systems, just that their applicability is limited to " +"situations where their \n" +"particular issues can be addressed." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:239 +#, python-format +msgid "" +"This was a closed-source network targeted at Iranian users.\n" +"Tor did a good writeup on what to look for in a " +"circumvention tool.\n" +"Suffice it to say that being closed source and publicly targeting a " +"specific country are not good ideas.\n" +"I2P is, of course, open source. However, that source, and our\n" +"technical documentation, need much more review." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:248 +msgid "Paid VPN Services" +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:249 +#: i2p2www/pages/site/comparison/other-networks.html:255 +#, python-format +msgid "" +"You may contribute an analysis by entering a\n" +"new ticket on Trac." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:254 +msgid "Others" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:2 +msgid "I2P Compared to Tor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:3 +msgid "November 2016" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:9 +#, python-format +msgid "" +"Tor and Onion Routing are both anonymizing proxy networks, \n" +"allowing people to tunnel out through their low latency mix \n" +"network. The two primary differences between Tor / \n" +"Onion-Routing and I2P are again related to differences in \n" +"the threat model and the out-proxy design (though Tor\n" +"supports hidden services as well). In addition, Tor\n" +"takes the directory-based approach - providing a \n" +"centralized point to manage the overall 'view' of the \n" +"network, as well as gather and report statistics, as \n" +"opposed to I2P's distributed network \n" +"database and peer selection." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:23 +msgid "" +"The I2P/Tor outproxy functionality does have a few \n" +"substantial weaknesses against certain attackers - \n" +"once the communication leaves the mixnet, global passive\n" +"adversaries can more easily mount traffic analysis. In \n" +"addition, the outproxies have access to the cleartext \n" +"of the data transferred in both directions, and \n" +"outproxies are prone to abuse, along with all of the \n" +"other security issues we've come to know and love with \n" +"normal Internet traffic." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:35 +msgid "" +"However, many people don't need to worry about those \n" +"situations, as they are outside their threat model. It\n" +"is, also, outside I2P's (formal) functional scope (if people want\n" +"to build outproxy functionality on top of an anonymous\n" +"communication layer, they can). In fact, some I2P users\n" +"currently take advantage of Tor to outproxy." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:49 +msgid "Comparison of Tor and I2P Terminology" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:50 +msgid "" +"While Tor and I2P are similar in many ways, much of the terminology is " +"different." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:55 +msgid "Cell" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:55 +msgid "Message" +msgstr "Besked" + +#: i2p2www/pages/site/comparison/tor.html:56 +msgid "Client" +msgstr "Klient" + +#: i2p2www/pages/site/comparison/tor.html:56 +msgid "Router or Client" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:57 +msgid "Circuit" +msgstr "Kredsløb" + +#: i2p2www/pages/site/comparison/tor.html:57 +msgid "Tunnel" +msgstr "Tunnel" + +#: i2p2www/pages/site/comparison/tor.html:58 +msgid "Directory" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:58 +msgid "NetDb" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:59 +msgid "Directory Server" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:59 +msgid "Floodfill Router" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:60 +msgid "Entry Guards" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:60 +msgid "Fast Peers" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:61 +msgid "Entry Node" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:61 +msgid "Inproxy" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:62 +msgid "Exit Node" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:62 +msgid "Outproxy" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:63 +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "Hidden Service" +msgstr "Skjulte Tjenster" + +#: i2p2www/pages/site/comparison/tor.html:63 +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "Eepsite or Destination" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:64 +msgid "Hidden Service Descriptor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:64 +msgid "LeaseSet" +msgstr "LeaseSet" + +#: i2p2www/pages/site/comparison/tor.html:65 +msgid "Introduction point" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:65 +msgid "Inbound Gateway" +msgstr "Indadgående portåbning" + +#: i2p2www/pages/site/comparison/tor.html:66 +msgid "Node" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:66 +#: i2p2www/pages/site/comparison/tor.html:69 +#: i2p2www/pages/site/comparison/tor.html:72 +msgid "Router" +msgstr "Router" + +#: i2p2www/pages/site/comparison/tor.html:67 +msgid "Onion Proxy" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:67 +msgid "I2PTunnel Client (more or less)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "Onion Service" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:69 +msgid "Relay" +msgstr "Relæ" + +#: i2p2www/pages/site/comparison/tor.html:70 +msgid "Rendezvous Point" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:70 +msgid "somewhat like Inbound Gateway + Outbound Endpoint" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:71 +msgid "Router Descriptor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:71 +msgid "RouterInfo" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:72 +msgid "Server" +msgstr "Server" + +#: i2p2www/pages/site/comparison/tor.html:75 +msgid "Benefits of Tor over I2P" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:78 +msgid "" +"Much bigger user base; much more visibility in the academic and hacker " +"communities; benefits from\n" +"formal studies of anonymity, resistance, and performance;\n" +"has a non-anonymous, visible, university-based leader" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:84 +msgid "Has already solved some scaling issues I2P has yet to address" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:85 +msgid "Has significant funding" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:86 +msgid "Has more developers, including several that are funded" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:88 +msgid "" +"More resistant to state-level blocking due to TLS transport layer and " +"bridges\n" +"(I2P has proposals for \"full restricted routes\" but these are not yet " +"implemented)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:93 +msgid "Big enough that it has had to adapt to blocking and DOS attempts" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:94 +msgid "Designed and optimized for exit traffic, with a large number of exit nodes" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:96 +msgid "" +"Better documentation, has formal papers and specifications,\n" +"better website, many more translations" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:101 +msgid "More efficient with memory usage" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:102 +msgid "Tor client nodes have very low bandwidth overhead" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:104 +msgid "" +"Centralized control reduces the complexity at each\n" +"node and can efficiently address Sybil attacks" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:110 +msgid "" +"A core of high capacity nodes provides higher\n" +"throughput and lower latency" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:115 +msgid "C, not Java (ewww)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:118 +msgid "Benefits of I2P over Tor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:120 +msgid "" +"Designed and optimized for hidden services, which are much faster than in" +" Tor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:121 +msgid "Fully distributed and self organizing" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:123 +msgid "" +"Peers are selected by continuously profiling and ranking performance,\n" +"rather than trusting claimed capacity" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:129 +msgid "" +"Floodfill peers (\"directory servers\") are varying and untrusted,\n" +"rather than hardcoded" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:134 +msgid "Small enough that it hasn't been blocked or DOSed much, or at all" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:135 +msgid "Peer-to-peer friendly" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:136 +msgid "Packet switched instead of circuit switched" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:139 +msgid "" +"implicit transparent load balancing of messages \n" +"across multiple peers, rather than a single path" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:145 +msgid "" +"resilience vs. failures by running multiple \n" +"tunnels in parallel, plus rotating tunnels" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:151 +msgid "" +"scale each client's connections at O(1) instead \n" +"of O(N) (Alice has e.g. 2 inbound tunnels that are \n" +"used by all of the peers Alice is talking with, \n" +"rather than a circuit for each)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:161 +msgid "" +"Unidirectional tunnels instead of bidirectional\n" +"circuits, doubling the number of nodes a peer has to\n" +"compromise to get the same information." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:166 +#, python-format +msgid "Counter-arguments and further discussion here." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:171 +msgid "" +"Protection against detecting client activity, even\n" +"when an attacker is participating in the tunnel, as\n" +"tunnels are used for more than simply passing end \n" +"to end messages (e.g. netDb, tunnel management, \n" +"tunnel testing)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:180 +msgid "" +"Tunnels in I2P are short lived, decreasing the number\n" +"of samples that an attacker can use to mount an \n" +"active attack with, unlike circuits in Tor, which are\n" +"typically long lived." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:188 +msgid "" +"I2P APIs are designed specifically for anonymity and\n" +"security, while SOCKS is designed for functionality." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:193 +msgid "Essentially all peers participate in routing for others" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:195 +msgid "" +"The bandwidth overhead of being a full peer is low, \n" +"while in Tor, while client nodes don't require much\n" +"bandwidth, they don't fully participate in the mixnet." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:201 +msgid "Integrated automatic update mechanism" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:202 +msgid "Both TCP and UDP transports" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:203 +msgid "Java, not C (ewww)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:206 +msgid "Other potential benefits of I2P but not yet implemented" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:207 +msgid "...and may never be implemented, so don't count on them!" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:210 +msgid "" +"Defense vs. message count analysis by garlic wrapping \n" +"multiple messages" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:216 +msgid "" +"Defense vs. long term intersection by adding delays \n" +"at various hops (where the delays are not discernible\n" +"by other hops)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:223 +msgid "" +"Various mixing strategies at the tunnel level (e.g.\n" +"create a tunnel that will handle 500 messages / minute,\n" +"where the endpoint will inject dummy messages if there\n" +"are insufficient messages, etc)" +msgstr "" + diff --git a/i2p2www/translations/hu/LC_MESSAGES/comparison.po b/i2p2www/translations/hu/LC_MESSAGES/comparison.po new file mode 100644 index 00000000..03a9adb0 --- /dev/null +++ b/i2p2www/translations/hu/LC_MESSAGES/comparison.po @@ -0,0 +1,707 @@ +# Hungarian translations for I2P. +# Copyright (C) 2018 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2018-08-24 11:47+0000\n" +"PO-Revision-Date: 2018-10-04 00:57+0000\n" +"Last-Translator: erinm\n" +"Language-Team: Hungarian (http://www.transifex.com/otf/I2P/language/hu/)\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/comparison/freenet.html:2 +msgid "I2P Compared to Freenet" +msgstr "" + +#: i2p2www/pages/site/comparison/freenet.html:8 +msgid "" +"Freenet is a fully distributed, peer to peer anonymous publishing " +"network, offering \n" +"secure ways to store data, as well as some approaches attempting to " +"address the loads\n" +"of a flash flood. While Freenet is designed as a distributed data store," +" people have\n" +"built applications on top of it to do more generic anonymous " +"communication, such as \n" +"static websites and message boards." +msgstr "" + +#: i2p2www/pages/site/comparison/freenet.html:16 +#, python-format +msgid "" +"Compared to I2P, Freenet offers some substantial benefits - it is a " +"distributed data\n" +"store, while I2P is not, allowing people to retrieve the content " +"published by others \n" +"even when the publisher is no longer online. In addition, it should be " +"able to \n" +"distribute popular data fairly efficiently. I2P itself does not and will" +" not provide \n" +"this functionality. On the other hand, there is overlap for users who " +"simply want to \n" +"communicate with each other anonymously through websites, message boards," +" file sharing\n" +"programs, etc. There have also been some attempts to develop a " +"distributed data \n" +"store to run on top of I2P,\n" +"(most recently a port of Tahoe-LAFS)\n" +"but nothing is yet ready for general use." +msgstr "" + +#: i2p2www/pages/site/comparison/freenet.html:29 +msgid "" +"However, even ignoring any implementations issues, there are some " +"concerns \n" +"about Freenet's algorithms from both a scalability and anonymity " +"perspective, owing \n" +"largely to Freenet's heuristic driven routing. The interactions of " +"various techniques \n" +"certainly may successfully deter various attacks, and perhaps some " +"aspects of the \n" +"routing algorithms will provide the hoped for scalability. " +"Unfortunately, not much\n" +"analysis of the algorithms involved has resulted in positive results, but" +" there is still\n" +"hope. At the very least, Freenet does provide substantial anonymity " +"against an attacker\n" +"who does not have the resources necessary to analyze it further." +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:2 +msgid "Comparing I2P to other projects" +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:4 +msgid "" +"There are a great many other applications and projects working on " +"anonymous \n" +"communication and I2P has been inspired by much of their efforts. This " +"is not \n" +"a comprehensive list of anonymity resources - both freehaven's \n" +"Anonymity " +"Bibliography\n" +"and GNUnet's related " +"projects\n" +"serve that purpose well. That said, a few systems stand out for further\n" +"comparison. The following have individual comparison pages:" +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:20 +#, python-format +msgid "" +"The following are discussed on the other " +"networks page:" +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:33 +#, python-format +msgid "" +"The content of this page is subject to update, discussion and dispute, " +"and we welcome comments and additions.\n" +"You may contribute an analysis by entering a new " +"ticket on Trac." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:2 +msgid "I2P Compared to Other Anonymous Networks" +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:5 +msgid "The following networks are discussed on this page." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:17 +#, python-format +msgid "" +"Most of the following sections are fairly old, and may not be accurate.\n" +"For an overview of available comparisons, see the\n" +"main network comparisons page.\n" +"You may contribute an analysis by entering a\n" +"new ticket on Trac." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:29 +#, python-format +msgid "" +"RetroShare is a set of peer-to-peer applications running in a\n" +"Friend-to-friend (F2F) network. Each peer of " +"such F2F \n" +"network makes direct IP connections only to authenticated peers " +"(\"friends\") after explicit \n" +"certificates exchange. It can discover unauthenticated peers (e.g. " +"friends of friends), \n" +"but connections to them are relayed over \"friend\" peers for providing " +"privacy and anonymity." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:37 +msgid "" +"RetroShare is designed to build a private network of trusted peers, while" +" I2P is designed \n" +"to be a large-scaled public anonymous network. Recent versions of " +"RetroShare have options to run \n" +"as a public \"darknet\" by using I2P or Tor as a transport. That way all " +"connections are \n" +"anonymized and no trust is required for adding new \"friends\"." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:48 +#, python-format +msgid "" +"Morphmix and Tarzan are both fully distributed, peer to peer networks of" +" \n" +"anonymizing proxies, allowing people to tunnel out through the low " +"latency \n" +"mix network. Morphmix includes some very interesting collusion detection" +" \n" +"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of " +"IP\n" +"addresses to accomplish the same. The two primary differences between \n" +"these systems and I2P are related to I2P's threat model \n" +"and their out-proxy design (as opposed to providing both sender and " +"receiver \n" +"anonymity). There is source code available to both systems, but we are " +"not aware \n" +"of their use outside of academic environments." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:172 +#, python-format +msgid "" +"\n" +"Mixminion and Mixmaster are networks to support anonymous email against a" +" very\n" +"powerful adversary.\n" +"High-latency messaging applications running on top of I2P\n" +"(for example Syndie or I2PBote)\n" +"may perhaps prove adequate to meet the threat\n" +"model of those adversaries, while running in parallel along side the " +"needs of low latency users, to provide\n" +"a significantly larger anonymity set.\n" +"High-latency support within the I2P router itself may or may not be added" +" in a distant future release.\n" +"It is too early to say if I2P will meet the needs of users requiring " +"extreme protection for email." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:184 +msgid "" +"As with Tor and Onion Routing, \n" +"both Mixminion and Mixmaster take the directory based approach as well." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:194 +#, python-format +msgid "" +"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing " +"web requests,\n" +"and as such it has a few centralized nodes (participants in the cascade) " +"that blend\n" +"and mix requests from clients through the sequence of nodes (the cascade)" +" before \n" +"proxying out onto the web. The scope, threat model, and security is " +"substantially \n" +"different from I2P, but for those who don't require significant anonymity" +" but still\n" +"are not satisfied with an Anonymizer-like service, JAP is worth " +"reviewing. One\n" +"caution to note is that anyone under the jurisdiction of the German " +"courts may want\n" +"to take care, as the German Federal Bureau of Criminal Investigation " +"(FBCI) has \n" +"successfully mounted an \n" +"attack \n" +"on the network. Even though the method of this attack was later found to" +" be illegal \n" +"in the German courts, the fact that the data was successfully collected " +"is the \n" +"concern. Courts change their minds based upon circumstance, and this is " +"evidence that \n" +"if a government body or intelligence agency wanted to, they could gather " +"the data, even \n" +"if it may be found inadmissible in some courts later)" +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:216 +#, python-format +msgid "" +"Both of these systems work through the same basic \n" +"antnet routing, providing some degree of\n" +"anonymity based on the threat model of providing plausible deniability " +"against a simple \n" +"non-colluding adversary. With the antnet routing, they first either do a" +" random walk or a \n" +"broadcast search to find some peer with the data or identity desired, and" +" then use a feedback\n" +"algorithm to optimize that found path. This works well for applications " +"that merely want to know \n" +"what other people around them have to offer - \"How are y'all doing\" vs." +" \"Hey Alice, how are you\" - \n" +"you basically get a local cluster of nodes that can share files with and " +"maintain some degree of \n" +"anonymity (though you don't have much control over who is in that group " +"of peers)." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:228 +msgid "" +"However, the algorithm does not scale well at all - if the application " +"wants to speak with a \n" +"particular peer it ends up doing a broadcast search or random walk " +"(though if they are lucky enough\n" +"for that to succeed, the antnet routing should optimize that found " +"connection). This means that \n" +"while these networks can work great at small scales, they are not " +"suitable for large networks where\n" +"someone wants to get in touch with another specific peer. That does not " +"mean that there is no \n" +"value in these systems, just that their applicability is limited to " +"situations where their \n" +"particular issues can be addressed." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:239 +#, python-format +msgid "" +"This was a closed-source network targeted at Iranian users.\n" +"Tor did a good writeup on what to look for in a " +"circumvention tool.\n" +"Suffice it to say that being closed source and publicly targeting a " +"specific country are not good ideas.\n" +"I2P is, of course, open source. However, that source, and our\n" +"technical documentation, need much more review." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:248 +msgid "Paid VPN Services" +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:249 +#: i2p2www/pages/site/comparison/other-networks.html:255 +#, python-format +msgid "" +"You may contribute an analysis by entering a\n" +"new ticket on Trac." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:254 +msgid "Others" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:2 +msgid "I2P Compared to Tor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:3 +msgid "November 2016" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:9 +#, python-format +msgid "" +"Tor and Onion Routing are both anonymizing proxy networks, \n" +"allowing people to tunnel out through their low latency mix \n" +"network. The two primary differences between Tor / \n" +"Onion-Routing and I2P are again related to differences in \n" +"the threat model and the out-proxy design (though Tor\n" +"supports hidden services as well). In addition, Tor\n" +"takes the directory-based approach - providing a \n" +"centralized point to manage the overall 'view' of the \n" +"network, as well as gather and report statistics, as \n" +"opposed to I2P's distributed network \n" +"database and peer selection." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:23 +msgid "" +"The I2P/Tor outproxy functionality does have a few \n" +"substantial weaknesses against certain attackers - \n" +"once the communication leaves the mixnet, global passive\n" +"adversaries can more easily mount traffic analysis. In \n" +"addition, the outproxies have access to the cleartext \n" +"of the data transferred in both directions, and \n" +"outproxies are prone to abuse, along with all of the \n" +"other security issues we've come to know and love with \n" +"normal Internet traffic." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:35 +msgid "" +"However, many people don't need to worry about those \n" +"situations, as they are outside their threat model. It\n" +"is, also, outside I2P's (formal) functional scope (if people want\n" +"to build outproxy functionality on top of an anonymous\n" +"communication layer, they can). In fact, some I2P users\n" +"currently take advantage of Tor to outproxy." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:49 +msgid "Comparison of Tor and I2P Terminology" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:50 +msgid "" +"While Tor and I2P are similar in many ways, much of the terminology is " +"different." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:55 +msgid "Cell" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:55 +msgid "Message" +msgstr "Üzenet" + +#: i2p2www/pages/site/comparison/tor.html:56 +msgid "Client" +msgstr "Kliens" + +#: i2p2www/pages/site/comparison/tor.html:56 +msgid "Router or Client" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:57 +msgid "Circuit" +msgstr "Hálózat" + +#: i2p2www/pages/site/comparison/tor.html:57 +msgid "Tunnel" +msgstr "Alagút" + +#: i2p2www/pages/site/comparison/tor.html:58 +msgid "Directory" +msgstr "Könyvtár" + +#: i2p2www/pages/site/comparison/tor.html:58 +msgid "NetDb" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:59 +msgid "Directory Server" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:59 +msgid "Floodfill Router" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:60 +msgid "Entry Guards" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:60 +msgid "Fast Peers" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:61 +msgid "Entry Node" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:61 +msgid "Inproxy" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:62 +msgid "Exit Node" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:62 +msgid "Outproxy" +msgstr "Kimenő proxy" + +#: i2p2www/pages/site/comparison/tor.html:63 +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "Hidden Service" +msgstr "Rejtett Szolgáltatás" + +#: i2p2www/pages/site/comparison/tor.html:63 +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "Eepsite or Destination" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:64 +msgid "Hidden Service Descriptor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:64 +msgid "LeaseSet" +msgstr "LeaseSet" + +#: i2p2www/pages/site/comparison/tor.html:65 +msgid "Introduction point" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:65 +msgid "Inbound Gateway" +msgstr "Bejövő Átjáró (Gateway)" + +#: i2p2www/pages/site/comparison/tor.html:66 +msgid "Node" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:66 +#: i2p2www/pages/site/comparison/tor.html:69 +#: i2p2www/pages/site/comparison/tor.html:72 +msgid "Router" +msgstr "Router" + +#: i2p2www/pages/site/comparison/tor.html:67 +msgid "Onion Proxy" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:67 +msgid "I2PTunnel Client (more or less)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "Onion Service" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:69 +msgid "Relay" +msgstr "Elosztó" + +#: i2p2www/pages/site/comparison/tor.html:70 +msgid "Rendezvous Point" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:70 +msgid "somewhat like Inbound Gateway + Outbound Endpoint" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:71 +msgid "Router Descriptor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:71 +msgid "RouterInfo" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:72 +msgid "Server" +msgstr "Szerver" + +#: i2p2www/pages/site/comparison/tor.html:75 +msgid "Benefits of Tor over I2P" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:78 +msgid "" +"Much bigger user base; much more visibility in the academic and hacker " +"communities; benefits from\n" +"formal studies of anonymity, resistance, and performance;\n" +"has a non-anonymous, visible, university-based leader" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:84 +msgid "Has already solved some scaling issues I2P has yet to address" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:85 +msgid "Has significant funding" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:86 +msgid "Has more developers, including several that are funded" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:88 +msgid "" +"More resistant to state-level blocking due to TLS transport layer and " +"bridges\n" +"(I2P has proposals for \"full restricted routes\" but these are not yet " +"implemented)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:93 +msgid "Big enough that it has had to adapt to blocking and DOS attempts" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:94 +msgid "Designed and optimized for exit traffic, with a large number of exit nodes" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:96 +msgid "" +"Better documentation, has formal papers and specifications,\n" +"better website, many more translations" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:101 +msgid "More efficient with memory usage" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:102 +msgid "Tor client nodes have very low bandwidth overhead" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:104 +msgid "" +"Centralized control reduces the complexity at each\n" +"node and can efficiently address Sybil attacks" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:110 +msgid "" +"A core of high capacity nodes provides higher\n" +"throughput and lower latency" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:115 +msgid "C, not Java (ewww)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:118 +msgid "Benefits of I2P over Tor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:120 +msgid "" +"Designed and optimized for hidden services, which are much faster than in" +" Tor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:121 +msgid "Fully distributed and self organizing" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:123 +msgid "" +"Peers are selected by continuously profiling and ranking performance,\n" +"rather than trusting claimed capacity" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:129 +msgid "" +"Floodfill peers (\"directory servers\") are varying and untrusted,\n" +"rather than hardcoded" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:134 +msgid "Small enough that it hasn't been blocked or DOSed much, or at all" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:135 +msgid "Peer-to-peer friendly" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:136 +msgid "Packet switched instead of circuit switched" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:139 +msgid "" +"implicit transparent load balancing of messages \n" +"across multiple peers, rather than a single path" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:145 +msgid "" +"resilience vs. failures by running multiple \n" +"tunnels in parallel, plus rotating tunnels" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:151 +msgid "" +"scale each client's connections at O(1) instead \n" +"of O(N) (Alice has e.g. 2 inbound tunnels that are \n" +"used by all of the peers Alice is talking with, \n" +"rather than a circuit for each)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:161 +msgid "" +"Unidirectional tunnels instead of bidirectional\n" +"circuits, doubling the number of nodes a peer has to\n" +"compromise to get the same information." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:166 +#, python-format +msgid "Counter-arguments and further discussion here." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:171 +msgid "" +"Protection against detecting client activity, even\n" +"when an attacker is participating in the tunnel, as\n" +"tunnels are used for more than simply passing end \n" +"to end messages (e.g. netDb, tunnel management, \n" +"tunnel testing)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:180 +msgid "" +"Tunnels in I2P are short lived, decreasing the number\n" +"of samples that an attacker can use to mount an \n" +"active attack with, unlike circuits in Tor, which are\n" +"typically long lived." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:188 +msgid "" +"I2P APIs are designed specifically for anonymity and\n" +"security, while SOCKS is designed for functionality." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:193 +msgid "Essentially all peers participate in routing for others" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:195 +msgid "" +"The bandwidth overhead of being a full peer is low, \n" +"while in Tor, while client nodes don't require much\n" +"bandwidth, they don't fully participate in the mixnet." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:201 +msgid "Integrated automatic update mechanism" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:202 +msgid "Both TCP and UDP transports" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:203 +msgid "Java, not C (ewww)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:206 +msgid "Other potential benefits of I2P but not yet implemented" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:207 +msgid "...and may never be implemented, so don't count on them!" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:210 +msgid "" +"Defense vs. message count analysis by garlic wrapping \n" +"multiple messages" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:216 +msgid "" +"Defense vs. long term intersection by adding delays \n" +"at various hops (where the delays are not discernible\n" +"by other hops)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:223 +msgid "" +"Various mixing strategies at the tunnel level (e.g.\n" +"create a tunnel that will handle 500 messages / minute,\n" +"where the endpoint will inject dummy messages if there\n" +"are insufficient messages, etc)" +msgstr "" + diff --git a/i2p2www/translations/ja/LC_MESSAGES/comparison.po b/i2p2www/translations/ja/LC_MESSAGES/comparison.po new file mode 100644 index 00000000..e1cc62a7 --- /dev/null +++ b/i2p2www/translations/ja/LC_MESSAGES/comparison.po @@ -0,0 +1,707 @@ +# Japanese translations for I2P. +# Copyright (C) 2018 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2018-08-24 11:47+0000\n" +"PO-Revision-Date: 2019-12-16 04:20+0000\n" +"Last-Translator: Yutaka Niibe \n" +"Language-Team: Japanese (http://www.transifex.com/otf/I2P/language/ja/)\n" +"Plural-Forms: nplurals=1; plural=0\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/comparison/freenet.html:2 +msgid "I2P Compared to Freenet" +msgstr "" + +#: i2p2www/pages/site/comparison/freenet.html:8 +msgid "" +"Freenet is a fully distributed, peer to peer anonymous publishing " +"network, offering \n" +"secure ways to store data, as well as some approaches attempting to " +"address the loads\n" +"of a flash flood. While Freenet is designed as a distributed data store," +" people have\n" +"built applications on top of it to do more generic anonymous " +"communication, such as \n" +"static websites and message boards." +msgstr "" + +#: i2p2www/pages/site/comparison/freenet.html:16 +#, python-format +msgid "" +"Compared to I2P, Freenet offers some substantial benefits - it is a " +"distributed data\n" +"store, while I2P is not, allowing people to retrieve the content " +"published by others \n" +"even when the publisher is no longer online. In addition, it should be " +"able to \n" +"distribute popular data fairly efficiently. I2P itself does not and will" +" not provide \n" +"this functionality. On the other hand, there is overlap for users who " +"simply want to \n" +"communicate with each other anonymously through websites, message boards," +" file sharing\n" +"programs, etc. There have also been some attempts to develop a " +"distributed data \n" +"store to run on top of I2P,\n" +"(most recently a port of Tahoe-LAFS)\n" +"but nothing is yet ready for general use." +msgstr "" + +#: i2p2www/pages/site/comparison/freenet.html:29 +msgid "" +"However, even ignoring any implementations issues, there are some " +"concerns \n" +"about Freenet's algorithms from both a scalability and anonymity " +"perspective, owing \n" +"largely to Freenet's heuristic driven routing. The interactions of " +"various techniques \n" +"certainly may successfully deter various attacks, and perhaps some " +"aspects of the \n" +"routing algorithms will provide the hoped for scalability. " +"Unfortunately, not much\n" +"analysis of the algorithms involved has resulted in positive results, but" +" there is still\n" +"hope. At the very least, Freenet does provide substantial anonymity " +"against an attacker\n" +"who does not have the resources necessary to analyze it further." +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:2 +msgid "Comparing I2P to other projects" +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:4 +msgid "" +"There are a great many other applications and projects working on " +"anonymous \n" +"communication and I2P has been inspired by much of their efforts. This " +"is not \n" +"a comprehensive list of anonymity resources - both freehaven's \n" +"Anonymity " +"Bibliography\n" +"and GNUnet's related " +"projects\n" +"serve that purpose well. That said, a few systems stand out for further\n" +"comparison. The following have individual comparison pages:" +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:20 +#, python-format +msgid "" +"The following are discussed on the other " +"networks page:" +msgstr "" + +#: i2p2www/pages/site/comparison/index.html:33 +#, python-format +msgid "" +"The content of this page is subject to update, discussion and dispute, " +"and we welcome comments and additions.\n" +"You may contribute an analysis by entering a new " +"ticket on Trac." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:2 +msgid "I2P Compared to Other Anonymous Networks" +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:5 +msgid "The following networks are discussed on this page." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:17 +#, python-format +msgid "" +"Most of the following sections are fairly old, and may not be accurate.\n" +"For an overview of available comparisons, see the\n" +"main network comparisons page.\n" +"You may contribute an analysis by entering a\n" +"new ticket on Trac." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:29 +#, python-format +msgid "" +"RetroShare is a set of peer-to-peer applications running in a\n" +"Friend-to-friend (F2F) network. Each peer of " +"such F2F \n" +"network makes direct IP connections only to authenticated peers " +"(\"friends\") after explicit \n" +"certificates exchange. It can discover unauthenticated peers (e.g. " +"friends of friends), \n" +"but connections to them are relayed over \"friend\" peers for providing " +"privacy and anonymity." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:37 +msgid "" +"RetroShare is designed to build a private network of trusted peers, while" +" I2P is designed \n" +"to be a large-scaled public anonymous network. Recent versions of " +"RetroShare have options to run \n" +"as a public \"darknet\" by using I2P or Tor as a transport. That way all " +"connections are \n" +"anonymized and no trust is required for adding new \"friends\"." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:48 +#, python-format +msgid "" +"Morphmix and Tarzan are both fully distributed, peer to peer networks of" +" \n" +"anonymizing proxies, allowing people to tunnel out through the low " +"latency \n" +"mix network. Morphmix includes some very interesting collusion detection" +" \n" +"algorithms and Sybil defenses, while Tarzan makes use of the scarcity of " +"IP\n" +"addresses to accomplish the same. The two primary differences between \n" +"these systems and I2P are related to I2P's threat model \n" +"and their out-proxy design (as opposed to providing both sender and " +"receiver \n" +"anonymity). There is source code available to both systems, but we are " +"not aware \n" +"of their use outside of academic environments." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:172 +#, python-format +msgid "" +"\n" +"Mixminion and Mixmaster are networks to support anonymous email against a" +" very\n" +"powerful adversary.\n" +"High-latency messaging applications running on top of I2P\n" +"(for example Syndie or I2PBote)\n" +"may perhaps prove adequate to meet the threat\n" +"model of those adversaries, while running in parallel along side the " +"needs of low latency users, to provide\n" +"a significantly larger anonymity set.\n" +"High-latency support within the I2P router itself may or may not be added" +" in a distant future release.\n" +"It is too early to say if I2P will meet the needs of users requiring " +"extreme protection for email." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:184 +msgid "" +"As with Tor and Onion Routing, \n" +"both Mixminion and Mixmaster take the directory based approach as well." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:194 +#, python-format +msgid "" +"JAP (Java Anonymous Proxy) is a network of mix cascades for anonymizing " +"web requests,\n" +"and as such it has a few centralized nodes (participants in the cascade) " +"that blend\n" +"and mix requests from clients through the sequence of nodes (the cascade)" +" before \n" +"proxying out onto the web. The scope, threat model, and security is " +"substantially \n" +"different from I2P, but for those who don't require significant anonymity" +" but still\n" +"are not satisfied with an Anonymizer-like service, JAP is worth " +"reviewing. One\n" +"caution to note is that anyone under the jurisdiction of the German " +"courts may want\n" +"to take care, as the German Federal Bureau of Criminal Investigation " +"(FBCI) has \n" +"successfully mounted an \n" +"attack \n" +"on the network. Even though the method of this attack was later found to" +" be illegal \n" +"in the German courts, the fact that the data was successfully collected " +"is the \n" +"concern. Courts change their minds based upon circumstance, and this is " +"evidence that \n" +"if a government body or intelligence agency wanted to, they could gather " +"the data, even \n" +"if it may be found inadmissible in some courts later)" +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:216 +#, python-format +msgid "" +"Both of these systems work through the same basic \n" +"antnet routing, providing some degree of\n" +"anonymity based on the threat model of providing plausible deniability " +"against a simple \n" +"non-colluding adversary. With the antnet routing, they first either do a" +" random walk or a \n" +"broadcast search to find some peer with the data or identity desired, and" +" then use a feedback\n" +"algorithm to optimize that found path. This works well for applications " +"that merely want to know \n" +"what other people around them have to offer - \"How are y'all doing\" vs." +" \"Hey Alice, how are you\" - \n" +"you basically get a local cluster of nodes that can share files with and " +"maintain some degree of \n" +"anonymity (though you don't have much control over who is in that group " +"of peers)." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:228 +msgid "" +"However, the algorithm does not scale well at all - if the application " +"wants to speak with a \n" +"particular peer it ends up doing a broadcast search or random walk " +"(though if they are lucky enough\n" +"for that to succeed, the antnet routing should optimize that found " +"connection). This means that \n" +"while these networks can work great at small scales, they are not " +"suitable for large networks where\n" +"someone wants to get in touch with another specific peer. That does not " +"mean that there is no \n" +"value in these systems, just that their applicability is limited to " +"situations where their \n" +"particular issues can be addressed." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:239 +#, python-format +msgid "" +"This was a closed-source network targeted at Iranian users.\n" +"Tor did a good writeup on what to look for in a " +"circumvention tool.\n" +"Suffice it to say that being closed source and publicly targeting a " +"specific country are not good ideas.\n" +"I2P is, of course, open source. However, that source, and our\n" +"technical documentation, need much more review." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:248 +msgid "Paid VPN Services" +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:249 +#: i2p2www/pages/site/comparison/other-networks.html:255 +#, python-format +msgid "" +"You may contribute an analysis by entering a\n" +"new ticket on Trac." +msgstr "" + +#: i2p2www/pages/site/comparison/other-networks.html:254 +msgid "Others" +msgstr "その他" + +#: i2p2www/pages/site/comparison/tor.html:2 +msgid "I2P Compared to Tor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:3 +msgid "November 2016" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:9 +#, python-format +msgid "" +"Tor and Onion Routing are both anonymizing proxy networks, \n" +"allowing people to tunnel out through their low latency mix \n" +"network. The two primary differences between Tor / \n" +"Onion-Routing and I2P are again related to differences in \n" +"the threat model and the out-proxy design (though Tor\n" +"supports hidden services as well). In addition, Tor\n" +"takes the directory-based approach - providing a \n" +"centralized point to manage the overall 'view' of the \n" +"network, as well as gather and report statistics, as \n" +"opposed to I2P's distributed network \n" +"database and peer selection." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:23 +msgid "" +"The I2P/Tor outproxy functionality does have a few \n" +"substantial weaknesses against certain attackers - \n" +"once the communication leaves the mixnet, global passive\n" +"adversaries can more easily mount traffic analysis. In \n" +"addition, the outproxies have access to the cleartext \n" +"of the data transferred in both directions, and \n" +"outproxies are prone to abuse, along with all of the \n" +"other security issues we've come to know and love with \n" +"normal Internet traffic." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:35 +msgid "" +"However, many people don't need to worry about those \n" +"situations, as they are outside their threat model. It\n" +"is, also, outside I2P's (formal) functional scope (if people want\n" +"to build outproxy functionality on top of an anonymous\n" +"communication layer, they can). In fact, some I2P users\n" +"currently take advantage of Tor to outproxy." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:49 +msgid "Comparison of Tor and I2P Terminology" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:50 +msgid "" +"While Tor and I2P are similar in many ways, much of the terminology is " +"different." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:55 +msgid "Cell" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:55 +msgid "Message" +msgstr "メッセージ" + +#: i2p2www/pages/site/comparison/tor.html:56 +msgid "Client" +msgstr "クライアント" + +#: i2p2www/pages/site/comparison/tor.html:56 +msgid "Router or Client" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:57 +msgid "Circuit" +msgstr "回路" + +#: i2p2www/pages/site/comparison/tor.html:57 +msgid "Tunnel" +msgstr "トンネル" + +#: i2p2www/pages/site/comparison/tor.html:58 +msgid "Directory" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:58 +msgid "NetDb" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:59 +msgid "Directory Server" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:59 +msgid "Floodfill Router" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:60 +msgid "Entry Guards" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:60 +msgid "Fast Peers" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:61 +msgid "Entry Node" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:61 +msgid "Inproxy" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:62 +msgid "Exit Node" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:62 +msgid "Outproxy" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:63 +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "Hidden Service" +msgstr "Hidden サービス" + +#: i2p2www/pages/site/comparison/tor.html:63 +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "Eepsite or Destination" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:64 +msgid "Hidden Service Descriptor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:64 +msgid "LeaseSet" +msgstr "リースセット" + +#: i2p2www/pages/site/comparison/tor.html:65 +msgid "Introduction point" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:65 +msgid "Inbound Gateway" +msgstr "受信ゲートウェイ" + +#: i2p2www/pages/site/comparison/tor.html:66 +msgid "Node" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:66 +#: i2p2www/pages/site/comparison/tor.html:69 +#: i2p2www/pages/site/comparison/tor.html:72 +msgid "Router" +msgstr "ルーター" + +#: i2p2www/pages/site/comparison/tor.html:67 +msgid "Onion Proxy" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:67 +msgid "I2PTunnel Client (more or less)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:68 +msgid "Onion Service" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:69 +msgid "Relay" +msgstr "リレー" + +#: i2p2www/pages/site/comparison/tor.html:70 +msgid "Rendezvous Point" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:70 +msgid "somewhat like Inbound Gateway + Outbound Endpoint" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:71 +msgid "Router Descriptor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:71 +msgid "RouterInfo" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:72 +msgid "Server" +msgstr "サーバー" + +#: i2p2www/pages/site/comparison/tor.html:75 +msgid "Benefits of Tor over I2P" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:78 +msgid "" +"Much bigger user base; much more visibility in the academic and hacker " +"communities; benefits from\n" +"formal studies of anonymity, resistance, and performance;\n" +"has a non-anonymous, visible, university-based leader" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:84 +msgid "Has already solved some scaling issues I2P has yet to address" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:85 +msgid "Has significant funding" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:86 +msgid "Has more developers, including several that are funded" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:88 +msgid "" +"More resistant to state-level blocking due to TLS transport layer and " +"bridges\n" +"(I2P has proposals for \"full restricted routes\" but these are not yet " +"implemented)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:93 +msgid "Big enough that it has had to adapt to blocking and DOS attempts" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:94 +msgid "Designed and optimized for exit traffic, with a large number of exit nodes" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:96 +msgid "" +"Better documentation, has formal papers and specifications,\n" +"better website, many more translations" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:101 +msgid "More efficient with memory usage" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:102 +msgid "Tor client nodes have very low bandwidth overhead" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:104 +msgid "" +"Centralized control reduces the complexity at each\n" +"node and can efficiently address Sybil attacks" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:110 +msgid "" +"A core of high capacity nodes provides higher\n" +"throughput and lower latency" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:115 +msgid "C, not Java (ewww)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:118 +msgid "Benefits of I2P over Tor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:120 +msgid "" +"Designed and optimized for hidden services, which are much faster than in" +" Tor" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:121 +msgid "Fully distributed and self organizing" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:123 +msgid "" +"Peers are selected by continuously profiling and ranking performance,\n" +"rather than trusting claimed capacity" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:129 +msgid "" +"Floodfill peers (\"directory servers\") are varying and untrusted,\n" +"rather than hardcoded" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:134 +msgid "Small enough that it hasn't been blocked or DOSed much, or at all" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:135 +msgid "Peer-to-peer friendly" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:136 +msgid "Packet switched instead of circuit switched" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:139 +msgid "" +"implicit transparent load balancing of messages \n" +"across multiple peers, rather than a single path" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:145 +msgid "" +"resilience vs. failures by running multiple \n" +"tunnels in parallel, plus rotating tunnels" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:151 +msgid "" +"scale each client's connections at O(1) instead \n" +"of O(N) (Alice has e.g. 2 inbound tunnels that are \n" +"used by all of the peers Alice is talking with, \n" +"rather than a circuit for each)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:161 +msgid "" +"Unidirectional tunnels instead of bidirectional\n" +"circuits, doubling the number of nodes a peer has to\n" +"compromise to get the same information." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:166 +#, python-format +msgid "Counter-arguments and further discussion here." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:171 +msgid "" +"Protection against detecting client activity, even\n" +"when an attacker is participating in the tunnel, as\n" +"tunnels are used for more than simply passing end \n" +"to end messages (e.g. netDb, tunnel management, \n" +"tunnel testing)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:180 +msgid "" +"Tunnels in I2P are short lived, decreasing the number\n" +"of samples that an attacker can use to mount an \n" +"active attack with, unlike circuits in Tor, which are\n" +"typically long lived." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:188 +msgid "" +"I2P APIs are designed specifically for anonymity and\n" +"security, while SOCKS is designed for functionality." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:193 +msgid "Essentially all peers participate in routing for others" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:195 +msgid "" +"The bandwidth overhead of being a full peer is low, \n" +"while in Tor, while client nodes don't require much\n" +"bandwidth, they don't fully participate in the mixnet." +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:201 +msgid "Integrated automatic update mechanism" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:202 +msgid "Both TCP and UDP transports" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:203 +msgid "Java, not C (ewww)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:206 +msgid "Other potential benefits of I2P but not yet implemented" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:207 +msgid "...and may never be implemented, so don't count on them!" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:210 +msgid "" +"Defense vs. message count analysis by garlic wrapping \n" +"multiple messages" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:216 +msgid "" +"Defense vs. long term intersection by adding delays \n" +"at various hops (where the delays are not discernible\n" +"by other hops)" +msgstr "" + +#: i2p2www/pages/site/comparison/tor.html:223 +msgid "" +"Various mixing strategies at the tunnel level (e.g.\n" +"create a tunnel that will handle 500 messages / minute,\n" +"where the endpoint will inject dummy messages if there\n" +"are insufficient messages, etc)" +msgstr "" + diff --git a/i2p2www/translations/sk/LC_MESSAGES/about.po b/i2p2www/translations/sk/LC_MESSAGES/about.po new file mode 100644 index 00000000..2f2e9afa --- /dev/null +++ b/i2p2www/translations/sk/LC_MESSAGES/about.po @@ -0,0 +1,2280 @@ +# Slovak translations for I2P. +# Copyright (C) 2019 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# ondy, 2016 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2019-12-04 15:24+0000\n" +"PO-Revision-Date: 2019-12-05 14:51+0000\n" +"Last-Translator: Ivan Pleva\n" +"Language-Team: Slovak (http://www.transifex.com/otf/I2P/language/sk/)\n" +"Plural-Forms: nplurals=4; plural=(n % 1 == 0 && n == 1 ? 0 : n % 1 == 0 " +"&& n >= 2 && n <= 4 ? 1 : n % 1 != 0 ? 2: 3)\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/about/alternative-clients.html:2 +#: i2p2www/pages/site/about/alternative-clients.html:4 +msgid "Alternative I2P clients" +msgstr "" + +#: i2p2www/pages/site/about/alternative-clients.html:5 +msgid "" +"The main I2P client implementation uses Java. If for some \n" +"reason you can't use Java on your device, there are alternative " +"implementations\n" +"developed by community members." +msgstr "" + +#: i2p2www/pages/site/about/alternative-clients.html:12 +#, python-format +msgid "" +"i2pd is a I2P client implementation in C++.\n" +"As of early 2016, i2pd is became stable enough to be used in \n" +"production, and since summer 2016 it fully implements all I2P APIs." +msgstr "" + +#: i2p2www/pages/site/about/alternative-clients.html:19 +#, python-format +msgid "" +"Kovri is active i2pd fork developed for Monero " +"cryptocurrency." +msgstr "" + +#: i2p2www/pages/site/about/alternative-clients.html:24 +#, python-format +msgid "" +"Go-I2P is I2P client developed using the\n" +"Go programming language. The project is in " +"early development." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:2 +msgid "Web Browser Configuration" +msgstr "Konfigurácia prehliadača" + +#: i2p2www/pages/site/about/browser-config.html:5 +msgid "" +"Your web browser will need to be configured in order to browse eepsites " +"and to\n" +"utilize the outproxies available within I2P. Below are walkthroughs for " +"some of\n" +"the most popular browsers." +msgstr "" +"Tvoj prehliadač musí byť nakonfigurovaný pre prehliadanie stránok i2p " +"(eepsites) a\n" +"pre využitie outproxy dostupných v I2P. Nižšie sa nachádza postup pre " +"niektoré\n" +"populárne prehliadače." + +#: i2p2www/pages/site/about/browser-config.html:11 +msgid "Firefox Profile for Windows" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:12 +#, python-format +msgid "" +"If you are using Windows, the recommended way of accessing I2P is using " +"the \n" +"Firefox profile." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:16 +msgid "" +"If you do not wish to use that profile or are not on Windows, you need to" +" \n" +"configure your browser yourself. Read below on how to that." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:21 +msgid "How to configure your browser" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:27 +#: i2p2www/pages/site/about/browser-config.html:104 +msgid "Outproxy Terms Of Service" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:32 +msgid "Internet Explorer 8 or Chrome" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:33 +msgid "" +"In the tools menu select the \"Internet Options\" line to open the " +"settings. In the\n" +"settings window choose the connections tab and click on LAN settings for " +"the\n" +"proxy port configuration." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:38 +msgid "IE Internet Options" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:39 +msgid "" +"Now set the checkmark at \"use a proxy server for your LAN\" and at the " +"\"Bypass\n" +"proxy server for local addresses\". With a click on Advanced-button you " +"open the\n" +"window to open the ports. Enter the values like on the picture, IP " +"127.0.0.1\n" +"and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save " +"the\n" +"settings and your browser is set to use the I2P proxy.\n" +"Note/Privacy tip: Set the FTP proxy to the same settings as the " +"HTTP proxy." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:47 +msgid "IE Proxy Settings" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:51 +msgid "Instructions for Firefox 57 and above:" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:52 +msgid "" +"From the Menu button in the top right, select Preferences.\n" +"Scroll down until you see the Network Proxy section, as shown in" +" the\n" +"screenshot below. Click on Settings" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:58 +msgid "Firefox57 Network Options" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:59 +msgid "" +"In the Connection Settings pop-up, select Manual proxy\n" +" configuration. Set both the HTTP and SSL Proxy to address\n" +"127.0.0.1 with port 4444 as shown in the " +"following\n" +"screenshot." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:66 +msgid "" +"Firefox57\n" +"Connection Settings" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:67 +msgid "Firefox57 Connection Settings" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:70 +msgid "" +"From the Tools menu, select Options to bring up the Firefox settings " +"panel.\n" +"Click the icon labelled Advanced, then click on the " +"Network\n" +"tab. In the Connections section, click on the Settings button. " +"You'll\n" +"see a Window like the following:" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:76 +msgid "Firefox Network Options" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:77 +msgid "" +"In the Connection Settings window, click the circle next to " +"Manual\n" +" proxy configuration, then enter 127.0.0.1, port 4444 in the HTTP" +" Proxy\n" +"field. Enter 127.0.0.1, port 4445 in the SSL Proxy field.\n" +"Be sure to enter localhost and 127.0.0.1 into the \"No Proxy for\" box.\n" +"Note/Privacy tip: Set the FTP proxy to the same settings as the " +"HTTP proxy." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:85 +msgid "Firefox Proxy Settings" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:90 +msgid "" +"From the Settings menu, select Configure Konqueror. In " +"the\n" +"Web Browsing group on the left side, select Proxy, then select the option" +" \"Use manually specified proxy\n" +"configuration\" on the right." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:95 +msgid "Konqueror Proxy Options" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:96 +msgid "" +"Enter 127.0.0.1 and port 4444 into the HTTP box. Enter 127.0.0.1 and port" +" 4445 into\n" +"HTTPS box. Enter 127.0.0.1,localhost into the Exceptions " +"box. Click Apply then OK\n" +"to close the configuration window.\n" +"Note/Privacy tip: Set the FTP proxy to the same settings as the " +"HTTP proxy." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:105 +msgid "" +"Remember: I2P was not designed for creating proxies to the outer " +"Internet.\n" +"Instead, it is meant to be used as an internal network." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:109 +msgid "" +"

The I2P project itself does not run any proxies to the " +"Internet. \n" +"The only outproxy is a service from the privacy solutions project. \n" +"Consider donating to them for a continued stable service. Higher " +"bandwidth will \n" +"increase with the founding of the organization. Maybe more outproxies " +"too.

\n" +"http://privacysolutions.no" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:117 +#, python-format +msgid "" +"By default, I2P comes with two outproxies configured: " +"%(http)s \n" +"and %(https)s. Even the domain names are different, it's the" +" same outproxy you hit.\n" +"(multi-homed/keyed for better performance)" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:122 +msgid "" +"Filtering is active on these outproxies (for example, mibbit and torrent\n" +"tracker access is blocked). Eepsites\n" +"that are accessible via .i2p addresses are also not allowed via the " +"outproxies.\n" +"As a convenience, the outproxy blocks ad servers." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:128 +msgid "" +"Tor is good application to use" +" as an\n" +"outproxy to the Internet." +msgstr "" + +#: i2p2www/pages/site/about/glossary.html:2 +msgid "Glossary" +msgstr "" + +#: i2p2www/pages/site/about/glossary.html:4 +msgid "" +"This page lists often-used terminology when discussing I2P and " +"cryptography." +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:2 +msgid "Hall Of Fame" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:7 +msgid "" +"I2P is a project made completely by spare time enthusiasts. But a big " +"project like\n" +"I2P is not made from software alone, several servers, domain " +"registrations, and coffees need to\n" +"be paid to get a great result. People all over the world donated to I2P " +"reach the state it is in\n" +"currently. Here we do track those who gave us a name to be published in a" +" I2P hall of fame." +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:12 +msgid "Big thanks go to the following people who have donated to I2P!" +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:13 +#, python-format +msgid "" +"If you have made a donation, please send an email to echelon\n" +"with your name or nick (and optionally homepage) so we can list you here." +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:18 +msgid "" +"The unsorted list of I2P donors in 15 years of I2P history, starting " +"March 2004 til March 2019." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:2 +msgid "Intro" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:4 +msgid "The Invisible Internet Project" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:5 +#, python-format +msgid "" +"I2P is an anonymous network, exposing a simple layer that applications " +"can \n" +"use to anonymously and securely send messages to each other. The network " +"itself is \n" +"strictly message based (a la IP), but there is a \n" +"library available to allow reliable streaming communication on top of it " +"(a la \n" +"TCP). \n" +"All communication is end to end encrypted (in total there are four layers" +" of \n" +"encryption used when sending a message), and even the end points " +"(\"destinations\") \n" +"are cryptographic identifiers (essentially a pair of public keys)." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:18 +msgid "How does it work?" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:20 +#, python-format +msgid "" +"To anonymize the messages sent, each client application has their I2P " +"\"router\"\n" +"build a few inbound and outbound \"tunnels\" - a \n" +"sequence of peers that pass messages in one direction (to and from the " +"client, \n" +"respectively). In turn, when a client wants to send a message to another" +" client, \n" +"the client passes that message out one of their outbound tunnels " +"targeting one of the \n" +"other client's inbound tunnels, eventually reaching the destination. " +"Every \n" +"participant in the network chooses the length of these tunnels, and in " +"doing so, \n" +"makes a tradeoff between anonymity, latency, and throughput according to " +"their \n" +"own needs. The result is that the number of peers relaying each end to " +"end \n" +"message is the absolute minimum necessary to meet both the sender's and " +"the \n" +"receiver's threat model." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:34 +#, python-format +msgid "" +"The first time a client wants to contact another client, they make a " +"query \n" +"against the fully distributed \"network \n" +"database\" - a custom structured \n" +"distributed hash table (DHT) based off the \n" +"Kademlia algorithm. This is done \n" +"to find the other client's inbound tunnels efficiently, but subsequent " +"messages \n" +"between them usually includes that data so no further network database " +"lookups \n" +"are required." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:47 +#, python-format +msgid "More details about how I2P works are available." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:51 +msgid "What can you do with it?" +msgstr "" + +#: i2p2www/pages/site/about/intro.html:53 +#, python-format +msgid "" +"Within the I2P network, applications are not restricted in how they can \n" +"communicate - those that typically use UDP can make use of the base I2P \n" +"functionality, and those that typically use TCP can use the TCP-like " +"streaming\n" +"library. We have a generic TCP/I2P bridge application \n" +"(\"I2PTunnel\") that enables people to " +"forward TCP streams\n" +"into the I2P network as well as to receive streams out of the network and" +" \n" +"forward them towards a specific TCP/IP address." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:63 +#, python-format +msgid "" +"I2PTunnel is currently used to let people run their own anonymous website" +" \n" +"(\"eepsite\") by running a normal webserver and pointing an I2PTunnel " +"'server' \n" +"at it, which people can access anonymously over I2P with a normal web " +"browser \n" +"by running an I2PTunnel HTTP proxy (\"eepproxy\"). In addition, we use " +"the same \n" +"technique to run an anonymous IRC network (where the IRC server is hosted" +" \n" +"anonymously, and standard IRC clients use an I2PTunnel to contact it). " +"There \n" +"are other application development efforts going on as well, such as one " +"to \n" +"build an optimized swarming file transfer application (a la \n" +"BitTorrent), a \n" +"distributed data store (a la Freenet / \n" +"MNet), and a blogging system (a fully \n" +"distributed LiveJournal), but those are \n" +"not ready for use yet." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:82 +#, python-format +msgid "" +"I2P is not inherently an \"outproxy\" network - the client you send a " +"message \n" +"to is the cryptographic identifier, not some IP address, so the message " +"must \n" +"be addressed to someone running I2P. However, it is possible for that " +"client\n" +"to be an outproxy, allowing you to anonymously make use of their Internet" +" \n" +"connection. To demonstrate this, the \"eepproxy\" will accept normal " +"non-I2P \n" +"URLs (e.g. \"http://www.i2p.net\") and forward them to a specific " +"destination\n" +"that runs a squid HTTP proxy, allowing \n" +"simple anonymous browsing of the normal web. Simple outproxies like that" +" are \n" +"not viable in the long run for several reasons (including the cost of " +"running \n" +"one as well as the anonymity and security issues they introduce), but in" +" \n" +"certain circumstances the technique could be appropriate." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:96 +#, python-format +msgid "" +"The I2P development team is an open group, " +"welcome to all \n" +"who are interested in getting involved, and" +" all of \n" +"the code is open source. The core I2P SDK " +"and the \n" +"current router implementation is done in Java (currently working with " +"both \n" +"sun and kaffe, gcj support planned for later), and there is a \n" +"simple socket based API for accessing the network" +" from \n" +"other languages (with a C library available, and both Python and Perl in" +" \n" +"development). The network is actively being developed and has not yet " +"reached \n" +"the 1.0 release, but the current roadmap " +"describes \n" +"our schedule." +msgstr "" + +#: i2p2www/pages/site/about/media.html:2 +msgid "Presentations on I2P" +msgstr "" + +#: i2p2www/pages/site/about/media.html:5 +#, python-format +msgid "" +"Following are links to presentations, videos, and tutorials about I2P. " +"Links to research papers on I2P are available here." +msgstr "" + +#: i2p2www/pages/site/about/media.html:8 +#, python-format +msgid "To request an addition to this page, please send to %(email)s." +msgstr "" + +#: i2p2www/pages/site/about/media.html:11 +msgid "" +"\n" +"Newest links are at the bottom of each section." +msgstr "" + +#: i2p2www/pages/site/about/media.html:16 +msgid "Presentations" +msgstr "" + +#: i2p2www/pages/site/about/media.html:19 +#, python-format +msgid "" +"IIP Presentation at CodeCon\n" +"MP3 audio\n" +"transcript\n" +"Lance James (0x90), February 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:27 +#, python-format +msgid "" +"IIP Presentation at ToorCon\n" +"MP3 audio\n" +"slides\n" +"Lance James (0x90), September 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:35 +#, python-format +msgid "" +"To Be or I2P\n" +"(Youtube Video)\n" +"An introduction into anonymous communication with I2P.\n" +"To Be or I2P (PDF presentation),\n" +"Jens Kubieziel, 24C3 Berlin, December 28, 2007." +msgstr "" + +#: i2p2www/pages/site/about/media.html:44 +#, python-format +msgid "" +"Video of I2P talk at Chemnitz Linux Tag,\n" +"Lars Schimmer,\n" +"March 14-15, 2009" +msgstr "" + +#: i2p2www/pages/site/about/media.html:50 +#, python-format +msgid "" +"HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of" +" Adrian Hong's talk\n" +"\"Hackers for Human Rights\".\n" +"MP3 audio" +msgstr "" + +#: i2p2www/pages/site/about/media.html:56 +#, python-format +msgid "" +"Into the I2P Darknet: Welcome to Cipherspace\n" +"Adrian Crenshaw. Schmoocon Firetalk, January 2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:61 +#, python-format +msgid "" +"Using techhnology to advance liberty\n" +"(Youtube Video)\n" +"Eric Johnson.\n" +"Agora I/O Unconference, March 27," +" 2011.\n" +"I2P covered from 10:00 to 20:00 in the video." +msgstr "" + +#: i2p2www/pages/site/about/media.html:69 +#, python-format +msgid "" +"Common Darknet Weaknesses\n" +"(Youtube Video)\n" +"Adrian Crenshaw, AIDE, July " +"11-15, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:75 +#, python-format +msgid "" +"I2P / Tor Workshop Notes\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:80 +#, python-format +msgid "" +"Cipherspaces/Darknets: An Overview Of Attack " +"Strategies -\n" +"DEF CON Live version (Youtube Video),\n" +"\"Studio\" version (Youtube Video),\n" +"Slides (ppt)\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:90 +msgid "" +"Modern cipherspace ecosystems, 0x375 " +"0x06 (Thessaloniki Tech Talk Sessions), November 4, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:94 +#, python-format +msgid "" +"I2P - The Anonymous Network\n" +"(Youtube Video)\n" +"Blair Dick, University of Abertay, Dundee Ethical Hacking Society, " +"January 25, 2012." +msgstr "" + +#: i2p2www/pages/site/about/media.html:100 +#, python-format +msgid "" +"I2PCon 2015\n" +"Toronto, August 15-16, 2015" +msgstr "" + +#: i2p2www/pages/site/about/media.html:105 +#, python-format +msgid "" +"I2P - Still alive! (pdf)\n" +"(video)\n" +"echelon, 32C3 (You Broke the Internet Assembly), Hamburg, December 28, " +"2015" +msgstr "" + +#: i2p2www/pages/site/about/media.html:112 +#, python-format +msgid "" +"Replacing Weary Crypto: Upgrading the I2P network with stronger " +"primitives\n" +"(pdf)\n" +"(odp)\n" +"str4d, Real World Crypto, Stanford, January 8, 2016" +msgstr "" + +#: i2p2www/pages/site/about/media.html:120 +#, python-format +msgid "" +"Onions and Garlic: the protocols of I2P\n" +"(pdf)\n" +"(odp)\n" +"str4d, COMPSCI 460: Computer Networking, University of Wisconsin " +"Whitewater, February 17, 2016" +msgstr "" + +#: i2p2www/pages/site/about/media.html:128 +#, python-format +msgid "" +"The Invisible Internet Project - An overview and guide to the technology\n" +"(mp4)\n" +"(webm)\n" +"Andrew Savchenko (bircoph), FOSDEM, Brussel, February 4, 2018" +msgstr "" + +#: i2p2www/pages/site/about/media.html:139 +msgid "Tutorials" +msgstr "" + +#: i2p2www/pages/site/about/media.html:142 +#, python-format +msgid "" +"I2P Windows Tutorial\n" +"(Youtube Video)\n" +"This guide will show you how to install I2P in Windows XP.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:149 +#, python-format +msgid "" +"I2P Debian Tutorial\n" +"(Youtube Video)\n" +"This will guide you through how to install I2P on a Debian Linux System.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:156 +#, python-format +msgid "" +"How to set up anonymous site in I2P\n" +"(Youtube Video)\n" +"How to set up an anonymous web site in I2P.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:163 +#, python-format +msgid "" +"I2P Tutorial Mac OS X\n" +"(Youtube Video)\n" +"A tutorial on how to run i2p on Mac OS X and how to connect to " +"irc.telecomix.i2p.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:170 +#, python-format +msgid "" +"Felix Atari explains the basic principles of I2P" +"\n" +"(Youtube Video)\n" +"Agent Felix Atari of the Telecomix Crypto Munitions Bureau.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:177 +#, python-format +msgid "" +"How to get onto I2P, the anonymous P2P Darknet " +"(Windows Install)\n" +"(Youtube Video)\n" +"This tutorial shows how to install and configure software needed to " +"access I2P." +msgstr "" + +#: i2p2www/pages/site/about/media.html:183 +#, python-format +msgid "" +"How to connect to I2P\n" +"(Youtube Video)\n" +"How to install I2P on Ubuntu." +msgstr "" + +#: i2p2www/pages/site/about/media.html:189 +#, python-format +msgid "" +"Installing the I2P darknet software in Linux\n" +"(Video)\n" +"Adrian Crenshaw.\n" +"January 2011" +msgstr "" + +#: i2p2www/pages/site/about/media.html:196 +#, python-format +msgid "" +"Short garlic routing animation\n" +"(Youtube Video)\n" +"Adrian Crenshaw.\n" +msgstr "" + +#: i2p2www/pages/site/about/media.html:204 +msgid "Articles and Interviews" +msgstr "" + +#: i2p2www/pages/site/about/media.html:207 +#, python-format +msgid "" +"Lance James (0x90) Interviewed by DistributedCity\n" +"Part 1\n" +"Part 2\n" +"July 26, 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:215 +#, python-format +msgid "" +"Lance James (0x90) Interviewed by El País\n" +"(original in Spanish)\n" +"English translation\n" +"October 31, 2002." +msgstr "" + +#: i2p2www/pages/site/about/media.html:222 +#, python-format +msgid "" +"2003 Business Week article referencing " +"invisiblenet\n" +"September 14, 2003." +msgstr "" + +#: i2p2www/pages/site/about/media.html:227 +#, python-format +msgid "" +"Netzwelt.de article about being anonymous in the " +"Internet\n" +"(German)\n" +"November 2007." +msgstr "" + +#: i2p2www/pages/site/about/media.html:233 +#, python-format +msgid "" +"zzz interviewed by gulli.com\n" +"March 2009\n" +"German translation" +msgstr "" + +#: i2p2www/pages/site/about/media.html:240 +#, python-format +msgid "" +"zzz interviewed on the InfoSec Daily Podcast Ep. 454 " +"(mp3)\n" +"August 18, 2011\n" +"(link dead, seeded inside I2P at postman's" +" tracker)" +msgstr "" + +#: i2p2www/pages/site/about/media.html:246 +#, python-format +msgid "" +"I2P - Anonymity for the Masses,\n" +"Jonathan Cox,\n" +"November 11, 2011." +msgstr "" + +#: i2p2www/pages/site/about/media.html:252 +#, python-format +msgid "" +"zzz and Lance James interviewed on the InfoSec Daily " +"Podcast Ep. 596 (mp3)\n" +"February 16, 2012\n" +"(link dead, seeded inside I2P at postman's" +" tracker)" +msgstr "" + +#: i2p2www/pages/site/about/media.html:258 +#, python-format +msgid "" +"Jeff and Str4d interviewed on the Brakeing Down " +"Security Podcast Ep. 2015-010 (mp3)\n" +"Part 1, February 28, 2015" +msgstr "" + +#: i2p2www/pages/site/about/media.html:263 +#, python-format +msgid "" +"Jeff and Str4d interviewed on the Brakeing Down " +"Security Podcast Ep. 2015-011 (mp3)\n" +"Part 2, March 6, 2015" +msgstr "" + +#: i2p2www/pages/site/about/media.html:268 +#, python-format +msgid "" +"Fireside With Lei - Episode 18: Lance James. " +"Success, Failures, Grief and Buddhism.\n" +"(archive.org)\n" +"(mp3)\n" +"Robert Lei, December 31, 2018" +msgstr "" + +#: i2p2www/pages/site/about/media.html:277 +#, python-format +msgid "" +"Articles by I2P contributor Masayuki Hatta on " +"Medium.com\n" +"2019\n" +msgstr "" + +#: i2p2www/pages/site/about/media.html:282 +#, python-format +msgid "" +"Enabling both .onion and .i2p routing with Proxy " +"Auto-Configuration\n" +"Daniel Aleksandersen, February 7 2019" +msgstr "" + +#: i2p2www/pages/site/about/media.html:289 +msgid "Other" +msgstr "Ďalší" + +#: i2p2www/pages/site/about/media.html:292 +msgid "" +"I2P mentioned in Netflix's \"House of Cards\" Season 2 Episode 2,\n" +"February 14, 2014" +msgstr "" + +#: i2p2www/pages/site/about/media.html:297 +#, python-format +msgid "" +"A curated list by I2P contributor meeh of I2P " +"implementations, libraries, resources, projects, and shiny things\n" +"2019" +msgstr "" + +#: i2p2www/pages/site/about/team.html:2 +msgid "I2P Project Members" +msgstr "" + +#: i2p2www/pages/site/about/team.html:5 +#, python-format +msgid "" +"We are a small group of people spread around several continents, working " +"to\n" +"advance different aspects of the project and discussing the design of the" +"\n" +"network.\n" +"Get involved!" +msgstr "" + +#: i2p2www/pages/site/about/team.html:14 +msgid "Admin" +msgstr "Administrátor" + +#: i2p2www/pages/site/about/team.html:15 +msgid "Project Manager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:17 +msgid "point of contact of last resort" +msgstr "" + +#: i2p2www/pages/site/about/team.html:20 +msgid "Donations treasurer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:22 +msgid "manage donations" +msgstr "" + +#: i2p2www/pages/site/about/team.html:25 +msgid "PR manager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:27 +msgid "press contact, manages public relations and affairs" +msgstr "" + +#: i2p2www/pages/site/about/team.html:30 +msgid "Compensation manager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:32 +msgid "Compensation management" +msgstr "" + +#: i2p2www/pages/site/about/team.html:35 i2p2www/pages/site/about/team.html:40 +msgid "Assistant PR manager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:37 +msgid "Public speaking, public relations assistance" +msgstr "" + +#: i2p2www/pages/site/about/team.html:42 +msgid "Public relations assistance" +msgstr "" + +#: i2p2www/pages/site/about/team.html:45 +#, python-format +msgid "Forum admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:47 +msgid "manage the public user forum" +msgstr "" + +#: i2p2www/pages/site/about/team.html:50 +msgid "Download mirrors admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:52 +msgid "manage the mirrors for the download files" +msgstr "" + +#: i2p2www/pages/site/about/team.html:55 +msgid "Website mirrors admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:56 i2p2www/pages/site/about/team.html:91 +#: i2p2www/pages/site/about/team.html:106 +#: i2p2www/pages/site/about/team.html:126 +#: i2p2www/pages/site/about/team.html:131 +#: i2p2www/pages/site/about/team.html:171 +#: i2p2www/pages/site/about/team.html:193 +#: i2p2www/pages/site/about/team.html:203 +#: i2p2www/pages/site/about/team.html:218 +#: i2p2www/pages/site/about/team.html:251 +msgid "vacant" +msgstr "" + +#: i2p2www/pages/site/about/team.html:57 +msgid "manage the mirrors for the website" +msgstr "" + +#: i2p2www/pages/site/about/team.html:60 +#, python-format +msgid "Monotone guru" +msgstr "" + +#: i2p2www/pages/site/about/team.html:62 +msgid "manage the public monotone repositories" +msgstr "" + +#: i2p2www/pages/site/about/team.html:65 +msgid "Packager; Linux" +msgstr "" + +#: i2p2www/pages/site/about/team.html:67 +msgid "Linux (Debian/Ubuntu) distribution packager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:70 +msgid "Packager; Windows" +msgstr "" + +#: i2p2www/pages/site/about/team.html:72 +msgid "Windows installer packager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:75 +msgid "Packager; OSX" +msgstr "" + +#: i2p2www/pages/site/about/team.html:77 +msgid "OSX installer packager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:80 +msgid "Release Manager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:82 +msgid "Builds and signs the releases" +msgstr "" + +#: i2p2www/pages/site/about/team.html:85 +msgid "Release Manager Alternates" +msgstr "" + +#: i2p2www/pages/site/about/team.html:87 +msgid "Backup release managers" +msgstr "" + +#: i2p2www/pages/site/about/team.html:90 +msgid "Tails Maintainer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:92 +msgid "Maintain the I2P package in Tails" +msgstr "" + +#: i2p2www/pages/site/about/team.html:95 +msgid "CI admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:97 +msgid "Maintain the Continuous Integration infrastructure" +msgstr "" + +#: i2p2www/pages/site/about/team.html:100 +msgid "Reseed admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:102 +msgid "Monitors, advises and recruits reseed hosts" +msgstr "" + +#: i2p2www/pages/site/about/team.html:105 +msgid "Security expert" +msgstr "" + +#: i2p2www/pages/site/about/team.html:107 +msgid "threat model / crypto expert" +msgstr "" + +#: i2p2www/pages/site/about/team.html:112 +msgid "Manage the project bug tracker" +msgstr "" + +#: i2p2www/pages/site/about/team.html:117 +#: i2p2www/pages/site/about/team.html:137 +msgid "manage the public project webservers" +msgstr "" + +#: i2p2www/pages/site/about/team.html:120 +msgid "Translation admins" +msgstr "" + +#: i2p2www/pages/site/about/team.html:125 +msgid "User Advocate" +msgstr "" + +#: i2p2www/pages/site/about/team.html:127 +msgid "gather, prioritize, advocate for user needs" +msgstr "" + +#: i2p2www/pages/site/about/team.html:130 +msgid "Web Designer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:132 +msgid "manage the public project website content design" +msgstr "" + +#: i2p2www/pages/site/about/team.html:135 +#, python-format +msgid "Webserver admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:140 +#, python-format +msgid "Website admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:142 +msgid "manage the public project website content" +msgstr "" + +#: i2p2www/pages/site/about/team.html:145 +msgid "News Admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:147 +msgid "manage router console news feed" +msgstr "" + +#: i2p2www/pages/site/about/team.html:150 +msgid "Backup News Admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:152 +msgid "manage the backup news feed" +msgstr "" + +#: i2p2www/pages/site/about/team.html:170 +msgid "Director of passion" +msgstr "" + +#: i2p2www/pages/site/about/team.html:172 +msgid "community motivator" +msgstr "" + +#: i2p2www/pages/site/about/team.html:176 +msgid "Dev" +msgstr "" + +#: i2p2www/pages/site/about/team.html:177 +msgid "Core Lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:179 +msgid "lead dev for the SDK and router" +msgstr "" + +#: i2p2www/pages/site/about/team.html:182 +#, python-format +msgid "I2P mail lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:184 +msgid "organize and develop the i2p mail system" +msgstr "" + +#: i2p2www/pages/site/about/team.html:187 +#, python-format +msgid "I2P-Bote lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:189 +msgid "I2P-Bote plugin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:192 +#, python-format +msgid "I2Phex lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:194 +msgid "I2Phex Gnutella client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:197 +#, python-format +msgid "I2PSnark lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:199 +msgid "Maintains the integrated Bittorrent client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:202 +#, python-format +msgid "Syndie lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:204 +msgid "Syndie development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:207 +msgid "Susimail lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:209 +msgid "Susimail development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:212 +msgid "Android lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:214 +msgid "Android development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:217 +msgid "Console" +msgstr "Konzola" + +#: i2p2www/pages/site/about/team.html:219 +msgid "Router console HTML/CSS design" +msgstr "" + +#: i2p2www/pages/site/about/team.html:222 +msgid "SAM" +msgstr "" + +#: i2p2www/pages/site/about/team.html:224 +msgid "SAM maintainer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:227 +msgid "Translators" +msgstr "" + +#: i2p2www/pages/site/about/team.html:228 +msgid "many many people!" +msgstr "" + +#: i2p2www/pages/site/about/team.html:233 +msgid "Contributors" +msgstr "" + +#: i2p2www/pages/site/about/team.html:235 +msgid "fire2pe dev, console enhancements" +msgstr "" + +#: i2p2www/pages/site/about/team.html:239 +msgid "desktopgui, dijjer port" +msgstr "" + +#: i2p2www/pages/site/about/team.html:243 +msgid "Debian/Ubuntu Packager and PPA maintainer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:247 +msgid "Routerconsole backend and UI work, website revamp, unit tests work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:252 +msgid "Help needed on many fronts!" +msgstr "" + +#: i2p2www/pages/site/about/team.html:256 +msgid "Past contributors" +msgstr "" + +#: i2p2www/pages/site/about/team.html:258 +msgid "I2PTunnel development, ministreaming library" +msgstr "" + +#: i2p2www/pages/site/about/team.html:262 +msgid "Project lead, Syndie lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:266 +msgid "Project lead, Syndie lead, I2Phex, support guru" +msgstr "" + +#: i2p2www/pages/site/about/team.html:270 +msgid "iMule lead" +msgstr "" + +#: i2p2www/pages/site/about/team.html:274 +#: i2p2www/pages/site/about/team.html:278 +#: i2p2www/pages/site/about/team.html:282 +msgid "I2Phex work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:286 +msgid "Python SAM library, attack simulations" +msgstr "" + +#: i2p2www/pages/site/about/team.html:290 +msgid "i2pmail development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:294 +msgid "Syndie help" +msgstr "" + +#: i2p2www/pages/site/about/team.html:298 +msgid "i2p mail,susimail and susidns apps" +msgstr "" + +#: i2p2www/pages/site/about/team.html:302 +msgid "I2Phex (port of Phex to I2P)" +msgstr "" + +#: i2p2www/pages/site/about/team.html:306 +msgid "addressbook,i2p-bt,syndie client" +msgstr "" + +#: i2p2www/pages/site/about/team.html:310 +msgid "organize and develop the i2p-bt BitTorrent port" +msgstr "" + +#: i2p2www/pages/site/about/team.html:314 +msgid "addressbook, i2p-bt, syndie client development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:318 +msgid "encryption and signature routines, I2PIM" +msgstr "" + +#: i2p2www/pages/site/about/team.html:322 +msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)" +msgstr "" + +#: i2p2www/pages/site/about/team.html:326 +msgid "installer, systray, bogobot" +msgstr "" + +#: i2p2www/pages/site/about/team.html:330 +msgid "jbigi development, wiki migration, doc cleanup" +msgstr "" + +#: i2p2www/pages/site/about/team.html:334 +msgid "java debugging and client development on I2PTunnel and the router console" +msgstr "" + +#: i2p2www/pages/site/about/team.html:338 +msgid "SAM perl module" +msgstr "" + +#: i2p2www/pages/site/about/team.html:342 +msgid "i2psnark work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:346 +msgid "java cleanup" +msgstr "" + +#: i2p2www/pages/site/about/team.html:350 +msgid "docs. wiki migration" +msgstr "" + +#: i2p2www/pages/site/about/team.html:354 +msgid "translations into French" +msgstr "" + +#: i2p2www/pages/site/about/team.html:358 +msgid "C port of jcpuid" +msgstr "" + +#: i2p2www/pages/site/about/team.html:362 +msgid "C# SAM library, pants, fortuna integration" +msgstr "" + +#: i2p2www/pages/site/about/team.html:366 +msgid "libSAM" +msgstr "" + +#: i2p2www/pages/site/about/team.html:370 +#: i2p2www/pages/site/about/team.html:374 +msgid "i2p-bt tracker development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:378 +msgid "Console and website themes" +msgstr "" + +#: i2p2www/pages/site/about/team.html:408 +msgid "… and many others" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:6 +msgid "" +"I2PCon 2015 was the first event of its kind. It had two short-term goals." +"\n" +"First, to provide the general public with an event where knowledge about " +"privacy could be obtained.\n" +"Second, to further the I2P project and its community with technical " +"discussions\n" +"about cryptography, anonymity and I2P-centric topics." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:15 +msgid "" +"A a larger and more long-term goal of this event was to build a\n" +"commnutiy of privacy-conscious individuals. By connecting people who " +"recognize\n" +"the importance of privacy, we wanted to provide a forum where this " +"community can grow." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:23 +msgid "" +"The idea for this event was first spawned by our wonderful friends at\n" +"Toronto Crypto.\n" +"The venue was provided by Hacklab.to." +"\n" +"The marketing was spearheaded by @YrB1rd and Siew.\n" +"Without them this event would not have been possible." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:32 +msgid "Slides and Video" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:34 +msgid "Slides are also available as an in-I2P torrent." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:41 +msgid "Note: Video links will be posted as they become available." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:44 +msgid "" +"Note that in-I2P torrents may also be available on the clearnet due to " +"bridging by Vuze clients." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:50 +msgid "Licenses" +msgstr "Licencie" + +#: i2p2www/pages/site/about/i2pcon/2015.html:52 +msgid "All videos are by z3r0fox." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:56 +msgid "License" +msgstr "Licencia" + +#: i2p2www/pages/site/about/i2pcon/2015.html:60 +msgid "Slides by psi: Public domain." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:65 +msgid "Slides by str4d and zzz:" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:71 +msgid "Slides by others: Contact the author for license information." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:77 +msgid "Speakers" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:79 +msgid "" +"Colin Mahns has a strong interest in the use of anonymity and encryption " +"technology to help preserve human rights in the digital age." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:85 +msgid "" +"David Dagon is a postdoc researcher at Georgia Tech focused on botnets, " +"malware, network security, and DNS.\n" +"His interest in I2P is centered on preserving user privacy, autonomous " +"filtering, and anti-abuse." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:89 +#: i2p2www/pages/site/about/i2pcon/2015.html:105 +msgid "More info" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:92 +msgid "J is the head of Toronto Crypto." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:98 +msgid "" +"Lance James is the founder of the Invisibile IRC Project, the predecessor" +" to I2P, back in 2002.\n" +"He founded his own cyber threat intelligence company in 2003.\n" +"He's been focused on network security, malware research, and information " +"security ever since.\n" +"During 2011-2013, he was Director of Threat Intelligence for The " +"Vigilant, which was acquired by Deloitte in 2013.\n" +"He recently left Deloitte to do consulting through his company The James " +"Group." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:109 +msgid "Nicholas D. is a member of Hacklab Toronto." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:115 +msgid "" +"Nicholas Johnston is a Professor of Information Security in Sheridan " +"College's School of Applied Computing in the InfoSec Bachelor's degree " +"program.\n" +"His previous professional career was in digital forensics and " +"investigations.\n" +"He is also a contractor specializing in incident response.\n" +"His research areas include secure software development and data analytics." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:124 +msgid "Psi is an I2P developer." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:130 +msgid "Str4d is an I2P developer." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:136 +msgid "Zzz is an I2P developer." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:143 +msgid "Press" +msgstr "Tlač" + +#: i2p2www/pages/site/about/i2pcon/2015.html:146 +msgid "Toronto Star article on Nicholas Johnston's talk" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:152 +msgid "Day 1" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:155 +#: i2p2www/pages/site/about/i2pcon/2015.html:235 +msgid "Talk" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:156 +#: i2p2www/pages/site/about/i2pcon/2015.html:236 +msgid "Presenter" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:157 +#: i2p2www/pages/site/about/i2pcon/2015.html:237 +msgid "Video" +msgstr "Video" + +#: i2p2www/pages/site/about/i2pcon/2015.html:158 +#: i2p2www/pages/site/about/i2pcon/2015.html:238 +msgid "Slides" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:232 +msgid "Day 2" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/index.html:4 +msgid "" +"The first conference dedicated to I2P was held in Toronto on August " +"15-16, 2015.\n" +"See the link below for more information and links to slides and videos." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/index.html:9 +msgid "Past years" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:2 +msgid "Future Performance Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:3 +msgid "August 2010" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:7 +msgid "" +"There are a few major techniques that can be done to improve the " +"perceived\n" +"performance of I2P - some of the following are CPU related, others " +"bandwidth\n" +"related, and others still are protocol related. However, all of those\n" +"dimensions affect the latency, throughput, and perceived performance of " +"the\n" +"network, as they reduce contention for scarce resources. This list is of" +" course\n" +"not comprehensive, but it does cover the major ones that are seen." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:15 +#: i2p2www/pages/site/about/performance/index.html:106 +#, python-format +msgid "" +"For past performance improvements see the \n" +"Performance History." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:20 +msgid "Better peer profiling and selection" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:21 +#, python-format +msgid "" +"Probably one of the most important parts of getting faster performance " +"will\n" +"be improving how routers choose the peers that they build their tunnels " +"through\n" +"- making sure they don't use peers with slow links or ones with fast " +"links that\n" +"are overloaded, etc. In addition, we've got to make sure we don't expose" +"\n" +"ourselves to a Sybil attack\n" +"from a powerful adversary with lots of fast machines." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:30 +msgid "Network database tuning" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:31 +msgid "" +"We're going to want to be more efficient with the network database's " +"healing\n" +"and maintenance algorithms - rather than constantly explore the keyspace " +"for new\n" +"peers - causing a significant number of network messages and router load " +"- we\n" +"can slow down or even stop exploring until we detect that there's " +"something new\n" +"worth finding (e.g. decay the exploration rate based upon the last time " +"someone\n" +"gave us a reference to someone we had never heard of). We can also do " +"some\n" +"tuning on what we actually send - how many peers we bounce back (or even " +"if we\n" +"bounce back a reply), as well as how many concurrent searches we perform." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:42 +msgid "Session Tag Tuning and Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:43 +#, python-format +msgid "" +"The way the ElGamal/AES+SessionTag " +"algorithm\n" +"works is by managing a set of random one-time-use 32 byte arrays, and " +"expiring\n" +"them if they aren't used quickly enough. If we expire them too soon, " +"we're\n" +"forced to fall back on a full (expensive) ElGamal encryption, but if we " +"don't\n" +"expire them quickly enough, we've got to reduce their quantity so that we" +" don't\n" +"run out of memory (and if the recipient somehow gets corrupted and loses " +"some\n" +"tags, even more encryption failures may occur prior to detection). With " +"some\n" +"more active detection and feedback driven algorithms, we can safely and " +"more\n" +"efficiently tune the lifetime of the tags, replacing the ElGamal " +"encryption with\n" +"a trivial AES operation." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:55 +#, python-format +msgid "" +"Additional ideas for improving Session Tag delivery are described on the\n" +"ElGamal/AES+SessionTag page." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:61 +msgid "Migrate sessionTag to synchronized PRNG" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:62 +#, python-format +msgid "" +"Right now, our ElGamal/AES+SessionTag \n" +"algorithm works by tagging each encrypted message with a unique random \n" +"32 byte nonce (a \"session tag\"), identifying that message as being " +"encrypted \n" +"with the associated AES session's key. This prevents peers from " +"distinguishing \n" +"messages that are part of the same session, since each message has a " +"completely \n" +"new random tag. To accomplish this, every few messages bundle a whole \n" +"new set of session tags within the encrypted message itself, " +"transparently \n" +"delivering a way to identify future messages. We then have to keep track" +" \n" +"of what messages are successfully delivered so that we know what tags \n" +"we may use." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:74 +msgid "" +"This works fine and is fairly robust, however it is inefficient in terms" +" \n" +"of bandwidth usage, as it requires the delivery of these tags ahead of \n" +"time (and not all tags may be necessary, or some may be wasted, due to \n" +"their expiration). On average though, predelivering the session tag costs" +" \n" +"32 bytes per message (the size of a tag). As Taral suggested though, that" +" \n" +"size can be avoided by replacing the delivery of the tags with a " +"synchronized \n" +"PRNG - when a new session is established (through an ElGamal encrypted \n" +"block), both sides seed a PRNG for use and generate the session tags on \n" +"demand (with the recipient precalculating the next few possible values \n" +"to handle out of order delivery)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:87 +msgid "Longer lasting tunnels" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:88 +msgid "" +"The current default tunnel duration of 10 minutes is fairly arbitrary, " +"though\n" +"it \"feels okay\". Once we've got tunnel healing code and more effective" +" failure\n" +"detection, we'll be able to more safely vary those durations, reducing " +"the\n" +"network and CPU load (due to expensive tunnel creation messages)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:95 +msgid "" +"This appears to be an easy fix for high load on the big-bandwidth " +"routers, but\n" +"we should not resort to it until we've tuned the tunnel building " +"algorithms further.\n" +"However, the 10 minute tunnel lifetime is hardcoded in quite a few " +"places,\n" +"so substantial effort would be required to change the duration.\n" +"Also, it would be difficult to maintain backward compatibility with such " +"a change." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:102 +msgid "" +"Currently, since the network average tunnel build success rate is fairly " +"high,\n" +"there are no current plans to extend tunnel lifetime." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:108 +msgid "Adjust the timeouts" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:109 +msgid "" +"Yet another of the fairly arbitrary but \"okay feeling\" things we've got" +" are the\n" +"current timeouts for various activities. Why do we have a 60 second " +"\"peer\n" +"unreachable\" timeout? Why do we try sending through a different tunnel " +"that a\n" +"LeaseSet advertises after 10 seconds? Why are the network database " +"queries\n" +"bounded by 60 or 20 second limits? Why are destinations configured to " +"ask for a\n" +"new set of tunnels every 10 minutes? Why do we allow 60 seconds for a " +"peer to\n" +"reply to our request that they join a tunnel? Why do we consider a " +"tunnel that\n" +"doesn't pass our test within 60 seconds \"dead\"?" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:119 +msgid "" +"Each of those imponderables can be addressed with more adaptive code, as " +"well\n" +"as tunable parameters to allow for more appropriate tradeoffs between\n" +"bandwidth, latency, and CPU usage." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:125 +msgid "Full streaming protocol improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:128 +msgid "" +"Perhaps re-enable the interactive stream profile (the \n" +"current implementation only uses the bulk stream profile)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:134 +msgid "" +"Client level bandwidth limiting (in either or both directions on a " +"stream, \n" +"or possibly shared across multiple streams). This would be in addition to" +" \n" +"the router's overall bandwidth limiting, of course." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:141 +msgid "" +"Access control lists (only allowing streams to or from certain other " +"known \n" +"destinations)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:147 +msgid "" +"Web controls and monitoring the health of the various streams, as well \n" +"as the ability to explicitly close or throttle them." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:153 +#, python-format +msgid "" +"Additional ideas for improving the streaming library are described on the" +"\n" +"streaming library page." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:2 +msgid "Performance History" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:4 +#, python-format +msgid "" +"Notable performance improvements have been made using the techniques " +"below.\n" +"There is more to do, see the Performance " +"page\n" +"for current issues and thoughts." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:10 +msgid "Native math" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:11 +#: i2p2www/pages/site/about/performance/history.html:67 +#: i2p2www/pages/site/about/performance/history.html:82 +#: i2p2www/pages/site/about/performance/history.html:105 +#: i2p2www/pages/site/about/performance/history.html:133 +msgid "implemented" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:12 +#, python-format +msgid "" +"When I last profiled the I2P code, the vast majority of time was spent " +"within\n" +"one function: java.math.BigInteger's\n" +"modPow.\n" +"Rather than try to tune this method, we'll call out to\n" +"GNU MP - an insanely fast math library\n" +"(with tuned assembler for many architectures). (Editor: see\n" +"NativeBigInteger for faster public key " +"cryptography)" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:23 +msgid "" +"\n" +"ugha and duck are working on the C/JNI glue code, and the existing java " +"code\n" +"is already deployed with hooks for that whenever its ready. Preliminary " +"results\n" +"look fantastic - running the router with the native GMP modPow is " +"providing over\n" +"a 800% speedup in encryption performance, and the load was cut in " +"half. This\n" +"was just on one user's machine, and things are nowhere near ready for " +"packaging\n" +"and deployment, yet." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:32 +msgid "Garlic wrapping a \"reply\" LeaseSet" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:33 +msgid "implemented but needs tuning" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:34 +msgid "" +"This algorithm tweak will only be relevant for applications that want " +"their\n" +"peers to reply to them (though that includes everything that uses " +"I2PTunnel or\n" +"mihi's ministreaming lib):" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:39 +msgid "" +"Previously, when Alice sent Bob a message, when Bob replied he had to do " +"a\n" +"lookup in the network database - sending out a few requests to get " +"Alice's\n" +"current LeaseSet. If he already has Alice's current LeaseSet, he can " +"instead\n" +"just send his reply immediately - this is (part of) why it typically " +"takes a\n" +"little longer talking to someone the first time you connect, but " +"subsequent\n" +"communication is faster. Currently - for all clients - we wrap\n" +"the sender's current LeaseSet in the garlic that is delivered to the " +"recipient,\n" +"so that when they go to reply, they'll always have the LeaseSet " +"locally\n" +"stored - completely removing any need for a network database lookup on " +"replies.\n" +"This trades off a large portion of the sender's bandwidth for that faster" +" reply.\n" +"If we didn't do this very often,\n" +"overall network bandwidth usage would decrease, since the recipient " +"doesn't\n" +"have to do the network database lookup." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:54 +msgid "" +"For unpublished LeaseSets such as \"shared clients\", this is the only " +"way to\n" +"get the LeaseSet to Bob. Unfortunately this bundling every time adds\n" +"almost 100% overhead to a high-bandwidth connection, and much more to" +"\n" +"a connection with smaller messages." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:60 +msgid "" +"Changes scheduled for release 0.6.2 will bundle the LeaseSet only when\n" +"necessary, at the beginning of a connection or when the LeaseSet changes." +"\n" +"This will substantially reduce the total overhead of I2P messaging." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:66 +msgid "More efficient TCP rejection" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:68 +msgid "" +"At the moment, all TCP connections do all of their peer validation after\n" +"going through the full (expensive) Diffie-Hellman handshaking to " +"negotiate a\n" +"private session key. This means that if someone's clock is really wrong," +" or\n" +"their NAT/firewall/etc is improperly configured (or they're just running " +"an\n" +"incompatible version of the router), they're going to consistently " +"(though not\n" +"constantly, thanks to the banlist) cause a futile expensive cryptographic" +"\n" +"operation on all the peers they know about. While we will want to keep " +"some\n" +"verification/validation within the encryption boundary, we'll want to " +"update the\n" +"protocol to do some of it first, so that we can reject them cleanly\n" +"without wasting much CPU or other resources." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:81 +msgid "Adjust the tunnel testing" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:83 +msgid "" +"Rather than going with the fairly random scheme we have now, we should " +"use a\n" +"more context aware algorithm for testing tunnels. e.g. if we already " +"know its\n" +"passing valid data correctly, there's no need to test it, while if we " +"haven't\n" +"seen any data through it recently, perhaps its worthwhile to throw some " +"data its\n" +"way. This will reduce the tunnel contention due to excess messages, as " +"well as\n" +"improve the speed at which we detect - and address - failing tunnels." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:92 +msgid "Persistent Tunnel / Lease Selection" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:93 +msgid "" +"Outbound tunnel selection implemented in 0.6.1.30, inbound lease " +"selection \n" +"implemented in release 0.6.2." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:97 +msgid "" +"Selecting tunnels and leases at random for every message creates a large" +" \n" +"incidence of out-of-order delivery, which prevents the streaming lib from" +" \n" +"increasing its window size as much as it could. By persisting with the \n" +"same selections for a given connection, the transfer rate is much faster." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:104 +msgid "Compress some data structures" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:106 +msgid "" +"The I2NP messages and the data they contain is already defined in a " +"fairly\n" +"compact structure, though one attribute of the RouterInfo structure is " +"not -\n" +"\"options\" is a plain ASCII name = value mapping. Right now, we're " +"filling it\n" +"with those published statistics - around 3300 bytes per peer. Trivial to" +"\n" +"implement GZip compression would nearly cut that to 1/3 its size, and " +"when you\n" +"consider how often RouterInfo structures are passed across the network, " +"that's\n" +"significant savings - every time a router asks another router for a " +"networkDb\n" +"entry that the peer doesn't have, it sends back 3-10 RouterInfo of them." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:117 +msgid "Update the ministreaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:118 +msgid "replaced by full streaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:119 +msgid "" +"Currently mihi's ministreaming library has a fairly simple stream " +"negotiation\n" +"protocol - Alice sends Bob a SYN message, Bob replies with an ACK " +"message, then\n" +"Alice and Bob send each other some data, until one of them sends the " +"other a\n" +"CLOSE message. For long lasting connections (to an IRC server, for " +"instance),\n" +"that overhead is negligible, but for simple one-off request/response " +"situations\n" +"(an HTTP request/reply, for instance), that's more than twice as many " +"messages as\n" +"necessary. If, however, Alice piggybacked her first payload in with the " +"SYN\n" +"message, and Bob piggybacked his first reply with the ACK - and perhaps " +"also\n" +"included the CLOSE flag - transient streams such as HTTP requests could " +"be\n" +"reduced to a pair of messages, instead of the " +"SYN+ACK+request+response+CLOSE." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:132 +msgid "Implement full streaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:134 +msgid "" +"The ministreaming protocol takes advantage of a poor design decision in " +"the\n" +"I2P client protocol (I2CP) - the exposure of \"mode=GUARANTEED\", " +"allowing what\n" +"would otherwise be an unreliable, best-effort, message based protocol to " +"be used\n" +"for reliable, blocking operation (under the covers, its still all " +"unreliable and\n" +"message based, with the router providing delivery guarantees by garlic " +"wrapping\n" +"an \"ACK\" message in with the payload, so once the data gets to the " +"target, the\n" +"ACK message is forwarded back to us [through tunnels, of course])." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:143 +#, python-format +msgid "" +"As I've said, having\n" +"I2PTunnel (and the ministreaming lib) go this route was the best thing " +"that\n" +"could be done, but more efficient mechanisms are available. When we rip " +"out the\n" +"\"mode=GUARANTEED\" functionality, we're essentially leaving ourselves " +"with an\n" +"I2CP that looks like an anonymous IP layer, and as such, we'll be able to" +"\n" +"implement the streaming library to take advantage of the design " +"experiences of\n" +"the TCP layer - selective ACKs, congestion detection, nagle, etc." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:2 +msgid "Performance" +msgstr "Výkon" + +#: i2p2www/pages/site/about/performance/index.html:5 +msgid "" +"How does I2P work, why is it slow, and why does it not use my full " +"bandwidth?" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:7 +msgid "" +"Probably one of the most frequent things people ask is \"how fast is " +"I2P?\",\n" +"and no one seems to like the answer - \"it depends\". After trying out " +"I2P, the\n" +"next thing they ask is \"will it get faster?\", and the answer to that is" +" a most\n" +"emphatic yes." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:14 +msgid "" +"I2P is a full dynamic network. Each client is known to other nodes and " +"tests local known nodes for reachability and capacity.\n" +"Only reachable and capable nodes are saved to a local NetDB (This is " +"generally only a portion of the network, around 500-1000).\n" +"When I2P builds tunnels, it selects the best resource from this pool. For" +" example, a small subset of 20-50 nodes are only available to build " +"tunnels with.\n" +"Because testing happens every minute, the pool of used nodes changes " +"every minute.\n" +"Each I2P node knows a different part of the net, meaning that each router" +" has a different set of I2P nodes to be used for tunnels.\n" +"Even if two routers have the same subset of known nodes, the tests for " +"reachability and capacity will likely show different results, as the " +"other routers could be under load just as one router tests, but be free " +"if the second router tests." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:23 +msgid "" +"The above describes why each I2P node has different nodes to build " +"tunnels.\n" +"Because every I2P node has a different latency and bandwith, tunnels " +"(which are built via those nodes) have different latency and bandwidth " +"values.\n" +"And because every I2P node has different tunnels built, no two I2P nodes " +"have the same tunnel sets." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:29 +msgid "" +"A server/client is known as a \"destination\" and each destination has at" +" least one inbound and one outbound tunnel. The default is 3 hops per " +"tunnel.\n" +"This adds up to 12 hops (aka 12 different I2P nodes) for a full roundtrip" +" client-server-client." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:34 +msgid "" +"Each data package is sent through 6 other I2P nodes until it reaches the " +"server:" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:40 +msgid "and on way back 6 different I2P nodes:" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:47 +msgid "" +"As most traffic on I2P (www, torrent,...) needs ack packages until new " +"data is sent, it needs to wait until a ack package returns from the " +"server.\n" +"In the end: send data, wait for ack, send more data, wait for ack,..\n" +"As the RTT (RoundTripTime) adds up from the latency of each individual " +"I2P node and each connection on this roundtrip, it takes usually 1-3 " +"seconds until a ack package comes back to the client.\n" +"With some internals of TCP and I2P transport, a data package has a " +"limited size and cannot be as large as we want it to be.\n" +"Together these conditions set a limit of max bandwidth per tunnel of " +"20-50 kbyte/sec.\n" +"But if ONLY ONE hop in the tunnel has only 5 kb/sec bandwidth to spend, " +"the whole tunnel is limited to 5 kb/sec, independent of the \n" +"latency and other limitations." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:57 +msgid "" +"Due to encryption used and other setups in I2P (howto built up tunnels, " +"latency, ...) it is quite expensive in CPU time to build a tunnel. This " +"is \n" +"why a destination is only allowed to have a max of 6 IN and 6 OUT tunnels" +" to transport data. With a max of 50 kb/sec per tunnel, a destination " +"could \n" +"use roughly 300 kb/sec traffic combined ( in reality it could be more if " +"shorter tunnels are used with low or no anonymity available).\n" +"Used tunnels are discarded every 10 minutes and new ones are built up.\n" +"This change of tunnels (and sometimes clients that shutdown hard due to " +"usage of \"shut down at once\" or situations where there is power loss) " +"does \n" +"sometimes break tunnels and connections, as seen on the IRC2P Network in " +"loss of connection (ping timeout) or on when using eepget." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:66 +msgid "" +"With a limited set of destinations and a limited set of tunnels per " +"destination, one I2P node only uses a limited set of tunnels across other" +" I2P nodes.\n" +"For example, if an I2P node is \"hop1\" in the small example above, we " +"only see 1 participating tunnel originating from the client.\n" +"If we sum up the whole I2P network, only a rather limited number of " +"participating tunnels could be built with a limited amount of bandwidth " +"all together.\n" +"If one distributes these limited numbers across the number of I2P nodes, " +"there is only a fraction of available bandwidth/capacity available for " +"use." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:73 +msgid "" +"To remain anonymous one router should not be used by the whole network " +"for building tunnels.\n" +"If one router does act as a tunnel router for ALL I2P nodes, it becomes a" +" very real central point of failure as well as a central point to grab " +"IPs and data from the clients. This is not good.\n" +"I2P attempts to spread the load across a lot of I2P nodes because of this" +" reason." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:79 +msgid "" +"Another point is the full mesh network. Each connection hop-hop utilizes " +"one TCP or UDP connection on the I2P nodes. With 1000 connections, one " +"sees \n" +"1000 TCP connections. That is quite a lot and some home and small office " +"routers (DSL, cable,..) only allow a small number of connections (or just" +" go mad if you use more than X connections).\n" +"I2P tries to limit these connections to be under 1500 per UDP and per TCP" +" type.\n" +"This limits the amount of traffic routed across your I2P node as well." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:86 +msgid "" +"In summary, I2P is very complex and there is no easy way to pinpoint why " +"your node is not used.\n" +"If your node is reachable and has a bandwidth setting of >128 kbyte/sec " +"shared and is reachable 24/7, it should be used after some time for " +"participating traffic.\n" +"If it is down in between, the testing of your I2P node done by other " +"nodes will tell them: you are not reachable. This blocks your node for at" +" least \n" +"24h on other nodes. So, the other nodes which tested you as down will not" +" use your node for 24h for building tunnels. This is why your traffic " +"will \n" +"be lower after a restart/shutdown for a minimum of 24h." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:94 +msgid "" +"Also: other I2P nodes needs to know your I2P router to test it for " +"reachability and capacity. It takes time for other nodes to get known to " +"your node. \n" +"It will be faster if you use I2P and build more tunnels, e.g. use a " +"torrent or www for some time." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:99 +msgid "Performance Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:101 +#, python-format +msgid "" +"For possible future performance improvements see\n" +"Future Performance Improvements." +msgstr "" + diff --git a/i2p2www/translations/sq/LC_MESSAGES/about.po b/i2p2www/translations/sq/LC_MESSAGES/about.po new file mode 100644 index 00000000..426d6b52 --- /dev/null +++ b/i2p2www/translations/sq/LC_MESSAGES/about.po @@ -0,0 +1,2397 @@ +# Albanian translations for I2P. +# Copyright (C) 2019 ORGANIZATION +# This file is distributed under the same license as the I2P project. +# +# Translators: +# Besnik , 2018 +msgid "" +msgstr "" +"Project-Id-Version: I2P\n" +"Report-Msgid-Bugs-To: http://trac.i2p2.de\n" +"POT-Creation-Date: 2019-12-04 15:24+0000\n" +"PO-Revision-Date: 2019-12-04 15:29+0000\n" +"Last-Translator: zzzi2p\n" +"Language-Team: Albanian (http://www.transifex.com/otf/I2P/language/sq/)\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/about/alternative-clients.html:2 +#: i2p2www/pages/site/about/alternative-clients.html:4 +msgid "Alternative I2P clients" +msgstr "Klientë I2P alternativë" + +#: i2p2www/pages/site/about/alternative-clients.html:5 +msgid "" +"The main I2P client implementation uses Java. If for some \n" +"reason you can't use Java on your device, there are alternative " +"implementations\n" +"developed by community members." +msgstr "" + +#: i2p2www/pages/site/about/alternative-clients.html:12 +#, python-format +msgid "" +"i2pd is a I2P client implementation in C++.\n" +"As of early 2016, i2pd is became stable enough to be used in \n" +"production, and since summer 2016 it fully implements all I2P APIs." +msgstr "" + +#: i2p2www/pages/site/about/alternative-clients.html:19 +#, python-format +msgid "" +"Kovri is active i2pd fork developed for Monero " +"cryptocurrency." +msgstr "" + +#: i2p2www/pages/site/about/alternative-clients.html:24 +#, python-format +msgid "" +"Go-I2P is I2P client developed using the\n" +"Go programming language. The project is in " +"early development." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:2 +msgid "Web Browser Configuration" +msgstr "Formësim Shfletuesi" + +#: i2p2www/pages/site/about/browser-config.html:5 +msgid "" +"Your web browser will need to be configured in order to browse eepsites " +"and to\n" +"utilize the outproxies available within I2P. Below are walkthroughs for " +"some of\n" +"the most popular browsers." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:11 +msgid "Firefox Profile for Windows" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:12 +#, python-format +msgid "" +"If you are using Windows, the recommended way of accessing I2P is using " +"the \n" +"Firefox profile." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:16 +msgid "" +"If you do not wish to use that profile or are not on Windows, you need to" +" \n" +"configure your browser yourself. Read below on how to that." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:21 +msgid "How to configure your browser" +msgstr "Si të formësoni shfletuesin tuaj" + +#: i2p2www/pages/site/about/browser-config.html:27 +#: i2p2www/pages/site/about/browser-config.html:104 +msgid "Outproxy Terms Of Service" +msgstr "Kushte Shërbimi për Outproxy-n" + +#: i2p2www/pages/site/about/browser-config.html:32 +msgid "Internet Explorer 8 or Chrome" +msgstr "Internet Explorer 8 ose Chrome" + +#: i2p2www/pages/site/about/browser-config.html:33 +msgid "" +"In the tools menu select the \"Internet Options\" line to open the " +"settings. In the\n" +"settings window choose the connections tab and click on LAN settings for " +"the\n" +"proxy port configuration." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:38 +msgid "IE Internet Options" +msgstr "Mundësi Internet për IE-n" + +#: i2p2www/pages/site/about/browser-config.html:39 +msgid "" +"Now set the checkmark at \"use a proxy server for your LAN\" and at the " +"\"Bypass\n" +"proxy server for local addresses\". With a click on Advanced-button you " +"open the\n" +"window to open the ports. Enter the values like on the picture, IP " +"127.0.0.1\n" +"and port 4444 for HTTP, port 4445 for HTTPS. With clicks on OK you save " +"the\n" +"settings and your browser is set to use the I2P proxy.\n" +"Note/Privacy tip: Set the FTP proxy to the same settings as the " +"HTTP proxy." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:47 +msgid "IE Proxy Settings" +msgstr "Rregullime Ndërmjetësi për IE-n" + +#: i2p2www/pages/site/about/browser-config.html:51 +msgid "Instructions for Firefox 57 and above:" +msgstr "Udhëzime për Firefox 57 dhe më të madh:" + +#: i2p2www/pages/site/about/browser-config.html:52 +msgid "" +"From the Menu button in the top right, select Preferences.\n" +"Scroll down until you see the Network Proxy section, as shown in" +" the\n" +"screenshot below. Click on Settings" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:58 +msgid "Firefox57 Network Options" +msgstr "Mundësi Rrjeti për Firefox57" + +#: i2p2www/pages/site/about/browser-config.html:59 +msgid "" +"In the Connection Settings pop-up, select Manual proxy\n" +" configuration. Set both the HTTP and SSL Proxy to address\n" +"127.0.0.1 with port 4444 as shown in the " +"following\n" +"screenshot." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:66 +msgid "" +"Firefox57\n" +"Connection Settings" +msgstr "" +"Rregullime Lidhjeje\n" +"për Firefox57" + +#: i2p2www/pages/site/about/browser-config.html:67 +msgid "Firefox57 Connection Settings" +msgstr "Rregullime Lidhjeje për Firefox57" + +#: i2p2www/pages/site/about/browser-config.html:70 +msgid "" +"From the Tools menu, select Options to bring up the Firefox settings " +"panel.\n" +"Click the icon labelled Advanced, then click on the " +"Network\n" +"tab. In the Connections section, click on the Settings button. " +"You'll\n" +"see a Window like the following:" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:76 +msgid "Firefox Network Options" +msgstr "Mundësi Rrjeti për Firefox-in" + +#: i2p2www/pages/site/about/browser-config.html:77 +msgid "" +"In the Connection Settings window, click the circle next to " +"Manual\n" +" proxy configuration, then enter 127.0.0.1, port 4444 in the HTTP" +" Proxy\n" +"field. Enter 127.0.0.1, port 4445 in the SSL Proxy field.\n" +"Be sure to enter localhost and 127.0.0.1 into the \"No Proxy for\" box.\n" +"Note/Privacy tip: Set the FTP proxy to the same settings as the " +"HTTP proxy." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:85 +msgid "Firefox Proxy Settings" +msgstr "Rregullime Ndërmjetësi për Firefox-in" + +#: i2p2www/pages/site/about/browser-config.html:90 +msgid "" +"From the Settings menu, select Configure Konqueror. In " +"the\n" +"Web Browsing group on the left side, select Proxy, then select the option" +" \"Use manually specified proxy\n" +"configuration\" on the right." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:95 +msgid "Konqueror Proxy Options" +msgstr "Rregullime Ndërmjetësi për Konqueror-in" + +#: i2p2www/pages/site/about/browser-config.html:96 +msgid "" +"Enter 127.0.0.1 and port 4444 into the HTTP box. Enter 127.0.0.1 and port" +" 4445 into\n" +"HTTPS box. Enter 127.0.0.1,localhost into the Exceptions " +"box. Click Apply then OK\n" +"to close the configuration window.\n" +"Note/Privacy tip: Set the FTP proxy to the same settings as the " +"HTTP proxy." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:105 +msgid "" +"Remember: I2P was not designed for creating proxies to the outer " +"Internet.\n" +"Instead, it is meant to be used as an internal network." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:109 +msgid "" +"

The I2P project itself does not run any proxies to the " +"Internet. \n" +"The only outproxy is a service from the privacy solutions project. \n" +"Consider donating to them for a continued stable service. Higher " +"bandwidth will \n" +"increase with the founding of the organization. Maybe more outproxies " +"too.

\n" +"http://privacysolutions.no" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:117 +#, python-format +msgid "" +"By default, I2P comes with two outproxies configured: " +"%(http)s \n" +"and %(https)s. Even the domain names are different, it's the" +" same outproxy you hit.\n" +"(multi-homed/keyed for better performance)" +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:122 +msgid "" +"Filtering is active on these outproxies (for example, mibbit and torrent\n" +"tracker access is blocked). Eepsites\n" +"that are accessible via .i2p addresses are also not allowed via the " +"outproxies.\n" +"As a convenience, the outproxy blocks ad servers." +msgstr "" + +#: i2p2www/pages/site/about/browser-config.html:128 +msgid "" +"Tor is good application to use" +" as an\n" +"outproxy to the Internet." +msgstr "" + +#: i2p2www/pages/site/about/glossary.html:2 +msgid "Glossary" +msgstr "Fjalorth" + +#: i2p2www/pages/site/about/glossary.html:4 +msgid "" +"This page lists often-used terminology when discussing I2P and " +"cryptography." +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:2 +msgid "Hall Of Fame" +msgstr "Vendi i Nderit" + +#: i2p2www/pages/site/about/hall-of-fame.html:7 +msgid "" +"I2P is a project made completely by spare time enthusiasts. But a big " +"project like\n" +"I2P is not made from software alone, several servers, domain " +"registrations, and coffees need to\n" +"be paid to get a great result. People all over the world donated to I2P " +"reach the state it is in\n" +"currently. Here we do track those who gave us a name to be published in a" +" I2P hall of fame." +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:12 +msgid "Big thanks go to the following people who have donated to I2P!" +msgstr "Një falënderim të madh për personat vijues që kanë dhuruar për I2P-në!" + +#: i2p2www/pages/site/about/hall-of-fame.html:13 +#, python-format +msgid "" +"If you have made a donation, please send an email to echelon\n" +"with your name or nick (and optionally homepage) so we can list you here." +msgstr "" + +#: i2p2www/pages/site/about/hall-of-fame.html:18 +msgid "" +"The unsorted list of I2P donors in 15 years of I2P history, starting " +"March 2004 til March 2019." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:2 +msgid "Intro" +msgstr "Hyrje" + +#: i2p2www/pages/site/about/intro.html:4 +msgid "The Invisible Internet Project" +msgstr "Projekti i Internetit të Padukshëm" + +#: i2p2www/pages/site/about/intro.html:5 +#, python-format +msgid "" +"I2P is an anonymous network, exposing a simple layer that applications " +"can \n" +"use to anonymously and securely send messages to each other. The network " +"itself is \n" +"strictly message based (a la IP), but there is a \n" +"library available to allow reliable streaming communication on top of it " +"(a la \n" +"TCP). \n" +"All communication is end to end encrypted (in total there are four layers" +" of \n" +"encryption used when sending a message), and even the end points " +"(\"destinations\") \n" +"are cryptographic identifiers (essentially a pair of public keys)." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:18 +msgid "How does it work?" +msgstr "Si funksionon?" + +#: i2p2www/pages/site/about/intro.html:20 +#, python-format +msgid "" +"To anonymize the messages sent, each client application has their I2P " +"\"router\"\n" +"build a few inbound and outbound \"tunnels\" - a \n" +"sequence of peers that pass messages in one direction (to and from the " +"client, \n" +"respectively). In turn, when a client wants to send a message to another" +" client, \n" +"the client passes that message out one of their outbound tunnels " +"targeting one of the \n" +"other client's inbound tunnels, eventually reaching the destination. " +"Every \n" +"participant in the network chooses the length of these tunnels, and in " +"doing so, \n" +"makes a tradeoff between anonymity, latency, and throughput according to " +"their \n" +"own needs. The result is that the number of peers relaying each end to " +"end \n" +"message is the absolute minimum necessary to meet both the sender's and " +"the \n" +"receiver's threat model." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:34 +#, python-format +msgid "" +"The first time a client wants to contact another client, they make a " +"query \n" +"against the fully distributed \"network \n" +"database\" - a custom structured \n" +"distributed hash table (DHT) based off the \n" +"Kademlia algorithm. This is done \n" +"to find the other client's inbound tunnels efficiently, but subsequent " +"messages \n" +"between them usually includes that data so no further network database " +"lookups \n" +"are required." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:47 +#, python-format +msgid "More details about how I2P works are available." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:51 +msgid "What can you do with it?" +msgstr "Ç’mund të bëni me të?" + +#: i2p2www/pages/site/about/intro.html:53 +#, python-format +msgid "" +"Within the I2P network, applications are not restricted in how they can \n" +"communicate - those that typically use UDP can make use of the base I2P \n" +"functionality, and those that typically use TCP can use the TCP-like " +"streaming\n" +"library. We have a generic TCP/I2P bridge application \n" +"(\"I2PTunnel\") that enables people to " +"forward TCP streams\n" +"into the I2P network as well as to receive streams out of the network and" +" \n" +"forward them towards a specific TCP/IP address." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:63 +#, python-format +msgid "" +"I2PTunnel is currently used to let people run their own anonymous website" +" \n" +"(\"eepsite\") by running a normal webserver and pointing an I2PTunnel " +"'server' \n" +"at it, which people can access anonymously over I2P with a normal web " +"browser \n" +"by running an I2PTunnel HTTP proxy (\"eepproxy\"). In addition, we use " +"the same \n" +"technique to run an anonymous IRC network (where the IRC server is hosted" +" \n" +"anonymously, and standard IRC clients use an I2PTunnel to contact it). " +"There \n" +"are other application development efforts going on as well, such as one " +"to \n" +"build an optimized swarming file transfer application (a la \n" +"BitTorrent), a \n" +"distributed data store (a la Freenet / \n" +"MNet), and a blogging system (a fully \n" +"distributed LiveJournal), but those are \n" +"not ready for use yet." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:82 +#, python-format +msgid "" +"I2P is not inherently an \"outproxy\" network - the client you send a " +"message \n" +"to is the cryptographic identifier, not some IP address, so the message " +"must \n" +"be addressed to someone running I2P. However, it is possible for that " +"client\n" +"to be an outproxy, allowing you to anonymously make use of their Internet" +" \n" +"connection. To demonstrate this, the \"eepproxy\" will accept normal " +"non-I2P \n" +"URLs (e.g. \"http://www.i2p.net\") and forward them to a specific " +"destination\n" +"that runs a squid HTTP proxy, allowing \n" +"simple anonymous browsing of the normal web. Simple outproxies like that" +" are \n" +"not viable in the long run for several reasons (including the cost of " +"running \n" +"one as well as the anonymity and security issues they introduce), but in" +" \n" +"certain circumstances the technique could be appropriate." +msgstr "" + +#: i2p2www/pages/site/about/intro.html:96 +#, python-format +msgid "" +"The I2P development team is an open group, " +"welcome to all \n" +"who are interested in getting involved, and" +" all of \n" +"the code is open source. The core I2P SDK " +"and the \n" +"current router implementation is done in Java (currently working with " +"both \n" +"sun and kaffe, gcj support planned for later), and there is a \n" +"simple socket based API for accessing the network" +" from \n" +"other languages (with a C library available, and both Python and Perl in" +" \n" +"development). The network is actively being developed and has not yet " +"reached \n" +"the 1.0 release, but the current roadmap " +"describes \n" +"our schedule." +msgstr "" + +#: i2p2www/pages/site/about/media.html:2 +msgid "Presentations on I2P" +msgstr "Paraqitje lidhur me I2P-n" + +#: i2p2www/pages/site/about/media.html:5 +#, python-format +msgid "" +"Following are links to presentations, videos, and tutorials about I2P. " +"Links to research papers on I2P are available here." +msgstr "" + +#: i2p2www/pages/site/about/media.html:8 +#, python-format +msgid "To request an addition to this page, please send to %(email)s." +msgstr "" + +#: i2p2www/pages/site/about/media.html:11 +msgid "" +"\n" +"Newest links are at the bottom of each section." +msgstr "" + +#: i2p2www/pages/site/about/media.html:16 +msgid "Presentations" +msgstr "Paraqitje" + +#: i2p2www/pages/site/about/media.html:19 +#, python-format +msgid "" +"IIP Presentation at CodeCon\n" +"MP3 audio\n" +"transcript\n" +"Lance James (0x90), February 2002." +msgstr "" +"Paraqitje e IIP në CodeCon\n" +"Audio MP3\n" +"transkriptim\n" +"Lance James (0x90), shkurt 2002." + +#: i2p2www/pages/site/about/media.html:27 +#, python-format +msgid "" +"IIP Presentation at ToorCon\n" +"MP3 audio\n" +"slides\n" +"Lance James (0x90), September 2002." +msgstr "" +"Paraqitje e IIP në ToorCon\n" +"Audio MP3\n" +"diapozitiva\n" +"Lance James (0x90), shtator 2002." + +#: i2p2www/pages/site/about/media.html:35 +#, python-format +msgid "" +"To Be or I2P\n" +"(Youtube Video)\n" +"An introduction into anonymous communication with I2P.\n" +"To Be or I2P (PDF presentation),\n" +"Jens Kubieziel, 24C3 Berlin, December 28, 2007." +msgstr "" +"To Be or I2P\n" +"(Video Youtube)\n" +"Një hyrje në komunikimin anonim me I2P.\n" +"To Be or I2P (Paraqitje PDF),\n" +"Jens Kubieziel, 24C3 Berlin, 28 dhjetor, 2007." + +#: i2p2www/pages/site/about/media.html:44 +#, python-format +msgid "" +"Video of I2P talk at Chemnitz Linux Tag,\n" +"Lars Schimmer,\n" +"March 14-15, 2009" +msgstr "" +"Video e bisedës mbi I2P-në në Chemnitz Linux " +"Tag,\n" +"Lars Schimmer,\n" +"14-15 mars, 2009" + +#: i2p2www/pages/site/about/media.html:50 +#, python-format +msgid "" +"HOPE New York July 17, 2010 - Brief overview of I2P by zzz, at the end of" +" Adrian Hong's talk\n" +"\"Hackers for Human Rights\".\n" +"MP3 audio" +msgstr "" +"HOPE, Nju Jork, 17 korrik, 2010 - Përmbledhje e shkurtër e I2P-së nga " +"zzz, në fund të fjalës nga Adrian Hong\n" +"\"Hackers for Human Rights\".\n" +"Audio MP3" + +#: i2p2www/pages/site/about/media.html:56 +#, python-format +msgid "" +"Into the I2P Darknet: Welcome to Cipherspace\n" +"Adrian Crenshaw. Schmoocon Firetalk, January 2011" +msgstr "" +"Into the I2P Darknet: Welcome to Cipherspace\n" +"Adrian Crenshaw. Schmoocon Firetalk, janar 2011" + +#: i2p2www/pages/site/about/media.html:61 +#, python-format +msgid "" +"Using techhnology to advance liberty\n" +"(Youtube Video)\n" +"Eric Johnson.\n" +"Agora I/O Unconference, March 27," +" 2011.\n" +"I2P covered from 10:00 to 20:00 in the video." +msgstr "" +"Përdorim i teknologjisë për shpënien më tej të " +"lirisë\n" +"(Video Youtube)\n" +"Eric Johnson.\n" +"Agora I/O Unconference, 27 mars, " +"2011.\n" +"Në video I2P diskutohet nga minuta 10:00 deri në atë 20:00." + +#: i2p2www/pages/site/about/media.html:69 +#, python-format +msgid "" +"Common Darknet Weaknesses\n" +"(Youtube Video)\n" +"Adrian Crenshaw, AIDE, July " +"11-15, 2011." +msgstr "" +"Common Darknet Weaknesses\n" +"(Video Youtube)\n" +"Adrian Crenshaw, AIDE, 11-15 " +"korrik, 2011." + +#: i2p2www/pages/site/about/media.html:75 +#, python-format +msgid "" +"I2P / Tor Workshop Notes\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011." +msgstr "" +"Shënime nga Praktika mbi I2P / Tor\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, 6 gusht, 2011." + +#: i2p2www/pages/site/about/media.html:80 +#, python-format +msgid "" +"Cipherspaces/Darknets: An Overview Of Attack " +"Strategies -\n" +"DEF CON Live version (Youtube Video),\n" +"\"Studio\" version (Youtube Video),\n" +"Slides (ppt)\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011." +msgstr "" +"Cipherspaces/Darknets: An Overview Of Attack " +"Strategies -\n" +"Versioni Live nga DEF CON (Video Youtube),\n" +"Versioni \"studio\" (Video Youtube),\n" +"Diapozitiva (ppt)\n" +"Adrian Crenshaw. DEF CON 19, Las Vegas, 7 gusht, 2011." + +#: i2p2www/pages/site/about/media.html:90 +msgid "" +"Modern cipherspace ecosystems, 0x375 " +"0x06 (Thessaloniki Tech Talk Sessions), November 4, 2011." +msgstr "" +"Modern cipherspace ecosystems, 0x375 " +"0x06 (Thessaloniki Tech Talk Sessions), 4 nëntor, 2011." + +#: i2p2www/pages/site/about/media.html:94 +#, python-format +msgid "" +"I2P - The Anonymous Network\n" +"(Youtube Video)\n" +"Blair Dick, University of Abertay, Dundee Ethical Hacking Society, " +"January 25, 2012." +msgstr "" +"I2P - Rrjeti Anonim\n" +"(Video Youtube)\n" +"Blair Dick, University of Abertay, Dundee Ethical Hacking Society, 25 " +"janr, 2012." + +#: i2p2www/pages/site/about/media.html:100 +#, python-format +msgid "" +"I2PCon 2015\n" +"Toronto, August 15-16, 2015" +msgstr "" +"I2PCon 2015\n" +"Toronto, 15-16 gusht, 2015" + +#: i2p2www/pages/site/about/media.html:105 +#, python-format +msgid "" +"I2P - Still alive! (pdf)\n" +"(video)\n" +"echelon, 32C3 (You Broke the Internet Assembly), Hamburg, December 28, " +"2015" +msgstr "" +"I2P - ende gjallë! (pdf)\n" +"(video)\n" +"echelon, 32C3 (You Broke the Internet Assembly), Hamburg, 28 dhjetor, 2015" + +#: i2p2www/pages/site/about/media.html:112 +#, python-format +msgid "" +"Replacing Weary Crypto: Upgrading the I2P network with stronger " +"primitives\n" +"(pdf)\n" +"(odp)\n" +"str4d, Real World Crypto, Stanford, January 8, 2016" +msgstr "" +"Zëvendësim i Fshehtëzimit të Lodhur: Përmirësim i rrjetit I2P me " +"primitivë më të fuqishëm\n" +"(pdf)\n" +"(odp)\n" +"str4d, Real World Crypto, Stanford, 8 janar, 2016" + +#: i2p2www/pages/site/about/media.html:120 +#, python-format +msgid "" +"Onions and Garlic: the protocols of I2P\n" +"(pdf)\n" +"(odp)\n" +"str4d, COMPSCI 460: Computer Networking, University of Wisconsin " +"Whitewater, February 17, 2016" +msgstr "" +"Qepër dhe Hudhra: protokollet e I2P-së\n" +"(pdf)\n" +"(odp)\n" +"str4d, COMPSCI 460: Computer Networking, University of Wisconsin " +"Whitewater, 17 shkurt, 2016" + +#: i2p2www/pages/site/about/media.html:128 +#, python-format +msgid "" +"The Invisible Internet Project - An overview and guide to the technology\n" +"(mp4)\n" +"(webm)\n" +"Andrew Savchenko (bircoph), FOSDEM, Brussel, February 4, 2018" +msgstr "" +"Projekti i Internetit të Padukshëm - Një përmbledhje dhe një udhërrëfyes " +"për teknologjinë\n" +"(mp4)\n" +"(webm)\n" +"Andrew Savchenko (bircoph), FOSDEM, Bruksel, 4 shkurt, 2018" + +#: i2p2www/pages/site/about/media.html:139 +msgid "Tutorials" +msgstr "Përkujdesore" + +#: i2p2www/pages/site/about/media.html:142 +#, python-format +msgid "" +"I2P Windows Tutorial\n" +"(Youtube Video)\n" +"This guide will show you how to install I2P in Windows XP.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:149 +#, python-format +msgid "" +"I2P Debian Tutorial\n" +"(Youtube Video)\n" +"This will guide you through how to install I2P on a Debian Linux System.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:156 +#, python-format +msgid "" +"How to set up anonymous site in I2P\n" +"(Youtube Video)\n" +"How to set up an anonymous web site in I2P.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:163 +#, python-format +msgid "" +"I2P Tutorial Mac OS X\n" +"(Youtube Video)\n" +"A tutorial on how to run i2p on Mac OS X and how to connect to " +"irc.telecomix.i2p.\n" +"By Telecomix" +msgstr "" + +#: i2p2www/pages/site/about/media.html:170 +#, python-format +msgid "" +"Felix Atari explains the basic principles of I2P" +"\n" +"(Youtube Video)\n" +"Agent Felix Atari of the Telecomix Crypto Munitions Bureau.\n" +"By Telecomix" +msgstr "" +"Felix Atari shpjegon parimet bazë të I2P-së\n" +"(Video Youtube)\n" +"Agjenti Felix Atari i Telecomix Crypto Munitions Bureau.\n" +"Nga Telecomix" + +#: i2p2www/pages/site/about/media.html:177 +#, python-format +msgid "" +"How to get onto I2P, the anonymous P2P Darknet " +"(Windows Install)\n" +"(Youtube Video)\n" +"This tutorial shows how to install and configure software needed to " +"access I2P." +msgstr "" +"Si të hyhet në I2P, Darknet-i P2P anonim (Instalim " +"Windows)\n" +"(Video Youtube)\n" +"Kjo përkujdesore tregon se si të instalohet dhe formësohet software-i i " +"nevojshëm për të përdorur I2P-në." + +#: i2p2www/pages/site/about/media.html:183 +#, python-format +msgid "" +"How to connect to I2P\n" +"(Youtube Video)\n" +"How to install I2P on Ubuntu." +msgstr "" +"Si të lidheni në I2P\n" +"(Video Youtube)\n" +"Si të instalohet I2P-ja në Ubuntu." + +#: i2p2www/pages/site/about/media.html:189 +#, python-format +msgid "" +"Installing the I2P darknet software in Linux\n" +"(Video)\n" +"Adrian Crenshaw.\n" +"January 2011" +msgstr "" +"Instalimi i software-it darknet I2P në Linux\n" +"(Video)\n" +"Adrian Crenshaw.\n" +"janar 2011" + +#: i2p2www/pages/site/about/media.html:196 +#, python-format +msgid "" +"Short garlic routing animation\n" +"(Youtube Video)\n" +"Adrian Crenshaw.\n" +msgstr "" +"Animacion i shkurtër mbi rrugëzim " +"garlic\n" +"(Video Youtube)\n" +"Adrian Crenshaw.\n" + +#: i2p2www/pages/site/about/media.html:204 +msgid "Articles and Interviews" +msgstr "Artikuj dhe Intervista" + +#: i2p2www/pages/site/about/media.html:207 +#, python-format +msgid "" +"Lance James (0x90) Interviewed by DistributedCity\n" +"Part 1\n" +"Part 2\n" +"July 26, 2002." +msgstr "" +"Lance James (0x90) intervistuar nga DistributedCity\n" +"Pjesa 1\n" +"Pjesa 2\n" +"26 korrik, 2002." + +#: i2p2www/pages/site/about/media.html:215 +#, python-format +msgid "" +"Lance James (0x90) Interviewed by El País\n" +"(original in Spanish)\n" +"English translation\n" +"October 31, 2002." +msgstr "" +"Lance James (0x90) intervistuar nga El País\n" +"(origjinali në spanjisht)\n" +"përkthimi në anglisht\n" +"31 tetor, 2002." + +#: i2p2www/pages/site/about/media.html:222 +#, python-format +msgid "" +"2003 Business Week article referencing " +"invisiblenet\n" +"September 14, 2003." +msgstr "" +"Artikull i 2003-shit në “Business Week” ku përmendet" +" invisiblenet\n" +"14 shtator, 2003." + +#: i2p2www/pages/site/about/media.html:227 +#, python-format +msgid "" +"Netzwelt.de article about being anonymous in the " +"Internet\n" +"(German)\n" +"November 2007." +msgstr "" +"Artikull i Netzwelt.de rreth se si të jeni anonim në" +" Internet\n" +"(gjermanisht)\n" +"nëntor 2007." + +#: i2p2www/pages/site/about/media.html:233 +#, python-format +msgid "" +"zzz interviewed by gulli.com\n" +"March 2009\n" +"German translation" +msgstr "" +"zzz intervistuar nga gulli.com\n" +"mars 2009\n" +"Përkthimi në gjermanisht" + +#: i2p2www/pages/site/about/media.html:240 +#, python-format +msgid "" +"zzz interviewed on the InfoSec Daily Podcast Ep. 454 " +"(mp3)\n" +"August 18, 2011\n" +"(link dead, seeded inside I2P at postman's" +" tracker)" +msgstr "" +"zzz intervistuar në InfoSec Daily Podcast Ep. 454 " +"(mp3)\n" +"18 gusht, 2011\n" +"(lidhje e vdekur, mbjellë brenda I2P te postman's" +" tracker)" + +#: i2p2www/pages/site/about/media.html:246 +#, python-format +msgid "" +"I2P - Anonymity for the Masses,\n" +"Jonathan Cox,\n" +"November 11, 2011." +msgstr "" +"I2P - Anonimitet për Masat,\n" +"Jonathan Cox,\n" +"11 nëntor, 2011." + +#: i2p2www/pages/site/about/media.html:252 +#, python-format +msgid "" +"zzz and Lance James interviewed on the InfoSec Daily " +"Podcast Ep. 596 (mp3)\n" +"February 16, 2012\n" +"(link dead, seeded inside I2P at postman's" +" tracker)" +msgstr "" +"zzz dhe Lance James intervistuar në InfoSec Daily " +"Podcast Ep. 596 (mp3)\n" +"16 shkurt, 2012\n" +"(lidhje e vdekur, mbjellë brenda I2P te postman's" +" tracker)" + +#: i2p2www/pages/site/about/media.html:258 +#, python-format +msgid "" +"Jeff and Str4d interviewed on the Brakeing Down " +"Security Podcast Ep. 2015-010 (mp3)\n" +"Part 1, February 28, 2015" +msgstr "" + +#: i2p2www/pages/site/about/media.html:263 +#, python-format +msgid "" +"Jeff and Str4d interviewed on the Brakeing Down " +"Security Podcast Ep. 2015-011 (mp3)\n" +"Part 2, March 6, 2015" +msgstr "" + +#: i2p2www/pages/site/about/media.html:268 +#, python-format +msgid "" +"Fireside With Lei - Episode 18: Lance James. " +"Success, Failures, Grief and Buddhism.\n" +"(archive.org)\n" +"(mp3)\n" +"Robert Lei, December 31, 2018" +msgstr "" + +#: i2p2www/pages/site/about/media.html:277 +#, python-format +msgid "" +"Articles by I2P contributor Masayuki Hatta on " +"Medium.com\n" +"2019\n" +msgstr "" + +#: i2p2www/pages/site/about/media.html:282 +#, python-format +msgid "" +"Enabling both .onion and .i2p routing with Proxy " +"Auto-Configuration\n" +"Daniel Aleksandersen, February 7 2019" +msgstr "" + +#: i2p2www/pages/site/about/media.html:289 +msgid "Other" +msgstr "Tjetër" + +#: i2p2www/pages/site/about/media.html:292 +msgid "" +"I2P mentioned in Netflix's \"House of Cards\" Season 2 Episode 2,\n" +"February 14, 2014" +msgstr "" + +#: i2p2www/pages/site/about/media.html:297 +#, python-format +msgid "" +"A curated list by I2P contributor meeh of I2P " +"implementations, libraries, resources, projects, and shiny things\n" +"2019" +msgstr "" + +#: i2p2www/pages/site/about/team.html:2 +msgid "I2P Project Members" +msgstr "Anëtarë të Projektit I2P" + +#: i2p2www/pages/site/about/team.html:5 +#, python-format +msgid "" +"We are a small group of people spread around several continents, working " +"to\n" +"advance different aspects of the project and discussing the design of the" +"\n" +"network.\n" +"Get involved!" +msgstr "" + +#: i2p2www/pages/site/about/team.html:14 +msgid "Admin" +msgstr "Admin" + +#: i2p2www/pages/site/about/team.html:15 +msgid "Project Manager" +msgstr "Përgjegjës Projekti" + +#: i2p2www/pages/site/about/team.html:17 +msgid "point of contact of last resort" +msgstr "" + +#: i2p2www/pages/site/about/team.html:20 +msgid "Donations treasurer" +msgstr "" + +#: i2p2www/pages/site/about/team.html:22 +msgid "manage donations" +msgstr "" + +#: i2p2www/pages/site/about/team.html:25 +msgid "PR manager" +msgstr "Përgjegjës PR-i" + +#: i2p2www/pages/site/about/team.html:27 +msgid "press contact, manages public relations and affairs" +msgstr "kontakt për shtypin, administron marrëdhëniet dhe çështjet me publikun" + +#: i2p2www/pages/site/about/team.html:30 +msgid "Compensation manager" +msgstr "" + +#: i2p2www/pages/site/about/team.html:32 +msgid "Compensation management" +msgstr "" + +#: i2p2www/pages/site/about/team.html:35 i2p2www/pages/site/about/team.html:40 +msgid "Assistant PR manager" +msgstr "Asistent përgjegjësi PR-i" + +#: i2p2www/pages/site/about/team.html:37 +msgid "Public speaking, public relations assistance" +msgstr "Komunikim me publikun, ndihmë në marrëdhëniet me pulbikun" + +#: i2p2www/pages/site/about/team.html:42 +msgid "Public relations assistance" +msgstr "Ndihmë në marrëdhëniet me publikun" + +#: i2p2www/pages/site/about/team.html:45 +#, python-format +msgid "Forum admin" +msgstr "Përgjegjës forumi" + +#: i2p2www/pages/site/about/team.html:47 +msgid "manage the public user forum" +msgstr "administron forumin publik të përdoruesve" + +#: i2p2www/pages/site/about/team.html:50 +msgid "Download mirrors admin" +msgstr "Përgjegjës pasqyrash shkarkimi" + +#: i2p2www/pages/site/about/team.html:52 +msgid "manage the mirrors for the download files" +msgstr "administron pasqyrat për kartela shkarkimi" + +#: i2p2www/pages/site/about/team.html:55 +msgid "Website mirrors admin" +msgstr "Përgjegjës pasqyrash sajti" + +#: i2p2www/pages/site/about/team.html:56 i2p2www/pages/site/about/team.html:91 +#: i2p2www/pages/site/about/team.html:106 +#: i2p2www/pages/site/about/team.html:126 +#: i2p2www/pages/site/about/team.html:131 +#: i2p2www/pages/site/about/team.html:171 +#: i2p2www/pages/site/about/team.html:193 +#: i2p2www/pages/site/about/team.html:203 +#: i2p2www/pages/site/about/team.html:218 +#: i2p2www/pages/site/about/team.html:251 +msgid "vacant" +msgstr "i pazënë" + +#: i2p2www/pages/site/about/team.html:57 +msgid "manage the mirrors for the website" +msgstr "administron pasqyrat për sajtin" + +#: i2p2www/pages/site/about/team.html:60 +#, python-format +msgid "Monotone guru" +msgstr "Guru Monotone" + +#: i2p2www/pages/site/about/team.html:62 +msgid "manage the public monotone repositories" +msgstr "administron depot publike Monotone" + +#: i2p2www/pages/site/about/team.html:65 +msgid "Packager; Linux" +msgstr "Paketues; Linux" + +#: i2p2www/pages/site/about/team.html:67 +msgid "Linux (Debian/Ubuntu) distribution packager" +msgstr "Paketues shpërndarjesh Linux (Debian/Ubuntu)" + +#: i2p2www/pages/site/about/team.html:70 +msgid "Packager; Windows" +msgstr "Paketues; Windows" + +#: i2p2www/pages/site/about/team.html:72 +msgid "Windows installer packager" +msgstr "Paketues instaluesi për Windows" + +#: i2p2www/pages/site/about/team.html:75 +msgid "Packager; OSX" +msgstr "Paketues; OSX" + +#: i2p2www/pages/site/about/team.html:77 +msgid "OSX installer packager" +msgstr "Paketues instaluesi për OSX" + +#: i2p2www/pages/site/about/team.html:80 +msgid "Release Manager" +msgstr "Përgjegjës Hedhjesh Në Qarkullim" + +#: i2p2www/pages/site/about/team.html:82 +msgid "Builds and signs the releases" +msgstr "Monton dhe nënshkruan hedhjet në qarkullim" + +#: i2p2www/pages/site/about/team.html:85 +msgid "Release Manager Alternates" +msgstr "" + +#: i2p2www/pages/site/about/team.html:87 +msgid "Backup release managers" +msgstr "" + +#: i2p2www/pages/site/about/team.html:90 +msgid "Tails Maintainer" +msgstr "Mirëmbajtës për Tails" + +#: i2p2www/pages/site/about/team.html:92 +msgid "Maintain the I2P package in Tails" +msgstr "Mirëmban Paketën I2P në Tails" + +#: i2p2www/pages/site/about/team.html:95 +msgid "CI admin" +msgstr "Përgjegjës CI" + +#: i2p2www/pages/site/about/team.html:97 +msgid "Maintain the Continuous Integration infrastructure" +msgstr "Mirëmban infrastrukturën Continuous Integration" + +#: i2p2www/pages/site/about/team.html:100 +msgid "Reseed admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:102 +msgid "Monitors, advises and recruits reseed hosts" +msgstr "" + +#: i2p2www/pages/site/about/team.html:105 +msgid "Security expert" +msgstr "Ekspert sigurie" + +#: i2p2www/pages/site/about/team.html:107 +msgid "threat model / crypto expert" +msgstr "" + +#: i2p2www/pages/site/about/team.html:112 +msgid "Manage the project bug tracker" +msgstr "Administron ndjekësin e të metave të projektit" + +#: i2p2www/pages/site/about/team.html:117 +#: i2p2www/pages/site/about/team.html:137 +msgid "manage the public project webservers" +msgstr "administron shërbyesit publikë të projektit" + +#: i2p2www/pages/site/about/team.html:120 +msgid "Translation admins" +msgstr "Përgjegjës përkthimi" + +#: i2p2www/pages/site/about/team.html:125 +msgid "User Advocate" +msgstr "" + +#: i2p2www/pages/site/about/team.html:127 +msgid "gather, prioritize, advocate for user needs" +msgstr "" + +#: i2p2www/pages/site/about/team.html:130 +msgid "Web Designer" +msgstr "Hartimi grafik për Web" + +#: i2p2www/pages/site/about/team.html:132 +msgid "manage the public project website content design" +msgstr "administron hartim grafik të lëndës së sajtit publik të projektit" + +#: i2p2www/pages/site/about/team.html:135 +#, python-format +msgid "Webserver admin" +msgstr "Përgjegjës shërbyesi" + +#: i2p2www/pages/site/about/team.html:140 +#, python-format +msgid "Website admin" +msgstr "Përgjegjës sajti" + +#: i2p2www/pages/site/about/team.html:142 +msgid "manage the public project website content" +msgstr "administron lëndën e sajtit publik të projektit" + +#: i2p2www/pages/site/about/team.html:145 +msgid "News Admin" +msgstr "Përgjegjës Lajmesh" + +#: i2p2www/pages/site/about/team.html:147 +msgid "manage router console news feed" +msgstr "" + +#: i2p2www/pages/site/about/team.html:150 +msgid "Backup News Admin" +msgstr "" + +#: i2p2www/pages/site/about/team.html:152 +msgid "manage the backup news feed" +msgstr "" + +#: i2p2www/pages/site/about/team.html:170 +msgid "Director of passion" +msgstr "" + +#: i2p2www/pages/site/about/team.html:172 +msgid "community motivator" +msgstr "motivues bashkësie" + +#: i2p2www/pages/site/about/team.html:176 +msgid "Dev" +msgstr "Zhvillues" + +#: i2p2www/pages/site/about/team.html:177 +msgid "Core Lead" +msgstr "Drejtues i Bazës" + +#: i2p2www/pages/site/about/team.html:179 +msgid "lead dev for the SDK and router" +msgstr "zhvillues drejtues për SDK-në dhe rrugëzuesin" + +#: i2p2www/pages/site/about/team.html:182 +#, python-format +msgid "I2P mail lead" +msgstr "Drejtues për postën I2P" + +#: i2p2www/pages/site/about/team.html:184 +msgid "organize and develop the i2p mail system" +msgstr "organizon dhe zhvillon sistemin e postës i2p" + +#: i2p2www/pages/site/about/team.html:187 +#, python-format +msgid "I2P-Bote lead" +msgstr "Drejtues për I2P-Bote" + +#: i2p2www/pages/site/about/team.html:189 +msgid "I2P-Bote plugin" +msgstr "Shtojcë I2P-Bote" + +#: i2p2www/pages/site/about/team.html:192 +#, python-format +msgid "I2Phex lead" +msgstr "Drejtues për I2Phex" + +#: i2p2www/pages/site/about/team.html:194 +msgid "I2Phex Gnutella client" +msgstr "Klienti Gnutella I2Phex" + +#: i2p2www/pages/site/about/team.html:197 +#, python-format +msgid "I2PSnark lead" +msgstr "Drejtues për I2PSnark" + +#: i2p2www/pages/site/about/team.html:199 +msgid "Maintains the integrated Bittorrent client" +msgstr "Mirëmban klientin e integruar Bittorrent" + +#: i2p2www/pages/site/about/team.html:202 +#, python-format +msgid "Syndie lead" +msgstr "Drejtues për Syndie" + +#: i2p2www/pages/site/about/team.html:204 +msgid "Syndie development" +msgstr "Zhvillim i Syndie-t" + +#: i2p2www/pages/site/about/team.html:207 +msgid "Susimail lead" +msgstr "Drejtues për Susimail" + +#: i2p2www/pages/site/about/team.html:209 +msgid "Susimail development" +msgstr "Zhvillim i Susimail-it" + +#: i2p2www/pages/site/about/team.html:212 +msgid "Android lead" +msgstr "Drejtues për Android" + +#: i2p2www/pages/site/about/team.html:214 +msgid "Android development" +msgstr "Zhvillim për Android" + +#: i2p2www/pages/site/about/team.html:217 +msgid "Console" +msgstr "Konsolë" + +#: i2p2www/pages/site/about/team.html:219 +msgid "Router console HTML/CSS design" +msgstr "Konceptimi HTML/CSS i konsolës së rrugëzuesit" + +#: i2p2www/pages/site/about/team.html:222 +msgid "SAM" +msgstr "SAM" + +#: i2p2www/pages/site/about/team.html:224 +msgid "SAM maintainer" +msgstr "Mirëmbajtës i SAM-it" + +#: i2p2www/pages/site/about/team.html:227 +msgid "Translators" +msgstr "Përkthyes" + +#: i2p2www/pages/site/about/team.html:228 +msgid "many many people!" +msgstr "shumë, shumë vetë!" + +#: i2p2www/pages/site/about/team.html:233 +msgid "Contributors" +msgstr "Kontribues" + +#: i2p2www/pages/site/about/team.html:235 +msgid "fire2pe dev, console enhancements" +msgstr "zhvillim i fire2pe-s, thellime konsole" + +#: i2p2www/pages/site/about/team.html:239 +msgid "desktopgui, dijjer port" +msgstr "desktopgui, portë për dijjer" + +#: i2p2www/pages/site/about/team.html:243 +msgid "Debian/Ubuntu Packager and PPA maintainer" +msgstr "Paketues dhe mirëmbajtës PPA për Debian/Ubuntu" + +#: i2p2www/pages/site/about/team.html:247 +msgid "Routerconsole backend and UI work, website revamp, unit tests work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:252 +msgid "Help needed on many fronts!" +msgstr "Na duhet ndihmë në shumë fronte!" + +#: i2p2www/pages/site/about/team.html:256 +msgid "Past contributors" +msgstr "Kontribues të dikurshëm" + +#: i2p2www/pages/site/about/team.html:258 +msgid "I2PTunnel development, ministreaming library" +msgstr "" + +#: i2p2www/pages/site/about/team.html:262 +msgid "Project lead, Syndie lead" +msgstr "Drejtues i projektit, drejtues i Syndie-t" + +#: i2p2www/pages/site/about/team.html:266 +msgid "Project lead, Syndie lead, I2Phex, support guru" +msgstr "Drejtues i projektit, drejtues i Syndie-t, I2Phex, guru asistence" + +#: i2p2www/pages/site/about/team.html:270 +msgid "iMule lead" +msgstr "Drejtues për iMule" + +#: i2p2www/pages/site/about/team.html:274 +#: i2p2www/pages/site/about/team.html:278 +#: i2p2www/pages/site/about/team.html:282 +msgid "I2Phex work" +msgstr "Punë me I2Phex" + +#: i2p2www/pages/site/about/team.html:286 +msgid "Python SAM library, attack simulations" +msgstr "Librari Python SAM, simulime sulmesh" + +#: i2p2www/pages/site/about/team.html:290 +msgid "i2pmail development" +msgstr "Zhvillim i i2pmail-it" + +#: i2p2www/pages/site/about/team.html:294 +msgid "Syndie help" +msgstr "Ndihmë për Syndie" + +#: i2p2www/pages/site/about/team.html:298 +msgid "i2p mail,susimail and susidns apps" +msgstr "aplikacione për postë i2p, susimail dhe susidns" + +#: i2p2www/pages/site/about/team.html:302 +msgid "I2Phex (port of Phex to I2P)" +msgstr "I2Phex (portë e Phex-it te I2P)" + +#: i2p2www/pages/site/about/team.html:306 +msgid "addressbook,i2p-bt,syndie client" +msgstr "addressbook, i2p-bt, klient syndie" + +#: i2p2www/pages/site/about/team.html:310 +msgid "organize and develop the i2p-bt BitTorrent port" +msgstr "" + +#: i2p2www/pages/site/about/team.html:314 +msgid "addressbook, i2p-bt, syndie client development" +msgstr "" + +#: i2p2www/pages/site/about/team.html:318 +msgid "encryption and signature routines, I2PIM" +msgstr "" + +#: i2p2www/pages/site/about/team.html:322 +msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)" +msgstr "" + +#: i2p2www/pages/site/about/team.html:326 +msgid "installer, systray, bogobot" +msgstr "instalues, systray, bogobot" + +#: i2p2www/pages/site/about/team.html:330 +msgid "jbigi development, wiki migration, doc cleanup" +msgstr "zhvillim i jbigi-it, migrim wiki, pastrim dokumentimi" + +#: i2p2www/pages/site/about/team.html:334 +msgid "java debugging and client development on I2PTunnel and the router console" +msgstr "" + +#: i2p2www/pages/site/about/team.html:338 +msgid "SAM perl module" +msgstr "Modul perl për Sam" + +#: i2p2www/pages/site/about/team.html:342 +msgid "i2psnark work" +msgstr "" + +#: i2p2www/pages/site/about/team.html:346 +msgid "java cleanup" +msgstr "Pastrim kodi Java" + +#: i2p2www/pages/site/about/team.html:350 +msgid "docs. wiki migration" +msgstr "" + +#: i2p2www/pages/site/about/team.html:354 +msgid "translations into French" +msgstr "përkthime në frëngjisht" + +#: i2p2www/pages/site/about/team.html:358 +msgid "C port of jcpuid" +msgstr "Portë C e jcpuid-së" + +#: i2p2www/pages/site/about/team.html:362 +msgid "C# SAM library, pants, fortuna integration" +msgstr "" + +#: i2p2www/pages/site/about/team.html:366 +msgid "libSAM" +msgstr "libSAM" + +#: i2p2www/pages/site/about/team.html:370 +#: i2p2www/pages/site/about/team.html:374 +msgid "i2p-bt tracker development" +msgstr "Zhvillim i gjurmuesit i2p-bt" + +#: i2p2www/pages/site/about/team.html:378 +msgid "Console and website themes" +msgstr "Tema konsole dhe sajti" + +#: i2p2www/pages/site/about/team.html:408 +msgid "… and many others" +msgstr "… dhe plot të tjera" + +#: i2p2www/pages/site/about/i2pcon/2015.html:6 +msgid "" +"I2PCon 2015 was the first event of its kind. It had two short-term goals." +"\n" +"First, to provide the general public with an event where knowledge about " +"privacy could be obtained.\n" +"Second, to further the I2P project and its community with technical " +"discussions\n" +"about cryptography, anonymity and I2P-centric topics." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:15 +msgid "" +"A a larger and more long-term goal of this event was to build a\n" +"commnutiy of privacy-conscious individuals. By connecting people who " +"recognize\n" +"the importance of privacy, we wanted to provide a forum where this " +"community can grow." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:23 +msgid "" +"The idea for this event was first spawned by our wonderful friends at\n" +"Toronto Crypto.\n" +"The venue was provided by Hacklab.to." +"\n" +"The marketing was spearheaded by @YrB1rd and Siew.\n" +"Without them this event would not have been possible." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:32 +msgid "Slides and Video" +msgstr "Diapozitiva dhe Video" + +#: i2p2www/pages/site/about/i2pcon/2015.html:34 +msgid "Slides are also available as an in-I2P torrent." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:41 +msgid "Note: Video links will be posted as they become available." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:44 +msgid "" +"Note that in-I2P torrents may also be available on the clearnet due to " +"bridging by Vuze clients." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:50 +msgid "Licenses" +msgstr "Licenca" + +#: i2p2www/pages/site/about/i2pcon/2015.html:52 +msgid "All videos are by z3r0fox." +msgstr "Krejt videot janë prej z3r0fox." + +#: i2p2www/pages/site/about/i2pcon/2015.html:56 +msgid "License" +msgstr "Licencë" + +#: i2p2www/pages/site/about/i2pcon/2015.html:60 +msgid "Slides by psi: Public domain." +msgstr "Diapozitiva nga psi: Përkatësi publike." + +#: i2p2www/pages/site/about/i2pcon/2015.html:65 +msgid "Slides by str4d and zzz:" +msgstr "Diapozitiva nga str4d dhe zzz:" + +#: i2p2www/pages/site/about/i2pcon/2015.html:71 +msgid "Slides by others: Contact the author for license information." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:77 +msgid "Speakers" +msgstr "Folës" + +#: i2p2www/pages/site/about/i2pcon/2015.html:79 +msgid "" +"Colin Mahns has a strong interest in the use of anonymity and encryption " +"technology to help preserve human rights in the digital age." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:85 +msgid "" +"David Dagon is a postdoc researcher at Georgia Tech focused on botnets, " +"malware, network security, and DNS.\n" +"His interest in I2P is centered on preserving user privacy, autonomous " +"filtering, and anti-abuse." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:89 +#: i2p2www/pages/site/about/i2pcon/2015.html:105 +msgid "More info" +msgstr "Më tepër të dhëna" + +#: i2p2www/pages/site/about/i2pcon/2015.html:92 +msgid "J is the head of Toronto Crypto." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:98 +msgid "" +"Lance James is the founder of the Invisibile IRC Project, the predecessor" +" to I2P, back in 2002.\n" +"He founded his own cyber threat intelligence company in 2003.\n" +"He's been focused on network security, malware research, and information " +"security ever since.\n" +"During 2011-2013, he was Director of Threat Intelligence for The " +"Vigilant, which was acquired by Deloitte in 2013.\n" +"He recently left Deloitte to do consulting through his company The James " +"Group." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:109 +msgid "Nicholas D. is a member of Hacklab Toronto." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:115 +msgid "" +"Nicholas Johnston is a Professor of Information Security in Sheridan " +"College's School of Applied Computing in the InfoSec Bachelor's degree " +"program.\n" +"His previous professional career was in digital forensics and " +"investigations.\n" +"He is also a contractor specializing in incident response.\n" +"His research areas include secure software development and data analytics." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:124 +msgid "Psi is an I2P developer." +msgstr "Psi është një zhvillues i I2P-së." + +#: i2p2www/pages/site/about/i2pcon/2015.html:130 +msgid "Str4d is an I2P developer." +msgstr "Str4d është një zhvillues i I2P-së." + +#: i2p2www/pages/site/about/i2pcon/2015.html:136 +msgid "Zzz is an I2P developer." +msgstr "Zzz është një zhvillues i I2P-së." + +#: i2p2www/pages/site/about/i2pcon/2015.html:143 +msgid "Press" +msgstr "Për Shtypin" + +#: i2p2www/pages/site/about/i2pcon/2015.html:146 +msgid "Toronto Star article on Nicholas Johnston's talk" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:152 +msgid "Day 1" +msgstr "Dita 1" + +#: i2p2www/pages/site/about/i2pcon/2015.html:155 +#: i2p2www/pages/site/about/i2pcon/2015.html:235 +msgid "Talk" +msgstr "Bisedë" + +#: i2p2www/pages/site/about/i2pcon/2015.html:156 +#: i2p2www/pages/site/about/i2pcon/2015.html:236 +msgid "Presenter" +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/2015.html:157 +#: i2p2www/pages/site/about/i2pcon/2015.html:237 +msgid "Video" +msgstr "Video" + +#: i2p2www/pages/site/about/i2pcon/2015.html:158 +#: i2p2www/pages/site/about/i2pcon/2015.html:238 +msgid "Slides" +msgstr "Diapozitiva" + +#: i2p2www/pages/site/about/i2pcon/2015.html:232 +msgid "Day 2" +msgstr "Dita 2" + +#: i2p2www/pages/site/about/i2pcon/index.html:4 +msgid "" +"The first conference dedicated to I2P was held in Toronto on August " +"15-16, 2015.\n" +"See the link below for more information and links to slides and videos." +msgstr "" + +#: i2p2www/pages/site/about/i2pcon/index.html:9 +msgid "Past years" +msgstr "Vitet e shkuara" + +#: i2p2www/pages/site/about/performance/future.html:2 +msgid "Future Performance Improvements" +msgstr "Përmirësime të Ardhshme të Funksionimit" + +#: i2p2www/pages/site/about/performance/future.html:3 +msgid "August 2010" +msgstr "Gusht 2010" + +#: i2p2www/pages/site/about/performance/future.html:7 +msgid "" +"There are a few major techniques that can be done to improve the " +"perceived\n" +"performance of I2P - some of the following are CPU related, others " +"bandwidth\n" +"related, and others still are protocol related. However, all of those\n" +"dimensions affect the latency, throughput, and perceived performance of " +"the\n" +"network, as they reduce contention for scarce resources. This list is of" +" course\n" +"not comprehensive, but it does cover the major ones that are seen." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:15 +#: i2p2www/pages/site/about/performance/index.html:106 +#, python-format +msgid "" +"For past performance improvements see the \n" +"Performance History." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:20 +msgid "Better peer profiling and selection" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:21 +#, python-format +msgid "" +"Probably one of the most important parts of getting faster performance " +"will\n" +"be improving how routers choose the peers that they build their tunnels " +"through\n" +"- making sure they don't use peers with slow links or ones with fast " +"links that\n" +"are overloaded, etc. In addition, we've got to make sure we don't expose" +"\n" +"ourselves to a Sybil attack\n" +"from a powerful adversary with lots of fast machines." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:30 +msgid "Network database tuning" +msgstr "Përimtime baze të dhënash rrjeti" + +#: i2p2www/pages/site/about/performance/future.html:31 +msgid "" +"We're going to want to be more efficient with the network database's " +"healing\n" +"and maintenance algorithms - rather than constantly explore the keyspace " +"for new\n" +"peers - causing a significant number of network messages and router load " +"- we\n" +"can slow down or even stop exploring until we detect that there's " +"something new\n" +"worth finding (e.g. decay the exploration rate based upon the last time " +"someone\n" +"gave us a reference to someone we had never heard of). We can also do " +"some\n" +"tuning on what we actually send - how many peers we bounce back (or even " +"if we\n" +"bounce back a reply), as well as how many concurrent searches we perform." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:42 +msgid "Session Tag Tuning and Improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:43 +#, python-format +msgid "" +"The way the ElGamal/AES+SessionTag " +"algorithm\n" +"works is by managing a set of random one-time-use 32 byte arrays, and " +"expiring\n" +"them if they aren't used quickly enough. If we expire them too soon, " +"we're\n" +"forced to fall back on a full (expensive) ElGamal encryption, but if we " +"don't\n" +"expire them quickly enough, we've got to reduce their quantity so that we" +" don't\n" +"run out of memory (and if the recipient somehow gets corrupted and loses " +"some\n" +"tags, even more encryption failures may occur prior to detection). With " +"some\n" +"more active detection and feedback driven algorithms, we can safely and " +"more\n" +"efficiently tune the lifetime of the tags, replacing the ElGamal " +"encryption with\n" +"a trivial AES operation." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:55 +#, python-format +msgid "" +"Additional ideas for improving Session Tag delivery are described on the\n" +"ElGamal/AES+SessionTag page." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:61 +msgid "Migrate sessionTag to synchronized PRNG" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:62 +#, python-format +msgid "" +"Right now, our ElGamal/AES+SessionTag \n" +"algorithm works by tagging each encrypted message with a unique random \n" +"32 byte nonce (a \"session tag\"), identifying that message as being " +"encrypted \n" +"with the associated AES session's key. This prevents peers from " +"distinguishing \n" +"messages that are part of the same session, since each message has a " +"completely \n" +"new random tag. To accomplish this, every few messages bundle a whole \n" +"new set of session tags within the encrypted message itself, " +"transparently \n" +"delivering a way to identify future messages. We then have to keep track" +" \n" +"of what messages are successfully delivered so that we know what tags \n" +"we may use." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:74 +msgid "" +"This works fine and is fairly robust, however it is inefficient in terms" +" \n" +"of bandwidth usage, as it requires the delivery of these tags ahead of \n" +"time (and not all tags may be necessary, or some may be wasted, due to \n" +"their expiration). On average though, predelivering the session tag costs" +" \n" +"32 bytes per message (the size of a tag). As Taral suggested though, that" +" \n" +"size can be avoided by replacing the delivery of the tags with a " +"synchronized \n" +"PRNG - when a new session is established (through an ElGamal encrypted \n" +"block), both sides seed a PRNG for use and generate the session tags on \n" +"demand (with the recipient precalculating the next few possible values \n" +"to handle out of order delivery)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:87 +msgid "Longer lasting tunnels" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:88 +msgid "" +"The current default tunnel duration of 10 minutes is fairly arbitrary, " +"though\n" +"it \"feels okay\". Once we've got tunnel healing code and more effective" +" failure\n" +"detection, we'll be able to more safely vary those durations, reducing " +"the\n" +"network and CPU load (due to expensive tunnel creation messages)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:95 +msgid "" +"This appears to be an easy fix for high load on the big-bandwidth " +"routers, but\n" +"we should not resort to it until we've tuned the tunnel building " +"algorithms further.\n" +"However, the 10 minute tunnel lifetime is hardcoded in quite a few " +"places,\n" +"so substantial effort would be required to change the duration.\n" +"Also, it would be difficult to maintain backward compatibility with such " +"a change." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:102 +msgid "" +"Currently, since the network average tunnel build success rate is fairly " +"high,\n" +"there are no current plans to extend tunnel lifetime." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:108 +msgid "Adjust the timeouts" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:109 +msgid "" +"Yet another of the fairly arbitrary but \"okay feeling\" things we've got" +" are the\n" +"current timeouts for various activities. Why do we have a 60 second " +"\"peer\n" +"unreachable\" timeout? Why do we try sending through a different tunnel " +"that a\n" +"LeaseSet advertises after 10 seconds? Why are the network database " +"queries\n" +"bounded by 60 or 20 second limits? Why are destinations configured to " +"ask for a\n" +"new set of tunnels every 10 minutes? Why do we allow 60 seconds for a " +"peer to\n" +"reply to our request that they join a tunnel? Why do we consider a " +"tunnel that\n" +"doesn't pass our test within 60 seconds \"dead\"?" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:119 +msgid "" +"Each of those imponderables can be addressed with more adaptive code, as " +"well\n" +"as tunable parameters to allow for more appropriate tradeoffs between\n" +"bandwidth, latency, and CPU usage." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:125 +msgid "Full streaming protocol improvements" +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:128 +msgid "" +"Perhaps re-enable the interactive stream profile (the \n" +"current implementation only uses the bulk stream profile)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:134 +msgid "" +"Client level bandwidth limiting (in either or both directions on a " +"stream, \n" +"or possibly shared across multiple streams). This would be in addition to" +" \n" +"the router's overall bandwidth limiting, of course." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:141 +msgid "" +"Access control lists (only allowing streams to or from certain other " +"known \n" +"destinations)." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:147 +msgid "" +"Web controls and monitoring the health of the various streams, as well \n" +"as the ability to explicitly close or throttle them." +msgstr "" + +#: i2p2www/pages/site/about/performance/future.html:153 +#, python-format +msgid "" +"Additional ideas for improving the streaming library are described on the" +"\n" +"streaming library page." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:2 +msgid "Performance History" +msgstr "Historik Funksionimi" + +#: i2p2www/pages/site/about/performance/history.html:4 +#, python-format +msgid "" +"Notable performance improvements have been made using the techniques " +"below.\n" +"There is more to do, see the Performance " +"page\n" +"for current issues and thoughts." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:10 +msgid "Native math" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:11 +#: i2p2www/pages/site/about/performance/history.html:67 +#: i2p2www/pages/site/about/performance/history.html:82 +#: i2p2www/pages/site/about/performance/history.html:105 +#: i2p2www/pages/site/about/performance/history.html:133 +msgid "implemented" +msgstr "e sendërtuar" + +#: i2p2www/pages/site/about/performance/history.html:12 +#, python-format +msgid "" +"When I last profiled the I2P code, the vast majority of time was spent " +"within\n" +"one function: java.math.BigInteger's\n" +"modPow.\n" +"Rather than try to tune this method, we'll call out to\n" +"GNU MP - an insanely fast math library\n" +"(with tuned assembler for many architectures). (Editor: see\n" +"NativeBigInteger for faster public key " +"cryptography)" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:23 +msgid "" +"\n" +"ugha and duck are working on the C/JNI glue code, and the existing java " +"code\n" +"is already deployed with hooks for that whenever its ready. Preliminary " +"results\n" +"look fantastic - running the router with the native GMP modPow is " +"providing over\n" +"a 800% speedup in encryption performance, and the load was cut in " +"half. This\n" +"was just on one user's machine, and things are nowhere near ready for " +"packaging\n" +"and deployment, yet." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:32 +msgid "Garlic wrapping a \"reply\" LeaseSet" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:33 +msgid "implemented but needs tuning" +msgstr "e sendëruar, por lyp përimtim" + +#: i2p2www/pages/site/about/performance/history.html:34 +msgid "" +"This algorithm tweak will only be relevant for applications that want " +"their\n" +"peers to reply to them (though that includes everything that uses " +"I2PTunnel or\n" +"mihi's ministreaming lib):" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:39 +msgid "" +"Previously, when Alice sent Bob a message, when Bob replied he had to do " +"a\n" +"lookup in the network database - sending out a few requests to get " +"Alice's\n" +"current LeaseSet. If he already has Alice's current LeaseSet, he can " +"instead\n" +"just send his reply immediately - this is (part of) why it typically " +"takes a\n" +"little longer talking to someone the first time you connect, but " +"subsequent\n" +"communication is faster. Currently - for all clients - we wrap\n" +"the sender's current LeaseSet in the garlic that is delivered to the " +"recipient,\n" +"so that when they go to reply, they'll always have the LeaseSet " +"locally\n" +"stored - completely removing any need for a network database lookup on " +"replies.\n" +"This trades off a large portion of the sender's bandwidth for that faster" +" reply.\n" +"If we didn't do this very often,\n" +"overall network bandwidth usage would decrease, since the recipient " +"doesn't\n" +"have to do the network database lookup." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:54 +msgid "" +"For unpublished LeaseSets such as \"shared clients\", this is the only " +"way to\n" +"get the LeaseSet to Bob. Unfortunately this bundling every time adds\n" +"almost 100% overhead to a high-bandwidth connection, and much more to" +"\n" +"a connection with smaller messages." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:60 +msgid "" +"Changes scheduled for release 0.6.2 will bundle the LeaseSet only when\n" +"necessary, at the beginning of a connection or when the LeaseSet changes." +"\n" +"This will substantially reduce the total overhead of I2P messaging." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:66 +msgid "More efficient TCP rejection" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:68 +msgid "" +"At the moment, all TCP connections do all of their peer validation after\n" +"going through the full (expensive) Diffie-Hellman handshaking to " +"negotiate a\n" +"private session key. This means that if someone's clock is really wrong," +" or\n" +"their NAT/firewall/etc is improperly configured (or they're just running " +"an\n" +"incompatible version of the router), they're going to consistently " +"(though not\n" +"constantly, thanks to the banlist) cause a futile expensive cryptographic" +"\n" +"operation on all the peers they know about. While we will want to keep " +"some\n" +"verification/validation within the encryption boundary, we'll want to " +"update the\n" +"protocol to do some of it first, so that we can reject them cleanly\n" +"without wasting much CPU or other resources." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:81 +msgid "Adjust the tunnel testing" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:83 +msgid "" +"Rather than going with the fairly random scheme we have now, we should " +"use a\n" +"more context aware algorithm for testing tunnels. e.g. if we already " +"know its\n" +"passing valid data correctly, there's no need to test it, while if we " +"haven't\n" +"seen any data through it recently, perhaps its worthwhile to throw some " +"data its\n" +"way. This will reduce the tunnel contention due to excess messages, as " +"well as\n" +"improve the speed at which we detect - and address - failing tunnels." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:92 +msgid "Persistent Tunnel / Lease Selection" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:93 +msgid "" +"Outbound tunnel selection implemented in 0.6.1.30, inbound lease " +"selection \n" +"implemented in release 0.6.2." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:97 +msgid "" +"Selecting tunnels and leases at random for every message creates a large" +" \n" +"incidence of out-of-order delivery, which prevents the streaming lib from" +" \n" +"increasing its window size as much as it could. By persisting with the \n" +"same selections for a given connection, the transfer rate is much faster." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:104 +msgid "Compress some data structures" +msgstr "Ngjeshje e disa strukturash të dhënash" + +#: i2p2www/pages/site/about/performance/history.html:106 +msgid "" +"The I2NP messages and the data they contain is already defined in a " +"fairly\n" +"compact structure, though one attribute of the RouterInfo structure is " +"not -\n" +"\"options\" is a plain ASCII name = value mapping. Right now, we're " +"filling it\n" +"with those published statistics - around 3300 bytes per peer. Trivial to" +"\n" +"implement GZip compression would nearly cut that to 1/3 its size, and " +"when you\n" +"consider how often RouterInfo structures are passed across the network, " +"that's\n" +"significant savings - every time a router asks another router for a " +"networkDb\n" +"entry that the peer doesn't have, it sends back 3-10 RouterInfo of them." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:117 +msgid "Update the ministreaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:118 +msgid "replaced by full streaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:119 +msgid "" +"Currently mihi's ministreaming library has a fairly simple stream " +"negotiation\n" +"protocol - Alice sends Bob a SYN message, Bob replies with an ACK " +"message, then\n" +"Alice and Bob send each other some data, until one of them sends the " +"other a\n" +"CLOSE message. For long lasting connections (to an IRC server, for " +"instance),\n" +"that overhead is negligible, but for simple one-off request/response " +"situations\n" +"(an HTTP request/reply, for instance), that's more than twice as many " +"messages as\n" +"necessary. If, however, Alice piggybacked her first payload in with the " +"SYN\n" +"message, and Bob piggybacked his first reply with the ACK - and perhaps " +"also\n" +"included the CLOSE flag - transient streams such as HTTP requests could " +"be\n" +"reduced to a pair of messages, instead of the " +"SYN+ACK+request+response+CLOSE." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:132 +msgid "Implement full streaming protocol" +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:134 +msgid "" +"The ministreaming protocol takes advantage of a poor design decision in " +"the\n" +"I2P client protocol (I2CP) - the exposure of \"mode=GUARANTEED\", " +"allowing what\n" +"would otherwise be an unreliable, best-effort, message based protocol to " +"be used\n" +"for reliable, blocking operation (under the covers, its still all " +"unreliable and\n" +"message based, with the router providing delivery guarantees by garlic " +"wrapping\n" +"an \"ACK\" message in with the payload, so once the data gets to the " +"target, the\n" +"ACK message is forwarded back to us [through tunnels, of course])." +msgstr "" + +#: i2p2www/pages/site/about/performance/history.html:143 +#, python-format +msgid "" +"As I've said, having\n" +"I2PTunnel (and the ministreaming lib) go this route was the best thing " +"that\n" +"could be done, but more efficient mechanisms are available. When we rip " +"out the\n" +"\"mode=GUARANTEED\" functionality, we're essentially leaving ourselves " +"with an\n" +"I2CP that looks like an anonymous IP layer, and as such, we'll be able to" +"\n" +"implement the streaming library to take advantage of the design " +"experiences of\n" +"the TCP layer - selective ACKs, congestion detection, nagle, etc." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:2 +msgid "Performance" +msgstr "Punim" + +#: i2p2www/pages/site/about/performance/index.html:5 +msgid "" +"How does I2P work, why is it slow, and why does it not use my full " +"bandwidth?" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:7 +msgid "" +"Probably one of the most frequent things people ask is \"how fast is " +"I2P?\",\n" +"and no one seems to like the answer - \"it depends\". After trying out " +"I2P, the\n" +"next thing they ask is \"will it get faster?\", and the answer to that is" +" a most\n" +"emphatic yes." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:14 +msgid "" +"I2P is a full dynamic network. Each client is known to other nodes and " +"tests local known nodes for reachability and capacity.\n" +"Only reachable and capable nodes are saved to a local NetDB (This is " +"generally only a portion of the network, around 500-1000).\n" +"When I2P builds tunnels, it selects the best resource from this pool. For" +" example, a small subset of 20-50 nodes are only available to build " +"tunnels with.\n" +"Because testing happens every minute, the pool of used nodes changes " +"every minute.\n" +"Each I2P node knows a different part of the net, meaning that each router" +" has a different set of I2P nodes to be used for tunnels.\n" +"Even if two routers have the same subset of known nodes, the tests for " +"reachability and capacity will likely show different results, as the " +"other routers could be under load just as one router tests, but be free " +"if the second router tests." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:23 +msgid "" +"The above describes why each I2P node has different nodes to build " +"tunnels.\n" +"Because every I2P node has a different latency and bandwith, tunnels " +"(which are built via those nodes) have different latency and bandwidth " +"values.\n" +"And because every I2P node has different tunnels built, no two I2P nodes " +"have the same tunnel sets." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:29 +msgid "" +"A server/client is known as a \"destination\" and each destination has at" +" least one inbound and one outbound tunnel. The default is 3 hops per " +"tunnel.\n" +"This adds up to 12 hops (aka 12 different I2P nodes) for a full roundtrip" +" client-server-client." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:34 +msgid "" +"Each data package is sent through 6 other I2P nodes until it reaches the " +"server:" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:40 +msgid "and on way back 6 different I2P nodes:" +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:47 +msgid "" +"As most traffic on I2P (www, torrent,...) needs ack packages until new " +"data is sent, it needs to wait until a ack package returns from the " +"server.\n" +"In the end: send data, wait for ack, send more data, wait for ack,..\n" +"As the RTT (RoundTripTime) adds up from the latency of each individual " +"I2P node and each connection on this roundtrip, it takes usually 1-3 " +"seconds until a ack package comes back to the client.\n" +"With some internals of TCP and I2P transport, a data package has a " +"limited size and cannot be as large as we want it to be.\n" +"Together these conditions set a limit of max bandwidth per tunnel of " +"20-50 kbyte/sec.\n" +"But if ONLY ONE hop in the tunnel has only 5 kb/sec bandwidth to spend, " +"the whole tunnel is limited to 5 kb/sec, independent of the \n" +"latency and other limitations." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:57 +msgid "" +"Due to encryption used and other setups in I2P (howto built up tunnels, " +"latency, ...) it is quite expensive in CPU time to build a tunnel. This " +"is \n" +"why a destination is only allowed to have a max of 6 IN and 6 OUT tunnels" +" to transport data. With a max of 50 kb/sec per tunnel, a destination " +"could \n" +"use roughly 300 kb/sec traffic combined ( in reality it could be more if " +"shorter tunnels are used with low or no anonymity available).\n" +"Used tunnels are discarded every 10 minutes and new ones are built up.\n" +"This change of tunnels (and sometimes clients that shutdown hard due to " +"usage of \"shut down at once\" or situations where there is power loss) " +"does \n" +"sometimes break tunnels and connections, as seen on the IRC2P Network in " +"loss of connection (ping timeout) or on when using eepget." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:66 +msgid "" +"With a limited set of destinations and a limited set of tunnels per " +"destination, one I2P node only uses a limited set of tunnels across other" +" I2P nodes.\n" +"For example, if an I2P node is \"hop1\" in the small example above, we " +"only see 1 participating tunnel originating from the client.\n" +"If we sum up the whole I2P network, only a rather limited number of " +"participating tunnels could be built with a limited amount of bandwidth " +"all together.\n" +"If one distributes these limited numbers across the number of I2P nodes, " +"there is only a fraction of available bandwidth/capacity available for " +"use." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:73 +msgid "" +"To remain anonymous one router should not be used by the whole network " +"for building tunnels.\n" +"If one router does act as a tunnel router for ALL I2P nodes, it becomes a" +" very real central point of failure as well as a central point to grab " +"IPs and data from the clients. This is not good.\n" +"I2P attempts to spread the load across a lot of I2P nodes because of this" +" reason." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:79 +msgid "" +"Another point is the full mesh network. Each connection hop-hop utilizes " +"one TCP or UDP connection on the I2P nodes. With 1000 connections, one " +"sees \n" +"1000 TCP connections. That is quite a lot and some home and small office " +"routers (DSL, cable,..) only allow a small number of connections (or just" +" go mad if you use more than X connections).\n" +"I2P tries to limit these connections to be under 1500 per UDP and per TCP" +" type.\n" +"This limits the amount of traffic routed across your I2P node as well." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:86 +msgid "" +"In summary, I2P is very complex and there is no easy way to pinpoint why " +"your node is not used.\n" +"If your node is reachable and has a bandwidth setting of >128 kbyte/sec " +"shared and is reachable 24/7, it should be used after some time for " +"participating traffic.\n" +"If it is down in between, the testing of your I2P node done by other " +"nodes will tell them: you are not reachable. This blocks your node for at" +" least \n" +"24h on other nodes. So, the other nodes which tested you as down will not" +" use your node for 24h for building tunnels. This is why your traffic " +"will \n" +"be lower after a restart/shutdown for a minimum of 24h." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:94 +msgid "" +"Also: other I2P nodes needs to know your I2P router to test it for " +"reachability and capacity. It takes time for other nodes to get known to " +"your node. \n" +"It will be faster if you use I2P and build more tunnels, e.g. use a " +"torrent or www for some time." +msgstr "" + +#: i2p2www/pages/site/about/performance/index.html:99 +msgid "Performance Improvements" +msgstr "Përmirësime Funksionimi" + +#: i2p2www/pages/site/about/performance/index.html:101 +#, python-format +msgid "" +"For possible future performance improvements see\n" +"Future Performance Improvements." +msgstr "" +