I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Updated translation strings

Browse Source
This commit is contained in:
str4d
2015-01-21 03:48:00 +00:00
parent 3974ddadfe
commit 04ba83d543
9 changed files with 3792 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

429
i2p2www/translations/de/LC_MESSAGES/blog.po
View File

@ -13,7 +13,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2014-12-02 23:11+0000\n"
"POT-Creation-Date: 2015-01-21 03:46+0000\n"
"PO-Revision-Date: 2014-12-27 15:23+0000\n"
"Last-Translator: tk2015\n"
"Language-Team: German "
@ -3276,3 +3276,430 @@ msgstr ""
msgid "`click here`"
msgstr "`hier klicken`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1
#, fuzzy
msgid ""
"================\n"
"31C3 trip report\n"
"================"
msgstr ""
"==============\n"
"0.9.11 Release\n"
"=============="
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9
msgid ""
"CCC has always been a productive time for us, and 31C3 was no exception. "
"Here is a summary of our various meetings and discussions."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20
msgid ""
"We were, for the second year in a row, at a great location in the "
"Congress, in\n"
"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square "
"has\n"
"really increased our visibility and helped many people find us. Thanks to"
" Noisy\n"
"Square and the 31C3 organizers for a great Congress."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29
msgid ""
"We also thank Gabriel Weinberg and his fabulous search engine "
"`DuckDuckGo`_ for\n"
"their support of open source anonymity tools and their `generous "
"contribution`_\n"
"to I2P in 2014. Funding from DuckDuckGo and others helped support our "
"attendance\n"
"at CCC. This is the primary annual meetup for I2P developers and it is "
"critical\n"
"to our success."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38
msgid "`generous contribution`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40
msgid ""
"Discussions with others\n"
"======================="
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48
msgid ""
"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved "
"himself\n"
"and the project from TU Munich to `Inria`_ in France. He has a large "
"number of\n"
"`open positions`_. This is a great opportunity to get paid to work on "
"open\n"
"source anonymity tools, we encourage everybody to contact him about it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57
#, fuzzy
msgid "`open positions`"
msgstr "`Nominierungen`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59
msgid ""
"The prospect of an invigorated GNUnet with a large amount of new funding "
"is\n"
"quite interesting. We discussed more ways to work together. In early "
"2014, we\n"
"worked hard to understand the GnuNet DNS replacement, but we were unable "
"to\n"
"figure out a good fit for it in I2P. One of his new ideas is a "
"distributed,\n"
"anonymous statistics gathering subsystem, for detecting problems or "
"attacks on\n"
"the network. We'd definitely be interested in that."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68
msgid ""
"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems "
"draft`_.\n"
"A new, greatly simplified version 3 was posted in December. The prospects"
" for\n"
"approval remain unclear. The best way to monitor or participate in the\n"
"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to "
"do so\n"
"on our side, and also give Hellekin a new point-of-contact for this topic."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76
msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77
msgid "`IETF DNSOP WG mailing list`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79
msgid ""
"We apologized to Christian for not being organized enough to have a talk "
"at his\n"
"`We Fix The Net assembly`_. One of our biggest failures is a project is "
"our\n"
"seeming inability to submit talks at conferences. We'll have to do better"
" in the\n"
"new year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86
msgid "`We Fix The Net assembly`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91
msgid ""
"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in "
"with\n"
"other anonymity tools into this new Debian \"superpackage\" of some sort,"
" and\n"
"would love to get I2P into Debian in 2015. He claims the process is now "
"easy,\n"
"just `follow the instructions`_. We said that's funny, we've been\n"
"`stuck in the process for over 7 years`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99
msgid "`follow the instructions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100
msgid "`stuck in the process for over 7 years`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102
msgid ""
"He said, well, try the new process, it works great, should be no problem "
"at all\n"
"if your package is in good shape. The people in Debian that run this "
"process are\n"
"eager volunteers who want nothing more than to get more packages in. We "
"said our\n"
"package is indeed in fantastic shape, and we would try out the new "
"process as\n"
"soon as possible. As best as we can tell, we are orphaned in the old "
"process and\n"
"have to restart in the new process? If all this is true, we will be in "
"the next\n"
"Debian release in late 2015. This would be very very cool."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:115
msgid ""
"We had a nice discussion with BitingBird of Tails. They are very happy "
"with our\n"
"rapid response to the `vulnerability disclosure`_ last summer, resulting "
"in our\n"
"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and "
"they\n"
"took `great offense`_ to that and the lack of private notification. We "
"thanked\n"
"them for taking the heat and fighting back."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123
msgid "`vulnerability disclosure`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124
#, fuzzy
msgid "`0.9.14 release`"
msgstr "0.9.4 Release"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:125
msgid "`great offense`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:127
msgid ""
"Biting Bird also handles support, and she tells us the number one issue "
"is how\n"
"long I2P takes to start up and be useful for browsing I2P sites. Her "
"standard\n"
"answer is \"wait ten more minutes\" and that seems to be effective. I2P "
"is\n"
"particularly slow to startup on Tails since it does not persist peer data"
" by\n"
"default. It would be nice to change that, but there's also things we can "
"do on\n"
"the I2P side to make things start faster. Expect some improvement in our "
"0.9.18\n"
"release."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:140
msgid ""
"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The "
"upcoming\n"
"Tor Hidden Services changes mean that their keys will no longer fit into "
"a\n"
"portion of an IPv6 address, and he was working on a solution. We reminded"
" him\n"
"that this has always been the case for I2P (with \"GarliCat\"), that it's"
" not a\n"
"new problem. He pointed us to `a presentation`_ of his proposal. It "
"involves\n"
"storing an extra record in the hidden service directory (equivalent of a\n"
"leaseset I2P's network database). It wasn't completely clear how this "
"would\n"
"work, or if we would consider it abuse of the netDb. We'll follow up with"
" him\n"
"as he gets further."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:153
msgid "`a presentation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:155
#, fuzzy
msgid ""
"New users\n"
"---------"
msgstr ""
"Neue App-Versionen\n"
"----------------"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:160
msgid ""
"We spent hours and hours explaining I2P to people stopping by our table. "
"Some\n"
"had heard of I2P before, some had not; everybody had heard of Tor and had"
" at\n"
"least a vague idea of what hidden services are. As usual, introducing "
"people to\n"
"I2P was a struggle. By the end of the Congress, we became convinced that "
"a part\n"
"of the problem was a difference in terminology. Back 12 years ago, when "
"I2P and\n"
"Tor were both getting started, we each came up with terms for the various"
" parts\n"
"of our systems. Today, the Tor terminology such as \"hidden service\" is\n"
"well-understood and commonplace. The I2P terminology such as \"eepsite\" "
"is\n"
"neither. We agreed to review our documentation, router console, and other"
" places\n"
"for opportunities to simplify it and use common terms."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:173
#, fuzzy
msgid ""
"I2P project topics\n"
"------------------"
msgstr ""
"Neue App-Versionen\n"
"----------------"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:178
msgid ""
"* *Spending money:* We discussed several ways to effectively use our "
"resources\n"
" in 2015, including more hardware for testing and development. Also, we "
"plan to\n"
" increase reimbursement levels for conference attendees."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:184
msgid ""
"* *Toronto meetup:* CCC is such a productive time for us, and it seems "
"that a\n"
" second meetup in the year would be quite helpful. We have proposed it "
"for\n"
" August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. "
"It\n"
" would include developer meetings together with presentations and "
"tutorials,\n"
" all open to the public. We are attempting to gauge interest and "
"research\n"
" possible venues. If you are considering attending, please let us know "
"by\n"
" `tweeting @i2p`_ or posting `on the dev forum thread`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:194
msgid ""
"* We discussed Meeh's workload and the state of the various services he "
"is\n"
" running. We made some plans to reduce his load and have some other "
"people help\n"
" out."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:200
msgid ""
"* We reviewed our critieria for placing links to `i2pd`_ on our download "
"page.\n"
" We agreed that the only remaining item is to have a nice page on the\n"
" `Privacy Solutions web site`_ or elsewhere with binary packages for "
"Windows,\n"
" Linux, and Mac, and source packages. It's not clear who is responsible "
"for\n"
" building the packages and where the \"official\" version is. Once "
"there's an\n"
" established process for building and signing packages and an official "
"place to\n"
" put them, we're ready to link to it. If it is not feasible to host it "
"on the\n"
" Privacy Solutions website, we will discuss alternatives with orignal,\n"
" including possible migration to our download servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:212
msgid ""
"* Lots of people coming by the table asked if we had a non-Java version. "
"It was\n"
" great to finally answer \"yes\" and we're eager to get the word out and"
" get more\n"
" users, testers, and developers on it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:218
msgid ""
"* `Vuze`_ continues to make good progress on their I2P integration. We "
"look\n"
" forward to working with them in the new year on a managed rollout to "
"more\n"
" users."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:224
msgid ""
"* We discussed the state of Meeh's and Sindu's reseed servers. They made "
"several\n"
" improvements while at the congress and are investigating migration to\n"
" `Matt Drollette's Go implementation`_. The security and reliability of "
"our\n"
" reseed servers is vital to new users and network operation. `User "
"'backup'`_\n"
" is doing a great job monitoring and managing the pool of reseed servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:232
msgid ""
"* We agreed to purchase a second root server for development, testing, "
"and\n"
" services. Echelon will be adminstering it. Contact him is you would "
"like a VM."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:237
msgid ""
"* We reiterated that we have funds available to purchase test hardware,\n"
" especially for Windows and Mac. Talk to echelon for details."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:242
msgid ""
"* We met with Welterde about the state of his services including his\n"
" `open tracker`_. These services are not being adequately maintained and"
" will\n"
" soon become inaccessible due to crypto changes if they are not "
"upgraded. He\n"
" committed to upgrading them soon."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:249
msgid ""
"* We met lots of people interested in our `Android app`_. We passed "
"several\n"
" ideas and bug reports back to str4d. We plan to make a big push to give"
" the\n"
" app some development love early in the year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:255
msgid ""
"* Regrettably, we didn't get to see too many talks at the Congress, as we"
" were\n"
" so busy meeting with people. We plan to catch up and `watch them "
"online`_. As\n"
" usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's "
"talk was\n"
" great. We hear that the cryptography talks were good as well."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262
msgid "`Toronto Crypto`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263
msgid "`tweeting @i2p`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:264
msgid "`on the dev forum thread`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:267
#, fuzzy
msgid "`Privacy Solutions web site`"
msgstr "`unsere Webseite`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271
msgid "`Matt Drollette's Go implementation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:272
msgid "`User 'backup'`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:274
#, fuzzy
msgid "`open tracker`"
msgstr "`auf Twitter`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:276
msgid "`Android app`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:278
msgid "`watch them online`"
msgstr ""

430
i2p2www/translations/es/LC_MESSAGES/blog.po
View File

@ -15,7 +15,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2014-12-02 23:11+0000\n"
"POT-Creation-Date: 2015-01-21 03:46+0000\n"
"PO-Revision-Date: 2014-12-06 06:52+0000\n"
"Last-Translator: strel\n"
"Language-Team: Spanish "
@ -4275,3 +4275,431 @@ msgstr ""
msgid "`click here`"
msgstr "`haga clic aquí`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1
#, fuzzy
msgid ""
"================\n"
"31C3 trip report\n"
"================"
msgstr ""
"================\n"
"Versión 0.9.14.1\n"
"================"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9
msgid ""
"CCC has always been a productive time for us, and 31C3 was no exception. "
"Here is a summary of our various meetings and discussions."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20
msgid ""
"We were, for the second year in a row, at a great location in the "
"Congress, in\n"
"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square "
"has\n"
"really increased our visibility and helped many people find us. Thanks to"
" Noisy\n"
"Square and the 31C3 organizers for a great Congress."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29
msgid ""
"We also thank Gabriel Weinberg and his fabulous search engine "
"`DuckDuckGo`_ for\n"
"their support of open source anonymity tools and their `generous "
"contribution`_\n"
"to I2P in 2014. Funding from DuckDuckGo and others helped support our "
"attendance\n"
"at CCC. This is the primary annual meetup for I2P developers and it is "
"critical\n"
"to our success."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38
msgid "`generous contribution`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40
msgid ""
"Discussions with others\n"
"======================="
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48
msgid ""
"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved "
"himself\n"
"and the project from TU Munich to `Inria`_ in France. He has a large "
"number of\n"
"`open positions`_. This is a great opportunity to get paid to work on "
"open\n"
"source anonymity tools, we encourage everybody to contact him about it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57
#, fuzzy
msgid "`open positions`"
msgstr "`nominaciones`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59
msgid ""
"The prospect of an invigorated GNUnet with a large amount of new funding "
"is\n"
"quite interesting. We discussed more ways to work together. In early "
"2014, we\n"
"worked hard to understand the GnuNet DNS replacement, but we were unable "
"to\n"
"figure out a good fit for it in I2P. One of his new ideas is a "
"distributed,\n"
"anonymous statistics gathering subsystem, for detecting problems or "
"attacks on\n"
"the network. We'd definitely be interested in that."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68
msgid ""
"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems "
"draft`_.\n"
"A new, greatly simplified version 3 was posted in December. The prospects"
" for\n"
"approval remain unclear. The best way to monitor or participate in the\n"
"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to "
"do so\n"
"on our side, and also give Hellekin a new point-of-contact for this topic."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76
msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77
msgid "`IETF DNSOP WG mailing list`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79
msgid ""
"We apologized to Christian for not being organized enough to have a talk "
"at his\n"
"`We Fix The Net assembly`_. One of our biggest failures is a project is "
"our\n"
"seeming inability to submit talks at conferences. We'll have to do better"
" in the\n"
"new year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86
msgid "`We Fix The Net assembly`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91
msgid ""
"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in "
"with\n"
"other anonymity tools into this new Debian \"superpackage\" of some sort,"
" and\n"
"would love to get I2P into Debian in 2015. He claims the process is now "
"easy,\n"
"just `follow the instructions`_. We said that's funny, we've been\n"
"`stuck in the process for over 7 years`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99
msgid "`follow the instructions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100
msgid "`stuck in the process for over 7 years`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102
msgid ""
"He said, well, try the new process, it works great, should be no problem "
"at all\n"
"if your package is in good shape. The people in Debian that run this "
"process are\n"
"eager volunteers who want nothing more than to get more packages in. We "
"said our\n"
"package is indeed in fantastic shape, and we would try out the new "
"process as\n"
"soon as possible. As best as we can tell, we are orphaned in the old "
"process and\n"
"have to restart in the new process? If all this is true, we will be in "
"the next\n"
"Debian release in late 2015. This would be very very cool."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:115
msgid ""
"We had a nice discussion with BitingBird of Tails. They are very happy "
"with our\n"
"rapid response to the `vulnerability disclosure`_ last summer, resulting "
"in our\n"
"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and "
"they\n"
"took `great offense`_ to that and the lack of private notification. We "
"thanked\n"
"them for taking the heat and fighting back."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123
msgid "`vulnerability disclosure`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124
#, fuzzy
msgid "`0.9.14 release`"
msgstr "Versión 0.9.4"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:125
msgid "`great offense`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:127
msgid ""
"Biting Bird also handles support, and she tells us the number one issue "
"is how\n"
"long I2P takes to start up and be useful for browsing I2P sites. Her "
"standard\n"
"answer is \"wait ten more minutes\" and that seems to be effective. I2P "
"is\n"
"particularly slow to startup on Tails since it does not persist peer data"
" by\n"
"default. It would be nice to change that, but there's also things we can "
"do on\n"
"the I2P side to make things start faster. Expect some improvement in our "
"0.9.18\n"
"release."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:140
msgid ""
"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The "
"upcoming\n"
"Tor Hidden Services changes mean that their keys will no longer fit into "
"a\n"
"portion of an IPv6 address, and he was working on a solution. We reminded"
" him\n"
"that this has always been the case for I2P (with \"GarliCat\"), that it's"
" not a\n"
"new problem. He pointed us to `a presentation`_ of his proposal. It "
"involves\n"
"storing an extra record in the hidden service directory (equivalent of a\n"
"leaseset I2P's network database). It wasn't completely clear how this "
"would\n"
"work, or if we would consider it abuse of the netDb. We'll follow up with"
" him\n"
"as he gets further."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:153
msgid "`a presentation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:155
#, fuzzy
msgid ""
"New users\n"
"---------"
msgstr ""
"Nuevas versiones de la aplicación\n"
"----------------"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:160
msgid ""
"We spent hours and hours explaining I2P to people stopping by our table. "
"Some\n"
"had heard of I2P before, some had not; everybody had heard of Tor and had"
" at\n"
"least a vague idea of what hidden services are. As usual, introducing "
"people to\n"
"I2P was a struggle. By the end of the Congress, we became convinced that "
"a part\n"
"of the problem was a difference in terminology. Back 12 years ago, when "
"I2P and\n"
"Tor were both getting started, we each came up with terms for the various"
" parts\n"
"of our systems. Today, the Tor terminology such as \"hidden service\" is\n"
"well-understood and commonplace. The I2P terminology such as \"eepsite\" "
"is\n"
"neither. We agreed to review our documentation, router console, and other"
" places\n"
"for opportunities to simplify it and use common terms."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:173
#, fuzzy
msgid ""
"I2P project topics\n"
"------------------"
msgstr ""
"Nuevas versiones de la aplicación\n"
"----------------"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:178
msgid ""
"* *Spending money:* We discussed several ways to effectively use our "
"resources\n"
" in 2015, including more hardware for testing and development. Also, we "
"plan to\n"
" increase reimbursement levels for conference attendees."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:184
msgid ""
"* *Toronto meetup:* CCC is such a productive time for us, and it seems "
"that a\n"
" second meetup in the year would be quite helpful. We have proposed it "
"for\n"
" August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. "
"It\n"
" would include developer meetings together with presentations and "
"tutorials,\n"
" all open to the public. We are attempting to gauge interest and "
"research\n"
" possible venues. If you are considering attending, please let us know "
"by\n"
" `tweeting @i2p`_ or posting `on the dev forum thread`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:194
msgid ""
"* We discussed Meeh's workload and the state of the various services he "
"is\n"
" running. We made some plans to reduce his load and have some other "
"people help\n"
" out."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:200
msgid ""
"* We reviewed our critieria for placing links to `i2pd`_ on our download "
"page.\n"
" We agreed that the only remaining item is to have a nice page on the\n"
" `Privacy Solutions web site`_ or elsewhere with binary packages for "
"Windows,\n"
" Linux, and Mac, and source packages. It's not clear who is responsible "
"for\n"
" building the packages and where the \"official\" version is. Once "
"there's an\n"
" established process for building and signing packages and an official "
"place to\n"
" put them, we're ready to link to it. If it is not feasible to host it "
"on the\n"
" Privacy Solutions website, we will discuss alternatives with orignal,\n"
" including possible migration to our download servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:212
msgid ""
"* Lots of people coming by the table asked if we had a non-Java version. "
"It was\n"
" great to finally answer \"yes\" and we're eager to get the word out and"
" get more\n"
" users, testers, and developers on it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:218
msgid ""
"* `Vuze`_ continues to make good progress on their I2P integration. We "
"look\n"
" forward to working with them in the new year on a managed rollout to "
"more\n"
" users."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:224
msgid ""
"* We discussed the state of Meeh's and Sindu's reseed servers. They made "
"several\n"
" improvements while at the congress and are investigating migration to\n"
" `Matt Drollette's Go implementation`_. The security and reliability of "
"our\n"
" reseed servers is vital to new users and network operation. `User "
"'backup'`_\n"
" is doing a great job monitoring and managing the pool of reseed servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:232
msgid ""
"* We agreed to purchase a second root server for development, testing, "
"and\n"
" services. Echelon will be adminstering it. Contact him is you would "
"like a VM."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:237
msgid ""
"* We reiterated that we have funds available to purchase test hardware,\n"
" especially for Windows and Mac. Talk to echelon for details."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:242
msgid ""
"* We met with Welterde about the state of his services including his\n"
" `open tracker`_. These services are not being adequately maintained and"
" will\n"
" soon become inaccessible due to crypto changes if they are not "
"upgraded. He\n"
" committed to upgrading them soon."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:249
msgid ""
"* We met lots of people interested in our `Android app`_. We passed "
"several\n"
" ideas and bug reports back to str4d. We plan to make a big push to give"
" the\n"
" app some development love early in the year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:255
msgid ""
"* Regrettably, we didn't get to see too many talks at the Congress, as we"
" were\n"
" so busy meeting with people. We plan to catch up and `watch them "
"online`_. As\n"
" usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's "
"talk was\n"
" great. We hear that the cryptography talks were good as well."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262
msgid "`Toronto Crypto`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263
msgid "`tweeting @i2p`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:264
#, fuzzy
msgid "`on the dev forum thread`"
msgstr "`este hilo de desarrollo`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:267
#, fuzzy
msgid "`Privacy Solutions web site`"
msgstr "`The Privacy Solutions Project`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271
msgid "`Matt Drollette's Go implementation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:272
msgid "`User 'backup'`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:274
#, fuzzy
msgid "`open tracker`"
msgstr "`en Twitter`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:276
msgid "`Android app`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:278
msgid "`watch them online`"
msgstr ""

423
i2p2www/translations/fr/LC_MESSAGES/blog.po
View File

@ -11,7 +11,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2014-12-02 23:11+0000\n"
"POT-Creation-Date: 2015-01-21 03:46+0000\n"
"PO-Revision-Date: 2014-12-02 23:13+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: French "
@ -3660,3 +3660,424 @@ msgstr ""
msgid "`click here`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1
#, fuzzy
msgid ""
"================\n"
"31C3 trip report\n"
"================"
msgstr ""
"==============\n"
"0.9.13 Release\n"
"=============="
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9
msgid ""
"CCC has always been a productive time for us, and 31C3 was no exception. "
"Here is a summary of our various meetings and discussions."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20
msgid ""
"We were, for the second year in a row, at a great location in the "
"Congress, in\n"
"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square "
"has\n"
"really increased our visibility and helped many people find us. Thanks to"
" Noisy\n"
"Square and the 31C3 organizers for a great Congress."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29
msgid ""
"We also thank Gabriel Weinberg and his fabulous search engine "
"`DuckDuckGo`_ for\n"
"their support of open source anonymity tools and their `generous "
"contribution`_\n"
"to I2P in 2014. Funding from DuckDuckGo and others helped support our "
"attendance\n"
"at CCC. This is the primary annual meetup for I2P developers and it is "
"critical\n"
"to our success."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38
msgid "`generous contribution`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40
msgid ""
"Discussions with others\n"
"======================="
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48
msgid ""
"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved "
"himself\n"
"and the project from TU Munich to `Inria`_ in France. He has a large "
"number of\n"
"`open positions`_. This is a great opportunity to get paid to work on "
"open\n"
"source anonymity tools, we encourage everybody to contact him about it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57
#, fuzzy
msgid "`open positions`"
msgstr "`nominations`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59
msgid ""
"The prospect of an invigorated GNUnet with a large amount of new funding "
"is\n"
"quite interesting. We discussed more ways to work together. In early "
"2014, we\n"
"worked hard to understand the GnuNet DNS replacement, but we were unable "
"to\n"
"figure out a good fit for it in I2P. One of his new ideas is a "
"distributed,\n"
"anonymous statistics gathering subsystem, for detecting problems or "
"attacks on\n"
"the network. We'd definitely be interested in that."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68
msgid ""
"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems "
"draft`_.\n"
"A new, greatly simplified version 3 was posted in December. The prospects"
" for\n"
"approval remain unclear. The best way to monitor or participate in the\n"
"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to "
"do so\n"
"on our side, and also give Hellekin a new point-of-contact for this topic."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76
msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77
msgid "`IETF DNSOP WG mailing list`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79
msgid ""
"We apologized to Christian for not being organized enough to have a talk "
"at his\n"
"`We Fix The Net assembly`_. One of our biggest failures is a project is "
"our\n"
"seeming inability to submit talks at conferences. We'll have to do better"
" in the\n"
"new year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86
msgid "`We Fix The Net assembly`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91
msgid ""
"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in "
"with\n"
"other anonymity tools into this new Debian \"superpackage\" of some sort,"
" and\n"
"would love to get I2P into Debian in 2015. He claims the process is now "
"easy,\n"
"just `follow the instructions`_. We said that's funny, we've been\n"
"`stuck in the process for over 7 years`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99
msgid "`follow the instructions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100
msgid "`stuck in the process for over 7 years`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102
msgid ""
"He said, well, try the new process, it works great, should be no problem "
"at all\n"
"if your package is in good shape. The people in Debian that run this "
"process are\n"
"eager volunteers who want nothing more than to get more packages in. We "
"said our\n"
"package is indeed in fantastic shape, and we would try out the new "
"process as\n"
"soon as possible. As best as we can tell, we are orphaned in the old "
"process and\n"
"have to restart in the new process? If all this is true, we will be in "
"the next\n"
"Debian release in late 2015. This would be very very cool."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:115
msgid ""
"We had a nice discussion with BitingBird of Tails. They are very happy "
"with our\n"
"rapid response to the `vulnerability disclosure`_ last summer, resulting "
"in our\n"
"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and "
"they\n"
"took `great offense`_ to that and the lack of private notification. We "
"thanked\n"
"them for taking the heat and fighting back."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123
msgid "`vulnerability disclosure`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124
#, fuzzy
msgid "`0.9.14 release`"
msgstr "Release 0.9.4"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:125
msgid "`great offense`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:127
msgid ""
"Biting Bird also handles support, and she tells us the number one issue "
"is how\n"
"long I2P takes to start up and be useful for browsing I2P sites. Her "
"standard\n"
"answer is \"wait ten more minutes\" and that seems to be effective. I2P "
"is\n"
"particularly slow to startup on Tails since it does not persist peer data"
" by\n"
"default. It would be nice to change that, but there's also things we can "
"do on\n"
"the I2P side to make things start faster. Expect some improvement in our "
"0.9.18\n"
"release."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:140
msgid ""
"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The "
"upcoming\n"
"Tor Hidden Services changes mean that their keys will no longer fit into "
"a\n"
"portion of an IPv6 address, and he was working on a solution. We reminded"
" him\n"
"that this has always been the case for I2P (with \"GarliCat\"), that it's"
" not a\n"
"new problem. He pointed us to `a presentation`_ of his proposal. It "
"involves\n"
"storing an extra record in the hidden service directory (equivalent of a\n"
"leaseset I2P's network database). It wasn't completely clear how this "
"would\n"
"work, or if we would consider it abuse of the netDb. We'll follow up with"
" him\n"
"as he gets further."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:153
msgid "`a presentation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:155
msgid ""
"New users\n"
"---------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:160
msgid ""
"We spent hours and hours explaining I2P to people stopping by our table. "
"Some\n"
"had heard of I2P before, some had not; everybody had heard of Tor and had"
" at\n"
"least a vague idea of what hidden services are. As usual, introducing "
"people to\n"
"I2P was a struggle. By the end of the Congress, we became convinced that "
"a part\n"
"of the problem was a difference in terminology. Back 12 years ago, when "
"I2P and\n"
"Tor were both getting started, we each came up with terms for the various"
" parts\n"
"of our systems. Today, the Tor terminology such as \"hidden service\" is\n"
"well-understood and commonplace. The I2P terminology such as \"eepsite\" "
"is\n"
"neither. We agreed to review our documentation, router console, and other"
" places\n"
"for opportunities to simplify it and use common terms."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:173
msgid ""
"I2P project topics\n"
"------------------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:178
msgid ""
"* *Spending money:* We discussed several ways to effectively use our "
"resources\n"
" in 2015, including more hardware for testing and development. Also, we "
"plan to\n"
" increase reimbursement levels for conference attendees."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:184
msgid ""
"* *Toronto meetup:* CCC is such a productive time for us, and it seems "
"that a\n"
" second meetup in the year would be quite helpful. We have proposed it "
"for\n"
" August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. "
"It\n"
" would include developer meetings together with presentations and "
"tutorials,\n"
" all open to the public. We are attempting to gauge interest and "
"research\n"
" possible venues. If you are considering attending, please let us know "
"by\n"
" `tweeting @i2p`_ or posting `on the dev forum thread`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:194
msgid ""
"* We discussed Meeh's workload and the state of the various services he "
"is\n"
" running. We made some plans to reduce his load and have some other "
"people help\n"
" out."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:200
msgid ""
"* We reviewed our critieria for placing links to `i2pd`_ on our download "
"page.\n"
" We agreed that the only remaining item is to have a nice page on the\n"
" `Privacy Solutions web site`_ or elsewhere with binary packages for "
"Windows,\n"
" Linux, and Mac, and source packages. It's not clear who is responsible "
"for\n"
" building the packages and where the \"official\" version is. Once "
"there's an\n"
" established process for building and signing packages and an official "
"place to\n"
" put them, we're ready to link to it. If it is not feasible to host it "
"on the\n"
" Privacy Solutions website, we will discuss alternatives with orignal,\n"
" including possible migration to our download servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:212
msgid ""
"* Lots of people coming by the table asked if we had a non-Java version. "
"It was\n"
" great to finally answer \"yes\" and we're eager to get the word out and"
" get more\n"
" users, testers, and developers on it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:218
msgid ""
"* `Vuze`_ continues to make good progress on their I2P integration. We "
"look\n"
" forward to working with them in the new year on a managed rollout to "
"more\n"
" users."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:224
msgid ""
"* We discussed the state of Meeh's and Sindu's reseed servers. They made "
"several\n"
" improvements while at the congress and are investigating migration to\n"
" `Matt Drollette's Go implementation`_. The security and reliability of "
"our\n"
" reseed servers is vital to new users and network operation. `User "
"'backup'`_\n"
" is doing a great job monitoring and managing the pool of reseed servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:232
msgid ""
"* We agreed to purchase a second root server for development, testing, "
"and\n"
" services. Echelon will be adminstering it. Contact him is you would "
"like a VM."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:237
msgid ""
"* We reiterated that we have funds available to purchase test hardware,\n"
" especially for Windows and Mac. Talk to echelon for details."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:242
msgid ""
"* We met with Welterde about the state of his services including his\n"
" `open tracker`_. These services are not being adequately maintained and"
" will\n"
" soon become inaccessible due to crypto changes if they are not "
"upgraded. He\n"
" committed to upgrading them soon."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:249
msgid ""
"* We met lots of people interested in our `Android app`_. We passed "
"several\n"
" ideas and bug reports back to str4d. We plan to make a big push to give"
" the\n"
" app some development love early in the year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:255
msgid ""
"* Regrettably, we didn't get to see too many talks at the Congress, as we"
" were\n"
" so busy meeting with people. We plan to catch up and `watch them "
"online`_. As\n"
" usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's "
"talk was\n"
" great. We hear that the cryptography talks were good as well."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262
msgid "`Toronto Crypto`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263
msgid "`tweeting @i2p`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:264
msgid "`on the dev forum thread`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:267
#, fuzzy
msgid "`Privacy Solutions web site`"
msgstr "`notre site web`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271
msgid "`Matt Drollette's Go implementation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:272
msgid "`User 'backup'`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:274
#, fuzzy
msgid "`open tracker`"
msgstr "`sur Twitter`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:276
msgid "`Android app`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:278
msgid "`watch them online`"
msgstr ""

415
i2p2www/translations/he/LC_MESSAGES/blog.po
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2014-12-02 23:11+0000\n"
"POT-Creation-Date: 2015-01-21 03:46+0000\n"
"PO-Revision-Date: 2014-02-09 19:53+0000\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: he <LL@li.org>\n"
@ -3226,3 +3226,416 @@ msgstr ""
msgid "`click here`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1
msgid ""
"================\n"
"31C3 trip report\n"
"================"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9
msgid ""
"CCC has always been a productive time for us, and 31C3 was no exception. "
"Here is a summary of our various meetings and discussions."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20
msgid ""
"We were, for the second year in a row, at a great location in the "
"Congress, in\n"
"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square "
"has\n"
"really increased our visibility and helped many people find us. Thanks to"
" Noisy\n"
"Square and the 31C3 organizers for a great Congress."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29
msgid ""
"We also thank Gabriel Weinberg and his fabulous search engine "
"`DuckDuckGo`_ for\n"
"their support of open source anonymity tools and their `generous "
"contribution`_\n"
"to I2P in 2014. Funding from DuckDuckGo and others helped support our "
"attendance\n"
"at CCC. This is the primary annual meetup for I2P developers and it is "
"critical\n"
"to our success."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38
msgid "`generous contribution`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40
msgid ""
"Discussions with others\n"
"======================="
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48
msgid ""
"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved "
"himself\n"
"and the project from TU Munich to `Inria`_ in France. He has a large "
"number of\n"
"`open positions`_. This is a great opportunity to get paid to work on "
"open\n"
"source anonymity tools, we encourage everybody to contact him about it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57
msgid "`open positions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59
msgid ""
"The prospect of an invigorated GNUnet with a large amount of new funding "
"is\n"
"quite interesting. We discussed more ways to work together. In early "
"2014, we\n"
"worked hard to understand the GnuNet DNS replacement, but we were unable "
"to\n"
"figure out a good fit for it in I2P. One of his new ideas is a "
"distributed,\n"
"anonymous statistics gathering subsystem, for detecting problems or "
"attacks on\n"
"the network. We'd definitely be interested in that."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68
msgid ""
"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems "
"draft`_.\n"
"A new, greatly simplified version 3 was posted in December. The prospects"
" for\n"
"approval remain unclear. The best way to monitor or participate in the\n"
"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to "
"do so\n"
"on our side, and also give Hellekin a new point-of-contact for this topic."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76
msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77
msgid "`IETF DNSOP WG mailing list`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79
msgid ""
"We apologized to Christian for not being organized enough to have a talk "
"at his\n"
"`We Fix The Net assembly`_. One of our biggest failures is a project is "
"our\n"
"seeming inability to submit talks at conferences. We'll have to do better"
" in the\n"
"new year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86
msgid "`We Fix The Net assembly`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91
msgid ""
"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in "
"with\n"
"other anonymity tools into this new Debian \"superpackage\" of some sort,"
" and\n"
"would love to get I2P into Debian in 2015. He claims the process is now "
"easy,\n"
"just `follow the instructions`_. We said that's funny, we've been\n"
"`stuck in the process for over 7 years`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99
msgid "`follow the instructions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100
msgid "`stuck in the process for over 7 years`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102
msgid ""
"He said, well, try the new process, it works great, should be no problem "
"at all\n"
"if your package is in good shape. The people in Debian that run this "
"process are\n"
"eager volunteers who want nothing more than to get more packages in. We "
"said our\n"
"package is indeed in fantastic shape, and we would try out the new "
"process as\n"
"soon as possible. As best as we can tell, we are orphaned in the old "
"process and\n"
"have to restart in the new process? If all this is true, we will be in "
"the next\n"
"Debian release in late 2015. This would be very very cool."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:115
msgid ""
"We had a nice discussion with BitingBird of Tails. They are very happy "
"with our\n"
"rapid response to the `vulnerability disclosure`_ last summer, resulting "
"in our\n"
"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and "
"they\n"
"took `great offense`_ to that and the lack of private notification. We "
"thanked\n"
"them for taking the heat and fighting back."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123
msgid "`vulnerability disclosure`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124
msgid "`0.9.14 release`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:125
msgid "`great offense`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:127
msgid ""
"Biting Bird also handles support, and she tells us the number one issue "
"is how\n"
"long I2P takes to start up and be useful for browsing I2P sites. Her "
"standard\n"
"answer is \"wait ten more minutes\" and that seems to be effective. I2P "
"is\n"
"particularly slow to startup on Tails since it does not persist peer data"
" by\n"
"default. It would be nice to change that, but there's also things we can "
"do on\n"
"the I2P side to make things start faster. Expect some improvement in our "
"0.9.18\n"
"release."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:140
msgid ""
"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The "
"upcoming\n"
"Tor Hidden Services changes mean that their keys will no longer fit into "
"a\n"
"portion of an IPv6 address, and he was working on a solution. We reminded"
" him\n"
"that this has always been the case for I2P (with \"GarliCat\"), that it's"
" not a\n"
"new problem. He pointed us to `a presentation`_ of his proposal. It "
"involves\n"
"storing an extra record in the hidden service directory (equivalent of a\n"
"leaseset I2P's network database). It wasn't completely clear how this "
"would\n"
"work, or if we would consider it abuse of the netDb. We'll follow up with"
" him\n"
"as he gets further."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:153
msgid "`a presentation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:155
msgid ""
"New users\n"
"---------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:160
msgid ""
"We spent hours and hours explaining I2P to people stopping by our table. "
"Some\n"
"had heard of I2P before, some had not; everybody had heard of Tor and had"
" at\n"
"least a vague idea of what hidden services are. As usual, introducing "
"people to\n"
"I2P was a struggle. By the end of the Congress, we became convinced that "
"a part\n"
"of the problem was a difference in terminology. Back 12 years ago, when "
"I2P and\n"
"Tor were both getting started, we each came up with terms for the various"
" parts\n"
"of our systems. Today, the Tor terminology such as \"hidden service\" is\n"
"well-understood and commonplace. The I2P terminology such as \"eepsite\" "
"is\n"
"neither. We agreed to review our documentation, router console, and other"
" places\n"
"for opportunities to simplify it and use common terms."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:173
msgid ""
"I2P project topics\n"
"------------------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:178
msgid ""
"* *Spending money:* We discussed several ways to effectively use our "
"resources\n"
" in 2015, including more hardware for testing and development. Also, we "
"plan to\n"
" increase reimbursement levels for conference attendees."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:184
msgid ""
"* *Toronto meetup:* CCC is such a productive time for us, and it seems "
"that a\n"
" second meetup in the year would be quite helpful. We have proposed it "
"for\n"
" August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. "
"It\n"
" would include developer meetings together with presentations and "
"tutorials,\n"
" all open to the public. We are attempting to gauge interest and "
"research\n"
" possible venues. If you are considering attending, please let us know "
"by\n"
" `tweeting @i2p`_ or posting `on the dev forum thread`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:194
msgid ""
"* We discussed Meeh's workload and the state of the various services he "
"is\n"
" running. We made some plans to reduce his load and have some other "
"people help\n"
" out."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:200
msgid ""
"* We reviewed our critieria for placing links to `i2pd`_ on our download "
"page.\n"
" We agreed that the only remaining item is to have a nice page on the\n"
" `Privacy Solutions web site`_ or elsewhere with binary packages for "
"Windows,\n"
" Linux, and Mac, and source packages. It's not clear who is responsible "
"for\n"
" building the packages and where the \"official\" version is. Once "
"there's an\n"
" established process for building and signing packages and an official "
"place to\n"
" put them, we're ready to link to it. If it is not feasible to host it "
"on the\n"
" Privacy Solutions website, we will discuss alternatives with orignal,\n"
" including possible migration to our download servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:212
msgid ""
"* Lots of people coming by the table asked if we had a non-Java version. "
"It was\n"
" great to finally answer \"yes\" and we're eager to get the word out and"
" get more\n"
" users, testers, and developers on it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:218
msgid ""
"* `Vuze`_ continues to make good progress on their I2P integration. We "
"look\n"
" forward to working with them in the new year on a managed rollout to "
"more\n"
" users."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:224
msgid ""
"* We discussed the state of Meeh's and Sindu's reseed servers. They made "
"several\n"
" improvements while at the congress and are investigating migration to\n"
" `Matt Drollette's Go implementation`_. The security and reliability of "
"our\n"
" reseed servers is vital to new users and network operation. `User "
"'backup'`_\n"
" is doing a great job monitoring and managing the pool of reseed servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:232
msgid ""
"* We agreed to purchase a second root server for development, testing, "
"and\n"
" services. Echelon will be adminstering it. Contact him is you would "
"like a VM."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:237
msgid ""
"* We reiterated that we have funds available to purchase test hardware,\n"
" especially for Windows and Mac. Talk to echelon for details."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:242
msgid ""
"* We met with Welterde about the state of his services including his\n"
" `open tracker`_. These services are not being adequately maintained and"
" will\n"
" soon become inaccessible due to crypto changes if they are not "
"upgraded. He\n"
" committed to upgrading them soon."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:249
msgid ""
"* We met lots of people interested in our `Android app`_. We passed "
"several\n"
" ideas and bug reports back to str4d. We plan to make a big push to give"
" the\n"
" app some development love early in the year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:255
msgid ""
"* Regrettably, we didn't get to see too many talks at the Congress, as we"
" were\n"
" so busy meeting with people. We plan to catch up and `watch them "
"online`_. As\n"
" usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's "
"talk was\n"
" great. We hear that the cryptography talks were good as well."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262
msgid "`Toronto Crypto`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263
msgid "`tweeting @i2p`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:264
msgid "`on the dev forum thread`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:267
msgid "`Privacy Solutions web site`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271
msgid "`Matt Drollette's Go implementation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:272
msgid "`User 'backup'`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:274
msgid "`open tracker`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:276
msgid "`Android app`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:278
msgid "`watch them online`"
msgstr ""

420
i2p2www/translations/ja/LC_MESSAGES/blog.po
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2014-12-02 23:11+0000\n"
"POT-Creation-Date: 2015-01-21 03:46+0000\n"
"PO-Revision-Date: 2014-05-23 23:34+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Japanese "
@ -3278,3 +3278,421 @@ msgstr ""
msgid "`click here`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1
#, fuzzy
msgid ""
"================\n"
"31C3 trip report\n"
"================"
msgstr ""
"==============\n"
"0.9.11 リリース\n"
"=============="
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9
msgid ""
"CCC has always been a productive time for us, and 31C3 was no exception. "
"Here is a summary of our various meetings and discussions."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20
msgid ""
"We were, for the second year in a row, at a great location in the "
"Congress, in\n"
"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square "
"has\n"
"really increased our visibility and helped many people find us. Thanks to"
" Noisy\n"
"Square and the 31C3 organizers for a great Congress."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29
msgid ""
"We also thank Gabriel Weinberg and his fabulous search engine "
"`DuckDuckGo`_ for\n"
"their support of open source anonymity tools and their `generous "
"contribution`_\n"
"to I2P in 2014. Funding from DuckDuckGo and others helped support our "
"attendance\n"
"at CCC. This is the primary annual meetup for I2P developers and it is "
"critical\n"
"to our success."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38
msgid "`generous contribution`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40
msgid ""
"Discussions with others\n"
"======================="
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48
msgid ""
"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved "
"himself\n"
"and the project from TU Munich to `Inria`_ in France. He has a large "
"number of\n"
"`open positions`_. This is a great opportunity to get paid to work on "
"open\n"
"source anonymity tools, we encourage everybody to contact him about it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57
msgid "`open positions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59
msgid ""
"The prospect of an invigorated GNUnet with a large amount of new funding "
"is\n"
"quite interesting. We discussed more ways to work together. In early "
"2014, we\n"
"worked hard to understand the GnuNet DNS replacement, but we were unable "
"to\n"
"figure out a good fit for it in I2P. One of his new ideas is a "
"distributed,\n"
"anonymous statistics gathering subsystem, for detecting problems or "
"attacks on\n"
"the network. We'd definitely be interested in that."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68
msgid ""
"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems "
"draft`_.\n"
"A new, greatly simplified version 3 was posted in December. The prospects"
" for\n"
"approval remain unclear. The best way to monitor or participate in the\n"
"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to "
"do so\n"
"on our side, and also give Hellekin a new point-of-contact for this topic."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76
msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77
msgid "`IETF DNSOP WG mailing list`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79
msgid ""
"We apologized to Christian for not being organized enough to have a talk "
"at his\n"
"`We Fix The Net assembly`_. One of our biggest failures is a project is "
"our\n"
"seeming inability to submit talks at conferences. We'll have to do better"
" in the\n"
"new year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86
msgid "`We Fix The Net assembly`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91
msgid ""
"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in "
"with\n"
"other anonymity tools into this new Debian \"superpackage\" of some sort,"
" and\n"
"would love to get I2P into Debian in 2015. He claims the process is now "
"easy,\n"
"just `follow the instructions`_. We said that's funny, we've been\n"
"`stuck in the process for over 7 years`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99
msgid "`follow the instructions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100
msgid "`stuck in the process for over 7 years`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102
msgid ""
"He said, well, try the new process, it works great, should be no problem "
"at all\n"
"if your package is in good shape. The people in Debian that run this "
"process are\n"
"eager volunteers who want nothing more than to get more packages in. We "
"said our\n"
"package is indeed in fantastic shape, and we would try out the new "
"process as\n"
"soon as possible. As best as we can tell, we are orphaned in the old "
"process and\n"
"have to restart in the new process? If all this is true, we will be in "
"the next\n"
"Debian release in late 2015. This would be very very cool."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:115
msgid ""
"We had a nice discussion with BitingBird of Tails. They are very happy "
"with our\n"
"rapid response to the `vulnerability disclosure`_ last summer, resulting "
"in our\n"
"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and "
"they\n"
"took `great offense`_ to that and the lack of private notification. We "
"thanked\n"
"them for taking the heat and fighting back."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123
msgid "`vulnerability disclosure`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124
#, fuzzy
msgid "`0.9.14 release`"
msgstr "0.9.2 リリース"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:125
msgid "`great offense`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:127
msgid ""
"Biting Bird also handles support, and she tells us the number one issue "
"is how\n"
"long I2P takes to start up and be useful for browsing I2P sites. Her "
"standard\n"
"answer is \"wait ten more minutes\" and that seems to be effective. I2P "
"is\n"
"particularly slow to startup on Tails since it does not persist peer data"
" by\n"
"default. It would be nice to change that, but there's also things we can "
"do on\n"
"the I2P side to make things start faster. Expect some improvement in our "
"0.9.18\n"
"release."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:140
msgid ""
"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The "
"upcoming\n"
"Tor Hidden Services changes mean that their keys will no longer fit into "
"a\n"
"portion of an IPv6 address, and he was working on a solution. We reminded"
" him\n"
"that this has always been the case for I2P (with \"GarliCat\"), that it's"
" not a\n"
"new problem. He pointed us to `a presentation`_ of his proposal. It "
"involves\n"
"storing an extra record in the hidden service directory (equivalent of a\n"
"leaseset I2P's network database). It wasn't completely clear how this "
"would\n"
"work, or if we would consider it abuse of the netDb. We'll follow up with"
" him\n"
"as he gets further."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:153
msgid "`a presentation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:155
msgid ""
"New users\n"
"---------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:160
msgid ""
"We spent hours and hours explaining I2P to people stopping by our table. "
"Some\n"
"had heard of I2P before, some had not; everybody had heard of Tor and had"
" at\n"
"least a vague idea of what hidden services are. As usual, introducing "
"people to\n"
"I2P was a struggle. By the end of the Congress, we became convinced that "
"a part\n"
"of the problem was a difference in terminology. Back 12 years ago, when "
"I2P and\n"
"Tor were both getting started, we each came up with terms for the various"
" parts\n"
"of our systems. Today, the Tor terminology such as \"hidden service\" is\n"
"well-understood and commonplace. The I2P terminology such as \"eepsite\" "
"is\n"
"neither. We agreed to review our documentation, router console, and other"
" places\n"
"for opportunities to simplify it and use common terms."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:173
msgid ""
"I2P project topics\n"
"------------------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:178
msgid ""
"* *Spending money:* We discussed several ways to effectively use our "
"resources\n"
" in 2015, including more hardware for testing and development. Also, we "
"plan to\n"
" increase reimbursement levels for conference attendees."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:184
msgid ""
"* *Toronto meetup:* CCC is such a productive time for us, and it seems "
"that a\n"
" second meetup in the year would be quite helpful. We have proposed it "
"for\n"
" August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. "
"It\n"
" would include developer meetings together with presentations and "
"tutorials,\n"
" all open to the public. We are attempting to gauge interest and "
"research\n"
" possible venues. If you are considering attending, please let us know "
"by\n"
" `tweeting @i2p`_ or posting `on the dev forum thread`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:194
msgid ""
"* We discussed Meeh's workload and the state of the various services he "
"is\n"
" running. We made some plans to reduce his load and have some other "
"people help\n"
" out."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:200
msgid ""
"* We reviewed our critieria for placing links to `i2pd`_ on our download "
"page.\n"
" We agreed that the only remaining item is to have a nice page on the\n"
" `Privacy Solutions web site`_ or elsewhere with binary packages for "
"Windows,\n"
" Linux, and Mac, and source packages. It's not clear who is responsible "
"for\n"
" building the packages and where the \"official\" version is. Once "
"there's an\n"
" established process for building and signing packages and an official "
"place to\n"
" put them, we're ready to link to it. If it is not feasible to host it "
"on the\n"
" Privacy Solutions website, we will discuss alternatives with orignal,\n"
" including possible migration to our download servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:212
msgid ""
"* Lots of people coming by the table asked if we had a non-Java version. "
"It was\n"
" great to finally answer \"yes\" and we're eager to get the word out and"
" get more\n"
" users, testers, and developers on it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:218
msgid ""
"* `Vuze`_ continues to make good progress on their I2P integration. We "
"look\n"
" forward to working with them in the new year on a managed rollout to "
"more\n"
" users."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:224
msgid ""
"* We discussed the state of Meeh's and Sindu's reseed servers. They made "
"several\n"
" improvements while at the congress and are investigating migration to\n"
" `Matt Drollette's Go implementation`_. The security and reliability of "
"our\n"
" reseed servers is vital to new users and network operation. `User "
"'backup'`_\n"
" is doing a great job monitoring and managing the pool of reseed servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:232
msgid ""
"* We agreed to purchase a second root server for development, testing, "
"and\n"
" services. Echelon will be adminstering it. Contact him is you would "
"like a VM."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:237
msgid ""
"* We reiterated that we have funds available to purchase test hardware,\n"
" especially for Windows and Mac. Talk to echelon for details."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:242
msgid ""
"* We met with Welterde about the state of his services including his\n"
" `open tracker`_. These services are not being adequately maintained and"
" will\n"
" soon become inaccessible due to crypto changes if they are not "
"upgraded. He\n"
" committed to upgrading them soon."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:249
msgid ""
"* We met lots of people interested in our `Android app`_. We passed "
"several\n"
" ideas and bug reports back to str4d. We plan to make a big push to give"
" the\n"
" app some development love early in the year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:255
msgid ""
"* Regrettably, we didn't get to see too many talks at the Congress, as we"
" were\n"
" so busy meeting with people. We plan to catch up and `watch them "
"online`_. As\n"
" usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's "
"talk was\n"
" great. We hear that the cryptography talks were good as well."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262
msgid "`Toronto Crypto`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263
msgid "`tweeting @i2p`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:264
msgid "`on the dev forum thread`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:267
msgid "`Privacy Solutions web site`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271
msgid "`Matt Drollette's Go implementation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:272
msgid "`User 'backup'`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:274
msgid "`open tracker`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:276
msgid "`Android app`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:278
msgid "`watch them online`"
msgstr ""

423
i2p2www/translations/pt_BR/LC_MESSAGES/blog.po
View File

@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2014-12-02 23:11+0000\n"
"POT-Creation-Date: 2015-01-21 03:46+0000\n"
"PO-Revision-Date: 2015-01-12 03:45+0000\n"
"Last-Translator: blueboy\n"
"Language-Team: Portuguese (Brazil) "
@ -3343,3 +3343,424 @@ msgstr ""
msgid "`click here`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1
#, fuzzy
msgid ""
"================\n"
"31C3 trip report\n"
"================"
msgstr ""
"=============================\n"
"Lançamento da versão 0.9.14.1\n"
"============================="
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9
msgid ""
"CCC has always been a productive time for us, and 31C3 was no exception. "
"Here is a summary of our various meetings and discussions."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20
msgid ""
"We were, for the second year in a row, at a great location in the "
"Congress, in\n"
"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square "
"has\n"
"really increased our visibility and helped many people find us. Thanks to"
" Noisy\n"
"Square and the 31C3 organizers for a great Congress."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29
msgid ""
"We also thank Gabriel Weinberg and his fabulous search engine "
"`DuckDuckGo`_ for\n"
"their support of open source anonymity tools and their `generous "
"contribution`_\n"
"to I2P in 2014. Funding from DuckDuckGo and others helped support our "
"attendance\n"
"at CCC. This is the primary annual meetup for I2P developers and it is "
"critical\n"
"to our success."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38
msgid "`generous contribution`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40
msgid ""
"Discussions with others\n"
"======================="
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48
msgid ""
"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved "
"himself\n"
"and the project from TU Munich to `Inria`_ in France. He has a large "
"number of\n"
"`open positions`_. This is a great opportunity to get paid to work on "
"open\n"
"source anonymity tools, we encourage everybody to contact him about it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57
#, fuzzy
msgid "`open positions`"
msgstr "`nomeações`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59
msgid ""
"The prospect of an invigorated GNUnet with a large amount of new funding "
"is\n"
"quite interesting. We discussed more ways to work together. In early "
"2014, we\n"
"worked hard to understand the GnuNet DNS replacement, but we were unable "
"to\n"
"figure out a good fit for it in I2P. One of his new ideas is a "
"distributed,\n"
"anonymous statistics gathering subsystem, for detecting problems or "
"attacks on\n"
"the network. We'd definitely be interested in that."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68
msgid ""
"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems "
"draft`_.\n"
"A new, greatly simplified version 3 was posted in December. The prospects"
" for\n"
"approval remain unclear. The best way to monitor or participate in the\n"
"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to "
"do so\n"
"on our side, and also give Hellekin a new point-of-contact for this topic."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76
msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77
msgid "`IETF DNSOP WG mailing list`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79
msgid ""
"We apologized to Christian for not being organized enough to have a talk "
"at his\n"
"`We Fix The Net assembly`_. One of our biggest failures is a project is "
"our\n"
"seeming inability to submit talks at conferences. We'll have to do better"
" in the\n"
"new year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86
msgid "`We Fix The Net assembly`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91
msgid ""
"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in "
"with\n"
"other anonymity tools into this new Debian \"superpackage\" of some sort,"
" and\n"
"would love to get I2P into Debian in 2015. He claims the process is now "
"easy,\n"
"just `follow the instructions`_. We said that's funny, we've been\n"
"`stuck in the process for over 7 years`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99
msgid "`follow the instructions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100
msgid "`stuck in the process for over 7 years`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102
msgid ""
"He said, well, try the new process, it works great, should be no problem "
"at all\n"
"if your package is in good shape. The people in Debian that run this "
"process are\n"
"eager volunteers who want nothing more than to get more packages in. We "
"said our\n"
"package is indeed in fantastic shape, and we would try out the new "
"process as\n"
"soon as possible. As best as we can tell, we are orphaned in the old "
"process and\n"
"have to restart in the new process? If all this is true, we will be in "
"the next\n"
"Debian release in late 2015. This would be very very cool."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:115
msgid ""
"We had a nice discussion with BitingBird of Tails. They are very happy "
"with our\n"
"rapid response to the `vulnerability disclosure`_ last summer, resulting "
"in our\n"
"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and "
"they\n"
"took `great offense`_ to that and the lack of private notification. We "
"thanked\n"
"them for taking the heat and fighting back."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123
msgid "`vulnerability disclosure`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124
#, fuzzy
msgid "`0.9.14 release`"
msgstr "Lançamento da versão 0.9.4"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:125
msgid "`great offense`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:127
msgid ""
"Biting Bird also handles support, and she tells us the number one issue "
"is how\n"
"long I2P takes to start up and be useful for browsing I2P sites. Her "
"standard\n"
"answer is \"wait ten more minutes\" and that seems to be effective. I2P "
"is\n"
"particularly slow to startup on Tails since it does not persist peer data"
" by\n"
"default. It would be nice to change that, but there's also things we can "
"do on\n"
"the I2P side to make things start faster. Expect some improvement in our "
"0.9.18\n"
"release."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:140
msgid ""
"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The "
"upcoming\n"
"Tor Hidden Services changes mean that their keys will no longer fit into "
"a\n"
"portion of an IPv6 address, and he was working on a solution. We reminded"
" him\n"
"that this has always been the case for I2P (with \"GarliCat\"), that it's"
" not a\n"
"new problem. He pointed us to `a presentation`_ of his proposal. It "
"involves\n"
"storing an extra record in the hidden service directory (equivalent of a\n"
"leaseset I2P's network database). It wasn't completely clear how this "
"would\n"
"work, or if we would consider it abuse of the netDb. We'll follow up with"
" him\n"
"as he gets further."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:153
msgid "`a presentation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:155
msgid ""
"New users\n"
"---------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:160
msgid ""
"We spent hours and hours explaining I2P to people stopping by our table. "
"Some\n"
"had heard of I2P before, some had not; everybody had heard of Tor and had"
" at\n"
"least a vague idea of what hidden services are. As usual, introducing "
"people to\n"
"I2P was a struggle. By the end of the Congress, we became convinced that "
"a part\n"
"of the problem was a difference in terminology. Back 12 years ago, when "
"I2P and\n"
"Tor were both getting started, we each came up with terms for the various"
" parts\n"
"of our systems. Today, the Tor terminology such as \"hidden service\" is\n"
"well-understood and commonplace. The I2P terminology such as \"eepsite\" "
"is\n"
"neither. We agreed to review our documentation, router console, and other"
" places\n"
"for opportunities to simplify it and use common terms."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:173
msgid ""
"I2P project topics\n"
"------------------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:178
msgid ""
"* *Spending money:* We discussed several ways to effectively use our "
"resources\n"
" in 2015, including more hardware for testing and development. Also, we "
"plan to\n"
" increase reimbursement levels for conference attendees."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:184
msgid ""
"* *Toronto meetup:* CCC is such a productive time for us, and it seems "
"that a\n"
" second meetup in the year would be quite helpful. We have proposed it "
"for\n"
" August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. "
"It\n"
" would include developer meetings together with presentations and "
"tutorials,\n"
" all open to the public. We are attempting to gauge interest and "
"research\n"
" possible venues. If you are considering attending, please let us know "
"by\n"
" `tweeting @i2p`_ or posting `on the dev forum thread`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:194
msgid ""
"* We discussed Meeh's workload and the state of the various services he "
"is\n"
" running. We made some plans to reduce his load and have some other "
"people help\n"
" out."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:200
msgid ""
"* We reviewed our critieria for placing links to `i2pd`_ on our download "
"page.\n"
" We agreed that the only remaining item is to have a nice page on the\n"
" `Privacy Solutions web site`_ or elsewhere with binary packages for "
"Windows,\n"
" Linux, and Mac, and source packages. It's not clear who is responsible "
"for\n"
" building the packages and where the \"official\" version is. Once "
"there's an\n"
" established process for building and signing packages and an official "
"place to\n"
" put them, we're ready to link to it. If it is not feasible to host it "
"on the\n"
" Privacy Solutions website, we will discuss alternatives with orignal,\n"
" including possible migration to our download servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:212
msgid ""
"* Lots of people coming by the table asked if we had a non-Java version. "
"It was\n"
" great to finally answer \"yes\" and we're eager to get the word out and"
" get more\n"
" users, testers, and developers on it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:218
msgid ""
"* `Vuze`_ continues to make good progress on their I2P integration. We "
"look\n"
" forward to working with them in the new year on a managed rollout to "
"more\n"
" users."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:224
msgid ""
"* We discussed the state of Meeh's and Sindu's reseed servers. They made "
"several\n"
" improvements while at the congress and are investigating migration to\n"
" `Matt Drollette's Go implementation`_. The security and reliability of "
"our\n"
" reseed servers is vital to new users and network operation. `User "
"'backup'`_\n"
" is doing a great job monitoring and managing the pool of reseed servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:232
msgid ""
"* We agreed to purchase a second root server for development, testing, "
"and\n"
" services. Echelon will be adminstering it. Contact him is you would "
"like a VM."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:237
msgid ""
"* We reiterated that we have funds available to purchase test hardware,\n"
" especially for Windows and Mac. Talk to echelon for details."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:242
msgid ""
"* We met with Welterde about the state of his services including his\n"
" `open tracker`_. These services are not being adequately maintained and"
" will\n"
" soon become inaccessible due to crypto changes if they are not "
"upgraded. He\n"
" committed to upgrading them soon."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:249
msgid ""
"* We met lots of people interested in our `Android app`_. We passed "
"several\n"
" ideas and bug reports back to str4d. We plan to make a big push to give"
" the\n"
" app some development love early in the year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:255
msgid ""
"* Regrettably, we didn't get to see too many talks at the Congress, as we"
" were\n"
" so busy meeting with people. We plan to catch up and `watch them "
"online`_. As\n"
" usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's "
"talk was\n"
" great. We hear that the cryptography talks were good as well."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262
msgid "`Toronto Crypto`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263
msgid "`tweeting @i2p`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:264
msgid "`on the dev forum thread`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:267
#, fuzzy
msgid "`Privacy Solutions web site`"
msgstr "`O Projeto SOLUÇÕES PARA PRIVACIDADE`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271
msgid "`Matt Drollette's Go implementation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:272
msgid "`User 'backup'`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:274
#, fuzzy
msgid "`open tracker`"
msgstr "`no Twitter`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:276
msgid "`Android app`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:278
msgid "`watch them online`"
msgstr ""

430
i2p2www/translations/ru/LC_MESSAGES/blog.po
View File

@ -15,7 +15,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2014-12-02 23:11+0000\n"
"POT-Creation-Date: 2015-01-21 03:46+0000\n"
"PO-Revision-Date: 2014-12-29 13:19+0000\n"
"Last-Translator: yume\n"
"Language-Team: Russian (Russia) "
@ -4072,3 +4072,431 @@ msgstr ""
msgid "`click here`"
msgstr "`нажмите сюда`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1
#, fuzzy
msgid ""
"================\n"
"31C3 trip report\n"
"================"
msgstr ""
"================\n"
"Версия 0.9.14.1\n"
"================"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9
msgid ""
"CCC has always been a productive time for us, and 31C3 was no exception. "
"Here is a summary of our various meetings and discussions."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20
msgid ""
"We were, for the second year in a row, at a great location in the "
"Congress, in\n"
"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square "
"has\n"
"really increased our visibility and helped many people find us. Thanks to"
" Noisy\n"
"Square and the 31C3 organizers for a great Congress."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29
msgid ""
"We also thank Gabriel Weinberg and his fabulous search engine "
"`DuckDuckGo`_ for\n"
"their support of open source anonymity tools and their `generous "
"contribution`_\n"
"to I2P in 2014. Funding from DuckDuckGo and others helped support our "
"attendance\n"
"at CCC. This is the primary annual meetup for I2P developers and it is "
"critical\n"
"to our success."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38
msgid "`generous contribution`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40
msgid ""
"Discussions with others\n"
"======================="
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48
msgid ""
"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved "
"himself\n"
"and the project from TU Munich to `Inria`_ in France. He has a large "
"number of\n"
"`open positions`_. This is a great opportunity to get paid to work on "
"open\n"
"source anonymity tools, we encourage everybody to contact him about it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57
#, fuzzy
msgid "`open positions`"
msgstr "`номинации`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59
msgid ""
"The prospect of an invigorated GNUnet with a large amount of new funding "
"is\n"
"quite interesting. We discussed more ways to work together. In early "
"2014, we\n"
"worked hard to understand the GnuNet DNS replacement, but we were unable "
"to\n"
"figure out a good fit for it in I2P. One of his new ideas is a "
"distributed,\n"
"anonymous statistics gathering subsystem, for detecting problems or "
"attacks on\n"
"the network. We'd definitely be interested in that."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68
msgid ""
"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems "
"draft`_.\n"
"A new, greatly simplified version 3 was posted in December. The prospects"
" for\n"
"approval remain unclear. The best way to monitor or participate in the\n"
"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to "
"do so\n"
"on our side, and also give Hellekin a new point-of-contact for this topic."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76
msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77
msgid "`IETF DNSOP WG mailing list`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79
msgid ""
"We apologized to Christian for not being organized enough to have a talk "
"at his\n"
"`We Fix The Net assembly`_. One of our biggest failures is a project is "
"our\n"
"seeming inability to submit talks at conferences. We'll have to do better"
" in the\n"
"new year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86
msgid "`We Fix The Net assembly`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91
msgid ""
"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in "
"with\n"
"other anonymity tools into this new Debian \"superpackage\" of some sort,"
" and\n"
"would love to get I2P into Debian in 2015. He claims the process is now "
"easy,\n"
"just `follow the instructions`_. We said that's funny, we've been\n"
"`stuck in the process for over 7 years`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99
msgid "`follow the instructions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100
msgid "`stuck in the process for over 7 years`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102
msgid ""
"He said, well, try the new process, it works great, should be no problem "
"at all\n"
"if your package is in good shape. The people in Debian that run this "
"process are\n"
"eager volunteers who want nothing more than to get more packages in. We "
"said our\n"
"package is indeed in fantastic shape, and we would try out the new "
"process as\n"
"soon as possible. As best as we can tell, we are orphaned in the old "
"process and\n"
"have to restart in the new process? If all this is true, we will be in "
"the next\n"
"Debian release in late 2015. This would be very very cool."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:115
msgid ""
"We had a nice discussion with BitingBird of Tails. They are very happy "
"with our\n"
"rapid response to the `vulnerability disclosure`_ last summer, resulting "
"in our\n"
"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and "
"they\n"
"took `great offense`_ to that and the lack of private notification. We "
"thanked\n"
"them for taking the heat and fighting back."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123
msgid "`vulnerability disclosure`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124
#, fuzzy
msgid "`0.9.14 release`"
msgstr "Версия 0.9.4"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:125
msgid "`great offense`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:127
msgid ""
"Biting Bird also handles support, and she tells us the number one issue "
"is how\n"
"long I2P takes to start up and be useful for browsing I2P sites. Her "
"standard\n"
"answer is \"wait ten more minutes\" and that seems to be effective. I2P "
"is\n"
"particularly slow to startup on Tails since it does not persist peer data"
" by\n"
"default. It would be nice to change that, but there's also things we can "
"do on\n"
"the I2P side to make things start faster. Expect some improvement in our "
"0.9.18\n"
"release."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:140
msgid ""
"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The "
"upcoming\n"
"Tor Hidden Services changes mean that their keys will no longer fit into "
"a\n"
"portion of an IPv6 address, and he was working on a solution. We reminded"
" him\n"
"that this has always been the case for I2P (with \"GarliCat\"), that it's"
" not a\n"
"new problem. He pointed us to `a presentation`_ of his proposal. It "
"involves\n"
"storing an extra record in the hidden service directory (equivalent of a\n"
"leaseset I2P's network database). It wasn't completely clear how this "
"would\n"
"work, or if we would consider it abuse of the netDb. We'll follow up with"
" him\n"
"as he gets further."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:153
msgid "`a presentation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:155
#, fuzzy
msgid ""
"New users\n"
"---------"
msgstr ""
"Новые версии приложения\n"
"----------------"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:160
msgid ""
"We spent hours and hours explaining I2P to people stopping by our table. "
"Some\n"
"had heard of I2P before, some had not; everybody had heard of Tor and had"
" at\n"
"least a vague idea of what hidden services are. As usual, introducing "
"people to\n"
"I2P was a struggle. By the end of the Congress, we became convinced that "
"a part\n"
"of the problem was a difference in terminology. Back 12 years ago, when "
"I2P and\n"
"Tor were both getting started, we each came up with terms for the various"
" parts\n"
"of our systems. Today, the Tor terminology such as \"hidden service\" is\n"
"well-understood and commonplace. The I2P terminology such as \"eepsite\" "
"is\n"
"neither. We agreed to review our documentation, router console, and other"
" places\n"
"for opportunities to simplify it and use common terms."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:173
#, fuzzy
msgid ""
"I2P project topics\n"
"------------------"
msgstr ""
"Новые версии приложения\n"
"----------------"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:178
msgid ""
"* *Spending money:* We discussed several ways to effectively use our "
"resources\n"
" in 2015, including more hardware for testing and development. Also, we "
"plan to\n"
" increase reimbursement levels for conference attendees."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:184
msgid ""
"* *Toronto meetup:* CCC is such a productive time for us, and it seems "
"that a\n"
" second meetup in the year would be quite helpful. We have proposed it "
"for\n"
" August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. "
"It\n"
" would include developer meetings together with presentations and "
"tutorials,\n"
" all open to the public. We are attempting to gauge interest and "
"research\n"
" possible venues. If you are considering attending, please let us know "
"by\n"
" `tweeting @i2p`_ or posting `on the dev forum thread`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:194
msgid ""
"* We discussed Meeh's workload and the state of the various services he "
"is\n"
" running. We made some plans to reduce his load and have some other "
"people help\n"
" out."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:200
msgid ""
"* We reviewed our critieria for placing links to `i2pd`_ on our download "
"page.\n"
" We agreed that the only remaining item is to have a nice page on the\n"
" `Privacy Solutions web site`_ or elsewhere with binary packages for "
"Windows,\n"
" Linux, and Mac, and source packages. It's not clear who is responsible "
"for\n"
" building the packages and where the \"official\" version is. Once "
"there's an\n"
" established process for building and signing packages and an official "
"place to\n"
" put them, we're ready to link to it. If it is not feasible to host it "
"on the\n"
" Privacy Solutions website, we will discuss alternatives with orignal,\n"
" including possible migration to our download servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:212
msgid ""
"* Lots of people coming by the table asked if we had a non-Java version. "
"It was\n"
" great to finally answer \"yes\" and we're eager to get the word out and"
" get more\n"
" users, testers, and developers on it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:218
msgid ""
"* `Vuze`_ continues to make good progress on their I2P integration. We "
"look\n"
" forward to working with them in the new year on a managed rollout to "
"more\n"
" users."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:224
msgid ""
"* We discussed the state of Meeh's and Sindu's reseed servers. They made "
"several\n"
" improvements while at the congress and are investigating migration to\n"
" `Matt Drollette's Go implementation`_. The security and reliability of "
"our\n"
" reseed servers is vital to new users and network operation. `User "
"'backup'`_\n"
" is doing a great job monitoring and managing the pool of reseed servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:232
msgid ""
"* We agreed to purchase a second root server for development, testing, "
"and\n"
" services. Echelon will be adminstering it. Contact him is you would "
"like a VM."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:237
msgid ""
"* We reiterated that we have funds available to purchase test hardware,\n"
" especially for Windows and Mac. Talk to echelon for details."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:242
msgid ""
"* We met with Welterde about the state of his services including his\n"
" `open tracker`_. These services are not being adequately maintained and"
" will\n"
" soon become inaccessible due to crypto changes if they are not "
"upgraded. He\n"
" committed to upgrading them soon."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:249
msgid ""
"* We met lots of people interested in our `Android app`_. We passed "
"several\n"
" ideas and bug reports back to str4d. We plan to make a big push to give"
" the\n"
" app some development love early in the year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:255
msgid ""
"* Regrettably, we didn't get to see too many talks at the Congress, as we"
" were\n"
" so busy meeting with people. We plan to catch up and `watch them "
"online`_. As\n"
" usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's "
"talk was\n"
" great. We hear that the cryptography talks were good as well."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262
msgid "`Toronto Crypto`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263
msgid "`tweeting @i2p`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:264
#, fuzzy
msgid "`on the dev forum thread`"
msgstr "`this development thread`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:267
#, fuzzy
msgid "`Privacy Solutions web site`"
msgstr "`The Privacy Solutions Project`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271
msgid "`Matt Drollette's Go implementation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:272
msgid "`User 'backup'`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:274
#, fuzzy
msgid "`open tracker`"
msgstr "`наш Twitter`"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:276
msgid "`Android app`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:278
msgid "`watch them online`"
msgstr ""

416
i2p2www/translations/sv/LC_MESSAGES/blog.po
View File

@ -10,7 +10,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2014-12-02 23:11+0000\n"
"POT-Creation-Date: 2015-01-21 03:46+0000\n"
"PO-Revision-Date: 2014-12-02 23:13+0000\n"
"Last-Translator: str4d <str4d@i2pmail.org>\n"
"Language-Team: Swedish (Sweden) "
@ -3286,3 +3286,417 @@ msgstr ""
msgid "`click here`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1
msgid ""
"================\n"
"31C3 trip report\n"
"================"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9
msgid ""
"CCC has always been a productive time for us, and 31C3 was no exception. "
"Here is a summary of our various meetings and discussions."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20
msgid ""
"We were, for the second year in a row, at a great location in the "
"Congress, in\n"
"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square "
"has\n"
"really increased our visibility and helped many people find us. Thanks to"
" Noisy\n"
"Square and the 31C3 organizers for a great Congress."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29
msgid ""
"We also thank Gabriel Weinberg and his fabulous search engine "
"`DuckDuckGo`_ for\n"
"their support of open source anonymity tools and their `generous "
"contribution`_\n"
"to I2P in 2014. Funding from DuckDuckGo and others helped support our "
"attendance\n"
"at CCC. This is the primary annual meetup for I2P developers and it is "
"critical\n"
"to our success."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38
msgid "`generous contribution`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40
msgid ""
"Discussions with others\n"
"======================="
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48
msgid ""
"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved "
"himself\n"
"and the project from TU Munich to `Inria`_ in France. He has a large "
"number of\n"
"`open positions`_. This is a great opportunity to get paid to work on "
"open\n"
"source anonymity tools, we encourage everybody to contact him about it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57
msgid "`open positions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59
msgid ""
"The prospect of an invigorated GNUnet with a large amount of new funding "
"is\n"
"quite interesting. We discussed more ways to work together. In early "
"2014, we\n"
"worked hard to understand the GnuNet DNS replacement, but we were unable "
"to\n"
"figure out a good fit for it in I2P. One of his new ideas is a "
"distributed,\n"
"anonymous statistics gathering subsystem, for detecting problems or "
"attacks on\n"
"the network. We'd definitely be interested in that."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68
msgid ""
"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems "
"draft`_.\n"
"A new, greatly simplified version 3 was posted in December. The prospects"
" for\n"
"approval remain unclear. The best way to monitor or participate in the\n"
"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to "
"do so\n"
"on our side, and also give Hellekin a new point-of-contact for this topic."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76
msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77
msgid "`IETF DNSOP WG mailing list`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79
msgid ""
"We apologized to Christian for not being organized enough to have a talk "
"at his\n"
"`We Fix The Net assembly`_. One of our biggest failures is a project is "
"our\n"
"seeming inability to submit talks at conferences. We'll have to do better"
" in the\n"
"new year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86
msgid "`We Fix The Net assembly`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91
msgid ""
"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in "
"with\n"
"other anonymity tools into this new Debian \"superpackage\" of some sort,"
" and\n"
"would love to get I2P into Debian in 2015. He claims the process is now "
"easy,\n"
"just `follow the instructions`_. We said that's funny, we've been\n"
"`stuck in the process for over 7 years`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99
msgid "`follow the instructions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100
msgid "`stuck in the process for over 7 years`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102
msgid ""
"He said, well, try the new process, it works great, should be no problem "
"at all\n"
"if your package is in good shape. The people in Debian that run this "
"process are\n"
"eager volunteers who want nothing more than to get more packages in. We "
"said our\n"
"package is indeed in fantastic shape, and we would try out the new "
"process as\n"
"soon as possible. As best as we can tell, we are orphaned in the old "
"process and\n"
"have to restart in the new process? If all this is true, we will be in "
"the next\n"
"Debian release in late 2015. This would be very very cool."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:115
msgid ""
"We had a nice discussion with BitingBird of Tails. They are very happy "
"with our\n"
"rapid response to the `vulnerability disclosure`_ last summer, resulting "
"in our\n"
"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and "
"they\n"
"took `great offense`_ to that and the lack of private notification. We "
"thanked\n"
"them for taking the heat and fighting back."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123
msgid "`vulnerability disclosure`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124
#, fuzzy
msgid "`0.9.14 release`"
msgstr "0.9.4 Release"
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:125
msgid "`great offense`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:127
msgid ""
"Biting Bird also handles support, and she tells us the number one issue "
"is how\n"
"long I2P takes to start up and be useful for browsing I2P sites. Her "
"standard\n"
"answer is \"wait ten more minutes\" and that seems to be effective. I2P "
"is\n"
"particularly slow to startup on Tails since it does not persist peer data"
" by\n"
"default. It would be nice to change that, but there's also things we can "
"do on\n"
"the I2P side to make things start faster. Expect some improvement in our "
"0.9.18\n"
"release."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:140
msgid ""
"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The "
"upcoming\n"
"Tor Hidden Services changes mean that their keys will no longer fit into "
"a\n"
"portion of an IPv6 address, and he was working on a solution. We reminded"
" him\n"
"that this has always been the case for I2P (with \"GarliCat\"), that it's"
" not a\n"
"new problem. He pointed us to `a presentation`_ of his proposal. It "
"involves\n"
"storing an extra record in the hidden service directory (equivalent of a\n"
"leaseset I2P's network database). It wasn't completely clear how this "
"would\n"
"work, or if we would consider it abuse of the netDb. We'll follow up with"
" him\n"
"as he gets further."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:153
msgid "`a presentation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:155
msgid ""
"New users\n"
"---------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:160
msgid ""
"We spent hours and hours explaining I2P to people stopping by our table. "
"Some\n"
"had heard of I2P before, some had not; everybody had heard of Tor and had"
" at\n"
"least a vague idea of what hidden services are. As usual, introducing "
"people to\n"
"I2P was a struggle. By the end of the Congress, we became convinced that "
"a part\n"
"of the problem was a difference in terminology. Back 12 years ago, when "
"I2P and\n"
"Tor were both getting started, we each came up with terms for the various"
" parts\n"
"of our systems. Today, the Tor terminology such as \"hidden service\" is\n"
"well-understood and commonplace. The I2P terminology such as \"eepsite\" "
"is\n"
"neither. We agreed to review our documentation, router console, and other"
" places\n"
"for opportunities to simplify it and use common terms."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:173
msgid ""
"I2P project topics\n"
"------------------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:178
msgid ""
"* *Spending money:* We discussed several ways to effectively use our "
"resources\n"
" in 2015, including more hardware for testing and development. Also, we "
"plan to\n"
" increase reimbursement levels for conference attendees."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:184
msgid ""
"* *Toronto meetup:* CCC is such a productive time for us, and it seems "
"that a\n"
" second meetup in the year would be quite helpful. We have proposed it "
"for\n"
" August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. "
"It\n"
" would include developer meetings together with presentations and "
"tutorials,\n"
" all open to the public. We are attempting to gauge interest and "
"research\n"
" possible venues. If you are considering attending, please let us know "
"by\n"
" `tweeting @i2p`_ or posting `on the dev forum thread`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:194
msgid ""
"* We discussed Meeh's workload and the state of the various services he "
"is\n"
" running. We made some plans to reduce his load and have some other "
"people help\n"
" out."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:200
msgid ""
"* We reviewed our critieria for placing links to `i2pd`_ on our download "
"page.\n"
" We agreed that the only remaining item is to have a nice page on the\n"
" `Privacy Solutions web site`_ or elsewhere with binary packages for "
"Windows,\n"
" Linux, and Mac, and source packages. It's not clear who is responsible "
"for\n"
" building the packages and where the \"official\" version is. Once "
"there's an\n"
" established process for building and signing packages and an official "
"place to\n"
" put them, we're ready to link to it. If it is not feasible to host it "
"on the\n"
" Privacy Solutions website, we will discuss alternatives with orignal,\n"
" including possible migration to our download servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:212
msgid ""
"* Lots of people coming by the table asked if we had a non-Java version. "
"It was\n"
" great to finally answer \"yes\" and we're eager to get the word out and"
" get more\n"
" users, testers, and developers on it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:218
msgid ""
"* `Vuze`_ continues to make good progress on their I2P integration. We "
"look\n"
" forward to working with them in the new year on a managed rollout to "
"more\n"
" users."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:224
msgid ""
"* We discussed the state of Meeh's and Sindu's reseed servers. They made "
"several\n"
" improvements while at the congress and are investigating migration to\n"
" `Matt Drollette's Go implementation`_. The security and reliability of "
"our\n"
" reseed servers is vital to new users and network operation. `User "
"'backup'`_\n"
" is doing a great job monitoring and managing the pool of reseed servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:232
msgid ""
"* We agreed to purchase a second root server for development, testing, "
"and\n"
" services. Echelon will be adminstering it. Contact him is you would "
"like a VM."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:237
msgid ""
"* We reiterated that we have funds available to purchase test hardware,\n"
" especially for Windows and Mac. Talk to echelon for details."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:242
msgid ""
"* We met with Welterde about the state of his services including his\n"
" `open tracker`_. These services are not being adequately maintained and"
" will\n"
" soon become inaccessible due to crypto changes if they are not "
"upgraded. He\n"
" committed to upgrading them soon."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:249
msgid ""
"* We met lots of people interested in our `Android app`_. We passed "
"several\n"
" ideas and bug reports back to str4d. We plan to make a big push to give"
" the\n"
" app some development love early in the year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:255
msgid ""
"* Regrettably, we didn't get to see too many talks at the Congress, as we"
" were\n"
" so busy meeting with people. We plan to catch up and `watch them "
"online`_. As\n"
" usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's "
"talk was\n"
" great. We hear that the cryptography talks were good as well."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262
msgid "`Toronto Crypto`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263
msgid "`tweeting @i2p`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:264
msgid "`on the dev forum thread`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:267
msgid "`Privacy Solutions web site`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271
msgid "`Matt Drollette's Go implementation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:272
msgid "`User 'backup'`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:274
msgid "`open tracker`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:276
msgid "`Android app`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:278
msgid "`watch them online`"
msgstr ""

415
pots/blog.pot
View File

@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: I2P website\n"
"Report-Msgid-Bugs-To: http://trac.i2p2.de\n"
"POT-Creation-Date: 2014-12-02 23:11+0000\n"
"POT-Creation-Date: 2015-01-21 03:46+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@ -3225,3 +3225,416 @@ msgstr ""
msgid "`click here`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:1
msgid ""
"================\n"
"31C3 trip report\n"
"================"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:9
msgid ""
"CCC has always been a productive time for us, and 31C3 was no exception. "
"Here is a summary of our various meetings and discussions."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:20
msgid ""
"We were, for the second year in a row, at a great location in the "
"Congress, in\n"
"`Noisy Square`_, right next to the EFF table. Being part of Noisy Square "
"has\n"
"really increased our visibility and helped many people find us. Thanks to"
" Noisy\n"
"Square and the 31C3 organizers for a great Congress."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:29
msgid ""
"We also thank Gabriel Weinberg and his fabulous search engine "
"`DuckDuckGo`_ for\n"
"their support of open source anonymity tools and their `generous "
"contribution`_\n"
"to I2P in 2014. Funding from DuckDuckGo and others helped support our "
"attendance\n"
"at CCC. This is the primary annual meetup for I2P developers and it is "
"critical\n"
"to our success."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:38
msgid "`generous contribution`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:40
msgid ""
"Discussions with others\n"
"======================="
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:48
msgid ""
"We spoke at length with Christian Grothoff of `GNUnet`_. He has moved "
"himself\n"
"and the project from TU Munich to `Inria`_ in France. He has a large "
"number of\n"
"`open positions`_. This is a great opportunity to get paid to work on "
"open\n"
"source anonymity tools, we encourage everybody to contact him about it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:57
msgid "`open positions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:59
msgid ""
"The prospect of an invigorated GNUnet with a large amount of new funding "
"is\n"
"quite interesting. We discussed more ways to work together. In early "
"2014, we\n"
"worked hard to understand the GnuNet DNS replacement, but we were unable "
"to\n"
"figure out a good fit for it in I2P. One of his new ideas is a "
"distributed,\n"
"anonymous statistics gathering subsystem, for detecting problems or "
"attacks on\n"
"the network. We'd definitely be interested in that."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:68
msgid ""
"We also discussed the `Special-Use Domain Names of Peer-to-Peer Systems "
"draft`_.\n"
"A new, greatly simplified version 3 was posted in December. The prospects"
" for\n"
"approval remain unclear. The best way to monitor or participate in the\n"
"discussion is via the `IETF DNSOP WG mailing list`_. We will attempt to "
"do so\n"
"on our side, and also give Hellekin a new point-of-contact for this topic."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:76
msgid "`Special-Use Domain Names of Peer-to-Peer Systems draft`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:77
msgid "`IETF DNSOP WG mailing list`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:79
msgid ""
"We apologized to Christian for not being organized enough to have a talk "
"at his\n"
"`We Fix The Net assembly`_. One of our biggest failures is a project is "
"our\n"
"seeming inability to submit talks at conferences. We'll have to do better"
" in the\n"
"new year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:86
msgid "`We Fix The Net assembly`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:91
msgid ""
"Iain Learmonth, a Debian participant, stopped by. He wants to put I2P in "
"with\n"
"other anonymity tools into this new Debian \"superpackage\" of some sort,"
" and\n"
"would love to get I2P into Debian in 2015. He claims the process is now "
"easy,\n"
"just `follow the instructions`_. We said that's funny, we've been\n"
"`stuck in the process for over 7 years`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:99
msgid "`follow the instructions`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:100
msgid "`stuck in the process for over 7 years`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:102
msgid ""
"He said, well, try the new process, it works great, should be no problem "
"at all\n"
"if your package is in good shape. The people in Debian that run this "
"process are\n"
"eager volunteers who want nothing more than to get more packages in. We "
"said our\n"
"package is indeed in fantastic shape, and we would try out the new "
"process as\n"
"soon as possible. As best as we can tell, we are orphaned in the old "
"process and\n"
"have to restart in the new process? If all this is true, we will be in "
"the next\n"
"Debian release in late 2015. This would be very very cool."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:115
msgid ""
"We had a nice discussion with BitingBird of Tails. They are very happy "
"with our\n"
"rapid response to the `vulnerability disclosure`_ last summer, resulting "
"in our\n"
"`0.9.14 release`_. Our vulnerability was initially blamed on Tails, and "
"they\n"
"took `great offense`_ to that and the lack of private notification. We "
"thanked\n"
"them for taking the heat and fighting back."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:123
msgid "`vulnerability disclosure`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:124
msgid "`0.9.14 release`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:125
msgid "`great offense`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:127
msgid ""
"Biting Bird also handles support, and she tells us the number one issue "
"is how\n"
"long I2P takes to start up and be useful for browsing I2P sites. Her "
"standard\n"
"answer is \"wait ten more minutes\" and that seems to be effective. I2P "
"is\n"
"particularly slow to startup on Tails since it does not persist peer data"
" by\n"
"default. It would be nice to change that, but there's also things we can "
"do on\n"
"the I2P side to make things start faster. Expect some improvement in our "
"0.9.18\n"
"release."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:140
msgid ""
"Longtime friend of I2P Bernhard Fischer of `OnionCat`_ stopped by. The "
"upcoming\n"
"Tor Hidden Services changes mean that their keys will no longer fit into "
"a\n"
"portion of an IPv6 address, and he was working on a solution. We reminded"
" him\n"
"that this has always been the case for I2P (with \"GarliCat\"), that it's"
" not a\n"
"new problem. He pointed us to `a presentation`_ of his proposal. It "
"involves\n"
"storing an extra record in the hidden service directory (equivalent of a\n"
"leaseset I2P's network database). It wasn't completely clear how this "
"would\n"
"work, or if we would consider it abuse of the netDb. We'll follow up with"
" him\n"
"as he gets further."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:153
msgid "`a presentation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:155
msgid ""
"New users\n"
"---------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:160
msgid ""
"We spent hours and hours explaining I2P to people stopping by our table. "
"Some\n"
"had heard of I2P before, some had not; everybody had heard of Tor and had"
" at\n"
"least a vague idea of what hidden services are. As usual, introducing "
"people to\n"
"I2P was a struggle. By the end of the Congress, we became convinced that "
"a part\n"
"of the problem was a difference in terminology. Back 12 years ago, when "
"I2P and\n"
"Tor were both getting started, we each came up with terms for the various"
" parts\n"
"of our systems. Today, the Tor terminology such as \"hidden service\" is\n"
"well-understood and commonplace. The I2P terminology such as \"eepsite\" "
"is\n"
"neither. We agreed to review our documentation, router console, and other"
" places\n"
"for opportunities to simplify it and use common terms."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:173
msgid ""
"I2P project topics\n"
"------------------"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:178
msgid ""
"* *Spending money:* We discussed several ways to effectively use our "
"resources\n"
" in 2015, including more hardware for testing and development. Also, we "
"plan to\n"
" increase reimbursement levels for conference attendees."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:184
msgid ""
"* *Toronto meetup:* CCC is such a productive time for us, and it seems "
"that a\n"
" second meetup in the year would be quite helpful. We have proposed it "
"for\n"
" August 2015 in Toronto, Canada, in conjunction with `Toronto Crypto`_. "
"It\n"
" would include developer meetings together with presentations and "
"tutorials,\n"
" all open to the public. We are attempting to gauge interest and "
"research\n"
" possible venues. If you are considering attending, please let us know "
"by\n"
" `tweeting @i2p`_ or posting `on the dev forum thread`_."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:194
msgid ""
"* We discussed Meeh's workload and the state of the various services he "
"is\n"
" running. We made some plans to reduce his load and have some other "
"people help\n"
" out."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:200
msgid ""
"* We reviewed our critieria for placing links to `i2pd`_ on our download "
"page.\n"
" We agreed that the only remaining item is to have a nice page on the\n"
" `Privacy Solutions web site`_ or elsewhere with binary packages for "
"Windows,\n"
" Linux, and Mac, and source packages. It's not clear who is responsible "
"for\n"
" building the packages and where the \"official\" version is. Once "
"there's an\n"
" established process for building and signing packages and an official "
"place to\n"
" put them, we're ready to link to it. If it is not feasible to host it "
"on the\n"
" Privacy Solutions website, we will discuss alternatives with orignal,\n"
" including possible migration to our download servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:212
msgid ""
"* Lots of people coming by the table asked if we had a non-Java version. "
"It was\n"
" great to finally answer \"yes\" and we're eager to get the word out and"
" get more\n"
" users, testers, and developers on it."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:218
msgid ""
"* `Vuze`_ continues to make good progress on their I2P integration. We "
"look\n"
" forward to working with them in the new year on a managed rollout to "
"more\n"
" users."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:224
msgid ""
"* We discussed the state of Meeh's and Sindu's reseed servers. They made "
"several\n"
" improvements while at the congress and are investigating migration to\n"
" `Matt Drollette's Go implementation`_. The security and reliability of "
"our\n"
" reseed servers is vital to new users and network operation. `User "
"'backup'`_\n"
" is doing a great job monitoring and managing the pool of reseed servers."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:232
msgid ""
"* We agreed to purchase a second root server for development, testing, "
"and\n"
" services. Echelon will be adminstering it. Contact him is you would "
"like a VM."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:237
msgid ""
"* We reiterated that we have funds available to purchase test hardware,\n"
" especially for Windows and Mac. Talk to echelon for details."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:242
msgid ""
"* We met with Welterde about the state of his services including his\n"
" `open tracker`_. These services are not being adequately maintained and"
" will\n"
" soon become inaccessible due to crypto changes if they are not "
"upgraded. He\n"
" committed to upgrading them soon."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:249
msgid ""
"* We met lots of people interested in our `Android app`_. We passed "
"several\n"
" ideas and bug reports back to str4d. We plan to make a big push to give"
" the\n"
" app some development love early in the year."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:255
msgid ""
"* Regrettably, we didn't get to see too many talks at the Congress, as we"
" were\n"
" so busy meeting with people. We plan to catch up and `watch them "
"online`_. As\n"
" usual, Tor's \"State of the Onion\" talk was excellent, and Jacob's "
"talk was\n"
" great. We hear that the cryptography talks were good as well."
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:262
msgid "`Toronto Crypto`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:263
msgid "`tweeting @i2p`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:264
msgid "`on the dev forum thread`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:267
msgid "`Privacy Solutions web site`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:271
msgid "`Matt Drollette's Go implementation`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:272
msgid "`User 'backup'`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:274
msgid "`open tracker`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:276
msgid "`Android app`"
msgstr ""
#: i2p2www/blog/2015/01/20/31C3-trip-report.rst:278
msgid "`watch them online`"
msgstr ""