Files
i2p.www/i2p2www/translations/ja/LC_MESSAGES/about.po
2024-07-08 17:29:07 -04:00

2602 lines
104 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Japanese translations for I2P.
# Copyright (C) 2022 ORGANIZATION
# This file is distributed under the same license as the I2P project.
#
# Translators:
# kami <b52c55627324b29125cbcfb101258463_228943>, 2015-2016
# daingewuvzeevisiddfddd, 2022-2024
# タカハシ, 2014
# タカハシ, 2022
# rafe <rafe.kun@gmail.com>, 2015
# daingewuvzeevisiddfddd, 2020-2021
# daingewuvzeevisiddfddd, 2021
msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2022-08-21 15:32+0000\n"
"PO-Revision-Date: 2013-07-15 11:59+0000\n"
"Last-Translator: daingewuvzeevisiddfddd, 2022-2024\n"
"Language-Team: Japanese (http://app.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/about/alternative-clients.html:2
#: i2p2www/pages/site/about/alternative-clients.html:4
msgid "Alternative I2P clients"
msgstr "代替のI2Pクライアント"
#: 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 "メインのI2PクライアントはJavaを使って実装されています。もし、あなたのデバイスでJavaを使えないなら、コミュニティの一員によって開発された代替実装があります。"
#: i2p2www/pages/site/about/alternative-clients.html:12
#, python-format
msgid ""
"<a href=\"%(i2pd)s\">i2pd</a> is a I2P client implementation in C++.\n"
"As of early 2016, i2pd has become stable enough to be used in \n"
"production, and since summer 2016 it fully implements all I2P APIs."
msgstr ""
"<a href=\"%(i2pd)s\">i2pd</a>はC++で実装されたI2Pクライアントです。\n"
"2016年初頭の時点で、i2pdは本番で使えるほど安定し、2016年夏以降のすべてのI2P APIを完全に実装しています。"
#: i2p2www/pages/site/about/alternative-clients.html:19
#, python-format
msgid ""
"<a href=\"%(kovri)s\">Kovri</a> is active i2pd fork developed for Monero "
"cryptocurrency."
msgstr "<a href=\"%(kovri)s\">Kovri</a>は暗号通貨Monero用に開発された、i2pdの活発なフォークです。"
#: i2p2www/pages/site/about/alternative-clients.html:24
#, python-format
msgid ""
"<a href=\"%(go_i2p)s\">Go-I2P</a> is I2P client developed using the\n"
"<a href=\"%(golang)s\">Go</a> programming language. The project is in "
"early development."
msgstr ""
"<a href=\"%(go_i2p)s\">Go-I2P</a>はプログラミング言語<a "
"href=\"%(golang)s\">Go</a>を使用して開発されたクライアントです。プロジェクトは初期開発段階にあります。"
#: i2p2www/pages/site/about/browser-config.html:2
msgid "Web Browser Configuration"
msgstr "ウェブサーバー設定"
#: i2p2www/pages/site/about/glossary.html:2
msgid "Glossary"
msgstr "用語集"
#: i2p2www/pages/site/about/glossary.html:4
msgid ""
"This table lists often-used terminology when discussing I2P and "
"cryptography."
msgstr "このテーブルは、I2Pや暗号を議論する際によく使われる用語のリストです。"
#: i2p2www/pages/site/about/glossary.html:9
msgid ""
"I2P: Invisible Internet Project: a project meant to\n"
" provide an anonymity layer, so user can communicate anonymously "
"using a\n"
" range of applications."
msgstr ""
"I2P: 不可視なインターネットプロジェクト: 匿名のレイヤーを提供する\n"
" という趣旨のプロジェクトで、ユーザーが様々なアプリケーションを使用して\n"
" 匿名に通信できるようにするものです。"
#: i2p2www/pages/site/about/glossary.html:12
msgid ""
"Router: The core I2P software, which routes encrypted\n"
" packets on the I2P network. All routers by default participate in"
" the\n"
" network, which both helps the network and provides cover traffic "
"for any\n"
" clients or servers connecting to the I2P network through the\n"
" router."
msgstr ""
"ルーター: コアとなるI2Pソフトウェアで、I2Pネットワーク上の暗号化\n"
" されたパケットを運びます。デフォルトで全てのルーターがネットワークに\n"
" 参加しており、ネットワークの助けとなるとともにルーターを通じてI2P\n"
" ネットワークに繋がるクライアントやサーバーに隠しトラフィックを提供\n"
" しています。"
#: i2p2www/pages/site/about/glossary.html:17
msgid ""
"RouterIdentity: A collection of information required to\n"
" communicate directly with a router, such as its IP address and "
"listening\n"
" port, public signing and encryption keys etc."
msgstr ""
"ルーターアイデンティティ: ルーターと直接通信するのに必要な情報の\n"
" 集まりで、例えばIPアドレスやリッスンしているポート\n"
" 公開署名鍵と暗号鍵のことです。"
#: i2p2www/pages/site/about/glossary.html:20
msgid ""
"Tunnel: An anonymous communication pathway between a\n"
" client or server and the I2P network. Tunnels are unidirectional,"
" so any\n"
" one client or server must have at least two Tunnels - one for "
"inbound\n"
" traffic and one for outbound traffic."
msgstr ""
"トンネル: クライアントやサーバーとI2Pネットワーク間の\n"
" 匿名通信経路です。トンネルは一方通行でなので、あるクライアント\n"
" またはサーバーには最低二つのトンネルが必要です。着信トラフィック\n"
" に一つ、送信トラフィックに一つです。"
#: i2p2www/pages/site/about/glossary.html:24
msgid ""
"Destination: The cryptographic identity of a tunnel.\n"
" These are the identities of clients and servers within the I2P "
"network,\n"
" and are analogous to the IP:port of a computer on the normal\n"
" internet."
msgstr ""
"宛先: トンネルの暗号化されたアイデンティティです。\n"
" I2Pネットワーク内のクライアントやサーバーのアイデンティティで\n"
" 通常のインターネット上のコンピューターのIP:ポート番号\n"
" に相当します。"
#: i2p2www/pages/site/about/glossary.html:28
msgid ""
"LeaseSet: A collection of information required to\n"
" communicate with a client or server at a particular Destination, "
"such as\n"
" the gateways of the inbound Tunnels for that\n"
" Destination."
msgstr ""
"リースセット: 特定の宛先のクライアントやサーバーと通信するのに\n"
" 必要な情報の集まりで、例えば、その宛先に対する\n"
" 着信トンネルのゲートウェイのようなものが\n"
" 当てはまります。"
#: i2p2www/pages/site/about/glossary.html:34
msgid ""
"This table lists definition of different networks and their components. "
"These\n"
"terms and the definitions provided are taken from\n"
"<a href=\"https://decentpatterns.xyz/report/#key-terms\">Decentralization"
" Off The\n"
"Shelf: 7 Maxims by Simply Secure</a>(used with permission)."
msgstr ""
"この表は、様々なネットワークやコンポーネントの定義を一覧にしたものです。\n"
"用語や定義は下記より引用したものです。\n"
"<a href=\"https://decentpatterns.xyz/report/#key-terms\">Decentralization"
" Off The\n"
"Shelf: 7 Maxims by Simply Secure</a>(許可を得て使用)"
#: i2p2www/pages/site/about/glossary.html:40
msgid ""
"Decentralization: Network architecture that avoids\n"
" reliance on a single party. Encompasses peer-to-peer, blockchain,"
"\n"
" federated, and distributed technologies that involve many "
"individual\n"
" users."
msgstr ""
"非中央集権化: 一つの当事者への依存を避けたネットワークの\n"
" アーキテクチャ。ピアツーピアやブロックチェーン、フェデレーション、\n"
" 多くの個々のユーザーを伴う分散型技術を含みます。"
#: i2p2www/pages/site/about/glossary.html:44
msgid ""
"Peer-to-Peer (p2p): Peers make a portion of their \n"
" resources, such as processing power, disk storage or network "
"bandwidth,\n"
" directly available to other network participants, without the "
"need for\n"
" central coordination by servers or stable hosts. Popularized by\n"
" BitTorrent, Napster, and Bitcoin."
msgstr ""
"ピアツーピア (p2p): ピアは、処理能力、ディスクストレージ、ネットワーク\n"
"帯域幅などのリソースの一部を、サーバーや安定したホストによる中央調整を必要とせず、他のネットワーク参加者が直接利用できるようにします。BitTorrent、Napster、Bitcoinによって有名になりました。"
" "
#: i2p2www/pages/site/about/glossary.html:49
msgid ""
"Federated: Federation allows separate deployments of a\n"
" service to communicate with each other through a common protocol,"
" for\n"
" instance a mail server run by Google federates with a mail server"
" run by\n"
" Microsoft when you send an email from @gmail.com to @hotmail.com."
"\n"
" Each deployment may host multiple users."
msgstr ""
"フェデレーション: フェデレーションは、あるサービスの別々のデプロイメントが\n"
" 共通のプロトコルを介して互いに通信することを可能にします。例えば、\n"
" @gmail.comから@hotmail.comにメールを送るとき、Googleが運営するメール\n"
" サーバーはMicrosoftが運営するメールサーバーとフェデレートしています。\n"
" 各デプロイメントは、複数のユーザーをホストすることができます。"
#: i2p2www/pages/site/about/glossary.html:54
msgid ""
"Blockchain: A distributed ledger that can record\n"
" transactions between multiple parties efficiently and in a "
"verifiable\n"
" and permanent way."
msgstr ""
"ブロックチェーン: 複数の参加者の間のトランザクションを\n"
" 検証可能かつ永続的な方法で効率的に記録\n"
" できる分散台帳です。"
#: i2p2www/pages/site/about/glossary.html:57
msgid ""
"Distributed systems: Academic topic within the\n"
" discipline of Computer Science which is concerned with the design"
" of\n"
" computer systems that consist of many individual computers "
"connected\n"
" over a network. Peer-to-peer networks and blockchains are "
"examples of\n"
" distributed systems architectures."
msgstr ""
"分散型システム: コンピュータサイエンス分野内の学術的トピックで、\n"
" ネットワーク越しに接続された多くの個々のコンピューターで構成\n"
" されるコンピューターシステムの設計に関するものです。ピアツーピア\n"
" ネットワークやブロックチェーンは、分散システムアーキテクチャ\n"
" の例になります。"
#: i2p2www/pages/site/about/glossary.html:62
msgid ""
"TCP/UDP: The two foundational transport protocols used\n"
" on the Internet. Common protocols used to send data between two\n"
" computers."
msgstr ""
"TCP/UDP: インターネット上で使用されている二つの主要\n"
" トランスポートプロトコルです。二つのコンピューター間でデータを\n"
" 送信するのに使われる一般的なプロトコルです。"
#: i2p2www/pages/site/about/glossary.html:65
msgid ""
"DHT: Distributed hash table, used in some projects to\n"
" connect peers to each other by storing information in the form of"
"\n"
" key-value pairs in a distributed manner."
msgstr ""
"DHT: 分散ハッシュテーブルのことで、一部のプロジェクトで分散される形で\n"
" キーバリュー型のペアの形式で情報を保存することによって\n"
" ピアを互いに接続するために使用されています。"
#: i2p2www/pages/site/about/glossary.html:68
msgid ""
"IP address: A number of a computer or network which is\n"
" unique and thus can be used to address it."
msgstr ""
"IPアドレス: コンピューターやネットワークに一意の数値で\n"
" それゆえにアドレスとして示すのに使えます。"
#: i2p2www/pages/site/about/glossary.html:70
msgid ""
"WebRTC: A protocol standard for establishing connections\n"
" in a web browser where data passes directly between\n"
" users."
msgstr ""
"WebRTC: ウェブブラウザで接続を確立させるプロトコルの\n"
" 基準で、データを直接ユーザー間で受け渡します。"
#: i2p2www/pages/site/about/glossary.html:73
msgid ""
"Hash: A number, usually displayed as a string of letters\n"
" and numbers. It can serve as a fingerprint uniquely identifying"
"\n"
" data."
msgstr ""
"ハッシュ: 通常、文字と数字の文字列で表示される数値。\n"
" データを一意に識別する「指紋」として機能します。"
#: i2p2www/pages/site/about/glossary.html:76
msgid ""
"UX: User experience, the overall experience of a person\n"
" using a product or a service, especially in terms of how easy it "
"is to\n"
" use."
msgstr ""
"UX: ユーザーエクスペリエンスのことで、特に使いやすさの観点から見た\n"
" あるプロダクトやサービスを使用している人の経験全体を指す。"
#: 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 "I2Pに寄付してくれた人たちにとても感謝します"
#: i2p2www/pages/site/about/hall-of-fame.html:13
#, python-format
msgid ""
"If you have made a donation, please send an email to <a "
"href=\"mailto:%(echelon)s\">echelon</a>\n"
"with your name or nick (and optionally homepage) so we can list you here."
msgstr ""
"もしあなたが寄付をしたいならば<a href=\"mailto:%(echelon)s\">echelon</a>までメールを送信してください\n"
"あなたの名前、またはニックネーム(あればホームページ)をここのリストに追加します"
#: 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 "2004年3月から2019年3月までの15年間のI2Pの歴史における寄付者の、整理されていない一覧です。"
#: i2p2www/pages/site/about/intro.html:2
#: i2p2www/pages/site/about/software.html:2
msgid "Intro"
msgstr "紹介"
#: i2p2www/pages/site/about/intro.html:4
msgid "The Invisible Internet Project"
msgstr "不可視なインターネットプロジェクト"
#: i2p2www/pages/site/about/intro.html:6
msgid ""
"The Invisible Internet Project (I2P) is a fully encrypted private network"
" layer that has been developed with privacy and security by design in "
"order to provide protection for your activity,\n"
"location and your identity. The software ships with a router that "
"connects you to the network and applications for sharing, communicating "
"and building."
msgstr "不可視なインターネットプロジェクト(I2P)は完全に暗号化されたプライベートネットワーク層であり、あなたの活動、位置情報、および身元に保護を提供するために、プライバシーとセキュリティを考慮して設計されています。ソフトウェアには、ネットワークに接続するルーターと、共有・通信・ビルディングのためのアプリケーションが内蔵されています。"
#: i2p2www/pages/site/about/intro.html:9
msgid "I2P Cares About Privacy"
msgstr "I2Pはプライバシーを大切にします"
#: i2p2www/pages/site/about/intro.html:11
msgid ""
"I2P hides the server from the user and the user from the server. All I2P "
"traffic is internal to the I2P network. Traffic inside I2P does not "
"interact with the Internet directly. It is a layer on top of the "
"Internet. It uses encrypted unidirectional tunnels between you and your "
"peers. No one can see where traffic is coming from, where it is going, or"
" what the contents are. Additionally I2P offers resistance to pattern "
"recognition and blocking by censors. Because the network relies on peers "
"to route traffic, location blocking is also reduced."
msgstr "I2Pは、サーバーからユーザー、及びユーザーからサーバーを隠します。全てのI2PトラフィックはI2Pネットワークの内部にあります。I2P内部のトラフィックは、インターネットと直接やりとりすることはありません。それはインターネットの上にある層です。あなたとあなたのピアの間で暗号化された一方向トンネルを使用します。トラフィックがどこから来ているのか、どこに向かっているのか、またはどんな内容かは誰も見ることができません。また、I2Pはパターン認識や検閲によるブロックに強いという特徴があります。なぜなら、ネットワークはトラフィックをルーティングするためにピアに頼るため、ロケーションブロッキングも減少します。"
#: i2p2www/pages/site/about/intro.html:14
msgid "How to Connect to the I2P Network"
msgstr "I2Pネットワークに接続する方法"
#: i2p2www/pages/site/about/intro.html:16
msgid ""
"The Invisible Internet Project provides software to download that "
"connects you to the network. In addition to the network privacy benefits,"
" I2P provides an application layer that allows people to use and create "
"familiar apps for daily use. I2P provides its own unique DNS so that you "
"can self host or mirror content on the network. You can create and own "
"your own platform that you can add to the I2P directory or only invite "
"your friends. The I2P network functions the same way the Internet does. "
"When you download the I2P software, it includes everything you need to "
"connect, share, and create privately."
msgstr ""
"不可視なインターネットプロジェクトでは、ネットワークに接続するソフトウェアをダウンロードできます。ネットワークのプライバシーのメリットに加え、I2P"
" は人々が日常的に慣れ親しんだアプリを使用したり作成したりすることができるアプリケーションレイヤーを提供します。I2P には独自の DNS "
"があるので、自分でネットワーク上でコンテンツをホストしたりミラーしたりすることができます。I2P "
"のディレクトリに追加したり、友人だけを招待したりする自分のプラットフォームを作成および保有することができます。I2P "
"ネットワークの機能は、インターネットの機能と同じです。I2P "
"ソフトウェアをダウンロードする時、プライベートに接続、共有、作成するのに必要な全てが含まれています。"
#: i2p2www/pages/site/about/intro.html:18
msgid "An Overview of the Network"
msgstr "ネットワークの概要"
#: i2p2www/pages/site/about/intro.html:20
msgid ""
"I2P uses cryptography to achieve a variety of properties for the tunnels "
"it builds and the communications it transports. I2P tunnels use "
"transports, NTCP2 and SSU, to hide the nature of the traffic being "
"transported over it. Connections are encrypted from router-to-router, and"
" from client-to-client(end-to-end). Forward-secrecy is provided for all "
"connections. Because I2P is cryptographically addressed, I2P addresses "
"are self-authenticating and only belong to the user who generated them."
msgstr ""
"I2P は作成するトンネルとトンネルが運ぶ通信の様々な特性を達成するため、暗号を使用しています。I2P トンネルはトランスポートと NTCP2 と"
" SSU "
"を使用しており、その上を行き交うトラフィックの性質を秘匿します。接続はルーターツールーター、クライアントツークライアントエンドツーエンドで暗号化されています。前方秘匿性は全ての接続に対して提供されます。I2P"
" のアドレスは暗号化されているので、I2P アドレスは自己認証され、生成したユーザーにのみ属します。"
#: i2p2www/pages/site/about/intro.html:23
msgid ""
"I2P is a secure and traffic protecting Internet-like layer. The network "
"is made up of peers (\"routers\") and unidirectional inbound and outbound"
" virtual tunnels. Routers communicate with each other using protocols "
"built on existing transport mechanisms (TCP, UDP, etc), passing messages."
" Client applications have their own cryptographic identifier "
"(\"Destination\") which enables it to send and receive messages. These "
"clients can connect to any router and authorize the temporary allocation "
"(\"lease\") of some tunnels that will be used for sending and receiving "
"messages through the network. I2P has its own internal network database "
"(using a modification of the Kademlia DHT) for distributing routing and "
"contact information securely."
msgstr ""
"I2P "
"はセキュアかつトラフィックを保護するインターネットに似たレイヤーです。ネットワークはピア「ルーター」と一方方向の着信・送信仮想トンネルからなります。ルーターは既存のトランポートメカニズムTCP、UDPなどに基づくプロトコルを使用して互いに通信し、メッセージをやりとりします。クライアントがメッセージを受信します。これらのクライアントはどのルーターにも接続でき、ネットワークを経由したメッセージの送受信に使用されるトンネルの一部の一時的な割り当て「リース」の承認を受けられます。I2P"
" には、せキュアにルート形成とコンタクト情報を配布するための独自の内部ネットワークデータベースKademlia DHTの改変を使用があります。"
#: i2p2www/pages/site/about/intro.html:26
msgid "About Decentralization and I2P"
msgstr "非中央集権化と I2P について"
#: i2p2www/pages/site/about/intro.html:28
msgid ""
"The I2P network is almost completely decentralized, with exception to "
"what are called \"Reseed Servers,\" which is how you first join the "
"network. This is to deal with the DHT ( Distributed Hash Table ) "
"bootstrap problem. Basically, there's not a good and reliable way to get "
"out of running at least one permanent bootstrap node that non-network "
"users can find to get started. Once you're connected to the network, you "
"only discover peers by building \"exploratory\" tunnels, but to make your"
" initial connection, you need to get a peer set from somewhere. The "
"reseed servers, which you can see listed on "
"http://127.0.0.1:7657/configreseed in the Java I2P router, provide you "
"with those peers. You then connect to them with the I2P router until you "
"find one who you can reach and build exploratory tunnels through. Reseed "
"servers can tell that you bootstrapped from them, but nothing else about "
"your traffic on the I2P network."
msgstr ""
"I2P ネットワークは、「再シードサーバー」と呼ばれるネットワークに初めて参加する手段を除いて、ほぼ完全に非中央集権化されています。これは、DHT"
" (分散ハッシュテーブル) "
"ブートストラップ問題で論じられます。要するに、非ネットワーク利用者が開始される方法を見つける、少なくとも1個の常設ブートストラップードの稼働をさせる、良くなく、信頼できない方法です。一度ネットワークに接続すると、「調査」トンネルを構築することによってのみピアを発見しますが、最初の接続をするとき、どこかからピアの組み合わせを入手する必要があります。再シードサーバー一覧は"
" Java I2P ルーター内の http://127.0.0.1:7657/configreseed "
"上に記載され、確認でき、これらのピアを提供します。そして、I2Pルーターで接続し、到達して調査トンネルを構築できる人を見つけるまで、それらに接続します。再シードサーバーは、あなたがそこからブートストラップしたことを知ることができますが、I2P"
" ネットワーク上のあなたのトラフィックについては、それ以外のことはわかりません。"
#: i2p2www/pages/site/about/intro.html:30
msgid ""
"I see IP addresses of all other I2P nodes in the router console. Does "
"that mean my IP address is visible by others?"
msgstr "ルーターコンソールからほかのすべてのI2PードのIPアドレスが見えます。つまり私のIPアドレスも他者から見えていますか"
#: i2p2www/pages/site/about/intro.html:32
msgid ""
"Yes, this is how a fully distributed peer-to-peer network works. Every "
"node participates in routing packets for others, so your IP address must "
"be known to establish connections. While the fact that your computer runs"
" I2P is public, nobody can see your activities in it. You can't say if a "
"user behind this IP address is sharing files, hosting a website, doing "
"research or just running a node to contribute bandwidth to the project."
msgstr ""
"はい、これは分散ピアツーピアネットワークとして機能します。全ードは他のードにパケットをルーティングする参加者であり、そのため接続を確立するには、IP"
" アドレスを知る必要があります。あなたのコンピューターが I2P "
"を実行しているという事実は公開されますが、その中でのあなたの活動は誰にも見ることができません。この IP "
"アドレスの背後にいる利用者が、ファイルを共有しているのか、ウェブサイトをホストしているのか、研究をしているのか、それともプロジェクトに帯域幅を提供するためにノードを運営しているだけなのか、判断することはできません。"
#: i2p2www/pages/site/about/intro.html:34
msgid "What I2P Does Not Do"
msgstr "I2P がしないこと"
#: i2p2www/pages/site/about/intro.html:36
msgid ""
"The I2P network does not officially \"Exit\" traffic. It has outproxies "
"to the Internet run by volunteers, which are centralized services. I2P is"
" primarily a hidden service network and outproxying is not an official "
"function, nor is it advised. The privacy benefits you get from "
"participating in the the I2P network come from remaining in the network "
"and not accessing the internet. I2P recommends that you use Tor Browser "
"or a trusted VPN when you want to browse the Internet privately."
msgstr ""
"I2P "
"ネットワークは公式には「出口」トラフィックではありません。それはアウトプロキシと呼ばれ、中央集権なサービスで、有志によって稼働され、インターネットに出ます。I2P"
" "
"は第一に秘匿サービスネットワークであり、アウトプロキシは公式の機能ではなく、推奨もしていません。プライバシーがあなたに与える便益は、インターネットにアクセスせずにネットワーク内に留まり続けることにより生じ、I2P"
" ネットワーク内に参加することで得られます。インターネットをプライベートに閲覧したいならば、Tor ブラウザまたは信用されたVPNを使用することを"
" I2P は推奨します。"
#: i2p2www/pages/site/about/intro.html:38
msgid "Comparisons"
msgstr "対照"
#: i2p2www/pages/site/about/intro.html:40
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"
"<a href=\"http://freehaven.net/anonbib/topic.html\">Anonymity "
"Bibliography</a>\n"
"and GNUnet's <a href=\"https://www.gnunet.org/links/\">related "
"projects</a>\n"
"serve that purpose well. That said, a few systems stand out for further\n"
"comparison. The following have individual comparison pages:"
msgstr ""
"他にも匿名通信に取り組んでいるアプリケーションやプロジェクトは非常に多く、I2P はそれら\n"
"の努力の多くに触発を受けています。これは匿名リソースの包括的な一覧ではありませんが、freehavenの <a "
"href=\"http://freehaven.net/anonbib/topic.html\">Anonymity "
"Bibliography</a> とGNUnetの<a "
"href=\"https://www.gnunet.org/links/\">関連プロジェクト</a>がその目的を十分に果たしています。とはいえ、いくつかのシステムは際立っており、詳細な比較ができます。以下は、個別の比較ページがあるものです。"
#: i2p2www/pages/site/about/intro.html:56
#, python-format
msgid ""
"The following are discussed on the <a href=\"%(othernetworks)s\">other "
"networks page:</a>"
msgstr "下記は<a href=\"%(othernetworks)s\">他のネットワークのページ</a>で議論されています:"
#: i2p2www/pages/site/about/media.html:2
msgid "Presentations on I2P"
msgstr "I2Pに関するプレゼンテーション"
#: 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 <a "
"href=\"%(papers)s\">here</a>."
msgstr ""
"以下は、プレゼンテーション、ビデオ、及びチュートリアルのリンクです。I2Pに関する研究論文は<a "
"href=\"%(papers)s\">こちら</a>です。"
#: i2p2www/pages/site/about/media.html:8
#, python-format
msgid "To request an addition to this page, please send to %(email)s."
msgstr "このページへの追加の要望は、%(email)sにご連絡ください。"
#: i2p2www/pages/site/about/media.html:11
msgid ""
"\n"
"Newest links are at the bottom of each section."
msgstr ""
"\n"
"最新のリンクは各節の下部にあります。"
#: 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"
"<a href=\"%(mp3)s\">MP3 audio</a>\n"
"<a href=\"%(transcript)s\">transcript</a>\n"
"Lance James (0x90), February 2002."
msgstr ""
#: i2p2www/pages/site/about/media.html:27
#, python-format
msgid ""
"IIP Presentation at ToorCon\n"
"<a href=\"%(mp3)s\">MP3 audio</a>\n"
"<a href=\"%(slides)s\">slides</a>\n"
"Lance James (0x90), September 2002."
msgstr ""
#: i2p2www/pages/site/about/media.html:35
#, python-format
msgid ""
"<a href=\"%(video)s\">To Be or I2P</a>\n"
"(Youtube Video)\n"
"An introduction into anonymous communication with I2P.\n"
"<a href=\"%(pdf)s\">To Be or I2P (PDF presentation)</a>,\n"
"Jens Kubieziel, 24C3 Berlin, December 28, 2007."
msgstr ""
#: i2p2www/pages/site/about/media.html:44
#, python-format
msgid ""
"<a href=\"%(video)s\">Video of I2P talk at Chemnitz Linux Tag</a>,\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"
"<a href=\"%(mp3)s\">MP3 audio</a>\n"
"<a href=\"%(vid)s\">Youtube Video</a> (I2P part at 44 minutes)"
msgstr ""
#: i2p2www/pages/site/about/media.html:57
#, python-format
msgid ""
"<a href=\"%(link)s\">Into the I2P Darknet: Welcome to Cipherspace</a>\n"
"Adrian Crenshaw. Schmoocon Firetalk, January 2011"
msgstr ""
#: i2p2www/pages/site/about/media.html:62
#, python-format
msgid ""
"<a href=\"%(link)s\">Using techhnology to advance liberty</a>\n"
"(Youtube Video)\n"
"Eric Johnson.\n"
"<a href=\"http://agora.io/etienne\">Agora I/O Unconference</a>, March 27,"
" 2011.\n"
"I2P covered from 10:00 to 20:00 in the video."
msgstr ""
#: i2p2www/pages/site/about/media.html:70
#, python-format
msgid ""
"<a href=\"%(link)s\">Common Darknet Weaknesses</a>\n"
"(Youtube Video)\n"
"Adrian Crenshaw, <a href=\"http://aide.marshall.edu/\">AIDE</a>, July "
"11-15, 2011."
msgstr ""
#: i2p2www/pages/site/about/media.html:76
#, python-format
msgid ""
"<a href=\"%(link)s\">I2P / Tor Workshop Notes</a>\n"
"Adrian Crenshaw. DEF CON 19, Las Vegas, August 6, 2011."
msgstr ""
#: i2p2www/pages/site/about/media.html:81
#, python-format
msgid ""
"<a href=\"%(live)s\">Cipherspaces/Darknets: An Overview Of Attack "
"Strategies -\n"
"DEF CON Live version (Youtube Video)</a>,\n"
"<a href=\"%(studio)s\">\"Studio\" version (Youtube Video)</a>,\n"
"<a href=\"%(slides)s\">Slides (ppt)</a>\n"
"Adrian Crenshaw. DEF CON 19, Las Vegas, August 7, 2011."
msgstr ""
#: i2p2www/pages/site/about/media.html:91
msgid ""
"<a href=\"http://0x375.org/\">Modern cipherspace ecosystems</a>, 0x375 "
"0x06 (Thessaloniki Tech Talk Sessions), November 4, 2011."
msgstr ""
#: i2p2www/pages/site/about/media.html:95
#, python-format
msgid ""
"<a href=\"%(link)s\">I2P - The Anonymous Network</a>\n"
"(Youtube Video)\n"
"Blair Dick, University of Abertay, Dundee Ethical Hacking Society, "
"January 25, 2012."
msgstr ""
#: i2p2www/pages/site/about/media.html:101
#, python-format
msgid ""
"<a href=\"%(link)s\">I2PCon 2015</a>\n"
"Toronto, August 15-16, 2015"
msgstr ""
"<a href=\"%(link)s\">I2PCon 2015</a>\n"
"トロント、2015年8月15-16日"
#: i2p2www/pages/site/about/media.html:106
#, python-format
msgid ""
"<a href=\"%(link)s\">I2P - Still alive! (pdf)</a>\n"
"<a href=\"%(link2)s\">(video)</a>\n"
"echelon, 32C3 (You Broke the Internet Assembly), Hamburg, December 28, "
"2015"
msgstr ""
#: i2p2www/pages/site/about/media.html:113
#, python-format
msgid ""
"Replacing Weary Crypto: Upgrading the I2P network with stronger "
"primitives\n"
"<a href=\"%(link)s\">(pdf)</a>\n"
"<a href=\"%(link2)s\">(odp)</a>\n"
"str4d, Real World Crypto, Stanford, January 8, 2016"
msgstr ""
#: i2p2www/pages/site/about/media.html:121
#, python-format
msgid ""
"Onions and Garlic: the protocols of I2P\n"
"<a href=\"%(link)s\">(pdf)</a>\n"
"<a href=\"%(link2)s\">(odp)</a>\n"
"str4d, COMPSCI 460: Computer Networking, University of Wisconsin "
"Whitewater, February 17, 2016"
msgstr ""
#: i2p2www/pages/site/about/media.html:129
#, python-format
msgid ""
"The Invisible Internet Project - An overview and guide to the technology\n"
"<a href=\"%(link)s\">(mp4)</a>\n"
"<a href=\"%(link2)s\">(webm)</a>\n"
"Andrew Savchenko (bircoph), FOSDEM, Brussel, February 4, 2018"
msgstr ""
#: i2p2www/pages/site/about/media.html:137
#, python-format
msgid ""
"<a href=\"%(link)s\">Intro to I2P for App Developers (mp4)</a>\n"
"idk"
msgstr ""
#: i2p2www/pages/site/about/media.html:145
msgid "Tutorials"
msgstr ""
#: i2p2www/pages/site/about/media.html:148
#, python-format
msgid ""
"<a href=\"%(link)s\">Felix Atari explains the basic principles of I2P</a>"
"\n"
"(Youtube Video)\n"
"Agent Felix Atari of the Telecomix Crypto Munitions Bureau.\n"
"By <a href=\"http://telecomix.org/\">Telecomix</a>"
msgstr ""
#: i2p2www/pages/site/about/media.html:155
#, python-format
msgid ""
"<a href=\"%(link)s\">Short garlic routing animation</a>\n"
"(Youtube Video)\n"
"Adrian Crenshaw.\n"
msgstr ""
#: i2p2www/pages/site/about/media.html:163
msgid "Articles and Interviews"
msgstr "記事とインタビュー"
#: i2p2www/pages/site/about/media.html:166
#, python-format
msgid ""
"Lance James (0x90) Interviewed by DistributedCity\n"
"<a href=\"%(link1)s\">Part 1</a>\n"
"<a href=\"%(link2)s\">Part 2</a>\n"
"July 26, 2002."
msgstr ""
#: i2p2www/pages/site/about/media.html:174
#, python-format
msgid ""
"Lance James (0x90) Interviewed by El País\n"
"(original in Spanish)\n"
"<a href=\"%(link)s\">English translation</a>\n"
"October 31, 2002."
msgstr ""
#: i2p2www/pages/site/about/media.html:181
#, python-format
msgid ""
"<a href=\"%(link)s\">2003 Business Week article referencing "
"invisiblenet</a>\n"
"September 14, 2003."
msgstr ""
#: i2p2www/pages/site/about/media.html:186
#, python-format
msgid ""
"<a href=\"%(link)s\">Netzwelt.de article about being anonymous in the "
"Internet</a>\n"
"(German)\n"
"November 2007."
msgstr ""
#: i2p2www/pages/site/about/media.html:192
#, python-format
msgid ""
"<a href=\"%(link)s\">zzz interviewed by gulli.com</a>\n"
"March 2009\n"
"<a href=\"%(german)s\">German translation</a>"
msgstr ""
#: i2p2www/pages/site/about/media.html:199
#, python-format
msgid ""
"<a href=\"%(mp3)s\">zzz interviewed on the InfoSec Daily Podcast Ep. 454 "
"(mp3)</a>\n"
"August 18, 2011\n"
"(link dead, seeded inside I2P at <a "
"href=\"http://tracker2.postman.i2p/index.php?view=TorrentDetail&id=14336\">postman's"
" tracker</a>)"
msgstr ""
#: i2p2www/pages/site/about/media.html:205
#, python-format
msgid ""
"<a href=\"%(link)s\">I2P - Anonymity for the Masses</a>,\n"
"Jonathan Cox,\n"
"November 11, 2011."
msgstr ""
#: i2p2www/pages/site/about/media.html:211
#, python-format
msgid ""
"<a href=\"%(mp3)s\">zzz and Lance James interviewed on the InfoSec Daily "
"Podcast Ep. 596 (mp3)</a>\n"
"February 16, 2012\n"
"(link dead, seeded inside I2P at <a "
"href=\"http://tracker2.postman.i2p/index.php?view=TorrentDetail&id=15905\">postman's"
" tracker</a>)"
msgstr ""
#: i2p2www/pages/site/about/media.html:217
#, python-format
msgid ""
"<a href=\"%(mp3)s\">Jeff and Str4d interviewed on the Brakeing Down "
"Security Podcast Ep. 2015-010 (mp3)</a>\n"
"Part 1, February 28, 2015"
msgstr ""
#: i2p2www/pages/site/about/media.html:222
#, python-format
msgid ""
"<a href=\"%(mp3)s\">Jeff and Str4d interviewed on the Brakeing Down "
"Security Podcast Ep. 2015-011 (mp3)</a>\n"
"Part 2, March 6, 2015"
msgstr ""
#: i2p2www/pages/site/about/media.html:227
#, python-format
msgid ""
"<a href=\"%(link)s\">Fireside With Lei - Episode 18: Lance James. "
"Success, Failures, Grief and Buddhism.</a>\n"
"<a href=\"%(archive)s\">(archive.org)</a>\n"
"<a href=\"%(mp3)s\">(mp3)</a>\n"
"Robert Lei, December 31, 2018"
msgstr ""
#: i2p2www/pages/site/about/media.html:236
#, python-format
msgid ""
"<a href=\"%(mhatta)s\">Articles by I2P contributor Masayuki Hatta on "
"Medium.com</a>\n"
"2019\n"
msgstr ""
#: i2p2www/pages/site/about/media.html:241
#, python-format
msgid ""
"<a href=\"%(ctrl)s\">Enabling both .onion and .i2p routing with Proxy "
"Auto-Configuration</a>\n"
"Daniel Aleksandersen, February 7 2019"
msgstr ""
#: i2p2www/pages/site/about/media.html:246
#, python-format
msgid ""
"<a href=\"%(advent)s\">Open-Source-Adventskalender: Die Darknets Freenet "
"und I2P</a>\n"
"Stefan Mey, December 21, 2021"
msgstr ""
#: i2p2www/pages/site/about/media.html:269
msgid "Other"
msgstr "その他"
#: i2p2www/pages/site/about/media.html:272
msgid ""
"I2P mentioned in Netflix's \"House of Cards\" Season 2 Episode 2,\n"
"February 14, 2014"
msgstr ""
#: i2p2www/pages/site/about/media.html:277
#, python-format
msgid ""
"<a href=\"%(meeh)s\">A curated list by I2P contributor meeh of I2P "
"implementations, libraries, resources, projects, and shiny things</a>\n"
"2019"
msgstr ""
#: i2p2www/pages/site/about/restrictive-countries.html:2
msgid "Strict Countries"
msgstr "厳しい国"
#: i2p2www/pages/site/about/restrictive-countries.html:4
msgid ""
"This implementation of I2P (the Java implementation distributed on this "
"site)\n"
"includes a \"Strict Countries List\" which we use to decide how routers "
"should behave \n"
"within regions where applications like I2P may be limited by law. For "
"example, while\n"
"no countries that we know of prohibit using I2P, some have broad "
"prohibitions on\n"
"participating in routing for others. Routers that appear to be in the "
"\"Strict\"\n"
"countries will automatically be placed into \"Hidden\" mode."
msgstr ""
"このI2Pの実装このサイトで配布しているJavaの実装には、\"厳しい国の一覧\"というものがあり、\n"
"I2Pのようなアプリケーションが法律で制限されている可能性がある地域で、\n"
"ルーターがどのように振る舞うべきかを決めるために使用しています。\n"
"例えば、我々が知る限りでI2Pの利用を禁止している国はありませんが、\n"
"他人のルーティングに参加することを広範に禁止している国もあります。\n"
"「厳しい」国に属すると思われるルーターは、自動的に「秘匿」モードが適用されます。"
#: i2p2www/pages/site/about/restrictive-countries.html:11
msgid ""
"The Project relies on the research provided by civil and digital rights "
"organizations in order\n"
"to make decisions that offer protections for its users. In this case the "
"ongoing research\n"
"provided by <a href=\"https://freedomhouse.org/\">Freedom House</a> has "
"been referenced. General\n"
"guidance is to include countries with a Civil Liberties (CL) score of 16 "
"or less or an Internet\n"
"Freedom score of 39 or less (not free)."
msgstr ""
"本プロジェクトは、使用者の保護を提供する決定を下すために、市民団体やデジタル人権団体から提供される調査に依存しています。\n"
"この場合、<a "
"href=\"https://freedomhouse.org/\">フリーダム・ハウス</a>が提供する継続的な調査が参照されています。一般的なガイダンスでは、市民の自由度CL点が16点以下、またはインターネットの自由度点が39点以下の国を含めることとしています。"
#: i2p2www/pages/site/about/restrictive-countries.html:18
msgid "Hidden Mode Summary"
msgstr "秘匿モード概観"
#: i2p2www/pages/site/about/restrictive-countries.html:19
msgid ""
"When a router is placed into hidden mode, three key things change about "
"it's behavior.\n"
"It will no longer publish a routerInfo to the NetDB, it will no longer "
"accept\n"
"participating tunnels, and it will reject direct connections to routers "
"in the same\n"
"country that it is in. These defenses make the routers more difficult to "
"enumerate\n"
"reliably, and prevent them from running afoul of restrictions on routing "
"traffic for\n"
"others."
msgstr ""
"ルーターが秘匿モードになると、その振る舞いについて3つの重要なことが変化します。\n"
"NetDBにルーター情報を公開しなくなり、参加するトンネルを受け付けなくなり、\n"
"同じ国にあるルーターへの直接接続を拒否するようになります。\n"
"これらの防御策は、ルーターを確実に列挙することを難しくし、\n"
"他の人のためにトラフィックをルーティングする際の制限に抵触することを防ぐためです。"
#: i2p2www/pages/site/about/restrictive-countries.html:26
msgid "Strict Countries List as of 2020"
msgstr "2020年の時点で厳しい国の一覧"
#: i2p2www/pages/site/about/restrictive-countries.html:71
msgid ""
"If you think a country should be added to the strict countries, file an "
"issue on the I2P gitlab."
msgstr "もし、ある国が厳しい国に追加されるべきと考えているなら、ファイルをI2P gitlab上でissueしてください。"
#: i2p2www/pages/site/about/software.html:4
msgid "The I2P Software"
msgstr "I2Pソフトウェア"
#: i2p2www/pages/site/about/software.html:6
msgid ""
"When you install the I2P software made available at geti2p.net, you are \n"
"actually installing an I2P router and an accompanying bundle of basic \n"
"applications. The I2P Java distribution is the first I2P software gateway"
" and \n"
"has been actively developed since 2003."
msgstr ""
"geti2p.net で入手可能になったI2Pソフトウェアをインストールするとき、\n"
"実際には、I2Pルーターと付随して、基本的なアプリケーションの同梱をインストールします。\n"
"I2P Javaディストリビューションは、最初のI2Pソフトウェアのゲートウェイで、2003年から活発に開発されています。"
#: i2p2www/pages/site/about/software.html:10
msgid ""
"The applications are made available through a webUI, which listens at \n"
"127.0.0.1:7657, and the main page of which is called the “Router "
"Console,” \n"
"where you monitor the health of your connection to the network and access"
" \n"
"applications to use on the network."
msgstr ""
"アプリケーションは 127.0.0.1:7657 "
"でリッスンし、\"ルーターコンソール\"と呼ばれるメインページであるウェブUIを介して利用可能になり、ネットワークへのあなたの接続の健全さを監視し、ネットワーク上で使うためのアプリケーションにアクセスします。"
#: i2p2www/pages/site/about/software.html:14
msgid "What is included:"
msgstr "何が内蔵されるのか:"
#: i2p2www/pages/site/about/software.html:15
msgid ""
"<strong>The Set Up Wizard</strong>: When you download the \n"
"I2P software, a set up wizard will guide you through a few configuration "
"steps \n"
"while your router is making its first connections to the network. This "
"happens \n"
"the same way that your home router connects you to the Internet. During "
"the set \n"
"up process, you will be given the option to test your bandwidth and set "
"your \n"
"bandwidth limits in order to ensure a good connection as a network peer."
msgstr ""
#: i2p2www/pages/site/about/software.html:21
msgid ""
"<strong>The I2P Router Console</strong>: Here is where you can see your \n"
"network connections and information about your router. You will be able "
"to see how many peers you \n"
"have, and other information that will help if you need to troubleshoot. "
"You can \n"
"stop and start the router as well. You will see the applications that the"
" \n"
"software includes, as well as links to some community forums and sites on"
" the \n"
"I2P network. You will receive news when there is a a new software "
"release, and \n"
"will be able to download the latest version here as well. Additionally, "
"you can \n"
"find shortcuts to other available applications. The console is "
"customizable and \n"
"includes a default light theme with a dark theme option."
msgstr ""
"<strong>I2Pルーターコンソール</strong>: ここでルーターについてのネットワーク接続と情報を見ることができます。\n"
"あなたが持っているピアの数や、トラブルシューティングが必要な場合に役立つその他の情報を見ることができます。\n"
"ルーターの停止と起動もできます。\n"
"ソフトウェアに含まれるアプリケーションや、I2Pネットワーク上のコミュニティフォーラムやサイトへのリンクが表示されます。\n"
"新しいソフトウェアがリリースされるとニュースを受け取り、最新版をダウンロードすることもできます。\n"
"さらに、他の利用可能なアプリケーションへのショートカットも見つけることができます。\n"
"コンソールは改変可能で、初期設定のライトテーマとダークテーマの選択肢があります。"
#: i2p2www/pages/site/about/software.html:30
msgid ""
"<strong>SusiMail</strong>: SusiMail is a secure email client. It is "
"primarily \n"
"intended for use with Postmans email servers inside of the I2P network ."
" It \n"
"is designed to avoid leaking information about email use to other "
"networks. \n"
"SusiMail is bridged so it can send and receive email from the internet as"
" well. \n"
"Occasionally you may see some services like Gmail classifying it as spam,"
" which \n"
"you can correct in your Internet email service providers settings."
msgstr ""
"<strong>SusiMail</strong>: "
"SusiMailは、安全なEメールクライアントです。これは第一に、I2Pネットワークの内側でPostmanのEメールサーバーを使うために意図されています。他のネットワークにEメールの使用に関する情報を漏洩するのを回避するよう設計されています。SusiMailはブリッジされていて、インターネットからもEメールを送受信できます。時折、Gmailのようないくつかのサービスにスパムとして分類されるのが確認でき、あなたはインターネットEメールサービス提供者の設定内で修正できます。"
#: i2p2www/pages/site/about/software.html:36
#, python-format
msgid ""
"<strong><a href=\"%(bittorrent)s\">I2PSnark</a></strong>: Snark is an I2P"
" network only BitTorrent client. It never makes a connection to a peer "
"over any other network."
msgstr ""
"<strong><a href=\"%(bittorrent)s\">I2PSnark</a></strong>: "
"SnarkはI2Pネットワークのみのビットトレントクライアントです。他のネットワークを介してピアに接続することはありません。"
#: i2p2www/pages/site/about/software.html:37
#, python-format
msgid ""
"<strong><a href=\"%(addressbook)s\">The Address Book</a></strong>: This "
"is a locally-defined list of \n"
"human-readable addresses ( ie: i2p-projekt.i2p) and corresponding I2P "
"addresses.(udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p) "
"It integrates with other applications to \n"
"allow you to use those human-readable addresses in place of those I2P \n"
"addresses. It is more similar to a hosts file or a contact list than a "
"network \n"
"database or a DNS service. There is no recognized global namespace, you "
"decide \n"
"what any given .i2p domain maps to in the end."
msgstr ""
"<strong><a href=\"%(addressbook)s\">アドレス帳</a></strong>: "
"これは、人間にとって読みやすいアドレス(例: i2p-projekt.i2pと一致するI2Pアドレス "
"(udhdrtrcetjm5sxzskjyr5ztpeszydbh4dpl3pl4utgqqw2v4jna.b32.i2p) "
"のローカルに定義された一覧です。 "
"それは、他のアプリケーションとそのI2Pアドレスの場所に、人間にとって読みやすいアドレスを使えるようにし、統合します。それは、ネットワークデータベースやDNSサービスよりも、hostsファイルや連絡先一覧に似ています。これらはコンピューターを識別する世界中の名前空間に非ず、即ち、"
" .i2p ドメインが最終的に何に割り当てられるかは、あなたが決めることです。"
#: i2p2www/pages/site/about/software.html:46
#, python-format
msgid ""
"<strong><a href=\"%(i2ptunnel)s\">I2P Hidden Services "
"Manager</a></strong> This is a general-purpose \n"
"adapter for forwarding services ( ie SSH ) into I2P and proxying client \n"
"requests to and from I2P. It provides a variety of “Tunnel Types” which "
"are \n"
"able to do advance filtering of traffic before it reaches I2P."
msgstr ""
#: i2p2www/pages/site/about/software.html:50
msgid "Applications Outside I2P to use with I2P"
msgstr "I2Pと共に使われるI2Pの外側のアプリケーション"
#: i2p2www/pages/site/about/software.html:51
#, python-format
msgid ""
"<strong><a href=\"%(browser)s\">Mozilla Firefox</a></strong>: A web "
"browser with advanced privacy and \n"
"security features, this is the best browser to configure to browse I2P \n"
"sites."
msgstr ""
#: i2p2www/pages/site/about/software.html:54
#, python-format
msgid ""
"<strong><a href=\"%(browser)s\">Chromium</a></strong>: A web browser "
"developed by Google that is the \n"
"Open-Source base of Google Chrome, this is sometimes used as an "
"alternative to \n"
"Firefox."
msgstr ""
#: i2p2www/pages/site/about/software.html:57
msgid ""
"<strong><a href=\"https://biglybt.com\">BiglyBT</a></strong>: A Feature-"
"Rich bittorrent client including I2P \n"
"support and the unique ability to “Bridge” regular torrents in-to I2P so"
" \n"
"people can download them anonymously."
msgstr ""
#: i2p2www/pages/site/about/software.html:60
#, python-format
msgid ""
"<strong><a href=\"https://openssh.com\">OpenSSH</a></strong>: OpenSSH is "
"a popular program used by systems administrators to <a "
"href=\"%(ssh)s\">remotely administer a server</a>, or to provide “Shell” "
"accounts for users on the server."
msgstr ""
#: i2p2www/pages/site/about/software.html:61
#, python-format
msgid ""
"<strong><a href=\"%(git)s\">Git</a>/<a "
"href=\"%(gitlab)s\">Gitlab</a></strong>: Git is a source-code control "
"tool which is \n"
"distributed, and often recommends a fork-first workflow. Hosting source "
"code on \n"
"I2P is an important activity, so Gitlab-specific instructions are "
"available for \n"
"all to use."
msgstr ""
#: i2p2www/pages/site/about/software.html:65
msgid ""
"<strong><a href=\"https://debian.org\">Debian</a> and <a "
"href=\"https://ubuntu.com\">Ubuntu</a> GNU/Linux</strong>: It is possible"
" to obtain \n"
"packages for Debian and Ubuntu GNU/Linux over I2P using <a "
"href=\"https://i2pgit.org/idk/apt-transport-i2p\">apt-transport-i2p</a> "
"and \n"
"<a href=\"https://i2pgit.org/idk/apt-transport-i2phttp\">apt-transport-"
"i2phttp</a>. In the future, a bittorrent-based transport may also be \n"
"developed."
msgstr ""
#: i2p2www/pages/site/about/software.html:69
msgid " Applications for Developers to create new things"
msgstr ""
#: i2p2www/pages/site/about/software.html:70
#, python-format
msgid ""
"<strong><a href=\"%(sam)s\">The SAM API Bridge</a></strong>: The SAM API "
"is a language-independent \n"
"API for writing applications that are I2P-native by communicating with "
"the \n"
"local I2P router. It can provide Streaming-like capabilities, Anonymous \n"
"Datagrams, or Repliable Datagrams."
msgstr ""
#: i2p2www/pages/site/about/software.html:74
#, python-format
msgid ""
"<strong><a href=\"%(bob)s\">The BOB API Bridge</a></strong>: This is a "
"deprecated technology, BOB \n"
"users should migrate to SAM if it is possible for them to do so."
msgstr ""
#: i2p2www/pages/site/about/software.html:76
#, python-format
msgid ""
"<strong><a href=\"%(i2cp)s\">The I2CP API</a></strong>: Not strictly an "
"application, this is how Java \n"
"applications communicate with the I2P router to set up tunnels, generate "
"and \n"
"manage keys, and communicate with other peers on the network."
msgstr ""
#: i2p2www/pages/site/about/team.html:2
msgid "I2P Project Members"
msgstr "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"
"<a href=\"%(volunteer)s\">Get involved!</a>"
msgstr ""
#: i2p2www/pages/site/about/team.html:14
msgid "Admin"
msgstr "管理者"
#: 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 "PRマネージャー"
#: i2p2www/pages/site/about/team.html:27
msgid "press contact, manages public relations and affairs"
msgstr "プレスコンタクト、広報担当"
#: i2p2www/pages/site/about/team.html:30
msgid "Assistant PR manager"
msgstr "PRマネージャー補佐"
#: i2p2www/pages/site/about/team.html:32
msgid "Public speaking, public relations assistance"
msgstr "会見、広報補佐"
#: i2p2www/pages/site/about/team.html:35
#, python-format
msgid "<a href=\"http://%(forum)s/\">Forum</a> admin"
msgstr "<a href=\"http://%(forum)s/\">フォーラム</a>管理人 "
#: i2p2www/pages/site/about/team.html:37
msgid "manage the public user forum"
msgstr "公開ユーザーフォーラムを管理"
#: i2p2www/pages/site/about/team.html:40
msgid "Download mirrors admin"
msgstr "ダウンロードミラー管理人"
#: i2p2www/pages/site/about/team.html:42
msgid "manage the mirrors for the download files"
msgstr "ダウンロードファイル用ミラーを管理"
#: i2p2www/pages/site/about/team.html:45
msgid "Website mirrors admin"
msgstr "ウェブサイトミラー管理者"
#: i2p2www/pages/site/about/team.html:46 i2p2www/pages/site/about/team.html:91
#: i2p2www/pages/site/about/team.html:171
#: i2p2www/pages/site/about/team.html:198
#: i2p2www/pages/site/about/team.html:246
msgid "vacant"
msgstr "空席"
#: i2p2www/pages/site/about/team.html:47
msgid "manage the mirrors for the website"
msgstr "ウェブサイト用ミラーを管理"
#: i2p2www/pages/site/about/team.html:50
#, python-format
msgid "<a href=\"%(monotone)s\">Monotone</a> guru"
msgstr "<a href=\"%(monotone)s\">Monotone</a> グル"
#: i2p2www/pages/site/about/team.html:52
msgid "manage the public monotone repositories"
msgstr "公開monotoneレポジトリを管理"
#: i2p2www/pages/site/about/team.html:55
msgid "Packager; Linux"
msgstr "パッケージャー; Linux"
#: i2p2www/pages/site/about/team.html:57
msgid "Linux (Debian/Ubuntu) distribution packager"
msgstr "Linux (Debian/Ubuntu) ディストリビューションパッケージャー"
#: i2p2www/pages/site/about/team.html:60
msgid "Packager; Windows"
msgstr "パッケージャー; Windows"
#: i2p2www/pages/site/about/team.html:62
msgid "Windows installer packager"
msgstr "Windows インストーラーパッケージャー"
#: i2p2www/pages/site/about/team.html:65
msgid "Packager; OSX"
msgstr "パッケージャー; OSX"
#: i2p2www/pages/site/about/team.html:67
msgid "OSX installer packager"
msgstr "OSX インストーラーパッケージャー"
#: i2p2www/pages/site/about/team.html:70
msgid "Release Manager"
msgstr "リリースマネージャー"
#: i2p2www/pages/site/about/team.html:72
msgid "Builds and signs the releases"
msgstr "リリースを構築と署名"
#: i2p2www/pages/site/about/team.html:75
msgid "Release Manager Alternates"
msgstr "リリースマネージャーの代わり"
#: i2p2www/pages/site/about/team.html:77
msgid "Backup release managers"
msgstr "リリースマネージャーを補助"
#: i2p2www/pages/site/about/team.html:80
msgid "CI admin"
msgstr "Cl 管理人"
#: i2p2www/pages/site/about/team.html:82
msgid "Maintain the Continuous Integration infrastructure"
msgstr "継続的インテグレーション基盤整備の保守"
#: i2p2www/pages/site/about/team.html:85
msgid "Reseed admin"
msgstr "再シード管理人"
#: i2p2www/pages/site/about/team.html:87
msgid "Monitors, advises and recruits reseed hosts"
msgstr "再シードの監視、助言、募集"
#: i2p2www/pages/site/about/team.html:90
msgid "Security Researcher"
msgstr "セキュリティ研究者"
#: i2p2www/pages/site/about/team.html:92
msgid "threat model / crypto expert"
msgstr "脅威モデル/暗号の玄人"
#: i2p2www/pages/site/about/team.html:97
msgid "Manage the project gitlab"
msgstr "プロジェクトのgitlabを管理"
#: i2p2www/pages/site/about/team.html:102
#: i2p2www/pages/site/about/team.html:107
msgid "Manage the project bug tracker"
msgstr "プロジェクトのバグトラッカーを管理"
#: i2p2www/pages/site/about/team.html:112
#: i2p2www/pages/site/about/team.html:137
msgid "manage the public project webservers"
msgstr "公開プロジェクトのウェブサーバーを管理"
#: i2p2www/pages/site/about/team.html:115
msgid "Translation admins"
msgstr "翻訳管理者"
#: i2p2www/pages/site/about/team.html:120
msgid "User Advocate"
msgstr "ユーザー啓発"
#: i2p2www/pages/site/about/team.html:122
msgid "gather, prioritize, advocate for user needs"
msgstr "ユーザーのニーズの集中・優先順位付け・啓発"
#: i2p2www/pages/site/about/team.html:125
msgid "Product Development"
msgstr "製品開発"
#: i2p2www/pages/site/about/team.html:127
msgid "supervises projects from the early planning stages to project completion"
msgstr "早期計画段階からプロジェクト完了までプロジェクトを監督"
#: i2p2www/pages/site/about/team.html:130
msgid "Website Maintainer"
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 "<a href=\"%(website)s\">Webserver</a> admin"
msgstr "<a href=\"%(website)s\">ウェブサーバー</a> 管理者"
#: i2p2www/pages/site/about/team.html:140
#, python-format
msgid "<a href=\"%(website)s\">Website</a> admin"
msgstr "<a href=\"%(website)s\">ウェブサイト</a> 管理者"
#: 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 "SDKとルーターのための開発者を指揮"
#: i2p2www/pages/site/about/team.html:182
#, python-format
msgid "<a href=\"http://%(postman)s/\">I2P mail</a> lead"
msgstr "<a href=\"http://%(postman)s/\">I2P mail</a>指揮"
#: i2p2www/pages/site/about/team.html:184
msgid "organize and develop the i2p mail system"
msgstr "i2pメールシステムの纏めと管理"
#: i2p2www/pages/site/about/team.html:187
#, python-format
msgid "<a href=\"http://%(bote)s/\">I2P-Bote</a> lead"
msgstr "<a href=\"http://%(bote)s/\">I2P-Bote</a>指揮"
#: i2p2www/pages/site/about/team.html:189
msgid "I2P-Bote plugin"
msgstr "I2P-Boteプラグイン"
#: i2p2www/pages/site/about/team.html:192
#, python-format
msgid "<a href=\"http://%(forum)s/viewforum.php?f=12\">I2PSnark</a> lead"
msgstr "<a href=\"http://%(forum)s/viewforum.php?f=12\">I2PSnark</a>指揮"
#: i2p2www/pages/site/about/team.html:194
msgid "Maintains the integrated Bittorrent client"
msgstr "統合されたビットトレントクライアントを保守"
#: i2p2www/pages/site/about/team.html:197
#, python-format
msgid "<a href=\"http://%(forum)s/viewforum.php?f=25\">Syndie</a> lead"
msgstr "<a href=\"http://%(forum)s/viewforum.php?f=25\">Syndie</a>指揮"
#: i2p2www/pages/site/about/team.html:199
msgid "Syndie development"
msgstr "Syndie開発"
#: i2p2www/pages/site/about/team.html:202
msgid "Susimail lead"
msgstr "Susimail指揮"
#: i2p2www/pages/site/about/team.html:204
msgid "Susimail development"
msgstr "Susimail開発"
#: i2p2www/pages/site/about/team.html:207
msgid "Android lead"
msgstr "Android指揮"
#: i2p2www/pages/site/about/team.html:209
msgid "Android development"
msgstr "Android開発"
#: i2p2www/pages/site/about/team.html:212
msgid "Console"
msgstr "コンソール"
#: i2p2www/pages/site/about/team.html:213
msgid "IDK/Sadie"
msgstr "IDK/Sadie"
#: i2p2www/pages/site/about/team.html:214
msgid "Router console HTML/CSS design"
msgstr "ルーターコンソールの HTML/CSS の設計"
#: i2p2www/pages/site/about/team.html:217
msgid "SAM"
msgstr "SAM"
#: i2p2www/pages/site/about/team.html:219
msgid "SAM maintainer"
msgstr "SAM保守者"
#: i2p2www/pages/site/about/team.html:222
msgid "Translators"
msgstr "翻訳者"
#: i2p2www/pages/site/about/team.html:223
msgid "many many people!"
msgstr "たくさんの、たくさんの、人たち!"
#: i2p2www/pages/site/about/team.html:228
msgid "Contributors"
msgstr "貢献"
#: i2p2www/pages/site/about/team.html:230
msgid "fire2pe dev, console enhancements"
msgstr "fire2pe開発、コンソール強化"
#: i2p2www/pages/site/about/team.html:234
msgid "desktopgui, dijjer port"
msgstr "desktopgui, dijjer port"
#: i2p2www/pages/site/about/team.html:238
msgid "Debian/Ubuntu Packager and PPA maintainer"
msgstr "Debian/Ubuntu パッケージャーとPPA保守者"
#: i2p2www/pages/site/about/team.html:242
msgid "Routerconsole backend and UI work, website revamp, unit tests work"
msgstr "ルーターコンソールのバックエンドと UI の動作、ウェブサイトの改良、単体テストの実施"
#: i2p2www/pages/site/about/team.html:247
msgid "Help needed on many fronts!"
msgstr "様々な方面からの支援が必要です!"
#: i2p2www/pages/site/about/team.html:251
msgid "Past contributors"
msgstr "過去の貢献者"
#: i2p2www/pages/site/about/team.html:253
msgid "I2PTunnel development, ministreaming library"
msgstr "I2PTunnel の開発とミニストリーミングライブラリ"
#: i2p2www/pages/site/about/team.html:257
msgid "Project lead, Syndie lead"
msgstr "プロジェクト指揮、Syndie指揮"
#: i2p2www/pages/site/about/team.html:261
msgid "Project lead, Syndie lead, I2Phex, support guru"
msgstr "プロジェクトリード、Syndieリード、I2Phex、サポートグル"
#: i2p2www/pages/site/about/team.html:265
msgid "iMule lead"
msgstr "iMule lead指揮"
#: i2p2www/pages/site/about/team.html:269
#: i2p2www/pages/site/about/team.html:273
#: i2p2www/pages/site/about/team.html:277
msgid "I2Phex work"
msgstr "I2Phex"
#: i2p2www/pages/site/about/team.html:281
msgid "Python SAM library, attack simulations"
msgstr "Python SAM ライブラリ、模擬攻撃実験"
#: i2p2www/pages/site/about/team.html:285
msgid "i2pmail development"
msgstr "i2pmail開発"
#: i2p2www/pages/site/about/team.html:289
msgid "Syndie help"
msgstr "Syndie ヘルプ"
#: i2p2www/pages/site/about/team.html:293
msgid "i2p mail,susimail and susidns apps"
msgstr "i2p mail、susimail及びsusidnsアプリ"
#: i2p2www/pages/site/about/team.html:297
msgid "I2Phex (port of Phex to I2P)"
msgstr "I2Phex (PhexのI2Pへのポート)"
#: i2p2www/pages/site/about/team.html:301
msgid "addressbook,i2p-bt,syndie client"
msgstr "アドレス帳、i2p-bt、syndieクライアント"
#: i2p2www/pages/site/about/team.html:305
msgid "organize and develop the i2p-bt BitTorrent port"
msgstr "i2p-bt BitTorrent 移植の編成と開発"
#: i2p2www/pages/site/about/team.html:309
msgid "addressbook, i2p-bt, syndie client development"
msgstr "アドレスブック, i2p-bt, syndie クライアント開発"
#: i2p2www/pages/site/about/team.html:313
msgid "encryption and signature routines, I2PIM"
msgstr "暗号化と署名のルーチン、I2PIM"
#: i2p2www/pages/site/about/team.html:317
msgid "SAM jython code, work on stasher (DHT) and v2v (VoI2P)"
msgstr "SAM jython コード, stasher (DHT) および v2v (VoI2P)に関する働き"
#: i2p2www/pages/site/about/team.html:321
msgid "installer, systray, bogobot"
msgstr "installer, systray, bogobot"
#: i2p2www/pages/site/about/team.html:325
msgid "jbigi development, wiki migration, doc cleanup"
msgstr "jbigi 開発, wiki 移転, ドキュメントの整理"
#: i2p2www/pages/site/about/team.html:329
msgid "java debugging and client development on I2PTunnel and the router console"
msgstr "I2PTunnelとルーターコンソールに関する java デバッグとクライアント開発"
#: i2p2www/pages/site/about/team.html:333
msgid "SAM perl module"
msgstr "SAM perl モジュール"
#: i2p2www/pages/site/about/team.html:337
msgid "i2psnark work"
msgstr "i2psnark"
#: i2p2www/pages/site/about/team.html:341
msgid "java cleanup"
msgstr "java クリーンナップ"
#: i2p2www/pages/site/about/team.html:345
msgid "docs. wiki migration"
msgstr "docs. wiki 移転"
#: i2p2www/pages/site/about/team.html:349
msgid "translations into French"
msgstr "フランス語翻訳"
#: i2p2www/pages/site/about/team.html:353
msgid "C port of jcpuid"
msgstr "jcpuidのC移植"
#: i2p2www/pages/site/about/team.html:357
msgid "C# SAM library, pants, fortuna integration"
msgstr "C# SAM ライブラリ、パンツ、フォルトゥナの統合"
#: i2p2www/pages/site/about/team.html:361
msgid "libSAM"
msgstr "libSAM"
#: i2p2www/pages/site/about/team.html:365
#: i2p2www/pages/site/about/team.html:369
msgid "i2p-bt tracker development"
msgstr "i2p-bt トラッカーの開発"
#: i2p2www/pages/site/about/team.html:373
msgid "Console and website themes"
msgstr "コンソールとウェブサイトのテーマ"
#: i2p2www/pages/site/about/team.html:403
msgid "&hellip; 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 ""
"I2PCon 2015は、この種の催しとしては初めてのものだった。短期的な目標は2つあった。\n"
"第一に、プライバシーの獲得に関する知識を得ることができる催しを一般の人々に提供すること。\n"
"2つ目は、暗号、匿名性、I2Pを中心とした事柄に関する主題で技術的な議論を行い、I2Pプロジェクトとそのコミュニティを更に発展させること。"
#: 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 ""
"この催しのより大きな、より長期的な目標は、プライバシーを意識する個人のコミュニティを構築することだった。\n"
"プライバシーの重要性を認識する人々を繋ぐことで、このコミュニティが成長できるフォーラムを提供したかったのだ。"
#: i2p2www/pages/site/about/i2pcon/2015.html:23
msgid ""
"The idea for this event was first spawned by our wonderful friends at\n"
"<a href=\"https://torontocrypto.org/\">Toronto Crypto</a>.\n"
"The venue was provided by <a href=\"https://hacklab.to/\">Hacklab.to</a>."
"\n"
"The marketing was spearheaded by <a "
"href=\"https://twitter.com/YrB1rd\">@YrB1rd</a> and Siew.\n"
"Without them this event would not have been possible."
msgstr ""
"この催しの構想は、<a href=\"https://torontocrypto.org/\">Toronto "
"Crypto</a>の素晴らしい友人たちから生まれた。\n"
"会場は<a href=\"https://hacklab.to/\">Hacklab.to</a>に提供された。\n"
"宣伝広告は<a href=\"https://twitter.com/YrB1rd\">@YrB1rd</a>とSiewが指揮を執った。\n"
"上記の協力者がいなければ、この催しは実現しなかっただろう。"
#: 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 non-private "
"internet due to bridging by Vuze clients."
msgstr ""
#: i2p2www/pages/site/about/i2pcon/2015.html:50
msgid "Licenses"
msgstr "ライセンス"
#: 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 "ライセンス"
#: 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 "PsiはI2Pの開発者です。"
#: i2p2www/pages/site/about/i2pcon/2015.html:130
msgid "Str4d is an I2P developer."
msgstr "Str4dはI2Pの開発者です。"
#: i2p2www/pages/site/about/i2pcon/2015.html:136
msgid "Zzz is an I2P developer."
msgstr "ZzzはI2Pの開発者です。"
#: i2p2www/pages/site/about/i2pcon/2015.html:143
msgid "Press"
msgstr "プレス"
#: 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 "1日目"
#: 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 "ビデオ"
#: 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 "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 ""
#: 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 "2010年8月"
#: 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 <a href=\"%(history)s\">\n"
"Performance History</a>."
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 <a href=\"%(sybilpdf)s\">Sybil</a> 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 <a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> "
"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"
"<a href=\"%(elgamalaes)s#future\">ElGamal/AES+SessionTag page</a>."
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 <a href=\"%(elgamalaes)s\">ElGamal/AES+SessionTag</a> \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"
"<a href=\"%(streaming)s#future\">streaming library page</a>."
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 <a href=\"%(performance)s\">Performance</a> "
"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"
"<a href=\"%(modpow)s\">modPow</a>.\n"
"Rather than try to tune this method, we'll call out to\n"
"<a href=\"%(gmp)s\">GNU MP</a> - an insanely fast math library\n"
"(with tuned assembler for many architectures). (<i>Editor: see\n"
"<a href=\"%(jbigi)s\">NativeBigInteger for faster public key "
"cryptography</a></i>)"
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&#37; 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 <i>always</i> 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&#37; 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 <a href=\"%(link)s\">said</a>, 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 "パフォーマンス"
#: 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 "I2Pはどのように動作するのか、なぜ遅いのか、そしてなぜ私の全帯域幅を使わないのか"
#: 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 <b>yes</b>."
msgstr ""
"恐らく最も頻繁に尋ねられることの一つは、「I2Pはどのくらい速いですか」、\n"
"と、尋ねられることが多いのですが、誰もその答え―「時と場合による」―が好きではないようです。I2Pを試した後、次に尋ねられることは「速くなるのか」で、答えは最も強く主張して"
" <b> はい</b> 。"
#: 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 ""
"I2Pは完全に動的なネットワークです。各クライアントは他のードに知られており、ローカルの既知のードに到達可能性と容量をテストします。\n"
"到達可能で容量のあるードのみがローカルのNetDBこれは一般的にネットワークの一部に過ぎず、約500-1000ですに保存されます。\n"
"I2Pがトンネルを構築したとき、プールから最適のリソースを選択します。例えば、20-50ードの小さなサブセットしか、トンネルの構築に利用できません。"
"\n"
"なぜなら、テストは毎分行われるため、使用されるノードのプールは毎分変化するからです。\n"
"各I2Pードはネットの異なる部分を知っているので、各ルーターはトンネルに使用するI2Pードの組み合わせが異なることを意味します。\n"
"つのルーターが既知のードの同じサブセットを持っている場合でも、到達可能性と容量のテストは他のルーターがつのルーターのテストと同じように負荷を受けている可能性がありますが、2"
" 番目のルーターのテストの場合はフリーになる可能性があるので、結果はおそらく異なります。"
#: 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 ""
"以上、各I2Pードにトンネルを構築するードが異なる理由を説明しました。\n"
"I2Pードごとに異なる遅延時間と帯域幅を持つため、それらのードを介して構築されるトンネルは異なる遅延時間と帯域幅の値を持つことになります。"
"\n"
"また、すべてのI2Pードには異なるトンネルが構築されているため、2つのI2Pードが同じトンネルの組み合わせを持つことはありません。"
#: 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"
"<a href=\"%(future)s\">Future Performance Improvements</a>."
msgstr ""
"今後のパフォーマンス向上の可能性については、以下を参照してください\n"
"<a href=\"%(future)s\">今後のパフォーマンス向上</a>。"