[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[www] branch stable updated (eb0a5c7 -> a89a27b)
|
From: |
gnunet |
|
Subject: |
[www] branch stable updated (eb0a5c7 -> a89a27b) |
|
Date: |
Fri, 19 Mar 2021 09:19:29 +0100 |
This is an automated email from the git hooks/post-receive script.
martin-schanzenbach pushed a change to branch stable
in repository www.
from eb0a5c7 add imported news
add dedb2e9 Translated using Weblate (Spanish)
add 8b57523 Translated using Weblate (Spanish)
add e912081 add another old news post
add 6930bcd start migration of faq
add de258eb more faq migration
add 400269e Translated using Weblate (Spanish)
add 243305c Translated using Weblate (Spanish)
add b8df189 Translated using Weblate (Spanish)
add a1cef89 Translated using Weblate (French)
add fed0917 Translated using Weblate (Italian)
add 1a859f1 Translated using Weblate (Japanese)
add 8cca97d merge
add 12736c4 merge
add 3574c52 remove dup
add 1038cd5 add more langs
add b0e2fc9 more faq!
add 551cf50 merge
add 90586a1 Merge branch 'master' of git+ssh://gnunet.org/www
add 7b5053c update ignore
add 4aa3308 Translated using Weblate (Spanish)
add 03ff161 Merge branch 'master' of git+ssh://gnunet.org/www
add 1af3e1d Translated using Weblate (Spanish)
add ae73124 Translated using Weblate (Spanish)
add 35b98fb Translated using Weblate (Spanish)
add 57cb430 Translated using Weblate (Spanish)
add ded9a80 Translated using Weblate (Spanish)
add a3d205b Translated using Weblate (Spanish)
add 2e80c39 Translated using Weblate (Spanish)
add 77732a6 Translated using Weblate (Spanish)
add 4a8d46c Translated using Weblate (Spanish)
add e909d5d Translated using Weblate (Spanish)
add 4482ca9 Translated using Weblate (Italian)
add da8912a Translated using Weblate (Spanish)
add a9115ac Translated using Weblate (Spanish)
add ea892d3 Translated using Weblate (Spanish)
add 2bdf692 Translated using Weblate (French)
add 15f788d Translated using Weblate (Italian)
add c2b65e6 Translated using Weblate (Arabic)
add 50483df Translated using Weblate (Spanish)
add 96aeb9a Translated using Weblate (Italian)
add a89a27b Translated using Weblate (Arabic)
No new revisions were added by this update.
Summary of changes:
.gitignore | 7 +
Makefile | 7 +-
locale/ar/LC_MESSAGES/messages.po | 2132 ++++++++++++++++++---------
locale/de/LC_MESSAGES/messages.po | 782 +++++++++-
locale/es/LC_MESSAGES/messages.po | 1230 ++++++++++++++--
locale/fr/LC_MESSAGES/messages.po | 862 ++++++++++-
locale/hi/LC_MESSAGES/messages.po | 2094 +++++++++++++++++---------
locale/it/LC_MESSAGES/messages.po | 897 ++++++++++-
locale/ja/LC_MESSAGES/messages.po | 2457 ++++++++++++++++++++-----------
locale/ko/LC_MESSAGES/messages.po | 2092 +++++++++++++++++---------
locale/messages.pot | 791 +++++++++-
locale/pt/LC_MESSAGES/messages.po | 2092 +++++++++++++++++---------
locale/zh_Hant/LC_MESSAGES/messages.po | 2092 +++++++++++++++++---------
news/2013-11-15-special-use-gns.html.j2 | 14 +
template/faq.html.j2 | 1059 ++++++++++++-
www.yml | 13 +
16 files changed, 13898 insertions(+), 4723 deletions(-)
create mode 100644 news/2013-11-15-special-use-gns.html.j2
diff --git a/.gitignore b/.gitignore
index accd124..2f8a6dd 100644
--- a/.gitignore
+++ b/.gitignore
@@ -31,3 +31,10 @@ config.mk
.style.yapf
help/
configure
+locale/ar/LC_MESSAGES/messages.mo
+locale/hi/LC_MESSAGES/messages.mo
+locale/ja/LC_MESSAGES/messages.mo
+locale/ko/LC_MESSAGES/messages.mo
+locale/pt/LC_MESSAGES/messages.mo
+locale/zh_Hant/LC_MESSAGES/messages.mo
+
diff --git a/Makefile b/Makefile
index f54788d..ff223d5 100644
--- a/Makefile
+++ b/Makefile
@@ -3,7 +3,7 @@
include build-system/config.mk
# List of all supported languages, add new languages here!
-LANGUAGES="en de fr it es"
+LANGUAGES="en de fr it es ar hi ja ko pt zh_Hant"
# All: build HTML pages in all languages and compile the
# TypeScript logic in web-common.
@@ -30,8 +30,9 @@ all: locale template
done)
(cd rendered; \
for lang in `echo $(LANGUAGES)`; do \
- $(cp) $$lang/rss.xml $$lang/news/rss.xml; \
- done)
+ mkdir -p $$lang/news/ &> /dev/null \
+ $(cp) $$lang/rss.xml $$lang/news/rss.xml; \
+ done)
(for d in dist ; do \
$(cp) -R $$d rendered/ ; \
done)
diff --git a/locale/ar/LC_MESSAGES/messages.po
b/locale/ar/LC_MESSAGES/messages.po
index 36f2655..9040707 100644
--- a/locale/ar/LC_MESSAGES/messages.po
+++ b/locale/ar/LC_MESSAGES/messages.po
@@ -7,19 +7,23 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2021-03-03 21:41+0100\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
-"Last-Translator: Automatically generated\n"
-"Language-Team: none\n"
+"POT-Creation-Date: 2021-03-12 15:55+0100\n"
+"PO-Revision-Date: 2021-03-16 22:31+0000\n"
+"Last-Translator: Shorouk Hassouna <shoroukhassuna@gmail.com>\n"
+"Language-Team: Arabic <http://weblate.taler.net/projects/gnunet/website/ar/>"
+"\n"
"Language: ar\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=6; plural=n==0 ? 0 : n==1 ? 1 : n==2 ? 2 : n%100>=3 "
+"&& n%100<=10 ? 3 : n%100>=11 ? 4 : 5;\n"
+"X-Generator: Weblate 4.4.2\n"
"Generated-By: Babel 2.9.0\n"
#: common/base.j2:5 common/news.j2:5
msgid "GNUnet"
-msgstr ""
+msgstr "GNUnet"
#: common/base.j2:6 common/news.j2:6
msgid "GNU's framework for secure p2p networking"
@@ -27,7 +31,7 @@ msgstr ""
#: common/footer.j2.inc:7
msgid "Contact"
-msgstr ""
+msgstr "جهات الاتصال"
#: common/footer.j2.inc:8 common/navigation.j2.inc:49
msgid "GNUnet e.V."
@@ -35,11 +39,11 @@ msgstr ""
#: common/footer.j2.inc:9 template/about.html.j2:6
msgid "About GNUnet"
-msgstr ""
+msgstr "عن GNUnet"
#: common/footer.j2.inc:14 common/navigation.j2.inc:64
msgid "Bug Tracker"
-msgstr ""
+msgstr "أداة تعقب الأخطاء"
#: common/footer.j2.inc:19 template/copyright.html.j2:6
msgid "Copyright Assignment"
@@ -48,28 +52,29 @@ msgstr ""
#: common/footer.j2.inc:20 common/navigation.j2.inc:90
#: template/developers.html.j2:24
msgid "Bibliography"
-msgstr ""
+msgstr "المراجع"
#: common/footer.j2.inc:31
msgid "Source code of this site."
-msgstr ""
+msgstr "Source code لهذا الموقع."
#: common/footer.j2.inc:32
msgid "Report issues with this website."
-msgstr ""
+msgstr "الابلاغ عن مشكلة بهذا الموقع."
#: common/navigation.j2.inc:38
msgid "About"
-msgstr ""
+msgstr "عن"
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
msgstr ""
#: common/navigation.j2.inc:40 template/index.html.j2:289
msgid "Applications"
-msgstr ""
+msgstr "التطبيقات"
#: common/navigation.j2.inc:44
msgid "Community"
@@ -93,7 +98,7 @@ msgstr ""
#: common/navigation.j2.inc:58
msgid "Development"
-msgstr ""
+msgstr "تطوير"
#: common/navigation.j2.inc:61
msgid "System Architecture"
@@ -129,7 +134,7 @@ msgstr ""
#: common/navigation.j2.inc:83 template/install-on-openwrt.html.j2:76
msgid "Use"
-msgstr ""
+msgstr "استخدم"
#: common/navigation.j2.inc:84
msgid "Videos"
@@ -153,26 +158,29 @@ msgstr ""
#: common/navigation.j2.inc:89
msgid "FAQ"
-msgstr ""
+msgstr "أسئلة شائعه"
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
-msgstr ""
+msgstr "منشورات جديدة عن التطورات فيما يخص GNUnet كالاصدارات والمناسبات"
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
msgstr ""
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
-msgstr ""
+msgstr "اقرأ المزيد"
#: news/index.html.j2:45
msgid "News archives:"
-msgstr ""
+msgstr "ارشيف الاخبار:"
#: template/about.html.j2:11
msgid "What is GNUnet?"
@@ -180,39 +188,38 @@ msgstr ""
#: template/about.html.j2:13
msgid ""
-"GNUnet is an alternative network stack for building secure, decentralized"
-" and privacy-preserving distributed applications. Our goal is to replace "
-"the old insecure Internet protocol stack. Starting from an application "
-"for secure publication of files, it has grown to include all kinds of "
-"basic protocol components and applications towards the creation of a GNU "
-"internet."
+"GNUnet is an alternative network stack for building secure, decentralized "
+"and privacy-preserving distributed applications. Our goal is to replace the "
+"old insecure Internet protocol stack. Starting from an application for "
+"secure publication of files, it has grown to include all kinds of basic "
+"protocol components and applications towards the creation of a GNU internet."
msgstr ""
#: template/about.html.j2:23
msgid ""
-"Today, the actual use and thus the social requirements for a global "
-"network differs widely from those goals of 1970. While the Internet "
-"remains suitable for military use, where the network equipment is "
-"operated by a command hierarchy and when necessary isolated from the rest"
-" of the world, the situation is less tenable for civil society."
+"Today, the actual use and thus the social requirements for a global network "
+"differs widely from those goals of 1970. While the Internet remains suitable "
+"for military use, where the network equipment is operated by a command "
+"hierarchy and when necessary isolated from the rest of the world, the "
+"situation is less tenable for civil society."
msgstr ""
#: template/about.html.j2:32
msgid ""
"Due to fundamental Internet design choices, Internet traffic can be "
-"misdirected, intercepted, censored and manipulated by hostile routers on "
-"the network. And indeed, the modern Internet has evolved exactly to the "
-"point where, as Matthew Green put it, <a "
-"href=\"https://blog.cryptographyengineering.com/2015/08/16/the-network-";
-"is-hostile/\">\"the network is hostile\"</a>."
+"misdirected, intercepted, censored and manipulated by hostile routers on the "
+"network. And indeed, the modern Internet has evolved exactly to the point "
+"where, as Matthew Green put it, <a href=\"https://blog.";
+"cryptographyengineering.com/2015/08/16/the-network-is-hostile/\">\"the "
+"network is hostile\"</a>."
msgstr ""
#: template/about.html.j2:41
msgid ""
-"We believe liberal societies need a network architecture that uses the "
-"anti-authoritarian decentralized peer-to-peer paradigm and privacy-"
-"preserving cryptographic protocols. The goal of the GNUnet project is to "
-"provide a Free Software realization of this ideal."
+"We believe liberal societies need a network architecture that uses the anti-"
+"authoritarian decentralized peer-to-peer paradigm and privacy-preserving "
+"cryptographic protocols. The goal of the GNUnet project is to provide a Free "
+"Software realization of this ideal."
msgstr ""
#: template/about.html.j2:49
@@ -223,8 +230,8 @@ msgstr ""
#: template/about.html.j2:56
msgid ""
-"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy";
-"/free-sw.html\">Free Software</a>."
+"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy/free-";
+"sw.html\">Free Software</a>."
msgstr ""
#: template/about.html.j2:60
@@ -235,8 +242,8 @@ msgstr ""
#: template/about.html.j2:61
msgid ""
-"GNUnet must be fully distributed and resilient to external attacks and "
-"rogue participants."
+"GNUnet must be fully distributed and resilient to external attacks and rogue "
+"participants."
msgstr ""
#: template/about.html.j2:62
@@ -247,8 +254,8 @@ msgstr ""
#: template/about.html.j2:63
msgid ""
-"GNUnet must inform the user which other participants have to be trusted "
-"when establishing private communications."
+"GNUnet must inform the user which other participants have to be trusted when "
+"establishing private communications."
msgstr ""
#: template/about.html.j2:64
@@ -269,33 +276,28 @@ msgstr ""
#: template/about.html.j2:68
msgid ""
-"GNUnet must provide incentives for peers to contribute more resources "
-"than they consume."
+"GNUnet must provide incentives for peers to contribute more resources than "
+"they consume."
msgstr ""
#: template/about.html.j2:72
msgid ""
-"To get know and learn more, please check our <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, "
-"especially the <a href=\"https://docs.gnunet.org/handbook/gnunet.html";
-"#Key-Concepts\">chapter on \"Key Concepts\"</a>, explaining the "
-"fundamental concepts of GNUnet: <ul> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Authentication\";>Authentication</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Accounting-";
-"to-Encourage-Resource-Sharing\">Accounting to Encourage Resource "
-"Sharing</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Confidentiality\";>Confidentiality</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability\";>Deniability</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Peer-";
-"Identities\">Peer Identities</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-";
-"Name-System-_0028GNS-Zones_0029\">Zones in the GNU Name System (GNS "
-"Zones)</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> "
-"</ul>"
+"To get know and learn more, please check our <a href=\"https://docs.gnunet.";
+"org/handbook/gnunet.html\">handbook</a>, especially the <a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Key-Concepts\">chapter on \"Key Concepts"
+"\"</a>, explaining the fundamental concepts of GNUnet: <ul> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Authentication";
+"\">Authentication</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Accounting-to-Encourage-Resource-Sharing\">Accounting to "
+"Encourage Resource Sharing</a></li> <li><a href=\"https://docs.gnunet.org/";
+"handbook/gnunet.html#Confidentiality\">Confidentiality</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></"
+"li> <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability";
+"\">Deniability</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Peer-Identities\">Peer Identities</a></li> <li><a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-Name-System-_0028GNS-"
+"Zones_0029\">Zones in the GNU Name System (GNS Zones)</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> </ul>"
msgstr ""
#: template/about.html.j2:88
@@ -304,27 +306,27 @@ msgstr ""
#: template/about.html.j2:90
msgid ""
-"There are many more resources to learn about GNUnet besides the <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such "
-"as the <a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers "
-"covering the various layers, many <a "
-"href=\"https://gnunet.org/en/video.html\";>videos</a> or a brief <a "
-"href=\"https://gnunet.org/en/glossary.html\";>glossary</a>."
+"There are many more resources to learn about GNUnet besides the <a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such as the "
+"<a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers covering "
+"the various layers, many <a href=\"https://gnunet.org/en/video.html";
+"\">videos</a> or a brief <a href=\"https://gnunet.org/en/glossary.html";
+"\">glossary</a>."
msgstr ""
#: template/about.html.j2:95
msgid ""
"You are most welcome to <a href=\"engage.html\">get engaged into the "
-"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a "
-"href=\"use.html\">use it</a> and <a href=\"engage.html\">contribute and "
-"get engaged</a> in various ways."
+"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a href=\"use."
+"html\">use it</a> and <a href=\"engage.html\">contribute and get engaged</a> "
+"in various ways."
msgstr ""
#: template/about.html.j2:100
msgid ""
-"Please be aware that this project is (despite of it's age) still in an "
-"early alpha stage when it comes to software – its not an easy task "
-"to rewrite the whole Internet!"
+"Please be aware that this project is (despite of it's age) still in an early "
+"alpha stage when it comes to software – its not an easy task to "
+"rewrite the whole Internet!"
msgstr ""
#: template/about.html.j2:105
@@ -333,24 +335,25 @@ msgstr ""
#: template/about.html.j2:110
msgid ""
-"We're receiving funding from NLnet's Next Generation Internet funding "
-"line to document and implement the GNU Name System protocol in a way "
-"suitable for the IETF standardization process."
+"We're receiving funding from NLnet's Next Generation Internet funding line "
+"to document and implement the GNU Name System protocol in a way suitable for "
+"the IETF standardization process."
msgstr ""
#: template/about.html.j2:123
msgid ""
"This project has received funding from the European Union’s Horizon 2020 "
"research and innovation programme under the NGI_TRUST grant agreement no "
-"825618. The project aims to integrate re:claimID with the GNU Taler "
-"payment system in a pilot in order to demonstrate the practical "
-"feasibility and benefits of privacy enhancing technologies for users and "
-"commercial service providers. The project is called \"Decentralized "
-"Identities for Self-Sovereign End-users\" (DISSENS)."
+"825618. The project aims to integrate re:claimID with the GNU Taler payment "
+"system in a pilot in order to demonstrate the practical feasibility and "
+"benefits of privacy enhancing technologies for users and commercial service "
+"providers. The project is called \"Decentralized Identities for Self-"
+"Sovereign End-users\" (DISSENS)."
msgstr ""
#: template/about.html.j2:141
-msgid "We are grateful for free hosting offered by the following
organizations:"
+msgid ""
+"We are grateful for free hosting offered by the following organizations:"
msgstr ""
#: template/about.html.j2:150
@@ -371,13 +374,13 @@ msgstr ""
#: template/applications.html.j2:15
msgid ""
-"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully "
-"decentralized replacement for the Domain Name System (DNS). Instead of "
-"using a hierarchy, GNS uses a directed graph. Naming conventions are "
-"similar to DNS, but queries and replies are private even with respect to "
-"peers providing the answers. The integrity of records and privacy of "
-"look-ups is cryptographically secured. <!-- Too technical: GNS integrates"
-" a robust, efficient and instant key revocation mechanism. -->"
+"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully decentralized "
+"replacement for the Domain Name System (DNS). Instead of using a hierarchy, "
+"GNS uses a directed graph. Naming conventions are similar to DNS, but "
+"queries and replies are private even with respect to peers providing the "
+"answers. The integrity of records and privacy of look-ups is "
+"cryptographically secured. <!-- Too technical: GNS integrates a robust, "
+"efficient and instant key revocation mechanism. -->"
msgstr ""
#: template/applications.html.j2:38
@@ -386,8 +389,8 @@ msgstr ""
#: template/applications.html.j2:40
msgid ""
-"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized"
-" Identity Provider (IdP) service built in top of the GNU Name System. It "
+"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized "
+"Identity Provider (IdP) service built in top of the GNU Name System. It "
"allows users to securely share personal information with websites using "
"standardized protocols (OpenID Connect)."
msgstr ""
@@ -398,10 +401,9 @@ msgstr ""
#: template/applications.html.j2:59
msgid ""
-"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that "
-"aims to provide censorship-resistant, anonymous filesharing. The "
-"publisher is empowered to make a gradual choice between performance and "
-"anonymity."
+"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that aims "
+"to provide censorship-resistant, anonymous filesharing. The publisher is "
+"empowered to make a gradual choice between performance and anonymity."
msgstr ""
#: template/applications.html.j2:73
@@ -411,8 +413,8 @@ msgstr ""
#: template/applications.html.j2:75
msgid ""
"GNUnet conversation is an application that provides secure voice "
-"communication in a fully decentralized way by employing GNUnet for "
-"routing and transport."
+"communication in a fully decentralized way by employing GNUnet for routing "
+"and transport."
msgstr ""
#: template/applications.html.j2:91
@@ -426,8 +428,8 @@ msgstr ""
#: template/applications.html.j2:99
msgid ""
"<a href=\"https://taler.net/\";>GNU Taler</a> is a new privacy-preserving "
-"electronic payment system. Payments are cryptographically secured and are"
-" confirmed within milliseconds with extremely low transaction costs."
+"electronic payment system. Payments are cryptographically secured and are "
+"confirmed within milliseconds with extremely low transaction costs."
msgstr ""
#: template/applications.html.j2:118
@@ -436,10 +438,10 @@ msgstr ""
#: template/applications.html.j2:120
msgid ""
-"<a href=\"https://secushare.org/\";>secushare</a> is creating a "
-"decentralized social networking application on top of GNUnet. Using "
-"overlay multicast and the extensible PSYC protocol, notifications are "
-"distributed end-to-end encrypted to authorized recipients only."
+"<a href=\"https://secushare.org/\";>secushare</a> is creating a decentralized "
+"social networking application on top of GNUnet. Using overlay multicast and "
+"the extensible PSYC protocol, notifications are distributed end-to-end "
+"encrypted to authorized recipients only."
msgstr ""
#: template/applications.html.j2:139
@@ -448,10 +450,10 @@ msgstr ""
#: template/applications.html.j2:141
msgid ""
-"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) "
-"is creating a usable end-to-end encrypted e-mail solution using "
-"opportunistic key exchange. p≡p will use GNUnet to protect metadata"
-" and exploit new cryptographic protocols to verify keys."
+"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) is "
+"creating a usable end-to-end encrypted e-mail solution using opportunistic "
+"key exchange. p≡p will use GNUnet to protect metadata and exploit new "
+"cryptographic protocols to verify keys."
msgstr ""
#: template/applications.html.j2:160
@@ -460,10 +462,10 @@ msgstr ""
#: template/applications.html.j2:162
msgid ""
-"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> "
-"is a convenient but feature-rich graphical application providing "
-"messaging using especially the CADET subsystem. It is developed using GTK"
-" and libhandy for a convergent design."
+"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> is a "
+"convenient but feature-rich graphical application providing messaging using "
+"especially the CADET subsystem. It is developed using GTK and libhandy for a "
+"convergent design."
msgstr ""
#: template/applications.html.j2:180
@@ -474,8 +476,8 @@ msgstr ""
msgid ""
"<a href=\"https://git.gnunet.org/groupchat.git/\";>groupchat</a> is a "
"terminal user interface providing messaging using especially the CADET "
-"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned"
-" to be compatible."
+"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned to "
+"be compatible."
msgstr ""
#: template/architecture.html.j2:6
@@ -488,11 +490,11 @@ msgstr ""
#: template/architecture.html.j2:22
msgid ""
-"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-"
-"like end-to-end encrypted messaging layer (CADET), a public key "
-"infrastructure (GNS) and a pluggable transport system (TRANSPORT).<br> "
-"Using public keys for addresses and self-organized decentralized routing "
-"algorithms, these subsystems replace the traditional TCP/IP stack."
+"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-like "
+"end-to-end encrypted messaging layer (CADET), a public key infrastructure "
+"(GNS) and a pluggable transport system (TRANSPORT).<br> Using public keys "
+"for addresses and self-organized decentralized routing algorithms, these "
+"subsystems replace the traditional TCP/IP stack."
msgstr ""
#: template/architecture.html.j2:35
@@ -503,9 +505,9 @@ msgstr ""
msgid ""
"GNUnet is implemented using a multi-process architecture. Each subsystem "
"runs as a separate process, providing fault-isolation and enabling tight "
-"permissions to be granted to each subsystem. Naturally, the "
-"implementation is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and"
-" will always remain free software."
+"permissions to be granted to each subsystem. Naturally, the implementation "
+"is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and will always "
+"remain free software."
msgstr ""
#: template/architecture.html.j2:52
@@ -538,11 +540,10 @@ msgstr ""
#: template/contact.html.j2:13
msgid ""
-"An archived, public mailing list for GNUnet is hosted at <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers\">https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>. You can send messages to the list at <a href=\"mailto"
-":gnunet-developers@gnu.org\">gnunet-developers@gnu.org</a>."
+"An archived, public mailing list for GNUnet is hosted at <a href=\"https://";
+"lists.gnu.org/mailman/listinfo/gnunet-developers\">https://lists.gnu.org/";
+"mailman/listinfo/gnunet-developers</a>. You can send messages to the list at "
+"<a href=\"mailto:gnunet-developers@gnu.org\";>gnunet-developers@gnu.org</a>."
msgstr ""
#: template/contact.html.j2:23
@@ -551,10 +552,9 @@ msgstr ""
#: template/contact.html.j2:25
msgid ""
-"<tt>#gnunet</tt> is reachable via <a "
-"href=\"https://freenode.net\";>irc.freenode.net</a>. There is also an <a "
-"href=\"https://view.matrix.org/room/!IjaAfLiruzjxFFzKAV:matrix.org/\";>archive</a>"
-" available."
+"<tt>#gnunet</tt> is reachable via <a href=\"https://freenode.net\";>irc."
+"freenode.net</a>. There is also an <a href=\"https://view.matrix.org/room/!";
+"IjaAfLiruzjxFFzKAV:matrix.org/\">archive</a> available."
msgstr ""
#: template/contact.html.j2:38
@@ -563,11 +563,10 @@ msgstr ""
#: template/contact.html.j2:40
msgid ""
-"GNUnet developers are generally reachable at either "
-"<tt>PSEUDONYM@gnunet.org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us"
-" support receiving GnuPG encrypted Emails. Urgent and sensitive security "
-"issues may be addressed to the GNU maintainers <tt>schanzen</tt> and "
-"<tt>grothoff</tt>."
+"GNUnet developers are generally reachable at either <tt>PSEUDONYM@gnunet."
+"org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us support receiving GnuPG "
+"encrypted Emails. Urgent and sensitive security issues may be addressed to "
+"the GNU maintainers <tt>schanzen</tt> and <tt>grothoff</tt>."
msgstr ""
#: template/contact.html.j2:53
@@ -576,38 +575,37 @@ msgstr ""
#: template/contact.html.j2:55
msgid ""
-"We track open feature requests and bugs for projects within GNUnet in our"
-" <a href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also "
-"report bugs or feature requests to the <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/bug-gnunet\";>bug-gnunet</a>"
-" mailing list. The mailinglist requires no subscription."
+"We track open feature requests and bugs for projects within GNUnet in our <a "
+"href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also report bugs "
+"or feature requests to the <a href=\"https://lists.gnu.org/mailman/listinfo/";
+"bug-gnunet\">bug-gnunet</a> mailing list. The mailinglist requires no "
+"subscription."
msgstr ""
#: template/copyright.html.j2:11
msgid ""
-"<p> Contributors to GNUnet with Git access must sign the <a "
-"href=\"/static/pdf/copyright.pdf\">copyright assignment</a> to ensure "
-"that the <a href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/gnunet_taler_agreement.tex\">GNUnet e.V. --- Taler Systems SA"
-" agreement on licensing and collaborative development</a> of the GNUnet "
-"and GNU Taler projects is satisfied. </p>"
+"<p> Contributors to GNUnet with Git access must sign the <a href=\"/static/"
+"pdf/copyright.pdf\">copyright assignment</a> to ensure that the <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/gnunet_taler_agreement.tex";
+"\">GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative "
+"development</a> of the GNUnet and GNU Taler projects is satisfied. </p>"
msgstr ""
#: template/copyright.html.j2:22
msgid ""
-"<p>The agreements ensure that the code will continue to be made available"
-" under free software licenses, but gives developers the freedom to move "
-"code between GNUnet and GNU Taler without worrying about licenses and to "
-"give the company the ability to dual-license (for example, so that we can"
-" distribute via App-stores that are hostile to free software).</p>"
+"<p>The agreements ensure that the code will continue to be made available "
+"under free software licenses, but gives developers the freedom to move code "
+"between GNUnet and GNU Taler without worrying about licenses and to give the "
+"company the ability to dual-license (for example, so that we can distribute "
+"via App-stores that are hostile to free software).</p>"
msgstr ""
#: template/copyright.html.j2:30
msgid ""
-"<p>Minor contributions (basically, anyone without Git access) do not "
-"require copyright assignment. Pseudonymous contributions are accepted, in"
-" this case simply sign the agreement with your pseudonym. Scanned copies "
-"are sufficient, but snail mail is preferred.</p>"
+"<p>Minor contributions (basically, anyone without Git access) do not require "
+"copyright assignment. Pseudonymous contributions are accepted, in this case "
+"simply sign the agreement with your pseudonym. Scanned copies are "
+"sufficient, but snail mail is preferred.</p>"
msgstr ""
#: template/developers.html.j2:5
@@ -620,14 +618,14 @@ msgstr ""
#: template/developers.html.j2:16
msgid ""
-"A list of our Git repositories can be found on our our <a "
-"href=\"https://git.gnunet.org/\";>Git Server</a>."
+"A list of our Git repositories can be found on our our <a href=\"https://git.";
+"gnunet.org/\">Git Server</a>."
msgstr ""
#: template/developers.html.j2:27
msgid ""
-"Technical papers can be found in our <a "
-"href=\"https://old.gnunet.org/bibliography\";>bibliography</a>."
+"Technical papers can be found in our <a href=\"https://old.gnunet.org/";
+"bibliography\">bibliography</a>."
msgstr ""
#: template/developers.html.j2:34
@@ -636,10 +634,10 @@ msgstr ""
#: template/developers.html.j2:37
msgid ""
-"We have a mailing list for developer discussions. You can subscribe to or"
-" read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo";
-"/gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>."
+"We have a mailing list for developer discussions. You can subscribe to or "
+"read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo/";
+"gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-developers</"
+"a>."
msgstr ""
#: template/developers.html.j2:47
@@ -648,9 +646,9 @@ msgstr ""
#: template/developers.html.j2:50
msgid ""
-"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests "
-"to detect regressions and check for portability at <a "
-"href=\"https://old.gnunet.org/buildbot/gnunet/\";>https://old.gnunet.org/buildbot/gnunet/</a>."
+"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests to "
+"detect regressions and check for portability at <a href=\"https://old.gnunet.";
+"org/buildbot/gnunet/\">https://old.gnunet.org/buildbot/gnunet/</a>."
msgstr ""
#: template/developers.html.j2:59
@@ -659,10 +657,9 @@ msgstr ""
#: template/developers.html.j2:62
msgid ""
-"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> "
-"to analyze the code coverage of our tests, the results are available at "
-"<a "
-"href=\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
+"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> to "
+"analyze the code coverage of our tests, the results are available at <a href="
+"\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
msgstr ""
#: template/developers.html.j2:72
@@ -671,9 +668,9 @@ msgstr ""
#: template/developers.html.j2:75
msgid ""
-"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for "
-"performance regression analysis of the exchange backend at <a "
-"href=\"https://old.gnunet.org/gauger/\";>https://old.gnunet.org/gauger/</a>."
+"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for performance "
+"regression analysis of the exchange backend at <a href=\"https://old.gnunet.";
+"org/gauger/\">https://old.gnunet.org/gauger/</a>."
msgstr ""
#: template/download.html.j2:7 template/gnurl.html.j2:209
@@ -682,8 +679,8 @@ msgstr ""
#: template/download.html.j2:11
msgid ""
-"Here you can download releases of our software and find links to the "
-"various versions."
+"Here you can download releases of our software and find links to the various "
+"versions."
msgstr ""
#: template/download.html.j2:17
@@ -705,7 +702,8 @@ msgid "git"
msgstr ""
#: template/download.html.j2:32
-msgid "You can fetch the git tag of version 0.11.x from our development
server:"
+msgid ""
+"You can fetch the git tag of version 0.11.x from our development server:"
msgstr ""
#: template/engage.html.j2:6
@@ -722,18 +720,17 @@ msgstr ""
#: template/ev.html.j2:13
msgid ""
-"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the"
-" \"Verein zur Förderung von GNUnet e.V.\", an association under "
-"German law to support GNUnet development. The Amtsgericht München "
-"registered the association on the 7th of March under VR 205287."
+"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the "
+"\"Verein zur Förderung von GNUnet e.V.\", an association under German "
+"law to support GNUnet development. The Amtsgericht München registered "
+"the association on the 7th of March under VR 205287."
msgstr ""
#: template/ev.html.j2:22
msgid ""
-"The association is officially dedicated to supporting research, "
-"development and education in the area of secure decentralized networking "
-"in general, and GNUnet specifically. This is the official website for the"
-" association."
+"The association is officially dedicated to supporting research, development "
+"and education in the area of secure decentralized networking in general, and "
+"GNUnet specifically. This is the official website for the association."
msgstr ""
#: template/ev.html.j2:31
@@ -742,15 +739,15 @@ msgstr ""
#: template/ev.html.j2:33
msgid ""
-"GNUnet developers with git (write) access can become members to "
-"participate in the decision process and formally support GNUnet e.V. For "
-"this, all you have to do is update the <tt>members.txt</tt> file in the "
-"<a href=\"https://git.gnunet.org/gnunet-ev.git/\";>gnunet-ev</a> "
-"repository. There are no membership dues; however, members are required "
-"to support GNUnet e.V. and in particularly contribute to the technical "
-"development within their means. For further details, we refer to the <a "
-"href=\"https://git.gnunet.org/gnunet-ev.git/\";>Satzung</a> (currently "
-"only available in German, translations welcome)."
+"GNUnet developers with git (write) access can become members to participate "
+"in the decision process and formally support GNUnet e.V. For this, all you "
+"have to do is update the <tt>members.txt</tt> file in the <a href=\"https://";
+"git.gnunet.org/gnunet-ev.git/\">gnunet-ev</a> repository. There are no "
+"membership dues; however, members are required to support GNUnet e.V. and in "
+"particularly contribute to the technical development within their means. For "
+"further details, we refer to the <a href=\"https://git.gnunet.org/gnunet-ev.";
+"git/\">Satzung</a> (currently only available in German, translations "
+"welcome)."
msgstr ""
#: template/ev.html.j2:52
@@ -759,16 +756,13 @@ msgstr ""
#: template/ev.html.j2:54
msgid ""
-"You can find our \"Satzung\", and the list of members under <a "
-"href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex\">https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex</a>. The current board consists of: "
+"You can find our \"Satzung\", and the list of members under <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex\";>https://git.gnunet.";
+"org/gnunet-ev.git/tree/satzung.tex</a>. The current board consists of: "
"<dl><dt>Vorsitz</dt> <dd><a href=\"https://schanzen.eu\";>Martin "
-"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> "
-"<dd>t3sserakt</dd> <dt>Kassenwart</dt> <dd>Florian Dold</dd> "
-"<dt>Beisitzer</dt> <dd> <a "
-"href=\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 "
-"</dd> </dl>"
+"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> <dd>t3sserakt</dd> "
+"<dt>Kassenwart</dt> <dd>Florian Dold</dd> <dt>Beisitzer</dt> <dd> <a href="
+"\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 </dd> </dl>"
msgstr ""
#: template/ev.html.j2:73
@@ -783,77 +777,801 @@ msgstr ""
msgid ""
"Everybody is welcome to support us via donations. For financial "
"contributions, Europeans are able to donate via SEPA. We hope to setup "
-"accounts in other major currency areas in the future. You can also donate"
-" via Bitcoin, routing details are given below. Please note that we are "
-"unable to provide receipts for your donations. If you are planning to "
-"donate a significant amount of money, please contact us first as it might"
-" be better to come to a custom arrangement. <dl><dt>BitCoin</dt> "
+"accounts in other major currency areas in the future. You can also donate "
+"via Bitcoin, routing details are given below. Please note that we are unable "
+"to provide receipts for your donations. If you are planning to donate a "
+"significant amount of money, please contact us first as it might be better "
+"to come to a custom arrangement. <dl><dt>BitCoin</dt> "
"<dd>1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh</dd> <dt>SEPA/IBAN</dt> "
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
-#: template/faq.html.j2:12
-msgid "Is GNUnet ready for use on production systems?"
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
msgstr ""
-#: template/faq.html.j2:14
-msgid ""
-"A: GNUnet is still undergoing major development. It is largely not yet "
-"ready for usage beyond developers. Your mileage will vary depending on "
-"the functionality you use, but you will always likely run into issues "
-"with our current low-level transport system. We are currently in the "
-"process of rewriting it (Project "Transport Next Generation "
-"[TNG]")"
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
msgstr ""
-#: template/faq.html.j2:24
-msgid "Is GNUnet build using distributed ledger technologies?"
+#: template/faq.html.j2:15 template/faq.html.j2:594
+msgid "Error messages"
+msgstr ""
+
+#: template/faq.html.j2:16 template/faq.html.j2:696
+msgid "File-sharing"
+msgstr ""
+
+#: template/faq.html.j2:17 template/faq.html.j2:872
+msgid "Contributing"
msgstr ""
#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr ""
+
+#: template/faq.html.j2:28
msgid ""
-"A: No. GNUnet is a new network protocol stack for building secure, "
-"distributed, and privacy-preserving applications. While a ledger could be"
-" built using GNUnet, we currently have no plans in doing so."
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
+"the #gnunet IRC on irc.freenode.net."
+msgstr ""
+
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:38
msgid ""
-"I receive many "WARNING Calculated flow delay for X at Y for "
-"Z". Should I worry?"
+"A: The general answer is, when it is ready. A better answer may be: earlier "
+"if you contribute (test, debug, code, document). Every release will be "
+"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://";
+"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
+"the RSS feed of this site to automatically receive a notification."
+msgstr ""
+
+#: template/faq.html.j2:49
+msgid "Is the code free?"
+msgstr ""
+
+#: template/faq.html.j2:51
+msgid ""
+"A: GNUnet is free software, available under the <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
+msgstr ""
+
+#: template/faq.html.j2:58
+msgid "Are there any known bugs?"
msgstr ""
-#: template/faq.html.j2:37
+#: template/faq.html.j2:60
msgid ""
-"A: Right now, this is expected and a known cause for high latency in "
-"GNUnet. We have started a major rewrite to address this and other "
-"problems, but until the Transport Next Generation (TNG) is ready, these "
-"warnings are expected."
+"A: We track the list of currently known bugs in the <a href=\"https://bugs.";
+"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
+"directly to developers or the developer mailing list. This is discouraged "
+"since developers often do not have the time to feed these bugs back into the "
+"Mantis database. Please report bugs directly to the bug tracking system. If "
+"you believe a bug is sensitive, you can set its view status to private (this "
+"should be the exception)."
msgstr ""
-#: template/faq.html.j2:46
+#: template/faq.html.j2:73 template/faq.html.j2:193
msgid "Is there a graphical user interface?"
msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:75
msgid ""
"A: gnunet-gtk is a separate download. The package contains various GTK+ "
"based graphical interfaces, including a graphical tool for configuration."
msgstr ""
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr ""
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called ""
+"proof-of-work" which is used to convince the network that your peer is "
+"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
+"on the network size estimator). The calculation is expected to take a few "
+"days, depending on how fast your CPU is. If the CPU load is creating a "
+"problem for you, you can set the value "WORKDELAY" in the ""
+"nse" section of your configuration file to a higher value. The default "
+"is "5 ms"."
+msgstr ""
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr ""
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
+"connections and, with the Tor Browser Bundle, for the Web in particular. "
+"GNUnet does not really have one focus; our theme is secure decentralized "
+"networking, but that is too broad to be called a focus."
+msgstr ""
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr ""
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost no "
+"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
+"using onion (or garlic) routing as the basis for various (anonymized) "
+"applications. I2P is largely used via a Web frontend."
+msgstr ""
+
+#: template/faq.html.j2:124
+msgid "Is GNUnet ready for use on production systems?"
+msgstr ""
+
+#: template/faq.html.j2:126
+msgid ""
+"A: GNUnet is still undergoing major development. It is largely not yet ready "
+"for usage beyond developers. Your mileage will vary depending on the "
+"functionality you use, but you will always likely run into issues with our "
+"current low-level transport system. We are currently in the process of "
+"rewriting it (Project "Transport Next Generation [TNG]")"
+msgstr ""
+
+#: template/faq.html.j2:136
+msgid "Is GNUnet build using distributed ledger technologies?"
+msgstr ""
+
+#: template/faq.html.j2:138
+msgid ""
+"A: No. GNUnet is a new network protocol stack for building secure, "
+"distributed, and privacy-preserving applications. While a ledger could be "
+"built using GNUnet, we currently have no plans in doing so."
+msgstr ""
+
+#: template/faq.html.j2:151
+msgid "What can I do with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
+"do more than just one thing. Naturally, the implementation and documentation "
+"of some of the features that exist are more advanced than others."
+msgstr ""
+
+#: template/faq.html.j2:160
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
+"decentralized and censorship-resistant replacement for DNS and a mechanism "
+"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
+msgstr ""
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We "
+"recommend that you use Tor for anonymous surfing."
+msgstr ""
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr ""
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+
+#: template/faq.html.j2:195
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the "
+"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
+"that integrates most of the other GUIs in one window. One exception is "
+"gnunet-setup, which must still be run separately at this time (as setup "
+"requires the peer to be stopped)."
+msgstr ""
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr ""
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
+"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
+"FreeBSD and macOS. We have reports of working versions on many other GNU/"
+"Linux distributions; in the past we had reports of working versions on "
+"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
+"so if you cannot get GNUnet to work on those systems please let us know."
+msgstr ""
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr ""
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a default "
+"configuration of top-level domains. The governance of this default "
+"configuration is not yet established. In any case, the user will be able to "
+"modify this configuration at will. We expect normal users to have no need to "
+"edit their own GNS zone(s) unless they host services themselves."
+msgstr ""
+
+#: template/faq.html.j2:241
+msgid "Where is the per-user GNS database kept?"
+msgstr ""
+
+#: template/faq.html.j2:243
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet peer. "
+"Now, a user may run multiple GNUnet peers, in which case the database could "
+"be kept at each peer (however, we don't have code for convenient "
+"replication). Similarly, multiple GNUnet peers can share one instance of the "
+"database --- the "gnunet-service-namestore" can be accessed from "
+"remote (via TCP). The actual data can be stored in a Postgres database, for "
+"which various replication options are again applicable. Ultimately, there "
+"are many options for how users can store (and secure) their GNS database."
+msgstr ""
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases "
+"will only grow to a few tens of thousands of entries, small enough to fit "
+"even on mobile devices."
+msgstr ""
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr ""
+
+#: template/faq.html.j2:272
+msgid ""
+"A: We believe so, as there is no entity that any government could force to "
+"change the mapping for a name except for each individual user (and then the "
+"changes would only apply to the names that this user is the authority for). "
+"So if everyone used GNS, the only practical attack of a government would be "
+"to force the operator of a server to change the GNS records for his server "
+"to point elsewhere. However, if the owner of the private key for a zone is "
+"unavailable for enforcement, the respective zone cannot be changed and any "
+"other zone delegating to this zone will achieve proper resolution."
+msgstr ""
+
+#: template/faq.html.j2:286
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr ""
+
+#: template/faq.html.j2:288
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
+"there are still registrars that determine who owns a name. <br><br> With "
+"GNS, we decentralize the database and also decentralize the responsibility "
+"for naming: each user runs his own personal root zone and is thus in "
+"complete control of the names he uses. GNS also has many additional features "
+"(to keep names short and enable migration) which don't even make sense in "
+"the context of CoDoNS."
+msgstr ""
+
+#: template/faq.html.j2:304
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr ""
+
+#: template/faq.html.j2:306
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared via "
+"delegation, and thus mappings will only change if the user responsible for "
+"the name (the authority) manually changes the record."
+msgstr ""
+
+#: template/faq.html.j2:320
+msgid "What is the difference between GNS and ODDNS?"
+msgstr ""
+
+#: template/faq.html.j2:322
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+
+#: template/faq.html.j2:333
+msgid "What is the difference between GNS and Namecoin?"
+msgstr ""
+
+#: template/faq.html.j2:340
+msgid "What is the difference between GNS and Handshake?"
+msgstr ""
+
+#: template/faq.html.j2:346
+msgid "What is the difference between GNS and ENS?"
+msgstr ""
+
+#: template/faq.html.j2:352
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr ""
+
+#: template/faq.html.j2:354
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks on "
+"DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from "
+"the DNS hierarchy."
+msgstr ""
+
+#: template/faq.html.j2:367
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the style "
+"of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:369
+msgid ""
+"A: For security, it is well known that an initial trust path between the two "
+"parties must exist. However, for applications where this is not required, "
+"weaker mechanisms can be used. For example, we have implemented a first-come-"
+"first-served (FCFS) authority which allows arbitrary users to register "
+"arbitrary names. The key of this authority is included with every GNUnet "
+"installation. Thus, any name registered with FCFS is in fact global and "
+"requires no further introduction. However, the security of these names "
+"depends entirely on the trustworthiness of the FCFS authority. The authority "
+"can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:384
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name in "
+"GNS?"
+msgstr ""
+
+#: template/faq.html.j2:386
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "legitimate" "
+"domain owner. Any user can claim any name (as his preferred name or ""
+"pseudonym") in his NICK record. Similarly, all other users can choose "
+"to ignore this preference and use a name of their choice (or even assign no "
+"name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:397
+msgid ""
+"Did you consider the privacy implications of making your personal GNS zone "
+"visible?"
+msgstr ""
+
+#: template/faq.html.j2:399
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not set. "
+"Thus, users have full control over what information about their zones is "
+"made public."
+msgstr ""
+
+#: template/faq.html.j2:409
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:411
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary because "
+"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
+"of virtual hosting. However, LEHOs are also useful to help with X.509 "
+"certificate validation (as they specify for which legacy hostname the "
+"certificate should be valid). Also, even with IPv6 fully deployed and ""
+"infinite" IP addresses being available, we're not sure that virtual "
+"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
+"become commonplace, GNS should work with today's networks."
+msgstr ""
+
+#: template/faq.html.j2:425
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:427
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. As "
+"trust relationships evolve, mappings would change their meaning as they "
+"cross each others thresholds. We decided that the resulting unpredictability "
+"of the resolution process was not acceptable. Furthermore, trust and "
+"consensus might be easy to manipulate by adversaries."
+msgstr ""
+
+#: template/faq.html.j2:438
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:440
+msgid ""
+"A: The owner of a private key can create a revocation message. This one can "
+"then be flooded throughout the overlay network, creating a copy at all "
+"peers. Before using a public key, peers check if that key has been revoked. "
+"All names that involve delegation via a revoked zone will then fail to "
+"resolve. Peers always automatically check for the existence of a revocation "
+"message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:452
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:454
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:468
+msgid ""
+"How can a GNS zone maintain several name servers, e.g. for load balancing?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share "
+"the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:483
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names are "
+"not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on your "
+"application, HTTPS may not be worth the cost. However, for users that are "
+"experiencing censorship (or are concerned about it), giving up globally "
+"unique names may very well be worth the cost. After all, what is a ""
+"globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:499
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:501
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by IANA/ICANN. "
+"This centralization creates vulnerabilities. For example, the US government "
+"was able to reassign the management of the country-TLDs of Afganistan and "
+"Iraq during the wars at the beginning of the 21st century."
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:514
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
+"so blocking a particular IP address causes much more collateral damage than "
+"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
+"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
+"censorship resistant naming system. Accessing Tor's ".onion" "
+"namespace currently requires users to use unmemorable cryptographic "
+"identifiers. With nicer names, Tor and tor2web-like services would be even "
+"easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:533
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:535
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can use "
+"GNS to perform name resolution as well as any normal user. Naturally, while "
+"we typically expect normal users to install custom software for name "
+"resolution, this is unlikely to work for search engines today. However, the "
+"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
+"they can still index GNS resources. However, as using DNS2GNS gateways "
+"breaks the cryptographic chain of trust, legacy search engines will "
+"obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:549
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:551
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was designed "
+"to interoperate with DNS as much as possible, and to also work as much as "
+"possible with the existing Web infrastructure. UIA is not at all concerned "
+"about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:564
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:566
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you know "
+"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
+"and can thus decide how much you trust the result. Naturally, the trusted-"
+"computing base (TCB) can become arbitrarily large this way --- however, "
+"given the name length restriction, for an individual name it is always less "
+"than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:578
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part of "
+"the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:580
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects the "
+""_Service._Proto" syntax, converts "Service" to the "
+"corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when the "
+"result is presented, GNS looks for the GNS-specific "BOX" record "
+"type. A BOX record is a record that contains another record (such as SRV or "
+"TLSA records) and adds a service and protocol number (and the original boxed "
+"record type) to it."
+msgstr ""
+
+#: template/faq.html.j2:596
+msgid ""
+"I receive many "WARNING Calculated flow delay for X at Y for Z". "
+"Should I worry?"
+msgstr ""
+
+#: template/faq.html.j2:598
+msgid ""
+"A: Right now, this is expected and a known cause for high latency in GNUnet. "
+"We have started a major rewrite to address this and other problems, but "
+"until the Transport Next Generation (TNG) is ready, these warnings are "
+"expected."
+msgstr ""
+
+#: template/faq.html.j2:607
+msgid "Error opening `/dev/net/tun': No such file or directory?"
+msgstr ""
+
+#: template/faq.html.j2:609
+msgid ""
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:621
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
+"dns)?"
+msgstr ""
+
+#: template/faq.html.j2:623
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check if "
+"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:635
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:637
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if "
+"your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:645
+msgid ""
+"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:647
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if you "
+"compiled GNUnet the normal way and/or used a binary package, that is highly "
+"unlikely. The more common cause is that you installed GNUnet to a directory "
+"that your linker does not search. There are several ways to fix this that "
+"are described below. If you are 'root' and you installed to a system folder "
+"(such as /usr/local), you want to add the libraries to the system-wide "
+"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
+"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
+"similar path, you obviously have to change \"/usr/local\" accordingly. If "
+"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
+"$USER/\", then you can explicitly tell your linker to search a particular "
+"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
+"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
+"you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:673
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the \"$\") "
+"to your .bashrc or .profile file. You will have to logout and login again to "
+"have this new profile be applied to all shells (including your desktop "
+"environment)."
+msgstr ""
+
+#: template/faq.html.j2:680
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:682
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
+"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
+"always refer to harmless events that require no action. For example, GNUnet "
+"may use an INFO message to indicate that it is currently performing an "
+"expensive operation that will take some time. GNUnet will also use INFO "
+"messages to display information about important configuration values."
+msgstr ""
+
+#: template/faq.html.j2:698
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:700
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
+"P2P networks, GNUnet was designed with security in mind as the highest "
+"priority. We intend on producing a network with comprehensive security "
+"features. Many other P2P networks are open to a wide variety of attacks, and "
+"users have little privacy. GNUnet is also Free Software and thus the source "
+"code is available, so you do not have to worry about being spied upon by the "
+"software. The following table summarises the main differences between GNUnet "
+"and other systems. The information is accurate to the best of our knowledge. "
+"The comparison is difficult since there are sometimes differences between "
+"various implementations of (almost) the same protocol. In general, we pick a "
+"free implementation as the reference implementation since it is possible to "
+"inspect the free code. Also, all of these systems are changing over time and "
+"thus the data below may not be up-to-date. If you find any flaws, please let "
+"us know. Finally, the table is not saying terribly much (it is hard to "
+"compare these systems this briefly), so if you want the real differences, "
+"read the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:814
+msgid ""
+"Another important point of reference are the various anonymous peer-to-peer "
+"networks. Here, there are differences in terms of application domain and how "
+"specifically anonymity is achieved. Anonymous routing is a hard research "
+"topic, so for a superficial comparisson like this one we focus on the "
+"latency. Another important factor is the programming language. Type-safe "
+"languages may offer certain security benefits; however, this may come at the "
+"cost of significant increases in resource consumption which in turn may "
+"reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:827
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:829
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of the "
+"same techniques used to generate reasonable passwords to defend against such "
+"an attack. In any event, we are not trying to hide content; thus, unless the "
+"user is trying to insert information into the network that can only be "
+"shared with a small group of people, there is no real reason to try to "
+"obfuscate the content by choosing a difficult keyword anyway."
+msgstr ""
+
+#: template/faq.html.j2:843
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:845
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all "
+"users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell which "
+"of the peers in the group originated the message. In other words, it should "
+"be difficult to impossible for an adversary to distinguish between the "
+"originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:857
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:859
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
+"its public key) and has a number of addresses it is reachable by (may have "
+"no addresses, for instance when it's behind a NAT). You specify bandwidth "
+"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
+"(how large your on-disk block storage is) . Your node will then proceed to "
+"connect to other nodes, becoming part of the network."
+msgstr ""
+
+#: template/faq.html.j2:874
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:876
+msgid ""
+"A: First, you need to register an account with our weblate system. Please "
+"send an e-mail with the desired target language to translators@gnunet.org or "
+"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
+"sufficient permissions will then grant you access. Naturally, any abuse will "
+"result in the loss of permissions."
+msgstr ""
+
+#: template/faq.html.j2:888
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:890
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly implement. "
+"The best way to actually get a new feature implemented is to do it yourself "
+"--- and to then send us a patch."
+msgstr ""
+
#: template/glossary.html.j2:12
msgid "Ego"
msgstr ""
#: template/glossary.html.j2:14
msgid ""
-"We use the term \"Ego\" to refer to the fact that users in GNUnet can "
-"have multiple unlinkable identities, in the sense of alter egos. The "
-"ability to have more than one identity is crucial, as we may want to keep"
-" our egos for business separate from those we use for political "
-"activities or romance.<br> Egos in GNUnet are technically equivalent to "
-"identities (and the code does not distinguish between them). We simply "
-"sometimes use the term \"ego\" to stress that you can have more than one."
+"We use the term \"Ego\" to refer to the fact that users in GNUnet can have "
+"multiple unlinkable identities, in the sense of alter egos. The ability to "
+"have more than one identity is crucial, as we may want to keep our egos for "
+"business separate from those we use for political activities or romance.<br> "
+"Egos in GNUnet are technically equivalent to identities (and the code does "
+"not distinguish between them). We simply sometimes use the term \"ego\" to "
+"stress that you can have more than one."
msgstr ""
#: template/glossary.html.j2:27
@@ -862,19 +1580,18 @@ msgstr ""
#: template/glossary.html.j2:29
msgid ""
-"In GNUnet users are identified via a public key, and that public key is "
-"then often referred to as the \"Identity\" of the user. However, the "
-"concept is not as draconian as it often is in real life where many are "
-"forced to have one name, one passport and one unique identification "
-"number. <br> As long as identities in GNUnet are simply public keys, "
-"users are free to create any number of identities, and we call those egos"
-" to emphasize the difference. Even though users can create such egos "
-"freely, it is possible to have an ego certified by some certification "
-"authority, resulting in something that more closely resembles the "
-"traditional concept of an identity.<br> For example, a university may "
-"certify the identities of its students such that they can prove that they"
-" are studying. Students may keep their (certified) student identity "
-"separate from other egos that they use for other activities in life."
+"In GNUnet users are identified via a public key, and that public key is then "
+"often referred to as the \"Identity\" of the user. However, the concept is "
+"not as draconian as it often is in real life where many are forced to have "
+"one name, one passport and one unique identification number. <br> As long as "
+"identities in GNUnet are simply public keys, users are free to create any "
+"number of identities, and we call those egos to emphasize the difference. "
+"Even though users can create such egos freely, it is possible to have an ego "
+"certified by some certification authority, resulting in something that more "
+"closely resembles the traditional concept of an identity.<br> For example, a "
+"university may certify the identities of its students such that they can "
+"prove that they are studying. Students may keep their (certified) student "
+"identity separate from other egos that they use for other activities in life."
msgstr ""
#: template/glossary.html.j2:50
@@ -886,10 +1603,10 @@ msgid ""
"A pseudonym is an ego that is specifically intended to not be linked to "
"one's real name. GNUnet users can create many egos, and thus also many "
"pseudonyms. <br> Repeated uses of the same pseudonym are linkable by "
-"definition, as they involve the same public key. Anonymity requires the "
-"use of either the special \"anonymous\" pseudonym (for GNUnet, this is "
-"the neutral element on the elliptic curve) or a throw-away pseudonym that"
-" is only used once."
+"definition, as they involve the same public key. Anonymity requires the use "
+"of either the special \"anonymous\" pseudonym (for GNUnet, this is the "
+"neutral element on the elliptic curve) or a throw-away pseudonym that is "
+"only used once."
msgstr ""
#: template/glossary.html.j2:71
@@ -898,15 +1615,15 @@ msgstr ""
#: template/glossary.html.j2:73
msgid ""
-"The GNU Name System allows every ego (or identity) to securely and "
-"privately associate any number of label-value pairs with an ego. The "
-"values are called record sets following the terminology of the Domain "
-"Name System (DNS). The mapping of labels to record sets for a given ego "
-"is called a namespace. <br> If records are made public and thus "
-"published, it is possible for other users to lookup the record given the "
-"ego's public key and the label. Here, not only the label can thus act as "
-"a passphrase but also the public key -- which despite its name may not be"
-" public knowledge and is never disclosed by the GNS protocol itself."
+"The GNU Name System allows every ego (or identity) to securely and privately "
+"associate any number of label-value pairs with an ego. The values are called "
+"record sets following the terminology of the Domain Name System (DNS). The "
+"mapping of labels to record sets for a given ego is called a namespace. <br> "
+"If records are made public and thus published, it is possible for other "
+"users to lookup the record given the ego's public key and the label. Here, "
+"not only the label can thus act as a passphrase but also the public key -- "
+"which despite its name may not be public knowledge and is never disclosed by "
+"the GNS protocol itself."
msgstr ""
#: template/glossary.html.j2:89
@@ -915,17 +1632,17 @@ msgstr ""
#: template/glossary.html.j2:91
msgid ""
-"A \"peer\" is an instance of GNUnet with its own per-instance public key "
-"and network addresses. Technically, it is possible to run multiple peers "
-"on the same host, but this only makes sense for testing. <br> By design "
-"GNUnet supports multiple users to share the same peer, just as UNIX is a "
-"multi-user system. A \"peer\" typically consists of a set of foundational"
-" GNUnet services running as the \"gnunet\" user and allowing all users in"
-" the \"gnunet\" group to utilize the API. On multi-user systems, "
-"additional \"personalized\" services may be required per user. <br> While"
-" peers are also identified by public keys, these public keys are "
-"completely unrelated to egos or identities. Namespaces cannot be "
-"associated with a peer, only with egos."
+"A \"peer\" is an instance of GNUnet with its own per-instance public key and "
+"network addresses. Technically, it is possible to run multiple peers on the "
+"same host, but this only makes sense for testing. <br> By design GNUnet "
+"supports multiple users to share the same peer, just as UNIX is a multi-user "
+"system. A \"peer\" typically consists of a set of foundational GNUnet "
+"services running as the \"gnunet\" user and allowing all users in the "
+"\"gnunet\" group to utilize the API. On multi-user systems, additional "
+"\"personalized\" services may be required per user. <br> While peers are "
+"also identified by public keys, these public keys are completely unrelated "
+"to egos or identities. Namespaces cannot be associated with a peer, only "
+"with egos."
msgstr ""
#: template/gns.html.j2:13 template/gnurl.html.j2:60
@@ -935,28 +1652,24 @@ msgstr ""
#: template/gns.html.j2:15
msgid ""
"The Domain Name System today enables traffic amplification attacks, "
-"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive "
-"cyber war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as "
-"DoT, DoH, DNSSEC, DPRIVE and the like will not fix this. This is why we "
-"built the GNU Name System (GNS), a secure, decentralized name system "
-"built on top of GNUnet."
+"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive cyber "
+"war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as DoT, DoH, "
+"DNSSEC, DPRIVE and the like will not fix this. This is why we built the GNU "
+"Name System (GNS), a secure, decentralized name system built on top of "
+"GNUnet."
msgstr ""
#: template/gns.html.j2:28
msgid "Overview"
msgstr ""
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
-
#: template/gns.html.j2:39
msgid ""
"The GNU Name System (GNS) is secure and decentralized naming system. It "
-"allows its users to register names as top-level domains (TLDs) and "
-"resolve other namespaces within their TLDs. <br/> GNS is designed to "
-"provide: <ul> <li>Censorship resistance</li> <li>Query privacy</li> "
-"<li>Secure name resolution</li> <li>Compatibility with DNS</li>"
+"allows its users to register names as top-level domains (TLDs) and resolve "
+"other namespaces within their TLDs. <br/> GNS is designed to provide: <ul> "
+"<li>Censorship resistance</li> <li>Query privacy</li> <li>Secure name "
+"resolution</li> <li>Compatibility with DNS</li>"
msgstr ""
#: template/gns.html.j2:52
@@ -965,23 +1678,23 @@ msgstr ""
#: template/gnurl.html.j2:21
msgid ""
-"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support "
-"only HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend "
-"(GnuTLS) to ensure a small footprint and uniform experience for "
-"developers regardless of how libcurl was compiled."
+"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support only "
+"HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend (GnuTLS) to "
+"ensure a small footprint and uniform experience for developers regardless of "
+"how libcurl was compiled."
msgstr ""
#: template/gnurl.html.j2:30
msgid ""
-"Our main usecase is for GNUnet and Taler, but it might be usable for "
-"others, hence we're releasing the code to the general public."
+"Our main usecase is for GNUnet and Taler, but it might be usable for others, "
+"hence we're releasing the code to the general public."
msgstr ""
#: template/gnurl.html.j2:37
msgid ""
"libgnurl is released under the same license as libcurl. Please read the "
-"README for instructions, as you must supply the correct options to "
-"configure to get a proper build of libgnurl."
+"README for instructions, as you must supply the correct options to configure "
+"to get a proper build of libgnurl."
msgstr ""
#: template/gnurl.html.j2:48
@@ -990,58 +1703,55 @@ msgstr ""
#: template/gnurl.html.j2:50
msgid ""
-"Large parts of the following 6 paragraphs are old and need to be "
-"rewritten."
+"Large parts of the following 6 paragraphs are old and need to be rewritten."
msgstr ""
#: template/gnurl.html.j2:62
msgid ""
-"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, "
-"but other variants are used by some distributions. Supporting other "
-"crypto backends would again expose us to a wider array of security "
-"issues, may create licensing issues and most importantly introduce new "
-"bugs as some crypto backends are known to introduce subtle runtime "
-"issues. While it is possible to have two versions of libcurl installed on"
-" the same system, this is error-prone, especially as if we are linked "
-"against the wrong version, the bugs that arise might be rather subtle."
+"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, but "
+"other variants are used by some distributions. Supporting other crypto "
+"backends would again expose us to a wider array of security issues, may "
+"create licensing issues and most importantly introduce new bugs as some "
+"crypto backends are known to introduce subtle runtime issues. While it is "
+"possible to have two versions of libcurl installed on the same system, this "
+"is error-prone, especially as if we are linked against the wrong version, "
+"the bugs that arise might be rather subtle."
msgstr ""
#: template/gnurl.html.j2:75
msgid ""
-"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, "
-"it would anyway be necessary to recompile cURL for GNUnet. But what "
-"happens if one links cURL against this version of GnuTLS? Well, first one"
-" would install GnuTLS by hand in the system. Then, we build cURL. cURL "
-"will build against it just fine, but the linker will eventually complain "
-"bitterly. The reason is that cURL also links against a bunch of other "
-"system libraries (gssapi, ldap, ssh2, rtmp, krb5, sasl2, see discussion "
-"on obscure protocols above), which --- as they are part of the "
-"distribution --- were linked against an older version of GnuTLS. As a "
-"result, the same binary would be linked against two different versions of"
-" GnuTLS. That is typically a recipe for disaster. Thus, in order to avoid"
-" updating a dozen system libraries (and having two versions of those "
-"installed), it is necessary to disable all of those cURL features that "
-"GNUnet does not use, and there are many of those. For GNUnet, the more "
-"obscure protocols supported by cURL are close to dead code --- mostly "
-"harmless, but not useful. However, as some application may use one of "
-"those features, distributions are typically forced to enable all of those"
-" features, and thus including security issues that might arise from that "
-"code."
+"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, it "
+"would anyway be necessary to recompile cURL for GNUnet. But what happens if "
+"one links cURL against this version of GnuTLS? Well, first one would install "
+"GnuTLS by hand in the system. Then, we build cURL. cURL will build against "
+"it just fine, but the linker will eventually complain bitterly. The reason "
+"is that cURL also links against a bunch of other system libraries (gssapi, "
+"ldap, ssh2, rtmp, krb5, sasl2, see discussion on obscure protocols above), "
+"which --- as they are part of the distribution --- were linked against an "
+"older version of GnuTLS. As a result, the same binary would be linked "
+"against two different versions of GnuTLS. That is typically a recipe for "
+"disaster. Thus, in order to avoid updating a dozen system libraries (and "
+"having two versions of those installed), it is necessary to disable all of "
+"those cURL features that GNUnet does not use, and there are many of those. "
+"For GNUnet, the more obscure protocols supported by cURL are close to dead "
+"code --- mostly harmless, but not useful. However, as some application may "
+"use one of those features, distributions are typically forced to enable all "
+"of those features, and thus including security issues that might arise from "
+"that code."
msgstr ""
#: template/gnurl.html.j2:99
msgid ""
-"So to use a modern version of GnuTLS, a sane approach is to disable all "
-"of the \"optional\" features of cURL that drag in system libraries that "
-"link against the older GnuTLS. That works, except that one should then "
-"NEVER install that version of libcurl in say /usr or /usr/local, as that "
-"may break other parts of the system that might depend on these features "
-"that we just disabled. Libtool versioning doesn't help here, as it is not"
-" intended to deal with libraries that have optional features. Naturally, "
-"installing cURL somewhere else is also problematic, as we now need to be "
-"really careful that the linker will link GNUnet against the right "
-"version. Note that none of this can really be trivially fixed by the cURL"
-" developers."
+"So to use a modern version of GnuTLS, a sane approach is to disable all of "
+"the \"optional\" features of cURL that drag in system libraries that link "
+"against the older GnuTLS. That works, except that one should then NEVER "
+"install that version of libcurl in say /usr or /usr/local, as that may break "
+"other parts of the system that might depend on these features that we just "
+"disabled. Libtool versioning doesn't help here, as it is not intended to "
+"deal with libraries that have optional features. Naturally, installing cURL "
+"somewhere else is also problematic, as we now need to be really careful that "
+"the linker will link GNUnet against the right version. Note that none of "
+"this can really be trivially fixed by the cURL developers."
msgstr ""
#: template/gnurl.html.j2:118
@@ -1052,19 +1762,19 @@ msgstr ""
#, python-format
msgid ""
"How does forking fix it? Easy. First, we can get rid of all of the "
-"compatibility issues --- if you use libgnurl, you state that you "
-"don't need anything but HTTP/HTTPS. Those applications that need "
-"more, should stick with the original cURL. Those that do not, can choose "
-"to move to something simpler. As the library gets a new name, we do not "
-"have to worry about tons of packages breaking as soon as one rebuilds it."
-" So renaming itself and saying that \"libgnurl = libcurl with only "
-"HTTP/HTTPS support and GnuTLS\" fixes 99%% of the problems that darkened "
-"my mood. Note that this pretty much CANNOT be done without a fork, as "
-"renaming is an essential part of the fix. Now, there might be creative "
-"solutions to achieve the same thing within the standard cURL build "
-"system, but this was deemed to be too much work when gnurl was originally"
-" started. The changes libgnurl makes to curl are miniscule and can easily"
-" be applied again and again whenever libcurl makes a new release."
+"compatibility issues --- if you use libgnurl, you state that you don't "
+"need anything but HTTP/HTTPS. Those applications that need more, should "
+"stick with the original cURL. Those that do not, can choose to move to "
+"something simpler. As the library gets a new name, we do not have to worry "
+"about tons of packages breaking as soon as one rebuilds it. So renaming "
+"itself and saying that \"libgnurl = libcurl with only HTTP/HTTPS support and "
+"GnuTLS\" fixes 99%% of the problems that darkened my mood. Note that this "
+"pretty much CANNOT be done without a fork, as renaming is an essential part "
+"of the fix. Now, there might be creative solutions to achieve the same thing "
+"within the standard cURL build system, but this was deemed to be too much "
+"work when gnurl was originally started. The changes libgnurl makes to curl "
+"are miniscule and can easily be applied again and again whenever libcurl "
+"makes a new release."
msgstr ""
#: template/gnurl.html.j2:142
@@ -1073,14 +1783,13 @@ msgstr ""
#: template/gnurl.html.j2:144
msgid ""
-"Projects that use cURL only for HTTP/HTTPS and that would work with "
-"GnuTLS should be able to switch to libgnurl by changing \"-lcurl\" to "
-"\"-lgnurl\". That's it. No changes to the source code should be "
-"required, as libgnurl strives for bug-for-bug compatibility with the "
-"HTTP/HTTPS/GnuTLS subset of cURL. We might add new features relating to "
-"this core subset if they are proposed, but so far we have kept our "
-"changes minimal and no additions to the original curl source have been "
-"written."
+"Projects that use cURL only for HTTP/HTTPS and that would work with GnuTLS "
+"should be able to switch to libgnurl by changing \"-lcurl\" to \"-lgnurl\". "
+"That's it. No changes to the source code should be required, as libgnurl "
+"strives for bug-for-bug compatibility with the HTTP/HTTPS/GnuTLS subset of "
+"cURL. We might add new features relating to this core subset if they are "
+"proposed, but so far we have kept our changes minimal and no additions to "
+"the original curl source have been written."
msgstr ""
#: template/gnurl.html.j2:161
@@ -1089,15 +1798,15 @@ msgstr ""
#: template/gnurl.html.j2:163
msgid ""
-"libgnurl and gnurl are not intended to be used as a replacement for curl "
-"for users: <br> This does not mean there is no confidence in the work "
-"done with gnurl, it means that tools which expect curl or libcurl will "
-"not make use of a different named binary and library. If you know what "
-"you are doing, you should be able to use gnurl as part of your tooling in"
-" place of curl. We do not recommend to do so however, as the only usage "
-"it is tested for <em>so far</em> is as part of Taler's and "
-"GNunet's build-system. <br> Since no conflicts in filenames occur you"
-" are not expected to remove curl to make use of gnurl and viceversa."
+"libgnurl and gnurl are not intended to be used as a replacement for curl for "
+"users: <br> This does not mean there is no confidence in the work done with "
+"gnurl, it means that tools which expect curl or libcurl will not make use of "
+"a different named binary and library. If you know what you are doing, you "
+"should be able to use gnurl as part of your tooling in place of curl. We do "
+"not recommend to do so however, as the only usage it is tested for <em>so "
+"far</em> is as part of Taler's and GNunet's build-system. <br> Since "
+"no conflicts in filenames occur you are not expected to remove curl to make "
+"use of gnurl and viceversa."
msgstr ""
#: template/gnurl.html.j2:188
@@ -1110,16 +1819,15 @@ msgstr ""
#: template/gnurl.html.j2:211
msgid ""
-"Releases are published on <a "
-"href=\"https://ftpmirror.gnu.org/gnu/gnunet/\";>ftpmirror.gnu.org/gnu/gnunet</a>."
-" gnurl is available from within a variety of distributions and package "
-"managers. Some Package Managers which include gnurl are: <a "
-"href=\"https://www.gnu.org/software/guix/\";>GNU Guix</a> (available as "
-"\"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> through the "
-"collaborative ebuild collection <a href=\"https://git.gnunet.org";
-"/youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a "
-"href=\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a "
-"href=\"https://pkgsrc.org\";>pkgsrc</a>."
+"Releases are published on <a href=\"https://ftpmirror.gnu.org/gnu/gnunet/";
+"\">ftpmirror.gnu.org/gnu/gnunet</a>. gnurl is available from within a "
+"variety of distributions and package managers. Some Package Managers which "
+"include gnurl are: <a href=\"https://www.gnu.org/software/guix/\";>GNU Guix</"
+"a> (available as \"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> "
+"through the collaborative ebuild collection <a href=\"https://git.gnunet.org/";
+"youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a href="
+"\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a href=\"https://";
+"pkgsrc.org\">pkgsrc</a>."
msgstr ""
#: template/gnurl.html.j2:228
@@ -1128,17 +1836,17 @@ msgstr ""
#: template/gnurl.html.j2:230
msgid ""
-"We suggest to closely follow release announcements, as they might "
-"indicate changes in how gnurl is to be build. <br> If your package "
-"manager provides a binary build or build instructions to build gnurl from"
-" source automated and integrated with your environment, we strongly "
-"suggest to use this binary build. <br> There are two ways to build gnurl."
-" The first one builds from the most recent git tag, the second one uses "
-"the distributed tarball. Distributors generally are supposed to build "
-"from the tarball, but we describe both methods here. Both methods are "
-"written with a NetBSD 9 userland in mind, substitute tools as necessary. "
-"<br> You should <b>avoid</b> building gnurl from the tip of the default "
-"git branch, as only tags are considered to be stable and approved builds."
+"We suggest to closely follow release announcements, as they might indicate "
+"changes in how gnurl is to be build. <br> If your package manager provides a "
+"binary build or build instructions to build gnurl from source automated and "
+"integrated with your environment, we strongly suggest to use this binary "
+"build. <br> There are two ways to build gnurl. The first one builds from the "
+"most recent git tag, the second one uses the distributed tarball. "
+"Distributors generally are supposed to build from the tarball, but we "
+"describe both methods here. Both methods are written with a NetBSD 9 "
+"userland in mind, substitute tools as necessary. <br> You should <b>avoid</"
+"b> building gnurl from the tip of the default git branch, as only tags are "
+"considered to be stable and approved builds."
msgstr ""
#: template/gnurl.html.j2:251
@@ -1147,8 +1855,8 @@ msgstr ""
#: template/gnurl.html.j2:253
msgid ""
-"If you want to verify the signature, install an OpenPGP compatible tool "
-"such as security/gnupgp2 (and set it up). Assuming you use pkgin:"
+"If you want to verify the signature, install an OpenPGP compatible tool such "
+"as security/gnupgp2 (and set it up). Assuming you use pkgin:"
msgstr ""
#: template/gnurl.html.j2:267
@@ -1161,8 +1869,7 @@ msgstr ""
#: template/gnurl.html.j2:276
msgid ""
-"Fetch the release, the signature, the checksum file as well as its "
-"signature:"
+"Fetch the release, the signature, the checksum file as well as its signature:"
msgstr ""
#: template/gnurl.html.j2:295
@@ -1211,8 +1918,8 @@ msgstr ""
#: template/gnurl.html.j2:371
msgid ""
-"Follow the steps above, but instead of downloading the tarball, clone the"
-" git tag you want to build from."
+"Follow the steps above, but instead of downloading the tarball, clone the "
+"git tag you want to build from."
msgstr ""
#: template/gnurl.html.j2:382
@@ -1221,10 +1928,9 @@ msgstr ""
#: template/gnurl.html.j2:384
msgid ""
-"You can report bugs on our bug tracker: <a "
-"href=\"https://bugs.gnunet.org/\";>bugs.gnunet.org</a>. Alternatively you "
-"can use our bug mailinglist, but we prefer to track bugs on the "
-"bugtracker."
+"You can report bugs on our bug tracker: <a href=\"https://bugs.gnunet.org/";
+"\">bugs.gnunet.org</a>. Alternatively you can use our bug mailinglist, but "
+"we prefer to track bugs on the bugtracker."
msgstr ""
#: template/gnurl.html.j2:395
@@ -1235,10 +1941,9 @@ msgstr ""
msgid ""
"gnurl/libgnurl is looking for a new maintainer. Releases after version "
"7.69.1 and up to version 7.72.0 were signed with the OpenPGP Key "
-"<b>0xD6B570842F7E7F8D</b> (<a "
-"href=\"https://keys.openpgp.org/search?q=6115012DEA3026F62A98A556D6B570842F7E7F8D\";>keys.openpgp.org</a>),"
-" with the key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E"
-" 7F8D</b>."
+"<b>0xD6B570842F7E7F8D</b> (<a href=\"https://keys.openpgp.org/search?";
+"q=6115012DEA3026F62A98A556D6B570842F7E7F8D\">keys.openpgp.org</a>), with the "
+"key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E 7F8D</b>."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:7
@@ -1252,68 +1957,65 @@ msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:18
msgid ""
"In the context of Google Summer of Code 2018, my mentor (Martin "
-"Schanzenbach) and I have worked on creating and extending the REST API of"
-" GNUnet. Currently, we mirrored the functionality of following commands:"
+"Schanzenbach) and I have worked on creating and extending the REST API of "
+"GNUnet. Currently, we mirrored the functionality of following commands:"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:32
msgid ""
-"Additionally, we developed a website with the Javascript framework "
-"Angular 6 and the design framework iotaCSS to use the new REST API. The "
-"REST API of GNUnet is now documented with Sphinx."
+"Additionally, we developed a website with the Javascript framework Angular 6 "
+"and the design framework iotaCSS to use the new REST API. The REST API of "
+"GNUnet is now documented with Sphinx."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:41
msgid ""
-"... when you can use the command line tools? We need to keep in mind, "
-"that everyone has the right to stay secure and private but not everyone "
-"feels comfortable using a terminal. The further developed REST access to "
-"GNUnet APIs in addition to the new web application allows new users to "
-"interact with GNUnet over a well known tool: their browsers. This "
-"addition to the C API and the command line tools may attract new users "
-"and developers."
+"... when you can use the command line tools? We need to keep in mind, that "
+"everyone has the right to stay secure and private but not everyone feels "
+"comfortable using a terminal. The further developed REST access to GNUnet "
+"APIs in addition to the new web application allows new users to interact "
+"with GNUnet over a well known tool: their browsers. This addition to the C "
+"API and the command line tools may attract new users and developers."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:54
msgid ""
"<li> The REST API developed in GNUnet<br> The REST API is already merged "
-"into the gnunet.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet.git/\";>GNUnet Main Git</a>).<br /> "
-"To use the new features, clone the repository and follow the <a "
-"href=\"https://gnunet.org/en/install.html\";>Installation</a> on "
-"gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
-"</li> <li> The Web Application<br> The web application is available under"
-" the gnunet-webui.git repository (<a href=\"https://gnunet.org/git";
-"/gnunet-webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the"
-" newest version of 'node' and 'yarn'. Dependent on your system, you may "
-"need to download newer versions and install them manually and not over "
-"your packet manager. After the installation succeeded, you need to clone "
-"the repository. Then, you need to run \"yarn install\" and \"yarn start\""
-" for testing purposes. To deploy the website (keep in mind, that this "
-"website communicates with another localhost instance) use \"yarn build\" "
-"for building the web application and use the output in the 'dist' "
-"directory. </li> <li> The Documentation<br /> The documentation is "
-"available under the gnunet-rest-api.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet-rest-api.git/\";>GNUnet REST API "
-"Docmentation Git</a>).<br /> Clone the repository and \"make html\". Then"
-" open the 'index.html' under 'build/html/'. </li>"
+"into the gnunet.git repository (<a href=\"https://gnunet.org/git/gnunet.git/";
+"\">GNUnet Main Git</a>).<br /> To use the new features, clone the repository "
+"and follow the <a href=\"https://gnunet.org/en/install.html\";>Installation</"
+"a> on gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
+"</li> <li> The Web Application<br> The web application is available under "
+"the gnunet-webui.git repository (<a href=\"https://gnunet.org/git/gnunet-";
+"webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the newest "
+"version of 'node' and 'yarn'. Dependent on your system, you may need to "
+"download newer versions and install them manually and not over your packet "
+"manager. After the installation succeeded, you need to clone the repository. "
+"Then, you need to run \"yarn install\" and \"yarn start\" for testing "
+"purposes. To deploy the website (keep in mind, that this website "
+"communicates with another localhost instance) use \"yarn build\" for "
+"building the web application and use the output in the 'dist' directory. </"
+"li> <li> The Documentation<br /> The documentation is available under the "
+"gnunet-rest-api.git repository (<a href=\"https://gnunet.org/git/gnunet-rest-";
+"api.git/\">GNUnet REST API Docmentation Git</a>).<br /> Clone the repository "
+"and \"make html\". Then open the 'index.html' under 'build/html/'. </li>"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:91
msgid ""
-"Please, give it a try and contact me, if you find any bugs or "
-"unintentional features. ;)"
+"Please, give it a try and contact me, if you find any bugs or unintentional "
+"features. ;)"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:98
msgid ""
"Right now, the build process of the web application may be a little too "
-"complex for a casual user. We may be able to solve this by using "
-"docker.<br /> Additionally, the web application does not prevent wrong "
-"inputs but responds with error messages. Adding GNUnet Records is "
-"currently only usable for people, who know how a GNS Record looks like. "
-"This can be adapted to each record type.<br /> Last but not least, "
-"additional features, design changes, etc..."
+"complex for a casual user. We may be able to solve this by using docker.<br /"
+"> Additionally, the web application does not prevent wrong inputs but "
+"responds with error messages. Adding GNUnet Records is currently only usable "
+"for people, who know how a GNS Record looks like. This can be adapted to "
+"each record type.<br /> Last but not least, additional features, design "
+"changes, etc..."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:111
@@ -1340,100 +2042,95 @@ msgstr ""
msgid ""
"As a GNU project, GNUnet has participated in the Google Summer of Code "
"(GSoC) for a number of years. This page lists all current, past, and "
-"finished projects. If you want to participate and apply for any of the "
-"ideas for 2020 below or any past project which is not yet finished (or "
-"even your own idea), please contact us either in IRC or mailing list."
+"finished projects. If you want to participate and apply for any of the ideas "
+"for 2020 below or any past project which is not yet finished (or even your "
+"own idea), please contact us either in IRC or mailing list."
msgstr ""
#: template/gsoc.html.j2:34
msgid ""
-"The GNUnet team is currently working on a transport layer rewrite in "
-"order to fix core issues with connectivity. This new component is "
-"currently developed under the name \"TNG\". What is currently known as "
-"\"transport plugins\" will in the TNG be represented as "
-"\"communicators\". Communicators are processes with a well defined API "
-"that allow to connect peers over a specific protocol. The primary "
-"protocol which are already implemented are UNIX sockets, UDP sockets, and"
-" TCP sockets. For a truly resilient network, other connectivity options "
-"such as WiFi mesh, Bluetooth, HTTP(S), QUIC or even more obscure "
-"alternatives such as radio are required. In this project, the goal is to "
-"select, implement and test new communicators. While TNG is not yet ready,"
-" communicators can, by design, be developed and tested against the "
-"current API. We expect that this project can be worked on by multiple "
+"The GNUnet team is currently working on a transport layer rewrite in order "
+"to fix core issues with connectivity. This new component is currently "
+"developed under the name \"TNG\". What is currently known as \"transport "
+"plugins\" will in the TNG be represented as \"communicators\". Communicators "
+"are processes with a well defined API that allow to connect peers over a "
+"specific protocol. The primary protocol which are already implemented are "
+"UNIX sockets, UDP sockets, and TCP sockets. For a truly resilient network, "
+"other connectivity options such as WiFi mesh, Bluetooth, HTTP(S), QUIC or "
+"even more obscure alternatives such as radio are required. In this project, "
+"the goal is to select, implement and test new communicators. While TNG is "
+"not yet ready, communicators can, by design, be developed and tested against "
+"the current API. We expect that this project can be worked on by multiple "
"students as there are a lot of protocols to choose from. The tasks would "
"consist of: <ol> <li>Deciding which communicators to implement.</li> "
-"<li>Test the communicators.</li> <li>Documentation.</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of HTTPS, QUIC, Bluetooth or WiFi.</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Average, but depends on selected protocols. "
-"<br/> <strong>Mentors:</strong> Martin Schanzenbach, t3sserakt"
+"<li>Test the communicators.</li> <li>Documentation.</li> </ol> Advantageous "
+"skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge of HTTPS, QUIC, "
+"Bluetooth or WiFi.</li> </ol> <br/> <strong>Difficulty:</strong> Average, "
+"but depends on selected protocols. <br/> <strong>Mentors:</strong> Martin "
+"Schanzenbach, t3sserakt"
msgstr ""
#: template/gsoc.html.j2:79
msgid ""
-"The REST API currently only supports a single user system. This is an "
-"issue as on multi-user systems, access control must be enfoced on a per-"
-"user basis. In this project, the REST service must be extended to support"
-" user authentication. This includes the correct handling of user context "
-"switches. <ol> <li>Implement user authentication.</li> <li>Test the "
-"access control.</li> <li>Document the changes to the REST API.</li> </ol>"
-" Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of user authentication subsystems on Linux/Unix.</li> <li>REST/HTTP "
-"Authentication methods</li> </ol> <br/> <strong>Difficulty:</strong> "
-"Beginner <br/> <strong>Mentors:</strong> Martin Schanzenbach"
+"The REST API currently only supports a single user system. This is an issue "
+"as on multi-user systems, access control must be enfoced on a per-user "
+"basis. In this project, the REST service must be extended to support user "
+"authentication. This includes the correct handling of user context switches. "
+"<ol> <li>Implement user authentication.</li> <li>Test the access control.</"
+"li> <li>Document the changes to the REST API.</li> </ol> Advantageous skills/"
+"languages/frameworks: <ol> <li>C</li> <li>Knowledge of user authentication "
+"subsystems on Linux/Unix.</li> <li>REST/HTTP Authentication methods</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:111
msgid ""
-"reclaimID is a decentralized identity system build on top of the GNU Name"
-" System. Currently, there is a Webextension which uses the GNUnet <a "
-"href=\"https://rest.gnunet.org\";>REST API</a>. In order to improve "
-"adoption and ease of use, this project aims to include a full GNUnet node"
-" within the Webextention as a fallback. GNUnet can be compiled to Web "
-"Assembly or JavaScript as demonstrated <a "
-"href=\"https://gnunet.io\";>here</a>. The idea is to improve upon this "
-"concept and support more of GNUnet's subsystems. The difficulty of this "
-"project largely depends on the students proficiency with build tools, "
-"emscripten and improvisation skills. There non-exhaustive task list would"
-" be: <ol> <li>Improve existing GNUnet emscripten build to include more "
-"subsystems.</li> <li>Integrate the result into a Webextention.</li> "
+"reclaimID is a decentralized identity system build on top of the GNU Name "
+"System. Currently, there is a Webextension which uses the GNUnet <a href="
+"\"https://rest.gnunet.org\";>REST API</a>. In order to improve adoption and "
+"ease of use, this project aims to include a full GNUnet node within the "
+"Webextention as a fallback. GNUnet can be compiled to Web Assembly or "
+"JavaScript as demonstrated <a href=\"https://gnunet.io\";>here</a>. The idea "
+"is to improve upon this concept and support more of GNUnet's subsystems. The "
+"difficulty of this project largely depends on the students proficiency with "
+"build tools, emscripten and improvisation skills. There non-exhaustive task "
+"list would be: <ol> <li>Improve existing GNUnet emscripten build to include "
+"more subsystems.</li> <li>Integrate the result into a Webextention.</li> "
"<li>Integrate the result into the re:claimID Webextension</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> "
-"<li>emscripten</li> <li>Webextensions</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Challenging <br/> <strong>Mentors:</strong> "
-"Martin Schanzenbach"
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>emscripten</"
+"li> <li>Webextensions</li> </ol> <br/> <strong>Difficulty:</strong> "
+"Challenging <br/> <strong>Mentors:</strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:147
msgid ""
-"Currently, the keys in our statistics database are too verbose. For "
-"example: </p> <p> nse # flood messages received: 13<br/> nse # peers "
-"connected: 4<br/> nse # nodes in the network (estimate): 203<br/> nse # "
-"flood messages started: 5<br/> nse # estimated network diameter: 3<br/> "
-"nse # flood messages transmitted: 10<br/> </p> <p> With such verbose keys"
-" there's no easy way to form compact JSON document or entries for time-"
-"series database. And you can't query single stats without having to "
-"copypaste the line exactly and put in quotes. In short, the goals are "
-"to... <ol> <li>Think of a way how statistics entries can be made "
-"canonical.</li> <li>Implement the change and migrate existing uses.</li> "
-"<li>Document the format(s) and define an appropriate registration "
-"mechanism for identifiers</li> </ol> Relevant bugs: <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> "
-"</ol> <br/> <strong>Difficulty:</strong> Beginner <br/> "
-"<strong>Mentors:</strong> Martin Schanzenbach"
+"Currently, the keys in our statistics database are too verbose. For example: "
+"</p> <p> nse # flood messages received: 13<br/> nse # peers connected: 4<br/"
+"> nse # nodes in the network (estimate): 203<br/> nse # flood messages "
+"started: 5<br/> nse # estimated network diameter: 3<br/> nse # flood "
+"messages transmitted: 10<br/> </p> <p> With such verbose keys there's no "
+"easy way to form compact JSON document or entries for time-series database. "
+"And you can't query single stats without having to copypaste the line "
+"exactly and put in quotes. In short, the goals are to... <ol> <li>Think of a "
+"way how statistics entries can be made canonical.</li> <li>Implement the "
+"change and migrate existing uses.</li> <li>Document the format(s) and define "
+"an appropriate registration mechanism for identifiers</li> </ol> Relevant "
+"bugs: <a href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:187
msgid ""
-"The goal is to either build upon the (outdated) <a "
-"href=\"https://github.com/canndrew/gnunet-rs\";>GNUnet Rust bindings</a> "
-"or to follow the path of <a href=\"GNUnet Go\">https://github.com/bfix";
-"/gnunet-go</a> which tries to reimplement most of the GNUnet stack. The "
-"end result should be an extension template for GNUnet in the form of the "
-"existing <a href=\"https://git.gnunet.org/gnunet-ext.git/\";>C "
-"template</a> which allows to quickly start implementing services and "
-"libraries for GNUnet."
+"The goal is to either build upon the (outdated) <a href=\"https://github.com/";
+"canndrew/gnunet-rs\">GNUnet Rust bindings</a> or to follow the path of <a "
+"href=\"GNUnet Go\">https://github.com/bfix/gnunet-go</a> which tries to "
+"reimplement most of the GNUnet stack. The end result should be an extension "
+"template for GNUnet in the form of the existing <a href=\"https://git.gnunet.";
+"org/gnunet-ext.git/\">C template</a> which allows to quickly start "
+"implementing services and libraries for GNUnet."
msgstr ""
#: template/gsoc.html.j2:198 template/gsoc.html.j2:652
@@ -1458,27 +2155,26 @@ msgstr ""
#: template/gsoc.html.j2:229
msgid ""
-"Includes: Implementation of rudimentary Android compatibility for GNUnet,"
-" in part by porting the GNUnet utils scheduler to act as a thin wrapper "
-"over libuv."
+"Includes: Implementation of rudimentary Android compatibility for GNUnet, in "
+"part by porting the GNUnet utils scheduler to act as a thin wrapper over "
+"libuv."
msgstr ""
#: template/gsoc.html.j2:236
msgid ""
-"<strong>Mentors:</strong> <a href=\"https://www.goebel-";
-"consult.de/\">Hartmut Goebel</a>, Jeff Burdges, Christian Grothoff"
+"<strong>Mentors:</strong> <a href=\"https://www.goebel-consult.de/\";>Hartmut "
+"Goebel</a>, Jeff Burdges, Christian Grothoff"
msgstr ""
#: template/gsoc.html.j2:245
msgid ""
-"There is a push for migrating our CI to Gitlab. The CI should eventually "
-"not just run \"make check\" on various platforms, but also perform tests "
-"with multiple peers running in different VMs with specific network "
-"topologies (i.e. NAT) between them being simulated. The CI should also be"
-" integrated with Gauger for performance regression analysis. Running jobs"
-" only when dependencies have changed and scripting more granular triggers"
-" or ideally automatic dependency discovery (as done by the autotools) is "
-"also important."
+"There is a push for migrating our CI to Gitlab. The CI should eventually not "
+"just run \"make check\" on various platforms, but also perform tests with "
+"multiple peers running in different VMs with specific network topologies (i."
+"e. NAT) between them being simulated. The CI should also be integrated with "
+"Gauger for performance regression analysis. Running jobs only when "
+"dependencies have changed and scripting more granular triggers or ideally "
+"automatic dependency discovery (as done by the autotools) is also important."
msgstr ""
#: template/gsoc.html.j2:257
@@ -1487,19 +2183,18 @@ msgstr ""
#: template/gsoc.html.j2:267
msgid ""
-"One great problem of the current Internet is the lack of "
-"disintermediation. When people want to talk they need a chat service. "
-"When they want to share files they need a file transfer service. Although"
-" GNUnet already possesses quite advanced integration into Linux "
-"networking, a little extra work is needed for existing applications like "
-"irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by"
-" using a GNS hostname like friend.gnu. Once people have added a person to"
-" their GNS they can immediately message, exchange files and suchlike "
-"directly, with nothing but the GNUnet in the middle, using applications "
-"that have been distributed with unix systems ever since the 1980's. We "
-"can produce an OS distribution where these things work out of the box "
-"with the nicknames of people instead of cloud services. For more "
-"information and context, read"
+"One great problem of the current Internet is the lack of disintermediation. "
+"When people want to talk they need a chat service. When they want to share "
+"files they need a file transfer service. Although GNUnet already possesses "
+"quite advanced integration into Linux networking, a little extra work is "
+"needed for existing applications like irc, www, ftp, rsh, nntpd to run over "
+"it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. "
+"Once people have added a person to their GNS they can immediately message, "
+"exchange files and suchlike directly, with nothing but the GNUnet in the "
+"middle, using applications that have been distributed with unix systems ever "
+"since the 1980's. We can produce an OS distribution where these things work "
+"out of the box with the nicknames of people instead of cloud services. For "
+"more information and context, read"
msgstr ""
#: template/gsoc.html.j2:288
@@ -1508,8 +2203,7 @@ msgstr ""
#: template/gsoc.html.j2:296
msgid ""
-"Implement the AnycastExit spec to enable GNUnet clients to connect over "
-"Tor."
+"Implement the AnycastExit spec to enable GNUnet clients to connect over Tor."
msgstr ""
#: template/gsoc.html.j2:302 template/gsoc.html.j2:337
@@ -1520,9 +2214,9 @@ msgstr ""
#: template/gsoc.html.j2:307
msgid ""
"Note: There was a Special TLDs spec to allow Tor to resolve domain names "
-"using GNS over Tor too, but currently that's on hold until folks think "
-"more about how names should be moved around the local system. We're "
-"calling this more collaborative approach NSS2 for now."
+"using GNS over Tor too, but currently that's on hold until folks think more "
+"about how names should be moved around the local system. We're calling this "
+"more collaborative approach NSS2 for now."
msgstr ""
#: template/gsoc.html.j2:316 template/gsoc.html.j2:456
@@ -1532,17 +2226,16 @@ msgstr ""
#: template/gsoc.html.j2:329
msgid ""
-"Improve the Rust implementation of GNUnet utils, possibly including "
-"adding support for asynchronous IO using mio, or perhaps a higher level "
-"asynchronous IO library built upon it, such as rotor, mioco, eventual_io,"
-" or gj."
+"Improve the Rust implementation of GNUnet utils, possibly including adding "
+"support for asynchronous IO using mio, or perhaps a higher level "
+"asynchronous IO library built upon it, such as rotor, mioco, eventual_io, or "
+"gj."
msgstr ""
#: template/gsoc.html.j2:345
msgid ""
-"Implementation of a replacement for PANDA (see Pond) with better "
-"security, and maybe integration with the GNU Name System for key "
-"exchange."
+"Implementation of a replacement for PANDA (see Pond) with better security, "
+"and maybe integration with the GNU Name System for key exchange."
msgstr ""
#: template/gsoc.html.j2:357
@@ -1556,8 +2249,8 @@ msgstr ""
#: template/gsoc.html.j2:370
msgid ""
-"Implement different place types and file sharing by creating a new place "
-"for the shared content."
+"Implement different place types and file sharing by creating a new place for "
+"the shared content."
msgstr ""
#: template/gsoc.html.j2:376
@@ -1566,12 +2259,12 @@ msgstr ""
#: template/gsoc.html.j2:380
msgid ""
-"<ul> <li>File: generic file with comments</li> <li>Image: display an "
-"image with comments referencing a region of the image</li> <li>Sound: "
-"play a sound file with comments referencing a timestamp</li> "
-"<li>Directory/Album: pointers to File / Image / Sound places</li> "
-"<li>Event: with RSVP</li> <li>Survey: ask your social neighborhood "
-"questions in a structured form</li> </ul>"
+"<ul> <li>File: generic file with comments</li> <li>Image: display an image "
+"with comments referencing a region of the image</li> <li>Sound: play a sound "
+"file with comments referencing a timestamp</li> <li>Directory/Album: "
+"pointers to File / Image / Sound places</li> <li>Event: with RSVP</li> "
+"<li>Survey: ask your social neighborhood questions in a structured form</li> "
+"</ul>"
msgstr ""
#: template/gsoc.html.j2:391
@@ -1581,16 +2274,16 @@ msgstr ""
#: template/gsoc.html.j2:395
msgid ""
"<ul> <li>Fork existing channels, reorganize people into new chatrooms or "
-"channels.</li> <li>Share a post (edit and repost something elsewhere, on "
-"a fan page for example).</li> <li>Edit a previously published post + "
-"offer edit history to readers.</li> <li>Control expiry of channel "
-"history.</li> </ul>"
+"channels.</li> <li>Share a post (edit and repost something elsewhere, on a "
+"fan page for example).</li> <li>Edit a previously published post + offer "
+"edit history to readers.</li> <li>Control expiry of channel history.</li> </"
+"ul>"
msgstr ""
#: template/gsoc.html.j2:404
msgid ""
-"See also <a "
-"href=\"http://secushare.org/features\";>http://secushare.org/features</a>"
+"See also <a href=\"http://secushare.org/features\";>http://secushare.org/";
+"features</a>"
msgstr ""
#: template/gsoc.html.j2:409
@@ -1603,20 +2296,19 @@ msgstr ""
#: template/gsoc.html.j2:427
msgid ""
-"Implement aggregation of distributed state from various channels in order"
-" to provide for a powerful social graph API capable of producing social "
-"network profiles, dashboards, a calendar out of upcoming event "
-"invitations (if available), social search functionality and most of all "
-"to make it easy for users to adopt cryptographic identities of their "
-"contacts/friends simply by finding them in the social graph of their "
-"existing contacts (\"This is Linda. You have 11 contacts in common with "
-"her. [ADD]\")."
+"Implement aggregation of distributed state from various channels in order to "
+"provide for a powerful social graph API capable of producing social network "
+"profiles, dashboards, a calendar out of upcoming event invitations (if "
+"available), social search functionality and most of all to make it easy for "
+"users to adopt cryptographic identities of their contacts/friends simply by "
+"finding them in the social graph of their existing contacts (\"This is "
+"Linda. You have 11 contacts in common with her. [ADD]\")."
msgstr ""
#: template/gsoc.html.j2:445
msgid ""
-"Related to <a "
-"href=\"http://secushare.org/rendezvous\";>secushare.org/rendezvous</a>"
+"Related to <a href=\"http://secushare.org/rendezvous\";>secushare.org/"
+"rendezvous</a>"
msgstr ""
#: template/gsoc.html.j2:451 template/gsoc.html.j2:491
@@ -1625,21 +2317,21 @@ msgstr ""
#: template/gsoc.html.j2:468
msgid ""
-"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform "
-"traditional mail clients into secushare user interfaces. </li> <li> Think"
-" of ways to map e-mail addresses to secushare identities. </li> <li> "
-"Encode or translate various e-mail features into secushare equivalents. "
-"</li> <li> Parts of secushare are currently written in Rust, therefore "
-"Rust is preferred for this task but it is not an requirement. </li> </ul>"
+"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform traditional "
+"mail clients into secushare user interfaces. </li> <li> Think of ways to map "
+"e-mail addresses to secushare identities. </li> <li> Encode or translate "
+"various e-mail features into secushare equivalents. </li> <li> Parts of "
+"secushare are currently written in Rust, therefore Rust is preferred for "
+"this task but it is not an requirement. </li> </ul>"
msgstr ""
#: template/gsoc.html.j2:509
msgid ""
"Implementation of the GNUnet auction system described in Chapter 3 of <a "
"href=\"https://grothoff.org/christian/teich2017ms.pdf\";>this thesis</a>. "
-"Specific tasks are adding smart contract creation and round time "
-"enforcement to libbrandt as well as creating the GNUnet auction service, "
-"library and the three user interface programs create, info and join."
+"Specific tasks are adding smart contract creation and round time enforcement "
+"to libbrandt as well as creating the GNUnet auction service, library and the "
+"three user interface programs create, info and join."
msgstr ""
#: template/gsoc.html.j2:521
@@ -1648,9 +2340,9 @@ msgstr ""
#: template/gsoc.html.j2:539
msgid ""
-"Implementation of additional transports to make GNUnet communication more"
-" robust in the presence of problematic networks: GNUnet-over-SMTP, "
-"GNUnet-over-DNS"
+"Implementation of additional transports to make GNUnet communication more "
+"robust in the presence of problematic networks: GNUnet-over-SMTP, GNUnet-"
+"over-DNS"
msgstr ""
#: template/gsoc.html.j2:546 template/gsoc.html.j2:560
@@ -1664,16 +2356,16 @@ msgid ""
msgstr ""
#: template/gsoc.html.j2:568
-msgid "<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff
Burdges"
+msgid ""
+"<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff Burdges"
msgstr ""
#: template/gsoc.html.j2:576
msgid ""
-"Improving libaboss to make computation on shared secrets (including "
-"repeated multiplication) based on <a "
-"href=\"https://dl.acm.org/citation.cfm?doid=62212.62213\";>Ben-Or et "
-"al.</a> if possible. This in particular means moving libaboss to bignums "
-"(gcry_mpi)."
+"Improving libaboss to make computation on shared secrets (including repeated "
+"multiplication) based on <a href=\"https://dl.acm.org/citation.cfm?";
+"doid=62212.62213\">Ben-Or et al.</a> if possible. This in particular means "
+"moving libaboss to bignums (gcry_mpi)."
msgstr ""
#: template/gsoc.html.j2:589
@@ -1685,11 +2377,10 @@ msgstr ""
#: template/gsoc.html.j2:602
msgid ""
"Python 2.7 is reaching its end-of-life, and we want to get rid of the "
-"dependency on Python. The existing gnunet-qr tool is a rather simple "
-"wrapper around python-zbar, which itself wraps libzbar. The goal of this "
-"project is to directly use libzbar to scan QR codes for GNUnet / the GNU "
-"Name System (see also <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
+"dependency on Python. The existing gnunet-qr tool is a rather simple wrapper "
+"around python-zbar, which itself wraps libzbar. The goal of this project is "
+"to directly use libzbar to scan QR codes for GNUnet / the GNU Name System "
+"(see also <a href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
msgstr ""
#: template/gsoc.html.j2:612
@@ -1714,11 +2405,11 @@ msgstr ""
#: template/gsoc.html.j2:642
msgid ""
-"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a "
-"yet to be determined framework such as Angular2. This includes the design"
-" and implementation of not yet existing <a "
-"href=\"http://jsonapi.org/\";>REST APIs</a> that expose the <a "
-"href=\"https://docs.gnunet.org/doxygen/modules.html\";>GNUnet API</a>."
+"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a yet "
+"to be determined framework such as Angular2. This includes the design and "
+"implementation of not yet existing <a href=\"http://jsonapi.org/\";>REST "
+"APIs</a> that expose the <a href=\"https://docs.gnunet.org/doxygen/modules.";
+"html\">GNUnet API</a>."
msgstr ""
#: template/gsoc.html.j2:657
@@ -1727,8 +2418,7 @@ msgstr ""
#: template/gsoc.html.j2:667
msgid ""
-"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet "
-"WebUI</a>"
+"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet WebUI</a>"
msgstr ""
#: template/index.html.j2:8
@@ -1750,25 +2440,24 @@ msgstr ""
#: template/index.html.j2:49
msgid ""
"The conventional Internet is currently like a system of roads with deep "
-"potholes and highwaymen all over the place. Even if you still can use the"
-" roads (e.g. send emails, or browse websites) your vehicle might get "
+"potholes and highwaymen all over the place. Even if you still can use the "
+"roads (e.g. send emails, or browse websites) your vehicle might get "
"hijacked, damaged, or long arms might reach into its back and steal your "
-"items (data) to use it against you and sell it to others - while you "
-"can't even notice the thievery nor accuse and hold the scroungers "
-"accountable. <!-- Proposal from Fabian Gerlach: The conventional Internet"
-" is currently like a system of roads with deep potholes and surveillance "
-"cameras all over the place. Even if you still can use the roads (e.g. "
-"send emails, or browse websites) your vehicle might gets damaged. And the"
-" surveillance cameras will create a movement profile about your life: "
-"They recognize your car license plate, track you everywhere you drive, "
-"and save this information in a central data base. --> The Internet was "
-"not designed with security in mind: protecting against address forgery, "
-"routers learning metadata, or choosing trustworthy third parties is "
-"nontrivial and sometimes impossible. <!-- Proposal from Fabian Gerlach: "
-"The Internet is not designed with security in mind: The network generally"
-" learns too much about users; it has insecure defaults and high "
-"complexity; and it is centralized. That makes it very vulnerable for "
-"multiple attacks massively threatening our freedom. -->"
+"items (data) to use it against you and sell it to others - while you can'"
+"t even notice the thievery nor accuse and hold the scroungers accountable. "
+"<!-- Proposal from Fabian Gerlach: The conventional Internet is currently "
+"like a system of roads with deep potholes and surveillance cameras all over "
+"the place. Even if you still can use the roads (e.g. send emails, or browse "
+"websites) your vehicle might gets damaged. And the surveillance cameras will "
+"create a movement profile about your life: They recognize your car license "
+"plate, track you everywhere you drive, and save this information in a "
+"central data base. --> The Internet was not designed with security in mind: "
+"protecting against address forgery, routers learning metadata, or choosing "
+"trustworthy third parties is nontrivial and sometimes impossible. <!-- "
+"Proposal from Fabian Gerlach: The Internet is not designed with security in "
+"mind: The network generally learns too much about users; it has insecure "
+"defaults and high complexity; and it is centralized. That makes it very "
+"vulnerable for multiple attacks massively threatening our freedom. -->"
msgstr ""
#: template/index.html.j2:94
@@ -1778,10 +2467,10 @@ msgstr ""
#: template/index.html.j2:96
msgid ""
"GNUnet is a network protocol stack for building secure, distributed, and "
-"privacy-preserving applications.<br/> With strong roots in <a "
-"class=\"link\" href=\"https://bib.gnunet.org\";>academic research</a>, our"
-" goal is to replace the <a class=\"link\" href=\"https://secushare.org";
-"/broken-internet\">old insecure Internet</a> protocol stack."
+"privacy-preserving applications.<br/> With strong roots in <a class=\"link\" "
+"href=\"https://bib.gnunet.org\";>academic research</a>, our goal is to "
+"replace the <a class=\"link\" href=\"https://secushare.org/broken-internet";
+"\">old insecure Internet</a> protocol stack."
msgstr ""
#: template/index.html.j2:119
@@ -1792,10 +2481,9 @@ msgstr ""
msgid ""
"Your metadata is just as revealing as the actual content; and it gets "
"exposed on the Internet.<br> Even though transport encryption is "
-"increasingly being deployed on the Internet, it still reveals data that "
-"can threaten democracy: the identities of senders and receivers, the "
-"times, frequency and the volume of communication are all still "
-"revealed.<br>"
+"increasingly being deployed on the Internet, it still reveals data that can "
+"threaten democracy: the identities of senders and receivers, the times, "
+"frequency and the volume of communication are all still revealed.<br>"
msgstr ""
#: template/index.html.j2:150
@@ -1804,15 +2492,13 @@ msgstr ""
#: template/index.html.j2:152
msgid ""
-"It provides <a class=\"link\" "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";> improving "
-"addressing, routing, naming and content distribution</a> in a technically"
-" robust manner - as opposed to ad-hoc designs in place today. <!-- "
-"Proposal from fabian gerlach: GNUnet is built <a "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by "
-"design\"</a> and \"distributed by design\". This improves addressing, "
-"routing, naming and content distribution in a technically robust manner. "
-"-->"
+"It provides <a class=\"link\" href=\"https://www.w3.org/2014/strint/";
+"papers/65.pdf\"> improving addressing, routing, naming and content "
+"distribution</a> in a technically robust manner - as opposed to ad-hoc "
+"designs in place today. <!-- Proposal from fabian gerlach: GNUnet is built "
+"<a href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by design"
+"\"</a> and \"distributed by design\". This improves addressing, routing, "
+"naming and content distribution in a technically robust manner. -->"
msgstr ""
#: template/index.html.j2:177
@@ -1822,9 +2508,9 @@ msgstr ""
#: template/index.html.j2:179
msgid ""
"Today, monitoring increasingly centralized infrastructure, proprietary "
-"implementations, traffic shapers and firewalls restrict all of the <a "
-"class=\"link\" href=\"https://www.gnu.org/philosophy/free-";
-"sw.html\">essential freedoms</a> to various degrees."
+"implementations, traffic shapers and firewalls restrict all of the <a class="
+"\"link\" href=\"https://www.gnu.org/philosophy/free-sw.html\";>essential "
+"freedoms</a> to various degrees."
msgstr ""
#: template/index.html.j2:203
@@ -1833,14 +2519,14 @@ msgstr ""
#: template/index.html.j2:205
msgid ""
-"GNUnet is a self-organizing network and it is <a class=\"link\" "
-"href=\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as"
-" in freedom. GNUnet puts you in control of your data. You determine which"
-" data to share with whom, and you're not pressured to accept "
-"compromises. It gives users freedoms to securely access information "
-"(\"run\" the network), to study all aspects of the network's "
-"operation (\"access the code\"), to distribute information (\"copy\"), as"
-" well as the freedom to deploy new applications (\"modify\")."
+"GNUnet is a self-organizing network and it is <a class=\"link\" href="
+"\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as in "
+"freedom. GNUnet puts you in control of your data. You determine which data "
+"to share with whom, and you're not pressured to accept compromises. It "
+"gives users freedoms to securely access information (\"run\" the network), "
+"to study all aspects of the network's operation (\"access the code\"), "
+"to distribute information (\"copy\"), as well as the freedom to deploy new "
+"applications (\"modify\")."
msgstr ""
#: template/index.html.j2:229
@@ -1849,13 +2535,13 @@ msgstr ""
#: template/index.html.j2:232
msgid ""
-"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every "
-"other distributed or P2P project develops its own library stack, covering"
-" transports, stream muxing, discovery and others. This divides effort and"
-" multiplies bug count. --> Instead of sharing common components and tools"
-" for building P2P systems, every P2P project seems to re-invent the "
-"wheel. <!-- TODO: rework this sentence. --> This heightens the effort and"
-" increases the potential number of vulnerabilities."
+"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every other "
+"distributed or P2P project develops its own library stack, covering "
+"transports, stream muxing, discovery and others. This divides effort and "
+"multiplies bug count. --> Instead of sharing common components and tools for "
+"building P2P systems, every P2P project seems to re-invent the wheel. <!-- "
+"TODO: rework this sentence. --> This heightens the effort and increases the "
+"potential number of vulnerabilities."
msgstr ""
#: template/index.html.j2:264
@@ -1864,10 +2550,10 @@ msgstr ""
#: template/index.html.j2:266
msgid ""
-"It offers a metadata-preserving foundation for your application. It "
-"offers components for addressing, reliable encrypted channels with "
-"advanced routing and resource discovery and naming. Our work is based on "
-"continuous research spanning almost two decades."
+"It offers a metadata-preserving foundation for your application. It offers "
+"components for addressing, reliable encrypted channels with advanced routing "
+"and resource discovery and naming. Our work is based on continuous research "
+"spanning almost two decades."
msgstr ""
#: template/index.html.j2:286
@@ -2009,75 +2695,69 @@ msgstr ""
#: template/install.html.j2:12
msgid ""
-"Notice: GNUnet is still undergoing major development. It is largely "
-"<i>not yet ready</i> for usage beyond developers."
+"Notice: GNUnet is still undergoing major development. It is largely <i>not "
+"yet ready</i> for usage beyond developers."
msgstr ""
#: template/install.html.j2:18
msgid ""
-"<p>Please be aware that this project is still in an early alpha stage "
-"when it comes to running software – its not an easy task to rewrite"
-" the whole Internet! We are happy to get your <a "
-"href=\"engage.html\">helping hand</a> anytime! Further information is "
-"available in our <a href=\"https://docs.gnunet.org/#toc-Using-";
-"GNUnet-1\">handbook</a>. If you have any queries about the installation "
-"or the usage, please <a href=\"engage.html\">get in touch!</a></p>"
+"<p>Please be aware that this project is still in an early alpha stage when "
+"it comes to running software – its not an easy task to rewrite the "
+"whole Internet! We are happy to get your <a href=\"engage.html\">helping "
+"hand</a> anytime! Further information is available in our <a href=\"https://";
+"docs.gnunet.org/#toc-Using-GNUnet-1\">handbook</a>. If you have any queries "
+"about the installation or the usage, please <a href=\"engage.html\">get in "
+"touch!</a></p>"
msgstr ""
#: template/install.html.j2:30
msgid ""
"We recommend to use binary packages provided by the package manager "
-"integrated within your Operating System. GNUnet is reportedly available "
-"for at least: <ul> <li><a "
-"href=\"https://pkgs.alpinelinux.org/package/edge/testing/x86_64/gnunet\";>Alpine</a></li>"
-" <li><a "
-"href=\"https://www.archlinux.org/packages/community/x86_64/gnunet/\";>Arch</a></li>"
-" <li><a "
-"href=\"https://packages.debian.org/search?keywords=gnunet\";>Debian</a></li>"
-" <li><a "
-"href=\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora "
-"(Copr)</a></li> <li><a "
-"href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
-"href=\"https://github.com/Homebrew/homebrew-";
-"core/blob/master/Formula/gnunet.rb\">Homebrew</a></li> <li><a "
-"href=\"https://nixos.org/nixos/packages.html?attr=gnunet&channel=nixpkgs-";
-"unstable&query=gnunet\">NixOS</a></li> <li><a href=\"install-on-"
-"openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is available for your "
-"Operating System and it is missing, send us feedback so that we can add "
-"it to this list. Furthermore, if you are interested in packaging GNUnet "
-"for your Operating System, get in touch with us at gnunet-"
-"developers@gnu.org if you require help with this job. If you were using "
-"an Operating System with the Alpine package manager, GNUnet could be "
-"installed as simple as:"
+"integrated within your Operating System. GNUnet is reportedly available for "
+"at least: <ul> <li><a href=\"https://pkgs.alpinelinux.org/package/edge/";
+"testing/x86_64/gnunet\">Alpine</a></li> <li><a href=\"https://www.archlinux.";
+"org/packages/community/x86_64/gnunet/\">Arch</a></li> <li><a href=\"https://";
+"packages.debian.org/search?keywords=gnunet\">Debian</a></li> <li><a href="
+"\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora (Copr)</a></"
+"li> <li><a href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
+"href=\"https://github.com/Homebrew/homebrew-core/blob/master/Formula/gnunet.";
+"rb\">Homebrew</a></li> <li><a href=\"https://nixos.org/nixos/packages.html?";
+"attr=gnunet&channel=nixpkgs-unstable&query=gnunet\">NixOS</a></li> <li><a "
+"href=\"install-on-openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is "
+"available for your Operating System and it is missing, send us feedback so "
+"that we can add it to this list. Furthermore, if you are interested in "
+"packaging GNUnet for your Operating System, get in touch with us at gnunet-"
+"developers@gnu.org if you require help with this job. If you were using an "
+"Operating System with the Alpine package manager, GNUnet could be installed "
+"as simple as:"
msgstr ""
#: template/install.html.j2:61
msgid ""
-"Next we describe a generic way to install from source. If you are using "
-"one of the following Operating Systems these step-by-step guides might be"
-" useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href"
-"=\"install-on-debian9.html\">Debian 9</a>, <a href=\"install-on-"
-"macos.html\">Mac OS</a>, <a href=\"install-on-netbsd.html\">NetBSD</a>, "
-"<a href=\"install-on-ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not"
-" all of them might be totally up-to-date! Please <a "
-"href=\"engage.html\">ask us</a> if you get stuck."
+"Next we describe a generic way to install from source. If you are using one "
+"of the following Operating Systems these step-by-step guides might be "
+"useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href=\"install-on-"
+"debian9.html\">Debian 9</a>, <a href=\"install-on-macos.html\">Mac OS</a>, "
+"<a href=\"install-on-netbsd.html\">NetBSD</a>, <a href=\"install-on-"
+"ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not all of them might be "
+"totally up-to-date! Please <a href=\"engage.html\">ask us</a> if you get "
+"stuck."
msgstr ""
#: template/install.html.j2:75
msgid ""
-"First, install the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>required "
-"dependencies</a> of GNUnet. There are base requirements and optional "
-"requirements."
+"First, install the <a href=\"https://git.gnunet.org/gnunet.git/tree/README";
+"\">required dependencies</a> of GNUnet. There are base requirements and "
+"optional requirements."
msgstr ""
#: template/install.html.j2:81
msgid ""
"Now, you need to decide if you want to install GNUnet from the release "
"tarball or from git. If you want to use GNUnet and there is no binary "
-"package available for your OS, you should stick with the release tarball."
-" If you want to develop using the most recent build, you should go with "
-"the <a href=\"https://git.gnunet.org/\";>git repository</a>."
+"package available for your OS, you should stick with the release tarball. If "
+"you want to develop using the most recent build, you should go with the <a "
+"href=\"https://git.gnunet.org/\";>git repository</a>."
msgstr ""
#: template/install.html.j2:98
@@ -2086,8 +2766,8 @@ msgstr ""
#: template/install.html.j2:106
msgid ""
-"Before building GNUnet, make sure that you setup the required groups and "
-"add your user to the group <code>gnunet</code>:"
+"Before building GNUnet, make sure that you setup the required groups and add "
+"your user to the group <code>gnunet</code>:"
msgstr ""
#: template/install.html.j2:117
@@ -2096,9 +2776,8 @@ msgstr ""
#: template/install.html.j2:128
msgid ""
-"You can find more configuration flags in the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>README</a>.<br> "
-"Install GNUnet with:"
+"You can find more configuration flags in the <a href=\"https://git.gnunet.";
+"org/gnunet.git/tree/README\">README</a>.<br> Install GNUnet with:"
msgstr ""
#: template/install.html.j2:138
@@ -2108,9 +2787,8 @@ msgstr ""
#: template/install.html.j2:146
msgid ""
"Check the <a href=\"https://docs.gnunet.org/handbook/gnunet.html#Minimal-";
-"configuration\">handbook</a> for detailed documentation. For a more "
-"hands-on experience, <a href=\"https://gnunet.org/en/use.html\";>continue "
-"here</a>."
+"configuration\">handbook</a> for detailed documentation. For a more hands-on "
+"experience, <a href=\"https://gnunet.org/en/use.html\";>continue here</a>."
msgstr ""
#: template/livingstandards.html.j2:11
diff --git a/locale/de/LC_MESSAGES/messages.po
b/locale/de/LC_MESSAGES/messages.po
index 99538b8..a3d680a 100644
--- a/locale/de/LC_MESSAGES/messages.po
+++ b/locale/de/LC_MESSAGES/messages.po
@@ -7,7 +7,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2021-03-03 21:41+0100\n"
+"POT-Creation-Date: 2021-03-12 16:12+0100\n"
"PO-Revision-Date: 2021-02-17 15:13+0000\n"
"Last-Translator: Weblate Admin <admin@example.com>\n"
"Language-Team: German <http://weblate.taler.net/projects/gnunet/website/de/";
@@ -66,6 +66,7 @@ msgid "About"
msgstr "Über GNUnet"
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
msgstr "Neues"
@@ -164,17 +165,20 @@ msgstr "REST API"
msgid "FAQ"
msgstr "FAQ"
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
msgstr ""
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
msgstr ""
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
msgstr ""
@@ -811,11 +815,133 @@ msgid ""
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
-#: template/faq.html.j2:12
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
+msgstr ""
+
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
+msgstr ""
+
+#: template/faq.html.j2:15 template/faq.html.j2:695
+msgid "Error messages"
+msgstr ""
+
+#: template/faq.html.j2:16 template/faq.html.j2:797
+#, fuzzy
+#| msgid "Motivation"
+msgid "File-sharing"
+msgstr "Motivation"
+
+#: template/faq.html.j2:17 template/faq.html.j2:973
+msgid "Contributing"
+msgstr ""
+
+#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr ""
+
+#: template/faq.html.j2:28
+msgid ""
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
+"the #gnunet IRC on irc.freenode.net."
+msgstr ""
+
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
+msgstr ""
+
+#: template/faq.html.j2:38
+msgid ""
+"A: The general answer is, when it is ready. A better answer may be: earlier "
+"if you contribute (test, debug, code, document). Every release will be "
+"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://";
+"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
+"the RSS feed of this site to automatically receive a notification."
+msgstr ""
+
+#: template/faq.html.j2:49
+msgid "Is the code free?"
+msgstr ""
+
+#: template/faq.html.j2:51
+msgid ""
+"A: GNUnet is free software, available under the <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
+msgstr ""
+
+#: template/faq.html.j2:58
+msgid "Are there any known bugs?"
+msgstr ""
+
+#: template/faq.html.j2:60
+msgid ""
+"A: We track the list of currently known bugs in the <a href=\"https://bugs.";
+"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
+"directly to developers or the developer mailing list. This is discouraged "
+"since developers often do not have the time to feed these bugs back into the "
+"Mantis database. Please report bugs directly to the bug tracking system. If "
+"you believe a bug is sensitive, you can set its view status to private (this "
+"should be the exception)."
+msgstr ""
+
+#: template/faq.html.j2:73 template/faq.html.j2:193
+msgid "Is there a graphical user interface?"
+msgstr "Gibt es eine Graphische Benutzeroberfläche?"
+
+#: template/faq.html.j2:75
+msgid ""
+"A: gnunet-gtk is a separate download. The package contains various GTK+ "
+"based graphical interfaces, including a graphical tool for configuration."
+msgstr ""
+
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr ""
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called ""
+"proof-of-work" which is used to convince the network that your peer is "
+"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
+"on the network size estimator). The calculation is expected to take a few "
+"days, depending on how fast your CPU is. If the CPU load is creating a "
+"problem for you, you can set the value "WORKDELAY" in the ""
+"nse" section of your configuration file to a higher value. The default "
+"is "5 ms"."
+msgstr ""
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr ""
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
+"connections and, with the Tor Browser Bundle, for the Web in particular. "
+"GNUnet does not really have one focus; our theme is secure decentralized "
+"networking, but that is too broad to be called a focus."
+msgstr ""
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr ""
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost no "
+"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
+"using onion (or garlic) routing as the basis for various (anonymized) "
+"applications. I2P is largely used via a Web frontend."
+msgstr ""
+
+#: template/faq.html.j2:124
msgid "Is GNUnet ready for use on production systems?"
msgstr ""
-#: template/faq.html.j2:14
+#: template/faq.html.j2:126
msgid ""
"A: GNUnet is still undergoing major development. It is largely not yet ready "
"for usage beyond developers. Your mileage will vary depending on the "
@@ -824,24 +950,467 @@ msgid ""
"rewriting it (Project "Transport Next Generation [TNG]")"
msgstr ""
-#: template/faq.html.j2:24
+#: template/faq.html.j2:136
msgid "Is GNUnet build using distributed ledger technologies?"
msgstr ""
-#: template/faq.html.j2:26
+#: template/faq.html.j2:138
msgid ""
"A: No. GNUnet is a new network protocol stack for building secure, "
"distributed, and privacy-preserving applications. While a ledger could be "
"built using GNUnet, we currently have no plans in doing so."
msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:151
+#, fuzzy
+#| msgid "What is GNUnet?"
+msgid "What can I do with GNUnet?"
+msgstr "Was ist GNUnet?"
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
+"do more than just one thing. Naturally, the implementation and documentation "
+"of some of the features that exist are more advanced than others."
+msgstr ""
+
+#: template/faq.html.j2:160
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
+"decentralized and censorship-resistant replacement for DNS and a mechanism "
+"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
+msgstr ""
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We "
+"recommend that you use Tor for anonymous surfing."
+msgstr ""
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr ""
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+
+#: template/faq.html.j2:195
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the "
+"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
+"that integrates most of the other GUIs in one window. One exception is "
+"gnunet-setup, which must still be run separately at this time (as setup "
+"requires the peer to be stopped)."
+msgstr ""
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr ""
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
+"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
+"FreeBSD and macOS. We have reports of working versions on many other GNU/"
+"Linux distributions; in the past we had reports of working versions on "
+"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
+"so if you cannot get GNUnet to work on those systems please let us know."
+msgstr ""
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr ""
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a default "
+"configuration of top-level domains. The governance of this default "
+"configuration is not yet established. In any case, the user will be able to "
+"modify this configuration at will. We expect normal users to have no need to "
+"edit their own GNS zone(s) unless they host services themselves."
+msgstr ""
+
+#: template/faq.html.j2:241
+msgid "Where is the per-user GNS database kept?"
+msgstr ""
+
+#: template/faq.html.j2:243
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet peer. "
+"Now, a user may run multiple GNUnet peers, in which case the database could "
+"be kept at each peer (however, we don't have code for convenient "
+"replication). Similarly, multiple GNUnet peers can share one instance of the "
+"database --- the "gnunet-service-namestore" can be accessed from "
+"remote (via TCP). The actual data can be stored in a Postgres database, for "
+"which various replication options are again applicable. Ultimately, there "
+"are many options for how users can store (and secure) their GNS database."
+msgstr ""
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases "
+"will only grow to a few tens of thousands of entries, small enough to fit "
+"even on mobile devices."
+msgstr ""
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr ""
+
+#: template/faq.html.j2:272
+msgid ""
+"A: We believe so, as there is no entity that any government could force to "
+"change the mapping for a name except for each individual user (and then the "
+"changes would only apply to the names that this user is the authority for). "
+"So if everyone used GNS, the only practical attack of a government would be "
+"to force the operator of a server to change the GNS records for his server "
+"to point elsewhere. However, if the owner of the private key for a zone is "
+"unavailable for enforcement, the respective zone cannot be changed and any "
+"other zone delegating to this zone will achieve proper resolution."
+msgstr ""
+
+#: template/faq.html.j2:286
+msgid "How does GNS compare to other name systems"
+msgstr ""
+
+#: template/faq.html.j2:288
+msgid ""
+"A: A scientific paper on this topic <a href=\"https://grothoff.org/christian/";
+"ns2018.pdf\">has been published </a> and below is a table from the "
+"publication. For detailed descriptions please refer to the paper."
+msgstr ""
+
+#: template/faq.html.j2:392
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr ""
+
+#: template/faq.html.j2:394
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
+"there are still registrars that determine who owns a name. <br><br> With "
+"GNS, we decentralize the database and also decentralize the responsibility "
+"for naming: each user runs his own personal root zone and is thus in "
+"complete control of the names he uses. GNS also has many additional features "
+"(to keep names short and enable migration) which don't even make sense in "
+"the context of CoDoNS."
+msgstr ""
+
+#: template/faq.html.j2:410
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr ""
+
+#: template/faq.html.j2:412
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared via "
+"delegation, and thus mappings will only change if the user responsible for "
+"the name (the authority) manually changes the record."
+msgstr ""
+
+#: template/faq.html.j2:426
+msgid "What is the difference between GNS and ODDNS?"
+msgstr ""
+
+#: template/faq.html.j2:428
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+
+#: template/faq.html.j2:439
+msgid "What is the difference between GNS and Handshake?"
+msgstr ""
+
+#: template/faq.html.j2:441
+msgid ""
+"A: Handshake is a blockchain-based method for root zone governance. Hence, "
+"it does not address the name resolution process itself but delegates "
+"resolution into DNS after the initial TLD resolution. Not taking "
+"sustainablility considerations into account, handshake could be used as an "
+"additional supporting GNS root zone governance model but we currently do not "
+"have such plans in mind."
+msgstr ""
+
+#: template/faq.html.j2:453
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr ""
+
+#: template/faq.html.j2:455
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks on "
+"DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from "
+"the DNS hierarchy."
+msgstr ""
+
+#: template/faq.html.j2:468
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the style "
+"of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: For security, it is well known that an initial trust path between the two "
+"parties must exist. However, for applications where this is not required, "
+"weaker mechanisms can be used. For example, we have implemented a first-come-"
+"first-served (FCFS) authority which allows arbitrary users to register "
+"arbitrary names. The key of this authority is included with every GNUnet "
+"installation. Thus, any name registered with FCFS is in fact global and "
+"requires no further introduction. However, the security of these names "
+"depends entirely on the trustworthiness of the FCFS authority. The authority "
+"can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name in "
+"GNS?"
+msgstr ""
+
+#: template/faq.html.j2:487
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "legitimate" "
+"domain owner. Any user can claim any name (as his preferred name or ""
+"pseudonym") in his NICK record. Similarly, all other users can choose "
+"to ignore this preference and use a name of their choice (or even assign no "
+"name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:498
+msgid ""
+"Did you consider the privacy implications of making your personal GNS zone "
+"visible?"
+msgstr ""
+
+#: template/faq.html.j2:500
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not set. "
+"Thus, users have full control over what information about their zones is "
+"made public."
+msgstr ""
+
+#: template/faq.html.j2:510
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary because "
+"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
+"of virtual hosting. However, LEHOs are also useful to help with X.509 "
+"certificate validation (as they specify for which legacy hostname the "
+"certificate should be valid). Also, even with IPv6 fully deployed and ""
+"infinite" IP addresses being available, we're not sure that virtual "
+"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
+"become commonplace, GNS should work with today's networks."
+msgstr ""
+
+#: template/faq.html.j2:526
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:528
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. As "
+"trust relationships evolve, mappings would change their meaning as they "
+"cross each others thresholds. We decided that the resulting unpredictability "
+"of the resolution process was not acceptable. Furthermore, trust and "
+"consensus might be easy to manipulate by adversaries."
+msgstr ""
+
+#: template/faq.html.j2:539
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:541
+msgid ""
+"A: The owner of a private key can create a revocation message. This one can "
+"then be flooded throughout the overlay network, creating a copy at all "
+"peers. Before using a public key, peers check if that key has been revoked. "
+"All names that involve delegation via a revoked zone will then fail to "
+"resolve. Peers always automatically check for the existence of a revocation "
+"message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:553
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:555
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:569
+msgid ""
+"How can a GNS zone maintain several name servers, e.g. for load balancing?"
+msgstr ""
+
+#: template/faq.html.j2:571
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share "
+"the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:584
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:586
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names are "
+"not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on your "
+"application, HTTPS may not be worth the cost. However, for users that are "
+"experiencing censorship (or are concerned about it), giving up globally "
+"unique names may very well be worth the cost. After all, what is a ""
+"globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:600
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:602
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by IANA/ICANN. "
+"This centralization creates vulnerabilities. For example, the US government "
+"was able to reassign the management of the country-TLDs of Afganistan and "
+"Iraq during the wars at the beginning of the 21st century."
+msgstr ""
+
+#: template/faq.html.j2:613
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:615
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
+"so blocking a particular IP address causes much more collateral damage than "
+"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
+"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
+"censorship resistant naming system. Accessing Tor's ".onion" "
+"namespace currently requires users to use unmemorable cryptographic "
+"identifiers. With nicer names, Tor and tor2web-like services would be even "
+"easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:634
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:636
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can use "
+"GNS to perform name resolution as well as any normal user. Naturally, while "
+"we typically expect normal users to install custom software for name "
+"resolution, this is unlikely to work for search engines today. However, the "
+"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
+"they can still index GNS resources. However, as using DNS2GNS gateways "
+"breaks the cryptographic chain of trust, legacy search engines will "
+"obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:650
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:652
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was designed "
+"to interoperate with DNS as much as possible, and to also work as much as "
+"possible with the existing Web infrastructure. UIA is not at all concerned "
+"about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:665
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:667
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you know "
+"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
+"and can thus decide how much you trust the result. Naturally, the trusted-"
+"computing base (TCB) can become arbitrarily large this way --- however, "
+"given the name length restriction, for an individual name it is always less "
+"than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:679
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part of "
+"the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:681
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects the "
+""_Service._Proto" syntax, converts "Service" to the "
+"corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when the "
+"result is presented, GNS looks for the GNS-specific "BOX" record "
+"type. A BOX record is a record that contains another record (such as SRV or "
+"TLSA records) and adds a service and protocol number (and the original boxed "
+"record type) to it."
+msgstr ""
+
+#: template/faq.html.j2:697
msgid ""
"I receive many "WARNING Calculated flow delay for X at Y for Z". "
"Should I worry?"
msgstr ""
-#: template/faq.html.j2:37
+#: template/faq.html.j2:699
msgid ""
"A: Right now, this is expected and a known cause for high latency in GNUnet. "
"We have started a major rewrite to address this and other problems, but "
@@ -849,14 +1418,191 @@ msgid ""
"expected."
msgstr ""
-#: template/faq.html.j2:46
-msgid "Is there a graphical user interface?"
-msgstr "Gibt es eine Graphische Benutzeroberfläche?"
+#: template/faq.html.j2:708
+msgid "Error opening `/dev/net/tun': No such file or directory?"
+msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:710
msgid ""
-"A: gnunet-gtk is a separate download. The package contains various GTK+ "
-"based graphical interfaces, including a graphical tool for configuration."
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:722
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
+"dns)?"
+msgstr ""
+
+#: template/faq.html.j2:724
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check if "
+"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:736
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:738
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if "
+"your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:746
+msgid ""
+"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:748
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if you "
+"compiled GNUnet the normal way and/or used a binary package, that is highly "
+"unlikely. The more common cause is that you installed GNUnet to a directory "
+"that your linker does not search. There are several ways to fix this that "
+"are described below. If you are 'root' and you installed to a system folder "
+"(such as /usr/local), you want to add the libraries to the system-wide "
+"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
+"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
+"similar path, you obviously have to change \"/usr/local\" accordingly. If "
+"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
+"$USER/\", then you can explicitly tell your linker to search a particular "
+"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
+"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
+"you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:774
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the \"$\") "
+"to your .bashrc or .profile file. You will have to logout and login again to "
+"have this new profile be applied to all shells (including your desktop "
+"environment)."
+msgstr ""
+
+#: template/faq.html.j2:781
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:783
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
+"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
+"always refer to harmless events that require no action. For example, GNUnet "
+"may use an INFO message to indicate that it is currently performing an "
+"expensive operation that will take some time. GNUnet will also use INFO "
+"messages to display information about important configuration values."
+msgstr ""
+
+#: template/faq.html.j2:799
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:801
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
+"P2P networks, GNUnet was designed with security in mind as the highest "
+"priority. We intend on producing a network with comprehensive security "
+"features. Many other P2P networks are open to a wide variety of attacks, and "
+"users have little privacy. GNUnet is also Free Software and thus the source "
+"code is available, so you do not have to worry about being spied upon by the "
+"software. The following table summarises the main differences between GNUnet "
+"and other systems. The information is accurate to the best of our knowledge. "
+"The comparison is difficult since there are sometimes differences between "
+"various implementations of (almost) the same protocol. In general, we pick a "
+"free implementation as the reference implementation since it is possible to "
+"inspect the free code. Also, all of these systems are changing over time and "
+"thus the data below may not be up-to-date. If you find any flaws, please let "
+"us know. Finally, the table is not saying terribly much (it is hard to "
+"compare these systems this briefly), so if you want the real differences, "
+"read the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:915
+msgid ""
+"Another important point of reference are the various anonymous peer-to-peer "
+"networks. Here, there are differences in terms of application domain and how "
+"specifically anonymity is achieved. Anonymous routing is a hard research "
+"topic, so for a superficial comparisson like this one we focus on the "
+"latency. Another important factor is the programming language. Type-safe "
+"languages may offer certain security benefits; however, this may come at the "
+"cost of significant increases in resource consumption which in turn may "
+"reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:928
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:930
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of the "
+"same techniques used to generate reasonable passwords to defend against such "
+"an attack. In any event, we are not trying to hide content; thus, unless the "
+"user is trying to insert information into the network that can only be "
+"shared with a small group of people, there is no real reason to try to "
+"obfuscate the content by choosing a difficult keyword anyway."
+msgstr ""
+
+#: template/faq.html.j2:944
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:946
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all "
+"users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell which "
+"of the peers in the group originated the message. In other words, it should "
+"be difficult to impossible for an adversary to distinguish between the "
+"originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:958
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:960
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
+"its public key) and has a number of addresses it is reachable by (may have "
+"no addresses, for instance when it's behind a NAT). You specify bandwidth "
+"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
+"(how large your on-disk block storage is) . Your node will then proceed to "
+"connect to other nodes, becoming part of the network."
+msgstr ""
+
+#: template/faq.html.j2:975
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:977
+msgid ""
+"A: First, you need to register an account with our weblate system. Please "
+"send an e-mail with the desired target language to translators@gnunet.org or "
+"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
+"sufficient permissions will then grant you access. Naturally, any abuse will "
+"result in the loss of permissions."
+msgstr ""
+
+#: template/faq.html.j2:989
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:991
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly implement. "
+"The best way to actually get a new feature implemented is to do it yourself "
+"--- and to then send us a patch."
msgstr ""
#: template/glossary.html.j2:12
@@ -963,10 +1709,6 @@ msgstr ""
msgid "Overview"
msgstr ""
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
-
#: template/gns.html.j2:39
msgid ""
"The GNU Name System (GNS) is secure and decentralized naming system. It "
diff --git a/locale/es/LC_MESSAGES/messages.po
b/locale/es/LC_MESSAGES/messages.po
index c8f0e9f..4607c01 100644
--- a/locale/es/LC_MESSAGES/messages.po
+++ b/locale/es/LC_MESSAGES/messages.po
@@ -8,7 +8,7 @@ msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
"POT-Creation-Date: 2021-03-03 21:41+0100\n"
-"PO-Revision-Date: 2021-03-09 18:35+0000\n"
+"PO-Revision-Date: 2021-03-16 22:31+0000\n"
"Last-Translator: Samira Tamboura <samiratg8@hotmail.com>\n"
"Language-Team: Spanish <http://weblate.taler.net/projects/gnunet/website/es/>"
"\n"
@@ -66,6 +66,7 @@ msgid "About"
msgstr "Sobre"
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
msgstr "Nuevo"
@@ -158,18 +159,21 @@ msgstr "REST API"
msgid "FAQ"
msgstr "Preguntas frecuentes"
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
msgstr ""
"Nuevas publicaciones sobre cambios en GNUnet, como lanzamientos y eventos"
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
msgstr "suscríbase a nuestro canal RSS"
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
msgstr "leer más"
@@ -198,7 +202,6 @@ msgstr ""
"creación de una internet GNU."
#: template/about.html.j2:23
-#, fuzzy
msgid ""
"Today, the actual use and thus the social requirements for a global network "
"differs widely from those goals of 1970. While the Internet remains suitable "
@@ -206,11 +209,11 @@ msgid ""
"hierarchy and when necessary isolated from the rest of the world, the "
"situation is less tenable for civil society."
msgstr ""
-"Hoy, el uso real y, consecuentemente, los requerimientos sociales para una "
-"red global difieren ampliamente de los mismos objetivos de 1970. Mientras "
-"que el internet sigue siendo útil para fines militares, donde el equipo de "
-"la red se opera por una jerarquía de comandos y aislada del resto del mundo "
-"cuando es necesario, la situación es menos sostenible para la sociedad civil."
+"El uso concreto y, en consecuencia, los requerimientos sociales de una red "
+"global en la actualidad, difieren con creces de las metas fijadas en 1970. "
+"Mientras el Internet aún es útil para fines militares, donde el equipo de "
+"red es operado por una cadena de mando que, si es necesario, puede aislarla "
+"del resto del mundo, la sociedad civil enfrenta mayor vulnerabilidad."
#: template/about.html.j2:32
msgid ""
@@ -221,25 +224,25 @@ msgid ""
"cryptographyengineering.com/2015/08/16/the-network-is-hostile/\">\"the "
"network is hostile\"</a>."
msgstr ""
-"Debido a las elecciones fundamentales de diseño de Internet, el trafico de "
-"internet puede ser desviado, interceptado, censurado y manipulado por "
-"enrutadores hostiles en la red. Y por supuesto, el internet moderno ha "
-"evolucionado exactamente hasta el punto en que , como Matthew Green lo puso, "
-"<a href=\"https://blog.cryptographyengineering.com/2015/08/16/";
-"the-network-is-hostile/\">\"La red es hostil\"</a>."
+"Debido a elecciones fundamentales sobre su diseño, el tráfico de Internet "
+"puede ser desviado, interceptado, censurado y manipulado por enrutadores "
+"hostiles en la red. Y claro, el internet moderno ha evolucionado hasta el "
+"punto exacto, como Matthew Green lo puso, <a href=\"https://blog.";
+"cryptographyengineering.com/2015/08/16/the-network-is-hostile/\">\"la red es "
+"hostil\"</a>."
#: template/about.html.j2:41
-#, fuzzy
msgid ""
"We believe liberal societies need a network architecture that uses the anti-"
"authoritarian decentralized peer-to-peer paradigm and privacy-preserving "
"cryptographic protocols. The goal of the GNUnet project is to provide a Free "
"Software realization of this ideal."
msgstr ""
-"Creemos que las sociedades liberales necesitan una arquitectura de red que "
-"utilice el paradigma anti-autoritario, descentralizado «peer to peer» y "
-"protocolos criptográficos de preservación de la privacidad. El objetivo del "
-"projecto GNUnet is proveer un resultado de Software libre de este ideal."
+"Creemos que las sociedades liberales necesitan una arquitectura de red "
+"acorde al paradigma anti-autoritario, descentralizado «peer to peer», así "
+"como protocolos criptográficos que resguarden la privacidad. El objetivo del "
+"proyecto GNUnet es proveer un resultado de Software libre conforme a este "
+"ideal."
#: template/about.html.j2:49
msgid ""
@@ -262,7 +265,7 @@ msgid ""
"GNUnet must minimize the amount of personally identifiable information "
"exposed."
msgstr ""
-"GNUnet debe minimizar la cantidad de información personal de identificación "
+"GNUnet debe minimizar la cantidad de información de identificación personal "
"expuesta."
#: template/about.html.j2:61
@@ -270,8 +273,8 @@ msgid ""
"GNUnet must be fully distributed and resilient to external attacks and rogue "
"participants."
msgstr ""
-"GNUnet debe ser plenamente distribuido con resistencia hacia ataques "
-"externos y a participantes fraudulentos."
+"GNUnet debe estar plenamente distribuido, resiliente a ataques externos y "
+"participantes fraudulentos."
#: template/about.html.j2:62
msgid ""
@@ -295,7 +298,9 @@ msgstr "GNUnet debe ser abierto y permitir que nuevos pares
se unan."
#: template/about.html.j2:65
msgid "GNUnet must support a diverse range of applications and devices."
-msgstr "GNUnet debe suportar un rango diverso de aplicaciones y dispositivos."
+msgstr ""
+"GNUnet debe ser compatible con un diverso rango de aplicaciones y "
+"dispositivos."
#: template/about.html.j2:66
msgid "GNUnet must use compartmentalization to protect sensitive information."
@@ -305,15 +310,15 @@ msgstr ""
#: template/about.html.j2:67
msgid "The GNUnet architecture must be resource efficient."
-msgstr "La arquitectura de GNUnet debe ser eficiente en términos de recursos."
+msgstr "La arquitectura de GNUnet debe hacer uso eficiente de sus recursos."
#: template/about.html.j2:68
msgid ""
"GNUnet must provide incentives for peers to contribute more resources than "
"they consume."
msgstr ""
-"GNUnet debe entregar incentivos para que los pares contribuyan con más "
-"recursos de los que consumen."
+"GNUnet debe incentivar que los pares contribuyan con más recursos de los que "
+"consumen."
#: template/about.html.j2:72
msgid ""
@@ -336,18 +341,18 @@ msgid ""
msgstr ""
"Para tener conocimiento y aprendes más, por favor chequé nuestro <a href="
"\"https://docs.gnunet.org/handbook/gnunet.html\";>manual</a>,especialmente el "
-"<a href=\"https://docs.gnunet.org/handbook/gnunet.html#Key-Concepts\"";
-">capitulo en \"conceptos clave\"</a>, explicando los conceptos fundamentales "
-"de GNUnet: <ul> <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#";
-"Authentication\">Auntenticación</a></li> <li><a href=\"https://docs.gnunet.";
-"org/handbook/gnunet.html#Accounting-to-Encourage-Resource-Sharing\""
-">Contabilidad para fomentar el intercambio de recursos</a></li> <li><a href="
-"\"https://docs.gnunet.org/handbook/gnunet.html#Confidentiality\"";
-">Confidencialidad</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"<a href=\"https://docs.gnunet.org/handbook/gnunet.html#Key-Concepts";
+"\">capitulo en \"conceptos clave\"</a>, explicando los conceptos "
+"fundamentales de GNUnet: <ul> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Authentication\">Auntenticación</a></li> <li><a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Accounting-to-Encourage-Resource-Sharing"
+"\">Contabilidad para fomentar el intercambio de recursos</a></li> <li><a "
+"href=\"https://docs.gnunet.org/handbook/gnunet.html#Confidentiality";
+"\">Confidencialidad</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
"gnunet.html#Anonymity\">Anonimato</a></li> <li><a href=\"https://docs.gnunet.";
-"org/handbook/gnunet.html#Deniability\">Negación</a></li> <li><a href=\"https"
-"://docs.gnunet.org/handbook/gnunet.html#Peer-Identities\">Identidades de "
-"compañeros</a></li> <li><a href=\"https://docs.gnunet.org/handbook/gnunet.";
+"org/handbook/gnunet.html#Deniability\">Negación</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Peer-Identities\";>Identidades "
+"de compañeros</a></li> <li><a href=\"https://docs.gnunet.org/handbook/gnunet.";
"html#Zones-in-the-GNU-Name-System-_0028GNS-Zones_0029\">Zonas en el nombre "
"del sistema GNU</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
"gnunet.html#Egos\">Egos</a></li> </ul>"
@@ -368,9 +373,9 @@ msgstr ""
"Hay muchos más recursos disponibles para aprender sobre GNUnet fuera del <a "
"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>manual</a>, como <a "
"href=\"https://bib.gnunet.org/\";>bibliografía</a> con artículos que cubren "
-"las diversas capas, muchos <a href=\"https://gnunet.org/en/video.html";
-"\">videos</a> o un corto <a href=\"https://gnunet.org/en/glossary.html";
-"\">glosario</a>."
+"las diversas capas, muchos <a href=\"https://gnunet.org/en/video.html\"";
+">videos</a> o un breve<a href=\"https://gnunet.org/en/glossary.html\";> "
+"glosario</a>."
#: template/about.html.j2:95
msgid ""
@@ -389,8 +394,8 @@ msgid ""
"alpha stage when it comes to software – its not an easy task to "
"rewrite the whole Internet!"
msgstr ""
-"Por favor tenga en cuenta que este proyecto está (a pesar de su edad) aún en "
-"una etapa temprana alfa en términos de software – y ¡no es tarea "
+"Por favor considere que, pese a su edad, el software de este proyecto se "
+"encuentra en una temprana etapa alfa de desarrollo – y ¡no es tarea "
"sencilla reescribir todo Internet!"
#: template/about.html.j2:105
@@ -420,9 +425,9 @@ msgstr ""
"Este proyecto ha recibido financiamiento del fondo de investigación e "
"innovación Horizonte 2020 de la Unión Europea bajo el convenio de subvención "
"NGI_TRUST n. 825618. El proyecto busca integrar re:claimID con el sistema de "
-"pago de GNU Taler en un proyecto piloto para así demostrar la factibilidad "
-"práctica y los beneficios de las tecnologías potenciadoras de la privacidad "
-"para usuarios y proveedores de servicios comerciales. Este proyecto se llama "
+"pago de GNU Taler en un proyecto piloto, para demostrar la factibilidad "
+"práctica y los beneficios de tecnologías que respaldan la privacidad de "
+"usuarios y proveedores de servicios comerciales. Este proyecto se llama "
"\"Identidad descentralizada para usuario final soberano\" (DISSENS)."
#: template/about.html.j2:141
@@ -446,7 +451,7 @@ msgstr "Aplicaciones que ofrece GNUnet"
#: template/applications.html.j2:13 template/gns.html.j2:7
msgid "The GNU Name System"
-msgstr "El sistema de nombres GNU"
+msgstr "El Sistema de Nombres GNU"
#: template/applications.html.j2:15
msgid ""
@@ -458,12 +463,12 @@ msgid ""
"cryptographically secured. <!-- Too technical: GNS integrates a robust, "
"efficient and instant key revocation mechanism. -->"
msgstr ""
-"El <a href=\"gns.html\">sistema de nombre GNU(GNS)</a> es un reemplazo "
-"totalmente descentralizado por el Sistema de Nombre de Domino (DNS). En "
-"lugar de usar un jerarquía, GNS usa un grafico dirigido. El convenio de "
-"denominaciones es similar a DNS, pero las consultas y respuestas son privada "
-"incluso con respecto a otros que brindas la respuesta- La integridad de "
-"registros y la privacidad de de las búsquedas esta protegida "
+"El <a href=\"gns.html\">Sistema de Nombre GNU(GNS)</a> es un reemplazo "
+"totalmente descentralizado para el Sistema de Nombre de Domino (DNS). En "
+"lugar de usar un jerarquía, GNS usa un gráfico dirigido. El convenio de "
+"denominaciones es similar al DNS, pero consultas y réplicas son privadas "
+"incluso para los pares que brindan las respuestas. La integridad de "
+"registros y la privacidad de de las búsquedas estpa protegida "
"criptográficamente. <!-- Too technical: GNS integrates a robust, efficient "
"and instant key revocation mechanism. -->"
@@ -695,8 +700,8 @@ msgid ""
"IjaAfLiruzjxFFzKAV:matrix.org/\">archive</a> available."
msgstr ""
"<tt>#gnunet</tt> es una vía accesible <a href=\"https://freenode.net\";>irc."
-"freenode.net</a>. También hay un <a href=\"https://view.matrix.org/room/";
-"!IjaAfLiruzjxFFzKAV:matrix.org/\">archivo</a> disponible."
+"freenode.net</a>. También hay un <a href=\"https://view.matrix.org/room/!";
+"IjaAfLiruzjxFFzKAV:matrix.org/\">archivo</a> disponible."
#: template/contact.html.j2:38
msgid "Contacting individuals"
@@ -841,8 +846,8 @@ msgid ""
msgstr ""
"Usamos <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> "
"para analizar la cobertura del código de nuestras pruebas, los resultados "
-"están disponibles en <a href=\"https://old.gnunet.org/coverage/\";>https://old";
-".gnunet.org/coverage/</a> ."
+"están disponibles en <a href=\"https://old.gnunet.org/coverage/\";>https://";
+"old.gnunet.org/coverage/</a> ."
#: template/developers.html.j2:72
msgid "Performance Analysis"
@@ -884,8 +889,8 @@ msgid ""
"The tarball of the latest version can be obtained from GNU FTP and its "
"mirrors."
msgstr ""
-"La ultima version del fichero, se puede obtener desde GNU FTP o en sus ré"
-"plicas/espejos."
+"La ultima version del fichero, se puede obtener desde GNU FTP o en sus "
+"réplicas/espejos."
#: template/download.html.j2:30
msgid "git"
@@ -950,10 +955,20 @@ msgid ""
"git/\">Satzung</a> (currently only available in German, translations "
"welcome)."
msgstr ""
+"Los desarrolladores de GNUnet con acceso a git (escritura) pueden "
+"convertirse en miembros para participar en el proceso de decisión y apoyar "
+"formalmente a GNUnet e.V. Para ello, todo lo que tienes que hacer es acceder "
+"al repositorio y actualizar el archivo <tt> members.txt </tt> en <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/\";> gnunet-ev </a>. No hay cuotas de "
+"membresía; sin embargo, se invita a que los miembros apoyen GNUnet e.V. y en "
+"particular que contribuyan al desarrollo técnico dentro de sus "
+"posibilidades. Para obtener más detalles, consulte el <a href=\"https://git.";
+"gnunet.org/gnunet-ev.git/\"> Satzung </a> (actualmente solo está disponible "
+"en alemán, las traducciones son bienvenidas)."
#: template/ev.html.j2:52
msgid "Governance"
-msgstr ""
+msgstr "Gobernanza"
#: template/ev.html.j2:54
msgid ""
@@ -965,14 +980,22 @@ msgid ""
"<dt>Kassenwart</dt> <dd>Florian Dold</dd> <dt>Beisitzer</dt> <dd> <a href="
"\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 </dd> </dl>"
msgstr ""
+"Puede encontrar nuestro \"Satzung\" y la lista de miembros en <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex\";> https: //git."
+"gnunet. org / gnunet-ev.git / tree / satzung.tex </a>. La junta directiva "
+"actual está formada por: <dl> <dt> Vorsitz </dt> <dd> <a href=\"https://";
+"schanzen.eu\"> Martin Schanzenbach </a> </dd> <dt> Stellvertretender Vorsitz "
+"< / dt> <dd> t3sserakt </dd> <dt> Kassenwart </dt> <dd> Florian Dold </dd> "
+"<dt> Beisitzer </dt> <dd> <a href = \"https: // grothoff. org / christian / "
+"\"> Christian Grothoff </a>, capítulo 3 </dd> </dl>"
#: template/ev.html.j2:73
msgid "Official Meeting Notes"
-msgstr ""
+msgstr "Notas Oficiales de la Reunión"
#: template/ev.html.j2:86
msgid "Support Us!"
-msgstr ""
+msgstr "¡Apóyanos!"
#: template/ev.html.j2:88
msgid ""
@@ -986,12 +1009,187 @@ msgid ""
"<dd>1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh</dd> <dt>SEPA/IBAN</dt> "
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
+"Todos son bienvenidos para apoyarnos a través de donaciones. Para las "
+"contribuciones financieras, los europeos pueden donar a través de SEPA. "
+"Esperamos configurar cuentas en otras áreas monetarias importantes en el "
+"futuro. También puede donar a través de Bitcoin, los detalles de "
+"enrutamiento están a continuación. Tenga en cuenta que no podemos "
+"proporcionar recibos de sus donaciones. Si planea donar una cantidad "
+"significativa de dinero, comuníquese con nosotros primero, ya que podría ser "
+"mejor llegar a un acuerdo personalizado. <dl> <dt> BitCoin </dt> <dd> "
+"1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh </dd> <dt> SEPA / IBAN </dt> <dd> "
+"DE67830654080004822650 (BIC / SWIFT: GENODEF1SLR) </dd> </dl>"
+
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
+msgstr "General"
+
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
+msgstr "Características"
-#: template/faq.html.j2:12
-msgid "Is GNUnet ready for use on production systems?"
+#: template/faq.html.j2:15 template/faq.html.j2:695
+msgid "Error messages"
+msgstr "Mensajes de error"
+
+#: template/faq.html.j2:16 template/faq.html.j2:797
+#, fuzzy
+msgid "File-sharing"
+msgstr "Filesharing o compartir documentos (Alfa)"
+
+#: template/faq.html.j2:17 template/faq.html.j2:973
+msgid "Contributing"
+msgstr "Contribuir"
+
+#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr "¿Qué hago si aquí no responden mi pregunta?"
+
+#: template/faq.html.j2:28
+msgid ""
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
+"the #gnunet IRC on irc.freenode.net."
+msgstr ""
+"R: Hay muchas otras fuentes de información. Puedes leer documentación "
+"adicional o preguntar en la lista de correos help-gnunet@gnu.org o en el IRC "
+"#gnunet en irc.freenode.net."
+
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
+msgstr "¿Cuándo lanzarán la próxima versión?"
+
+#: template/faq.html.j2:38
+msgid ""
+"A: The general answer is, when it is ready. A better answer may be: earlier "
+"if you contribute (test, debug, code, document). Every release will be "
+"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://";
+"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
+"the RSS feed of this site to automatically receive a notification."
msgstr ""
+"R: La respuesta general es, cuando esté lista. Una mejor respuesta puede ser:"
+" antes si colaboras (probando, depurando, escribiendo código, documentando). "
+"Cada lanzamiento se anunciará en la lista de correo info-gnunet@gnu.org y en "
+"<a href=\"https://planet.gnu.org\";> planeta GNU </a>. Puedes suscribirte a "
+"la lista de correo o al canal RSS de este sitio para recibir automáticamente "
+"una notificación."
+
+#: template/faq.html.j2:49
+#, fuzzy
+msgid "Is the code free?"
+msgstr "¿Es software libre?"
-#: template/faq.html.j2:14
+#: template/faq.html.j2:51
+msgid ""
+"A: GNUnet is free software, available under the <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
+msgstr ""
+"R: GNUnet es un software libre, disponible bajo la <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\"> GNU Affero Public License (AGPL) </a>."
+
+#: template/faq.html.j2:58
+#, fuzzy
+msgid "Are there any known bugs?"
+msgstr "¿Hay algún error conocido?"
+
+#: template/faq.html.j2:60
+#, fuzzy
+msgid ""
+"A: We track the list of currently known bugs in the <a href=\"https://bugs.";
+"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
+"directly to developers or the developer mailing list. This is discouraged "
+"since developers often do not have the time to feed these bugs back into the "
+"Mantis database. Please report bugs directly to the bug tracking system. If "
+"you believe a bug is sensitive, you can set its view status to private (this "
+"should be the exception)."
+msgstr ""
+"R: Hacemos seguimiento sobre la lista de errores ya conocidos en el <a href="
+"\"https://bugs.gnunet.org/\";>sistema Mantis</a>. Algunos errores son, "
+"ocasionalmente, enviados directamente a programadores o a la lista de "
+"correo. Se desaconseja esto ya que los desarrolladores a menudo no tienen "
+"tiempo para enviar estos errores a la base de datos de Mantis. Informa los "
+"errores directamente al sistema de seguimiento de errores. Si crees que un "
+"error es \"sensible\", puedes establecer su estado de vista como privado ("
+"esta debería ser la excepción)."
+
+#: template/faq.html.j2:73 template/faq.html.j2:193
+msgid "Is there a graphical user interface?"
+msgstr "¿Existe una interfaz gráfica de usuario?"
+
+#: template/faq.html.j2:75
+msgid ""
+"A: gnunet-gtk is a separate download. The package contains various GTK+ "
+"based graphical interfaces, including a graphical tool for configuration."
+msgstr ""
+"R: gnunet-gtk es una descarga separada. El paquete contiene varias "
+"interfaces gráficas basadas en GTK +, incluida una herramienta gráfica para "
+"la configuración."
+
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr "¿Por qué gnunet-service-nse genera un uso elevado del CPU?"
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called ""
+"proof-of-work" which is used to convince the network that your peer is "
+"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
+"on the network size estimator). The calculation is expected to take a few "
+"days, depending on how fast your CPU is. If the CPU load is creating a "
+"problem for you, you can set the value "WORKDELAY" in the ""
+"nse" section of your configuration file to a higher value. The default "
+"is "5 ms"."
+msgstr ""
+"R: El proceso gnunet-service-nse computará inicialmente las bien llamadas "
+""pruebas de trabajo" lo cual se usa para convencer a la red que tu "
+"red de pares es real (o, más bien, hacer que sea costoso para un adversario "
+"organizar un ataque Sybil en la estimación del tamaño de la red). Se espera "
+"que los cálculos lleven varios días, dependiendo de lo rápido que sea tu "
+"CPU. Si la carga del CPU te produce un problema, puedes especificar un valor "
+"mayor en el "WORKDELAY" en la sección "nse" de "
+"configuración de tu archivo. El valor por defecto es "5 ms"."
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr "¿Cómo se compara GNUnet con Tor?"
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
+"connections and, with the Tor Browser Bundle, for the Web in particular. "
+"GNUnet does not really have one focus; our theme is secure decentralized "
+"networking, but that is too broad to be called a focus."
+msgstr ""
+"R: Tor se centra en comunicaciones anónimas y en resistencia a la censura "
+"para conexiones TCP (Protocolo de Control de Transmisión) y, el paquete de "
+"navegador Tor, para la web en particular. GNUnet no tiene realmente un "
+"enfoque; nuestro propósito es una red segura descentralizada, pero esto es "
+"muy amplio para ser considerado un enfoque."
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr "¿Cómo se compara GNUnet con I2P (Proyecto de Internet invisible)?"
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost no "
+"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
+"using onion (or garlic) routing as the basis for various (anonymized) "
+"applications. I2P is largely used via a Web frontend."
+msgstr ""
+"R: Ambos dos, GNUnet y I2P, quieren construir un internet mejor, mas seguro "
+"y mas descentralizado. Sin embargo, desde el punto de vista técnico, no hay "
+"casi coincidencias.<br><b. r>I2P esta escrito en Java, y tiene túneles de "
+"enrutamiento (asimétricos) cebolla (o ajo) como base para varias "
+"aplicaciones (anonimizadas). I2P is principalmente usada en webs del lado "
+"del cliente."
+
+#: template/faq.html.j2:124
+msgid "Is GNUnet ready for use on production systems?"
+msgstr "¿Está GNUnet lista para usarse en sistemas de producción?"
+
+#: template/faq.html.j2:126
msgid ""
"A: GNUnet is still undergoing major development. It is largely not yet ready "
"for usage beyond developers. Your mileage will vary depending on the "
@@ -999,45 +1197,787 @@ msgid ""
"current low-level transport system. We are currently in the process of "
"rewriting it (Project "Transport Next Generation [TNG]")"
msgstr ""
+"R: GNUnet todavía está experimentando un desarrollo importante. En su "
+"mayoría, aún no está listo para usarse más allá de los desarrolladores. Su "
+"millaje variará según la funcionalidad que utilice, pero es probable que "
+"vaya a encontrar problemas con nuestro sistema de transporte que actualmente "
+"tiene un nivel bajo. Actualmente, estamos en proceso de reescribirlo "
+"(Project & quot; Transport Next Generation [TNG] & quot;)"
-#: template/faq.html.j2:24
+#: template/faq.html.j2:136
msgid "Is GNUnet build using distributed ledger technologies?"
msgstr ""
+"¿Se están utilizando tecnologías de contabilidad distribuida para hacer "
+"GNUnet ?"
-#: template/faq.html.j2:26
+#: template/faq.html.j2:138
msgid ""
"A: No. GNUnet is a new network protocol stack for building secure, "
"distributed, and privacy-preserving applications. While a ledger could be "
"built using GNUnet, we currently have no plans in doing so."
msgstr ""
+"R: No. GNUnet es una nueva pila de protocolos de red para crear aplicaciones "
+"seguras, distribuidas y que preservan la privacidad. Si bien se podría "
+"construir un libro de contabilidad usando GNUnet, actualmente no tenemos "
+"planes para hacerlo."
+
+#: template/faq.html.j2:151
+msgid "What can I do with GNUnet?"
+msgstr "¿Qué puedo hacer con GNUnet?"
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
+"do more than just one thing. Naturally, the implementation and documentation "
+"of some of the features that exist are more advanced than others."
+msgstr ""
+"R: GNUnet es una estructura de red de pares, por lo que queremos decir que "
+"es capaz de hacer más que una sola cosa. Naturalmente, la implementación y "
+"documentación de algunas de sus herramientas existentes, son mas avanzadas "
+"que otras."
+
+#: template/faq.html.j2:160
+#, fuzzy
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
+"decentralized and censorship-resistant replacement for DNS and a mechanism "
+"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
+msgstr ""
+"Para usuarios, GNUnet ofrece compartir archivos en el anonimato o no, una "
+"completa sustitución descentralizada con resistencia de censura para DNS ("
+"sistema de nombre de dominio) y un mecanismo de traducción y tunneling (NAT-"
+"PT with DNS-ALG) para el protocolo IPv4-IPv6."
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr "¿Se puede navegar en la WWW en anonimato con GNUnet?"
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We "
+"recommend that you use Tor for anonymous surfing."
+msgstr ""
+"R: En este momento no es posible usar GNUnet para navegar de modo anónimo. "
+"Recomendamos que utilice Tor para hacer búsquedas anónimas."
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr "¿Es posible acceder a GNUnet desde un buscador en anónimo en www?"
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+"R: Actualmente no hay ningún proxy, como el proxy libre de Freenet, para "
+"GNUnet, que lo haga accesible con un buscador. Es posible construir "
+"semejante proxy y todo lo que se necesita saber es el protocolo usado entre "
+"el navegador y el proxy, y una mirada rápida al código en GNUnet para el "
+"intercambio de archivos."
+
+#: template/faq.html.j2:195
+#, fuzzy
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the "
+"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
+"that integrates most of the other GUIs in one window. One exception is "
+"gnunet-setup, which must still be run separately at this time (as setup "
+"requires the peer to be stopped)."
+msgstr ""
+"R: En realidad, existen algunas interfaces gráficas de usuario para "
+"diferentes funciones. gnunet-setup es para configurar GNUnet, y gnunet-fs-"
+"gtk es para compartir archivos. Hay algunas otras GUI de gnunet-XXX-gtk de "
+"menor importancia. Ten en cuenta que para obtener la GUI, debes instalar el "
+"paquete gnunet-gtk, que es una descarga separada. gnunet-gtk es una GUI meta "
+"que integra la mayoría de las otras GUI en una ventana. Una excepción es "
+"gnunet-setup, que todavía debe ejecutarse por separado (ya que la "
+"instalación requiere que se detenga)."
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr "¿Sobre qué sistemas operativos se ejecuta GNUnet?"
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
+"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
+"FreeBSD and macOS. We have reports of working versions on many other GNU/"
+"Linux distributions; in the past we had reports of working versions on "
+"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
+"so if you cannot get GNUnet to work on those systems please let us know."
+msgstr ""
+"R: GNUnet se está desarrollando y probando principalmente en Debian GNU/"
+"Linux. Además, regularmente construimos y probamos GNUnet en Fedora, Ubuntu, "
+"Arch, FreeBSD y macOS. Tenemos informes de versiones que funcionan en muchas "
+"otras distribuciones GNU/Linux; en el pasado tuvimos informes de versiones "
+"de trabajo en NetBSD, OpenBSD y Solaris. Sin embargo, no todos esos informes "
+"son recientes, por lo que si no puedes hacer que GNUnet funcione en esos "
+"sistemas, háznoslo saber."
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr "¿Quién administra la zona raíz de GNS?"
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a default "
+"configuration of top-level domains. The governance of this default "
+"configuration is not yet established. In any case, the user will be able to "
+"modify this configuration at will. We expect normal users to have no need to "
+"edit their own GNS zone(s) unless they host services themselves."
+msgstr ""
+"R: Respuesta corta: tú. La respuesta larga es que GNUnet se enviará con una "
+"configuración predeterminada de dominios de nivel superior. La gobernanza de "
+"esta configuración predeterminada aún no está establecida. En cualquier "
+"caso, el usuario podrá modificar esta configuración a su antojo. Esperamos "
+"que los usuarios promedio no tengan necesidad de editar sus propias zonas "
+"GNS a menos que ellos mismos alojen los servicios."
+
+#: template/faq.html.j2:241
+#, fuzzy
+msgid "Where is the per-user GNS database kept?"
+msgstr "¿Dónde se guarda la base de datos GNS por usuario?"
+
+#: template/faq.html.j2:243
+#, fuzzy
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet peer. "
+"Now, a user may run multiple GNUnet peers, in which case the database could "
+"be kept at each peer (however, we don't have code for convenient "
+"replication). Similarly, multiple GNUnet peers can share one instance of the "
+"database --- the "gnunet-service-namestore" can be accessed from "
+"remote (via TCP). The actual data can be stored in a Postgres database, for "
+"which various replication options are again applicable. Ultimately, there "
+"are many options for how users can store (and secure) their GNS database."
+msgstr ""
+"R: La respuesta corta es que la base de datos se guarda en el par GNUnet del "
+"usuario. Ahora, un usuario puede ejecutar múltiples pares GNUnet, en cuyo "
+"caso la base de datos podría mantenerse en cada par (sin embargo, no tenemos "
+"código para una replicación conveniente). De manera similar, varios pares de "
+"GNUnet pueden compartir una instancia de la base de datos: el & quot; gnunet-"
+"service-namestore & quot; se puede acceder de forma remota (a través de TCP)"
+". Los datos reales se pueden almacenar en una base de datos de Postgres, "
+"para lo cual se aplican nuevamente varias opciones de replicación. En última "
+"instancia, existen muchas opciones sobre cómo los usuarios pueden almacenar ("
+"y proteger) su base de datos GNS."
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+"¿Cuál es el tamaño promedio esperado de una base de datos de nombres GNS?"
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases "
+"will only grow to a few tens of thousands of entries, small enough to fit "
+"even on mobile devices."
+msgstr ""
+"R: Muy pequeña. Basándonos en nuestro estudio de usuarios, donde revisamos "
+"historiales de buscador y el número de dominios visitados, esperamos que las "
+"bases de datos GNS crezcan hasta decenas de miles de entradas, lo "
+"suficientemente pequeñas para caber incluso en dispositivos móviles."
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr "¿GNS es resistente a los ataque de DNS utilizados por los E.E. U.U.?"
+
+#: template/faq.html.j2:272
+#, fuzzy
+msgid ""
+"A: We believe so, as there is no entity that any government could force to "
+"change the mapping for a name except for each individual user (and then the "
+"changes would only apply to the names that this user is the authority for). "
+"So if everyone used GNS, the only practical attack of a government would be "
+"to force the operator of a server to change the GNS records for his server "
+"to point elsewhere. However, if the owner of the private key for a zone is "
+"unavailable for enforcement, the respective zone cannot be changed and any "
+"other zone delegating to this zone will achieve proper resolution."
+msgstr ""
+"R: Creemos que sí, ya que no existe una entidad a la que ningún gobierno "
+"pueda obligar a cambiar el mapeo de un nombre excepto para cada usuario "
+"individual (y luego los cambios solo se aplicarían a los nombres para los "
+"que este usuario es la autoridad). Así que si todo el mundo usase GNS, el "
+"único ataque practico del gobierno seria forzar el operador de un servidor "
+"para cambiar el historial de GNS por un servidor que lleve a otra parte. Sin "
+"embargo, si el propietario de la clave privada para una zona es incapaz de "
+"esforzarla, la respectiva zona no puede ser cambiada y cualquier otra zona "
+"delegada a esta, alcanzara adecuada resolución."
+
+#: template/faq.html.j2:286
+msgid "How does GNS compare to other name systems"
+msgstr "¿Cómo se compara GNS a otros sistemas de nombres de dominio?"
+
+#: template/faq.html.j2:288
+msgid ""
+"A: A scientific paper on this topic <a href=\"https://grothoff.org/christian/";
+"ns2018.pdf\">has been published </a> and below is a table from the "
+"publication. For detailed descriptions please refer to the paper."
+msgstr ""
+"R: <a href=\"https://grothoff.org/christian/ns2018.pdf\";>Ha sido publicado </"
+"a> un documento científico sobre este tema y mas abajo hay una tabla de esta "
+"publicación. Para una descripción mas detallada por favor diríjanse al "
+"documento."
+
+#: template/faq.html.j2:392
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr "¿Cuál es la diferencia entre GNS y CoDoNS?"
+
+#: template/faq.html.j2:394
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
+"there are still registrars that determine who owns a name. <br><br> With "
+"GNS, we decentralize the database and also decentralize the responsibility "
+"for naming: each user runs his own personal root zone and is thus in "
+"complete control of the names he uses. GNS also has many additional features "
+"(to keep names short and enable migration) which don't even make sense in "
+"the context of CoDoNS."
+msgstr ""
+"R: CoDoNS descentraliza la base de datos de DNS (usando DHT) pero preserva "
+"la jerarquía de DNS. Con CoDoNS, IANA/ICANN esta aun al mando, y también hay "
+"registradores que determinan quien posee el nombre.<br><br> Con GNS, "
+"centralizamos la base de datos y también descentralizamos la responsabilidad "
+"para nombrar; cada usuario opera su zona raíz personal y tiene por lo tanto "
+"tiene control absoluto sobre los nombres que usa. GNS además tiene muchas "
+"cualidades adicionales (para mantener nombres cortos y habilitar migraciones)"
+" lo cual en el contexto de CoDoNS ni si quiere tiene sentido."
+
+#: template/faq.html.j2:410
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr "¿Cuál es la diferencia entre GNS y SocialDNS?"
+
+#: template/faq.html.j2:412
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared via "
+"delegation, and thus mappings will only change if the user responsible for "
+"the name (the authority) manually changes the record."
+msgstr ""
+"R: Como GNS, SocialDNS permite crear a cada usuario un mapeado DNS. Sin "
+"embargo, con SocialDNS los mapeados son compartidos mediante una red social "
+"y sujetos a clasificaciones. Así como las relaciones evolucionan, los "
+"nombres pueden de este modo cambiar de maneras insospechadas. <br><br> Con "
+"GNS, los nombres son primeramente compartidos mediante delegación, y por "
+"ello los mapeados solo cambiaran si el usuario responsable del nombre (la "
+"autoridad) cambia manualmente el historial."
+
+#: template/faq.html.j2:426
+msgid "What is the difference between GNS and ODDNS?"
+msgstr "¿Cuál es la diferencia entre GNS y ODDNS?"
+
+#: template/faq.html.j2:428
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+"R: ODDNS (DNS abierta y descentralizada en español) es primeramente diseñado "
+"para bordear la zona raíz de DNS y los registros de TLD (como los de \".com\""
+" y\".org\" ). En vez de usar esos, se espera que cada usuario mantenga una "
+"base de datos (segundo nivel) de dominios (como \"gnu.org\") y la dirección "
+"IP de los respectivos nombres. La resolución fallara si los servidores de "
+"nombres cambian las IP."
+
+#: template/faq.html.j2:439
+msgid "What is the difference between GNS and Handshake?"
+msgstr "¿Cuál es la diferencia entre GNS y Handshake?"
+
+#: template/faq.html.j2:441
+msgid ""
+"A: Handshake is a blockchain-based method for root zone governance. Hence, "
+"it does not address the name resolution process itself but delegates "
+"resolution into DNS after the initial TLD resolution. Not taking "
+"sustainablility considerations into account, handshake could be used as an "
+"additional supporting GNS root zone governance model but we currently do not "
+"have such plans in mind."
+msgstr ""
+"R: Handshake es un método de cadena de bloques para la gobernanza de la zona "
+"raíz. Por lo tanto, no gestiona el proceso de resolución del nombre en si "
+"misma pero delega la resolución en la DNS después de una resolución TLD "
+"inicial. No toma consideraciones sostenibles en consideración, Handshake "
+"podria ser usado como un modelo de gobernanza de la zona raíz de GNS de "
+"apoyo adicional, pero actualmente no tenemos tales planes en mente."
+
+#: template/faq.html.j2:453
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr "¿Cuál es la diferencia entre GNS y TrickleDNS?"
+
+#: template/faq.html.j2:455
+#, fuzzy
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks on "
+"DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from "
+"the DNS hierarchy."
+msgstr ""
+"R: TrickleDNS envía registros DNS ("críticos") entre los "
+"resolutores de DNS de los dominios participantes para proporcionar "una "
+"mejor disponibilidad, tiempos de resolución de consultas más bajos y una "
+"propagación de actualizaciones más rápida". Por lo tanto, TrickleDNS se "
+"centra en derrotar los ataques a la disponibilidad (y el rendimiento) de la "
+"propagación de registros en DNS, por ejemplo, a través de ataques DDoS en "
+"servidores raíz de DNS. Por lo tanto, TrickleDNS se preocupa por cómo "
+"garantizar la distribución de registros autorizados, y la autoridad sigue "
+"derivando de la jerarquía del DNS."
+
+#: template/faq.html.j2:468
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the style "
+"of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: For security, it is well known that an initial trust path between the two "
+"parties must exist. However, for applications where this is not required, "
+"weaker mechanisms can be used. For example, we have implemented a first-come-"
+"first-served (FCFS) authority which allows arbitrary users to register "
+"arbitrary names. The key of this authority is included with every GNUnet "
+"installation. Thus, any name registered with FCFS is in fact global and "
+"requires no further introduction. However, the security of these names "
+"depends entirely on the trustworthiness of the FCFS authority. The authority "
+"can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name in "
+"GNS?"
+msgstr ""
+
+#: template/faq.html.j2:487
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "legitimate" "
+"domain owner. Any user can claim any name (as his preferred name or ""
+"pseudonym") in his NICK record. Similarly, all other users can choose "
+"to ignore this preference and use a name of their choice (or even assign no "
+"name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:498
+msgid ""
+"Did you consider the privacy implications of making your personal GNS zone "
+"visible?"
+msgstr ""
+
+#: template/faq.html.j2:500
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not set. "
+"Thus, users have full control over what information about their zones is "
+"made public."
+msgstr ""
+
+#: template/faq.html.j2:510
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary because "
+"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
+"of virtual hosting. However, LEHOs are also useful to help with X.509 "
+"certificate validation (as they specify for which legacy hostname the "
+"certificate should be valid). Also, even with IPv6 fully deployed and ""
+"infinite" IP addresses being available, we're not sure that virtual "
+"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
+"become commonplace, GNS should work with today's networks."
+msgstr ""
+
+#: template/faq.html.j2:526
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:528
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. As "
+"trust relationships evolve, mappings would change their meaning as they "
+"cross each others thresholds. We decided that the resulting unpredictability "
+"of the resolution process was not acceptable. Furthermore, trust and "
+"consensus might be easy to manipulate by adversaries."
+msgstr ""
+
+#: template/faq.html.j2:539
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:541
+msgid ""
+"A: The owner of a private key can create a revocation message. This one can "
+"then be flooded throughout the overlay network, creating a copy at all "
+"peers. Before using a public key, peers check if that key has been revoked. "
+"All names that involve delegation via a revoked zone will then fail to "
+"resolve. Peers always automatically check for the existence of a revocation "
+"message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:553
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:555
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:569
+msgid ""
+"How can a GNS zone maintain several name servers, e.g. for load balancing?"
+msgstr ""
+
+#: template/faq.html.j2:571
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share "
+"the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:584
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:586
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names are "
+"not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on your "
+"application, HTTPS may not be worth the cost. However, for users that are "
+"experiencing censorship (or are concerned about it), giving up globally "
+"unique names may very well be worth the cost. After all, what is a ""
+"globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:600
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:602
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by IANA/ICANN. "
+"This centralization creates vulnerabilities. For example, the US government "
+"was able to reassign the management of the country-TLDs of Afganistan and "
+"Iraq during the wars at the beginning of the 21st century."
+msgstr ""
+
+#: template/faq.html.j2:613
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:615
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
+"so blocking a particular IP address causes much more collateral damage than "
+"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
+"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
+"censorship resistant naming system. Accessing Tor's ".onion" "
+"namespace currently requires users to use unmemorable cryptographic "
+"identifiers. With nicer names, Tor and tor2web-like services would be even "
+"easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:634
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:636
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can use "
+"GNS to perform name resolution as well as any normal user. Naturally, while "
+"we typically expect normal users to install custom software for name "
+"resolution, this is unlikely to work for search engines today. However, the "
+"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
+"they can still index GNS resources. However, as using DNS2GNS gateways "
+"breaks the cryptographic chain of trust, legacy search engines will "
+"obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:650
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:652
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was designed "
+"to interoperate with DNS as much as possible, and to also work as much as "
+"possible with the existing Web infrastructure. UIA is not at all concerned "
+"about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:665
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:667
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you know "
+"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
+"and can thus decide how much you trust the result. Naturally, the trusted-"
+"computing base (TCB) can become arbitrarily large this way --- however, "
+"given the name length restriction, for an individual name it is always less "
+"than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:679
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part of "
+"the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:681
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects the "
+""_Service._Proto" syntax, converts "Service" to the "
+"corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when the "
+"result is presented, GNS looks for the GNS-specific "BOX" record "
+"type. A BOX record is a record that contains another record (such as SRV or "
+"TLSA records) and adds a service and protocol number (and the original boxed "
+"record type) to it."
+msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:697
msgid ""
"I receive many "WARNING Calculated flow delay for X at Y for Z". "
"Should I worry?"
msgstr ""
+"Recibo muchas " WARNING Retardo de flujo calculado para X en Y para "
+"Z". ¿Debería preocuparme?"
-#: template/faq.html.j2:37
+#: template/faq.html.j2:699
msgid ""
"A: Right now, this is expected and a known cause for high latency in GNUnet. "
"We have started a major rewrite to address this and other problems, but "
"until the Transport Next Generation (TNG) is ready, these warnings are "
"expected."
msgstr ""
+"R: En este momento, esto es esperado y es una causa debido a la alta "
+"latencia en GNUnet. Hemos comenzado una reescritura importante para abordar "
+"este y otros problemas, pero hasta que el Transport Next Generation (TNG) "
+"esté listo, estas advertencias seguirán ocurriendo."
-#: template/faq.html.j2:46
-msgid "Is there a graphical user interface?"
+#: template/faq.html.j2:708
+msgid "Error opening `/dev/net/tun': No such file or directory?"
msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:710
msgid ""
-"A: gnunet-gtk is a separate download. The package contains various GTK+ "
-"based graphical interfaces, including a graphical tool for configuration."
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:722
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
+"dns)?"
+msgstr ""
+
+#: template/faq.html.j2:724
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check if "
+"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:736
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:738
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if "
+"your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:746
+msgid ""
+"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:748
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if you "
+"compiled GNUnet the normal way and/or used a binary package, that is highly "
+"unlikely. The more common cause is that you installed GNUnet to a directory "
+"that your linker does not search. There are several ways to fix this that "
+"are described below. If you are 'root' and you installed to a system folder "
+"(such as /usr/local), you want to add the libraries to the system-wide "
+"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
+"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
+"similar path, you obviously have to change \"/usr/local\" accordingly. If "
+"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
+"$USER/\", then you can explicitly tell your linker to search a particular "
+"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
+"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
+"you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:774
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the \"$\") "
+"to your .bashrc or .profile file. You will have to logout and login again to "
+"have this new profile be applied to all shells (including your desktop "
+"environment)."
+msgstr ""
+
+#: template/faq.html.j2:781
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:783
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
+"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
+"always refer to harmless events that require no action. For example, GNUnet "
+"may use an INFO message to indicate that it is currently performing an "
+"expensive operation that will take some time. GNUnet will also use INFO "
+"messages to display information about important configuration values."
+msgstr ""
+
+#: template/faq.html.j2:799
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:801
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
+"P2P networks, GNUnet was designed with security in mind as the highest "
+"priority. We intend on producing a network with comprehensive security "
+"features. Many other P2P networks are open to a wide variety of attacks, and "
+"users have little privacy. GNUnet is also Free Software and thus the source "
+"code is available, so you do not have to worry about being spied upon by the "
+"software. The following table summarises the main differences between GNUnet "
+"and other systems. The information is accurate to the best of our knowledge. "
+"The comparison is difficult since there are sometimes differences between "
+"various implementations of (almost) the same protocol. In general, we pick a "
+"free implementation as the reference implementation since it is possible to "
+"inspect the free code. Also, all of these systems are changing over time and "
+"thus the data below may not be up-to-date. If you find any flaws, please let "
+"us know. Finally, the table is not saying terribly much (it is hard to "
+"compare these systems this briefly), so if you want the real differences, "
+"read the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:915
+msgid ""
+"Another important point of reference are the various anonymous peer-to-peer "
+"networks. Here, there are differences in terms of application domain and how "
+"specifically anonymity is achieved. Anonymous routing is a hard research "
+"topic, so for a superficial comparisson like this one we focus on the "
+"latency. Another important factor is the programming language. Type-safe "
+"languages may offer certain security benefits; however, this may come at the "
+"cost of significant increases in resource consumption which in turn may "
+"reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:928
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:930
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of the "
+"same techniques used to generate reasonable passwords to defend against such "
+"an attack. In any event, we are not trying to hide content; thus, unless the "
+"user is trying to insert information into the network that can only be "
+"shared with a small group of people, there is no real reason to try to "
+"obfuscate the content by choosing a difficult keyword anyway."
+msgstr ""
+
+#: template/faq.html.j2:944
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:946
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all "
+"users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell which "
+"of the peers in the group originated the message. In other words, it should "
+"be difficult to impossible for an adversary to distinguish between the "
+"originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:958
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:960
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
+"its public key) and has a number of addresses it is reachable by (may have "
+"no addresses, for instance when it's behind a NAT). You specify bandwidth "
+"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
+"(how large your on-disk block storage is) . Your node will then proceed to "
+"connect to other nodes, becoming part of the network."
+msgstr ""
+
+#: template/faq.html.j2:975
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:977
+msgid ""
+"A: First, you need to register an account with our weblate system. Please "
+"send an e-mail with the desired target language to translators@gnunet.org or "
+"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
+"sufficient permissions will then grant you access. Naturally, any abuse will "
+"result in the loss of permissions."
+msgstr ""
+
+#: template/faq.html.j2:989
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:991
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly implement. "
+"The best way to actually get a new feature implemented is to do it yourself "
+"--- and to then send us a patch."
msgstr ""
#: template/glossary.html.j2:12
msgid "Ego"
-msgstr ""
+msgstr "El Ego"
#: template/glossary.html.j2:14
msgid ""
@@ -1049,10 +1989,18 @@ msgid ""
"not distinguish between them). We simply sometimes use the term \"ego\" to "
"stress that you can have more than one."
msgstr ""
+"Usamos el término \"Ego\" para referirnos al hecho de que los usuarios de "
+"GNUnet pueden tener múltiples identidades no vinculadas, en el sentido de "
+"alter egos. La capacidad de tener más de una identidad es importante, ya que "
+"es posible que deseemos mantener nuestros egos separados por ejemplo el de "
+"negocios del político o romántico. <br> Los egos en GNUnet son técnicamente "
+"equivalentes a las identidades (y el código no los distingue entre ellos). A "
+"veces simplemente usamos el término \"ego\" para enfatizar que puedes tener "
+"más de uno."
#: template/glossary.html.j2:27
msgid "Identity"
-msgstr ""
+msgstr "Identidad"
#: template/glossary.html.j2:29
msgid ""
@@ -1069,10 +2017,24 @@ msgid ""
"prove that they are studying. Students may keep their (certified) student "
"identity separate from other egos that they use for other activities in life."
msgstr ""
+"En GNUnet, los usuarios se identifican mediante una clave pública, y esa "
+"clave pública a menudo se denomina como la \"Identidad\" del usuario. Sin "
+"embargo, el concepto no es tan draconiano como suele serlo en la vida real, "
+"donde muchos se ven obligados a tener un nombre, un pasaporte y un número de "
+"identificación único. <br> Siempre y cuando las identidades en GNUnet sean "
+"simplemente claves públicas, los usuarios son libres de crear cualquier "
+"número de identidades, y nombramos a esos egos para enfatizar la diferencia. "
+"Aunque los usuarios pueden crear tales egos libremente, es posible tener un "
+"ego certificado por alguna autoridad de certificación, lo que se asemeja más "
+"al concepto tradicional de identidad. <br> Por ejemplo, una universidad "
+"puede certificar las identidades de sus estudiantes de manera que puedan "
+"demostrar que están estudiando. Los estudiantes pueden mantener su identidad "
+"de estudiante (certificada) separada de otros egos que usan para otras "
+"actividades en su vida."
#: template/glossary.html.j2:50
msgid "Pseudonym"
-msgstr ""
+msgstr "Pseudónimo"
#: template/glossary.html.j2:52
msgid ""
@@ -1084,10 +2046,17 @@ msgid ""
"neutral element on the elliptic curve) or a throw-away pseudonym that is "
"only used once."
msgstr ""
+"Un pseudónimo es un ego con el objetivo de no ser relacionado con el nombre "
+"propio. Los usuarios de GNUnet pueden crear varios egos, por ende varios "
+"pseudónimos. <br> El uso repetitivo del mismo pseudónimo puede relacionarse "
+"por definición, ya que se relacionan por la misma clave pública. La "
+"anonimidad requiere el uso de pseudónimos \"anónimos\" especiales (para "
+"GNUnet, es el elemento neutral de la curva elíptica) o un pseudónimo "
+"desechable de único uso."
#: template/glossary.html.j2:71
msgid "Namespaces"
-msgstr ""
+msgstr "Espacio de nombres"
#: template/glossary.html.j2:73
msgid ""
@@ -1101,10 +2070,20 @@ msgid ""
"which despite its name may not be public knowledge and is never disclosed by "
"the GNS protocol itself."
msgstr ""
+"El sistema de nombres GNU permite que cada identidad asocie de forma segura "
+"y privada cualquier numero de pares valor-etiqueta con un ego. El valor se "
+"denomina conjunto de registros siendo la terminología del sistema de nombres "
+"de dominio (DNS). El mapeo de etiquetas a conjuntos de registros para un ego "
+"dado se llama espacio de nombres. Si los registros se hacen públicos y por "
+"lo tanto se publican es posible que otros usuarios busquen el registro dada "
+"la clave publica y la etiqueta del ego. Aquí no solo la etiqueta puede "
+"actuar como una frase de contraseña, sino también la clave publica. que a "
+"pesar de su nombre puede no ser de conocimientos publico y nunca es revelado "
+"por el propio protocolo."
#: template/glossary.html.j2:89
msgid "Peer"
-msgstr ""
+msgstr "Par"
#: template/glossary.html.j2:91
msgid ""
@@ -1136,14 +2115,16 @@ msgid ""
"Name System (GNS), a secure, decentralized name system built on top of "
"GNUnet."
msgstr ""
+"El Sistema de Nombres de Dominio hoy permite ataques a la ampliación de "
+"tráfico, censura (p.e. China), vigilancia masiva (MORECOWBELL) y guerra "
+"cibernética ofensiva (QUANTUMDNS).<br/> Lastimosamente, soluciones rápidas "
+"como DoT, DoH, DNSSEC, DPRIVE, y similares no lo arreglarán. Es por esto que "
+"construimos el Sistema de Nombres GNU (GNS), un sistema de nombres seguro y "
+"descentralizado construido sobre GNUnet."
#: template/gns.html.j2:28
msgid "Overview"
-msgstr ""
-
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
+msgstr "visión general"
#: template/gns.html.j2:39
msgid ""
@@ -1153,10 +2134,16 @@ msgid ""
"<li>Censorship resistance</li> <li>Query privacy</li> <li>Secure name "
"resolution</li> <li>Compatibility with DNS</li>"
msgstr ""
+"El Sistema de Nombres GNU (GNS) es un sistema de nombres seguro y "
+"descentralizado. Permite a sus usuarios registrar nombres como Dominios de "
+"Nivel Superior (TLD) y resolver otros espacios de nombres dentro de sus TLD. "
+"<br/> El diseño de GNS ofrece: <ul> <li>Resistencia a la censura </li> "
+"<li>Privacidad en las búsquedas</li> <li>Resolución de nombre segura </li> "
+"<li> Compatibilidad con DNS</li>"
#: template/gns.html.j2:52
msgid "Resources"
-msgstr ""
+msgstr "Recursos"
#: template/gnurl.html.j2:21
msgid ""
@@ -1171,6 +2158,9 @@ msgid ""
"Our main usecase is for GNUnet and Taler, but it might be usable for others, "
"hence we're releasing the code to the general public."
msgstr ""
+"Nuestro principal caso de uso es para GNUnet y Taler, pero puede ser "
+"utilizado por otros, por eso notros estamos soltando el código para el "
+"público en general."
#: template/gnurl.html.j2:37
msgid ""
@@ -1180,15 +2170,15 @@ msgid ""
msgstr ""
#: template/gnurl.html.j2:48
-#, fuzzy
-#| msgid "About"
msgid "About gnurl"
-msgstr "Sobre"
+msgstr "Acerca de gnurl"
#: template/gnurl.html.j2:50
msgid ""
"Large parts of the following 6 paragraphs are old and need to be rewritten."
msgstr ""
+"Grandes partes de los siguientes 6 párrafos son antiguos y necesitan "
+"reescritura."
#: template/gnurl.html.j2:62
msgid ""
@@ -1263,7 +2253,7 @@ msgstr ""
#: template/gnurl.html.j2:142
msgid "Using libgnurl"
-msgstr ""
+msgstr "Usar libgnurl"
#: template/gnurl.html.j2:144
msgid ""
@@ -1372,11 +2362,11 @@ msgstr ""
#: template/gnurl.html.j2:321
msgid "Now you can either run"
-msgstr ""
+msgstr "Ahora puede reproducir"
#: template/gnurl.html.j2:331
msgid "directly (and read configure-gnurl before you do so) or invoke"
-msgstr ""
+msgstr "directamente (lea configure-gnurl antes de hacerlo) o invocar"
#: template/gnurl.html.j2:341
msgid ""
@@ -1386,15 +2376,15 @@ msgstr ""
#: template/gnurl.html.j2:346
msgid "Now run"
-msgstr ""
+msgstr "Ahora reproduzca"
#: template/gnurl.html.j2:356
msgid "(this is optional)"
-msgstr ""
+msgstr "(esto es opcional)"
#: template/gnurl.html.j2:365
msgid "and you are done."
-msgstr ""
+msgstr "y eso es todo."
#: template/gnurl.html.j2:369
msgid "Building from a tagged git commit"
@@ -1408,7 +2398,7 @@ msgstr ""
#: template/gnurl.html.j2:382
msgid "Reporting Bugs"
-msgstr ""
+msgstr "Reporte de Bugs"
#: template/gnurl.html.j2:384
msgid ""
@@ -1416,10 +2406,14 @@ msgid ""
"\">bugs.gnunet.org</a>. Alternatively you can use our bug mailinglist, but "
"we prefer to track bugs on the bugtracker."
msgstr ""
+"Usted puede reportar bugs o problemas en nuestro sistema de seguimiento de "
+"bugs: <a href=\"https://bugs.gnunet.org/\";>bugs.gnunet.org</a>. De manera "
+"alternativa, usted puede usar nuestra lista de correos de bug, pero "
+"preferimos seguirlo en el sistema de seguimiento de bugs."
#: template/gnurl.html.j2:395
msgid "Maintainer and Cryptographic signatures"
-msgstr ""
+msgstr "Mantenedor y firmas criptográficas"
#: template/gnurl.html.j2:397
msgid ""
@@ -1429,14 +2423,20 @@ msgid ""
"q=6115012DEA3026F62A98A556D6B570842F7E7F8D\">keys.openpgp.org</a>), with the "
"key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E 7F8D</b>."
msgstr ""
+"gnurl/libgnurl está buscando un nuevo mantenedor. Los lanzamientos tras la "
+"versión 7.69.1 y hasta la versión 7.72.0 se firmaron con la clave OpenPGP "
+"Key <b>0xD6B570842F7E7F8D</b><a href=\"https://keys.openpgp.org/search?q=";
+"6115012DEA3026F62A98A556D6B570842F7E7F8D\">keys.openpgp.org</a>, con la "
+"huella digital de clave pública,<b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 "
+"2F7E 7F8D</b>."
#: template/gsoc-2018-gnunet-webui.html.j2:7
msgid "GSoC 2018: GNUnet WebUI (GNUnet Web-based User Interface)"
-msgstr ""
+msgstr "GSoc 2018: GNUnet WebUI (Interfaz de usuario basada en la web GNUnet)"
#: template/gsoc-2018-gnunet-webui.html.j2:11
msgid "Tue, 08/14/2018 - 07:55, Phil Buschmann"
-msgstr ""
+msgstr "Martes, 14/08/2018 - 07:55, Phil Buschmann"
#: template/gsoc-2018-gnunet-webui.html.j2:18
msgid ""
@@ -1444,6 +2444,9 @@ msgid ""
"Schanzenbach) and I have worked on creating and extending the REST API of "
"GNUnet. Currently, we mirrored the functionality of following commands:"
msgstr ""
+"En el contexto de Google Summer of Code 2018, mi mentor (Martin Schazenbach) "
+"y yo trabajamos en la creación y expansión del REST API de GNUnet. "
+"Actualmente reflejamos la funcionalidad de los siguientes comandos:"
#: template/gsoc-2018-gnunet-webui.html.j2:32
msgid ""
@@ -1451,6 +2454,9 @@ msgid ""
"and the design framework iotaCSS to use the new REST API. The REST API of "
"GNUnet is now documented with Sphinx."
msgstr ""
+"Adicionalmente, desarrollamos un sitio web con el marco de Javascript "
+"Angular 6 y el diseño de marco iotaCSS para usar el nuevo REST API. El REST "
+"API de GNUnet está documentado ahora con Sphinx."
#: template/gsoc-2018-gnunet-webui.html.j2:41
msgid ""
@@ -1461,6 +2467,14 @@ msgid ""
"with GNUnet over a well known tool: their browsers. This addition to the C "
"API and the command line tools may attract new users and developers."
msgstr ""
+"... Cuándo podrá usar las herramientas de línea de comando? Necesitamos "
+"tener en cuenta que todos tienen el derecho a permanecer seguros y privados, "
+"pero no todos se sienten seguros al usar una terminal. El acceso restante "
+"desarrollado a REST a GNUnet APIs además de la nueva aplicación web permite "
+"a los usuarios nuevos interactuar con GNUnet por medio de una herramienta de "
+"amplio conocimiento: sus navegadores. Esta adición a la API C y las "
+"herramientas de línea de comando pueden atraer nuevos usuarios y "
+"desarrolladores."
#: template/gsoc-2018-gnunet-webui.html.j2:54
msgid ""
@@ -1490,6 +2504,8 @@ msgid ""
"Please, give it a try and contact me, if you find any bugs or unintentional "
"features. ;)"
msgstr ""
+"Por favor, pruébelo y contácteme si encuentra bugs o características no "
+"intencionadas. ;)"
#: template/gsoc-2018-gnunet-webui.html.j2:98
msgid ""
@@ -1504,7 +2520,7 @@ msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:111
msgid "Thanks for reading."
-msgstr ""
+msgstr "Gracias por leer."
#: template/gsoc.html.j2:6
msgid "GNUnet's Google Summer of Code projects"
@@ -1515,16 +2531,12 @@ msgid "Ideas 2021"
msgstr ""
#: template/gsoc.html.j2:13 template/gsoc.html.j2:215
-#, fuzzy
-#| msgid "GSoC Projects"
msgid "Past projects"
-msgstr "Projectos de GSoC"
+msgstr "Proyectos pasados"
#: template/gsoc.html.j2:14 template/gsoc.html.j2:596
-#, fuzzy
-#| msgid "GSoC Projects"
msgid "Finished projects"
-msgstr "Projectos de GSoC"
+msgstr "Proyectos finalizados"
#: template/gsoc.html.j2:21
msgid ""
@@ -1534,6 +2546,12 @@ msgid ""
"for 2020 below or any past project which is not yet finished (or even your "
"own idea), please contact us either in IRC or mailing list."
msgstr ""
+"Como projecto GNU, GNUnet ha participado en el Google Summer of Code (GSoC) "
+"por varios años. Esta página enlista todos los proyectos, actuales, pasados "
+"y finalizados. SI quiere participar y aplicar para cualquiera de las ideas "
+"para 2020 a continuación, o cualquier proyecto pasado que aún no haya "
+"finalizado (o incluso una idea suya), por favor contáctenos vía IRC o lista "
+"de correo."
#: template/gsoc.html.j2:34
msgid ""
diff --git a/locale/fr/LC_MESSAGES/messages.po
b/locale/fr/LC_MESSAGES/messages.po
index e9e7597..58c10b3 100644
--- a/locale/fr/LC_MESSAGES/messages.po
+++ b/locale/fr/LC_MESSAGES/messages.po
@@ -3,181 +3,189 @@
# This file is distributed under the same license as the PROJECT project.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2017.
#
-#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
"POT-Creation-Date: 2021-03-03 21:41+0100\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"
+"PO-Revision-Date: 2021-03-15 15:12+0000\n"
+"Last-Translator: Marianne Le Guennec <marianne.leguennec@gmail.com>\n"
+"Language-Team: French <http://weblate.taler.net/projects/gnunet/website/fr/>"
+"\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=n > 1;\n"
+"X-Generator: Weblate 4.4.2\n"
"Generated-By: Babel 2.4.0\n"
#: common/base.j2:5 common/news.j2:5
msgid "GNUnet"
-msgstr ""
+msgstr "GNUnet"
#: common/base.j2:6 common/news.j2:6
msgid "GNU's framework for secure p2p networking"
-msgstr ""
+msgstr "Système GNU pour un réseau p2p sécurisé"
#: common/footer.j2.inc:7
msgid "Contact"
-msgstr ""
+msgstr "Contact"
#: common/footer.j2.inc:8 common/navigation.j2.inc:49
msgid "GNUnet e.V."
-msgstr ""
+msgstr "GNUnet e.V."
#: common/footer.j2.inc:9 template/about.html.j2:6
msgid "About GNUnet"
-msgstr ""
+msgstr "À propos de GNUnet"
#: common/footer.j2.inc:14 common/navigation.j2.inc:64
msgid "Bug Tracker"
-msgstr ""
+msgstr "Système de suivi des bugs"
#: common/footer.j2.inc:19 template/copyright.html.j2:6
msgid "Copyright Assignment"
-msgstr ""
+msgstr "Cession de droits d'auteur"
#: common/footer.j2.inc:20 common/navigation.j2.inc:90
#: template/developers.html.j2:24
msgid "Bibliography"
-msgstr ""
+msgstr "Bibliographie"
#: common/footer.j2.inc:31
msgid "Source code of this site."
-msgstr ""
+msgstr "Code source de ce site."
#: common/footer.j2.inc:32
msgid "Report issues with this website."
-msgstr ""
+msgstr "Signaler des problèmes sur ce site."
#: common/navigation.j2.inc:38
msgid "About"
-msgstr ""
+msgstr "À propos"
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
-msgstr ""
+msgstr "Actualités"
#: common/navigation.j2.inc:40 template/index.html.j2:289
msgid "Applications"
-msgstr ""
+msgstr "Fonctions"
#: common/navigation.j2.inc:44
msgid "Community"
-msgstr ""
+msgstr "Communauté"
#: common/navigation.j2.inc:47 template/index.html.j2:292
msgid "Engage"
-msgstr ""
+msgstr "Participer"
#: common/navigation.j2.inc:48
msgid "GSoC Projects"
-msgstr ""
+msgstr "Projets GSoC"
#: common/navigation.j2.inc:50
msgid "Copyright for Contributors"
-msgstr ""
+msgstr "Droits d'auteur pour les contributeurs"
#: common/navigation.j2.inc:51
msgid "IRC Archive"
-msgstr ""
+msgstr "Archive IRC"
#: common/navigation.j2.inc:58
msgid "Development"
-msgstr ""
+msgstr "Développement"
#: common/navigation.j2.inc:61
msgid "System Architecture"
-msgstr ""
+msgstr "Infrastructure Logiciel"
#: common/navigation.j2.inc:63 template/roadmap.html.j2:6
msgid "Roadmap"
-msgstr ""
+msgstr "Feuille de route"
#: common/navigation.j2.inc:65 template/gnurl.html.j2:186
msgid "Source Code"
-msgstr ""
+msgstr "Code Source"
#: common/navigation.j2.inc:66
msgid "Source Code Documentation"
-msgstr ""
+msgstr "Documents Code Source"
#: common/navigation.j2.inc:67
msgid "Continuous Integration"
-msgstr ""
+msgstr "Intégration continue"
#: common/navigation.j2.inc:68
msgid "Development Tutorial"
-msgstr ""
+msgstr "Tutoriel de Développement"
#: common/navigation.j2.inc:79
msgid "Documentation"
-msgstr ""
+msgstr "Documents"
#: common/navigation.j2.inc:82 template/install.html.j2:6
msgid "Install"
-msgstr ""
+msgstr "Installer"
#: common/navigation.j2.inc:83 template/install-on-openwrt.html.j2:76
msgid "Use"
-msgstr ""
+msgstr "Utiliser"
#: common/navigation.j2.inc:84
msgid "Videos"
-msgstr ""
+msgstr "Vidéos"
#: common/navigation.j2.inc:85 template/glossary.html.j2:6
msgid "Glossary"
-msgstr ""
+msgstr "Glossaire"
#: common/navigation.j2.inc:86
msgid "Handbook"
-msgstr ""
+msgstr "Manuel"
#: common/navigation.j2.inc:87 template/livingstandards.html.j2:8
msgid "Living Standards"
-msgstr ""
+msgstr "Niveau de Vie"
#: common/navigation.j2.inc:88
msgid "REST API"
-msgstr ""
+msgstr "API REST"
#: common/navigation.j2.inc:89
msgid "FAQ"
-msgstr ""
+msgstr "F.A.Q"
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
msgstr ""
+"Publications d'actualités de changements liés à GNUnet comme des parutions "
+"et des évènements"
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
-msgstr ""
+msgstr "Abonnez-vous à notre Flux RSS"
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
-msgstr ""
+msgstr "Plus de détails"
#: news/index.html.j2:45
msgid "News archives:"
-msgstr ""
+msgstr "Archives des actualités :"
#: template/about.html.j2:11
msgid "What is GNUnet?"
-msgstr ""
+msgstr "Qu'est-ce que GNUnet ?"
#: template/about.html.j2:13
msgid ""
@@ -779,11 +787,131 @@ msgid ""
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
-#: template/faq.html.j2:12
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
+msgstr ""
+
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
+msgstr ""
+
+#: template/faq.html.j2:15 template/faq.html.j2:695
+msgid "Error messages"
+msgstr ""
+
+#: template/faq.html.j2:16 template/faq.html.j2:797
+msgid "File-sharing"
+msgstr ""
+
+#: template/faq.html.j2:17 template/faq.html.j2:973
+msgid "Contributing"
+msgstr ""
+
+#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr ""
+
+#: template/faq.html.j2:28
+msgid ""
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
+"the #gnunet IRC on irc.freenode.net."
+msgstr ""
+
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
+msgstr ""
+
+#: template/faq.html.j2:38
+msgid ""
+"A: The general answer is, when it is ready. A better answer may be: earlier "
+"if you contribute (test, debug, code, document). Every release will be "
+"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://";
+"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
+"the RSS feed of this site to automatically receive a notification."
+msgstr ""
+
+#: template/faq.html.j2:49
+msgid "Is the code free?"
+msgstr ""
+
+#: template/faq.html.j2:51
+msgid ""
+"A: GNUnet is free software, available under the <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
+msgstr ""
+
+#: template/faq.html.j2:58
+msgid "Are there any known bugs?"
+msgstr ""
+
+#: template/faq.html.j2:60
+msgid ""
+"A: We track the list of currently known bugs in the <a href=\"https://bugs.";
+"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
+"directly to developers or the developer mailing list. This is discouraged "
+"since developers often do not have the time to feed these bugs back into the "
+"Mantis database. Please report bugs directly to the bug tracking system. If "
+"you believe a bug is sensitive, you can set its view status to private (this "
+"should be the exception)."
+msgstr ""
+
+#: template/faq.html.j2:73 template/faq.html.j2:193
+msgid "Is there a graphical user interface?"
+msgstr ""
+
+#: template/faq.html.j2:75
+msgid ""
+"A: gnunet-gtk is a separate download. The package contains various GTK+ "
+"based graphical interfaces, including a graphical tool for configuration."
+msgstr ""
+
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr ""
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called ""
+"proof-of-work" which is used to convince the network that your peer is "
+"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
+"on the network size estimator). The calculation is expected to take a few "
+"days, depending on how fast your CPU is. If the CPU load is creating a "
+"problem for you, you can set the value "WORKDELAY" in the ""
+"nse" section of your configuration file to a higher value. The default "
+"is "5 ms"."
+msgstr ""
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr ""
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
+"connections and, with the Tor Browser Bundle, for the Web in particular. "
+"GNUnet does not really have one focus; our theme is secure decentralized "
+"networking, but that is too broad to be called a focus."
+msgstr ""
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr ""
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost no "
+"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
+"using onion (or garlic) routing as the basis for various (anonymized) "
+"applications. I2P is largely used via a Web frontend."
+msgstr ""
+
+#: template/faq.html.j2:124
msgid "Is GNUnet ready for use on production systems?"
msgstr ""
-#: template/faq.html.j2:14
+#: template/faq.html.j2:126
msgid ""
"A: GNUnet is still undergoing major development. It is largely not yet ready "
"for usage beyond developers. Your mileage will vary depending on the "
@@ -792,24 +920,465 @@ msgid ""
"rewriting it (Project "Transport Next Generation [TNG]")"
msgstr ""
-#: template/faq.html.j2:24
+#: template/faq.html.j2:136
msgid "Is GNUnet build using distributed ledger technologies?"
msgstr ""
-#: template/faq.html.j2:26
+#: template/faq.html.j2:138
msgid ""
"A: No. GNUnet is a new network protocol stack for building secure, "
"distributed, and privacy-preserving applications. While a ledger could be "
"built using GNUnet, we currently have no plans in doing so."
msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:151
+msgid "What can I do with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
+"do more than just one thing. Naturally, the implementation and documentation "
+"of some of the features that exist are more advanced than others."
+msgstr ""
+
+#: template/faq.html.j2:160
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
+"decentralized and censorship-resistant replacement for DNS and a mechanism "
+"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
+msgstr ""
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We "
+"recommend that you use Tor for anonymous surfing."
+msgstr ""
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr ""
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+
+#: template/faq.html.j2:195
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the "
+"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
+"that integrates most of the other GUIs in one window. One exception is "
+"gnunet-setup, which must still be run separately at this time (as setup "
+"requires the peer to be stopped)."
+msgstr ""
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr ""
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
+"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
+"FreeBSD and macOS. We have reports of working versions on many other GNU/"
+"Linux distributions; in the past we had reports of working versions on "
+"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
+"so if you cannot get GNUnet to work on those systems please let us know."
+msgstr ""
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr ""
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a default "
+"configuration of top-level domains. The governance of this default "
+"configuration is not yet established. In any case, the user will be able to "
+"modify this configuration at will. We expect normal users to have no need to "
+"edit their own GNS zone(s) unless they host services themselves."
+msgstr ""
+
+#: template/faq.html.j2:241
+msgid "Where is the per-user GNS database kept?"
+msgstr ""
+
+#: template/faq.html.j2:243
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet peer. "
+"Now, a user may run multiple GNUnet peers, in which case the database could "
+"be kept at each peer (however, we don't have code for convenient "
+"replication). Similarly, multiple GNUnet peers can share one instance of the "
+"database --- the "gnunet-service-namestore" can be accessed from "
+"remote (via TCP). The actual data can be stored in a Postgres database, for "
+"which various replication options are again applicable. Ultimately, there "
+"are many options for how users can store (and secure) their GNS database."
+msgstr ""
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases "
+"will only grow to a few tens of thousands of entries, small enough to fit "
+"even on mobile devices."
+msgstr ""
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr ""
+
+#: template/faq.html.j2:272
+msgid ""
+"A: We believe so, as there is no entity that any government could force to "
+"change the mapping for a name except for each individual user (and then the "
+"changes would only apply to the names that this user is the authority for). "
+"So if everyone used GNS, the only practical attack of a government would be "
+"to force the operator of a server to change the GNS records for his server "
+"to point elsewhere. However, if the owner of the private key for a zone is "
+"unavailable for enforcement, the respective zone cannot be changed and any "
+"other zone delegating to this zone will achieve proper resolution."
+msgstr ""
+
+#: template/faq.html.j2:286
+msgid "How does GNS compare to other name systems"
+msgstr ""
+
+#: template/faq.html.j2:288
+msgid ""
+"A: A scientific paper on this topic <a href=\"https://grothoff.org/christian/";
+"ns2018.pdf\">has been published </a> and below is a table from the "
+"publication. For detailed descriptions please refer to the paper."
+msgstr ""
+
+#: template/faq.html.j2:392
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr ""
+
+#: template/faq.html.j2:394
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
+"there are still registrars that determine who owns a name. <br><br> With "
+"GNS, we decentralize the database and also decentralize the responsibility "
+"for naming: each user runs his own personal root zone and is thus in "
+"complete control of the names he uses. GNS also has many additional features "
+"(to keep names short and enable migration) which don't even make sense in "
+"the context of CoDoNS."
+msgstr ""
+
+#: template/faq.html.j2:410
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr ""
+
+#: template/faq.html.j2:412
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared via "
+"delegation, and thus mappings will only change if the user responsible for "
+"the name (the authority) manually changes the record."
+msgstr ""
+
+#: template/faq.html.j2:426
+msgid "What is the difference between GNS and ODDNS?"
+msgstr ""
+
+#: template/faq.html.j2:428
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+
+#: template/faq.html.j2:439
+msgid "What is the difference between GNS and Handshake?"
+msgstr ""
+
+#: template/faq.html.j2:441
+msgid ""
+"A: Handshake is a blockchain-based method for root zone governance. Hence, "
+"it does not address the name resolution process itself but delegates "
+"resolution into DNS after the initial TLD resolution. Not taking "
+"sustainablility considerations into account, handshake could be used as an "
+"additional supporting GNS root zone governance model but we currently do not "
+"have such plans in mind."
+msgstr ""
+
+#: template/faq.html.j2:453
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr ""
+
+#: template/faq.html.j2:455
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks on "
+"DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from "
+"the DNS hierarchy."
+msgstr ""
+
+#: template/faq.html.j2:468
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the style "
+"of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: For security, it is well known that an initial trust path between the two "
+"parties must exist. However, for applications where this is not required, "
+"weaker mechanisms can be used. For example, we have implemented a first-come-"
+"first-served (FCFS) authority which allows arbitrary users to register "
+"arbitrary names. The key of this authority is included with every GNUnet "
+"installation. Thus, any name registered with FCFS is in fact global and "
+"requires no further introduction. However, the security of these names "
+"depends entirely on the trustworthiness of the FCFS authority. The authority "
+"can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name in "
+"GNS?"
+msgstr ""
+
+#: template/faq.html.j2:487
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "legitimate" "
+"domain owner. Any user can claim any name (as his preferred name or ""
+"pseudonym") in his NICK record. Similarly, all other users can choose "
+"to ignore this preference and use a name of their choice (or even assign no "
+"name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:498
+msgid ""
+"Did you consider the privacy implications of making your personal GNS zone "
+"visible?"
+msgstr ""
+
+#: template/faq.html.j2:500
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not set. "
+"Thus, users have full control over what information about their zones is "
+"made public."
+msgstr ""
+
+#: template/faq.html.j2:510
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary because "
+"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
+"of virtual hosting. However, LEHOs are also useful to help with X.509 "
+"certificate validation (as they specify for which legacy hostname the "
+"certificate should be valid). Also, even with IPv6 fully deployed and ""
+"infinite" IP addresses being available, we're not sure that virtual "
+"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
+"become commonplace, GNS should work with today's networks."
+msgstr ""
+
+#: template/faq.html.j2:526
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:528
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. As "
+"trust relationships evolve, mappings would change their meaning as they "
+"cross each others thresholds. We decided that the resulting unpredictability "
+"of the resolution process was not acceptable. Furthermore, trust and "
+"consensus might be easy to manipulate by adversaries."
+msgstr ""
+
+#: template/faq.html.j2:539
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:541
+msgid ""
+"A: The owner of a private key can create a revocation message. This one can "
+"then be flooded throughout the overlay network, creating a copy at all "
+"peers. Before using a public key, peers check if that key has been revoked. "
+"All names that involve delegation via a revoked zone will then fail to "
+"resolve. Peers always automatically check for the existence of a revocation "
+"message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:553
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:555
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:569
+msgid ""
+"How can a GNS zone maintain several name servers, e.g. for load balancing?"
+msgstr ""
+
+#: template/faq.html.j2:571
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share "
+"the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:584
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:586
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names are "
+"not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on your "
+"application, HTTPS may not be worth the cost. However, for users that are "
+"experiencing censorship (or are concerned about it), giving up globally "
+"unique names may very well be worth the cost. After all, what is a ""
+"globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:600
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:602
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by IANA/ICANN. "
+"This centralization creates vulnerabilities. For example, the US government "
+"was able to reassign the management of the country-TLDs of Afganistan and "
+"Iraq during the wars at the beginning of the 21st century."
+msgstr ""
+
+#: template/faq.html.j2:613
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:615
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
+"so blocking a particular IP address causes much more collateral damage than "
+"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
+"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
+"censorship resistant naming system. Accessing Tor's ".onion" "
+"namespace currently requires users to use unmemorable cryptographic "
+"identifiers. With nicer names, Tor and tor2web-like services would be even "
+"easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:634
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:636
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can use "
+"GNS to perform name resolution as well as any normal user. Naturally, while "
+"we typically expect normal users to install custom software for name "
+"resolution, this is unlikely to work for search engines today. However, the "
+"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
+"they can still index GNS resources. However, as using DNS2GNS gateways "
+"breaks the cryptographic chain of trust, legacy search engines will "
+"obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:650
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:652
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was designed "
+"to interoperate with DNS as much as possible, and to also work as much as "
+"possible with the existing Web infrastructure. UIA is not at all concerned "
+"about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:665
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:667
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you know "
+"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
+"and can thus decide how much you trust the result. Naturally, the trusted-"
+"computing base (TCB) can become arbitrarily large this way --- however, "
+"given the name length restriction, for an individual name it is always less "
+"than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:679
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part of "
+"the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:681
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects the "
+""_Service._Proto" syntax, converts "Service" to the "
+"corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when the "
+"result is presented, GNS looks for the GNS-specific "BOX" record "
+"type. A BOX record is a record that contains another record (such as SRV or "
+"TLSA records) and adds a service and protocol number (and the original boxed "
+"record type) to it."
+msgstr ""
+
+#: template/faq.html.j2:697
msgid ""
"I receive many "WARNING Calculated flow delay for X at Y for Z". "
"Should I worry?"
msgstr ""
-#: template/faq.html.j2:37
+#: template/faq.html.j2:699
msgid ""
"A: Right now, this is expected and a known cause for high latency in GNUnet. "
"We have started a major rewrite to address this and other problems, but "
@@ -817,14 +1386,191 @@ msgid ""
"expected."
msgstr ""
-#: template/faq.html.j2:46
-msgid "Is there a graphical user interface?"
+#: template/faq.html.j2:708
+msgid "Error opening `/dev/net/tun': No such file or directory?"
msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:710
msgid ""
-"A: gnunet-gtk is a separate download. The package contains various GTK+ "
-"based graphical interfaces, including a graphical tool for configuration."
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:722
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
+"dns)?"
+msgstr ""
+
+#: template/faq.html.j2:724
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check if "
+"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:736
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:738
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if "
+"your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:746
+msgid ""
+"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:748
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if you "
+"compiled GNUnet the normal way and/or used a binary package, that is highly "
+"unlikely. The more common cause is that you installed GNUnet to a directory "
+"that your linker does not search. There are several ways to fix this that "
+"are described below. If you are 'root' and you installed to a system folder "
+"(such as /usr/local), you want to add the libraries to the system-wide "
+"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
+"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
+"similar path, you obviously have to change \"/usr/local\" accordingly. If "
+"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
+"$USER/\", then you can explicitly tell your linker to search a particular "
+"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
+"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
+"you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:774
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the \"$\") "
+"to your .bashrc or .profile file. You will have to logout and login again to "
+"have this new profile be applied to all shells (including your desktop "
+"environment)."
+msgstr ""
+
+#: template/faq.html.j2:781
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:783
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
+"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
+"always refer to harmless events that require no action. For example, GNUnet "
+"may use an INFO message to indicate that it is currently performing an "
+"expensive operation that will take some time. GNUnet will also use INFO "
+"messages to display information about important configuration values."
+msgstr ""
+
+#: template/faq.html.j2:799
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:801
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
+"P2P networks, GNUnet was designed with security in mind as the highest "
+"priority. We intend on producing a network with comprehensive security "
+"features. Many other P2P networks are open to a wide variety of attacks, and "
+"users have little privacy. GNUnet is also Free Software and thus the source "
+"code is available, so you do not have to worry about being spied upon by the "
+"software. The following table summarises the main differences between GNUnet "
+"and other systems. The information is accurate to the best of our knowledge. "
+"The comparison is difficult since there are sometimes differences between "
+"various implementations of (almost) the same protocol. In general, we pick a "
+"free implementation as the reference implementation since it is possible to "
+"inspect the free code. Also, all of these systems are changing over time and "
+"thus the data below may not be up-to-date. If you find any flaws, please let "
+"us know. Finally, the table is not saying terribly much (it is hard to "
+"compare these systems this briefly), so if you want the real differences, "
+"read the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:915
+msgid ""
+"Another important point of reference are the various anonymous peer-to-peer "
+"networks. Here, there are differences in terms of application domain and how "
+"specifically anonymity is achieved. Anonymous routing is a hard research "
+"topic, so for a superficial comparisson like this one we focus on the "
+"latency. Another important factor is the programming language. Type-safe "
+"languages may offer certain security benefits; however, this may come at the "
+"cost of significant increases in resource consumption which in turn may "
+"reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:928
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:930
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of the "
+"same techniques used to generate reasonable passwords to defend against such "
+"an attack. In any event, we are not trying to hide content; thus, unless the "
+"user is trying to insert information into the network that can only be "
+"shared with a small group of people, there is no real reason to try to "
+"obfuscate the content by choosing a difficult keyword anyway."
+msgstr ""
+
+#: template/faq.html.j2:944
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:946
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all "
+"users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell which "
+"of the peers in the group originated the message. In other words, it should "
+"be difficult to impossible for an adversary to distinguish between the "
+"originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:958
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:960
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
+"its public key) and has a number of addresses it is reachable by (may have "
+"no addresses, for instance when it's behind a NAT). You specify bandwidth "
+"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
+"(how large your on-disk block storage is) . Your node will then proceed to "
+"connect to other nodes, becoming part of the network."
+msgstr ""
+
+#: template/faq.html.j2:975
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:977
+msgid ""
+"A: First, you need to register an account with our weblate system. Please "
+"send an e-mail with the desired target language to translators@gnunet.org or "
+"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
+"sufficient permissions will then grant you access. Naturally, any abuse will "
+"result in the loss of permissions."
+msgstr ""
+
+#: template/faq.html.j2:989
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:991
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly implement. "
+"The best way to actually get a new feature implemented is to do it yourself "
+"--- and to then send us a patch."
msgstr ""
#: template/glossary.html.j2:12
@@ -931,10 +1677,6 @@ msgstr ""
msgid "Overview"
msgstr ""
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
-
#: template/gns.html.j2:39
msgid ""
"The GNU Name System (GNS) is secure and decentralized naming system. It "
diff --git a/locale/hi/LC_MESSAGES/messages.po
b/locale/hi/LC_MESSAGES/messages.po
index ecc2c71..e1a6307 100644
--- a/locale/hi/LC_MESSAGES/messages.po
+++ b/locale/hi/LC_MESSAGES/messages.po
@@ -7,13 +7,13 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2021-03-03 21:41+0100\n"
+"POT-Creation-Date: 2021-03-12 15:55+0100\n"
"PO-Revision-Date: 2021-03-09 18:35+0000\n"
"Last-Translator: Jigisha Sharma <jigishas38@gmail.com>\n"
"Language-Team: Hindi <http://weblate.taler.net/projects/gnunet/website/hi/>\n"
"Language: hi\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=n > 1;\n"
"X-Generator: Weblate 4.4.2\n"
@@ -65,6 +65,7 @@ msgid "About"
msgstr "जानकारी"
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
msgstr "समाचार"
@@ -157,17 +158,20 @@ msgstr "र.ई.एस.टी ए .पी .इ"
msgid "FAQ"
msgstr "अकसर पूछे जाने वाले सवाल"
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
msgstr "समाचार पत्र बदलाव जी॰एन॰यू॰ नेट को लेकर घटना और प्रकाशित के उदाहरण"
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
msgstr "अभिदाता बने हमारे रस्स वेब फ़ीड पर"
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
msgstr "और पड़े"
@@ -182,39 +186,38 @@ msgstr "क्या हे जी॰ एन॰यू॰ नेट?"
#: template/about.html.j2:13
msgid ""
-"GNUnet is an alternative network stack for building secure, decentralized"
-" and privacy-preserving distributed applications. Our goal is to replace "
-"the old insecure Internet protocol stack. Starting from an application "
-"for secure publication of files, it has grown to include all kinds of "
-"basic protocol components and applications towards the creation of a GNU "
-"internet."
+"GNUnet is an alternative network stack for building secure, decentralized "
+"and privacy-preserving distributed applications. Our goal is to replace the "
+"old insecure Internet protocol stack. Starting from an application for "
+"secure publication of files, it has grown to include all kinds of basic "
+"protocol components and applications towards the creation of a GNU internet."
msgstr ""
#: template/about.html.j2:23
msgid ""
-"Today, the actual use and thus the social requirements for a global "
-"network differs widely from those goals of 1970. While the Internet "
-"remains suitable for military use, where the network equipment is "
-"operated by a command hierarchy and when necessary isolated from the rest"
-" of the world, the situation is less tenable for civil society."
+"Today, the actual use and thus the social requirements for a global network "
+"differs widely from those goals of 1970. While the Internet remains suitable "
+"for military use, where the network equipment is operated by a command "
+"hierarchy and when necessary isolated from the rest of the world, the "
+"situation is less tenable for civil society."
msgstr ""
#: template/about.html.j2:32
msgid ""
"Due to fundamental Internet design choices, Internet traffic can be "
-"misdirected, intercepted, censored and manipulated by hostile routers on "
-"the network. And indeed, the modern Internet has evolved exactly to the "
-"point where, as Matthew Green put it, <a "
-"href=\"https://blog.cryptographyengineering.com/2015/08/16/the-network-";
-"is-hostile/\">\"the network is hostile\"</a>."
+"misdirected, intercepted, censored and manipulated by hostile routers on the "
+"network. And indeed, the modern Internet has evolved exactly to the point "
+"where, as Matthew Green put it, <a href=\"https://blog.";
+"cryptographyengineering.com/2015/08/16/the-network-is-hostile/\">\"the "
+"network is hostile\"</a>."
msgstr ""
#: template/about.html.j2:41
msgid ""
-"We believe liberal societies need a network architecture that uses the "
-"anti-authoritarian decentralized peer-to-peer paradigm and privacy-"
-"preserving cryptographic protocols. The goal of the GNUnet project is to "
-"provide a Free Software realization of this ideal."
+"We believe liberal societies need a network architecture that uses the anti-"
+"authoritarian decentralized peer-to-peer paradigm and privacy-preserving "
+"cryptographic protocols. The goal of the GNUnet project is to provide a Free "
+"Software realization of this ideal."
msgstr ""
#: template/about.html.j2:49
@@ -225,8 +228,8 @@ msgstr ""
#: template/about.html.j2:56
msgid ""
-"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy";
-"/free-sw.html\">Free Software</a>."
+"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy/free-";
+"sw.html\">Free Software</a>."
msgstr ""
#: template/about.html.j2:60
@@ -237,8 +240,8 @@ msgstr ""
#: template/about.html.j2:61
msgid ""
-"GNUnet must be fully distributed and resilient to external attacks and "
-"rogue participants."
+"GNUnet must be fully distributed and resilient to external attacks and rogue "
+"participants."
msgstr ""
#: template/about.html.j2:62
@@ -249,8 +252,8 @@ msgstr ""
#: template/about.html.j2:63
msgid ""
-"GNUnet must inform the user which other participants have to be trusted "
-"when establishing private communications."
+"GNUnet must inform the user which other participants have to be trusted when "
+"establishing private communications."
msgstr ""
#: template/about.html.j2:64
@@ -271,33 +274,28 @@ msgstr ""
#: template/about.html.j2:68
msgid ""
-"GNUnet must provide incentives for peers to contribute more resources "
-"than they consume."
+"GNUnet must provide incentives for peers to contribute more resources than "
+"they consume."
msgstr ""
#: template/about.html.j2:72
msgid ""
-"To get know and learn more, please check our <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, "
-"especially the <a href=\"https://docs.gnunet.org/handbook/gnunet.html";
-"#Key-Concepts\">chapter on \"Key Concepts\"</a>, explaining the "
-"fundamental concepts of GNUnet: <ul> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Authentication\";>Authentication</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Accounting-";
-"to-Encourage-Resource-Sharing\">Accounting to Encourage Resource "
-"Sharing</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Confidentiality\";>Confidentiality</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability\";>Deniability</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Peer-";
-"Identities\">Peer Identities</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-";
-"Name-System-_0028GNS-Zones_0029\">Zones in the GNU Name System (GNS "
-"Zones)</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> "
-"</ul>"
+"To get know and learn more, please check our <a href=\"https://docs.gnunet.";
+"org/handbook/gnunet.html\">handbook</a>, especially the <a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Key-Concepts\">chapter on \"Key Concepts"
+"\"</a>, explaining the fundamental concepts of GNUnet: <ul> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Authentication";
+"\">Authentication</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Accounting-to-Encourage-Resource-Sharing\">Accounting to "
+"Encourage Resource Sharing</a></li> <li><a href=\"https://docs.gnunet.org/";
+"handbook/gnunet.html#Confidentiality\">Confidentiality</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></"
+"li> <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability";
+"\">Deniability</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Peer-Identities\">Peer Identities</a></li> <li><a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-Name-System-_0028GNS-"
+"Zones_0029\">Zones in the GNU Name System (GNS Zones)</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> </ul>"
msgstr ""
#: template/about.html.j2:88
@@ -306,27 +304,27 @@ msgstr ""
#: template/about.html.j2:90
msgid ""
-"There are many more resources to learn about GNUnet besides the <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such "
-"as the <a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers "
-"covering the various layers, many <a "
-"href=\"https://gnunet.org/en/video.html\";>videos</a> or a brief <a "
-"href=\"https://gnunet.org/en/glossary.html\";>glossary</a>."
+"There are many more resources to learn about GNUnet besides the <a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such as the "
+"<a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers covering "
+"the various layers, many <a href=\"https://gnunet.org/en/video.html";
+"\">videos</a> or a brief <a href=\"https://gnunet.org/en/glossary.html";
+"\">glossary</a>."
msgstr ""
#: template/about.html.j2:95
msgid ""
"You are most welcome to <a href=\"engage.html\">get engaged into the "
-"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a "
-"href=\"use.html\">use it</a> and <a href=\"engage.html\">contribute and "
-"get engaged</a> in various ways."
+"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a href=\"use."
+"html\">use it</a> and <a href=\"engage.html\">contribute and get engaged</a> "
+"in various ways."
msgstr ""
#: template/about.html.j2:100
msgid ""
-"Please be aware that this project is (despite of it's age) still in an "
-"early alpha stage when it comes to software – its not an easy task "
-"to rewrite the whole Internet!"
+"Please be aware that this project is (despite of it's age) still in an early "
+"alpha stage when it comes to software – its not an easy task to "
+"rewrite the whole Internet!"
msgstr ""
#: template/about.html.j2:105
@@ -335,24 +333,25 @@ msgstr ""
#: template/about.html.j2:110
msgid ""
-"We're receiving funding from NLnet's Next Generation Internet funding "
-"line to document and implement the GNU Name System protocol in a way "
-"suitable for the IETF standardization process."
+"We're receiving funding from NLnet's Next Generation Internet funding line "
+"to document and implement the GNU Name System protocol in a way suitable for "
+"the IETF standardization process."
msgstr ""
#: template/about.html.j2:123
msgid ""
"This project has received funding from the European Union’s Horizon 2020 "
"research and innovation programme under the NGI_TRUST grant agreement no "
-"825618. The project aims to integrate re:claimID with the GNU Taler "
-"payment system in a pilot in order to demonstrate the practical "
-"feasibility and benefits of privacy enhancing technologies for users and "
-"commercial service providers. The project is called \"Decentralized "
-"Identities for Self-Sovereign End-users\" (DISSENS)."
+"825618. The project aims to integrate re:claimID with the GNU Taler payment "
+"system in a pilot in order to demonstrate the practical feasibility and "
+"benefits of privacy enhancing technologies for users and commercial service "
+"providers. The project is called \"Decentralized Identities for Self-"
+"Sovereign End-users\" (DISSENS)."
msgstr ""
#: template/about.html.j2:141
-msgid "We are grateful for free hosting offered by the following
organizations:"
+msgid ""
+"We are grateful for free hosting offered by the following organizations:"
msgstr ""
#: template/about.html.j2:150
@@ -373,13 +372,13 @@ msgstr ""
#: template/applications.html.j2:15
msgid ""
-"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully "
-"decentralized replacement for the Domain Name System (DNS). Instead of "
-"using a hierarchy, GNS uses a directed graph. Naming conventions are "
-"similar to DNS, but queries and replies are private even with respect to "
-"peers providing the answers. The integrity of records and privacy of "
-"look-ups is cryptographically secured. <!-- Too technical: GNS integrates"
-" a robust, efficient and instant key revocation mechanism. -->"
+"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully decentralized "
+"replacement for the Domain Name System (DNS). Instead of using a hierarchy, "
+"GNS uses a directed graph. Naming conventions are similar to DNS, but "
+"queries and replies are private even with respect to peers providing the "
+"answers. The integrity of records and privacy of look-ups is "
+"cryptographically secured. <!-- Too technical: GNS integrates a robust, "
+"efficient and instant key revocation mechanism. -->"
msgstr ""
#: template/applications.html.j2:38
@@ -388,8 +387,8 @@ msgstr ""
#: template/applications.html.j2:40
msgid ""
-"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized"
-" Identity Provider (IdP) service built in top of the GNU Name System. It "
+"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized "
+"Identity Provider (IdP) service built in top of the GNU Name System. It "
"allows users to securely share personal information with websites using "
"standardized protocols (OpenID Connect)."
msgstr ""
@@ -400,10 +399,9 @@ msgstr ""
#: template/applications.html.j2:59
msgid ""
-"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that "
-"aims to provide censorship-resistant, anonymous filesharing. The "
-"publisher is empowered to make a gradual choice between performance and "
-"anonymity."
+"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that aims "
+"to provide censorship-resistant, anonymous filesharing. The publisher is "
+"empowered to make a gradual choice between performance and anonymity."
msgstr ""
#: template/applications.html.j2:73
@@ -413,8 +411,8 @@ msgstr ""
#: template/applications.html.j2:75
msgid ""
"GNUnet conversation is an application that provides secure voice "
-"communication in a fully decentralized way by employing GNUnet for "
-"routing and transport."
+"communication in a fully decentralized way by employing GNUnet for routing "
+"and transport."
msgstr ""
#: template/applications.html.j2:91
@@ -428,8 +426,8 @@ msgstr ""
#: template/applications.html.j2:99
msgid ""
"<a href=\"https://taler.net/\";>GNU Taler</a> is a new privacy-preserving "
-"electronic payment system. Payments are cryptographically secured and are"
-" confirmed within milliseconds with extremely low transaction costs."
+"electronic payment system. Payments are cryptographically secured and are "
+"confirmed within milliseconds with extremely low transaction costs."
msgstr ""
#: template/applications.html.j2:118
@@ -438,10 +436,10 @@ msgstr ""
#: template/applications.html.j2:120
msgid ""
-"<a href=\"https://secushare.org/\";>secushare</a> is creating a "
-"decentralized social networking application on top of GNUnet. Using "
-"overlay multicast and the extensible PSYC protocol, notifications are "
-"distributed end-to-end encrypted to authorized recipients only."
+"<a href=\"https://secushare.org/\";>secushare</a> is creating a decentralized "
+"social networking application on top of GNUnet. Using overlay multicast and "
+"the extensible PSYC protocol, notifications are distributed end-to-end "
+"encrypted to authorized recipients only."
msgstr ""
#: template/applications.html.j2:139
@@ -450,10 +448,10 @@ msgstr ""
#: template/applications.html.j2:141
msgid ""
-"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) "
-"is creating a usable end-to-end encrypted e-mail solution using "
-"opportunistic key exchange. p≡p will use GNUnet to protect metadata"
-" and exploit new cryptographic protocols to verify keys."
+"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) is "
+"creating a usable end-to-end encrypted e-mail solution using opportunistic "
+"key exchange. p≡p will use GNUnet to protect metadata and exploit new "
+"cryptographic protocols to verify keys."
msgstr ""
#: template/applications.html.j2:160
@@ -462,10 +460,10 @@ msgstr ""
#: template/applications.html.j2:162
msgid ""
-"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> "
-"is a convenient but feature-rich graphical application providing "
-"messaging using especially the CADET subsystem. It is developed using GTK"
-" and libhandy for a convergent design."
+"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> is a "
+"convenient but feature-rich graphical application providing messaging using "
+"especially the CADET subsystem. It is developed using GTK and libhandy for a "
+"convergent design."
msgstr ""
#: template/applications.html.j2:180
@@ -476,8 +474,8 @@ msgstr ""
msgid ""
"<a href=\"https://git.gnunet.org/groupchat.git/\";>groupchat</a> is a "
"terminal user interface providing messaging using especially the CADET "
-"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned"
-" to be compatible."
+"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned to "
+"be compatible."
msgstr ""
#: template/architecture.html.j2:6
@@ -490,11 +488,11 @@ msgstr ""
#: template/architecture.html.j2:22
msgid ""
-"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-"
-"like end-to-end encrypted messaging layer (CADET), a public key "
-"infrastructure (GNS) and a pluggable transport system (TRANSPORT).<br> "
-"Using public keys for addresses and self-organized decentralized routing "
-"algorithms, these subsystems replace the traditional TCP/IP stack."
+"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-like "
+"end-to-end encrypted messaging layer (CADET), a public key infrastructure "
+"(GNS) and a pluggable transport system (TRANSPORT).<br> Using public keys "
+"for addresses and self-organized decentralized routing algorithms, these "
+"subsystems replace the traditional TCP/IP stack."
msgstr ""
#: template/architecture.html.j2:35
@@ -505,9 +503,9 @@ msgstr ""
msgid ""
"GNUnet is implemented using a multi-process architecture. Each subsystem "
"runs as a separate process, providing fault-isolation and enabling tight "
-"permissions to be granted to each subsystem. Naturally, the "
-"implementation is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and"
-" will always remain free software."
+"permissions to be granted to each subsystem. Naturally, the implementation "
+"is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and will always "
+"remain free software."
msgstr ""
#: template/architecture.html.j2:52
@@ -540,11 +538,10 @@ msgstr ""
#: template/contact.html.j2:13
msgid ""
-"An archived, public mailing list for GNUnet is hosted at <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers\">https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>. You can send messages to the list at <a href=\"mailto"
-":gnunet-developers@gnu.org\">gnunet-developers@gnu.org</a>."
+"An archived, public mailing list for GNUnet is hosted at <a href=\"https://";
+"lists.gnu.org/mailman/listinfo/gnunet-developers\">https://lists.gnu.org/";
+"mailman/listinfo/gnunet-developers</a>. You can send messages to the list at "
+"<a href=\"mailto:gnunet-developers@gnu.org\";>gnunet-developers@gnu.org</a>."
msgstr ""
#: template/contact.html.j2:23
@@ -553,10 +550,9 @@ msgstr ""
#: template/contact.html.j2:25
msgid ""
-"<tt>#gnunet</tt> is reachable via <a "
-"href=\"https://freenode.net\";>irc.freenode.net</a>. There is also an <a "
-"href=\"https://view.matrix.org/room/!IjaAfLiruzjxFFzKAV:matrix.org/\";>archive</a>"
-" available."
+"<tt>#gnunet</tt> is reachable via <a href=\"https://freenode.net\";>irc."
+"freenode.net</a>. There is also an <a href=\"https://view.matrix.org/room/!";
+"IjaAfLiruzjxFFzKAV:matrix.org/\">archive</a> available."
msgstr ""
#: template/contact.html.j2:38
@@ -565,11 +561,10 @@ msgstr ""
#: template/contact.html.j2:40
msgid ""
-"GNUnet developers are generally reachable at either "
-"<tt>PSEUDONYM@gnunet.org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us"
-" support receiving GnuPG encrypted Emails. Urgent and sensitive security "
-"issues may be addressed to the GNU maintainers <tt>schanzen</tt> and "
-"<tt>grothoff</tt>."
+"GNUnet developers are generally reachable at either <tt>PSEUDONYM@gnunet."
+"org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us support receiving GnuPG "
+"encrypted Emails. Urgent and sensitive security issues may be addressed to "
+"the GNU maintainers <tt>schanzen</tt> and <tt>grothoff</tt>."
msgstr ""
#: template/contact.html.j2:53
@@ -578,38 +573,37 @@ msgstr ""
#: template/contact.html.j2:55
msgid ""
-"We track open feature requests and bugs for projects within GNUnet in our"
-" <a href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also "
-"report bugs or feature requests to the <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/bug-gnunet\";>bug-gnunet</a>"
-" mailing list. The mailinglist requires no subscription."
+"We track open feature requests and bugs for projects within GNUnet in our <a "
+"href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also report bugs "
+"or feature requests to the <a href=\"https://lists.gnu.org/mailman/listinfo/";
+"bug-gnunet\">bug-gnunet</a> mailing list. The mailinglist requires no "
+"subscription."
msgstr ""
#: template/copyright.html.j2:11
msgid ""
-"<p> Contributors to GNUnet with Git access must sign the <a "
-"href=\"/static/pdf/copyright.pdf\">copyright assignment</a> to ensure "
-"that the <a href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/gnunet_taler_agreement.tex\">GNUnet e.V. --- Taler Systems SA"
-" agreement on licensing and collaborative development</a> of the GNUnet "
-"and GNU Taler projects is satisfied. </p>"
+"<p> Contributors to GNUnet with Git access must sign the <a href=\"/static/"
+"pdf/copyright.pdf\">copyright assignment</a> to ensure that the <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/gnunet_taler_agreement.tex";
+"\">GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative "
+"development</a> of the GNUnet and GNU Taler projects is satisfied. </p>"
msgstr ""
#: template/copyright.html.j2:22
msgid ""
-"<p>The agreements ensure that the code will continue to be made available"
-" under free software licenses, but gives developers the freedom to move "
-"code between GNUnet and GNU Taler without worrying about licenses and to "
-"give the company the ability to dual-license (for example, so that we can"
-" distribute via App-stores that are hostile to free software).</p>"
+"<p>The agreements ensure that the code will continue to be made available "
+"under free software licenses, but gives developers the freedom to move code "
+"between GNUnet and GNU Taler without worrying about licenses and to give the "
+"company the ability to dual-license (for example, so that we can distribute "
+"via App-stores that are hostile to free software).</p>"
msgstr ""
#: template/copyright.html.j2:30
msgid ""
-"<p>Minor contributions (basically, anyone without Git access) do not "
-"require copyright assignment. Pseudonymous contributions are accepted, in"
-" this case simply sign the agreement with your pseudonym. Scanned copies "
-"are sufficient, but snail mail is preferred.</p>"
+"<p>Minor contributions (basically, anyone without Git access) do not require "
+"copyright assignment. Pseudonymous contributions are accepted, in this case "
+"simply sign the agreement with your pseudonym. Scanned copies are "
+"sufficient, but snail mail is preferred.</p>"
msgstr ""
#: template/developers.html.j2:5
@@ -622,14 +616,14 @@ msgstr ""
#: template/developers.html.j2:16
msgid ""
-"A list of our Git repositories can be found on our our <a "
-"href=\"https://git.gnunet.org/\";>Git Server</a>."
+"A list of our Git repositories can be found on our our <a href=\"https://git.";
+"gnunet.org/\">Git Server</a>."
msgstr ""
#: template/developers.html.j2:27
msgid ""
-"Technical papers can be found in our <a "
-"href=\"https://old.gnunet.org/bibliography\";>bibliography</a>."
+"Technical papers can be found in our <a href=\"https://old.gnunet.org/";
+"bibliography\">bibliography</a>."
msgstr ""
#: template/developers.html.j2:34
@@ -638,10 +632,10 @@ msgstr ""
#: template/developers.html.j2:37
msgid ""
-"We have a mailing list for developer discussions. You can subscribe to or"
-" read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo";
-"/gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>."
+"We have a mailing list for developer discussions. You can subscribe to or "
+"read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo/";
+"gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-developers</"
+"a>."
msgstr ""
#: template/developers.html.j2:47
@@ -650,9 +644,9 @@ msgstr ""
#: template/developers.html.j2:50
msgid ""
-"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests "
-"to detect regressions and check for portability at <a "
-"href=\"https://old.gnunet.org/buildbot/gnunet/\";>https://old.gnunet.org/buildbot/gnunet/</a>."
+"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests to "
+"detect regressions and check for portability at <a href=\"https://old.gnunet.";
+"org/buildbot/gnunet/\">https://old.gnunet.org/buildbot/gnunet/</a>."
msgstr ""
#: template/developers.html.j2:59
@@ -661,10 +655,9 @@ msgstr ""
#: template/developers.html.j2:62
msgid ""
-"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> "
-"to analyze the code coverage of our tests, the results are available at "
-"<a "
-"href=\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
+"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> to "
+"analyze the code coverage of our tests, the results are available at <a href="
+"\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
msgstr ""
#: template/developers.html.j2:72
@@ -673,9 +666,9 @@ msgstr ""
#: template/developers.html.j2:75
msgid ""
-"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for "
-"performance regression analysis of the exchange backend at <a "
-"href=\"https://old.gnunet.org/gauger/\";>https://old.gnunet.org/gauger/</a>."
+"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for performance "
+"regression analysis of the exchange backend at <a href=\"https://old.gnunet.";
+"org/gauger/\">https://old.gnunet.org/gauger/</a>."
msgstr ""
#: template/download.html.j2:7 template/gnurl.html.j2:209
@@ -684,8 +677,8 @@ msgstr ""
#: template/download.html.j2:11
msgid ""
-"Here you can download releases of our software and find links to the "
-"various versions."
+"Here you can download releases of our software and find links to the various "
+"versions."
msgstr ""
#: template/download.html.j2:17
@@ -707,7 +700,8 @@ msgid "git"
msgstr ""
#: template/download.html.j2:32
-msgid "You can fetch the git tag of version 0.11.x from our development
server:"
+msgid ""
+"You can fetch the git tag of version 0.11.x from our development server:"
msgstr ""
#: template/engage.html.j2:6
@@ -724,18 +718,17 @@ msgstr ""
#: template/ev.html.j2:13
msgid ""
-"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the"
-" \"Verein zur Förderung von GNUnet e.V.\", an association under "
-"German law to support GNUnet development. The Amtsgericht München "
-"registered the association on the 7th of March under VR 205287."
+"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the "
+"\"Verein zur Förderung von GNUnet e.V.\", an association under German "
+"law to support GNUnet development. The Amtsgericht München registered "
+"the association on the 7th of March under VR 205287."
msgstr ""
#: template/ev.html.j2:22
msgid ""
-"The association is officially dedicated to supporting research, "
-"development and education in the area of secure decentralized networking "
-"in general, and GNUnet specifically. This is the official website for the"
-" association."
+"The association is officially dedicated to supporting research, development "
+"and education in the area of secure decentralized networking in general, and "
+"GNUnet specifically. This is the official website for the association."
msgstr ""
#: template/ev.html.j2:31
@@ -744,15 +737,15 @@ msgstr ""
#: template/ev.html.j2:33
msgid ""
-"GNUnet developers with git (write) access can become members to "
-"participate in the decision process and formally support GNUnet e.V. For "
-"this, all you have to do is update the <tt>members.txt</tt> file in the "
-"<a href=\"https://git.gnunet.org/gnunet-ev.git/\";>gnunet-ev</a> "
-"repository. There are no membership dues; however, members are required "
-"to support GNUnet e.V. and in particularly contribute to the technical "
-"development within their means. For further details, we refer to the <a "
-"href=\"https://git.gnunet.org/gnunet-ev.git/\";>Satzung</a> (currently "
-"only available in German, translations welcome)."
+"GNUnet developers with git (write) access can become members to participate "
+"in the decision process and formally support GNUnet e.V. For this, all you "
+"have to do is update the <tt>members.txt</tt> file in the <a href=\"https://";
+"git.gnunet.org/gnunet-ev.git/\">gnunet-ev</a> repository. There are no "
+"membership dues; however, members are required to support GNUnet e.V. and in "
+"particularly contribute to the technical development within their means. For "
+"further details, we refer to the <a href=\"https://git.gnunet.org/gnunet-ev.";
+"git/\">Satzung</a> (currently only available in German, translations "
+"welcome)."
msgstr ""
#: template/ev.html.j2:52
@@ -761,16 +754,13 @@ msgstr ""
#: template/ev.html.j2:54
msgid ""
-"You can find our \"Satzung\", and the list of members under <a "
-"href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex\">https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex</a>. The current board consists of: "
+"You can find our \"Satzung\", and the list of members under <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex\";>https://git.gnunet.";
+"org/gnunet-ev.git/tree/satzung.tex</a>. The current board consists of: "
"<dl><dt>Vorsitz</dt> <dd><a href=\"https://schanzen.eu\";>Martin "
-"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> "
-"<dd>t3sserakt</dd> <dt>Kassenwart</dt> <dd>Florian Dold</dd> "
-"<dt>Beisitzer</dt> <dd> <a "
-"href=\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 "
-"</dd> </dl>"
+"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> <dd>t3sserakt</dd> "
+"<dt>Kassenwart</dt> <dd>Florian Dold</dd> <dt>Beisitzer</dt> <dd> <a href="
+"\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 </dd> </dl>"
msgstr ""
#: template/ev.html.j2:73
@@ -785,77 +775,803 @@ msgstr ""
msgid ""
"Everybody is welcome to support us via donations. For financial "
"contributions, Europeans are able to donate via SEPA. We hope to setup "
-"accounts in other major currency areas in the future. You can also donate"
-" via Bitcoin, routing details are given below. Please note that we are "
-"unable to provide receipts for your donations. If you are planning to "
-"donate a significant amount of money, please contact us first as it might"
-" be better to come to a custom arrangement. <dl><dt>BitCoin</dt> "
+"accounts in other major currency areas in the future. You can also donate "
+"via Bitcoin, routing details are given below. Please note that we are unable "
+"to provide receipts for your donations. If you are planning to donate a "
+"significant amount of money, please contact us first as it might be better "
+"to come to a custom arrangement. <dl><dt>BitCoin</dt> "
"<dd>1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh</dd> <dt>SEPA/IBAN</dt> "
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
-#: template/faq.html.j2:12
-msgid "Is GNUnet ready for use on production systems?"
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
msgstr ""
-#: template/faq.html.j2:14
-msgid ""
-"A: GNUnet is still undergoing major development. It is largely not yet "
-"ready for usage beyond developers. Your mileage will vary depending on "
-"the functionality you use, but you will always likely run into issues "
-"with our current low-level transport system. We are currently in the "
-"process of rewriting it (Project "Transport Next Generation "
-"[TNG]")"
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
msgstr ""
-#: template/faq.html.j2:24
-msgid "Is GNUnet build using distributed ledger technologies?"
+#: template/faq.html.j2:15 template/faq.html.j2:594
+msgid "Error messages"
+msgstr ""
+
+#: template/faq.html.j2:16 template/faq.html.j2:696
+msgid "File-sharing"
+msgstr ""
+
+#: template/faq.html.j2:17 template/faq.html.j2:872
+msgid "Contributing"
msgstr ""
#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr ""
+
+#: template/faq.html.j2:28
msgid ""
-"A: No. GNUnet is a new network protocol stack for building secure, "
-"distributed, and privacy-preserving applications. While a ledger could be"
-" built using GNUnet, we currently have no plans in doing so."
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
+"the #gnunet IRC on irc.freenode.net."
msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
+msgstr ""
+
+#: template/faq.html.j2:38
msgid ""
-"I receive many "WARNING Calculated flow delay for X at Y for "
-"Z". Should I worry?"
+"A: The general answer is, when it is ready. A better answer may be: earlier "
+"if you contribute (test, debug, code, document). Every release will be "
+"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://";
+"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
+"the RSS feed of this site to automatically receive a notification."
+msgstr ""
+
+#: template/faq.html.j2:49
+msgid "Is the code free?"
msgstr ""
-#: template/faq.html.j2:37
+#: template/faq.html.j2:51
msgid ""
-"A: Right now, this is expected and a known cause for high latency in "
-"GNUnet. We have started a major rewrite to address this and other "
-"problems, but until the Transport Next Generation (TNG) is ready, these "
-"warnings are expected."
+"A: GNUnet is free software, available under the <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
msgstr ""
-#: template/faq.html.j2:46
+#: template/faq.html.j2:58
+msgid "Are there any known bugs?"
+msgstr ""
+
+#: template/faq.html.j2:60
+msgid ""
+"A: We track the list of currently known bugs in the <a href=\"https://bugs.";
+"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
+"directly to developers or the developer mailing list. This is discouraged "
+"since developers often do not have the time to feed these bugs back into the "
+"Mantis database. Please report bugs directly to the bug tracking system. If "
+"you believe a bug is sensitive, you can set its view status to private (this "
+"should be the exception)."
+msgstr ""
+
+#: template/faq.html.j2:73 template/faq.html.j2:193
msgid "Is there a graphical user interface?"
msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:75
msgid ""
"A: gnunet-gtk is a separate download. The package contains various GTK+ "
"based graphical interfaces, including a graphical tool for configuration."
msgstr ""
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr ""
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called ""
+"proof-of-work" which is used to convince the network that your peer is "
+"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
+"on the network size estimator). The calculation is expected to take a few "
+"days, depending on how fast your CPU is. If the CPU load is creating a "
+"problem for you, you can set the value "WORKDELAY" in the ""
+"nse" section of your configuration file to a higher value. The default "
+"is "5 ms"."
+msgstr ""
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr ""
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
+"connections and, with the Tor Browser Bundle, for the Web in particular. "
+"GNUnet does not really have one focus; our theme is secure decentralized "
+"networking, but that is too broad to be called a focus."
+msgstr ""
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr ""
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost no "
+"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
+"using onion (or garlic) routing as the basis for various (anonymized) "
+"applications. I2P is largely used via a Web frontend."
+msgstr ""
+
+#: template/faq.html.j2:124
+msgid "Is GNUnet ready for use on production systems?"
+msgstr ""
+
+#: template/faq.html.j2:126
+msgid ""
+"A: GNUnet is still undergoing major development. It is largely not yet ready "
+"for usage beyond developers. Your mileage will vary depending on the "
+"functionality you use, but you will always likely run into issues with our "
+"current low-level transport system. We are currently in the process of "
+"rewriting it (Project "Transport Next Generation [TNG]")"
+msgstr ""
+
+#: template/faq.html.j2:136
+msgid "Is GNUnet build using distributed ledger technologies?"
+msgstr ""
+
+#: template/faq.html.j2:138
+msgid ""
+"A: No. GNUnet is a new network protocol stack for building secure, "
+"distributed, and privacy-preserving applications. While a ledger could be "
+"built using GNUnet, we currently have no plans in doing so."
+msgstr ""
+
+#: template/faq.html.j2:151
+#, fuzzy
+#| msgid "What is GNUnet?"
+msgid "What can I do with GNUnet?"
+msgstr "क्या हे जी॰ एन॰यू॰ नेट?"
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
+"do more than just one thing. Naturally, the implementation and documentation "
+"of some of the features that exist are more advanced than others."
+msgstr ""
+
+#: template/faq.html.j2:160
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
+"decentralized and censorship-resistant replacement for DNS and a mechanism "
+"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
+msgstr ""
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We "
+"recommend that you use Tor for anonymous surfing."
+msgstr ""
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr ""
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+
+#: template/faq.html.j2:195
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the "
+"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
+"that integrates most of the other GUIs in one window. One exception is "
+"gnunet-setup, which must still be run separately at this time (as setup "
+"requires the peer to be stopped)."
+msgstr ""
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr ""
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
+"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
+"FreeBSD and macOS. We have reports of working versions on many other GNU/"
+"Linux distributions; in the past we had reports of working versions on "
+"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
+"so if you cannot get GNUnet to work on those systems please let us know."
+msgstr ""
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr ""
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a default "
+"configuration of top-level domains. The governance of this default "
+"configuration is not yet established. In any case, the user will be able to "
+"modify this configuration at will. We expect normal users to have no need to "
+"edit their own GNS zone(s) unless they host services themselves."
+msgstr ""
+
+#: template/faq.html.j2:241
+msgid "Where is the per-user GNS database kept?"
+msgstr ""
+
+#: template/faq.html.j2:243
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet peer. "
+"Now, a user may run multiple GNUnet peers, in which case the database could "
+"be kept at each peer (however, we don't have code for convenient "
+"replication). Similarly, multiple GNUnet peers can share one instance of the "
+"database --- the "gnunet-service-namestore" can be accessed from "
+"remote (via TCP). The actual data can be stored in a Postgres database, for "
+"which various replication options are again applicable. Ultimately, there "
+"are many options for how users can store (and secure) their GNS database."
+msgstr ""
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases "
+"will only grow to a few tens of thousands of entries, small enough to fit "
+"even on mobile devices."
+msgstr ""
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr ""
+
+#: template/faq.html.j2:272
+msgid ""
+"A: We believe so, as there is no entity that any government could force to "
+"change the mapping for a name except for each individual user (and then the "
+"changes would only apply to the names that this user is the authority for). "
+"So if everyone used GNS, the only practical attack of a government would be "
+"to force the operator of a server to change the GNS records for his server "
+"to point elsewhere. However, if the owner of the private key for a zone is "
+"unavailable for enforcement, the respective zone cannot be changed and any "
+"other zone delegating to this zone will achieve proper resolution."
+msgstr ""
+
+#: template/faq.html.j2:286
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr ""
+
+#: template/faq.html.j2:288
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
+"there are still registrars that determine who owns a name. <br><br> With "
+"GNS, we decentralize the database and also decentralize the responsibility "
+"for naming: each user runs his own personal root zone and is thus in "
+"complete control of the names he uses. GNS also has many additional features "
+"(to keep names short and enable migration) which don't even make sense in "
+"the context of CoDoNS."
+msgstr ""
+
+#: template/faq.html.j2:304
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr ""
+
+#: template/faq.html.j2:306
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared via "
+"delegation, and thus mappings will only change if the user responsible for "
+"the name (the authority) manually changes the record."
+msgstr ""
+
+#: template/faq.html.j2:320
+msgid "What is the difference between GNS and ODDNS?"
+msgstr ""
+
+#: template/faq.html.j2:322
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+
+#: template/faq.html.j2:333
+msgid "What is the difference between GNS and Namecoin?"
+msgstr ""
+
+#: template/faq.html.j2:340
+msgid "What is the difference between GNS and Handshake?"
+msgstr ""
+
+#: template/faq.html.j2:346
+msgid "What is the difference between GNS and ENS?"
+msgstr ""
+
+#: template/faq.html.j2:352
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr ""
+
+#: template/faq.html.j2:354
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks on "
+"DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from "
+"the DNS hierarchy."
+msgstr ""
+
+#: template/faq.html.j2:367
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the style "
+"of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:369
+msgid ""
+"A: For security, it is well known that an initial trust path between the two "
+"parties must exist. However, for applications where this is not required, "
+"weaker mechanisms can be used. For example, we have implemented a first-come-"
+"first-served (FCFS) authority which allows arbitrary users to register "
+"arbitrary names. The key of this authority is included with every GNUnet "
+"installation. Thus, any name registered with FCFS is in fact global and "
+"requires no further introduction. However, the security of these names "
+"depends entirely on the trustworthiness of the FCFS authority. The authority "
+"can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:384
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name in "
+"GNS?"
+msgstr ""
+
+#: template/faq.html.j2:386
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "legitimate" "
+"domain owner. Any user can claim any name (as his preferred name or ""
+"pseudonym") in his NICK record. Similarly, all other users can choose "
+"to ignore this preference and use a name of their choice (or even assign no "
+"name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:397
+msgid ""
+"Did you consider the privacy implications of making your personal GNS zone "
+"visible?"
+msgstr ""
+
+#: template/faq.html.j2:399
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not set. "
+"Thus, users have full control over what information about their zones is "
+"made public."
+msgstr ""
+
+#: template/faq.html.j2:409
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:411
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary because "
+"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
+"of virtual hosting. However, LEHOs are also useful to help with X.509 "
+"certificate validation (as they specify for which legacy hostname the "
+"certificate should be valid). Also, even with IPv6 fully deployed and ""
+"infinite" IP addresses being available, we're not sure that virtual "
+"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
+"become commonplace, GNS should work with today's networks."
+msgstr ""
+
+#: template/faq.html.j2:425
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:427
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. As "
+"trust relationships evolve, mappings would change their meaning as they "
+"cross each others thresholds. We decided that the resulting unpredictability "
+"of the resolution process was not acceptable. Furthermore, trust and "
+"consensus might be easy to manipulate by adversaries."
+msgstr ""
+
+#: template/faq.html.j2:438
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:440
+msgid ""
+"A: The owner of a private key can create a revocation message. This one can "
+"then be flooded throughout the overlay network, creating a copy at all "
+"peers. Before using a public key, peers check if that key has been revoked. "
+"All names that involve delegation via a revoked zone will then fail to "
+"resolve. Peers always automatically check for the existence of a revocation "
+"message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:452
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:454
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:468
+msgid ""
+"How can a GNS zone maintain several name servers, e.g. for load balancing?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share "
+"the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:483
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names are "
+"not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on your "
+"application, HTTPS may not be worth the cost. However, for users that are "
+"experiencing censorship (or are concerned about it), giving up globally "
+"unique names may very well be worth the cost. After all, what is a ""
+"globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:499
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:501
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by IANA/ICANN. "
+"This centralization creates vulnerabilities. For example, the US government "
+"was able to reassign the management of the country-TLDs of Afganistan and "
+"Iraq during the wars at the beginning of the 21st century."
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:514
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
+"so blocking a particular IP address causes much more collateral damage than "
+"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
+"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
+"censorship resistant naming system. Accessing Tor's ".onion" "
+"namespace currently requires users to use unmemorable cryptographic "
+"identifiers. With nicer names, Tor and tor2web-like services would be even "
+"easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:533
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:535
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can use "
+"GNS to perform name resolution as well as any normal user. Naturally, while "
+"we typically expect normal users to install custom software for name "
+"resolution, this is unlikely to work for search engines today. However, the "
+"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
+"they can still index GNS resources. However, as using DNS2GNS gateways "
+"breaks the cryptographic chain of trust, legacy search engines will "
+"obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:549
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:551
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was designed "
+"to interoperate with DNS as much as possible, and to also work as much as "
+"possible with the existing Web infrastructure. UIA is not at all concerned "
+"about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:564
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:566
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you know "
+"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
+"and can thus decide how much you trust the result. Naturally, the trusted-"
+"computing base (TCB) can become arbitrarily large this way --- however, "
+"given the name length restriction, for an individual name it is always less "
+"than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:578
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part of "
+"the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:580
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects the "
+""_Service._Proto" syntax, converts "Service" to the "
+"corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when the "
+"result is presented, GNS looks for the GNS-specific "BOX" record "
+"type. A BOX record is a record that contains another record (such as SRV or "
+"TLSA records) and adds a service and protocol number (and the original boxed "
+"record type) to it."
+msgstr ""
+
+#: template/faq.html.j2:596
+msgid ""
+"I receive many "WARNING Calculated flow delay for X at Y for Z". "
+"Should I worry?"
+msgstr ""
+
+#: template/faq.html.j2:598
+msgid ""
+"A: Right now, this is expected and a known cause for high latency in GNUnet. "
+"We have started a major rewrite to address this and other problems, but "
+"until the Transport Next Generation (TNG) is ready, these warnings are "
+"expected."
+msgstr ""
+
+#: template/faq.html.j2:607
+msgid "Error opening `/dev/net/tun': No such file or directory?"
+msgstr ""
+
+#: template/faq.html.j2:609
+msgid ""
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:621
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
+"dns)?"
+msgstr ""
+
+#: template/faq.html.j2:623
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check if "
+"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:635
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:637
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if "
+"your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:645
+msgid ""
+"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:647
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if you "
+"compiled GNUnet the normal way and/or used a binary package, that is highly "
+"unlikely. The more common cause is that you installed GNUnet to a directory "
+"that your linker does not search. There are several ways to fix this that "
+"are described below. If you are 'root' and you installed to a system folder "
+"(such as /usr/local), you want to add the libraries to the system-wide "
+"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
+"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
+"similar path, you obviously have to change \"/usr/local\" accordingly. If "
+"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
+"$USER/\", then you can explicitly tell your linker to search a particular "
+"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
+"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
+"you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:673
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the \"$\") "
+"to your .bashrc or .profile file. You will have to logout and login again to "
+"have this new profile be applied to all shells (including your desktop "
+"environment)."
+msgstr ""
+
+#: template/faq.html.j2:680
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:682
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
+"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
+"always refer to harmless events that require no action. For example, GNUnet "
+"may use an INFO message to indicate that it is currently performing an "
+"expensive operation that will take some time. GNUnet will also use INFO "
+"messages to display information about important configuration values."
+msgstr ""
+
+#: template/faq.html.j2:698
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:700
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
+"P2P networks, GNUnet was designed with security in mind as the highest "
+"priority. We intend on producing a network with comprehensive security "
+"features. Many other P2P networks are open to a wide variety of attacks, and "
+"users have little privacy. GNUnet is also Free Software and thus the source "
+"code is available, so you do not have to worry about being spied upon by the "
+"software. The following table summarises the main differences between GNUnet "
+"and other systems. The information is accurate to the best of our knowledge. "
+"The comparison is difficult since there are sometimes differences between "
+"various implementations of (almost) the same protocol. In general, we pick a "
+"free implementation as the reference implementation since it is possible to "
+"inspect the free code. Also, all of these systems are changing over time and "
+"thus the data below may not be up-to-date. If you find any flaws, please let "
+"us know. Finally, the table is not saying terribly much (it is hard to "
+"compare these systems this briefly), so if you want the real differences, "
+"read the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:814
+msgid ""
+"Another important point of reference are the various anonymous peer-to-peer "
+"networks. Here, there are differences in terms of application domain and how "
+"specifically anonymity is achieved. Anonymous routing is a hard research "
+"topic, so for a superficial comparisson like this one we focus on the "
+"latency. Another important factor is the programming language. Type-safe "
+"languages may offer certain security benefits; however, this may come at the "
+"cost of significant increases in resource consumption which in turn may "
+"reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:827
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:829
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of the "
+"same techniques used to generate reasonable passwords to defend against such "
+"an attack. In any event, we are not trying to hide content; thus, unless the "
+"user is trying to insert information into the network that can only be "
+"shared with a small group of people, there is no real reason to try to "
+"obfuscate the content by choosing a difficult keyword anyway."
+msgstr ""
+
+#: template/faq.html.j2:843
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:845
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all "
+"users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell which "
+"of the peers in the group originated the message. In other words, it should "
+"be difficult to impossible for an adversary to distinguish between the "
+"originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:857
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:859
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
+"its public key) and has a number of addresses it is reachable by (may have "
+"no addresses, for instance when it's behind a NAT). You specify bandwidth "
+"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
+"(how large your on-disk block storage is) . Your node will then proceed to "
+"connect to other nodes, becoming part of the network."
+msgstr ""
+
+#: template/faq.html.j2:874
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:876
+msgid ""
+"A: First, you need to register an account with our weblate system. Please "
+"send an e-mail with the desired target language to translators@gnunet.org or "
+"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
+"sufficient permissions will then grant you access. Naturally, any abuse will "
+"result in the loss of permissions."
+msgstr ""
+
+#: template/faq.html.j2:888
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:890
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly implement. "
+"The best way to actually get a new feature implemented is to do it yourself "
+"--- and to then send us a patch."
+msgstr ""
+
#: template/glossary.html.j2:12
msgid "Ego"
msgstr ""
#: template/glossary.html.j2:14
msgid ""
-"We use the term \"Ego\" to refer to the fact that users in GNUnet can "
-"have multiple unlinkable identities, in the sense of alter egos. The "
-"ability to have more than one identity is crucial, as we may want to keep"
-" our egos for business separate from those we use for political "
-"activities or romance.<br> Egos in GNUnet are technically equivalent to "
-"identities (and the code does not distinguish between them). We simply "
-"sometimes use the term \"ego\" to stress that you can have more than one."
+"We use the term \"Ego\" to refer to the fact that users in GNUnet can have "
+"multiple unlinkable identities, in the sense of alter egos. The ability to "
+"have more than one identity is crucial, as we may want to keep our egos for "
+"business separate from those we use for political activities or romance.<br> "
+"Egos in GNUnet are technically equivalent to identities (and the code does "
+"not distinguish between them). We simply sometimes use the term \"ego\" to "
+"stress that you can have more than one."
msgstr ""
#: template/glossary.html.j2:27
@@ -864,19 +1580,18 @@ msgstr ""
#: template/glossary.html.j2:29
msgid ""
-"In GNUnet users are identified via a public key, and that public key is "
-"then often referred to as the \"Identity\" of the user. However, the "
-"concept is not as draconian as it often is in real life where many are "
-"forced to have one name, one passport and one unique identification "
-"number. <br> As long as identities in GNUnet are simply public keys, "
-"users are free to create any number of identities, and we call those egos"
-" to emphasize the difference. Even though users can create such egos "
-"freely, it is possible to have an ego certified by some certification "
-"authority, resulting in something that more closely resembles the "
-"traditional concept of an identity.<br> For example, a university may "
-"certify the identities of its students such that they can prove that they"
-" are studying. Students may keep their (certified) student identity "
-"separate from other egos that they use for other activities in life."
+"In GNUnet users are identified via a public key, and that public key is then "
+"often referred to as the \"Identity\" of the user. However, the concept is "
+"not as draconian as it often is in real life where many are forced to have "
+"one name, one passport and one unique identification number. <br> As long as "
+"identities in GNUnet are simply public keys, users are free to create any "
+"number of identities, and we call those egos to emphasize the difference. "
+"Even though users can create such egos freely, it is possible to have an ego "
+"certified by some certification authority, resulting in something that more "
+"closely resembles the traditional concept of an identity.<br> For example, a "
+"university may certify the identities of its students such that they can "
+"prove that they are studying. Students may keep their (certified) student "
+"identity separate from other egos that they use for other activities in life."
msgstr ""
#: template/glossary.html.j2:50
@@ -888,10 +1603,10 @@ msgid ""
"A pseudonym is an ego that is specifically intended to not be linked to "
"one's real name. GNUnet users can create many egos, and thus also many "
"pseudonyms. <br> Repeated uses of the same pseudonym are linkable by "
-"definition, as they involve the same public key. Anonymity requires the "
-"use of either the special \"anonymous\" pseudonym (for GNUnet, this is "
-"the neutral element on the elliptic curve) or a throw-away pseudonym that"
-" is only used once."
+"definition, as they involve the same public key. Anonymity requires the use "
+"of either the special \"anonymous\" pseudonym (for GNUnet, this is the "
+"neutral element on the elliptic curve) or a throw-away pseudonym that is "
+"only used once."
msgstr ""
#: template/glossary.html.j2:71
@@ -900,15 +1615,15 @@ msgstr ""
#: template/glossary.html.j2:73
msgid ""
-"The GNU Name System allows every ego (or identity) to securely and "
-"privately associate any number of label-value pairs with an ego. The "
-"values are called record sets following the terminology of the Domain "
-"Name System (DNS). The mapping of labels to record sets for a given ego "
-"is called a namespace. <br> If records are made public and thus "
-"published, it is possible for other users to lookup the record given the "
-"ego's public key and the label. Here, not only the label can thus act as "
-"a passphrase but also the public key -- which despite its name may not be"
-" public knowledge and is never disclosed by the GNS protocol itself."
+"The GNU Name System allows every ego (or identity) to securely and privately "
+"associate any number of label-value pairs with an ego. The values are called "
+"record sets following the terminology of the Domain Name System (DNS). The "
+"mapping of labels to record sets for a given ego is called a namespace. <br> "
+"If records are made public and thus published, it is possible for other "
+"users to lookup the record given the ego's public key and the label. Here, "
+"not only the label can thus act as a passphrase but also the public key -- "
+"which despite its name may not be public knowledge and is never disclosed by "
+"the GNS protocol itself."
msgstr ""
#: template/glossary.html.j2:89
@@ -917,17 +1632,17 @@ msgstr ""
#: template/glossary.html.j2:91
msgid ""
-"A \"peer\" is an instance of GNUnet with its own per-instance public key "
-"and network addresses. Technically, it is possible to run multiple peers "
-"on the same host, but this only makes sense for testing. <br> By design "
-"GNUnet supports multiple users to share the same peer, just as UNIX is a "
-"multi-user system. A \"peer\" typically consists of a set of foundational"
-" GNUnet services running as the \"gnunet\" user and allowing all users in"
-" the \"gnunet\" group to utilize the API. On multi-user systems, "
-"additional \"personalized\" services may be required per user. <br> While"
-" peers are also identified by public keys, these public keys are "
-"completely unrelated to egos or identities. Namespaces cannot be "
-"associated with a peer, only with egos."
+"A \"peer\" is an instance of GNUnet with its own per-instance public key and "
+"network addresses. Technically, it is possible to run multiple peers on the "
+"same host, but this only makes sense for testing. <br> By design GNUnet "
+"supports multiple users to share the same peer, just as UNIX is a multi-user "
+"system. A \"peer\" typically consists of a set of foundational GNUnet "
+"services running as the \"gnunet\" user and allowing all users in the "
+"\"gnunet\" group to utilize the API. On multi-user systems, additional "
+"\"personalized\" services may be required per user. <br> While peers are "
+"also identified by public keys, these public keys are completely unrelated "
+"to egos or identities. Namespaces cannot be associated with a peer, only "
+"with egos."
msgstr ""
#: template/gns.html.j2:13 template/gnurl.html.j2:60
@@ -937,28 +1652,24 @@ msgstr ""
#: template/gns.html.j2:15
msgid ""
"The Domain Name System today enables traffic amplification attacks, "
-"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive "
-"cyber war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as "
-"DoT, DoH, DNSSEC, DPRIVE and the like will not fix this. This is why we "
-"built the GNU Name System (GNS), a secure, decentralized name system "
-"built on top of GNUnet."
+"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive cyber "
+"war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as DoT, DoH, "
+"DNSSEC, DPRIVE and the like will not fix this. This is why we built the GNU "
+"Name System (GNS), a secure, decentralized name system built on top of "
+"GNUnet."
msgstr ""
#: template/gns.html.j2:28
msgid "Overview"
msgstr ""
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
-
#: template/gns.html.j2:39
msgid ""
"The GNU Name System (GNS) is secure and decentralized naming system. It "
-"allows its users to register names as top-level domains (TLDs) and "
-"resolve other namespaces within their TLDs. <br/> GNS is designed to "
-"provide: <ul> <li>Censorship resistance</li> <li>Query privacy</li> "
-"<li>Secure name resolution</li> <li>Compatibility with DNS</li>"
+"allows its users to register names as top-level domains (TLDs) and resolve "
+"other namespaces within their TLDs. <br/> GNS is designed to provide: <ul> "
+"<li>Censorship resistance</li> <li>Query privacy</li> <li>Secure name "
+"resolution</li> <li>Compatibility with DNS</li>"
msgstr ""
#: template/gns.html.j2:52
@@ -967,23 +1678,23 @@ msgstr ""
#: template/gnurl.html.j2:21
msgid ""
-"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support "
-"only HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend "
-"(GnuTLS) to ensure a small footprint and uniform experience for "
-"developers regardless of how libcurl was compiled."
+"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support only "
+"HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend (GnuTLS) to "
+"ensure a small footprint and uniform experience for developers regardless of "
+"how libcurl was compiled."
msgstr ""
#: template/gnurl.html.j2:30
msgid ""
-"Our main usecase is for GNUnet and Taler, but it might be usable for "
-"others, hence we're releasing the code to the general public."
+"Our main usecase is for GNUnet and Taler, but it might be usable for others, "
+"hence we're releasing the code to the general public."
msgstr ""
#: template/gnurl.html.j2:37
msgid ""
"libgnurl is released under the same license as libcurl. Please read the "
-"README for instructions, as you must supply the correct options to "
-"configure to get a proper build of libgnurl."
+"README for instructions, as you must supply the correct options to configure "
+"to get a proper build of libgnurl."
msgstr ""
#: template/gnurl.html.j2:48
@@ -992,58 +1703,55 @@ msgstr ""
#: template/gnurl.html.j2:50
msgid ""
-"Large parts of the following 6 paragraphs are old and need to be "
-"rewritten."
+"Large parts of the following 6 paragraphs are old and need to be rewritten."
msgstr ""
#: template/gnurl.html.j2:62
msgid ""
-"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, "
-"but other variants are used by some distributions. Supporting other "
-"crypto backends would again expose us to a wider array of security "
-"issues, may create licensing issues and most importantly introduce new "
-"bugs as some crypto backends are known to introduce subtle runtime "
-"issues. While it is possible to have two versions of libcurl installed on"
-" the same system, this is error-prone, especially as if we are linked "
-"against the wrong version, the bugs that arise might be rather subtle."
+"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, but "
+"other variants are used by some distributions. Supporting other crypto "
+"backends would again expose us to a wider array of security issues, may "
+"create licensing issues and most importantly introduce new bugs as some "
+"crypto backends are known to introduce subtle runtime issues. While it is "
+"possible to have two versions of libcurl installed on the same system, this "
+"is error-prone, especially as if we are linked against the wrong version, "
+"the bugs that arise might be rather subtle."
msgstr ""
#: template/gnurl.html.j2:75
msgid ""
-"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, "
-"it would anyway be necessary to recompile cURL for GNUnet. But what "
-"happens if one links cURL against this version of GnuTLS? Well, first one"
-" would install GnuTLS by hand in the system. Then, we build cURL. cURL "
-"will build against it just fine, but the linker will eventually complain "
-"bitterly. The reason is that cURL also links against a bunch of other "
-"system libraries (gssapi, ldap, ssh2, rtmp, krb5, sasl2, see discussion "
-"on obscure protocols above), which --- as they are part of the "
-"distribution --- were linked against an older version of GnuTLS. As a "
-"result, the same binary would be linked against two different versions of"
-" GnuTLS. That is typically a recipe for disaster. Thus, in order to avoid"
-" updating a dozen system libraries (and having two versions of those "
-"installed), it is necessary to disable all of those cURL features that "
-"GNUnet does not use, and there are many of those. For GNUnet, the more "
-"obscure protocols supported by cURL are close to dead code --- mostly "
-"harmless, but not useful. However, as some application may use one of "
-"those features, distributions are typically forced to enable all of those"
-" features, and thus including security issues that might arise from that "
-"code."
+"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, it "
+"would anyway be necessary to recompile cURL for GNUnet. But what happens if "
+"one links cURL against this version of GnuTLS? Well, first one would install "
+"GnuTLS by hand in the system. Then, we build cURL. cURL will build against "
+"it just fine, but the linker will eventually complain bitterly. The reason "
+"is that cURL also links against a bunch of other system libraries (gssapi, "
+"ldap, ssh2, rtmp, krb5, sasl2, see discussion on obscure protocols above), "
+"which --- as they are part of the distribution --- were linked against an "
+"older version of GnuTLS. As a result, the same binary would be linked "
+"against two different versions of GnuTLS. That is typically a recipe for "
+"disaster. Thus, in order to avoid updating a dozen system libraries (and "
+"having two versions of those installed), it is necessary to disable all of "
+"those cURL features that GNUnet does not use, and there are many of those. "
+"For GNUnet, the more obscure protocols supported by cURL are close to dead "
+"code --- mostly harmless, but not useful. However, as some application may "
+"use one of those features, distributions are typically forced to enable all "
+"of those features, and thus including security issues that might arise from "
+"that code."
msgstr ""
#: template/gnurl.html.j2:99
msgid ""
-"So to use a modern version of GnuTLS, a sane approach is to disable all "
-"of the \"optional\" features of cURL that drag in system libraries that "
-"link against the older GnuTLS. That works, except that one should then "
-"NEVER install that version of libcurl in say /usr or /usr/local, as that "
-"may break other parts of the system that might depend on these features "
-"that we just disabled. Libtool versioning doesn't help here, as it is not"
-" intended to deal with libraries that have optional features. Naturally, "
-"installing cURL somewhere else is also problematic, as we now need to be "
-"really careful that the linker will link GNUnet against the right "
-"version. Note that none of this can really be trivially fixed by the cURL"
-" developers."
+"So to use a modern version of GnuTLS, a sane approach is to disable all of "
+"the \"optional\" features of cURL that drag in system libraries that link "
+"against the older GnuTLS. That works, except that one should then NEVER "
+"install that version of libcurl in say /usr or /usr/local, as that may break "
+"other parts of the system that might depend on these features that we just "
+"disabled. Libtool versioning doesn't help here, as it is not intended to "
+"deal with libraries that have optional features. Naturally, installing cURL "
+"somewhere else is also problematic, as we now need to be really careful that "
+"the linker will link GNUnet against the right version. Note that none of "
+"this can really be trivially fixed by the cURL developers."
msgstr ""
#: template/gnurl.html.j2:118
@@ -1054,19 +1762,19 @@ msgstr ""
#, python-format
msgid ""
"How does forking fix it? Easy. First, we can get rid of all of the "
-"compatibility issues --- if you use libgnurl, you state that you "
-"don't need anything but HTTP/HTTPS. Those applications that need "
-"more, should stick with the original cURL. Those that do not, can choose "
-"to move to something simpler. As the library gets a new name, we do not "
-"have to worry about tons of packages breaking as soon as one rebuilds it."
-" So renaming itself and saying that \"libgnurl = libcurl with only "
-"HTTP/HTTPS support and GnuTLS\" fixes 99%% of the problems that darkened "
-"my mood. Note that this pretty much CANNOT be done without a fork, as "
-"renaming is an essential part of the fix. Now, there might be creative "
-"solutions to achieve the same thing within the standard cURL build "
-"system, but this was deemed to be too much work when gnurl was originally"
-" started. The changes libgnurl makes to curl are miniscule and can easily"
-" be applied again and again whenever libcurl makes a new release."
+"compatibility issues --- if you use libgnurl, you state that you don't "
+"need anything but HTTP/HTTPS. Those applications that need more, should "
+"stick with the original cURL. Those that do not, can choose to move to "
+"something simpler. As the library gets a new name, we do not have to worry "
+"about tons of packages breaking as soon as one rebuilds it. So renaming "
+"itself and saying that \"libgnurl = libcurl with only HTTP/HTTPS support and "
+"GnuTLS\" fixes 99%% of the problems that darkened my mood. Note that this "
+"pretty much CANNOT be done without a fork, as renaming is an essential part "
+"of the fix. Now, there might be creative solutions to achieve the same thing "
+"within the standard cURL build system, but this was deemed to be too much "
+"work when gnurl was originally started. The changes libgnurl makes to curl "
+"are miniscule and can easily be applied again and again whenever libcurl "
+"makes a new release."
msgstr ""
#: template/gnurl.html.j2:142
@@ -1075,14 +1783,13 @@ msgstr ""
#: template/gnurl.html.j2:144
msgid ""
-"Projects that use cURL only for HTTP/HTTPS and that would work with "
-"GnuTLS should be able to switch to libgnurl by changing \"-lcurl\" to "
-"\"-lgnurl\". That's it. No changes to the source code should be "
-"required, as libgnurl strives for bug-for-bug compatibility with the "
-"HTTP/HTTPS/GnuTLS subset of cURL. We might add new features relating to "
-"this core subset if they are proposed, but so far we have kept our "
-"changes minimal and no additions to the original curl source have been "
-"written."
+"Projects that use cURL only for HTTP/HTTPS and that would work with GnuTLS "
+"should be able to switch to libgnurl by changing \"-lcurl\" to \"-lgnurl\". "
+"That's it. No changes to the source code should be required, as libgnurl "
+"strives for bug-for-bug compatibility with the HTTP/HTTPS/GnuTLS subset of "
+"cURL. We might add new features relating to this core subset if they are "
+"proposed, but so far we have kept our changes minimal and no additions to "
+"the original curl source have been written."
msgstr ""
#: template/gnurl.html.j2:161
@@ -1091,15 +1798,15 @@ msgstr ""
#: template/gnurl.html.j2:163
msgid ""
-"libgnurl and gnurl are not intended to be used as a replacement for curl "
-"for users: <br> This does not mean there is no confidence in the work "
-"done with gnurl, it means that tools which expect curl or libcurl will "
-"not make use of a different named binary and library. If you know what "
-"you are doing, you should be able to use gnurl as part of your tooling in"
-" place of curl. We do not recommend to do so however, as the only usage "
-"it is tested for <em>so far</em> is as part of Taler's and "
-"GNunet's build-system. <br> Since no conflicts in filenames occur you"
-" are not expected to remove curl to make use of gnurl and viceversa."
+"libgnurl and gnurl are not intended to be used as a replacement for curl for "
+"users: <br> This does not mean there is no confidence in the work done with "
+"gnurl, it means that tools which expect curl or libcurl will not make use of "
+"a different named binary and library. If you know what you are doing, you "
+"should be able to use gnurl as part of your tooling in place of curl. We do "
+"not recommend to do so however, as the only usage it is tested for <em>so "
+"far</em> is as part of Taler's and GNunet's build-system. <br> Since "
+"no conflicts in filenames occur you are not expected to remove curl to make "
+"use of gnurl and viceversa."
msgstr ""
#: template/gnurl.html.j2:188
@@ -1112,16 +1819,15 @@ msgstr ""
#: template/gnurl.html.j2:211
msgid ""
-"Releases are published on <a "
-"href=\"https://ftpmirror.gnu.org/gnu/gnunet/\";>ftpmirror.gnu.org/gnu/gnunet</a>."
-" gnurl is available from within a variety of distributions and package "
-"managers. Some Package Managers which include gnurl are: <a "
-"href=\"https://www.gnu.org/software/guix/\";>GNU Guix</a> (available as "
-"\"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> through the "
-"collaborative ebuild collection <a href=\"https://git.gnunet.org";
-"/youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a "
-"href=\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a "
-"href=\"https://pkgsrc.org\";>pkgsrc</a>."
+"Releases are published on <a href=\"https://ftpmirror.gnu.org/gnu/gnunet/";
+"\">ftpmirror.gnu.org/gnu/gnunet</a>. gnurl is available from within a "
+"variety of distributions and package managers. Some Package Managers which "
+"include gnurl are: <a href=\"https://www.gnu.org/software/guix/\";>GNU Guix</"
+"a> (available as \"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> "
+"through the collaborative ebuild collection <a href=\"https://git.gnunet.org/";
+"youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a href="
+"\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a href=\"https://";
+"pkgsrc.org\">pkgsrc</a>."
msgstr ""
#: template/gnurl.html.j2:228
@@ -1130,17 +1836,17 @@ msgstr ""
#: template/gnurl.html.j2:230
msgid ""
-"We suggest to closely follow release announcements, as they might "
-"indicate changes in how gnurl is to be build. <br> If your package "
-"manager provides a binary build or build instructions to build gnurl from"
-" source automated and integrated with your environment, we strongly "
-"suggest to use this binary build. <br> There are two ways to build gnurl."
-" The first one builds from the most recent git tag, the second one uses "
-"the distributed tarball. Distributors generally are supposed to build "
-"from the tarball, but we describe both methods here. Both methods are "
-"written with a NetBSD 9 userland in mind, substitute tools as necessary. "
-"<br> You should <b>avoid</b> building gnurl from the tip of the default "
-"git branch, as only tags are considered to be stable and approved builds."
+"We suggest to closely follow release announcements, as they might indicate "
+"changes in how gnurl is to be build. <br> If your package manager provides a "
+"binary build or build instructions to build gnurl from source automated and "
+"integrated with your environment, we strongly suggest to use this binary "
+"build. <br> There are two ways to build gnurl. The first one builds from the "
+"most recent git tag, the second one uses the distributed tarball. "
+"Distributors generally are supposed to build from the tarball, but we "
+"describe both methods here. Both methods are written with a NetBSD 9 "
+"userland in mind, substitute tools as necessary. <br> You should <b>avoid</"
+"b> building gnurl from the tip of the default git branch, as only tags are "
+"considered to be stable and approved builds."
msgstr ""
#: template/gnurl.html.j2:251
@@ -1149,8 +1855,8 @@ msgstr ""
#: template/gnurl.html.j2:253
msgid ""
-"If you want to verify the signature, install an OpenPGP compatible tool "
-"such as security/gnupgp2 (and set it up). Assuming you use pkgin:"
+"If you want to verify the signature, install an OpenPGP compatible tool such "
+"as security/gnupgp2 (and set it up). Assuming you use pkgin:"
msgstr ""
#: template/gnurl.html.j2:267
@@ -1163,8 +1869,7 @@ msgstr ""
#: template/gnurl.html.j2:276
msgid ""
-"Fetch the release, the signature, the checksum file as well as its "
-"signature:"
+"Fetch the release, the signature, the checksum file as well as its signature:"
msgstr ""
#: template/gnurl.html.j2:295
@@ -1213,8 +1918,8 @@ msgstr ""
#: template/gnurl.html.j2:371
msgid ""
-"Follow the steps above, but instead of downloading the tarball, clone the"
-" git tag you want to build from."
+"Follow the steps above, but instead of downloading the tarball, clone the "
+"git tag you want to build from."
msgstr ""
#: template/gnurl.html.j2:382
@@ -1223,10 +1928,9 @@ msgstr ""
#: template/gnurl.html.j2:384
msgid ""
-"You can report bugs on our bug tracker: <a "
-"href=\"https://bugs.gnunet.org/\";>bugs.gnunet.org</a>. Alternatively you "
-"can use our bug mailinglist, but we prefer to track bugs on the "
-"bugtracker."
+"You can report bugs on our bug tracker: <a href=\"https://bugs.gnunet.org/";
+"\">bugs.gnunet.org</a>. Alternatively you can use our bug mailinglist, but "
+"we prefer to track bugs on the bugtracker."
msgstr ""
#: template/gnurl.html.j2:395
@@ -1237,10 +1941,9 @@ msgstr ""
msgid ""
"gnurl/libgnurl is looking for a new maintainer. Releases after version "
"7.69.1 and up to version 7.72.0 were signed with the OpenPGP Key "
-"<b>0xD6B570842F7E7F8D</b> (<a "
-"href=\"https://keys.openpgp.org/search?q=6115012DEA3026F62A98A556D6B570842F7E7F8D\";>keys.openpgp.org</a>),"
-" with the key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E"
-" 7F8D</b>."
+"<b>0xD6B570842F7E7F8D</b> (<a href=\"https://keys.openpgp.org/search?";
+"q=6115012DEA3026F62A98A556D6B570842F7E7F8D\">keys.openpgp.org</a>), with the "
+"key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E 7F8D</b>."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:7
@@ -1254,68 +1957,65 @@ msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:18
msgid ""
"In the context of Google Summer of Code 2018, my mentor (Martin "
-"Schanzenbach) and I have worked on creating and extending the REST API of"
-" GNUnet. Currently, we mirrored the functionality of following commands:"
+"Schanzenbach) and I have worked on creating and extending the REST API of "
+"GNUnet. Currently, we mirrored the functionality of following commands:"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:32
msgid ""
-"Additionally, we developed a website with the Javascript framework "
-"Angular 6 and the design framework iotaCSS to use the new REST API. The "
-"REST API of GNUnet is now documented with Sphinx."
+"Additionally, we developed a website with the Javascript framework Angular 6 "
+"and the design framework iotaCSS to use the new REST API. The REST API of "
+"GNUnet is now documented with Sphinx."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:41
msgid ""
-"... when you can use the command line tools? We need to keep in mind, "
-"that everyone has the right to stay secure and private but not everyone "
-"feels comfortable using a terminal. The further developed REST access to "
-"GNUnet APIs in addition to the new web application allows new users to "
-"interact with GNUnet over a well known tool: their browsers. This "
-"addition to the C API and the command line tools may attract new users "
-"and developers."
+"... when you can use the command line tools? We need to keep in mind, that "
+"everyone has the right to stay secure and private but not everyone feels "
+"comfortable using a terminal. The further developed REST access to GNUnet "
+"APIs in addition to the new web application allows new users to interact "
+"with GNUnet over a well known tool: their browsers. This addition to the C "
+"API and the command line tools may attract new users and developers."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:54
msgid ""
"<li> The REST API developed in GNUnet<br> The REST API is already merged "
-"into the gnunet.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet.git/\";>GNUnet Main Git</a>).<br /> "
-"To use the new features, clone the repository and follow the <a "
-"href=\"https://gnunet.org/en/install.html\";>Installation</a> on "
-"gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
-"</li> <li> The Web Application<br> The web application is available under"
-" the gnunet-webui.git repository (<a href=\"https://gnunet.org/git";
-"/gnunet-webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the"
-" newest version of 'node' and 'yarn'. Dependent on your system, you may "
-"need to download newer versions and install them manually and not over "
-"your packet manager. After the installation succeeded, you need to clone "
-"the repository. Then, you need to run \"yarn install\" and \"yarn start\""
-" for testing purposes. To deploy the website (keep in mind, that this "
-"website communicates with another localhost instance) use \"yarn build\" "
-"for building the web application and use the output in the 'dist' "
-"directory. </li> <li> The Documentation<br /> The documentation is "
-"available under the gnunet-rest-api.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet-rest-api.git/\";>GNUnet REST API "
-"Docmentation Git</a>).<br /> Clone the repository and \"make html\". Then"
-" open the 'index.html' under 'build/html/'. </li>"
+"into the gnunet.git repository (<a href=\"https://gnunet.org/git/gnunet.git/";
+"\">GNUnet Main Git</a>).<br /> To use the new features, clone the repository "
+"and follow the <a href=\"https://gnunet.org/en/install.html\";>Installation</"
+"a> on gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
+"</li> <li> The Web Application<br> The web application is available under "
+"the gnunet-webui.git repository (<a href=\"https://gnunet.org/git/gnunet-";
+"webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the newest "
+"version of 'node' and 'yarn'. Dependent on your system, you may need to "
+"download newer versions and install them manually and not over your packet "
+"manager. After the installation succeeded, you need to clone the repository. "
+"Then, you need to run \"yarn install\" and \"yarn start\" for testing "
+"purposes. To deploy the website (keep in mind, that this website "
+"communicates with another localhost instance) use \"yarn build\" for "
+"building the web application and use the output in the 'dist' directory. </"
+"li> <li> The Documentation<br /> The documentation is available under the "
+"gnunet-rest-api.git repository (<a href=\"https://gnunet.org/git/gnunet-rest-";
+"api.git/\">GNUnet REST API Docmentation Git</a>).<br /> Clone the repository "
+"and \"make html\". Then open the 'index.html' under 'build/html/'. </li>"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:91
msgid ""
-"Please, give it a try and contact me, if you find any bugs or "
-"unintentional features. ;)"
+"Please, give it a try and contact me, if you find any bugs or unintentional "
+"features. ;)"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:98
msgid ""
"Right now, the build process of the web application may be a little too "
-"complex for a casual user. We may be able to solve this by using "
-"docker.<br /> Additionally, the web application does not prevent wrong "
-"inputs but responds with error messages. Adding GNUnet Records is "
-"currently only usable for people, who know how a GNS Record looks like. "
-"This can be adapted to each record type.<br /> Last but not least, "
-"additional features, design changes, etc..."
+"complex for a casual user. We may be able to solve this by using docker.<br /"
+"> Additionally, the web application does not prevent wrong inputs but "
+"responds with error messages. Adding GNUnet Records is currently only usable "
+"for people, who know how a GNS Record looks like. This can be adapted to "
+"each record type.<br /> Last but not least, additional features, design "
+"changes, etc..."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:111
@@ -1342,100 +2042,95 @@ msgstr ""
msgid ""
"As a GNU project, GNUnet has participated in the Google Summer of Code "
"(GSoC) for a number of years. This page lists all current, past, and "
-"finished projects. If you want to participate and apply for any of the "
-"ideas for 2020 below or any past project which is not yet finished (or "
-"even your own idea), please contact us either in IRC or mailing list."
+"finished projects. If you want to participate and apply for any of the ideas "
+"for 2020 below or any past project which is not yet finished (or even your "
+"own idea), please contact us either in IRC or mailing list."
msgstr ""
#: template/gsoc.html.j2:34
msgid ""
-"The GNUnet team is currently working on a transport layer rewrite in "
-"order to fix core issues with connectivity. This new component is "
-"currently developed under the name \"TNG\". What is currently known as "
-"\"transport plugins\" will in the TNG be represented as "
-"\"communicators\". Communicators are processes with a well defined API "
-"that allow to connect peers over a specific protocol. The primary "
-"protocol which are already implemented are UNIX sockets, UDP sockets, and"
-" TCP sockets. For a truly resilient network, other connectivity options "
-"such as WiFi mesh, Bluetooth, HTTP(S), QUIC or even more obscure "
-"alternatives such as radio are required. In this project, the goal is to "
-"select, implement and test new communicators. While TNG is not yet ready,"
-" communicators can, by design, be developed and tested against the "
-"current API. We expect that this project can be worked on by multiple "
+"The GNUnet team is currently working on a transport layer rewrite in order "
+"to fix core issues with connectivity. This new component is currently "
+"developed under the name \"TNG\". What is currently known as \"transport "
+"plugins\" will in the TNG be represented as \"communicators\". Communicators "
+"are processes with a well defined API that allow to connect peers over a "
+"specific protocol. The primary protocol which are already implemented are "
+"UNIX sockets, UDP sockets, and TCP sockets. For a truly resilient network, "
+"other connectivity options such as WiFi mesh, Bluetooth, HTTP(S), QUIC or "
+"even more obscure alternatives such as radio are required. In this project, "
+"the goal is to select, implement and test new communicators. While TNG is "
+"not yet ready, communicators can, by design, be developed and tested against "
+"the current API. We expect that this project can be worked on by multiple "
"students as there are a lot of protocols to choose from. The tasks would "
"consist of: <ol> <li>Deciding which communicators to implement.</li> "
-"<li>Test the communicators.</li> <li>Documentation.</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of HTTPS, QUIC, Bluetooth or WiFi.</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Average, but depends on selected protocols. "
-"<br/> <strong>Mentors:</strong> Martin Schanzenbach, t3sserakt"
+"<li>Test the communicators.</li> <li>Documentation.</li> </ol> Advantageous "
+"skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge of HTTPS, QUIC, "
+"Bluetooth or WiFi.</li> </ol> <br/> <strong>Difficulty:</strong> Average, "
+"but depends on selected protocols. <br/> <strong>Mentors:</strong> Martin "
+"Schanzenbach, t3sserakt"
msgstr ""
#: template/gsoc.html.j2:79
msgid ""
-"The REST API currently only supports a single user system. This is an "
-"issue as on multi-user systems, access control must be enfoced on a per-"
-"user basis. In this project, the REST service must be extended to support"
-" user authentication. This includes the correct handling of user context "
-"switches. <ol> <li>Implement user authentication.</li> <li>Test the "
-"access control.</li> <li>Document the changes to the REST API.</li> </ol>"
-" Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of user authentication subsystems on Linux/Unix.</li> <li>REST/HTTP "
-"Authentication methods</li> </ol> <br/> <strong>Difficulty:</strong> "
-"Beginner <br/> <strong>Mentors:</strong> Martin Schanzenbach"
+"The REST API currently only supports a single user system. This is an issue "
+"as on multi-user systems, access control must be enfoced on a per-user "
+"basis. In this project, the REST service must be extended to support user "
+"authentication. This includes the correct handling of user context switches. "
+"<ol> <li>Implement user authentication.</li> <li>Test the access control.</"
+"li> <li>Document the changes to the REST API.</li> </ol> Advantageous skills/"
+"languages/frameworks: <ol> <li>C</li> <li>Knowledge of user authentication "
+"subsystems on Linux/Unix.</li> <li>REST/HTTP Authentication methods</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:111
msgid ""
-"reclaimID is a decentralized identity system build on top of the GNU Name"
-" System. Currently, there is a Webextension which uses the GNUnet <a "
-"href=\"https://rest.gnunet.org\";>REST API</a>. In order to improve "
-"adoption and ease of use, this project aims to include a full GNUnet node"
-" within the Webextention as a fallback. GNUnet can be compiled to Web "
-"Assembly or JavaScript as demonstrated <a "
-"href=\"https://gnunet.io\";>here</a>. The idea is to improve upon this "
-"concept and support more of GNUnet's subsystems. The difficulty of this "
-"project largely depends on the students proficiency with build tools, "
-"emscripten and improvisation skills. There non-exhaustive task list would"
-" be: <ol> <li>Improve existing GNUnet emscripten build to include more "
-"subsystems.</li> <li>Integrate the result into a Webextention.</li> "
+"reclaimID is a decentralized identity system build on top of the GNU Name "
+"System. Currently, there is a Webextension which uses the GNUnet <a href="
+"\"https://rest.gnunet.org\";>REST API</a>. In order to improve adoption and "
+"ease of use, this project aims to include a full GNUnet node within the "
+"Webextention as a fallback. GNUnet can be compiled to Web Assembly or "
+"JavaScript as demonstrated <a href=\"https://gnunet.io\";>here</a>. The idea "
+"is to improve upon this concept and support more of GNUnet's subsystems. The "
+"difficulty of this project largely depends on the students proficiency with "
+"build tools, emscripten and improvisation skills. There non-exhaustive task "
+"list would be: <ol> <li>Improve existing GNUnet emscripten build to include "
+"more subsystems.</li> <li>Integrate the result into a Webextention.</li> "
"<li>Integrate the result into the re:claimID Webextension</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> "
-"<li>emscripten</li> <li>Webextensions</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Challenging <br/> <strong>Mentors:</strong> "
-"Martin Schanzenbach"
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>emscripten</"
+"li> <li>Webextensions</li> </ol> <br/> <strong>Difficulty:</strong> "
+"Challenging <br/> <strong>Mentors:</strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:147
msgid ""
-"Currently, the keys in our statistics database are too verbose. For "
-"example: </p> <p> nse # flood messages received: 13<br/> nse # peers "
-"connected: 4<br/> nse # nodes in the network (estimate): 203<br/> nse # "
-"flood messages started: 5<br/> nse # estimated network diameter: 3<br/> "
-"nse # flood messages transmitted: 10<br/> </p> <p> With such verbose keys"
-" there's no easy way to form compact JSON document or entries for time-"
-"series database. And you can't query single stats without having to "
-"copypaste the line exactly and put in quotes. In short, the goals are "
-"to... <ol> <li>Think of a way how statistics entries can be made "
-"canonical.</li> <li>Implement the change and migrate existing uses.</li> "
-"<li>Document the format(s) and define an appropriate registration "
-"mechanism for identifiers</li> </ol> Relevant bugs: <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> "
-"</ol> <br/> <strong>Difficulty:</strong> Beginner <br/> "
-"<strong>Mentors:</strong> Martin Schanzenbach"
+"Currently, the keys in our statistics database are too verbose. For example: "
+"</p> <p> nse # flood messages received: 13<br/> nse # peers connected: 4<br/"
+"> nse # nodes in the network (estimate): 203<br/> nse # flood messages "
+"started: 5<br/> nse # estimated network diameter: 3<br/> nse # flood "
+"messages transmitted: 10<br/> </p> <p> With such verbose keys there's no "
+"easy way to form compact JSON document or entries for time-series database. "
+"And you can't query single stats without having to copypaste the line "
+"exactly and put in quotes. In short, the goals are to... <ol> <li>Think of a "
+"way how statistics entries can be made canonical.</li> <li>Implement the "
+"change and migrate existing uses.</li> <li>Document the format(s) and define "
+"an appropriate registration mechanism for identifiers</li> </ol> Relevant "
+"bugs: <a href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:187
msgid ""
-"The goal is to either build upon the (outdated) <a "
-"href=\"https://github.com/canndrew/gnunet-rs\";>GNUnet Rust bindings</a> "
-"or to follow the path of <a href=\"GNUnet Go\">https://github.com/bfix";
-"/gnunet-go</a> which tries to reimplement most of the GNUnet stack. The "
-"end result should be an extension template for GNUnet in the form of the "
-"existing <a href=\"https://git.gnunet.org/gnunet-ext.git/\";>C "
-"template</a> which allows to quickly start implementing services and "
-"libraries for GNUnet."
+"The goal is to either build upon the (outdated) <a href=\"https://github.com/";
+"canndrew/gnunet-rs\">GNUnet Rust bindings</a> or to follow the path of <a "
+"href=\"GNUnet Go\">https://github.com/bfix/gnunet-go</a> which tries to "
+"reimplement most of the GNUnet stack. The end result should be an extension "
+"template for GNUnet in the form of the existing <a href=\"https://git.gnunet.";
+"org/gnunet-ext.git/\">C template</a> which allows to quickly start "
+"implementing services and libraries for GNUnet."
msgstr ""
#: template/gsoc.html.j2:198 template/gsoc.html.j2:652
@@ -1460,27 +2155,26 @@ msgstr ""
#: template/gsoc.html.j2:229
msgid ""
-"Includes: Implementation of rudimentary Android compatibility for GNUnet,"
-" in part by porting the GNUnet utils scheduler to act as a thin wrapper "
-"over libuv."
+"Includes: Implementation of rudimentary Android compatibility for GNUnet, in "
+"part by porting the GNUnet utils scheduler to act as a thin wrapper over "
+"libuv."
msgstr ""
#: template/gsoc.html.j2:236
msgid ""
-"<strong>Mentors:</strong> <a href=\"https://www.goebel-";
-"consult.de/\">Hartmut Goebel</a>, Jeff Burdges, Christian Grothoff"
+"<strong>Mentors:</strong> <a href=\"https://www.goebel-consult.de/\";>Hartmut "
+"Goebel</a>, Jeff Burdges, Christian Grothoff"
msgstr ""
#: template/gsoc.html.j2:245
msgid ""
-"There is a push for migrating our CI to Gitlab. The CI should eventually "
-"not just run \"make check\" on various platforms, but also perform tests "
-"with multiple peers running in different VMs with specific network "
-"topologies (i.e. NAT) between them being simulated. The CI should also be"
-" integrated with Gauger for performance regression analysis. Running jobs"
-" only when dependencies have changed and scripting more granular triggers"
-" or ideally automatic dependency discovery (as done by the autotools) is "
-"also important."
+"There is a push for migrating our CI to Gitlab. The CI should eventually not "
+"just run \"make check\" on various platforms, but also perform tests with "
+"multiple peers running in different VMs with specific network topologies (i."
+"e. NAT) between them being simulated. The CI should also be integrated with "
+"Gauger for performance regression analysis. Running jobs only when "
+"dependencies have changed and scripting more granular triggers or ideally "
+"automatic dependency discovery (as done by the autotools) is also important."
msgstr ""
#: template/gsoc.html.j2:257
@@ -1489,19 +2183,18 @@ msgstr ""
#: template/gsoc.html.j2:267
msgid ""
-"One great problem of the current Internet is the lack of "
-"disintermediation. When people want to talk they need a chat service. "
-"When they want to share files they need a file transfer service. Although"
-" GNUnet already possesses quite advanced integration into Linux "
-"networking, a little extra work is needed for existing applications like "
-"irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by"
-" using a GNS hostname like friend.gnu. Once people have added a person to"
-" their GNS they can immediately message, exchange files and suchlike "
-"directly, with nothing but the GNUnet in the middle, using applications "
-"that have been distributed with unix systems ever since the 1980's. We "
-"can produce an OS distribution where these things work out of the box "
-"with the nicknames of people instead of cloud services. For more "
-"information and context, read"
+"One great problem of the current Internet is the lack of disintermediation. "
+"When people want to talk they need a chat service. When they want to share "
+"files they need a file transfer service. Although GNUnet already possesses "
+"quite advanced integration into Linux networking, a little extra work is "
+"needed for existing applications like irc, www, ftp, rsh, nntpd to run over "
+"it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. "
+"Once people have added a person to their GNS they can immediately message, "
+"exchange files and suchlike directly, with nothing but the GNUnet in the "
+"middle, using applications that have been distributed with unix systems ever "
+"since the 1980's. We can produce an OS distribution where these things work "
+"out of the box with the nicknames of people instead of cloud services. For "
+"more information and context, read"
msgstr ""
#: template/gsoc.html.j2:288
@@ -1510,8 +2203,7 @@ msgstr ""
#: template/gsoc.html.j2:296
msgid ""
-"Implement the AnycastExit spec to enable GNUnet clients to connect over "
-"Tor."
+"Implement the AnycastExit spec to enable GNUnet clients to connect over Tor."
msgstr ""
#: template/gsoc.html.j2:302 template/gsoc.html.j2:337
@@ -1522,9 +2214,9 @@ msgstr ""
#: template/gsoc.html.j2:307
msgid ""
"Note: There was a Special TLDs spec to allow Tor to resolve domain names "
-"using GNS over Tor too, but currently that's on hold until folks think "
-"more about how names should be moved around the local system. We're "
-"calling this more collaborative approach NSS2 for now."
+"using GNS over Tor too, but currently that's on hold until folks think more "
+"about how names should be moved around the local system. We're calling this "
+"more collaborative approach NSS2 for now."
msgstr ""
#: template/gsoc.html.j2:316 template/gsoc.html.j2:456
@@ -1534,17 +2226,16 @@ msgstr ""
#: template/gsoc.html.j2:329
msgid ""
-"Improve the Rust implementation of GNUnet utils, possibly including "
-"adding support for asynchronous IO using mio, or perhaps a higher level "
-"asynchronous IO library built upon it, such as rotor, mioco, eventual_io,"
-" or gj."
+"Improve the Rust implementation of GNUnet utils, possibly including adding "
+"support for asynchronous IO using mio, or perhaps a higher level "
+"asynchronous IO library built upon it, such as rotor, mioco, eventual_io, or "
+"gj."
msgstr ""
#: template/gsoc.html.j2:345
msgid ""
-"Implementation of a replacement for PANDA (see Pond) with better "
-"security, and maybe integration with the GNU Name System for key "
-"exchange."
+"Implementation of a replacement for PANDA (see Pond) with better security, "
+"and maybe integration with the GNU Name System for key exchange."
msgstr ""
#: template/gsoc.html.j2:357
@@ -1558,8 +2249,8 @@ msgstr ""
#: template/gsoc.html.j2:370
msgid ""
-"Implement different place types and file sharing by creating a new place "
-"for the shared content."
+"Implement different place types and file sharing by creating a new place for "
+"the shared content."
msgstr ""
#: template/gsoc.html.j2:376
@@ -1568,12 +2259,12 @@ msgstr ""
#: template/gsoc.html.j2:380
msgid ""
-"<ul> <li>File: generic file with comments</li> <li>Image: display an "
-"image with comments referencing a region of the image</li> <li>Sound: "
-"play a sound file with comments referencing a timestamp</li> "
-"<li>Directory/Album: pointers to File / Image / Sound places</li> "
-"<li>Event: with RSVP</li> <li>Survey: ask your social neighborhood "
-"questions in a structured form</li> </ul>"
+"<ul> <li>File: generic file with comments</li> <li>Image: display an image "
+"with comments referencing a region of the image</li> <li>Sound: play a sound "
+"file with comments referencing a timestamp</li> <li>Directory/Album: "
+"pointers to File / Image / Sound places</li> <li>Event: with RSVP</li> "
+"<li>Survey: ask your social neighborhood questions in a structured form</li> "
+"</ul>"
msgstr ""
#: template/gsoc.html.j2:391
@@ -1583,16 +2274,16 @@ msgstr ""
#: template/gsoc.html.j2:395
msgid ""
"<ul> <li>Fork existing channels, reorganize people into new chatrooms or "
-"channels.</li> <li>Share a post (edit and repost something elsewhere, on "
-"a fan page for example).</li> <li>Edit a previously published post + "
-"offer edit history to readers.</li> <li>Control expiry of channel "
-"history.</li> </ul>"
+"channels.</li> <li>Share a post (edit and repost something elsewhere, on a "
+"fan page for example).</li> <li>Edit a previously published post + offer "
+"edit history to readers.</li> <li>Control expiry of channel history.</li> </"
+"ul>"
msgstr ""
#: template/gsoc.html.j2:404
msgid ""
-"See also <a "
-"href=\"http://secushare.org/features\";>http://secushare.org/features</a>"
+"See also <a href=\"http://secushare.org/features\";>http://secushare.org/";
+"features</a>"
msgstr ""
#: template/gsoc.html.j2:409
@@ -1605,20 +2296,19 @@ msgstr ""
#: template/gsoc.html.j2:427
msgid ""
-"Implement aggregation of distributed state from various channels in order"
-" to provide for a powerful social graph API capable of producing social "
-"network profiles, dashboards, a calendar out of upcoming event "
-"invitations (if available), social search functionality and most of all "
-"to make it easy for users to adopt cryptographic identities of their "
-"contacts/friends simply by finding them in the social graph of their "
-"existing contacts (\"This is Linda. You have 11 contacts in common with "
-"her. [ADD]\")."
+"Implement aggregation of distributed state from various channels in order to "
+"provide for a powerful social graph API capable of producing social network "
+"profiles, dashboards, a calendar out of upcoming event invitations (if "
+"available), social search functionality and most of all to make it easy for "
+"users to adopt cryptographic identities of their contacts/friends simply by "
+"finding them in the social graph of their existing contacts (\"This is "
+"Linda. You have 11 contacts in common with her. [ADD]\")."
msgstr ""
#: template/gsoc.html.j2:445
msgid ""
-"Related to <a "
-"href=\"http://secushare.org/rendezvous\";>secushare.org/rendezvous</a>"
+"Related to <a href=\"http://secushare.org/rendezvous\";>secushare.org/"
+"rendezvous</a>"
msgstr ""
#: template/gsoc.html.j2:451 template/gsoc.html.j2:491
@@ -1627,21 +2317,21 @@ msgstr ""
#: template/gsoc.html.j2:468
msgid ""
-"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform "
-"traditional mail clients into secushare user interfaces. </li> <li> Think"
-" of ways to map e-mail addresses to secushare identities. </li> <li> "
-"Encode or translate various e-mail features into secushare equivalents. "
-"</li> <li> Parts of secushare are currently written in Rust, therefore "
-"Rust is preferred for this task but it is not an requirement. </li> </ul>"
+"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform traditional "
+"mail clients into secushare user interfaces. </li> <li> Think of ways to map "
+"e-mail addresses to secushare identities. </li> <li> Encode or translate "
+"various e-mail features into secushare equivalents. </li> <li> Parts of "
+"secushare are currently written in Rust, therefore Rust is preferred for "
+"this task but it is not an requirement. </li> </ul>"
msgstr ""
#: template/gsoc.html.j2:509
msgid ""
"Implementation of the GNUnet auction system described in Chapter 3 of <a "
"href=\"https://grothoff.org/christian/teich2017ms.pdf\";>this thesis</a>. "
-"Specific tasks are adding smart contract creation and round time "
-"enforcement to libbrandt as well as creating the GNUnet auction service, "
-"library and the three user interface programs create, info and join."
+"Specific tasks are adding smart contract creation and round time enforcement "
+"to libbrandt as well as creating the GNUnet auction service, library and the "
+"three user interface programs create, info and join."
msgstr ""
#: template/gsoc.html.j2:521
@@ -1650,9 +2340,9 @@ msgstr ""
#: template/gsoc.html.j2:539
msgid ""
-"Implementation of additional transports to make GNUnet communication more"
-" robust in the presence of problematic networks: GNUnet-over-SMTP, "
-"GNUnet-over-DNS"
+"Implementation of additional transports to make GNUnet communication more "
+"robust in the presence of problematic networks: GNUnet-over-SMTP, GNUnet-"
+"over-DNS"
msgstr ""
#: template/gsoc.html.j2:546 template/gsoc.html.j2:560
@@ -1666,16 +2356,16 @@ msgid ""
msgstr ""
#: template/gsoc.html.j2:568
-msgid "<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff
Burdges"
+msgid ""
+"<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff Burdges"
msgstr ""
#: template/gsoc.html.j2:576
msgid ""
-"Improving libaboss to make computation on shared secrets (including "
-"repeated multiplication) based on <a "
-"href=\"https://dl.acm.org/citation.cfm?doid=62212.62213\";>Ben-Or et "
-"al.</a> if possible. This in particular means moving libaboss to bignums "
-"(gcry_mpi)."
+"Improving libaboss to make computation on shared secrets (including repeated "
+"multiplication) based on <a href=\"https://dl.acm.org/citation.cfm?";
+"doid=62212.62213\">Ben-Or et al.</a> if possible. This in particular means "
+"moving libaboss to bignums (gcry_mpi)."
msgstr ""
#: template/gsoc.html.j2:589
@@ -1687,11 +2377,10 @@ msgstr ""
#: template/gsoc.html.j2:602
msgid ""
"Python 2.7 is reaching its end-of-life, and we want to get rid of the "
-"dependency on Python. The existing gnunet-qr tool is a rather simple "
-"wrapper around python-zbar, which itself wraps libzbar. The goal of this "
-"project is to directly use libzbar to scan QR codes for GNUnet / the GNU "
-"Name System (see also <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
+"dependency on Python. The existing gnunet-qr tool is a rather simple wrapper "
+"around python-zbar, which itself wraps libzbar. The goal of this project is "
+"to directly use libzbar to scan QR codes for GNUnet / the GNU Name System "
+"(see also <a href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
msgstr ""
#: template/gsoc.html.j2:612
@@ -1716,11 +2405,11 @@ msgstr ""
#: template/gsoc.html.j2:642
msgid ""
-"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a "
-"yet to be determined framework such as Angular2. This includes the design"
-" and implementation of not yet existing <a "
-"href=\"http://jsonapi.org/\";>REST APIs</a> that expose the <a "
-"href=\"https://docs.gnunet.org/doxygen/modules.html\";>GNUnet API</a>."
+"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a yet "
+"to be determined framework such as Angular2. This includes the design and "
+"implementation of not yet existing <a href=\"http://jsonapi.org/\";>REST "
+"APIs</a> that expose the <a href=\"https://docs.gnunet.org/doxygen/modules.";
+"html\">GNUnet API</a>."
msgstr ""
#: template/gsoc.html.j2:657
@@ -1729,8 +2418,7 @@ msgstr ""
#: template/gsoc.html.j2:667
msgid ""
-"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet "
-"WebUI</a>"
+"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet WebUI</a>"
msgstr ""
#: template/index.html.j2:8
@@ -1752,25 +2440,24 @@ msgstr ""
#: template/index.html.j2:49
msgid ""
"The conventional Internet is currently like a system of roads with deep "
-"potholes and highwaymen all over the place. Even if you still can use the"
-" roads (e.g. send emails, or browse websites) your vehicle might get "
+"potholes and highwaymen all over the place. Even if you still can use the "
+"roads (e.g. send emails, or browse websites) your vehicle might get "
"hijacked, damaged, or long arms might reach into its back and steal your "
-"items (data) to use it against you and sell it to others - while you "
-"can't even notice the thievery nor accuse and hold the scroungers "
-"accountable. <!-- Proposal from Fabian Gerlach: The conventional Internet"
-" is currently like a system of roads with deep potholes and surveillance "
-"cameras all over the place. Even if you still can use the roads (e.g. "
-"send emails, or browse websites) your vehicle might gets damaged. And the"
-" surveillance cameras will create a movement profile about your life: "
-"They recognize your car license plate, track you everywhere you drive, "
-"and save this information in a central data base. --> The Internet was "
-"not designed with security in mind: protecting against address forgery, "
-"routers learning metadata, or choosing trustworthy third parties is "
-"nontrivial and sometimes impossible. <!-- Proposal from Fabian Gerlach: "
-"The Internet is not designed with security in mind: The network generally"
-" learns too much about users; it has insecure defaults and high "
-"complexity; and it is centralized. That makes it very vulnerable for "
-"multiple attacks massively threatening our freedom. -->"
+"items (data) to use it against you and sell it to others - while you can'"
+"t even notice the thievery nor accuse and hold the scroungers accountable. "
+"<!-- Proposal from Fabian Gerlach: The conventional Internet is currently "
+"like a system of roads with deep potholes and surveillance cameras all over "
+"the place. Even if you still can use the roads (e.g. send emails, or browse "
+"websites) your vehicle might gets damaged. And the surveillance cameras will "
+"create a movement profile about your life: They recognize your car license "
+"plate, track you everywhere you drive, and save this information in a "
+"central data base. --> The Internet was not designed with security in mind: "
+"protecting against address forgery, routers learning metadata, or choosing "
+"trustworthy third parties is nontrivial and sometimes impossible. <!-- "
+"Proposal from Fabian Gerlach: The Internet is not designed with security in "
+"mind: The network generally learns too much about users; it has insecure "
+"defaults and high complexity; and it is centralized. That makes it very "
+"vulnerable for multiple attacks massively threatening our freedom. -->"
msgstr ""
#: template/index.html.j2:94
@@ -1780,10 +2467,10 @@ msgstr ""
#: template/index.html.j2:96
msgid ""
"GNUnet is a network protocol stack for building secure, distributed, and "
-"privacy-preserving applications.<br/> With strong roots in <a "
-"class=\"link\" href=\"https://bib.gnunet.org\";>academic research</a>, our"
-" goal is to replace the <a class=\"link\" href=\"https://secushare.org";
-"/broken-internet\">old insecure Internet</a> protocol stack."
+"privacy-preserving applications.<br/> With strong roots in <a class=\"link\" "
+"href=\"https://bib.gnunet.org\";>academic research</a>, our goal is to "
+"replace the <a class=\"link\" href=\"https://secushare.org/broken-internet";
+"\">old insecure Internet</a> protocol stack."
msgstr ""
#: template/index.html.j2:119
@@ -1794,10 +2481,9 @@ msgstr ""
msgid ""
"Your metadata is just as revealing as the actual content; and it gets "
"exposed on the Internet.<br> Even though transport encryption is "
-"increasingly being deployed on the Internet, it still reveals data that "
-"can threaten democracy: the identities of senders and receivers, the "
-"times, frequency and the volume of communication are all still "
-"revealed.<br>"
+"increasingly being deployed on the Internet, it still reveals data that can "
+"threaten democracy: the identities of senders and receivers, the times, "
+"frequency and the volume of communication are all still revealed.<br>"
msgstr ""
#: template/index.html.j2:150
@@ -1806,15 +2492,13 @@ msgstr ""
#: template/index.html.j2:152
msgid ""
-"It provides <a class=\"link\" "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";> improving "
-"addressing, routing, naming and content distribution</a> in a technically"
-" robust manner - as opposed to ad-hoc designs in place today. <!-- "
-"Proposal from fabian gerlach: GNUnet is built <a "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by "
-"design\"</a> and \"distributed by design\". This improves addressing, "
-"routing, naming and content distribution in a technically robust manner. "
-"-->"
+"It provides <a class=\"link\" href=\"https://www.w3.org/2014/strint/";
+"papers/65.pdf\"> improving addressing, routing, naming and content "
+"distribution</a> in a technically robust manner - as opposed to ad-hoc "
+"designs in place today. <!-- Proposal from fabian gerlach: GNUnet is built "
+"<a href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by design"
+"\"</a> and \"distributed by design\". This improves addressing, routing, "
+"naming and content distribution in a technically robust manner. -->"
msgstr ""
#: template/index.html.j2:177
@@ -1824,9 +2508,9 @@ msgstr ""
#: template/index.html.j2:179
msgid ""
"Today, monitoring increasingly centralized infrastructure, proprietary "
-"implementations, traffic shapers and firewalls restrict all of the <a "
-"class=\"link\" href=\"https://www.gnu.org/philosophy/free-";
-"sw.html\">essential freedoms</a> to various degrees."
+"implementations, traffic shapers and firewalls restrict all of the <a class="
+"\"link\" href=\"https://www.gnu.org/philosophy/free-sw.html\";>essential "
+"freedoms</a> to various degrees."
msgstr ""
#: template/index.html.j2:203
@@ -1835,14 +2519,14 @@ msgstr ""
#: template/index.html.j2:205
msgid ""
-"GNUnet is a self-organizing network and it is <a class=\"link\" "
-"href=\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as"
-" in freedom. GNUnet puts you in control of your data. You determine which"
-" data to share with whom, and you're not pressured to accept "
-"compromises. It gives users freedoms to securely access information "
-"(\"run\" the network), to study all aspects of the network's "
-"operation (\"access the code\"), to distribute information (\"copy\"), as"
-" well as the freedom to deploy new applications (\"modify\")."
+"GNUnet is a self-organizing network and it is <a class=\"link\" href="
+"\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as in "
+"freedom. GNUnet puts you in control of your data. You determine which data "
+"to share with whom, and you're not pressured to accept compromises. It "
+"gives users freedoms to securely access information (\"run\" the network), "
+"to study all aspects of the network's operation (\"access the code\"), "
+"to distribute information (\"copy\"), as well as the freedom to deploy new "
+"applications (\"modify\")."
msgstr ""
#: template/index.html.j2:229
@@ -1851,13 +2535,13 @@ msgstr ""
#: template/index.html.j2:232
msgid ""
-"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every "
-"other distributed or P2P project develops its own library stack, covering"
-" transports, stream muxing, discovery and others. This divides effort and"
-" multiplies bug count. --> Instead of sharing common components and tools"
-" for building P2P systems, every P2P project seems to re-invent the "
-"wheel. <!-- TODO: rework this sentence. --> This heightens the effort and"
-" increases the potential number of vulnerabilities."
+"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every other "
+"distributed or P2P project develops its own library stack, covering "
+"transports, stream muxing, discovery and others. This divides effort and "
+"multiplies bug count. --> Instead of sharing common components and tools for "
+"building P2P systems, every P2P project seems to re-invent the wheel. <!-- "
+"TODO: rework this sentence. --> This heightens the effort and increases the "
+"potential number of vulnerabilities."
msgstr ""
#: template/index.html.j2:264
@@ -1866,10 +2550,10 @@ msgstr ""
#: template/index.html.j2:266
msgid ""
-"It offers a metadata-preserving foundation for your application. It "
-"offers components for addressing, reliable encrypted channels with "
-"advanced routing and resource discovery and naming. Our work is based on "
-"continuous research spanning almost two decades."
+"It offers a metadata-preserving foundation for your application. It offers "
+"components for addressing, reliable encrypted channels with advanced routing "
+"and resource discovery and naming. Our work is based on continuous research "
+"spanning almost two decades."
msgstr ""
#: template/index.html.j2:286
@@ -2011,75 +2695,69 @@ msgstr ""
#: template/install.html.j2:12
msgid ""
-"Notice: GNUnet is still undergoing major development. It is largely "
-"<i>not yet ready</i> for usage beyond developers."
+"Notice: GNUnet is still undergoing major development. It is largely <i>not "
+"yet ready</i> for usage beyond developers."
msgstr ""
#: template/install.html.j2:18
msgid ""
-"<p>Please be aware that this project is still in an early alpha stage "
-"when it comes to running software – its not an easy task to rewrite"
-" the whole Internet! We are happy to get your <a "
-"href=\"engage.html\">helping hand</a> anytime! Further information is "
-"available in our <a href=\"https://docs.gnunet.org/#toc-Using-";
-"GNUnet-1\">handbook</a>. If you have any queries about the installation "
-"or the usage, please <a href=\"engage.html\">get in touch!</a></p>"
+"<p>Please be aware that this project is still in an early alpha stage when "
+"it comes to running software – its not an easy task to rewrite the "
+"whole Internet! We are happy to get your <a href=\"engage.html\">helping "
+"hand</a> anytime! Further information is available in our <a href=\"https://";
+"docs.gnunet.org/#toc-Using-GNUnet-1\">handbook</a>. If you have any queries "
+"about the installation or the usage, please <a href=\"engage.html\">get in "
+"touch!</a></p>"
msgstr ""
#: template/install.html.j2:30
msgid ""
"We recommend to use binary packages provided by the package manager "
-"integrated within your Operating System. GNUnet is reportedly available "
-"for at least: <ul> <li><a "
-"href=\"https://pkgs.alpinelinux.org/package/edge/testing/x86_64/gnunet\";>Alpine</a></li>"
-" <li><a "
-"href=\"https://www.archlinux.org/packages/community/x86_64/gnunet/\";>Arch</a></li>"
-" <li><a "
-"href=\"https://packages.debian.org/search?keywords=gnunet\";>Debian</a></li>"
-" <li><a "
-"href=\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora "
-"(Copr)</a></li> <li><a "
-"href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
-"href=\"https://github.com/Homebrew/homebrew-";
-"core/blob/master/Formula/gnunet.rb\">Homebrew</a></li> <li><a "
-"href=\"https://nixos.org/nixos/packages.html?attr=gnunet&channel=nixpkgs-";
-"unstable&query=gnunet\">NixOS</a></li> <li><a href=\"install-on-"
-"openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is available for your "
-"Operating System and it is missing, send us feedback so that we can add "
-"it to this list. Furthermore, if you are interested in packaging GNUnet "
-"for your Operating System, get in touch with us at gnunet-"
-"developers@gnu.org if you require help with this job. If you were using "
-"an Operating System with the Alpine package manager, GNUnet could be "
-"installed as simple as:"
+"integrated within your Operating System. GNUnet is reportedly available for "
+"at least: <ul> <li><a href=\"https://pkgs.alpinelinux.org/package/edge/";
+"testing/x86_64/gnunet\">Alpine</a></li> <li><a href=\"https://www.archlinux.";
+"org/packages/community/x86_64/gnunet/\">Arch</a></li> <li><a href=\"https://";
+"packages.debian.org/search?keywords=gnunet\">Debian</a></li> <li><a href="
+"\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora (Copr)</a></"
+"li> <li><a href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
+"href=\"https://github.com/Homebrew/homebrew-core/blob/master/Formula/gnunet.";
+"rb\">Homebrew</a></li> <li><a href=\"https://nixos.org/nixos/packages.html?";
+"attr=gnunet&channel=nixpkgs-unstable&query=gnunet\">NixOS</a></li> <li><a "
+"href=\"install-on-openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is "
+"available for your Operating System and it is missing, send us feedback so "
+"that we can add it to this list. Furthermore, if you are interested in "
+"packaging GNUnet for your Operating System, get in touch with us at gnunet-"
+"developers@gnu.org if you require help with this job. If you were using an "
+"Operating System with the Alpine package manager, GNUnet could be installed "
+"as simple as:"
msgstr ""
#: template/install.html.j2:61
msgid ""
-"Next we describe a generic way to install from source. If you are using "
-"one of the following Operating Systems these step-by-step guides might be"
-" useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href"
-"=\"install-on-debian9.html\">Debian 9</a>, <a href=\"install-on-"
-"macos.html\">Mac OS</a>, <a href=\"install-on-netbsd.html\">NetBSD</a>, "
-"<a href=\"install-on-ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not"
-" all of them might be totally up-to-date! Please <a "
-"href=\"engage.html\">ask us</a> if you get stuck."
+"Next we describe a generic way to install from source. If you are using one "
+"of the following Operating Systems these step-by-step guides might be "
+"useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href=\"install-on-"
+"debian9.html\">Debian 9</a>, <a href=\"install-on-macos.html\">Mac OS</a>, "
+"<a href=\"install-on-netbsd.html\">NetBSD</a>, <a href=\"install-on-"
+"ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not all of them might be "
+"totally up-to-date! Please <a href=\"engage.html\">ask us</a> if you get "
+"stuck."
msgstr ""
#: template/install.html.j2:75
msgid ""
-"First, install the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>required "
-"dependencies</a> of GNUnet. There are base requirements and optional "
-"requirements."
+"First, install the <a href=\"https://git.gnunet.org/gnunet.git/tree/README";
+"\">required dependencies</a> of GNUnet. There are base requirements and "
+"optional requirements."
msgstr ""
#: template/install.html.j2:81
msgid ""
"Now, you need to decide if you want to install GNUnet from the release "
"tarball or from git. If you want to use GNUnet and there is no binary "
-"package available for your OS, you should stick with the release tarball."
-" If you want to develop using the most recent build, you should go with "
-"the <a href=\"https://git.gnunet.org/\";>git repository</a>."
+"package available for your OS, you should stick with the release tarball. If "
+"you want to develop using the most recent build, you should go with the <a "
+"href=\"https://git.gnunet.org/\";>git repository</a>."
msgstr ""
#: template/install.html.j2:98
@@ -2088,8 +2766,8 @@ msgstr ""
#: template/install.html.j2:106
msgid ""
-"Before building GNUnet, make sure that you setup the required groups and "
-"add your user to the group <code>gnunet</code>:"
+"Before building GNUnet, make sure that you setup the required groups and add "
+"your user to the group <code>gnunet</code>:"
msgstr ""
#: template/install.html.j2:117
@@ -2098,9 +2776,8 @@ msgstr ""
#: template/install.html.j2:128
msgid ""
-"You can find more configuration flags in the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>README</a>.<br> "
-"Install GNUnet with:"
+"You can find more configuration flags in the <a href=\"https://git.gnunet.";
+"org/gnunet.git/tree/README\">README</a>.<br> Install GNUnet with:"
msgstr ""
#: template/install.html.j2:138
@@ -2110,9 +2787,8 @@ msgstr ""
#: template/install.html.j2:146
msgid ""
"Check the <a href=\"https://docs.gnunet.org/handbook/gnunet.html#Minimal-";
-"configuration\">handbook</a> for detailed documentation. For a more "
-"hands-on experience, <a href=\"https://gnunet.org/en/use.html\";>continue "
-"here</a>."
+"configuration\">handbook</a> for detailed documentation. For a more hands-on "
+"experience, <a href=\"https://gnunet.org/en/use.html\";>continue here</a>."
msgstr ""
#: template/livingstandards.html.j2:11
diff --git a/locale/it/LC_MESSAGES/messages.po
b/locale/it/LC_MESSAGES/messages.po
index dc4f31e..189d637 100644
--- a/locale/it/LC_MESSAGES/messages.po
+++ b/locale/it/LC_MESSAGES/messages.po
@@ -7,9 +7,9 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2021-03-03 21:41+0100\n"
-"PO-Revision-Date: 2021-03-09 18:35+0000\n"
-"Last-Translator: Sabino Miani <sbn.miani@gmail.com>\n"
+"POT-Creation-Date: 2021-03-12 16:12+0100\n"
+"PO-Revision-Date: 2021-03-16 22:31+0000\n"
+"Last-Translator: Francesca Cipriani <cesca.cipriani@gmail.com>\n"
"Language-Team: Italian <http://weblate.taler.net/projects/gnunet/website/it/>"
"\n"
"Language: it\n"
@@ -26,11 +26,11 @@ msgstr "GNUnet"
#: common/base.j2:6 common/news.j2:6
msgid "GNU's framework for secure p2p networking"
-msgstr "La struttura di GNU per una connessione p2p sicura"
+msgstr "L'architettura GNU per una rete p2p sicura"
#: common/footer.j2.inc:7
msgid "Contact"
-msgstr "Contatto"
+msgstr "Contatti"
#: common/footer.j2.inc:8 common/navigation.j2.inc:49
msgid "GNUnet e.V."
@@ -38,11 +38,11 @@ msgstr "GNUnet e.V."
#: common/footer.j2.inc:9 template/about.html.j2:6
msgid "About GNUnet"
-msgstr "Per quanto riguarda GNUnet"
+msgstr "Informazioni su GNUnet"
#: common/footer.j2.inc:14 common/navigation.j2.inc:64
msgid "Bug Tracker"
-msgstr "Rilevatore di bachi"
+msgstr "Registro bug"
#: common/footer.j2.inc:19 template/copyright.html.j2:6
msgid "Copyright Assignment"
@@ -55,20 +55,21 @@ msgstr "Bibliografia"
#: common/footer.j2.inc:31
msgid "Source code of this site."
-msgstr "Il codice sorgente di questo sito."
+msgstr "Codice sorgente del sito."
#: common/footer.j2.inc:32
msgid "Report issues with this website."
-msgstr "Segnalare problemi con questo sito."
+msgstr "Segnalare problemi del sito."
#: common/navigation.j2.inc:38
msgid "About"
-msgstr "Per quanto riguarda"
+msgstr "Cos'è GNUnet"
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
-msgstr "Notizia"
+msgstr "Novità"
#: common/navigation.j2.inc:40 template/index.html.j2:289
msgid "Applications"
@@ -76,11 +77,11 @@ msgstr "Applicazioni"
#: common/navigation.j2.inc:44
msgid "Community"
-msgstr "Comunità"
+msgstr "Community"
#: common/navigation.j2.inc:47 template/index.html.j2:292
msgid "Engage"
-msgstr "Impegnare"
+msgstr "Partecipa"
#: common/navigation.j2.inc:48
msgid "GSoC Projects"
@@ -88,7 +89,7 @@ msgstr "Progetti GSoC"
#: common/navigation.j2.inc:50
msgid "Copyright for Contributors"
-msgstr "Diritti per i Contributori"
+msgstr "Copyright per i collaboratori"
#: common/navigation.j2.inc:51
msgid "IRC Archive"
@@ -100,7 +101,7 @@ msgstr "Sviluppo"
#: common/navigation.j2.inc:61
msgid "System Architecture"
-msgstr "Architettura di Sistema"
+msgstr "Architettura del sistema"
#: common/navigation.j2.inc:63 template/roadmap.html.j2:6
msgid "Roadmap"
@@ -108,19 +109,19 @@ msgstr "Tabella di marcia"
#: common/navigation.j2.inc:65 template/gnurl.html.j2:186
msgid "Source Code"
-msgstr "Codice Sorgente"
+msgstr "Codice sorgente"
#: common/navigation.j2.inc:66
msgid "Source Code Documentation"
-msgstr "Documentazione del Codice Sorgente"
+msgstr "Documentazione del codice sorgente"
#: common/navigation.j2.inc:67
msgid "Continuous Integration"
-msgstr "Integrazione Continua"
+msgstr "Integrazione continua"
#: common/navigation.j2.inc:68
msgid "Development Tutorial"
-msgstr "Esercitazione di Sviluppo"
+msgstr "Guida allo sviluppo"
#: common/navigation.j2.inc:79
msgid "Documentation"
@@ -158,19 +159,22 @@ msgstr "REST API"
msgid "FAQ"
msgstr "Domande Frequenti"
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
msgstr ""
"Annunci di notizie legate ai cambiamenti di GNUnet come comunicati stampa ed "
"eventi"
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
msgstr "Fai la sottoscrizione alla nostra bacheca RSS"
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
msgstr "Per saperne di più"
@@ -227,8 +231,8 @@ msgstr ""
"ostili presenti nella rete. \n"
"Inoltre, l'internet dei giorni nostri si è evoluto al punto che, come "
"sottolineato da Matthew Green, \n"
-"<a href=\"https://blog.cryptographyengineering.com/2015/08/16/";
-"the-network-is-hostile/\">\"la rete è ostile\"</a>."
+"<a href=\"https://blog.cryptographyengineering.com/2015/08/16/the-network-is-";
+"hostile/\">\"la rete è ostile\"</a>."
#: template/about.html.j2:41
msgid ""
@@ -294,7 +298,8 @@ msgstr ""
#: template/about.html.j2:64
msgid "GNUnet must be open and permit new peers to join."
-msgstr "GNUnet deve essere aperto e lasciare che nuovi colleghi possano
unirsi."
+msgstr ""
+"GNUnet deve essere aperto e lasciare che nuovi colleghi possano unirsi."
#: template/about.html.j2:65
msgid "GNUnet must support a diverse range of applications and devices."
@@ -366,9 +371,9 @@ msgstr ""
"Esistono molte più risorse che permettono di conoscere GNUnet oltre che il "
"<a href=\"https://docs.gnunet.org/handbook/gnunet.html\";>manuale</a>, "
"abbiamo la<a href=\"https://bib.gnunet.org/\";>bibliografia</a> con fogli che "
-"coprono i vari strati, molti<a href=\"https://gnunet.org/en/video.html\"";
-">video</a>o un breve <a href=\"https://gnunet.org/en/glossary.html\"";
-">glossario</a>."
+"coprono i vari strati, molti<a href=\"https://gnunet.org/en/video.html";
+"\">video</a>o un breve <a href=\"https://gnunet.org/en/glossary.html";
+"\">glossario</a>."
#: template/about.html.j2:95
msgid ""
@@ -379,8 +384,8 @@ msgid ""
msgstr ""
"Sei sempre il benvenuto <a href=\"engage.html\">quando si tratta di "
"affrontare conversazioni</a>, <a href=\"install.html\">installare GNUnet</"
-"a>, <a href=\"use.html\">utilizzarlo</a> e <a href=\"engage.html\""
-">contribuire ed impegnarsi</a> in svariati modi."
+"a>, <a href=\"use.html\">utilizzarlo</a> e <a href=\"engage.html"
+"\">contribuire ed impegnarsi</a> in svariati modi."
#: template/about.html.j2:100
msgid ""
@@ -615,10 +620,16 @@ msgid ""
"for addresses and self-organized decentralized routing algorithms, these "
"subsystems replace the traditional TCP/IP stack."
msgstr ""
+"Le basi di GNUnet sono una tabella hash distribuita (R5N), un livello di "
+"messaggistica con crittografia end-to-end di tipo SCTP (CADET), "
+"un'infrastruttura a chiave pubblica (GNS) e un sistema di trasporto "
+"collegabile (TRANSPORT).<br> Questi sottosistemi sostituiscono lo stack TCP/"
+"IP, poiché utilizzano chiavi pubbliche per indirizzi e algoritmi di routing "
+"decentralizzati e auto-organizzati."
#: template/architecture.html.j2:35
msgid "Security"
-msgstr ""
+msgstr "Sicurezza"
#: template/architecture.html.j2:38
msgid ""
@@ -628,34 +639,39 @@ msgid ""
"is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and will always "
"remain free software."
msgstr ""
+"GNUnet è implementato con un’architettura multiprocesso. Ogni sottosistema "
+"viene eseguito come un processo separato, permettendo l’isolamento degli "
+"errori e la concessione di autorizzazioni limitate a ciascun sottosistema. L’"
+"implementazione è un pacchetto <a href=\"https://www.gnu.org/\";>GNU</a>, "
+"quindi sarà sempre un software gratuito."
#: template/architecture.html.j2:52
msgid "System architecture"
-msgstr ""
+msgstr "Architettura del sistema"
#: template/architecture.html.j2:58
msgid "Subsystems"
-msgstr ""
+msgstr "Sottosistemi"
#: template/architecture.html.j2:67
msgid "libgnunetutil"
-msgstr ""
+msgstr "libgnunetutil"
#: template/architecture.html.j2:73
msgid "APIs"
-msgstr ""
+msgstr "API"
#: template/architecture.html.j2:86
msgid "Legend"
-msgstr ""
+msgstr "Legenda"
#: template/contact.html.j2:6
msgid "Contact information"
-msgstr ""
+msgstr "Contatti"
#: template/contact.html.j2:11
msgid "The mailing list"
-msgstr ""
+msgstr "Mailing list"
#: template/contact.html.j2:13
msgid ""
@@ -664,10 +680,15 @@ msgid ""
"mailman/listinfo/gnunet-developers</a>. You can send messages to the list at "
"<a href=\"mailto:gnunet-developers@gnu.org\";>gnunet-developers@gnu.org</a>."
msgstr ""
+"All'indirizzo <a href=\"https://lists.gnu.org/mailman/listinfo/gnunet-";
+"developers\">https://lists.gnu.org/mailman/listinfo/gnunet-developers</a> è "
+"possibile trovare una mailing list di GNUnet pubblica e archiviata. Per "
+"inviare un messaggio all'intera mailing list, scrivere a <a href=\"mailto"
+":gnunet-developers@gnu.org\">gnunet-developers@gnu.org</a>."
#: template/contact.html.j2:23
msgid "The IRC channel"
-msgstr ""
+msgstr "Canale IRC"
#: template/contact.html.j2:25
msgid ""
@@ -675,10 +696,13 @@ msgid ""
"freenode.net</a>. There is also an <a href=\"https://view.matrix.org/room/!";
"IjaAfLiruzjxFFzKAV:matrix.org/\">archive</a> available."
msgstr ""
+"<tt>#gnunet</tt> è accessibile su <a href=\"https://freenode.net\";>irc."
+"freenode.net</a>. È disponibile anche un <a href=\"https://view.matrix.org/";
+"room/!IjaAfLiruzjxFFzKAV:matrix.org/\">archivio</a>."
#: template/contact.html.j2:38
msgid "Contacting individuals"
-msgstr ""
+msgstr "Contatti degli sviluppatori"
#: template/contact.html.j2:40
msgid ""
@@ -687,10 +711,15 @@ msgid ""
"encrypted Emails. Urgent and sensitive security issues may be addressed to "
"the GNU maintainers <tt>schanzen</tt> and <tt>grothoff</tt>."
msgstr ""
+"È possibile contattare gli sviluppatori di GNUnet scrivendo a "
+"<tt>PSEUDONYM@gnunet.org</tt> o <tt>LASTNAME@gnunet.org</tt>. Quasi tutti "
+"gli sviluppatori supportano la ricezione di email con crittografia GnuPG. "
+"Per questioni di sicurezza urgenti e sensibili rivolgersi ai maintainer "
+"<tt>schanzen</tt> e <tt>grothoff</tt>."
#: template/contact.html.j2:53
msgid "Reporting bugs"
-msgstr ""
+msgstr "Report dei bug"
#: template/contact.html.j2:55
msgid ""
@@ -700,6 +729,12 @@ msgid ""
"bug-gnunet\">bug-gnunet</a> mailing list. The mailinglist requires no "
"subscription."
msgstr ""
+"Monitoriamo richieste di funzionalità e bug aperti per i progetti "
+"all'interno di GNUnet nel nostro <a href=\"https://bugs.gnunet.org/\"";
+">Registro bug</a>. È possibile segnalare bug o richieste di funzionalità "
+"scrivendo alla mailing list <a href=\"https://lists.gnu.org/mailman/listinfo/";
+"bug-gnunet\">bug-gnunet</a>. Non è necessario iscriversi alla mailing list "
+"per inviare un messaggio."
#: template/copyright.html.j2:11
msgid ""
@@ -709,6 +744,12 @@ msgid ""
"\">GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative "
"development</a> of the GNUnet and GNU Taler projects is satisfied. </p>"
msgstr ""
+"<p> I collaboratori di GNUnet con accesso Git devono firmare l'<a href=\"/"
+"static/pdf/copyright.pdf\">accordo sul copyright</a> per garantire "
+"l'adempimento dell'<a href=\"https://git.gnunet.org/gnunet-ev.git/tree/";
+"gnunet_taler_agreement.tex\">accordo GNUnet e.V. --- Taler Systems SA sulla "
+"gestione delle licenze e sullo sviluppo collaborativo</a> dei progetti "
+"GNUnet e GNU Taler. </p>"
#: template/copyright.html.j2:22
msgid ""
@@ -718,6 +759,12 @@ msgid ""
"company the ability to dual-license (for example, so that we can distribute "
"via App-stores that are hostile to free software).</p>"
msgstr ""
+"<p>Gli accordi garantiscono che il codice continui a essere disponibile con "
+"licenze software gratuite, ma conferisce agli sviluppatori la libertà di "
+"spostare il codice tra GNUnet e GNU Taler senza preoccuparsi delle licenze e "
+"consente all'azienda la possibilità di una doppia licenza (affinché, ad "
+"esempio, la distribuzione possa avvenire tramite gli App-store, che sono "
+"ostili ai software gratuiti).</p>"
#: template/copyright.html.j2:30
msgid ""
@@ -905,11 +952,133 @@ msgid ""
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
-#: template/faq.html.j2:12
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
+msgstr ""
+
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
+msgstr ""
+
+#: template/faq.html.j2:15 template/faq.html.j2:695
+msgid "Error messages"
+msgstr ""
+
+#: template/faq.html.j2:16 template/faq.html.j2:797
+#, fuzzy
+#| msgid "Filesharing (Alpha)"
+msgid "File-sharing"
+msgstr "Condivisione di file (Alpha)"
+
+#: template/faq.html.j2:17 template/faq.html.j2:973
+msgid "Contributing"
+msgstr ""
+
+#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr ""
+
+#: template/faq.html.j2:28
+msgid ""
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
+"the #gnunet IRC on irc.freenode.net."
+msgstr ""
+
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
+msgstr ""
+
+#: template/faq.html.j2:38
+msgid ""
+"A: The general answer is, when it is ready. A better answer may be: earlier "
+"if you contribute (test, debug, code, document). Every release will be "
+"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://";
+"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
+"the RSS feed of this site to automatically receive a notification."
+msgstr ""
+
+#: template/faq.html.j2:49
+msgid "Is the code free?"
+msgstr ""
+
+#: template/faq.html.j2:51
+msgid ""
+"A: GNUnet is free software, available under the <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
+msgstr ""
+
+#: template/faq.html.j2:58
+msgid "Are there any known bugs?"
+msgstr ""
+
+#: template/faq.html.j2:60
+msgid ""
+"A: We track the list of currently known bugs in the <a href=\"https://bugs.";
+"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
+"directly to developers or the developer mailing list. This is discouraged "
+"since developers often do not have the time to feed these bugs back into the "
+"Mantis database. Please report bugs directly to the bug tracking system. If "
+"you believe a bug is sensitive, you can set its view status to private (this "
+"should be the exception)."
+msgstr ""
+
+#: template/faq.html.j2:73 template/faq.html.j2:193
+msgid "Is there a graphical user interface?"
+msgstr ""
+
+#: template/faq.html.j2:75
+msgid ""
+"A: gnunet-gtk is a separate download. The package contains various GTK+ "
+"based graphical interfaces, including a graphical tool for configuration."
+msgstr ""
+
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr ""
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called ""
+"proof-of-work" which is used to convince the network that your peer is "
+"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
+"on the network size estimator). The calculation is expected to take a few "
+"days, depending on how fast your CPU is. If the CPU load is creating a "
+"problem for you, you can set the value "WORKDELAY" in the ""
+"nse" section of your configuration file to a higher value. The default "
+"is "5 ms"."
+msgstr ""
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr ""
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
+"connections and, with the Tor Browser Bundle, for the Web in particular. "
+"GNUnet does not really have one focus; our theme is secure decentralized "
+"networking, but that is too broad to be called a focus."
+msgstr ""
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr ""
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost no "
+"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
+"using onion (or garlic) routing as the basis for various (anonymized) "
+"applications. I2P is largely used via a Web frontend."
+msgstr ""
+
+#: template/faq.html.j2:124
msgid "Is GNUnet ready for use on production systems?"
msgstr ""
-#: template/faq.html.j2:14
+#: template/faq.html.j2:126
msgid ""
"A: GNUnet is still undergoing major development. It is largely not yet ready "
"for usage beyond developers. Your mileage will vary depending on the "
@@ -918,24 +1087,467 @@ msgid ""
"rewriting it (Project "Transport Next Generation [TNG]")"
msgstr ""
-#: template/faq.html.j2:24
+#: template/faq.html.j2:136
msgid "Is GNUnet build using distributed ledger technologies?"
msgstr ""
-#: template/faq.html.j2:26
+#: template/faq.html.j2:138
msgid ""
"A: No. GNUnet is a new network protocol stack for building secure, "
"distributed, and privacy-preserving applications. While a ledger could be "
"built using GNUnet, we currently have no plans in doing so."
msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:151
+#, fuzzy
+#| msgid "What is GNUnet?"
+msgid "What can I do with GNUnet?"
+msgstr "Cos'è GNUnet?"
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
+"do more than just one thing. Naturally, the implementation and documentation "
+"of some of the features that exist are more advanced than others."
+msgstr ""
+
+#: template/faq.html.j2:160
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
+"decentralized and censorship-resistant replacement for DNS and a mechanism "
+"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
+msgstr ""
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We "
+"recommend that you use Tor for anonymous surfing."
+msgstr ""
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr ""
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+
+#: template/faq.html.j2:195
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the "
+"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
+"that integrates most of the other GUIs in one window. One exception is "
+"gnunet-setup, which must still be run separately at this time (as setup "
+"requires the peer to be stopped)."
+msgstr ""
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr ""
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
+"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
+"FreeBSD and macOS. We have reports of working versions on many other GNU/"
+"Linux distributions; in the past we had reports of working versions on "
+"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
+"so if you cannot get GNUnet to work on those systems please let us know."
+msgstr ""
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr ""
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a default "
+"configuration of top-level domains. The governance of this default "
+"configuration is not yet established. In any case, the user will be able to "
+"modify this configuration at will. We expect normal users to have no need to "
+"edit their own GNS zone(s) unless they host services themselves."
+msgstr ""
+
+#: template/faq.html.j2:241
+msgid "Where is the per-user GNS database kept?"
+msgstr ""
+
+#: template/faq.html.j2:243
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet peer. "
+"Now, a user may run multiple GNUnet peers, in which case the database could "
+"be kept at each peer (however, we don't have code for convenient "
+"replication). Similarly, multiple GNUnet peers can share one instance of the "
+"database --- the "gnunet-service-namestore" can be accessed from "
+"remote (via TCP). The actual data can be stored in a Postgres database, for "
+"which various replication options are again applicable. Ultimately, there "
+"are many options for how users can store (and secure) their GNS database."
+msgstr ""
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases "
+"will only grow to a few tens of thousands of entries, small enough to fit "
+"even on mobile devices."
+msgstr ""
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr ""
+
+#: template/faq.html.j2:272
+msgid ""
+"A: We believe so, as there is no entity that any government could force to "
+"change the mapping for a name except for each individual user (and then the "
+"changes would only apply to the names that this user is the authority for). "
+"So if everyone used GNS, the only practical attack of a government would be "
+"to force the operator of a server to change the GNS records for his server "
+"to point elsewhere. However, if the owner of the private key for a zone is "
+"unavailable for enforcement, the respective zone cannot be changed and any "
+"other zone delegating to this zone will achieve proper resolution."
+msgstr ""
+
+#: template/faq.html.j2:286
+msgid "How does GNS compare to other name systems"
+msgstr ""
+
+#: template/faq.html.j2:288
+msgid ""
+"A: A scientific paper on this topic <a href=\"https://grothoff.org/christian/";
+"ns2018.pdf\">has been published </a> and below is a table from the "
+"publication. For detailed descriptions please refer to the paper."
+msgstr ""
+
+#: template/faq.html.j2:392
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr ""
+
+#: template/faq.html.j2:394
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
+"there are still registrars that determine who owns a name. <br><br> With "
+"GNS, we decentralize the database and also decentralize the responsibility "
+"for naming: each user runs his own personal root zone and is thus in "
+"complete control of the names he uses. GNS also has many additional features "
+"(to keep names short and enable migration) which don't even make sense in "
+"the context of CoDoNS."
+msgstr ""
+
+#: template/faq.html.j2:410
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr ""
+
+#: template/faq.html.j2:412
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared via "
+"delegation, and thus mappings will only change if the user responsible for "
+"the name (the authority) manually changes the record."
+msgstr ""
+
+#: template/faq.html.j2:426
+msgid "What is the difference between GNS and ODDNS?"
+msgstr ""
+
+#: template/faq.html.j2:428
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+
+#: template/faq.html.j2:439
+msgid "What is the difference between GNS and Handshake?"
+msgstr ""
+
+#: template/faq.html.j2:441
+msgid ""
+"A: Handshake is a blockchain-based method for root zone governance. Hence, "
+"it does not address the name resolution process itself but delegates "
+"resolution into DNS after the initial TLD resolution. Not taking "
+"sustainablility considerations into account, handshake could be used as an "
+"additional supporting GNS root zone governance model but we currently do not "
+"have such plans in mind."
+msgstr ""
+
+#: template/faq.html.j2:453
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr ""
+
+#: template/faq.html.j2:455
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks on "
+"DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from "
+"the DNS hierarchy."
+msgstr ""
+
+#: template/faq.html.j2:468
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the style "
+"of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: For security, it is well known that an initial trust path between the two "
+"parties must exist. However, for applications where this is not required, "
+"weaker mechanisms can be used. For example, we have implemented a first-come-"
+"first-served (FCFS) authority which allows arbitrary users to register "
+"arbitrary names. The key of this authority is included with every GNUnet "
+"installation. Thus, any name registered with FCFS is in fact global and "
+"requires no further introduction. However, the security of these names "
+"depends entirely on the trustworthiness of the FCFS authority. The authority "
+"can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name in "
+"GNS?"
+msgstr ""
+
+#: template/faq.html.j2:487
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "legitimate" "
+"domain owner. Any user can claim any name (as his preferred name or ""
+"pseudonym") in his NICK record. Similarly, all other users can choose "
+"to ignore this preference and use a name of their choice (or even assign no "
+"name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:498
+msgid ""
+"Did you consider the privacy implications of making your personal GNS zone "
+"visible?"
+msgstr ""
+
+#: template/faq.html.j2:500
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not set. "
+"Thus, users have full control over what information about their zones is "
+"made public."
+msgstr ""
+
+#: template/faq.html.j2:510
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary because "
+"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
+"of virtual hosting. However, LEHOs are also useful to help with X.509 "
+"certificate validation (as they specify for which legacy hostname the "
+"certificate should be valid). Also, even with IPv6 fully deployed and ""
+"infinite" IP addresses being available, we're not sure that virtual "
+"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
+"become commonplace, GNS should work with today's networks."
+msgstr ""
+
+#: template/faq.html.j2:526
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:528
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. As "
+"trust relationships evolve, mappings would change their meaning as they "
+"cross each others thresholds. We decided that the resulting unpredictability "
+"of the resolution process was not acceptable. Furthermore, trust and "
+"consensus might be easy to manipulate by adversaries."
+msgstr ""
+
+#: template/faq.html.j2:539
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:541
+msgid ""
+"A: The owner of a private key can create a revocation message. This one can "
+"then be flooded throughout the overlay network, creating a copy at all "
+"peers. Before using a public key, peers check if that key has been revoked. "
+"All names that involve delegation via a revoked zone will then fail to "
+"resolve. Peers always automatically check for the existence of a revocation "
+"message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:553
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:555
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:569
+msgid ""
+"How can a GNS zone maintain several name servers, e.g. for load balancing?"
+msgstr ""
+
+#: template/faq.html.j2:571
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share "
+"the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:584
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:586
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names are "
+"not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on your "
+"application, HTTPS may not be worth the cost. However, for users that are "
+"experiencing censorship (or are concerned about it), giving up globally "
+"unique names may very well be worth the cost. After all, what is a ""
+"globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:600
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:602
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by IANA/ICANN. "
+"This centralization creates vulnerabilities. For example, the US government "
+"was able to reassign the management of the country-TLDs of Afganistan and "
+"Iraq during the wars at the beginning of the 21st century."
+msgstr ""
+
+#: template/faq.html.j2:613
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:615
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
+"so blocking a particular IP address causes much more collateral damage than "
+"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
+"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
+"censorship resistant naming system. Accessing Tor's ".onion" "
+"namespace currently requires users to use unmemorable cryptographic "
+"identifiers. With nicer names, Tor and tor2web-like services would be even "
+"easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:634
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:636
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can use "
+"GNS to perform name resolution as well as any normal user. Naturally, while "
+"we typically expect normal users to install custom software for name "
+"resolution, this is unlikely to work for search engines today. However, the "
+"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
+"they can still index GNS resources. However, as using DNS2GNS gateways "
+"breaks the cryptographic chain of trust, legacy search engines will "
+"obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:650
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:652
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was designed "
+"to interoperate with DNS as much as possible, and to also work as much as "
+"possible with the existing Web infrastructure. UIA is not at all concerned "
+"about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:665
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:667
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you know "
+"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
+"and can thus decide how much you trust the result. Naturally, the trusted-"
+"computing base (TCB) can become arbitrarily large this way --- however, "
+"given the name length restriction, for an individual name it is always less "
+"than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:679
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part of "
+"the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:681
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects the "
+""_Service._Proto" syntax, converts "Service" to the "
+"corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when the "
+"result is presented, GNS looks for the GNS-specific "BOX" record "
+"type. A BOX record is a record that contains another record (such as SRV or "
+"TLSA records) and adds a service and protocol number (and the original boxed "
+"record type) to it."
+msgstr ""
+
+#: template/faq.html.j2:697
msgid ""
"I receive many "WARNING Calculated flow delay for X at Y for Z". "
"Should I worry?"
msgstr ""
-#: template/faq.html.j2:37
+#: template/faq.html.j2:699
msgid ""
"A: Right now, this is expected and a known cause for high latency in GNUnet. "
"We have started a major rewrite to address this and other problems, but "
@@ -943,14 +1555,191 @@ msgid ""
"expected."
msgstr ""
-#: template/faq.html.j2:46
-msgid "Is there a graphical user interface?"
+#: template/faq.html.j2:708
+msgid "Error opening `/dev/net/tun': No such file or directory?"
msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:710
msgid ""
-"A: gnunet-gtk is a separate download. The package contains various GTK+ "
-"based graphical interfaces, including a graphical tool for configuration."
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:722
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
+"dns)?"
+msgstr ""
+
+#: template/faq.html.j2:724
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check if "
+"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:736
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:738
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if "
+"your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:746
+msgid ""
+"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:748
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if you "
+"compiled GNUnet the normal way and/or used a binary package, that is highly "
+"unlikely. The more common cause is that you installed GNUnet to a directory "
+"that your linker does not search. There are several ways to fix this that "
+"are described below. If you are 'root' and you installed to a system folder "
+"(such as /usr/local), you want to add the libraries to the system-wide "
+"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
+"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
+"similar path, you obviously have to change \"/usr/local\" accordingly. If "
+"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
+"$USER/\", then you can explicitly tell your linker to search a particular "
+"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
+"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
+"you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:774
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the \"$\") "
+"to your .bashrc or .profile file. You will have to logout and login again to "
+"have this new profile be applied to all shells (including your desktop "
+"environment)."
+msgstr ""
+
+#: template/faq.html.j2:781
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:783
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
+"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
+"always refer to harmless events that require no action. For example, GNUnet "
+"may use an INFO message to indicate that it is currently performing an "
+"expensive operation that will take some time. GNUnet will also use INFO "
+"messages to display information about important configuration values."
+msgstr ""
+
+#: template/faq.html.j2:799
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:801
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
+"P2P networks, GNUnet was designed with security in mind as the highest "
+"priority. We intend on producing a network with comprehensive security "
+"features. Many other P2P networks are open to a wide variety of attacks, and "
+"users have little privacy. GNUnet is also Free Software and thus the source "
+"code is available, so you do not have to worry about being spied upon by the "
+"software. The following table summarises the main differences between GNUnet "
+"and other systems. The information is accurate to the best of our knowledge. "
+"The comparison is difficult since there are sometimes differences between "
+"various implementations of (almost) the same protocol. In general, we pick a "
+"free implementation as the reference implementation since it is possible to "
+"inspect the free code. Also, all of these systems are changing over time and "
+"thus the data below may not be up-to-date. If you find any flaws, please let "
+"us know. Finally, the table is not saying terribly much (it is hard to "
+"compare these systems this briefly), so if you want the real differences, "
+"read the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:915
+msgid ""
+"Another important point of reference are the various anonymous peer-to-peer "
+"networks. Here, there are differences in terms of application domain and how "
+"specifically anonymity is achieved. Anonymous routing is a hard research "
+"topic, so for a superficial comparisson like this one we focus on the "
+"latency. Another important factor is the programming language. Type-safe "
+"languages may offer certain security benefits; however, this may come at the "
+"cost of significant increases in resource consumption which in turn may "
+"reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:928
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:930
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of the "
+"same techniques used to generate reasonable passwords to defend against such "
+"an attack. In any event, we are not trying to hide content; thus, unless the "
+"user is trying to insert information into the network that can only be "
+"shared with a small group of people, there is no real reason to try to "
+"obfuscate the content by choosing a difficult keyword anyway."
+msgstr ""
+
+#: template/faq.html.j2:944
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:946
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all "
+"users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell which "
+"of the peers in the group originated the message. In other words, it should "
+"be difficult to impossible for an adversary to distinguish between the "
+"originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:958
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:960
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
+"its public key) and has a number of addresses it is reachable by (may have "
+"no addresses, for instance when it's behind a NAT). You specify bandwidth "
+"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
+"(how large your on-disk block storage is) . Your node will then proceed to "
+"connect to other nodes, becoming part of the network."
+msgstr ""
+
+#: template/faq.html.j2:975
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:977
+msgid ""
+"A: First, you need to register an account with our weblate system. Please "
+"send an e-mail with the desired target language to translators@gnunet.org or "
+"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
+"sufficient permissions will then grant you access. Naturally, any abuse will "
+"result in the loss of permissions."
+msgstr ""
+
+#: template/faq.html.j2:989
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:991
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly implement. "
+"The best way to actually get a new feature implemented is to do it yourself "
+"--- and to then send us a patch."
msgstr ""
#: template/glossary.html.j2:12
@@ -1057,10 +1846,6 @@ msgstr ""
msgid "Overview"
msgstr ""
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
-
#: template/gns.html.j2:39
msgid ""
"The GNU Name System (GNS) is secure and decentralized naming system. It "
diff --git a/locale/ja/LC_MESSAGES/messages.po
b/locale/ja/LC_MESSAGES/messages.po
index 1b39288..ce70773 100644
--- a/locale/ja/LC_MESSAGES/messages.po
+++ b/locale/ja/LC_MESSAGES/messages.po
@@ -7,14 +7,14 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2021-03-03 21:41+0100\n"
-"PO-Revision-Date: 2021-03-09 18:35+0000\n"
+"POT-Creation-Date: 2021-03-12 15:55+0100\n"
+"PO-Revision-Date: 2021-03-12 14:49+0000\n"
"Last-Translator: Kanoko Kondo <yves0625@gmail.com>\n"
"Language-Team: Japanese <http://weblate.taler.net/projects/gnunet/website/ja/";
">\n"
"Language: ja\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Weblate 4.4.2\n"
@@ -66,6 +66,7 @@ msgid "About"
msgstr "概要"
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
msgstr "更新情報"
@@ -158,17 +159,21 @@ msgstr "REST API"
msgid "FAQ"
msgstr "よくある質問"
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
-msgstr "リリースやイベントなど、GNUnet 関連の各種変更についての情報を掲載しています"
+msgstr ""
+"リリースやイベントなど、GNUnet 関連の各種変更についての情報を掲載しています"
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
msgstr "RSS フィードに登録"
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
msgstr "詳細"
@@ -183,51 +188,58 @@ msgstr "GNUnet とは"
#: template/about.html.j2:13
msgid ""
-"GNUnet is an alternative network stack for building secure, decentralized"
-" and privacy-preserving distributed applications. Our goal is to replace "
-"the old insecure Internet protocol stack. Starting from an application "
-"for secure publication of files, it has grown to include all kinds of "
-"basic protocol components and applications towards the creation of a GNU "
-"internet."
+"GNUnet is an alternative network stack for building secure, decentralized "
+"and privacy-preserving distributed applications. Our goal is to replace the "
+"old insecure Internet protocol stack. Starting from an application for "
+"secure publication of files, it has grown to include all kinds of basic "
+"protocol components and applications towards the creation of a GNU internet."
msgstr ""
-"GNUnet とは、安全、脱一元化、プライバシー保護を実現する分散型プリケーションを構築するための代替ネットワーク スタックであり、"
-"従来型の安全性に欠くインターネット プロトコル "
-"スタックを置き換えることを目的としています。各種ファイルを安全に公開できるアプリケーションとしてスタートし、現在は、あらゆる種類の基本プロトコル "
-"コンポーネントやアプリケーションなどを含め、GNU インターネットの創造を目指しています。"
+"GNUnet とは、安全、脱一元化、プライバシー保護を実現する分散型プリケーションを"
+"構築するための代替ネットワーク スタックであり、従来型の安全性に欠くインター"
+"ネット プロトコル スタックを置き換えることを目的としています。各種ファイルを"
+"安全に公開できるアプリケーションとしてスタートし、現在は、あらゆる種類の基本"
+"プロトコル コンポーネントやアプリケーションなどを含め、GNU インターネットの創"
+"造を目指しています。"
#: template/about.html.j2:23
msgid ""
-"Today, the actual use and thus the social requirements for a global "
-"network differs widely from those goals of 1970. While the Internet "
-"remains suitable for military use, where the network equipment is "
-"operated by a command hierarchy and when necessary isolated from the rest"
-" of the world, the situation is less tenable for civil society."
+"Today, the actual use and thus the social requirements for a global network "
+"differs widely from those goals of 1970. While the Internet remains suitable "
+"for military use, where the network equipment is operated by a command "
+"hierarchy and when necessary isolated from the rest of the world, the "
+"situation is less tenable for civil society."
msgstr ""
-"今日、グローバル ネットワークの実利用、つまり社会的要件は 1970 年の目標とは大きく異なります。ネットワーク機器はコマンド階層によって運用され、必要に"
-"応じて一部のみ切り離すことができるという点で、インターネットは軍事利用に適しているものの、現状では一般市民による利用に適しているとはいえません。"
+"今日、グローバル ネットワークの実利用、つまり社会的要件は 1970 年の目標とは大"
+"きく異なります。ネットワーク機器はコマンド階層によって運用され、必要に応じて"
+"一部のみ切り離すことができるという点で、インターネットは軍事利用に適している"
+"ものの、現状では一般市民による利用に適しているとはいえません。"
#: template/about.html.j2:32
msgid ""
"Due to fundamental Internet design choices, Internet traffic can be "
-"misdirected, intercepted, censored and manipulated by hostile routers on "
-"the network. And indeed, the modern Internet has evolved exactly to the "
-"point where, as Matthew Green put it, <a "
-"href=\"https://blog.cryptographyengineering.com/2015/08/16/the-network-";
-"is-hostile/\">\"the network is hostile\"</a>."
-msgstr ""
-"インターネットの基本設計は、ネットワーク上の悪意あるルーターを経由したトラフィックの誤ダイレクト、傍受、検閲、操作などを可能にしています。実際に現代のイン"
-"ターネットは、マシュー・グリーンによる<a href=\"https://blog.cryptographyengineering.com/2015/";
-"08/16/the-network-is-hostile/\">「ネットワークには敵意がある」</a>という表現を正に体現するに至ったと言えます。"
+"misdirected, intercepted, censored and manipulated by hostile routers on the "
+"network. And indeed, the modern Internet has evolved exactly to the point "
+"where, as Matthew Green put it, <a href=\"https://blog.";
+"cryptographyengineering.com/2015/08/16/the-network-is-hostile/\">\"the "
+"network is hostile\"</a>."
+msgstr ""
+"インターネットの基本設計は、ネットワーク上の悪意あるルーターを経由したトラ"
+"フィックの誤ダイレクト、傍受、検閲、操作などを可能にしています。実際に現代の"
+"インターネットは、マシュー・グリーンによる<a href=\"https://blog.";
+"cryptographyengineering.com/2015/08/16/the-network-is-hostile/\">「ネットワー"
+"クには敵意がある」</a>という表現を正に体現するに至ったと言えます。"
#: template/about.html.j2:41
msgid ""
-"We believe liberal societies need a network architecture that uses the "
-"anti-authoritarian decentralized peer-to-peer paradigm and privacy-"
-"preserving cryptographic protocols. The goal of the GNUnet project is to "
-"provide a Free Software realization of this ideal."
+"We believe liberal societies need a network architecture that uses the anti-"
+"authoritarian decentralized peer-to-peer paradigm and privacy-preserving "
+"cryptographic protocols. The goal of the GNUnet project is to provide a Free "
+"Software realization of this ideal."
msgstr ""
-"自由主義社会には、権威から独立した分散型ピアツーピア パラダイムとプライバシー保護のための暗号プロトコルを使用するネットワーク "
-"アーキテクチャが必要であると私たちは考えます。こうした理想を実現する自由ソフトウェアを提供することが GNUnet プロジェクトの目的です。"
+"自由主義社会には、権威から独立した分散型ピアツーピア パラダイムとプライバシー"
+"保護のための暗号プロトコルを使用するネットワーク アーキテクチャが必要であると"
+"私たちは考えます。こうした理想を実現する自由ソフトウェアを提供することが "
+"GNUnet プロジェクトの目的です。"
#: template/about.html.j2:49
msgid ""
@@ -237,11 +249,11 @@ msgstr "具体的には、GNUnet の設計は次の原則に則っています
#: template/about.html.j2:56
msgid ""
-"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy";
-"/free-sw.html\">Free Software</a>."
+"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy/free-";
+"sw.html\">Free Software</a>."
msgstr ""
-"GNUnet は<a href=\"https://www.gnu.org/philosophy/free-sw.html\"";
-">自由ソフトウェア</a>として実装される。"
+"GNUnet は<a href=\"https://www.gnu.org/philosophy/free-sw.html\";>自由ソフト"
+"ウェア</a>として実装される。"
#: template/about.html.j2:60
msgid ""
@@ -251,21 +263,27 @@ msgstr "公開される PII（個人を特定できる情報）を最小限に
#: template/about.html.j2:61
msgid ""
-"GNUnet must be fully distributed and resilient to external attacks and "
-"rogue participants."
-msgstr "GNUnet は完全な分散型であり、外部からの攻撃や悪質な参加者に対して回復力がなければならない。"
+"GNUnet must be fully distributed and resilient to external attacks and rogue "
+"participants."
+msgstr ""
+"GNUnet は完全な分散型であり、外部からの攻撃や悪質な参加者に対して回復力がなけ"
+"ればならない。"
#: template/about.html.j2:62
msgid ""
"GNUnet must be self-organizing and not depend on administrators or "
"centralized infrastructure."
-msgstr "GNUnet は自律した組織化構造を持ち、管理者や中央一元型インフラストラクチャに依存してはならない。"
+msgstr ""
+"GNUnet は自律した組織化構造を持ち、管理者や中央一元型インフラストラクチャに依"
+"存してはならない。"
#: template/about.html.j2:63
msgid ""
-"GNUnet must inform the user which other participants have to be trusted "
-"when establishing private communications."
-msgstr "GNUnet は、プライベート通信を確立する際、信頼すべき他の参加者をユーザーに通知する。"
+"GNUnet must inform the user which other participants have to be trusted when "
+"establishing private communications."
+msgstr ""
+"GNUnet は、プライベート通信を確立する際、信頼すべき他の参加者をユーザーに通知"
+"する。"
#: template/about.html.j2:64
msgid "GNUnet must be open and permit new peers to join."
@@ -273,7 +291,8 @@ msgstr "GNUnet はオープンであり、新しい参加者を受け入れな
#: template/about.html.j2:65
msgid "GNUnet must support a diverse range of applications and devices."
-msgstr "GNUnet は、さまざまなアプリケーションやデバイスに対応しなければならない。"
+msgstr ""
+"GNUnet は、さまざまなアプリケーションやデバイスに対応しなければならない。"
#: template/about.html.j2:66
msgid "GNUnet must use compartmentalization to protect sensitive information."
@@ -285,48 +304,46 @@ msgstr "GNUnet アーキテクチャはリソース効率が高くなければ
#: template/about.html.j2:68
msgid ""
-"GNUnet must provide incentives for peers to contribute more resources "
-"than they consume."
-msgstr "GNUnet は、リソースの消費を超える貢献をしてもらうため、ピアを動機づけしなければならない。"
+"GNUnet must provide incentives for peers to contribute more resources than "
+"they consume."
+msgstr ""
+"GNUnet は、リソースの消費を超える貢献をしてもらうため、ピアを動機づけしなけれ"
+"ばならない。"
#: template/about.html.j2:72
msgid ""
-"To get know and learn more, please check our <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, "
-"especially the <a href=\"https://docs.gnunet.org/handbook/gnunet.html";
-"#Key-Concepts\">chapter on \"Key Concepts\"</a>, explaining the "
-"fundamental concepts of GNUnet: <ul> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Authentication\";>Authentication</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Accounting-";
-"to-Encourage-Resource-Sharing\">Accounting to Encourage Resource "
-"Sharing</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Confidentiality\";>Confidentiality</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability\";>Deniability</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Peer-";
-"Identities\">Peer Identities</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-";
-"Name-System-_0028GNS-Zones_0029\">Zones in the GNU Name System (GNS "
-"Zones)</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> "
-"</ul>"
-msgstr ""
-"詳細は<a href=\"https://docs.gnunet.org/handbook/gnunet.html\";>ハンドブック</a>中の、特に "
-"GNUnet の基本概念を説明する<a href=\"https://docs.gnunet.org/handbook/gnunet.html#Key-";
-"Concepts\">「主要概念」の章</a>を参照してください。<ul><li><a href=\"https://docs.gnunet.org/";
-"handbook/gnunet.html#Authentication\">認証</a></li><li><a href=\"https://docs.";
-"gnunet.org/handbook/gnunet.html#Accounting-to-Encourage-Resource-Sharing\""
-">リソース共有の奨励</a></li><li><a href=\"https://docs.gnunet.org/handbook/gnunet.";
-"html#Confidentiality\">守秘義務</a></li><li><a href=\"https://docs.gnunet.org/";
-"handbook/gnunet.html#Anonymity\">匿名性</a></li><li><a href=\"https://docs.";
-"gnunet.org/handbook/gnunet.html#Deniability\">否認権</a></li><li><a href=\"https"
-"://docs.gnunet.org/handbook/gnunet.html#Peer-Identities\">ピア ID</a></"
-"li><li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Zones-in-the-";
-"GNU-Name-System-_0028GNS-Zones_0029\">GNU ネーム システムのゾーン（GNS ゾーン）</a></"
-"li><li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Egos\"";
-">Egos</a></li></ul>"
+"To get know and learn more, please check our <a href=\"https://docs.gnunet.";
+"org/handbook/gnunet.html\">handbook</a>, especially the <a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Key-Concepts\">chapter on \"Key Concepts"
+"\"</a>, explaining the fundamental concepts of GNUnet: <ul> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Authentication";
+"\">Authentication</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Accounting-to-Encourage-Resource-Sharing\">Accounting to "
+"Encourage Resource Sharing</a></li> <li><a href=\"https://docs.gnunet.org/";
+"handbook/gnunet.html#Confidentiality\">Confidentiality</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></"
+"li> <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability";
+"\">Deniability</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Peer-Identities\">Peer Identities</a></li> <li><a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-Name-System-_0028GNS-"
+"Zones_0029\">Zones in the GNU Name System (GNS Zones)</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> </ul>"
+msgstr ""
+"詳細は<a href=\"https://docs.gnunet.org/handbook/gnunet.html\";>ハンドブック</"
+"a>中の、特に GNUnet の基本概念を説明する<a href=\"https://docs.gnunet.org/";
+"handbook/gnunet.html#Key-Concepts\">「主要概念」の章</a>を参照してください。"
+"<ul><li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Authentication";
+"\">認証</a></li><li><a href=\"https://docs.gnunet.org/handbook/gnunet.";
+"html#Accounting-to-Encourage-Resource-Sharing\">リソース共有の奨励</a></"
+"li><li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Confidentiality";
+"\">守秘義務</a></li><li><a href=\"https://docs.gnunet.org/handbook/gnunet.";
+"html#Anonymity\">匿名性</a></li><li><a href=\"https://docs.gnunet.org/";
+"handbook/gnunet.html#Deniability\">否認権</a></li><li><a href=\"https://docs.";
+"gnunet.org/handbook/gnunet.html#Peer-Identities\">ピア ID</a></li><li><a "
+"href=\"https://docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-Name-";
+"System-_0028GNS-Zones_0029\">GNU ネーム システムのゾーン（GNS ゾーン）</a></"
+"li><li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</"
+"a></li></ul>"
#: template/about.html.j2:88
msgid "More Resources"
@@ -334,35 +351,38 @@ msgstr "その他のリソース"
#: template/about.html.j2:90
msgid ""
-"There are many more resources to learn about GNUnet besides the <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such "
-"as the <a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers "
-"covering the various layers, many <a "
-"href=\"https://gnunet.org/en/video.html\";>videos</a> or a brief <a "
-"href=\"https://gnunet.org/en/glossary.html\";>glossary</a>."
+"There are many more resources to learn about GNUnet besides the <a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such as the "
+"<a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers covering "
+"the various layers, many <a href=\"https://gnunet.org/en/video.html";
+"\">videos</a> or a brief <a href=\"https://gnunet.org/en/glossary.html";
+"\">glossary</a>."
msgstr ""
-"GNUnet の詳細については、<a href=\"https://docs.gnunet.org/handbook/gnunet.html\"";
-">ハンドブック</a>以外にも多くのリソースがあり、一例としては、多角的な視点での論文を集めた<a href=\"https://bib.gnunet.";
-"org/\">参考文献</a>、各種<a href=\"https://gnunet.org/en/video.html\";>動画</a>、簡潔な<a "
-"href=\"https://gnunet.org/en/glossary.html\";>用語集</a>などが挙げられます。"
+"GNUnet の詳細については、<a href=\"https://docs.gnunet.org/handbook/gnunet.";
+"html\">ハンドブック</a>以外にも多くのリソースがあり、一例としては、多角的な視"
+"点での論文を集めた<a href=\"https://bib.gnunet.org/\";>参考文献</a>、各種<a "
+"href=\"https://gnunet.org/en/video.html\";>動画</a>、簡潔な<a href=\"https://";
+"gnunet.org/en/glossary.html\">用語集</a>などが挙げられます。"
#: template/about.html.j2:95
msgid ""
"You are most welcome to <a href=\"engage.html\">get engaged into the "
-"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a "
-"href=\"use.html\">use it</a> and <a href=\"engage.html\">contribute and "
-"get engaged</a> in various ways."
+"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a href=\"use."
+"html\">use it</a> and <a href=\"engage.html\">contribute and get engaged</a> "
+"in various ways."
msgstr ""
"<a href=\"engage.html\">会話に参加する</a>、<a href=\"install.html\">GNUnet "
-"をインストールする</a>、<a href=\"use.html\">実際に利用する</a>、<a href=\"engage.html\""
-">貢献して参加する</a>など、さまざまな方法で活用いただけます。"
+"をインストールする</a>、<a href=\"use.html\">実際に利用する</a>、<a href="
+"\"engage.html\">貢献して参加する</a>など、さまざまな方法で活用いただけます。"
#: template/about.html.j2:100
msgid ""
-"Please be aware that this project is (despite of it's age) still in an "
-"early alpha stage when it comes to software – its not an easy task "
-"to rewrite the whole Internet!"
-msgstr "このプロジェクトは、ソフトウェア–に関してまだ初期のアルファ段階にあり、インターネット全体の書き換えはまだ現実的ではありません。"
+"Please be aware that this project is (despite of it's age) still in an early "
+"alpha stage when it comes to software – its not an easy task to "
+"rewrite the whole Internet!"
+msgstr ""
+"このプロジェクトは、ソフトウェア–に関してまだ初期のアルファ段階にあり、"
+"インターネット全体の書き換えはまだ現実的ではありません。"
#: template/about.html.j2:105
msgid "Current funding"
@@ -370,31 +390,34 @@ msgstr "現在の資金調達"
#: template/about.html.j2:110
msgid ""
-"We're receiving funding from NLnet's Next Generation Internet funding "
-"line to document and implement the GNU Name System protocol in a way "
-"suitable for the IETF standardization process."
+"We're receiving funding from NLnet's Next Generation Internet funding line "
+"to document and implement the GNU Name System protocol in a way suitable for "
+"the IETF standardization process."
msgstr ""
-"NLnet の次世代インターネット資金ラインから支援を受け、IETF 標準化プロセスに適合させる形で GNU "
-"ネームシステムプロトコルを文書化し、実装しています。"
+"NLnet の次世代インターネット資金ラインから支援を受け、IETF 標準化プロセスに適"
+"合させる形で GNU ネームシステムプロトコルを文書化し、実装しています。"
#: template/about.html.j2:123
msgid ""
"This project has received funding from the European Union’s Horizon 2020 "
"research and innovation programme under the NGI_TRUST grant agreement no "
-"825618. The project aims to integrate re:claimID with the GNU Taler "
-"payment system in a pilot in order to demonstrate the practical "
-"feasibility and benefits of privacy enhancing technologies for users and "
-"commercial service providers. The project is called \"Decentralized "
-"Identities for Self-Sovereign End-users\" (DISSENS)."
-msgstr ""
-"このプロジェクトは、欧州連合の「Horizon 2020」研究・イノベーションプログラムから NGI_TRUST 補助金契約 No. 825618 "
-"に基づき資金を受け取っています。本プロジェクトは、re:claimID および、試験段階にある GNU Taler 支払いシステムを統合することで、ユーザ"
-"ーと商用サービスプロバイダーに向け、実用への可能性とプライバシー向上技術の利点を証明することを目指しています。プロジェクトは「Decentralized "
-"Identities for Self-Sovereign End-uers（DISSENS：自己主権を持つエンドユーザーのための脱中央型 "
-"ID）」と呼ばれます。"
+"825618. The project aims to integrate re:claimID with the GNU Taler payment "
+"system in a pilot in order to demonstrate the practical feasibility and "
+"benefits of privacy enhancing technologies for users and commercial service "
+"providers. The project is called \"Decentralized Identities for Self-"
+"Sovereign End-users\" (DISSENS)."
+msgstr ""
+"このプロジェクトは、欧州連合の「Horizon 2020」研究・イノベーションプログラム"
+"から NGI_TRUST 補助金契約 No. 825618 に基づき資金を受け取っています。本プロ"
+"ジェクトは、re:claimID および、試験段階にある GNU Taler 支払いシステムを統合"
+"することで、ユーザーと商用サービスプロバイダーに向け、実用への可能性とプライ"
+"バシー向上技術の利点を証明することを目指しています。プロジェクトは"
+"「Decentralized Identities for Self-Sovereign End-uers（DISSENS：自己主権を持"
+"つエンドユーザーのための脱中央型 ID）」と呼ばれます。"
#: template/about.html.j2:141
-msgid "We are grateful for free hosting offered by the following
organizations:"
+msgid ""
+"We are grateful for free hosting offered by the following organizations:"
msgstr "次の組織により無料でホスティングを提供いただいています。"
#: template/about.html.j2:150
@@ -415,18 +438,19 @@ msgstr "GNU ネームシステム"
#: template/applications.html.j2:15
msgid ""
-"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully "
-"decentralized replacement for the Domain Name System (DNS). Instead of "
-"using a hierarchy, GNS uses a directed graph. Naming conventions are "
-"similar to DNS, but queries and replies are private even with respect to "
-"peers providing the answers. The integrity of records and privacy of "
-"look-ups is cryptographically secured. <!-- Too technical: GNS integrates"
-" a robust, efficient and instant key revocation mechanism. -->"
-msgstr ""
-"<a href=\"gns.html\">GNU "
-"ネームシステム（GNS）</a>は、ドメインネームシステム（DNS）が完全に分散されたもので、その代替です。GNU "
-"は階層構造に代わり有向グラフを使用します。命名規則は DNS に類似していますが、クエリと応答は、回答をするピアに関してもプライベートです。レコードの完全"
-"性とルックアップのプライバシーはセキュアに暗号化されます。<!-- Too technical: GNS integrates a robust, "
+"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully decentralized "
+"replacement for the Domain Name System (DNS). Instead of using a hierarchy, "
+"GNS uses a directed graph. Naming conventions are similar to DNS, but "
+"queries and replies are private even with respect to peers providing the "
+"answers. The integrity of records and privacy of look-ups is "
+"cryptographically secured. <!-- Too technical: GNS integrates a robust, "
+"efficient and instant key revocation mechanism. -->"
+msgstr ""
+"<a href=\"gns.html\">GNU ネームシステム（GNS）</a>は、ドメインネームシステム"
+"（DNS）が完全に分散されたもので、その代替です。GNU は階層構造に代わり有向グラ"
+"フを使用します。命名規則は DNS に類似していますが、クエリと応答は、回答をする"
+"ピアに関してもプライベートです。レコードの完全性とルックアップのプライバシー"
+"はセキュアに暗号化されます。<!-- Too technical: GNS integrates a robust, "
"efficient and instant key revocation mechanism. -->"
#: template/applications.html.j2:38
@@ -435,15 +459,15 @@ msgstr "自己主権型、脱中央型の IdP"
#: template/applications.html.j2:40
msgid ""
-"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized"
-" Identity Provider (IdP) service built in top of the GNU Name System. It "
+"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized "
+"Identity Provider (IdP) service built in top of the GNU Name System. It "
"allows users to securely share personal information with websites using "
"standardized protocols (OpenID Connect)."
msgstr ""
-"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> は分散型のアイデンティティ "
-"プロバイダ（IdP）サービスであり、GNU "
-"ネームシステムの上位に組み込まれています。これによりユーザーは、標準化されたプロトコルを使い、ウェブサイトから個人情報を安全に共有することができます（"
-"OpenID Connect）。"
+"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> は分散型のアイデンティ"
+"ティ プロバイダ（IdP）サービスであり、GNU ネームシステムの上位に組み込まれて"
+"います。これによりユーザーは、標準化されたプロトコルを使い、ウェブサイトから"
+"個人情報を安全に共有することができます（OpenID Connect）。"
#: template/applications.html.j2:57
msgid "Filesharing (Alpha)"
@@ -451,13 +475,13 @@ msgstr "ファイル共有（アルファ）"
#: template/applications.html.j2:59
msgid ""
-"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that "
-"aims to provide censorship-resistant, anonymous filesharing. The "
-"publisher is empowered to make a gradual choice between performance and "
-"anonymity."
+"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that aims "
+"to provide censorship-resistant, anonymous filesharing. The publisher is "
+"empowered to make a gradual choice between performance and anonymity."
msgstr ""
-"GNUnet の<a href=\"use.html#fs\">ファイル共有</a>は、検閲耐性と匿名性を備えたファイル共有を目指すアプリケーションです。"
-"発行者は、パフォーマンスと匿名性の度合いを自在に選択することができます。"
+"GNUnet の<a href=\"use.html#fs\">ファイル共有</a>は、検閲耐性と匿名性を備えた"
+"ファイル共有を目指すアプリケーションです。発行者は、パフォーマンスと匿名性の"
+"度合いを自在に選択することができます。"
#: template/applications.html.j2:73
msgid "Conversation (Pre-Alpha)"
@@ -466,11 +490,11 @@ msgstr "カンバセーション（プレアルファ）"
#: template/applications.html.j2:75
msgid ""
"GNUnet conversation is an application that provides secure voice "
-"communication in a fully decentralized way by employing GNUnet for "
-"routing and transport."
+"communication in a fully decentralized way by employing GNUnet for routing "
+"and transport."
msgstr ""
-"GNUnet カンバセーションは、ルーティングとトランスポートに GNUnet "
-"を採用することにより、完全分散型の安全な音声通話を提供するアプリケーションです。"
+"GNUnet カンバセーションは、ルーティングとトランスポートに GNUnet を採用するこ"
+"とにより、完全分散型の安全な音声通話を提供するアプリケーションです。"
#: template/applications.html.j2:91
msgid "Applications utilizing GNUnet"
@@ -483,11 +507,12 @@ msgstr "GNU Taler（アルファ）"
#: template/applications.html.j2:99
msgid ""
"<a href=\"https://taler.net/\";>GNU Taler</a> is a new privacy-preserving "
-"electronic payment system. Payments are cryptographically secured and are"
-" confirmed within milliseconds with extremely low transaction costs."
+"electronic payment system. Payments are cryptographically secured and are "
+"confirmed within milliseconds with extremely low transaction costs."
msgstr ""
-"<a href=\"https://taler.net/\";>GNU Taler</a> "
-"は、プライバシーを保護する新しい電子決済システムです。決済はセキュアに暗号化され、数ミリ秒で完了、トランザクションも大変低コストです。"
+"<a href=\"https://taler.net/\";>GNU Taler</a> は、プライバシーを保護する新しい"
+"電子決済システムです。決済はセキュアに暗号化され、数ミリ秒で完了、トランザク"
+"ションも大変低コストです。"
#: template/applications.html.j2:118
msgid "secushare"
@@ -495,14 +520,15 @@ msgstr "secushare"
#: template/applications.html.j2:120
msgid ""
-"<a href=\"https://secushare.org/\";>secushare</a> is creating a "
-"decentralized social networking application on top of GNUnet. Using "
-"overlay multicast and the extensible PSYC protocol, notifications are "
-"distributed end-to-end encrypted to authorized recipients only."
+"<a href=\"https://secushare.org/\";>secushare</a> is creating a decentralized "
+"social networking application on top of GNUnet. Using overlay multicast and "
+"the extensible PSYC protocol, notifications are distributed end-to-end "
+"encrypted to authorized recipients only."
msgstr ""
-"<a href=\"https://secushare.org/\";>secushare</a> は、GNUnet 上に分散型ソーシャルネットワーキング "
-"アプリケーションを作成しています。オーバーレイ マルチキャスト、拡張可能な PSYC "
-"プロトコル、通知機能がエンドツーエンドで暗号化され、承認済みの受信者にのみ配信されます。"
+"<a href=\"https://secushare.org/\";>secushare</a> は、GNUnet 上に分散型ソー"
+"シャルネットワーキング アプリケーションを作成しています。オーバーレイ マルチ"
+"キャスト、拡張可能な PSYC プロトコル、通知機能がエンドツーエンドで暗号化さ"
+"れ、承認済みの受信者にのみ配信されます。"
#: template/applications.html.j2:139
msgid "pretty Easy privacy"
@@ -510,14 +536,15 @@ msgstr "pretty Easy privacy"
#: template/applications.html.j2:141
msgid ""
-"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) "
-"is creating a usable end-to-end encrypted e-mail solution using "
-"opportunistic key exchange. p≡p will use GNUnet to protect metadata"
-" and exploit new cryptographic protocols to verify keys."
+"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) is "
+"creating a usable end-to-end encrypted e-mail solution using opportunistic "
+"key exchange. p≡p will use GNUnet to protect metadata and exploit new "
+"cryptographic protocols to verify keys."
msgstr ""
-"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a>（p≡p）は、日和見鍵交"
-"換を使用して、実用性のあるエンドツーエンドで暗号化された電子メールソリューションを作成しています。p≡p は GNUnet "
-"によりメタデータを保護し、新たな暗号化プロトコルで鍵を検証します。"
+"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a>（p≡p）は、"
+"日和見鍵交換を使用して、実用性のあるエンドツーエンドで暗号化された電子メール"
+"ソリューションを作成しています。p≡p は GNUnet によりメタデータを保護"
+"し、新たな暗号化プロトコルで鍵を検証します。"
#: template/applications.html.j2:160
msgid "Cadet-GTK"
@@ -525,14 +552,15 @@ msgstr "Cadet-GTK"
#: template/applications.html.j2:162
msgid ""
-"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> "
-"is a convenient but feature-rich graphical application providing "
-"messaging using especially the CADET subsystem. It is developed using GTK"
-" and libhandy for a convergent design."
+"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> is a "
+"convenient but feature-rich graphical application providing messaging using "
+"especially the CADET subsystem. It is developed using GTK and libhandy for a "
+"convergent design."
msgstr ""
"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> は、"
-"高い利便性と豊富な機能を備えたグラフィカル アプリケーションで、特に CADET サブシステムを使用してメッセージ機能を提供します。GTK と "
-"libhandy を利用して開発されいます。"
+"高い利便性と豊富な機能を備えたグラフィカル アプリケーションで、特に CADET サ"
+"ブシステムを使用してメッセージ機能を提供します。GTK と libhandy を利用して開"
+"発されいます。"
#: template/applications.html.j2:180
msgid "groupchat"
@@ -542,12 +570,13 @@ msgstr "groupchat"
msgid ""
"<a href=\"https://git.gnunet.org/groupchat.git/\";>groupchat</a> is a "
"terminal user interface providing messaging using especially the CADET "
-"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned"
-" to be compatible."
+"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned to "
+"be compatible."
msgstr ""
-"<a href=\"https://git.gnunet.org/groupchat.git/\";>groupchat</a> は、主に CADET "
-"サブシステムを使用してメッセージ機能を提供するターミナル ユーザーインターフェースです。開発言語は Nim で、将来的には Cadet-GTK と "
-"groupchat と互換性を持つ予定です。"
+"<a href=\"https://git.gnunet.org/groupchat.git/\";>groupchat</a> は、主に "
+"CADET サブシステムを使用してメッセージ機能を提供するターミナル ユーザーイン"
+"ターフェースです。開発言語は Nim で、将来的には Cadet-GTK と groupchat と互換"
+"性を持つ予定です。"
#: template/architecture.html.j2:6
msgid "GNUnet System Architecture"
@@ -559,16 +588,17 @@ msgstr "基盤"
#: template/architecture.html.j2:22
msgid ""
-"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-"
-"like end-to-end encrypted messaging layer (CADET), a public key "
-"infrastructure (GNS) and a pluggable transport system (TRANSPORT).<br> "
-"Using public keys for addresses and self-organized decentralized routing "
-"algorithms, these subsystems replace the traditional TCP/IP stack."
+"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-like "
+"end-to-end encrypted messaging layer (CADET), a public key infrastructure "
+"(GNS) and a pluggable transport system (TRANSPORT).<br> Using public keys "
+"for addresses and self-organized decentralized routing algorithms, these "
+"subsystems replace the traditional TCP/IP stack."
msgstr ""
-"GNUnet の基盤は、分散ハッシュ テーブル（R5N）、SCTP に類似したエンド ツー "
-"エンドの暗号化メッセージング層（CADET）、公開鍵基盤（GNS）、プラグ可能なトランスポート "
-"システム（TRANSPORT）です。<br>これらのサブシステムは、アドレスや自己組織する分散型ルーティング アルゴリズムに公開鍵を使用し、従来の "
-"TCP/IP スタックに代替するものです。"
+"GNUnet の基盤は、分散ハッシュ テーブル（R5N）、SCTP に類似したエンド ツー エ"
+"ンドの暗号化メッセージング層（CADET）、公開鍵基盤（GNS）、プラグ可能なトラン"
+"スポート システム（TRANSPORT）です。<br>これらのサブシステムは、アドレスや自"
+"己組織する分散型ルーティング アルゴリズムに公開鍵を使用し、従来の TCP/IP ス"
+"タックに代替するものです。"
#: template/architecture.html.j2:35
msgid "Security"
@@ -578,13 +608,14 @@ msgstr "セキュリティ"
msgid ""
"GNUnet is implemented using a multi-process architecture. Each subsystem "
"runs as a separate process, providing fault-isolation and enabling tight "
-"permissions to be granted to each subsystem. Naturally, the "
-"implementation is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and"
-" will always remain free software."
+"permissions to be granted to each subsystem. Naturally, the implementation "
+"is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and will always "
+"remain free software."
msgstr ""
-"GNUnet はマルチプロセス "
-"アーキテクチャを使用して実装されます。各サブシステムは別々のプロセスとして実行され、問題の切り分けや厳格な権限付与がサブシステム毎に可能です。そのため、"
-"実装は<a href=\"https://www.gnu.org/\";> GNU</a> パッケージであり、その後も自由ソフトウェアであり続けます。"
+"GNUnet はマルチプロセス アーキテクチャを使用して実装されます。各サブシステム"
+"は別々のプロセスとして実行され、問題の切り分けや厳格な権限付与がサブシステム"
+"毎に可能です。そのため、実装は<a href=\"https://www.gnu.org/\";> GNU</a> パッ"
+"ケージであり、その後も自由ソフトウェアであり続けます。"
#: template/architecture.html.j2:52
msgid "System architecture"
@@ -616,16 +647,16 @@ msgstr "メーリングリスト"
#: template/contact.html.j2:13
msgid ""
-"An archived, public mailing list for GNUnet is hosted at <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers\">https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>. You can send messages to the list at <a href=\"mailto"
-":gnunet-developers@gnu.org\">gnunet-developers@gnu.org</a>."
+"An archived, public mailing list for GNUnet is hosted at <a href=\"https://";
+"lists.gnu.org/mailman/listinfo/gnunet-developers\">https://lists.gnu.org/";
+"mailman/listinfo/gnunet-developers</a>. You can send messages to the list at "
+"<a href=\"mailto:gnunet-developers@gnu.org\";>gnunet-developers@gnu.org</a>."
msgstr ""
-"GNUnet の公開メーリング リストのアーカイブは<a href=\"https://lists.gnu.org/mailman/listinfo/";
-"gnunet-developers\">https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>にホストされています。このリストへのメッセージは<a href=\"mailto:gnunet-developers@gnu.";
-"org\">gnunet-developers@gnu.org</a>から送信できます。"
+"GNUnet の公開メーリング リストのアーカイブは<a href=\"https://lists.gnu.org/";
+"mailman/listinfo/gnunet-developers\">https://lists.gnu.org/mailman/listinfo/";
+"gnunet-developers</a>にホストされています。このリストへのメッセージは<a href="
+"\"mailto:gnunet-developers@gnu.org\";>gnunet-developers@gnu.org</a>から送信で"
+"きます。"
#: template/contact.html.j2:23
msgid "The IRC channel"
@@ -633,14 +664,13 @@ msgstr "IRC チャネル"
#: template/contact.html.j2:25
msgid ""
-"<tt>#gnunet</tt> is reachable via <a "
-"href=\"https://freenode.net\";>irc.freenode.net</a>. There is also an <a "
-"href=\"https://view.matrix.org/room/!IjaAfLiruzjxFFzKAV:matrix.org/\";>archive</a>"
-" available."
+"<tt>#gnunet</tt> is reachable via <a href=\"https://freenode.net\";>irc."
+"freenode.net</a>. There is also an <a href=\"https://view.matrix.org/room/!";
+"IjaAfLiruzjxFFzKAV:matrix.org/\">archive</a> available."
msgstr ""
-"<tt>#gnune</tt>は<a href=\"https://freenode.net\";>irc.freenode."
-"net</a>からアクセスできます。また、<a href=\"https://view.matrix.org/room/";
-"!IjaAfLiruzjxFFzKAV:matrix.org/\">アーカイブ</a>はこちらです。"
+"<tt>#gnune</tt>は<a href=\"https://freenode.net\";>irc.freenode.net</a>からア"
+"クセスできます。また、<a href=\"https://view.matrix.org/room/!";
+"IjaAfLiruzjxFFzKAV:matrix.org/\">アーカイブ</a>はこちらです。"
#: template/contact.html.j2:38
msgid "Contacting individuals"
@@ -648,16 +678,16 @@ msgstr "個人へのお問い合わせ"
#: template/contact.html.j2:40
msgid ""
-"GNUnet developers are generally reachable at either "
-"<tt>PSEUDONYM@gnunet.org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us"
-" support receiving GnuPG encrypted Emails. Urgent and sensitive security "
-"issues may be addressed to the GNU maintainers <tt>schanzen</tt> and "
-"<tt>grothoff</tt>."
+"GNUnet developers are generally reachable at either <tt>PSEUDONYM@gnunet."
+"org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us support receiving GnuPG "
+"encrypted Emails. Urgent and sensitive security issues may be addressed to "
+"the GNU maintainers <tt>schanzen</tt> and <tt>grothoff</tt>."
msgstr ""
-"GNUnet 開発者へのご連絡は、通常 <tt>PSEUDONYM@gnunet.org</tt> または <tt>LASTNAME@gnunet."
-"org</tt> から可能です。ほとんどのメンバーは GnuPG "
-"暗号化メールの受信に対応しています。緊急の場合や機密性の高いセキュリティ関連の問題については、GNU 保守を担当する <tt> schanzen</"
-"tt> および <tt> grothoff</tt> までご連絡ください。"
+"GNUnet 開発者へのご連絡は、通常 <tt>PSEUDONYM@gnunet.org</tt> または "
+"<tt>LASTNAME@gnunet.org</tt> から可能です。ほとんどのメンバーは GnuPG 暗号化"
+"メールの受信に対応しています。緊急の場合や機密性の高いセキュリティ関連の問題"
+"については、GNU 保守を担当する <tt> schanzen</tt> および <tt> grothoff</tt> "
+"までご連絡ください。"
#: template/contact.html.j2:53
msgid "Reporting bugs"
@@ -665,50 +695,55 @@ msgstr "バグの報告"
#: template/contact.html.j2:55
msgid ""
-"We track open feature requests and bugs for projects within GNUnet in our"
-" <a href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also "
-"report bugs or feature requests to the <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/bug-gnunet\";>bug-gnunet</a>"
-" mailing list. The mailinglist requires no subscription."
+"We track open feature requests and bugs for projects within GNUnet in our <a "
+"href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also report bugs "
+"or feature requests to the <a href=\"https://lists.gnu.org/mailman/listinfo/";
+"bug-gnunet\">bug-gnunet</a> mailing list. The mailinglist requires no "
+"subscription."
msgstr ""
-"GNUnet 内の各種プロジェクトの公開機能リクエストやバグは、<a href=\"https://bugs.gnunet.org/\";>バグ "
-"トラッカー</a>で管理しています。バグの報告や機能リクエストは、<a href=\"https://lists.gnu.org/mailman/";
-"listinfo/bug-gnunet\">bug-gnunet</a> のメーリングリストからも送信できます。メーリングリストへの登録は必要ありません。"
+"GNUnet 内の各種プロジェクトの公開機能リクエストやバグは、<a href=\"https://";
+"bugs.gnunet.org/\">バグ トラッカー</a>で管理しています。バグの報告や機能リク"
+"エストは、<a href=\"https://lists.gnu.org/mailman/listinfo/bug-gnunet\";>bug-"
+"gnunet</a> のメーリングリストからも送信できます。メーリングリストへの登録は必"
+"要ありません。"
#: template/copyright.html.j2:11
msgid ""
-"<p> Contributors to GNUnet with Git access must sign the <a "
-"href=\"/static/pdf/copyright.pdf\">copyright assignment</a> to ensure "
-"that the <a href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/gnunet_taler_agreement.tex\">GNUnet e.V. --- Taler Systems SA"
-" agreement on licensing and collaborative development</a> of the GNUnet "
-"and GNU Taler projects is satisfied. </p>"
+"<p> Contributors to GNUnet with Git access must sign the <a href=\"/static/"
+"pdf/copyright.pdf\">copyright assignment</a> to ensure that the <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/gnunet_taler_agreement.tex";
+"\">GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative "
+"development</a> of the GNUnet and GNU Taler projects is satisfied. </p>"
msgstr ""
-"<p>GNUnet の参加者で Git を使われている場合、<a href=\"/static/pdf/copyright.pdf\""
-">著作権譲渡書</a>に合意し、GNUnet および GNU Taler プロジェクトの「<a href=\"https://git.gnunet.";
-"org/gnunet-ev.git/tree/gnunet_taler_agreement.tex\">GNUnet e.V. --- "
-"ライセンスと共同開発についての Taler システム SA 合意</a>」に順守することが必要となります。</p>"
+"<p>GNUnet の参加者で Git を使われている場合、<a href=\"/static/pdf/copyright."
+"pdf\">著作権譲渡書</a>に合意し、GNUnet および GNU Taler プロジェクトの「<a "
+"href=\"https://git.gnunet.org/gnunet-ev.git/tree/gnunet_taler_agreement.tex";
+"\">GNUnet e.V. --- ライセンスと共同開発についての Taler システム SA 合意</"
+"a>」に順守することが必要となります。</p>"
#: template/copyright.html.j2:22
msgid ""
-"<p>The agreements ensure that the code will continue to be made available"
-" under free software licenses, but gives developers the freedom to move "
-"code between GNUnet and GNU Taler without worrying about licenses and to "
-"give the company the ability to dual-license (for example, so that we can"
-" distribute via App-stores that are hostile to free software).</p>"
+"<p>The agreements ensure that the code will continue to be made available "
+"under free software licenses, but gives developers the freedom to move code "
+"between GNUnet and GNU Taler without worrying about licenses and to give the "
+"company the ability to dual-license (for example, so that we can distribute "
+"via App-stores that are hostile to free software).</p>"
msgstr ""
-"<p>本合意により、今後も自由ソフトウェア ライセンスのもとでコードの公開が可能となり、開発者は GNUnet と GNU Taler の両方の許諾を得な"
-"くても双方でプログラムのコードを使うことができます。（例えば、自由ソフトウェアに好意的でないアプリストアを通じた配布も可能となります。）</p>"
+"<p>本合意により、今後も自由ソフトウェア ライセンスのもとでコードの公開が可能"
+"となり、開発者は GNUnet と GNU Taler の両方の許諾を得なくても双方でプログラム"
+"のコードを使うことができます。（例えば、自由ソフトウェアに好意的でないアプリ"
+"ストアを通じた配布も可能となります。）</p>"
#: template/copyright.html.j2:30
msgid ""
-"<p>Minor contributions (basically, anyone without Git access) do not "
-"require copyright assignment. Pseudonymous contributions are accepted, in"
-" this case simply sign the agreement with your pseudonym. Scanned copies "
-"are sufficient, but snail mail is preferred.</p>"
+"<p>Minor contributions (basically, anyone without Git access) do not require "
+"copyright assignment. Pseudonymous contributions are accepted, in this case "
+"simply sign the agreement with your pseudonym. Scanned copies are "
+"sufficient, but snail mail is preferred.</p>"
msgstr ""
-"<p>Git アクセス権のない方のご協力については、著作権譲渡書は不要です。偽名でご協力いただくことも可能ですが、著作権譲渡書も同じ偽名で署名してください"
-"。スキャンしたコピーも受け付けていますが、郵送を推奨しています。</p>"
+"<p>Git アクセス権のない方のご協力については、著作権譲渡書は不要です。偽名でご"
+"協力いただくことも可能ですが、著作権譲渡書も同じ偽名で署名してください。ス"
+"キャンしたコピーも受け付けていますが、郵送を推奨しています。</p>"
#: template/developers.html.j2:5
msgid "GNUnet for developers"
@@ -720,17 +755,19 @@ msgstr "レポジトリ"
#: template/developers.html.j2:16
msgid ""
-"A list of our Git repositories can be found on our our <a "
-"href=\"https://git.gnunet.org/\";>Git Server</a>."
+"A list of our Git repositories can be found on our our <a href=\"https://git.";
+"gnunet.org/\">Git Server</a>."
msgstr ""
"Git レポジトリのリストは <a href=\"https://git.gnunet.org/\";>Git Server</a> "
"からご確認いただけます。"
#: template/developers.html.j2:27
msgid ""
-"Technical papers can be found in our <a "
-"href=\"https://old.gnunet.org/bibliography\";>bibliography</a>."
-msgstr "技術論文は<a href=\"https://old.gnunet.org/bibliography\";>参考文献</a>に掲載しています。"
+"Technical papers can be found in our <a href=\"https://old.gnunet.org/";
+"bibliography\">bibliography</a>."
+msgstr ""
+"技術論文は<a href=\"https://old.gnunet.org/bibliography\";>参考文献</a>に掲載"
+"しています。"
#: template/developers.html.j2:34
msgid "Discussion"
@@ -738,14 +775,15 @@ msgstr "ディスカッション"
#: template/developers.html.j2:37
msgid ""
-"We have a mailing list for developer discussions. You can subscribe to or"
-" read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo";
-"/gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>."
+"We have a mailing list for developer discussions. You can subscribe to or "
+"read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo/";
+"gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-developers</"
+"a>."
msgstr ""
-"開発者向けディスカッション用にメーリングリストを用意しています。登録やアーカイブの閲覧は、<a href=\"http://lists.gnu.org/";
-"mailman/listinfo/gnunet-developers\">http://lists.gnu.org/mailman/listinfo/";
-"gnunet-developers</a> から可能です。"
+"開発者向けディスカッション用にメーリングリストを用意しています。登録やアーカ"
+"イブの閲覧は、<a href=\"http://lists.gnu.org/mailman/listinfo/gnunet-";
+"developers\">http://lists.gnu.org/mailman/listinfo/gnunet-developers</a> から"
+"可能です。"
#: template/developers.html.j2:47
msgid "Regression Testing"
@@ -753,13 +791,13 @@ msgstr "回帰テスト"
#: template/developers.html.j2:50
msgid ""
-"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests "
-"to detect regressions and check for portability at <a "
-"href=\"https://old.gnunet.org/buildbot/gnunet/\";>https://old.gnunet.org/buildbot/gnunet/</a>."
+"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests to "
+"detect regressions and check for portability at <a href=\"https://old.gnunet.";
+"org/buildbot/gnunet/\">https://old.gnunet.org/buildbot/gnunet/</a>."
msgstr ""
-"リグレッションの検出と移植性の確認のため、<a href=\"https://old.gnunet.org/buildbot/gnunet/\"";
-">https://old.gnunet.org/buildbot/gnunet/</a> で <a href=\"https://buildbot.";
-"net/\">Buildbot</a> 自動テストを実施しています。"
+"リグレッションの検出と移植性の確認のため、<a href=\"https://old.gnunet.org/";
+"buildbot/gnunet/\">https://old.gnunet.org/buildbot/gnunet/</a> で <a href="
+"\"https://buildbot.net/\";>Buildbot</a> 自動テストを実施しています。"
#: template/developers.html.j2:59
msgid "Code Coverage Analysis"
@@ -767,14 +805,13 @@ msgstr "コード カバレッジ分析"
#: template/developers.html.j2:62
msgid ""
-"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> "
-"to analyze the code coverage of our tests, the results are available at "
-"<a "
-"href=\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
+"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> to "
+"analyze the code coverage of our tests, the results are available at <a href="
+"\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
msgstr ""
-"<a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> によりテストのコード "
-"カバレッジを分析しており、結果は <a href=\"https://old.gnunet.org/coverage/\";>https://old.";
-"gnunet.org/coverage/</a> から参照可能です。"
+"<a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> によりテス"
+"トのコード カバレッジを分析しており、結果は <a href=\"https://old.gnunet.org/";
+"coverage/\">https://old.gnunet.org/coverage/</a> から参照可能です。"
#: template/developers.html.j2:72
msgid "Performance Analysis"
@@ -782,175 +819,953 @@ msgstr "パフォーマンス分析"
#: template/developers.html.j2:75
msgid ""
-"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for "
-"performance regression analysis of the exchange backend at <a "
-"href=\"https://old.gnunet.org/gauger/\";>https://old.gnunet.org/gauger/</a>."
+"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for performance "
+"regression analysis of the exchange backend at <a href=\"https://old.gnunet.";
+"org/gauger/\">https://old.gnunet.org/gauger/</a>."
msgstr ""
+"交換バックエンドのパフォーマンス回帰分析には、<a href=\"https://old.gnunet.";
+"org/gauger/\">https://old.gnunet.org/gauger/</a>で <a href=\"https://old.";
+"gnunet.org/gauger\">Gauger</a> を使用しています。"
#: template/download.html.j2:7 template/gnurl.html.j2:209
msgid "Downloads"
-msgstr ""
+msgstr "ダウンロード"
#: template/download.html.j2:11
msgid ""
-"Here you can download releases of our software and find links to the "
-"various versions."
+"Here you can download releases of our software and find links to the various "
+"versions."
msgstr ""
+"こちらからソフトウェアのリリースをダウンロードできます。また、各種バージョン"
+"へのリンクを掲載しています。"
#: template/download.html.j2:17
msgid "0.11.x series"
-msgstr ""
+msgstr "0.11.x シリーズ"
#: template/download.html.j2:18
msgid "tarball"
-msgstr ""
+msgstr "tarball"
#: template/download.html.j2:20
msgid ""
"The tarball of the latest version can be obtained from GNU FTP and its "
"mirrors."
-msgstr ""
+msgstr "最新バージョンの tar は GNU FTP とそのミラーから取得できます。"
#: template/download.html.j2:30
msgid "git"
-msgstr ""
+msgstr "Git"
#: template/download.html.j2:32
-msgid "You can fetch the git tag of version 0.11.x from our development
server:"
-msgstr ""
+msgid ""
+"You can fetch the git tag of version 0.11.x from our development server:"
+msgstr "バージョン 0.11.x の Git タグは開発サーバーから取得できます。"
#: template/engage.html.j2:6
msgid "Engage!"
-msgstr ""
+msgstr "参加しませんか"
#: template/ev.html.j2:6
+#, fuzzy
msgid "Verein zur Förderung von GNUnet e.V."
-msgstr ""
+msgstr "Verein zur Förderung von GNUnet e.V."
#: template/ev.html.j2:11
msgid "About GNUnet e.V."
-msgstr ""
+msgstr "GNUnet e.V. について"
#: template/ev.html.j2:13
msgid ""
-"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the"
-" \"Verein zur Förderung von GNUnet e.V.\", an association under "
-"German law to support GNUnet development. The Amtsgericht München "
-"registered the association on the 7th of March under VR 205287."
+"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the "
+"\"Verein zur Förderung von GNUnet e.V.\", an association under German "
+"law to support GNUnet development. The Amtsgericht München registered "
+"the association on the 7th of March under VR 205287."
msgstr ""
+"2013 年 12 月 27 日、GNUnet ハッカーのグループが 30c3 に集まり、ドイツ法に基"
+"づく GNUnet 開発支援のための協会である「Verein zur Förderung von GNUnet "
+"e.V.」を結成しました。この協会は Amtsgericht München により 3 月 7 日に "
+"VR 205287 のもと登録されています。"
#: template/ev.html.j2:22
msgid ""
-"The association is officially dedicated to supporting research, "
-"development and education in the area of secure decentralized networking "
-"in general, and GNUnet specifically. This is the official website for the"
-" association."
+"The association is officially dedicated to supporting research, development "
+"and education in the area of secure decentralized networking in general, and "
+"GNUnet specifically. This is the official website for the association."
msgstr ""
+"協会は、安全な分散型ネットワーキング分野全般、特に GNUnet の研究、開発、教育"
+"の支援を公式な取り組みとしており、このウェブサイトは協会の公式ウェブサイトで"
+"す。"
#: template/ev.html.j2:31
msgid "Becoming a Member of GNUnet e.V."
-msgstr ""
+msgstr "GNUnet e.V. のメンバーになる"
#: template/ev.html.j2:33
msgid ""
-"GNUnet developers with git (write) access can become members to "
-"participate in the decision process and formally support GNUnet e.V. For "
-"this, all you have to do is update the <tt>members.txt</tt> file in the "
-"<a href=\"https://git.gnunet.org/gnunet-ev.git/\";>gnunet-ev</a> "
-"repository. There are no membership dues; however, members are required "
-"to support GNUnet e.V. and in particularly contribute to the technical "
-"development within their means. For further details, we refer to the <a "
-"href=\"https://git.gnunet.org/gnunet-ev.git/\";>Satzung</a> (currently "
-"only available in German, translations welcome)."
-msgstr ""
+"GNUnet developers with git (write) access can become members to participate "
+"in the decision process and formally support GNUnet e.V. For this, all you "
+"have to do is update the <tt>members.txt</tt> file in the <a href=\"https://";
+"git.gnunet.org/gnunet-ev.git/\">gnunet-ev</a> repository. There are no "
+"membership dues; however, members are required to support GNUnet e.V. and in "
+"particularly contribute to the technical development within their means. For "
+"further details, we refer to the <a href=\"https://git.gnunet.org/gnunet-ev.";
+"git/\">Satzung</a> (currently only available in German, translations "
+"welcome)."
+msgstr ""
+"Git（書き込み）アクセス権を持つ GNUnet 開発者は、メンバーとして意思決定プロセ"
+"スに参加し、GNUnet e.V. を正式にサポートすることができます。メンバーとなるに"
+"は、<a href=\"https://git.gnunet.org/gnunet-ev.git/\";>gnunet-ev</a> レポジト"
+"リにある <tt>members.txt</tt> ファイルを更新してください。会費はありません"
+"が、メンバーには GNUnet e.V. へのサポート、特に技術開発面での相応の貢献が求め"
+"られます。詳細については、<a href=\"https://git.gnunet.org/gnunet-ev.git/";
+"\">Satzung</a> を参照してください（現在ドイツ語のみですが、翻訳も歓迎しま"
+"す）。"
#: template/ev.html.j2:52
msgid "Governance"
-msgstr ""
+msgstr "ガバナンス"
#: template/ev.html.j2:54
msgid ""
-"You can find our \"Satzung\", and the list of members under <a "
-"href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex\">https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex</a>. The current board consists of: "
+"You can find our \"Satzung\", and the list of members under <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex\";>https://git.gnunet.";
+"org/gnunet-ev.git/tree/satzung.tex</a>. The current board consists of: "
"<dl><dt>Vorsitz</dt> <dd><a href=\"https://schanzen.eu\";>Martin "
-"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> "
-"<dd>t3sserakt</dd> <dt>Kassenwart</dt> <dd>Florian Dold</dd> "
-"<dt>Beisitzer</dt> <dd> <a "
-"href=\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 "
-"</dd> </dl>"
-msgstr ""
+"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> <dd>t3sserakt</dd> "
+"<dt>Kassenwart</dt> <dd>Florian Dold</dd> <dt>Beisitzer</dt> <dd> <a href="
+"\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 </dd> </dl>"
+msgstr ""
+"「Satzung」およびメンバーのリストは<a href=\"https://git.gnunet.org/gnunet-";
+"ev.git/tree/satzung.tex\">https://git.gnunet.org/gnunet-ev.git/tree/satzung.";
+"tex</a> から確認できます。現在の委員会メンバーは次の通りです。 "
+"<dl><dt>Vorsitz</dt><dd><a href=\"https://schanzen.eu\";>Martin Schanzenbach</"
+"a></dd><dt>stellvertretender Vorsitz</dt><dd>t3sserakt</dd><dt>Kassenwart</"
+"dt><dd>Florian Dold</dd><dt>Beisitzer</dt><dd><a href=\"https://grothoff.org/";
+"christian/\">Christian Grothoff</a>, ch3 </dd></dl>"
#: template/ev.html.j2:73
msgid "Official Meeting Notes"
-msgstr ""
+msgstr "公式議事録"
#: template/ev.html.j2:86
msgid "Support Us!"
-msgstr ""
+msgstr "支援"
#: template/ev.html.j2:88
msgid ""
"Everybody is welcome to support us via donations. For financial "
"contributions, Europeans are able to donate via SEPA. We hope to setup "
-"accounts in other major currency areas in the future. You can also donate"
-" via Bitcoin, routing details are given below. Please note that we are "
-"unable to provide receipts for your donations. If you are planning to "
-"donate a significant amount of money, please contact us first as it might"
-" be better to come to a custom arrangement. <dl><dt>BitCoin</dt> "
+"accounts in other major currency areas in the future. You can also donate "
+"via Bitcoin, routing details are given below. Please note that we are unable "
+"to provide receipts for your donations. If you are planning to donate a "
+"significant amount of money, please contact us first as it might be better "
+"to come to a custom arrangement. <dl><dt>BitCoin</dt> "
"<dd>1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh</dd> <dt>SEPA/IBAN</dt> "
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
+"どなたでも寄付を通じてご支援いただけます。金銭的な貢献に関し、欧州にお住まい"
+"の場合 SEPA 経由で寄付いただくことができます。将来的には他の主要通貨でも受け"
+"付けられるよう取り組んでいきたいと考えています。また、Bitcoin による寄付も可"
+"能で、ルーティング詳細は下に記載しています。ただし、寄付金について領収書は発"
+"行することができませんのでご了承ください。大口の寄付につきましては、関税処理"
+"が必要な場合があるため、事前にご連絡をいただけますようお願いします。"
+"<dl><dt>BitCoin</dt><dd>1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh</dd><dt>SEPA/"
+"IBAN</dt><dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd></dl>"
-#: template/faq.html.j2:12
-msgid "Is GNUnet ready for use on production systems?"
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
msgstr ""
-#: template/faq.html.j2:14
-msgid ""
-"A: GNUnet is still undergoing major development. It is largely not yet "
-"ready for usage beyond developers. Your mileage will vary depending on "
-"the functionality you use, but you will always likely run into issues "
-"with our current low-level transport system. We are currently in the "
-"process of rewriting it (Project "Transport Next Generation "
-"[TNG]")"
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
msgstr ""
-#: template/faq.html.j2:24
-msgid "Is GNUnet build using distributed ledger technologies?"
+#: template/faq.html.j2:15 template/faq.html.j2:594
+msgid "Error messages"
+msgstr ""
+
+#: template/faq.html.j2:16 template/faq.html.j2:696
+#, fuzzy
+#| msgid "Filesharing (Alpha)"
+msgid "File-sharing"
+msgstr "ファイル共有（アルファ）"
+
+#: template/faq.html.j2:17 template/faq.html.j2:872
+msgid "Contributing"
msgstr ""
#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr ""
+
+#: template/faq.html.j2:28
msgid ""
-"A: No. GNUnet is a new network protocol stack for building secure, "
-"distributed, and privacy-preserving applications. While a ledger could be"
-" built using GNUnet, we currently have no plans in doing so."
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
+"the #gnunet IRC on irc.freenode.net."
msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
+msgstr ""
+
+#: template/faq.html.j2:38
msgid ""
-"I receive many "WARNING Calculated flow delay for X at Y for "
-"Z". Should I worry?"
+"A: The general answer is, when it is ready. A better answer may be: earlier "
+"if you contribute (test, debug, code, document). Every release will be "
+"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://";
+"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
+"the RSS feed of this site to automatically receive a notification."
+msgstr ""
+
+#: template/faq.html.j2:49
+msgid "Is the code free?"
msgstr ""
-#: template/faq.html.j2:37
+#: template/faq.html.j2:51
msgid ""
-"A: Right now, this is expected and a known cause for high latency in "
-"GNUnet. We have started a major rewrite to address this and other "
-"problems, but until the Transport Next Generation (TNG) is ready, these "
-"warnings are expected."
+"A: GNUnet is free software, available under the <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
msgstr ""
-#: template/faq.html.j2:46
-msgid "Is there a graphical user interface?"
+#: template/faq.html.j2:58
+msgid "Are there any known bugs?"
msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:60
+msgid ""
+"A: We track the list of currently known bugs in the <a href=\"https://bugs.";
+"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
+"directly to developers or the developer mailing list. This is discouraged "
+"since developers often do not have the time to feed these bugs back into the "
+"Mantis database. Please report bugs directly to the bug tracking system. If "
+"you believe a bug is sensitive, you can set its view status to private (this "
+"should be the exception)."
+msgstr ""
+
+#: template/faq.html.j2:73 template/faq.html.j2:193
+msgid "Is there a graphical user interface?"
+msgstr "グラフィカル ユーザー インターフェースはありますか？"
+
+#: template/faq.html.j2:75
msgid ""
"A: gnunet-gtk is a separate download. The package contains various GTK+ "
"based graphical interfaces, including a graphical tool for configuration."
msgstr ""
+"回答：gnunet-gtk を別途ダウンロードいただけます。このパッケージには、設定用の"
+"グラフィカル ツールなど、各種 GTK+ ベースのグラフィカル インターフェースが含"
+"まれます。"
+
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr ""
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called ""
+"proof-of-work" which is used to convince the network that your peer is "
+"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
+"on the network size estimator). The calculation is expected to take a few "
+"days, depending on how fast your CPU is. If the CPU load is creating a "
+"problem for you, you can set the value "WORKDELAY" in the ""
+"nse" section of your configuration file to a higher value. The default "
+"is "5 ms"."
+msgstr ""
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr ""
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
+"connections and, with the Tor Browser Bundle, for the Web in particular. "
+"GNUnet does not really have one focus; our theme is secure decentralized "
+"networking, but that is too broad to be called a focus."
+msgstr ""
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr ""
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost no "
+"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
+"using onion (or garlic) routing as the basis for various (anonymized) "
+"applications. I2P is largely used via a Web frontend."
+msgstr ""
+
+#: template/faq.html.j2:124
+msgid "Is GNUnet ready for use on production systems?"
+msgstr "GNUnet は本番システムで利用できますか？"
+
+#: template/faq.html.j2:126
+msgid ""
+"A: GNUnet is still undergoing major development. It is largely not yet ready "
+"for usage beyond developers. Your mileage will vary depending on the "
+"functionality you use, but you will always likely run into issues with our "
+"current low-level transport system. We are currently in the process of "
+"rewriting it (Project "Transport Next Generation [TNG]")"
+msgstr ""
+"回答：GNUnet はまだ開発途上であるため、大部分が開発者以外の方による使用には適"
+"していません。利用価値は、使いたい機能にもよりますが、現時点では転送システム"
+"が洗練されておらず、常に何らかの問題に直面すると考えられます。この部分につい"
+"ては現在書き換えを進めています。（プロジェクト"Transport Next "
+"Generation [TNG]"）"
+
+#: template/faq.html.j2:136
+msgid "Is GNUnet build using distributed ledger technologies?"
+msgstr "GNUnet は分散型台帳技術を使用して構築されていますか？"
+
+#: template/faq.html.j2:138
+msgid ""
+"A: No. GNUnet is a new network protocol stack for building secure, "
+"distributed, and privacy-preserving applications. While a ledger could be "
+"built using GNUnet, we currently have no plans in doing so."
+msgstr ""
+"回答：いいえ。GNUnet は、安全で分散型のプライバシー保護を実現したアプリケー"
+"ションを構築することができる、新しいネットワーク プロトコル スタックです。"
+"GNUnet で台帳を構築することもできますが、現時点でその予定はありません。"
+
+#: template/faq.html.j2:151
+#, fuzzy
+#| msgid "What is GNUnet?"
+msgid "What can I do with GNUnet?"
+msgstr "GNUnet とは"
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
+"do more than just one thing. Naturally, the implementation and documentation "
+"of some of the features that exist are more advanced than others."
+msgstr ""
+
+#: template/faq.html.j2:160
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
+"decentralized and censorship-resistant replacement for DNS and a mechanism "
+"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
+msgstr ""
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We "
+"recommend that you use Tor for anonymous surfing."
+msgstr ""
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr ""
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+
+#: template/faq.html.j2:195
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the "
+"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
+"that integrates most of the other GUIs in one window. One exception is "
+"gnunet-setup, which must still be run separately at this time (as setup "
+"requires the peer to be stopped)."
+msgstr ""
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr ""
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
+"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
+"FreeBSD and macOS. We have reports of working versions on many other GNU/"
+"Linux distributions; in the past we had reports of working versions on "
+"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
+"so if you cannot get GNUnet to work on those systems please let us know."
+msgstr ""
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr ""
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a default "
+"configuration of top-level domains. The governance of this default "
+"configuration is not yet established. In any case, the user will be able to "
+"modify this configuration at will. We expect normal users to have no need to "
+"edit their own GNS zone(s) unless they host services themselves."
+msgstr ""
+
+#: template/faq.html.j2:241
+msgid "Where is the per-user GNS database kept?"
+msgstr ""
+
+#: template/faq.html.j2:243
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet peer. "
+"Now, a user may run multiple GNUnet peers, in which case the database could "
+"be kept at each peer (however, we don't have code for convenient "
+"replication). Similarly, multiple GNUnet peers can share one instance of the "
+"database --- the "gnunet-service-namestore" can be accessed from "
+"remote (via TCP). The actual data can be stored in a Postgres database, for "
+"which various replication options are again applicable. Ultimately, there "
+"are many options for how users can store (and secure) their GNS database."
+msgstr ""
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases "
+"will only grow to a few tens of thousands of entries, small enough to fit "
+"even on mobile devices."
+msgstr ""
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr ""
+
+#: template/faq.html.j2:272
+msgid ""
+"A: We believe so, as there is no entity that any government could force to "
+"change the mapping for a name except for each individual user (and then the "
+"changes would only apply to the names that this user is the authority for). "
+"So if everyone used GNS, the only practical attack of a government would be "
+"to force the operator of a server to change the GNS records for his server "
+"to point elsewhere. However, if the owner of the private key for a zone is "
+"unavailable for enforcement, the respective zone cannot be changed and any "
+"other zone delegating to this zone will achieve proper resolution."
+msgstr ""
+
+#: template/faq.html.j2:286
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr ""
+
+#: template/faq.html.j2:288
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
+"there are still registrars that determine who owns a name. <br><br> With "
+"GNS, we decentralize the database and also decentralize the responsibility "
+"for naming: each user runs his own personal root zone and is thus in "
+"complete control of the names he uses. GNS also has many additional features "
+"(to keep names short and enable migration) which don't even make sense in "
+"the context of CoDoNS."
+msgstr ""
+
+#: template/faq.html.j2:304
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr ""
+
+#: template/faq.html.j2:306
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared via "
+"delegation, and thus mappings will only change if the user responsible for "
+"the name (the authority) manually changes the record."
+msgstr ""
+
+#: template/faq.html.j2:320
+msgid "What is the difference between GNS and ODDNS?"
+msgstr ""
+
+#: template/faq.html.j2:322
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+
+#: template/faq.html.j2:333
+msgid "What is the difference between GNS and Namecoin?"
+msgstr ""
+
+#: template/faq.html.j2:340
+msgid "What is the difference between GNS and Handshake?"
+msgstr ""
+
+#: template/faq.html.j2:346
+msgid "What is the difference between GNS and ENS?"
+msgstr ""
+
+#: template/faq.html.j2:352
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr ""
+
+#: template/faq.html.j2:354
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks on "
+"DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from "
+"the DNS hierarchy."
+msgstr ""
+
+#: template/faq.html.j2:367
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the style "
+"of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:369
+msgid ""
+"A: For security, it is well known that an initial trust path between the two "
+"parties must exist. However, for applications where this is not required, "
+"weaker mechanisms can be used. For example, we have implemented a first-come-"
+"first-served (FCFS) authority which allows arbitrary users to register "
+"arbitrary names. The key of this authority is included with every GNUnet "
+"installation. Thus, any name registered with FCFS is in fact global and "
+"requires no further introduction. However, the security of these names "
+"depends entirely on the trustworthiness of the FCFS authority. The authority "
+"can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:384
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name in "
+"GNS?"
+msgstr ""
+
+#: template/faq.html.j2:386
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "legitimate" "
+"domain owner. Any user can claim any name (as his preferred name or ""
+"pseudonym") in his NICK record. Similarly, all other users can choose "
+"to ignore this preference and use a name of their choice (or even assign no "
+"name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:397
+msgid ""
+"Did you consider the privacy implications of making your personal GNS zone "
+"visible?"
+msgstr ""
+
+#: template/faq.html.j2:399
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not set. "
+"Thus, users have full control over what information about their zones is "
+"made public."
+msgstr ""
+
+#: template/faq.html.j2:409
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:411
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary because "
+"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
+"of virtual hosting. However, LEHOs are also useful to help with X.509 "
+"certificate validation (as they specify for which legacy hostname the "
+"certificate should be valid). Also, even with IPv6 fully deployed and ""
+"infinite" IP addresses being available, we're not sure that virtual "
+"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
+"become commonplace, GNS should work with today's networks."
+msgstr ""
+
+#: template/faq.html.j2:425
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:427
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. As "
+"trust relationships evolve, mappings would change their meaning as they "
+"cross each others thresholds. We decided that the resulting unpredictability "
+"of the resolution process was not acceptable. Furthermore, trust and "
+"consensus might be easy to manipulate by adversaries."
+msgstr ""
+
+#: template/faq.html.j2:438
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:440
+msgid ""
+"A: The owner of a private key can create a revocation message. This one can "
+"then be flooded throughout the overlay network, creating a copy at all "
+"peers. Before using a public key, peers check if that key has been revoked. "
+"All names that involve delegation via a revoked zone will then fail to "
+"resolve. Peers always automatically check for the existence of a revocation "
+"message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:452
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:454
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:468
+msgid ""
+"How can a GNS zone maintain several name servers, e.g. for load balancing?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share "
+"the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:483
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names are "
+"not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on your "
+"application, HTTPS may not be worth the cost. However, for users that are "
+"experiencing censorship (or are concerned about it), giving up globally "
+"unique names may very well be worth the cost. After all, what is a ""
+"globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:499
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:501
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by IANA/ICANN. "
+"This centralization creates vulnerabilities. For example, the US government "
+"was able to reassign the management of the country-TLDs of Afganistan and "
+"Iraq during the wars at the beginning of the 21st century."
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:514
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
+"so blocking a particular IP address causes much more collateral damage than "
+"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
+"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
+"censorship resistant naming system. Accessing Tor's ".onion" "
+"namespace currently requires users to use unmemorable cryptographic "
+"identifiers. With nicer names, Tor and tor2web-like services would be even "
+"easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:533
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:535
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can use "
+"GNS to perform name resolution as well as any normal user. Naturally, while "
+"we typically expect normal users to install custom software for name "
+"resolution, this is unlikely to work for search engines today. However, the "
+"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
+"they can still index GNS resources. However, as using DNS2GNS gateways "
+"breaks the cryptographic chain of trust, legacy search engines will "
+"obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:549
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:551
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was designed "
+"to interoperate with DNS as much as possible, and to also work as much as "
+"possible with the existing Web infrastructure. UIA is not at all concerned "
+"about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:564
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:566
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you know "
+"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
+"and can thus decide how much you trust the result. Naturally, the trusted-"
+"computing base (TCB) can become arbitrarily large this way --- however, "
+"given the name length restriction, for an individual name it is always less "
+"than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:578
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part of "
+"the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:580
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects the "
+""_Service._Proto" syntax, converts "Service" to the "
+"corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when the "
+"result is presented, GNS looks for the GNS-specific "BOX" record "
+"type. A BOX record is a record that contains another record (such as SRV or "
+"TLSA records) and adds a service and protocol number (and the original boxed "
+"record type) to it."
+msgstr ""
+
+#: template/faq.html.j2:596
+msgid ""
+"I receive many "WARNING Calculated flow delay for X at Y for Z". "
+"Should I worry?"
+msgstr ""
+"「WARNING Calculated flow delay for X at Y for Z」という警告が多くでますが、"
+"懸念すべきですか？"
+
+#: template/faq.html.j2:598
+msgid ""
+"A: Right now, this is expected and a known cause for high latency in GNUnet. "
+"We have started a major rewrite to address this and other problems, but "
+"until the Transport Next Generation (TNG) is ready, these warnings are "
+"expected."
+msgstr ""
+"回答：現時点でこれは想定内であり、GNUnet での高レイテンシの既知の原因です。こ"
+"の件および他の問題に対処するため、主要な書き換えを開始していますが、"
+"Transport Next Generation（TNG）が準備できるまでは発生が続くことが見込まれま"
+"す。"
+
+#: template/faq.html.j2:607
+msgid "Error opening `/dev/net/tun': No such file or directory?"
+msgstr ""
+
+#: template/faq.html.j2:609
+msgid ""
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:621
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
+"dns)?"
+msgstr ""
+
+#: template/faq.html.j2:623
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check if "
+"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:635
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:637
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if "
+"your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:645
+msgid ""
+"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:647
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if you "
+"compiled GNUnet the normal way and/or used a binary package, that is highly "
+"unlikely. The more common cause is that you installed GNUnet to a directory "
+"that your linker does not search. There are several ways to fix this that "
+"are described below. If you are 'root' and you installed to a system folder "
+"(such as /usr/local), you want to add the libraries to the system-wide "
+"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
+"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
+"similar path, you obviously have to change \"/usr/local\" accordingly. If "
+"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
+"$USER/\", then you can explicitly tell your linker to search a particular "
+"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
+"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
+"you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:673
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the \"$\") "
+"to your .bashrc or .profile file. You will have to logout and login again to "
+"have this new profile be applied to all shells (including your desktop "
+"environment)."
+msgstr ""
+
+#: template/faq.html.j2:680
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:682
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
+"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
+"always refer to harmless events that require no action. For example, GNUnet "
+"may use an INFO message to indicate that it is currently performing an "
+"expensive operation that will take some time. GNUnet will also use INFO "
+"messages to display information about important configuration values."
+msgstr ""
+
+#: template/faq.html.j2:698
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:700
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
+"P2P networks, GNUnet was designed with security in mind as the highest "
+"priority. We intend on producing a network with comprehensive security "
+"features. Many other P2P networks are open to a wide variety of attacks, and "
+"users have little privacy. GNUnet is also Free Software and thus the source "
+"code is available, so you do not have to worry about being spied upon by the "
+"software. The following table summarises the main differences between GNUnet "
+"and other systems. The information is accurate to the best of our knowledge. "
+"The comparison is difficult since there are sometimes differences between "
+"various implementations of (almost) the same protocol. In general, we pick a "
+"free implementation as the reference implementation since it is possible to "
+"inspect the free code. Also, all of these systems are changing over time and "
+"thus the data below may not be up-to-date. If you find any flaws, please let "
+"us know. Finally, the table is not saying terribly much (it is hard to "
+"compare these systems this briefly), so if you want the real differences, "
+"read the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:814
+msgid ""
+"Another important point of reference are the various anonymous peer-to-peer "
+"networks. Here, there are differences in terms of application domain and how "
+"specifically anonymity is achieved. Anonymous routing is a hard research "
+"topic, so for a superficial comparisson like this one we focus on the "
+"latency. Another important factor is the programming language. Type-safe "
+"languages may offer certain security benefits; however, this may come at the "
+"cost of significant increases in resource consumption which in turn may "
+"reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:827
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:829
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of the "
+"same techniques used to generate reasonable passwords to defend against such "
+"an attack. In any event, we are not trying to hide content; thus, unless the "
+"user is trying to insert information into the network that can only be "
+"shared with a small group of people, there is no real reason to try to "
+"obfuscate the content by choosing a difficult keyword anyway."
+msgstr ""
+
+#: template/faq.html.j2:843
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:845
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all "
+"users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell which "
+"of the peers in the group originated the message. In other words, it should "
+"be difficult to impossible for an adversary to distinguish between the "
+"originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:857
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:859
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
+"its public key) and has a number of addresses it is reachable by (may have "
+"no addresses, for instance when it's behind a NAT). You specify bandwidth "
+"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
+"(how large your on-disk block storage is) . Your node will then proceed to "
+"connect to other nodes, becoming part of the network."
+msgstr ""
+
+#: template/faq.html.j2:874
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:876
+msgid ""
+"A: First, you need to register an account with our weblate system. Please "
+"send an e-mail with the desired target language to translators@gnunet.org or "
+"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
+"sufficient permissions will then grant you access. Naturally, any abuse will "
+"result in the loss of permissions."
+msgstr ""
+
+#: template/faq.html.j2:888
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:890
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly implement. "
+"The best way to actually get a new feature implemented is to do it yourself "
+"--- and to then send us a patch."
+msgstr ""
#: template/glossary.html.j2:12
msgid "Ego"
@@ -958,13 +1773,13 @@ msgstr ""
#: template/glossary.html.j2:14
msgid ""
-"We use the term \"Ego\" to refer to the fact that users in GNUnet can "
-"have multiple unlinkable identities, in the sense of alter egos. The "
-"ability to have more than one identity is crucial, as we may want to keep"
-" our egos for business separate from those we use for political "
-"activities or romance.<br> Egos in GNUnet are technically equivalent to "
-"identities (and the code does not distinguish between them). We simply "
-"sometimes use the term \"ego\" to stress that you can have more than one."
+"We use the term \"Ego\" to refer to the fact that users in GNUnet can have "
+"multiple unlinkable identities, in the sense of alter egos. The ability to "
+"have more than one identity is crucial, as we may want to keep our egos for "
+"business separate from those we use for political activities or romance.<br> "
+"Egos in GNUnet are technically equivalent to identities (and the code does "
+"not distinguish between them). We simply sometimes use the term \"ego\" to "
+"stress that you can have more than one."
msgstr ""
#: template/glossary.html.j2:27
@@ -973,19 +1788,18 @@ msgstr ""
#: template/glossary.html.j2:29
msgid ""
-"In GNUnet users are identified via a public key, and that public key is "
-"then often referred to as the \"Identity\" of the user. However, the "
-"concept is not as draconian as it often is in real life where many are "
-"forced to have one name, one passport and one unique identification "
-"number. <br> As long as identities in GNUnet are simply public keys, "
-"users are free to create any number of identities, and we call those egos"
-" to emphasize the difference. Even though users can create such egos "
-"freely, it is possible to have an ego certified by some certification "
-"authority, resulting in something that more closely resembles the "
-"traditional concept of an identity.<br> For example, a university may "
-"certify the identities of its students such that they can prove that they"
-" are studying. Students may keep their (certified) student identity "
-"separate from other egos that they use for other activities in life."
+"In GNUnet users are identified via a public key, and that public key is then "
+"often referred to as the \"Identity\" of the user. However, the concept is "
+"not as draconian as it often is in real life where many are forced to have "
+"one name, one passport and one unique identification number. <br> As long as "
+"identities in GNUnet are simply public keys, users are free to create any "
+"number of identities, and we call those egos to emphasize the difference. "
+"Even though users can create such egos freely, it is possible to have an ego "
+"certified by some certification authority, resulting in something that more "
+"closely resembles the traditional concept of an identity.<br> For example, a "
+"university may certify the identities of its students such that they can "
+"prove that they are studying. Students may keep their (certified) student "
+"identity separate from other egos that they use for other activities in life."
msgstr ""
#: template/glossary.html.j2:50
@@ -997,10 +1811,10 @@ msgid ""
"A pseudonym is an ego that is specifically intended to not be linked to "
"one's real name. GNUnet users can create many egos, and thus also many "
"pseudonyms. <br> Repeated uses of the same pseudonym are linkable by "
-"definition, as they involve the same public key. Anonymity requires the "
-"use of either the special \"anonymous\" pseudonym (for GNUnet, this is "
-"the neutral element on the elliptic curve) or a throw-away pseudonym that"
-" is only used once."
+"definition, as they involve the same public key. Anonymity requires the use "
+"of either the special \"anonymous\" pseudonym (for GNUnet, this is the "
+"neutral element on the elliptic curve) or a throw-away pseudonym that is "
+"only used once."
msgstr ""
#: template/glossary.html.j2:71
@@ -1009,15 +1823,15 @@ msgstr ""
#: template/glossary.html.j2:73
msgid ""
-"The GNU Name System allows every ego (or identity) to securely and "
-"privately associate any number of label-value pairs with an ego. The "
-"values are called record sets following the terminology of the Domain "
-"Name System (DNS). The mapping of labels to record sets for a given ego "
-"is called a namespace. <br> If records are made public and thus "
-"published, it is possible for other users to lookup the record given the "
-"ego's public key and the label. Here, not only the label can thus act as "
-"a passphrase but also the public key -- which despite its name may not be"
-" public knowledge and is never disclosed by the GNS protocol itself."
+"The GNU Name System allows every ego (or identity) to securely and privately "
+"associate any number of label-value pairs with an ego. The values are called "
+"record sets following the terminology of the Domain Name System (DNS). The "
+"mapping of labels to record sets for a given ego is called a namespace. <br> "
+"If records are made public and thus published, it is possible for other "
+"users to lookup the record given the ego's public key and the label. Here, "
+"not only the label can thus act as a passphrase but also the public key -- "
+"which despite its name may not be public knowledge and is never disclosed by "
+"the GNS protocol itself."
msgstr ""
#: template/glossary.html.j2:89
@@ -1026,17 +1840,17 @@ msgstr ""
#: template/glossary.html.j2:91
msgid ""
-"A \"peer\" is an instance of GNUnet with its own per-instance public key "
-"and network addresses. Technically, it is possible to run multiple peers "
-"on the same host, but this only makes sense for testing. <br> By design "
-"GNUnet supports multiple users to share the same peer, just as UNIX is a "
-"multi-user system. A \"peer\" typically consists of a set of foundational"
-" GNUnet services running as the \"gnunet\" user and allowing all users in"
-" the \"gnunet\" group to utilize the API. On multi-user systems, "
-"additional \"personalized\" services may be required per user. <br> While"
-" peers are also identified by public keys, these public keys are "
-"completely unrelated to egos or identities. Namespaces cannot be "
-"associated with a peer, only with egos."
+"A \"peer\" is an instance of GNUnet with its own per-instance public key and "
+"network addresses. Technically, it is possible to run multiple peers on the "
+"same host, but this only makes sense for testing. <br> By design GNUnet "
+"supports multiple users to share the same peer, just as UNIX is a multi-user "
+"system. A \"peer\" typically consists of a set of foundational GNUnet "
+"services running as the \"gnunet\" user and allowing all users in the "
+"\"gnunet\" group to utilize the API. On multi-user systems, additional "
+"\"personalized\" services may be required per user. <br> While peers are "
+"also identified by public keys, these public keys are completely unrelated "
+"to egos or identities. Namespaces cannot be associated with a peer, only "
+"with egos."
msgstr ""
#: template/gns.html.j2:13 template/gnurl.html.j2:60
@@ -1046,28 +1860,24 @@ msgstr ""
#: template/gns.html.j2:15
msgid ""
"The Domain Name System today enables traffic amplification attacks, "
-"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive "
-"cyber war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as "
-"DoT, DoH, DNSSEC, DPRIVE and the like will not fix this. This is why we "
-"built the GNU Name System (GNS), a secure, decentralized name system "
-"built on top of GNUnet."
+"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive cyber "
+"war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as DoT, DoH, "
+"DNSSEC, DPRIVE and the like will not fix this. This is why we built the GNU "
+"Name System (GNS), a secure, decentralized name system built on top of "
+"GNUnet."
msgstr ""
#: template/gns.html.j2:28
msgid "Overview"
msgstr ""
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
-
#: template/gns.html.j2:39
msgid ""
"The GNU Name System (GNS) is secure and decentralized naming system. It "
-"allows its users to register names as top-level domains (TLDs) and "
-"resolve other namespaces within their TLDs. <br/> GNS is designed to "
-"provide: <ul> <li>Censorship resistance</li> <li>Query privacy</li> "
-"<li>Secure name resolution</li> <li>Compatibility with DNS</li>"
+"allows its users to register names as top-level domains (TLDs) and resolve "
+"other namespaces within their TLDs. <br/> GNS is designed to provide: <ul> "
+"<li>Censorship resistance</li> <li>Query privacy</li> <li>Secure name "
+"resolution</li> <li>Compatibility with DNS</li>"
msgstr ""
#: template/gns.html.j2:52
@@ -1076,23 +1886,23 @@ msgstr ""
#: template/gnurl.html.j2:21
msgid ""
-"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support "
-"only HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend "
-"(GnuTLS) to ensure a small footprint and uniform experience for "
-"developers regardless of how libcurl was compiled."
+"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support only "
+"HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend (GnuTLS) to "
+"ensure a small footprint and uniform experience for developers regardless of "
+"how libcurl was compiled."
msgstr ""
#: template/gnurl.html.j2:30
msgid ""
-"Our main usecase is for GNUnet and Taler, but it might be usable for "
-"others, hence we're releasing the code to the general public."
+"Our main usecase is for GNUnet and Taler, but it might be usable for others, "
+"hence we're releasing the code to the general public."
msgstr ""
#: template/gnurl.html.j2:37
msgid ""
"libgnurl is released under the same license as libcurl. Please read the "
-"README for instructions, as you must supply the correct options to "
-"configure to get a proper build of libgnurl."
+"README for instructions, as you must supply the correct options to configure "
+"to get a proper build of libgnurl."
msgstr ""
#: template/gnurl.html.j2:48
@@ -1101,58 +1911,55 @@ msgstr ""
#: template/gnurl.html.j2:50
msgid ""
-"Large parts of the following 6 paragraphs are old and need to be "
-"rewritten."
+"Large parts of the following 6 paragraphs are old and need to be rewritten."
msgstr ""
#: template/gnurl.html.j2:62
msgid ""
-"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, "
-"but other variants are used by some distributions. Supporting other "
-"crypto backends would again expose us to a wider array of security "
-"issues, may create licensing issues and most importantly introduce new "
-"bugs as some crypto backends are known to introduce subtle runtime "
-"issues. While it is possible to have two versions of libcurl installed on"
-" the same system, this is error-prone, especially as if we are linked "
-"against the wrong version, the bugs that arise might be rather subtle."
+"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, but "
+"other variants are used by some distributions. Supporting other crypto "
+"backends would again expose us to a wider array of security issues, may "
+"create licensing issues and most importantly introduce new bugs as some "
+"crypto backends are known to introduce subtle runtime issues. While it is "
+"possible to have two versions of libcurl installed on the same system, this "
+"is error-prone, especially as if we are linked against the wrong version, "
+"the bugs that arise might be rather subtle."
msgstr ""
#: template/gnurl.html.j2:75
msgid ""
-"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, "
-"it would anyway be necessary to recompile cURL for GNUnet. But what "
-"happens if one links cURL against this version of GnuTLS? Well, first one"
-" would install GnuTLS by hand in the system. Then, we build cURL. cURL "
-"will build against it just fine, but the linker will eventually complain "
-"bitterly. The reason is that cURL also links against a bunch of other "
-"system libraries (gssapi, ldap, ssh2, rtmp, krb5, sasl2, see discussion "
-"on obscure protocols above), which --- as they are part of the "
-"distribution --- were linked against an older version of GnuTLS. As a "
-"result, the same binary would be linked against two different versions of"
-" GnuTLS. That is typically a recipe for disaster. Thus, in order to avoid"
-" updating a dozen system libraries (and having two versions of those "
-"installed), it is necessary to disable all of those cURL features that "
-"GNUnet does not use, and there are many of those. For GNUnet, the more "
-"obscure protocols supported by cURL are close to dead code --- mostly "
-"harmless, but not useful. However, as some application may use one of "
-"those features, distributions are typically forced to enable all of those"
-" features, and thus including security issues that might arise from that "
-"code."
+"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, it "
+"would anyway be necessary to recompile cURL for GNUnet. But what happens if "
+"one links cURL against this version of GnuTLS? Well, first one would install "
+"GnuTLS by hand in the system. Then, we build cURL. cURL will build against "
+"it just fine, but the linker will eventually complain bitterly. The reason "
+"is that cURL also links against a bunch of other system libraries (gssapi, "
+"ldap, ssh2, rtmp, krb5, sasl2, see discussion on obscure protocols above), "
+"which --- as they are part of the distribution --- were linked against an "
+"older version of GnuTLS. As a result, the same binary would be linked "
+"against two different versions of GnuTLS. That is typically a recipe for "
+"disaster. Thus, in order to avoid updating a dozen system libraries (and "
+"having two versions of those installed), it is necessary to disable all of "
+"those cURL features that GNUnet does not use, and there are many of those. "
+"For GNUnet, the more obscure protocols supported by cURL are close to dead "
+"code --- mostly harmless, but not useful. However, as some application may "
+"use one of those features, distributions are typically forced to enable all "
+"of those features, and thus including security issues that might arise from "
+"that code."
msgstr ""
#: template/gnurl.html.j2:99
msgid ""
-"So to use a modern version of GnuTLS, a sane approach is to disable all "
-"of the \"optional\" features of cURL that drag in system libraries that "
-"link against the older GnuTLS. That works, except that one should then "
-"NEVER install that version of libcurl in say /usr or /usr/local, as that "
-"may break other parts of the system that might depend on these features "
-"that we just disabled. Libtool versioning doesn't help here, as it is not"
-" intended to deal with libraries that have optional features. Naturally, "
-"installing cURL somewhere else is also problematic, as we now need to be "
-"really careful that the linker will link GNUnet against the right "
-"version. Note that none of this can really be trivially fixed by the cURL"
-" developers."
+"So to use a modern version of GnuTLS, a sane approach is to disable all of "
+"the \"optional\" features of cURL that drag in system libraries that link "
+"against the older GnuTLS. That works, except that one should then NEVER "
+"install that version of libcurl in say /usr or /usr/local, as that may break "
+"other parts of the system that might depend on these features that we just "
+"disabled. Libtool versioning doesn't help here, as it is not intended to "
+"deal with libraries that have optional features. Naturally, installing cURL "
+"somewhere else is also problematic, as we now need to be really careful that "
+"the linker will link GNUnet against the right version. Note that none of "
+"this can really be trivially fixed by the cURL developers."
msgstr ""
#: template/gnurl.html.j2:118
@@ -1163,19 +1970,19 @@ msgstr ""
#, python-format
msgid ""
"How does forking fix it? Easy. First, we can get rid of all of the "
-"compatibility issues --- if you use libgnurl, you state that you "
-"don't need anything but HTTP/HTTPS. Those applications that need "
-"more, should stick with the original cURL. Those that do not, can choose "
-"to move to something simpler. As the library gets a new name, we do not "
-"have to worry about tons of packages breaking as soon as one rebuilds it."
-" So renaming itself and saying that \"libgnurl = libcurl with only "
-"HTTP/HTTPS support and GnuTLS\" fixes 99%% of the problems that darkened "
-"my mood. Note that this pretty much CANNOT be done without a fork, as "
-"renaming is an essential part of the fix. Now, there might be creative "
-"solutions to achieve the same thing within the standard cURL build "
-"system, but this was deemed to be too much work when gnurl was originally"
-" started. The changes libgnurl makes to curl are miniscule and can easily"
-" be applied again and again whenever libcurl makes a new release."
+"compatibility issues --- if you use libgnurl, you state that you don't "
+"need anything but HTTP/HTTPS. Those applications that need more, should "
+"stick with the original cURL. Those that do not, can choose to move to "
+"something simpler. As the library gets a new name, we do not have to worry "
+"about tons of packages breaking as soon as one rebuilds it. So renaming "
+"itself and saying that \"libgnurl = libcurl with only HTTP/HTTPS support and "
+"GnuTLS\" fixes 99%% of the problems that darkened my mood. Note that this "
+"pretty much CANNOT be done without a fork, as renaming is an essential part "
+"of the fix. Now, there might be creative solutions to achieve the same thing "
+"within the standard cURL build system, but this was deemed to be too much "
+"work when gnurl was originally started. The changes libgnurl makes to curl "
+"are miniscule and can easily be applied again and again whenever libcurl "
+"makes a new release."
msgstr ""
#: template/gnurl.html.j2:142
@@ -1184,14 +1991,13 @@ msgstr ""
#: template/gnurl.html.j2:144
msgid ""
-"Projects that use cURL only for HTTP/HTTPS and that would work with "
-"GnuTLS should be able to switch to libgnurl by changing \"-lcurl\" to "
-"\"-lgnurl\". That's it. No changes to the source code should be "
-"required, as libgnurl strives for bug-for-bug compatibility with the "
-"HTTP/HTTPS/GnuTLS subset of cURL. We might add new features relating to "
-"this core subset if they are proposed, but so far we have kept our "
-"changes minimal and no additions to the original curl source have been "
-"written."
+"Projects that use cURL only for HTTP/HTTPS and that would work with GnuTLS "
+"should be able to switch to libgnurl by changing \"-lcurl\" to \"-lgnurl\". "
+"That's it. No changes to the source code should be required, as libgnurl "
+"strives for bug-for-bug compatibility with the HTTP/HTTPS/GnuTLS subset of "
+"cURL. We might add new features relating to this core subset if they are "
+"proposed, but so far we have kept our changes minimal and no additions to "
+"the original curl source have been written."
msgstr ""
#: template/gnurl.html.j2:161
@@ -1200,15 +2006,15 @@ msgstr ""
#: template/gnurl.html.j2:163
msgid ""
-"libgnurl and gnurl are not intended to be used as a replacement for curl "
-"for users: <br> This does not mean there is no confidence in the work "
-"done with gnurl, it means that tools which expect curl or libcurl will "
-"not make use of a different named binary and library. If you know what "
-"you are doing, you should be able to use gnurl as part of your tooling in"
-" place of curl. We do not recommend to do so however, as the only usage "
-"it is tested for <em>so far</em> is as part of Taler's and "
-"GNunet's build-system. <br> Since no conflicts in filenames occur you"
-" are not expected to remove curl to make use of gnurl and viceversa."
+"libgnurl and gnurl are not intended to be used as a replacement for curl for "
+"users: <br> This does not mean there is no confidence in the work done with "
+"gnurl, it means that tools which expect curl or libcurl will not make use of "
+"a different named binary and library. If you know what you are doing, you "
+"should be able to use gnurl as part of your tooling in place of curl. We do "
+"not recommend to do so however, as the only usage it is tested for <em>so "
+"far</em> is as part of Taler's and GNunet's build-system. <br> Since "
+"no conflicts in filenames occur you are not expected to remove curl to make "
+"use of gnurl and viceversa."
msgstr ""
#: template/gnurl.html.j2:188
@@ -1221,16 +2027,15 @@ msgstr ""
#: template/gnurl.html.j2:211
msgid ""
-"Releases are published on <a "
-"href=\"https://ftpmirror.gnu.org/gnu/gnunet/\";>ftpmirror.gnu.org/gnu/gnunet</a>."
-" gnurl is available from within a variety of distributions and package "
-"managers. Some Package Managers which include gnurl are: <a "
-"href=\"https://www.gnu.org/software/guix/\";>GNU Guix</a> (available as "
-"\"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> through the "
-"collaborative ebuild collection <a href=\"https://git.gnunet.org";
-"/youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a "
-"href=\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a "
-"href=\"https://pkgsrc.org\";>pkgsrc</a>."
+"Releases are published on <a href=\"https://ftpmirror.gnu.org/gnu/gnunet/";
+"\">ftpmirror.gnu.org/gnu/gnunet</a>. gnurl is available from within a "
+"variety of distributions and package managers. Some Package Managers which "
+"include gnurl are: <a href=\"https://www.gnu.org/software/guix/\";>GNU Guix</"
+"a> (available as \"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> "
+"through the collaborative ebuild collection <a href=\"https://git.gnunet.org/";
+"youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a href="
+"\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a href=\"https://";
+"pkgsrc.org\">pkgsrc</a>."
msgstr ""
#: template/gnurl.html.j2:228
@@ -1239,17 +2044,17 @@ msgstr ""
#: template/gnurl.html.j2:230
msgid ""
-"We suggest to closely follow release announcements, as they might "
-"indicate changes in how gnurl is to be build. <br> If your package "
-"manager provides a binary build or build instructions to build gnurl from"
-" source automated and integrated with your environment, we strongly "
-"suggest to use this binary build. <br> There are two ways to build gnurl."
-" The first one builds from the most recent git tag, the second one uses "
-"the distributed tarball. Distributors generally are supposed to build "
-"from the tarball, but we describe both methods here. Both methods are "
-"written with a NetBSD 9 userland in mind, substitute tools as necessary. "
-"<br> You should <b>avoid</b> building gnurl from the tip of the default "
-"git branch, as only tags are considered to be stable and approved builds."
+"We suggest to closely follow release announcements, as they might indicate "
+"changes in how gnurl is to be build. <br> If your package manager provides a "
+"binary build or build instructions to build gnurl from source automated and "
+"integrated with your environment, we strongly suggest to use this binary "
+"build. <br> There are two ways to build gnurl. The first one builds from the "
+"most recent git tag, the second one uses the distributed tarball. "
+"Distributors generally are supposed to build from the tarball, but we "
+"describe both methods here. Both methods are written with a NetBSD 9 "
+"userland in mind, substitute tools as necessary. <br> You should <b>avoid</"
+"b> building gnurl from the tip of the default git branch, as only tags are "
+"considered to be stable and approved builds."
msgstr ""
#: template/gnurl.html.j2:251
@@ -1258,8 +2063,8 @@ msgstr ""
#: template/gnurl.html.j2:253
msgid ""
-"If you want to verify the signature, install an OpenPGP compatible tool "
-"such as security/gnupgp2 (and set it up). Assuming you use pkgin:"
+"If you want to verify the signature, install an OpenPGP compatible tool such "
+"as security/gnupgp2 (and set it up). Assuming you use pkgin:"
msgstr ""
#: template/gnurl.html.j2:267
@@ -1272,8 +2077,7 @@ msgstr ""
#: template/gnurl.html.j2:276
msgid ""
-"Fetch the release, the signature, the checksum file as well as its "
-"signature:"
+"Fetch the release, the signature, the checksum file as well as its signature:"
msgstr ""
#: template/gnurl.html.j2:295
@@ -1322,8 +2126,8 @@ msgstr ""
#: template/gnurl.html.j2:371
msgid ""
-"Follow the steps above, but instead of downloading the tarball, clone the"
-" git tag you want to build from."
+"Follow the steps above, but instead of downloading the tarball, clone the "
+"git tag you want to build from."
msgstr ""
#: template/gnurl.html.j2:382
@@ -1332,10 +2136,9 @@ msgstr ""
#: template/gnurl.html.j2:384
msgid ""
-"You can report bugs on our bug tracker: <a "
-"href=\"https://bugs.gnunet.org/\";>bugs.gnunet.org</a>. Alternatively you "
-"can use our bug mailinglist, but we prefer to track bugs on the "
-"bugtracker."
+"You can report bugs on our bug tracker: <a href=\"https://bugs.gnunet.org/";
+"\">bugs.gnunet.org</a>. Alternatively you can use our bug mailinglist, but "
+"we prefer to track bugs on the bugtracker."
msgstr ""
#: template/gnurl.html.j2:395
@@ -1346,10 +2149,9 @@ msgstr ""
msgid ""
"gnurl/libgnurl is looking for a new maintainer. Releases after version "
"7.69.1 and up to version 7.72.0 were signed with the OpenPGP Key "
-"<b>0xD6B570842F7E7F8D</b> (<a "
-"href=\"https://keys.openpgp.org/search?q=6115012DEA3026F62A98A556D6B570842F7E7F8D\";>keys.openpgp.org</a>),"
-" with the key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E"
-" 7F8D</b>."
+"<b>0xD6B570842F7E7F8D</b> (<a href=\"https://keys.openpgp.org/search?";
+"q=6115012DEA3026F62A98A556D6B570842F7E7F8D\">keys.openpgp.org</a>), with the "
+"key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E 7F8D</b>."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:7
@@ -1363,68 +2165,65 @@ msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:18
msgid ""
"In the context of Google Summer of Code 2018, my mentor (Martin "
-"Schanzenbach) and I have worked on creating and extending the REST API of"
-" GNUnet. Currently, we mirrored the functionality of following commands:"
+"Schanzenbach) and I have worked on creating and extending the REST API of "
+"GNUnet. Currently, we mirrored the functionality of following commands:"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:32
msgid ""
-"Additionally, we developed a website with the Javascript framework "
-"Angular 6 and the design framework iotaCSS to use the new REST API. The "
-"REST API of GNUnet is now documented with Sphinx."
+"Additionally, we developed a website with the Javascript framework Angular 6 "
+"and the design framework iotaCSS to use the new REST API. The REST API of "
+"GNUnet is now documented with Sphinx."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:41
msgid ""
-"... when you can use the command line tools? We need to keep in mind, "
-"that everyone has the right to stay secure and private but not everyone "
-"feels comfortable using a terminal. The further developed REST access to "
-"GNUnet APIs in addition to the new web application allows new users to "
-"interact with GNUnet over a well known tool: their browsers. This "
-"addition to the C API and the command line tools may attract new users "
-"and developers."
+"... when you can use the command line tools? We need to keep in mind, that "
+"everyone has the right to stay secure and private but not everyone feels "
+"comfortable using a terminal. The further developed REST access to GNUnet "
+"APIs in addition to the new web application allows new users to interact "
+"with GNUnet over a well known tool: their browsers. This addition to the C "
+"API and the command line tools may attract new users and developers."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:54
msgid ""
"<li> The REST API developed in GNUnet<br> The REST API is already merged "
-"into the gnunet.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet.git/\";>GNUnet Main Git</a>).<br /> "
-"To use the new features, clone the repository and follow the <a "
-"href=\"https://gnunet.org/en/install.html\";>Installation</a> on "
-"gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
-"</li> <li> The Web Application<br> The web application is available under"
-" the gnunet-webui.git repository (<a href=\"https://gnunet.org/git";
-"/gnunet-webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the"
-" newest version of 'node' and 'yarn'. Dependent on your system, you may "
-"need to download newer versions and install them manually and not over "
-"your packet manager. After the installation succeeded, you need to clone "
-"the repository. Then, you need to run \"yarn install\" and \"yarn start\""
-" for testing purposes. To deploy the website (keep in mind, that this "
-"website communicates with another localhost instance) use \"yarn build\" "
-"for building the web application and use the output in the 'dist' "
-"directory. </li> <li> The Documentation<br /> The documentation is "
-"available under the gnunet-rest-api.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet-rest-api.git/\";>GNUnet REST API "
-"Docmentation Git</a>).<br /> Clone the repository and \"make html\". Then"
-" open the 'index.html' under 'build/html/'. </li>"
+"into the gnunet.git repository (<a href=\"https://gnunet.org/git/gnunet.git/";
+"\">GNUnet Main Git</a>).<br /> To use the new features, clone the repository "
+"and follow the <a href=\"https://gnunet.org/en/install.html\";>Installation</"
+"a> on gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
+"</li> <li> The Web Application<br> The web application is available under "
+"the gnunet-webui.git repository (<a href=\"https://gnunet.org/git/gnunet-";
+"webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the newest "
+"version of 'node' and 'yarn'. Dependent on your system, you may need to "
+"download newer versions and install them manually and not over your packet "
+"manager. After the installation succeeded, you need to clone the repository. "
+"Then, you need to run \"yarn install\" and \"yarn start\" for testing "
+"purposes. To deploy the website (keep in mind, that this website "
+"communicates with another localhost instance) use \"yarn build\" for "
+"building the web application and use the output in the 'dist' directory. </"
+"li> <li> The Documentation<br /> The documentation is available under the "
+"gnunet-rest-api.git repository (<a href=\"https://gnunet.org/git/gnunet-rest-";
+"api.git/\">GNUnet REST API Docmentation Git</a>).<br /> Clone the repository "
+"and \"make html\". Then open the 'index.html' under 'build/html/'. </li>"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:91
msgid ""
-"Please, give it a try and contact me, if you find any bugs or "
-"unintentional features. ;)"
+"Please, give it a try and contact me, if you find any bugs or unintentional "
+"features. ;)"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:98
msgid ""
"Right now, the build process of the web application may be a little too "
-"complex for a casual user. We may be able to solve this by using "
-"docker.<br /> Additionally, the web application does not prevent wrong "
-"inputs but responds with error messages. Adding GNUnet Records is "
-"currently only usable for people, who know how a GNS Record looks like. "
-"This can be adapted to each record type.<br /> Last but not least, "
-"additional features, design changes, etc..."
+"complex for a casual user. We may be able to solve this by using docker.<br /"
+"> Additionally, the web application does not prevent wrong inputs but "
+"responds with error messages. Adding GNUnet Records is currently only usable "
+"for people, who know how a GNS Record looks like. This can be adapted to "
+"each record type.<br /> Last but not least, additional features, design "
+"changes, etc..."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:111
@@ -1451,100 +2250,95 @@ msgstr ""
msgid ""
"As a GNU project, GNUnet has participated in the Google Summer of Code "
"(GSoC) for a number of years. This page lists all current, past, and "
-"finished projects. If you want to participate and apply for any of the "
-"ideas for 2020 below or any past project which is not yet finished (or "
-"even your own idea), please contact us either in IRC or mailing list."
+"finished projects. If you want to participate and apply for any of the ideas "
+"for 2020 below or any past project which is not yet finished (or even your "
+"own idea), please contact us either in IRC or mailing list."
msgstr ""
#: template/gsoc.html.j2:34
msgid ""
-"The GNUnet team is currently working on a transport layer rewrite in "
-"order to fix core issues with connectivity. This new component is "
-"currently developed under the name \"TNG\". What is currently known as "
-"\"transport plugins\" will in the TNG be represented as "
-"\"communicators\". Communicators are processes with a well defined API "
-"that allow to connect peers over a specific protocol. The primary "
-"protocol which are already implemented are UNIX sockets, UDP sockets, and"
-" TCP sockets. For a truly resilient network, other connectivity options "
-"such as WiFi mesh, Bluetooth, HTTP(S), QUIC or even more obscure "
-"alternatives such as radio are required. In this project, the goal is to "
-"select, implement and test new communicators. While TNG is not yet ready,"
-" communicators can, by design, be developed and tested against the "
-"current API. We expect that this project can be worked on by multiple "
+"The GNUnet team is currently working on a transport layer rewrite in order "
+"to fix core issues with connectivity. This new component is currently "
+"developed under the name \"TNG\". What is currently known as \"transport "
+"plugins\" will in the TNG be represented as \"communicators\". Communicators "
+"are processes with a well defined API that allow to connect peers over a "
+"specific protocol. The primary protocol which are already implemented are "
+"UNIX sockets, UDP sockets, and TCP sockets. For a truly resilient network, "
+"other connectivity options such as WiFi mesh, Bluetooth, HTTP(S), QUIC or "
+"even more obscure alternatives such as radio are required. In this project, "
+"the goal is to select, implement and test new communicators. While TNG is "
+"not yet ready, communicators can, by design, be developed and tested against "
+"the current API. We expect that this project can be worked on by multiple "
"students as there are a lot of protocols to choose from. The tasks would "
"consist of: <ol> <li>Deciding which communicators to implement.</li> "
-"<li>Test the communicators.</li> <li>Documentation.</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of HTTPS, QUIC, Bluetooth or WiFi.</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Average, but depends on selected protocols. "
-"<br/> <strong>Mentors:</strong> Martin Schanzenbach, t3sserakt"
+"<li>Test the communicators.</li> <li>Documentation.</li> </ol> Advantageous "
+"skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge of HTTPS, QUIC, "
+"Bluetooth or WiFi.</li> </ol> <br/> <strong>Difficulty:</strong> Average, "
+"but depends on selected protocols. <br/> <strong>Mentors:</strong> Martin "
+"Schanzenbach, t3sserakt"
msgstr ""
#: template/gsoc.html.j2:79
msgid ""
-"The REST API currently only supports a single user system. This is an "
-"issue as on multi-user systems, access control must be enfoced on a per-"
-"user basis. In this project, the REST service must be extended to support"
-" user authentication. This includes the correct handling of user context "
-"switches. <ol> <li>Implement user authentication.</li> <li>Test the "
-"access control.</li> <li>Document the changes to the REST API.</li> </ol>"
-" Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of user authentication subsystems on Linux/Unix.</li> <li>REST/HTTP "
-"Authentication methods</li> </ol> <br/> <strong>Difficulty:</strong> "
-"Beginner <br/> <strong>Mentors:</strong> Martin Schanzenbach"
+"The REST API currently only supports a single user system. This is an issue "
+"as on multi-user systems, access control must be enfoced on a per-user "
+"basis. In this project, the REST service must be extended to support user "
+"authentication. This includes the correct handling of user context switches. "
+"<ol> <li>Implement user authentication.</li> <li>Test the access control.</"
+"li> <li>Document the changes to the REST API.</li> </ol> Advantageous skills/"
+"languages/frameworks: <ol> <li>C</li> <li>Knowledge of user authentication "
+"subsystems on Linux/Unix.</li> <li>REST/HTTP Authentication methods</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:111
msgid ""
-"reclaimID is a decentralized identity system build on top of the GNU Name"
-" System. Currently, there is a Webextension which uses the GNUnet <a "
-"href=\"https://rest.gnunet.org\";>REST API</a>. In order to improve "
-"adoption and ease of use, this project aims to include a full GNUnet node"
-" within the Webextention as a fallback. GNUnet can be compiled to Web "
-"Assembly or JavaScript as demonstrated <a "
-"href=\"https://gnunet.io\";>here</a>. The idea is to improve upon this "
-"concept and support more of GNUnet's subsystems. The difficulty of this "
-"project largely depends on the students proficiency with build tools, "
-"emscripten and improvisation skills. There non-exhaustive task list would"
-" be: <ol> <li>Improve existing GNUnet emscripten build to include more "
-"subsystems.</li> <li>Integrate the result into a Webextention.</li> "
+"reclaimID is a decentralized identity system build on top of the GNU Name "
+"System. Currently, there is a Webextension which uses the GNUnet <a href="
+"\"https://rest.gnunet.org\";>REST API</a>. In order to improve adoption and "
+"ease of use, this project aims to include a full GNUnet node within the "
+"Webextention as a fallback. GNUnet can be compiled to Web Assembly or "
+"JavaScript as demonstrated <a href=\"https://gnunet.io\";>here</a>. The idea "
+"is to improve upon this concept and support more of GNUnet's subsystems. The "
+"difficulty of this project largely depends on the students proficiency with "
+"build tools, emscripten and improvisation skills. There non-exhaustive task "
+"list would be: <ol> <li>Improve existing GNUnet emscripten build to include "
+"more subsystems.</li> <li>Integrate the result into a Webextention.</li> "
"<li>Integrate the result into the re:claimID Webextension</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> "
-"<li>emscripten</li> <li>Webextensions</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Challenging <br/> <strong>Mentors:</strong> "
-"Martin Schanzenbach"
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>emscripten</"
+"li> <li>Webextensions</li> </ol> <br/> <strong>Difficulty:</strong> "
+"Challenging <br/> <strong>Mentors:</strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:147
msgid ""
-"Currently, the keys in our statistics database are too verbose. For "
-"example: </p> <p> nse # flood messages received: 13<br/> nse # peers "
-"connected: 4<br/> nse # nodes in the network (estimate): 203<br/> nse # "
-"flood messages started: 5<br/> nse # estimated network diameter: 3<br/> "
-"nse # flood messages transmitted: 10<br/> </p> <p> With such verbose keys"
-" there's no easy way to form compact JSON document or entries for time-"
-"series database. And you can't query single stats without having to "
-"copypaste the line exactly and put in quotes. In short, the goals are "
-"to... <ol> <li>Think of a way how statistics entries can be made "
-"canonical.</li> <li>Implement the change and migrate existing uses.</li> "
-"<li>Document the format(s) and define an appropriate registration "
-"mechanism for identifiers</li> </ol> Relevant bugs: <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> "
-"</ol> <br/> <strong>Difficulty:</strong> Beginner <br/> "
-"<strong>Mentors:</strong> Martin Schanzenbach"
+"Currently, the keys in our statistics database are too verbose. For example: "
+"</p> <p> nse # flood messages received: 13<br/> nse # peers connected: 4<br/"
+"> nse # nodes in the network (estimate): 203<br/> nse # flood messages "
+"started: 5<br/> nse # estimated network diameter: 3<br/> nse # flood "
+"messages transmitted: 10<br/> </p> <p> With such verbose keys there's no "
+"easy way to form compact JSON document or entries for time-series database. "
+"And you can't query single stats without having to copypaste the line "
+"exactly and put in quotes. In short, the goals are to... <ol> <li>Think of a "
+"way how statistics entries can be made canonical.</li> <li>Implement the "
+"change and migrate existing uses.</li> <li>Document the format(s) and define "
+"an appropriate registration mechanism for identifiers</li> </ol> Relevant "
+"bugs: <a href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:187
msgid ""
-"The goal is to either build upon the (outdated) <a "
-"href=\"https://github.com/canndrew/gnunet-rs\";>GNUnet Rust bindings</a> "
-"or to follow the path of <a href=\"GNUnet Go\">https://github.com/bfix";
-"/gnunet-go</a> which tries to reimplement most of the GNUnet stack. The "
-"end result should be an extension template for GNUnet in the form of the "
-"existing <a href=\"https://git.gnunet.org/gnunet-ext.git/\";>C "
-"template</a> which allows to quickly start implementing services and "
-"libraries for GNUnet."
+"The goal is to either build upon the (outdated) <a href=\"https://github.com/";
+"canndrew/gnunet-rs\">GNUnet Rust bindings</a> or to follow the path of <a "
+"href=\"GNUnet Go\">https://github.com/bfix/gnunet-go</a> which tries to "
+"reimplement most of the GNUnet stack. The end result should be an extension "
+"template for GNUnet in the form of the existing <a href=\"https://git.gnunet.";
+"org/gnunet-ext.git/\">C template</a> which allows to quickly start "
+"implementing services and libraries for GNUnet."
msgstr ""
#: template/gsoc.html.j2:198 template/gsoc.html.j2:652
@@ -1569,27 +2363,26 @@ msgstr ""
#: template/gsoc.html.j2:229
msgid ""
-"Includes: Implementation of rudimentary Android compatibility for GNUnet,"
-" in part by porting the GNUnet utils scheduler to act as a thin wrapper "
-"over libuv."
+"Includes: Implementation of rudimentary Android compatibility for GNUnet, in "
+"part by porting the GNUnet utils scheduler to act as a thin wrapper over "
+"libuv."
msgstr ""
#: template/gsoc.html.j2:236
msgid ""
-"<strong>Mentors:</strong> <a href=\"https://www.goebel-";
-"consult.de/\">Hartmut Goebel</a>, Jeff Burdges, Christian Grothoff"
+"<strong>Mentors:</strong> <a href=\"https://www.goebel-consult.de/\";>Hartmut "
+"Goebel</a>, Jeff Burdges, Christian Grothoff"
msgstr ""
#: template/gsoc.html.j2:245
msgid ""
-"There is a push for migrating our CI to Gitlab. The CI should eventually "
-"not just run \"make check\" on various platforms, but also perform tests "
-"with multiple peers running in different VMs with specific network "
-"topologies (i.e. NAT) between them being simulated. The CI should also be"
-" integrated with Gauger for performance regression analysis. Running jobs"
-" only when dependencies have changed and scripting more granular triggers"
-" or ideally automatic dependency discovery (as done by the autotools) is "
-"also important."
+"There is a push for migrating our CI to Gitlab. The CI should eventually not "
+"just run \"make check\" on various platforms, but also perform tests with "
+"multiple peers running in different VMs with specific network topologies (i."
+"e. NAT) between them being simulated. The CI should also be integrated with "
+"Gauger for performance regression analysis. Running jobs only when "
+"dependencies have changed and scripting more granular triggers or ideally "
+"automatic dependency discovery (as done by the autotools) is also important."
msgstr ""
#: template/gsoc.html.j2:257
@@ -1598,19 +2391,18 @@ msgstr ""
#: template/gsoc.html.j2:267
msgid ""
-"One great problem of the current Internet is the lack of "
-"disintermediation. When people want to talk they need a chat service. "
-"When they want to share files they need a file transfer service. Although"
-" GNUnet already possesses quite advanced integration into Linux "
-"networking, a little extra work is needed for existing applications like "
-"irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by"
-" using a GNS hostname like friend.gnu. Once people have added a person to"
-" their GNS they can immediately message, exchange files and suchlike "
-"directly, with nothing but the GNUnet in the middle, using applications "
-"that have been distributed with unix systems ever since the 1980's. We "
-"can produce an OS distribution where these things work out of the box "
-"with the nicknames of people instead of cloud services. For more "
-"information and context, read"
+"One great problem of the current Internet is the lack of disintermediation. "
+"When people want to talk they need a chat service. When they want to share "
+"files they need a file transfer service. Although GNUnet already possesses "
+"quite advanced integration into Linux networking, a little extra work is "
+"needed for existing applications like irc, www, ftp, rsh, nntpd to run over "
+"it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. "
+"Once people have added a person to their GNS they can immediately message, "
+"exchange files and suchlike directly, with nothing but the GNUnet in the "
+"middle, using applications that have been distributed with unix systems ever "
+"since the 1980's. We can produce an OS distribution where these things work "
+"out of the box with the nicknames of people instead of cloud services. For "
+"more information and context, read"
msgstr ""
#: template/gsoc.html.j2:288
@@ -1619,8 +2411,7 @@ msgstr ""
#: template/gsoc.html.j2:296
msgid ""
-"Implement the AnycastExit spec to enable GNUnet clients to connect over "
-"Tor."
+"Implement the AnycastExit spec to enable GNUnet clients to connect over Tor."
msgstr ""
#: template/gsoc.html.j2:302 template/gsoc.html.j2:337
@@ -1631,9 +2422,9 @@ msgstr ""
#: template/gsoc.html.j2:307
msgid ""
"Note: There was a Special TLDs spec to allow Tor to resolve domain names "
-"using GNS over Tor too, but currently that's on hold until folks think "
-"more about how names should be moved around the local system. We're "
-"calling this more collaborative approach NSS2 for now."
+"using GNS over Tor too, but currently that's on hold until folks think more "
+"about how names should be moved around the local system. We're calling this "
+"more collaborative approach NSS2 for now."
msgstr ""
#: template/gsoc.html.j2:316 template/gsoc.html.j2:456
@@ -1643,17 +2434,16 @@ msgstr ""
#: template/gsoc.html.j2:329
msgid ""
-"Improve the Rust implementation of GNUnet utils, possibly including "
-"adding support for asynchronous IO using mio, or perhaps a higher level "
-"asynchronous IO library built upon it, such as rotor, mioco, eventual_io,"
-" or gj."
+"Improve the Rust implementation of GNUnet utils, possibly including adding "
+"support for asynchronous IO using mio, or perhaps a higher level "
+"asynchronous IO library built upon it, such as rotor, mioco, eventual_io, or "
+"gj."
msgstr ""
#: template/gsoc.html.j2:345
msgid ""
-"Implementation of a replacement for PANDA (see Pond) with better "
-"security, and maybe integration with the GNU Name System for key "
-"exchange."
+"Implementation of a replacement for PANDA (see Pond) with better security, "
+"and maybe integration with the GNU Name System for key exchange."
msgstr ""
#: template/gsoc.html.j2:357
@@ -1667,8 +2457,8 @@ msgstr ""
#: template/gsoc.html.j2:370
msgid ""
-"Implement different place types and file sharing by creating a new place "
-"for the shared content."
+"Implement different place types and file sharing by creating a new place for "
+"the shared content."
msgstr ""
#: template/gsoc.html.j2:376
@@ -1677,12 +2467,12 @@ msgstr ""
#: template/gsoc.html.j2:380
msgid ""
-"<ul> <li>File: generic file with comments</li> <li>Image: display an "
-"image with comments referencing a region of the image</li> <li>Sound: "
-"play a sound file with comments referencing a timestamp</li> "
-"<li>Directory/Album: pointers to File / Image / Sound places</li> "
-"<li>Event: with RSVP</li> <li>Survey: ask your social neighborhood "
-"questions in a structured form</li> </ul>"
+"<ul> <li>File: generic file with comments</li> <li>Image: display an image "
+"with comments referencing a region of the image</li> <li>Sound: play a sound "
+"file with comments referencing a timestamp</li> <li>Directory/Album: "
+"pointers to File / Image / Sound places</li> <li>Event: with RSVP</li> "
+"<li>Survey: ask your social neighborhood questions in a structured form</li> "
+"</ul>"
msgstr ""
#: template/gsoc.html.j2:391
@@ -1692,16 +2482,16 @@ msgstr ""
#: template/gsoc.html.j2:395
msgid ""
"<ul> <li>Fork existing channels, reorganize people into new chatrooms or "
-"channels.</li> <li>Share a post (edit and repost something elsewhere, on "
-"a fan page for example).</li> <li>Edit a previously published post + "
-"offer edit history to readers.</li> <li>Control expiry of channel "
-"history.</li> </ul>"
+"channels.</li> <li>Share a post (edit and repost something elsewhere, on a "
+"fan page for example).</li> <li>Edit a previously published post + offer "
+"edit history to readers.</li> <li>Control expiry of channel history.</li> </"
+"ul>"
msgstr ""
#: template/gsoc.html.j2:404
msgid ""
-"See also <a "
-"href=\"http://secushare.org/features\";>http://secushare.org/features</a>"
+"See also <a href=\"http://secushare.org/features\";>http://secushare.org/";
+"features</a>"
msgstr ""
#: template/gsoc.html.j2:409
@@ -1714,20 +2504,19 @@ msgstr ""
#: template/gsoc.html.j2:427
msgid ""
-"Implement aggregation of distributed state from various channels in order"
-" to provide for a powerful social graph API capable of producing social "
-"network profiles, dashboards, a calendar out of upcoming event "
-"invitations (if available), social search functionality and most of all "
-"to make it easy for users to adopt cryptographic identities of their "
-"contacts/friends simply by finding them in the social graph of their "
-"existing contacts (\"This is Linda. You have 11 contacts in common with "
-"her. [ADD]\")."
+"Implement aggregation of distributed state from various channels in order to "
+"provide for a powerful social graph API capable of producing social network "
+"profiles, dashboards, a calendar out of upcoming event invitations (if "
+"available), social search functionality and most of all to make it easy for "
+"users to adopt cryptographic identities of their contacts/friends simply by "
+"finding them in the social graph of their existing contacts (\"This is "
+"Linda. You have 11 contacts in common with her. [ADD]\")."
msgstr ""
#: template/gsoc.html.j2:445
msgid ""
-"Related to <a "
-"href=\"http://secushare.org/rendezvous\";>secushare.org/rendezvous</a>"
+"Related to <a href=\"http://secushare.org/rendezvous\";>secushare.org/"
+"rendezvous</a>"
msgstr ""
#: template/gsoc.html.j2:451 template/gsoc.html.j2:491
@@ -1736,21 +2525,21 @@ msgstr ""
#: template/gsoc.html.j2:468
msgid ""
-"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform "
-"traditional mail clients into secushare user interfaces. </li> <li> Think"
-" of ways to map e-mail addresses to secushare identities. </li> <li> "
-"Encode or translate various e-mail features into secushare equivalents. "
-"</li> <li> Parts of secushare are currently written in Rust, therefore "
-"Rust is preferred for this task but it is not an requirement. </li> </ul>"
+"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform traditional "
+"mail clients into secushare user interfaces. </li> <li> Think of ways to map "
+"e-mail addresses to secushare identities. </li> <li> Encode or translate "
+"various e-mail features into secushare equivalents. </li> <li> Parts of "
+"secushare are currently written in Rust, therefore Rust is preferred for "
+"this task but it is not an requirement. </li> </ul>"
msgstr ""
#: template/gsoc.html.j2:509
msgid ""
"Implementation of the GNUnet auction system described in Chapter 3 of <a "
"href=\"https://grothoff.org/christian/teich2017ms.pdf\";>this thesis</a>. "
-"Specific tasks are adding smart contract creation and round time "
-"enforcement to libbrandt as well as creating the GNUnet auction service, "
-"library and the three user interface programs create, info and join."
+"Specific tasks are adding smart contract creation and round time enforcement "
+"to libbrandt as well as creating the GNUnet auction service, library and the "
+"three user interface programs create, info and join."
msgstr ""
#: template/gsoc.html.j2:521
@@ -1759,9 +2548,9 @@ msgstr ""
#: template/gsoc.html.j2:539
msgid ""
-"Implementation of additional transports to make GNUnet communication more"
-" robust in the presence of problematic networks: GNUnet-over-SMTP, "
-"GNUnet-over-DNS"
+"Implementation of additional transports to make GNUnet communication more "
+"robust in the presence of problematic networks: GNUnet-over-SMTP, GNUnet-"
+"over-DNS"
msgstr ""
#: template/gsoc.html.j2:546 template/gsoc.html.j2:560
@@ -1775,16 +2564,16 @@ msgid ""
msgstr ""
#: template/gsoc.html.j2:568
-msgid "<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff
Burdges"
+msgid ""
+"<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff Burdges"
msgstr ""
#: template/gsoc.html.j2:576
msgid ""
-"Improving libaboss to make computation on shared secrets (including "
-"repeated multiplication) based on <a "
-"href=\"https://dl.acm.org/citation.cfm?doid=62212.62213\";>Ben-Or et "
-"al.</a> if possible. This in particular means moving libaboss to bignums "
-"(gcry_mpi)."
+"Improving libaboss to make computation on shared secrets (including repeated "
+"multiplication) based on <a href=\"https://dl.acm.org/citation.cfm?";
+"doid=62212.62213\">Ben-Or et al.</a> if possible. This in particular means "
+"moving libaboss to bignums (gcry_mpi)."
msgstr ""
#: template/gsoc.html.j2:589
@@ -1796,11 +2585,10 @@ msgstr ""
#: template/gsoc.html.j2:602
msgid ""
"Python 2.7 is reaching its end-of-life, and we want to get rid of the "
-"dependency on Python. The existing gnunet-qr tool is a rather simple "
-"wrapper around python-zbar, which itself wraps libzbar. The goal of this "
-"project is to directly use libzbar to scan QR codes for GNUnet / the GNU "
-"Name System (see also <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
+"dependency on Python. The existing gnunet-qr tool is a rather simple wrapper "
+"around python-zbar, which itself wraps libzbar. The goal of this project is "
+"to directly use libzbar to scan QR codes for GNUnet / the GNU Name System "
+"(see also <a href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
msgstr ""
#: template/gsoc.html.j2:612
@@ -1825,11 +2613,11 @@ msgstr ""
#: template/gsoc.html.j2:642
msgid ""
-"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a "
-"yet to be determined framework such as Angular2. This includes the design"
-" and implementation of not yet existing <a "
-"href=\"http://jsonapi.org/\";>REST APIs</a> that expose the <a "
-"href=\"https://docs.gnunet.org/doxygen/modules.html\";>GNUnet API</a>."
+"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a yet "
+"to be determined framework such as Angular2. This includes the design and "
+"implementation of not yet existing <a href=\"http://jsonapi.org/\";>REST "
+"APIs</a> that expose the <a href=\"https://docs.gnunet.org/doxygen/modules.";
+"html\">GNUnet API</a>."
msgstr ""
#: template/gsoc.html.j2:657
@@ -1838,8 +2626,7 @@ msgstr ""
#: template/gsoc.html.j2:667
msgid ""
-"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet "
-"WebUI</a>"
+"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet WebUI</a>"
msgstr ""
#: template/index.html.j2:8
@@ -1861,25 +2648,24 @@ msgstr ""
#: template/index.html.j2:49
msgid ""
"The conventional Internet is currently like a system of roads with deep "
-"potholes and highwaymen all over the place. Even if you still can use the"
-" roads (e.g. send emails, or browse websites) your vehicle might get "
+"potholes and highwaymen all over the place. Even if you still can use the "
+"roads (e.g. send emails, or browse websites) your vehicle might get "
"hijacked, damaged, or long arms might reach into its back and steal your "
-"items (data) to use it against you and sell it to others - while you "
-"can't even notice the thievery nor accuse and hold the scroungers "
-"accountable. <!-- Proposal from Fabian Gerlach: The conventional Internet"
-" is currently like a system of roads with deep potholes and surveillance "
-"cameras all over the place. Even if you still can use the roads (e.g. "
-"send emails, or browse websites) your vehicle might gets damaged. And the"
-" surveillance cameras will create a movement profile about your life: "
-"They recognize your car license plate, track you everywhere you drive, "
-"and save this information in a central data base. --> The Internet was "
-"not designed with security in mind: protecting against address forgery, "
-"routers learning metadata, or choosing trustworthy third parties is "
-"nontrivial and sometimes impossible. <!-- Proposal from Fabian Gerlach: "
-"The Internet is not designed with security in mind: The network generally"
-" learns too much about users; it has insecure defaults and high "
-"complexity; and it is centralized. That makes it very vulnerable for "
-"multiple attacks massively threatening our freedom. -->"
+"items (data) to use it against you and sell it to others - while you can'"
+"t even notice the thievery nor accuse and hold the scroungers accountable. "
+"<!-- Proposal from Fabian Gerlach: The conventional Internet is currently "
+"like a system of roads with deep potholes and surveillance cameras all over "
+"the place. Even if you still can use the roads (e.g. send emails, or browse "
+"websites) your vehicle might gets damaged. And the surveillance cameras will "
+"create a movement profile about your life: They recognize your car license "
+"plate, track you everywhere you drive, and save this information in a "
+"central data base. --> The Internet was not designed with security in mind: "
+"protecting against address forgery, routers learning metadata, or choosing "
+"trustworthy third parties is nontrivial and sometimes impossible. <!-- "
+"Proposal from Fabian Gerlach: The Internet is not designed with security in "
+"mind: The network generally learns too much about users; it has insecure "
+"defaults and high complexity; and it is centralized. That makes it very "
+"vulnerable for multiple attacks massively threatening our freedom. -->"
msgstr ""
#: template/index.html.j2:94
@@ -1889,10 +2675,10 @@ msgstr ""
#: template/index.html.j2:96
msgid ""
"GNUnet is a network protocol stack for building secure, distributed, and "
-"privacy-preserving applications.<br/> With strong roots in <a "
-"class=\"link\" href=\"https://bib.gnunet.org\";>academic research</a>, our"
-" goal is to replace the <a class=\"link\" href=\"https://secushare.org";
-"/broken-internet\">old insecure Internet</a> protocol stack."
+"privacy-preserving applications.<br/> With strong roots in <a class=\"link\" "
+"href=\"https://bib.gnunet.org\";>academic research</a>, our goal is to "
+"replace the <a class=\"link\" href=\"https://secushare.org/broken-internet";
+"\">old insecure Internet</a> protocol stack."
msgstr ""
#: template/index.html.j2:119
@@ -1903,10 +2689,9 @@ msgstr ""
msgid ""
"Your metadata is just as revealing as the actual content; and it gets "
"exposed on the Internet.<br> Even though transport encryption is "
-"increasingly being deployed on the Internet, it still reveals data that "
-"can threaten democracy: the identities of senders and receivers, the "
-"times, frequency and the volume of communication are all still "
-"revealed.<br>"
+"increasingly being deployed on the Internet, it still reveals data that can "
+"threaten democracy: the identities of senders and receivers, the times, "
+"frequency and the volume of communication are all still revealed.<br>"
msgstr ""
#: template/index.html.j2:150
@@ -1915,15 +2700,13 @@ msgstr ""
#: template/index.html.j2:152
msgid ""
-"It provides <a class=\"link\" "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";> improving "
-"addressing, routing, naming and content distribution</a> in a technically"
-" robust manner - as opposed to ad-hoc designs in place today. <!-- "
-"Proposal from fabian gerlach: GNUnet is built <a "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by "
-"design\"</a> and \"distributed by design\". This improves addressing, "
-"routing, naming and content distribution in a technically robust manner. "
-"-->"
+"It provides <a class=\"link\" href=\"https://www.w3.org/2014/strint/";
+"papers/65.pdf\"> improving addressing, routing, naming and content "
+"distribution</a> in a technically robust manner - as opposed to ad-hoc "
+"designs in place today. <!-- Proposal from fabian gerlach: GNUnet is built "
+"<a href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by design"
+"\"</a> and \"distributed by design\". This improves addressing, routing, "
+"naming and content distribution in a technically robust manner. -->"
msgstr ""
#: template/index.html.j2:177
@@ -1933,9 +2716,9 @@ msgstr ""
#: template/index.html.j2:179
msgid ""
"Today, monitoring increasingly centralized infrastructure, proprietary "
-"implementations, traffic shapers and firewalls restrict all of the <a "
-"class=\"link\" href=\"https://www.gnu.org/philosophy/free-";
-"sw.html\">essential freedoms</a> to various degrees."
+"implementations, traffic shapers and firewalls restrict all of the <a class="
+"\"link\" href=\"https://www.gnu.org/philosophy/free-sw.html\";>essential "
+"freedoms</a> to various degrees."
msgstr ""
#: template/index.html.j2:203
@@ -1944,14 +2727,14 @@ msgstr ""
#: template/index.html.j2:205
msgid ""
-"GNUnet is a self-organizing network and it is <a class=\"link\" "
-"href=\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as"
-" in freedom. GNUnet puts you in control of your data. You determine which"
-" data to share with whom, and you're not pressured to accept "
-"compromises. It gives users freedoms to securely access information "
-"(\"run\" the network), to study all aspects of the network's "
-"operation (\"access the code\"), to distribute information (\"copy\"), as"
-" well as the freedom to deploy new applications (\"modify\")."
+"GNUnet is a self-organizing network and it is <a class=\"link\" href="
+"\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as in "
+"freedom. GNUnet puts you in control of your data. You determine which data "
+"to share with whom, and you're not pressured to accept compromises. It "
+"gives users freedoms to securely access information (\"run\" the network), "
+"to study all aspects of the network's operation (\"access the code\"), "
+"to distribute information (\"copy\"), as well as the freedom to deploy new "
+"applications (\"modify\")."
msgstr ""
#: template/index.html.j2:229
@@ -1960,13 +2743,13 @@ msgstr ""
#: template/index.html.j2:232
msgid ""
-"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every "
-"other distributed or P2P project develops its own library stack, covering"
-" transports, stream muxing, discovery and others. This divides effort and"
-" multiplies bug count. --> Instead of sharing common components and tools"
-" for building P2P systems, every P2P project seems to re-invent the "
-"wheel. <!-- TODO: rework this sentence. --> This heightens the effort and"
-" increases the potential number of vulnerabilities."
+"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every other "
+"distributed or P2P project develops its own library stack, covering "
+"transports, stream muxing, discovery and others. This divides effort and "
+"multiplies bug count. --> Instead of sharing common components and tools for "
+"building P2P systems, every P2P project seems to re-invent the wheel. <!-- "
+"TODO: rework this sentence. --> This heightens the effort and increases the "
+"potential number of vulnerabilities."
msgstr ""
#: template/index.html.j2:264
@@ -1975,10 +2758,10 @@ msgstr ""
#: template/index.html.j2:266
msgid ""
-"It offers a metadata-preserving foundation for your application. It "
-"offers components for addressing, reliable encrypted channels with "
-"advanced routing and resource discovery and naming. Our work is based on "
-"continuous research spanning almost two decades."
+"It offers a metadata-preserving foundation for your application. It offers "
+"components for addressing, reliable encrypted channels with advanced routing "
+"and resource discovery and naming. Our work is based on continuous research "
+"spanning almost two decades."
msgstr ""
#: template/index.html.j2:286
@@ -2120,75 +2903,69 @@ msgstr ""
#: template/install.html.j2:12
msgid ""
-"Notice: GNUnet is still undergoing major development. It is largely "
-"<i>not yet ready</i> for usage beyond developers."
+"Notice: GNUnet is still undergoing major development. It is largely <i>not "
+"yet ready</i> for usage beyond developers."
msgstr ""
#: template/install.html.j2:18
msgid ""
-"<p>Please be aware that this project is still in an early alpha stage "
-"when it comes to running software – its not an easy task to rewrite"
-" the whole Internet! We are happy to get your <a "
-"href=\"engage.html\">helping hand</a> anytime! Further information is "
-"available in our <a href=\"https://docs.gnunet.org/#toc-Using-";
-"GNUnet-1\">handbook</a>. If you have any queries about the installation "
-"or the usage, please <a href=\"engage.html\">get in touch!</a></p>"
+"<p>Please be aware that this project is still in an early alpha stage when "
+"it comes to running software – its not an easy task to rewrite the "
+"whole Internet! We are happy to get your <a href=\"engage.html\">helping "
+"hand</a> anytime! Further information is available in our <a href=\"https://";
+"docs.gnunet.org/#toc-Using-GNUnet-1\">handbook</a>. If you have any queries "
+"about the installation or the usage, please <a href=\"engage.html\">get in "
+"touch!</a></p>"
msgstr ""
#: template/install.html.j2:30
msgid ""
"We recommend to use binary packages provided by the package manager "
-"integrated within your Operating System. GNUnet is reportedly available "
-"for at least: <ul> <li><a "
-"href=\"https://pkgs.alpinelinux.org/package/edge/testing/x86_64/gnunet\";>Alpine</a></li>"
-" <li><a "
-"href=\"https://www.archlinux.org/packages/community/x86_64/gnunet/\";>Arch</a></li>"
-" <li><a "
-"href=\"https://packages.debian.org/search?keywords=gnunet\";>Debian</a></li>"
-" <li><a "
-"href=\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora "
-"(Copr)</a></li> <li><a "
-"href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
-"href=\"https://github.com/Homebrew/homebrew-";
-"core/blob/master/Formula/gnunet.rb\">Homebrew</a></li> <li><a "
-"href=\"https://nixos.org/nixos/packages.html?attr=gnunet&channel=nixpkgs-";
-"unstable&query=gnunet\">NixOS</a></li> <li><a href=\"install-on-"
-"openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is available for your "
-"Operating System and it is missing, send us feedback so that we can add "
-"it to this list. Furthermore, if you are interested in packaging GNUnet "
-"for your Operating System, get in touch with us at gnunet-"
-"developers@gnu.org if you require help with this job. If you were using "
-"an Operating System with the Alpine package manager, GNUnet could be "
-"installed as simple as:"
+"integrated within your Operating System. GNUnet is reportedly available for "
+"at least: <ul> <li><a href=\"https://pkgs.alpinelinux.org/package/edge/";
+"testing/x86_64/gnunet\">Alpine</a></li> <li><a href=\"https://www.archlinux.";
+"org/packages/community/x86_64/gnunet/\">Arch</a></li> <li><a href=\"https://";
+"packages.debian.org/search?keywords=gnunet\">Debian</a></li> <li><a href="
+"\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora (Copr)</a></"
+"li> <li><a href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
+"href=\"https://github.com/Homebrew/homebrew-core/blob/master/Formula/gnunet.";
+"rb\">Homebrew</a></li> <li><a href=\"https://nixos.org/nixos/packages.html?";
+"attr=gnunet&channel=nixpkgs-unstable&query=gnunet\">NixOS</a></li> <li><a "
+"href=\"install-on-openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is "
+"available for your Operating System and it is missing, send us feedback so "
+"that we can add it to this list. Furthermore, if you are interested in "
+"packaging GNUnet for your Operating System, get in touch with us at gnunet-"
+"developers@gnu.org if you require help with this job. If you were using an "
+"Operating System with the Alpine package manager, GNUnet could be installed "
+"as simple as:"
msgstr ""
#: template/install.html.j2:61
msgid ""
-"Next we describe a generic way to install from source. If you are using "
-"one of the following Operating Systems these step-by-step guides might be"
-" useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href"
-"=\"install-on-debian9.html\">Debian 9</a>, <a href=\"install-on-"
-"macos.html\">Mac OS</a>, <a href=\"install-on-netbsd.html\">NetBSD</a>, "
-"<a href=\"install-on-ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not"
-" all of them might be totally up-to-date! Please <a "
-"href=\"engage.html\">ask us</a> if you get stuck."
+"Next we describe a generic way to install from source. If you are using one "
+"of the following Operating Systems these step-by-step guides might be "
+"useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href=\"install-on-"
+"debian9.html\">Debian 9</a>, <a href=\"install-on-macos.html\">Mac OS</a>, "
+"<a href=\"install-on-netbsd.html\">NetBSD</a>, <a href=\"install-on-"
+"ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not all of them might be "
+"totally up-to-date! Please <a href=\"engage.html\">ask us</a> if you get "
+"stuck."
msgstr ""
#: template/install.html.j2:75
msgid ""
-"First, install the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>required "
-"dependencies</a> of GNUnet. There are base requirements and optional "
-"requirements."
+"First, install the <a href=\"https://git.gnunet.org/gnunet.git/tree/README";
+"\">required dependencies</a> of GNUnet. There are base requirements and "
+"optional requirements."
msgstr ""
#: template/install.html.j2:81
msgid ""
"Now, you need to decide if you want to install GNUnet from the release "
"tarball or from git. If you want to use GNUnet and there is no binary "
-"package available for your OS, you should stick with the release tarball."
-" If you want to develop using the most recent build, you should go with "
-"the <a href=\"https://git.gnunet.org/\";>git repository</a>."
+"package available for your OS, you should stick with the release tarball. If "
+"you want to develop using the most recent build, you should go with the <a "
+"href=\"https://git.gnunet.org/\";>git repository</a>."
msgstr ""
#: template/install.html.j2:98
@@ -2197,8 +2974,8 @@ msgstr ""
#: template/install.html.j2:106
msgid ""
-"Before building GNUnet, make sure that you setup the required groups and "
-"add your user to the group <code>gnunet</code>:"
+"Before building GNUnet, make sure that you setup the required groups and add "
+"your user to the group <code>gnunet</code>:"
msgstr ""
#: template/install.html.j2:117
@@ -2207,9 +2984,8 @@ msgstr ""
#: template/install.html.j2:128
msgid ""
-"You can find more configuration flags in the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>README</a>.<br> "
-"Install GNUnet with:"
+"You can find more configuration flags in the <a href=\"https://git.gnunet.";
+"org/gnunet.git/tree/README\">README</a>.<br> Install GNUnet with:"
msgstr ""
#: template/install.html.j2:138
@@ -2219,9 +2995,8 @@ msgstr ""
#: template/install.html.j2:146
msgid ""
"Check the <a href=\"https://docs.gnunet.org/handbook/gnunet.html#Minimal-";
-"configuration\">handbook</a> for detailed documentation. For a more "
-"hands-on experience, <a href=\"https://gnunet.org/en/use.html\";>continue "
-"here</a>."
+"configuration\">handbook</a> for detailed documentation. For a more hands-on "
+"experience, <a href=\"https://gnunet.org/en/use.html\";>continue here</a>."
msgstr ""
#: template/livingstandards.html.j2:11
diff --git a/locale/ko/LC_MESSAGES/messages.po
b/locale/ko/LC_MESSAGES/messages.po
index 6b25ee3..2a3d82e 100644
--- a/locale/ko/LC_MESSAGES/messages.po
+++ b/locale/ko/LC_MESSAGES/messages.po
@@ -7,13 +7,13 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2021-03-03 21:41+0100\n"
+"POT-Creation-Date: 2021-03-12 15:55+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
"Language: ko\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.9.0\n"
@@ -63,6 +63,7 @@ msgid "About"
msgstr ""
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
msgstr ""
@@ -155,17 +156,20 @@ msgstr ""
msgid "FAQ"
msgstr ""
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
msgstr ""
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
msgstr ""
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
msgstr ""
@@ -180,39 +184,38 @@ msgstr ""
#: template/about.html.j2:13
msgid ""
-"GNUnet is an alternative network stack for building secure, decentralized"
-" and privacy-preserving distributed applications. Our goal is to replace "
-"the old insecure Internet protocol stack. Starting from an application "
-"for secure publication of files, it has grown to include all kinds of "
-"basic protocol components and applications towards the creation of a GNU "
-"internet."
+"GNUnet is an alternative network stack for building secure, decentralized "
+"and privacy-preserving distributed applications. Our goal is to replace the "
+"old insecure Internet protocol stack. Starting from an application for "
+"secure publication of files, it has grown to include all kinds of basic "
+"protocol components and applications towards the creation of a GNU internet."
msgstr ""
#: template/about.html.j2:23
msgid ""
-"Today, the actual use and thus the social requirements for a global "
-"network differs widely from those goals of 1970. While the Internet "
-"remains suitable for military use, where the network equipment is "
-"operated by a command hierarchy and when necessary isolated from the rest"
-" of the world, the situation is less tenable for civil society."
+"Today, the actual use and thus the social requirements for a global network "
+"differs widely from those goals of 1970. While the Internet remains suitable "
+"for military use, where the network equipment is operated by a command "
+"hierarchy and when necessary isolated from the rest of the world, the "
+"situation is less tenable for civil society."
msgstr ""
#: template/about.html.j2:32
msgid ""
"Due to fundamental Internet design choices, Internet traffic can be "
-"misdirected, intercepted, censored and manipulated by hostile routers on "
-"the network. And indeed, the modern Internet has evolved exactly to the "
-"point where, as Matthew Green put it, <a "
-"href=\"https://blog.cryptographyengineering.com/2015/08/16/the-network-";
-"is-hostile/\">\"the network is hostile\"</a>."
+"misdirected, intercepted, censored and manipulated by hostile routers on the "
+"network. And indeed, the modern Internet has evolved exactly to the point "
+"where, as Matthew Green put it, <a href=\"https://blog.";
+"cryptographyengineering.com/2015/08/16/the-network-is-hostile/\">\"the "
+"network is hostile\"</a>."
msgstr ""
#: template/about.html.j2:41
msgid ""
-"We believe liberal societies need a network architecture that uses the "
-"anti-authoritarian decentralized peer-to-peer paradigm and privacy-"
-"preserving cryptographic protocols. The goal of the GNUnet project is to "
-"provide a Free Software realization of this ideal."
+"We believe liberal societies need a network architecture that uses the anti-"
+"authoritarian decentralized peer-to-peer paradigm and privacy-preserving "
+"cryptographic protocols. The goal of the GNUnet project is to provide a Free "
+"Software realization of this ideal."
msgstr ""
#: template/about.html.j2:49
@@ -223,8 +226,8 @@ msgstr ""
#: template/about.html.j2:56
msgid ""
-"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy";
-"/free-sw.html\">Free Software</a>."
+"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy/free-";
+"sw.html\">Free Software</a>."
msgstr ""
#: template/about.html.j2:60
@@ -235,8 +238,8 @@ msgstr ""
#: template/about.html.j2:61
msgid ""
-"GNUnet must be fully distributed and resilient to external attacks and "
-"rogue participants."
+"GNUnet must be fully distributed and resilient to external attacks and rogue "
+"participants."
msgstr ""
#: template/about.html.j2:62
@@ -247,8 +250,8 @@ msgstr ""
#: template/about.html.j2:63
msgid ""
-"GNUnet must inform the user which other participants have to be trusted "
-"when establishing private communications."
+"GNUnet must inform the user which other participants have to be trusted when "
+"establishing private communications."
msgstr ""
#: template/about.html.j2:64
@@ -269,33 +272,28 @@ msgstr ""
#: template/about.html.j2:68
msgid ""
-"GNUnet must provide incentives for peers to contribute more resources "
-"than they consume."
+"GNUnet must provide incentives for peers to contribute more resources than "
+"they consume."
msgstr ""
#: template/about.html.j2:72
msgid ""
-"To get know and learn more, please check our <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, "
-"especially the <a href=\"https://docs.gnunet.org/handbook/gnunet.html";
-"#Key-Concepts\">chapter on \"Key Concepts\"</a>, explaining the "
-"fundamental concepts of GNUnet: <ul> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Authentication\";>Authentication</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Accounting-";
-"to-Encourage-Resource-Sharing\">Accounting to Encourage Resource "
-"Sharing</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Confidentiality\";>Confidentiality</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability\";>Deniability</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Peer-";
-"Identities\">Peer Identities</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-";
-"Name-System-_0028GNS-Zones_0029\">Zones in the GNU Name System (GNS "
-"Zones)</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> "
-"</ul>"
+"To get know and learn more, please check our <a href=\"https://docs.gnunet.";
+"org/handbook/gnunet.html\">handbook</a>, especially the <a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Key-Concepts\">chapter on \"Key Concepts"
+"\"</a>, explaining the fundamental concepts of GNUnet: <ul> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Authentication";
+"\">Authentication</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Accounting-to-Encourage-Resource-Sharing\">Accounting to "
+"Encourage Resource Sharing</a></li> <li><a href=\"https://docs.gnunet.org/";
+"handbook/gnunet.html#Confidentiality\">Confidentiality</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></"
+"li> <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability";
+"\">Deniability</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Peer-Identities\">Peer Identities</a></li> <li><a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-Name-System-_0028GNS-"
+"Zones_0029\">Zones in the GNU Name System (GNS Zones)</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> </ul>"
msgstr ""
#: template/about.html.j2:88
@@ -304,27 +302,27 @@ msgstr ""
#: template/about.html.j2:90
msgid ""
-"There are many more resources to learn about GNUnet besides the <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such "
-"as the <a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers "
-"covering the various layers, many <a "
-"href=\"https://gnunet.org/en/video.html\";>videos</a> or a brief <a "
-"href=\"https://gnunet.org/en/glossary.html\";>glossary</a>."
+"There are many more resources to learn about GNUnet besides the <a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such as the "
+"<a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers covering "
+"the various layers, many <a href=\"https://gnunet.org/en/video.html";
+"\">videos</a> or a brief <a href=\"https://gnunet.org/en/glossary.html";
+"\">glossary</a>."
msgstr ""
#: template/about.html.j2:95
msgid ""
"You are most welcome to <a href=\"engage.html\">get engaged into the "
-"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a "
-"href=\"use.html\">use it</a> and <a href=\"engage.html\">contribute and "
-"get engaged</a> in various ways."
+"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a href=\"use."
+"html\">use it</a> and <a href=\"engage.html\">contribute and get engaged</a> "
+"in various ways."
msgstr ""
#: template/about.html.j2:100
msgid ""
-"Please be aware that this project is (despite of it's age) still in an "
-"early alpha stage when it comes to software – its not an easy task "
-"to rewrite the whole Internet!"
+"Please be aware that this project is (despite of it's age) still in an early "
+"alpha stage when it comes to software – its not an easy task to "
+"rewrite the whole Internet!"
msgstr ""
#: template/about.html.j2:105
@@ -333,24 +331,25 @@ msgstr ""
#: template/about.html.j2:110
msgid ""
-"We're receiving funding from NLnet's Next Generation Internet funding "
-"line to document and implement the GNU Name System protocol in a way "
-"suitable for the IETF standardization process."
+"We're receiving funding from NLnet's Next Generation Internet funding line "
+"to document and implement the GNU Name System protocol in a way suitable for "
+"the IETF standardization process."
msgstr ""
#: template/about.html.j2:123
msgid ""
"This project has received funding from the European Union’s Horizon 2020 "
"research and innovation programme under the NGI_TRUST grant agreement no "
-"825618. The project aims to integrate re:claimID with the GNU Taler "
-"payment system in a pilot in order to demonstrate the practical "
-"feasibility and benefits of privacy enhancing technologies for users and "
-"commercial service providers. The project is called \"Decentralized "
-"Identities for Self-Sovereign End-users\" (DISSENS)."
+"825618. The project aims to integrate re:claimID with the GNU Taler payment "
+"system in a pilot in order to demonstrate the practical feasibility and "
+"benefits of privacy enhancing technologies for users and commercial service "
+"providers. The project is called \"Decentralized Identities for Self-"
+"Sovereign End-users\" (DISSENS)."
msgstr ""
#: template/about.html.j2:141
-msgid "We are grateful for free hosting offered by the following
organizations:"
+msgid ""
+"We are grateful for free hosting offered by the following organizations:"
msgstr ""
#: template/about.html.j2:150
@@ -371,13 +370,13 @@ msgstr ""
#: template/applications.html.j2:15
msgid ""
-"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully "
-"decentralized replacement for the Domain Name System (DNS). Instead of "
-"using a hierarchy, GNS uses a directed graph. Naming conventions are "
-"similar to DNS, but queries and replies are private even with respect to "
-"peers providing the answers. The integrity of records and privacy of "
-"look-ups is cryptographically secured. <!-- Too technical: GNS integrates"
-" a robust, efficient and instant key revocation mechanism. -->"
+"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully decentralized "
+"replacement for the Domain Name System (DNS). Instead of using a hierarchy, "
+"GNS uses a directed graph. Naming conventions are similar to DNS, but "
+"queries and replies are private even with respect to peers providing the "
+"answers. The integrity of records and privacy of look-ups is "
+"cryptographically secured. <!-- Too technical: GNS integrates a robust, "
+"efficient and instant key revocation mechanism. -->"
msgstr ""
#: template/applications.html.j2:38
@@ -386,8 +385,8 @@ msgstr ""
#: template/applications.html.j2:40
msgid ""
-"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized"
-" Identity Provider (IdP) service built in top of the GNU Name System. It "
+"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized "
+"Identity Provider (IdP) service built in top of the GNU Name System. It "
"allows users to securely share personal information with websites using "
"standardized protocols (OpenID Connect)."
msgstr ""
@@ -398,10 +397,9 @@ msgstr ""
#: template/applications.html.j2:59
msgid ""
-"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that "
-"aims to provide censorship-resistant, anonymous filesharing. The "
-"publisher is empowered to make a gradual choice between performance and "
-"anonymity."
+"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that aims "
+"to provide censorship-resistant, anonymous filesharing. The publisher is "
+"empowered to make a gradual choice between performance and anonymity."
msgstr ""
#: template/applications.html.j2:73
@@ -411,8 +409,8 @@ msgstr ""
#: template/applications.html.j2:75
msgid ""
"GNUnet conversation is an application that provides secure voice "
-"communication in a fully decentralized way by employing GNUnet for "
-"routing and transport."
+"communication in a fully decentralized way by employing GNUnet for routing "
+"and transport."
msgstr ""
#: template/applications.html.j2:91
@@ -426,8 +424,8 @@ msgstr ""
#: template/applications.html.j2:99
msgid ""
"<a href=\"https://taler.net/\";>GNU Taler</a> is a new privacy-preserving "
-"electronic payment system. Payments are cryptographically secured and are"
-" confirmed within milliseconds with extremely low transaction costs."
+"electronic payment system. Payments are cryptographically secured and are "
+"confirmed within milliseconds with extremely low transaction costs."
msgstr ""
#: template/applications.html.j2:118
@@ -436,10 +434,10 @@ msgstr ""
#: template/applications.html.j2:120
msgid ""
-"<a href=\"https://secushare.org/\";>secushare</a> is creating a "
-"decentralized social networking application on top of GNUnet. Using "
-"overlay multicast and the extensible PSYC protocol, notifications are "
-"distributed end-to-end encrypted to authorized recipients only."
+"<a href=\"https://secushare.org/\";>secushare</a> is creating a decentralized "
+"social networking application on top of GNUnet. Using overlay multicast and "
+"the extensible PSYC protocol, notifications are distributed end-to-end "
+"encrypted to authorized recipients only."
msgstr ""
#: template/applications.html.j2:139
@@ -448,10 +446,10 @@ msgstr ""
#: template/applications.html.j2:141
msgid ""
-"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) "
-"is creating a usable end-to-end encrypted e-mail solution using "
-"opportunistic key exchange. p≡p will use GNUnet to protect metadata"
-" and exploit new cryptographic protocols to verify keys."
+"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) is "
+"creating a usable end-to-end encrypted e-mail solution using opportunistic "
+"key exchange. p≡p will use GNUnet to protect metadata and exploit new "
+"cryptographic protocols to verify keys."
msgstr ""
#: template/applications.html.j2:160
@@ -460,10 +458,10 @@ msgstr ""
#: template/applications.html.j2:162
msgid ""
-"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> "
-"is a convenient but feature-rich graphical application providing "
-"messaging using especially the CADET subsystem. It is developed using GTK"
-" and libhandy for a convergent design."
+"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> is a "
+"convenient but feature-rich graphical application providing messaging using "
+"especially the CADET subsystem. It is developed using GTK and libhandy for a "
+"convergent design."
msgstr ""
#: template/applications.html.j2:180
@@ -474,8 +472,8 @@ msgstr ""
msgid ""
"<a href=\"https://git.gnunet.org/groupchat.git/\";>groupchat</a> is a "
"terminal user interface providing messaging using especially the CADET "
-"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned"
-" to be compatible."
+"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned to "
+"be compatible."
msgstr ""
#: template/architecture.html.j2:6
@@ -488,11 +486,11 @@ msgstr ""
#: template/architecture.html.j2:22
msgid ""
-"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-"
-"like end-to-end encrypted messaging layer (CADET), a public key "
-"infrastructure (GNS) and a pluggable transport system (TRANSPORT).<br> "
-"Using public keys for addresses and self-organized decentralized routing "
-"algorithms, these subsystems replace the traditional TCP/IP stack."
+"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-like "
+"end-to-end encrypted messaging layer (CADET), a public key infrastructure "
+"(GNS) and a pluggable transport system (TRANSPORT).<br> Using public keys "
+"for addresses and self-organized decentralized routing algorithms, these "
+"subsystems replace the traditional TCP/IP stack."
msgstr ""
#: template/architecture.html.j2:35
@@ -503,9 +501,9 @@ msgstr ""
msgid ""
"GNUnet is implemented using a multi-process architecture. Each subsystem "
"runs as a separate process, providing fault-isolation and enabling tight "
-"permissions to be granted to each subsystem. Naturally, the "
-"implementation is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and"
-" will always remain free software."
+"permissions to be granted to each subsystem. Naturally, the implementation "
+"is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and will always "
+"remain free software."
msgstr ""
#: template/architecture.html.j2:52
@@ -538,11 +536,10 @@ msgstr ""
#: template/contact.html.j2:13
msgid ""
-"An archived, public mailing list for GNUnet is hosted at <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers\">https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>. You can send messages to the list at <a href=\"mailto"
-":gnunet-developers@gnu.org\">gnunet-developers@gnu.org</a>."
+"An archived, public mailing list for GNUnet is hosted at <a href=\"https://";
+"lists.gnu.org/mailman/listinfo/gnunet-developers\">https://lists.gnu.org/";
+"mailman/listinfo/gnunet-developers</a>. You can send messages to the list at "
+"<a href=\"mailto:gnunet-developers@gnu.org\";>gnunet-developers@gnu.org</a>."
msgstr ""
#: template/contact.html.j2:23
@@ -551,10 +548,9 @@ msgstr ""
#: template/contact.html.j2:25
msgid ""
-"<tt>#gnunet</tt> is reachable via <a "
-"href=\"https://freenode.net\";>irc.freenode.net</a>. There is also an <a "
-"href=\"https://view.matrix.org/room/!IjaAfLiruzjxFFzKAV:matrix.org/\";>archive</a>"
-" available."
+"<tt>#gnunet</tt> is reachable via <a href=\"https://freenode.net\";>irc."
+"freenode.net</a>. There is also an <a href=\"https://view.matrix.org/room/!";
+"IjaAfLiruzjxFFzKAV:matrix.org/\">archive</a> available."
msgstr ""
#: template/contact.html.j2:38
@@ -563,11 +559,10 @@ msgstr ""
#: template/contact.html.j2:40
msgid ""
-"GNUnet developers are generally reachable at either "
-"<tt>PSEUDONYM@gnunet.org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us"
-" support receiving GnuPG encrypted Emails. Urgent and sensitive security "
-"issues may be addressed to the GNU maintainers <tt>schanzen</tt> and "
-"<tt>grothoff</tt>."
+"GNUnet developers are generally reachable at either <tt>PSEUDONYM@gnunet."
+"org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us support receiving GnuPG "
+"encrypted Emails. Urgent and sensitive security issues may be addressed to "
+"the GNU maintainers <tt>schanzen</tt> and <tt>grothoff</tt>."
msgstr ""
#: template/contact.html.j2:53
@@ -576,38 +571,37 @@ msgstr ""
#: template/contact.html.j2:55
msgid ""
-"We track open feature requests and bugs for projects within GNUnet in our"
-" <a href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also "
-"report bugs or feature requests to the <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/bug-gnunet\";>bug-gnunet</a>"
-" mailing list. The mailinglist requires no subscription."
+"We track open feature requests and bugs for projects within GNUnet in our <a "
+"href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also report bugs "
+"or feature requests to the <a href=\"https://lists.gnu.org/mailman/listinfo/";
+"bug-gnunet\">bug-gnunet</a> mailing list. The mailinglist requires no "
+"subscription."
msgstr ""
#: template/copyright.html.j2:11
msgid ""
-"<p> Contributors to GNUnet with Git access must sign the <a "
-"href=\"/static/pdf/copyright.pdf\">copyright assignment</a> to ensure "
-"that the <a href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/gnunet_taler_agreement.tex\">GNUnet e.V. --- Taler Systems SA"
-" agreement on licensing and collaborative development</a> of the GNUnet "
-"and GNU Taler projects is satisfied. </p>"
+"<p> Contributors to GNUnet with Git access must sign the <a href=\"/static/"
+"pdf/copyright.pdf\">copyright assignment</a> to ensure that the <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/gnunet_taler_agreement.tex";
+"\">GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative "
+"development</a> of the GNUnet and GNU Taler projects is satisfied. </p>"
msgstr ""
#: template/copyright.html.j2:22
msgid ""
-"<p>The agreements ensure that the code will continue to be made available"
-" under free software licenses, but gives developers the freedom to move "
-"code between GNUnet and GNU Taler without worrying about licenses and to "
-"give the company the ability to dual-license (for example, so that we can"
-" distribute via App-stores that are hostile to free software).</p>"
+"<p>The agreements ensure that the code will continue to be made available "
+"under free software licenses, but gives developers the freedom to move code "
+"between GNUnet and GNU Taler without worrying about licenses and to give the "
+"company the ability to dual-license (for example, so that we can distribute "
+"via App-stores that are hostile to free software).</p>"
msgstr ""
#: template/copyright.html.j2:30
msgid ""
-"<p>Minor contributions (basically, anyone without Git access) do not "
-"require copyright assignment. Pseudonymous contributions are accepted, in"
-" this case simply sign the agreement with your pseudonym. Scanned copies "
-"are sufficient, but snail mail is preferred.</p>"
+"<p>Minor contributions (basically, anyone without Git access) do not require "
+"copyright assignment. Pseudonymous contributions are accepted, in this case "
+"simply sign the agreement with your pseudonym. Scanned copies are "
+"sufficient, but snail mail is preferred.</p>"
msgstr ""
#: template/developers.html.j2:5
@@ -620,14 +614,14 @@ msgstr ""
#: template/developers.html.j2:16
msgid ""
-"A list of our Git repositories can be found on our our <a "
-"href=\"https://git.gnunet.org/\";>Git Server</a>."
+"A list of our Git repositories can be found on our our <a href=\"https://git.";
+"gnunet.org/\">Git Server</a>."
msgstr ""
#: template/developers.html.j2:27
msgid ""
-"Technical papers can be found in our <a "
-"href=\"https://old.gnunet.org/bibliography\";>bibliography</a>."
+"Technical papers can be found in our <a href=\"https://old.gnunet.org/";
+"bibliography\">bibliography</a>."
msgstr ""
#: template/developers.html.j2:34
@@ -636,10 +630,10 @@ msgstr ""
#: template/developers.html.j2:37
msgid ""
-"We have a mailing list for developer discussions. You can subscribe to or"
-" read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo";
-"/gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>."
+"We have a mailing list for developer discussions. You can subscribe to or "
+"read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo/";
+"gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-developers</"
+"a>."
msgstr ""
#: template/developers.html.j2:47
@@ -648,9 +642,9 @@ msgstr ""
#: template/developers.html.j2:50
msgid ""
-"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests "
-"to detect regressions and check for portability at <a "
-"href=\"https://old.gnunet.org/buildbot/gnunet/\";>https://old.gnunet.org/buildbot/gnunet/</a>."
+"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests to "
+"detect regressions and check for portability at <a href=\"https://old.gnunet.";
+"org/buildbot/gnunet/\">https://old.gnunet.org/buildbot/gnunet/</a>."
msgstr ""
#: template/developers.html.j2:59
@@ -659,10 +653,9 @@ msgstr ""
#: template/developers.html.j2:62
msgid ""
-"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> "
-"to analyze the code coverage of our tests, the results are available at "
-"<a "
-"href=\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
+"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> to "
+"analyze the code coverage of our tests, the results are available at <a href="
+"\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
msgstr ""
#: template/developers.html.j2:72
@@ -671,9 +664,9 @@ msgstr ""
#: template/developers.html.j2:75
msgid ""
-"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for "
-"performance regression analysis of the exchange backend at <a "
-"href=\"https://old.gnunet.org/gauger/\";>https://old.gnunet.org/gauger/</a>."
+"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for performance "
+"regression analysis of the exchange backend at <a href=\"https://old.gnunet.";
+"org/gauger/\">https://old.gnunet.org/gauger/</a>."
msgstr ""
#: template/download.html.j2:7 template/gnurl.html.j2:209
@@ -682,8 +675,8 @@ msgstr ""
#: template/download.html.j2:11
msgid ""
-"Here you can download releases of our software and find links to the "
-"various versions."
+"Here you can download releases of our software and find links to the various "
+"versions."
msgstr ""
#: template/download.html.j2:17
@@ -705,7 +698,8 @@ msgid "git"
msgstr ""
#: template/download.html.j2:32
-msgid "You can fetch the git tag of version 0.11.x from our development
server:"
+msgid ""
+"You can fetch the git tag of version 0.11.x from our development server:"
msgstr ""
#: template/engage.html.j2:6
@@ -722,18 +716,17 @@ msgstr ""
#: template/ev.html.j2:13
msgid ""
-"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the"
-" \"Verein zur Förderung von GNUnet e.V.\", an association under "
-"German law to support GNUnet development. The Amtsgericht München "
-"registered the association on the 7th of March under VR 205287."
+"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the "
+"\"Verein zur Förderung von GNUnet e.V.\", an association under German "
+"law to support GNUnet development. The Amtsgericht München registered "
+"the association on the 7th of March under VR 205287."
msgstr ""
#: template/ev.html.j2:22
msgid ""
-"The association is officially dedicated to supporting research, "
-"development and education in the area of secure decentralized networking "
-"in general, and GNUnet specifically. This is the official website for the"
-" association."
+"The association is officially dedicated to supporting research, development "
+"and education in the area of secure decentralized networking in general, and "
+"GNUnet specifically. This is the official website for the association."
msgstr ""
#: template/ev.html.j2:31
@@ -742,15 +735,15 @@ msgstr ""
#: template/ev.html.j2:33
msgid ""
-"GNUnet developers with git (write) access can become members to "
-"participate in the decision process and formally support GNUnet e.V. For "
-"this, all you have to do is update the <tt>members.txt</tt> file in the "
-"<a href=\"https://git.gnunet.org/gnunet-ev.git/\";>gnunet-ev</a> "
-"repository. There are no membership dues; however, members are required "
-"to support GNUnet e.V. and in particularly contribute to the technical "
-"development within their means. For further details, we refer to the <a "
-"href=\"https://git.gnunet.org/gnunet-ev.git/\";>Satzung</a> (currently "
-"only available in German, translations welcome)."
+"GNUnet developers with git (write) access can become members to participate "
+"in the decision process and formally support GNUnet e.V. For this, all you "
+"have to do is update the <tt>members.txt</tt> file in the <a href=\"https://";
+"git.gnunet.org/gnunet-ev.git/\">gnunet-ev</a> repository. There are no "
+"membership dues; however, members are required to support GNUnet e.V. and in "
+"particularly contribute to the technical development within their means. For "
+"further details, we refer to the <a href=\"https://git.gnunet.org/gnunet-ev.";
+"git/\">Satzung</a> (currently only available in German, translations "
+"welcome)."
msgstr ""
#: template/ev.html.j2:52
@@ -759,16 +752,13 @@ msgstr ""
#: template/ev.html.j2:54
msgid ""
-"You can find our \"Satzung\", and the list of members under <a "
-"href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex\">https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex</a>. The current board consists of: "
+"You can find our \"Satzung\", and the list of members under <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex\";>https://git.gnunet.";
+"org/gnunet-ev.git/tree/satzung.tex</a>. The current board consists of: "
"<dl><dt>Vorsitz</dt> <dd><a href=\"https://schanzen.eu\";>Martin "
-"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> "
-"<dd>t3sserakt</dd> <dt>Kassenwart</dt> <dd>Florian Dold</dd> "
-"<dt>Beisitzer</dt> <dd> <a "
-"href=\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 "
-"</dd> </dl>"
+"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> <dd>t3sserakt</dd> "
+"<dt>Kassenwart</dt> <dd>Florian Dold</dd> <dt>Beisitzer</dt> <dd> <a href="
+"\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 </dd> </dl>"
msgstr ""
#: template/ev.html.j2:73
@@ -783,77 +773,801 @@ msgstr ""
msgid ""
"Everybody is welcome to support us via donations. For financial "
"contributions, Europeans are able to donate via SEPA. We hope to setup "
-"accounts in other major currency areas in the future. You can also donate"
-" via Bitcoin, routing details are given below. Please note that we are "
-"unable to provide receipts for your donations. If you are planning to "
-"donate a significant amount of money, please contact us first as it might"
-" be better to come to a custom arrangement. <dl><dt>BitCoin</dt> "
+"accounts in other major currency areas in the future. You can also donate "
+"via Bitcoin, routing details are given below. Please note that we are unable "
+"to provide receipts for your donations. If you are planning to donate a "
+"significant amount of money, please contact us first as it might be better "
+"to come to a custom arrangement. <dl><dt>BitCoin</dt> "
"<dd>1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh</dd> <dt>SEPA/IBAN</dt> "
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
-#: template/faq.html.j2:12
-msgid "Is GNUnet ready for use on production systems?"
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
msgstr ""
-#: template/faq.html.j2:14
-msgid ""
-"A: GNUnet is still undergoing major development. It is largely not yet "
-"ready for usage beyond developers. Your mileage will vary depending on "
-"the functionality you use, but you will always likely run into issues "
-"with our current low-level transport system. We are currently in the "
-"process of rewriting it (Project "Transport Next Generation "
-"[TNG]")"
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
msgstr ""
-#: template/faq.html.j2:24
-msgid "Is GNUnet build using distributed ledger technologies?"
+#: template/faq.html.j2:15 template/faq.html.j2:594
+msgid "Error messages"
+msgstr ""
+
+#: template/faq.html.j2:16 template/faq.html.j2:696
+msgid "File-sharing"
+msgstr ""
+
+#: template/faq.html.j2:17 template/faq.html.j2:872
+msgid "Contributing"
msgstr ""
#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr ""
+
+#: template/faq.html.j2:28
msgid ""
-"A: No. GNUnet is a new network protocol stack for building secure, "
-"distributed, and privacy-preserving applications. While a ledger could be"
-" built using GNUnet, we currently have no plans in doing so."
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
+"the #gnunet IRC on irc.freenode.net."
msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
+msgstr ""
+
+#: template/faq.html.j2:38
msgid ""
-"I receive many "WARNING Calculated flow delay for X at Y for "
-"Z". Should I worry?"
+"A: The general answer is, when it is ready. A better answer may be: earlier "
+"if you contribute (test, debug, code, document). Every release will be "
+"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://";
+"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
+"the RSS feed of this site to automatically receive a notification."
+msgstr ""
+
+#: template/faq.html.j2:49
+msgid "Is the code free?"
msgstr ""
-#: template/faq.html.j2:37
+#: template/faq.html.j2:51
msgid ""
-"A: Right now, this is expected and a known cause for high latency in "
-"GNUnet. We have started a major rewrite to address this and other "
-"problems, but until the Transport Next Generation (TNG) is ready, these "
-"warnings are expected."
+"A: GNUnet is free software, available under the <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
msgstr ""
-#: template/faq.html.j2:46
+#: template/faq.html.j2:58
+msgid "Are there any known bugs?"
+msgstr ""
+
+#: template/faq.html.j2:60
+msgid ""
+"A: We track the list of currently known bugs in the <a href=\"https://bugs.";
+"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
+"directly to developers or the developer mailing list. This is discouraged "
+"since developers often do not have the time to feed these bugs back into the "
+"Mantis database. Please report bugs directly to the bug tracking system. If "
+"you believe a bug is sensitive, you can set its view status to private (this "
+"should be the exception)."
+msgstr ""
+
+#: template/faq.html.j2:73 template/faq.html.j2:193
msgid "Is there a graphical user interface?"
msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:75
msgid ""
"A: gnunet-gtk is a separate download. The package contains various GTK+ "
"based graphical interfaces, including a graphical tool for configuration."
msgstr ""
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr ""
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called ""
+"proof-of-work" which is used to convince the network that your peer is "
+"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
+"on the network size estimator). The calculation is expected to take a few "
+"days, depending on how fast your CPU is. If the CPU load is creating a "
+"problem for you, you can set the value "WORKDELAY" in the ""
+"nse" section of your configuration file to a higher value. The default "
+"is "5 ms"."
+msgstr ""
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr ""
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
+"connections and, with the Tor Browser Bundle, for the Web in particular. "
+"GNUnet does not really have one focus; our theme is secure decentralized "
+"networking, but that is too broad to be called a focus."
+msgstr ""
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr ""
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost no "
+"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
+"using onion (or garlic) routing as the basis for various (anonymized) "
+"applications. I2P is largely used via a Web frontend."
+msgstr ""
+
+#: template/faq.html.j2:124
+msgid "Is GNUnet ready for use on production systems?"
+msgstr ""
+
+#: template/faq.html.j2:126
+msgid ""
+"A: GNUnet is still undergoing major development. It is largely not yet ready "
+"for usage beyond developers. Your mileage will vary depending on the "
+"functionality you use, but you will always likely run into issues with our "
+"current low-level transport system. We are currently in the process of "
+"rewriting it (Project "Transport Next Generation [TNG]")"
+msgstr ""
+
+#: template/faq.html.j2:136
+msgid "Is GNUnet build using distributed ledger technologies?"
+msgstr ""
+
+#: template/faq.html.j2:138
+msgid ""
+"A: No. GNUnet is a new network protocol stack for building secure, "
+"distributed, and privacy-preserving applications. While a ledger could be "
+"built using GNUnet, we currently have no plans in doing so."
+msgstr ""
+
+#: template/faq.html.j2:151
+msgid "What can I do with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
+"do more than just one thing. Naturally, the implementation and documentation "
+"of some of the features that exist are more advanced than others."
+msgstr ""
+
+#: template/faq.html.j2:160
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
+"decentralized and censorship-resistant replacement for DNS and a mechanism "
+"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
+msgstr ""
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We "
+"recommend that you use Tor for anonymous surfing."
+msgstr ""
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr ""
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+
+#: template/faq.html.j2:195
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the "
+"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
+"that integrates most of the other GUIs in one window. One exception is "
+"gnunet-setup, which must still be run separately at this time (as setup "
+"requires the peer to be stopped)."
+msgstr ""
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr ""
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
+"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
+"FreeBSD and macOS. We have reports of working versions on many other GNU/"
+"Linux distributions; in the past we had reports of working versions on "
+"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
+"so if you cannot get GNUnet to work on those systems please let us know."
+msgstr ""
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr ""
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a default "
+"configuration of top-level domains. The governance of this default "
+"configuration is not yet established. In any case, the user will be able to "
+"modify this configuration at will. We expect normal users to have no need to "
+"edit their own GNS zone(s) unless they host services themselves."
+msgstr ""
+
+#: template/faq.html.j2:241
+msgid "Where is the per-user GNS database kept?"
+msgstr ""
+
+#: template/faq.html.j2:243
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet peer. "
+"Now, a user may run multiple GNUnet peers, in which case the database could "
+"be kept at each peer (however, we don't have code for convenient "
+"replication). Similarly, multiple GNUnet peers can share one instance of the "
+"database --- the "gnunet-service-namestore" can be accessed from "
+"remote (via TCP). The actual data can be stored in a Postgres database, for "
+"which various replication options are again applicable. Ultimately, there "
+"are many options for how users can store (and secure) their GNS database."
+msgstr ""
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases "
+"will only grow to a few tens of thousands of entries, small enough to fit "
+"even on mobile devices."
+msgstr ""
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr ""
+
+#: template/faq.html.j2:272
+msgid ""
+"A: We believe so, as there is no entity that any government could force to "
+"change the mapping for a name except for each individual user (and then the "
+"changes would only apply to the names that this user is the authority for). "
+"So if everyone used GNS, the only practical attack of a government would be "
+"to force the operator of a server to change the GNS records for his server "
+"to point elsewhere. However, if the owner of the private key for a zone is "
+"unavailable for enforcement, the respective zone cannot be changed and any "
+"other zone delegating to this zone will achieve proper resolution."
+msgstr ""
+
+#: template/faq.html.j2:286
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr ""
+
+#: template/faq.html.j2:288
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
+"there are still registrars that determine who owns a name. <br><br> With "
+"GNS, we decentralize the database and also decentralize the responsibility "
+"for naming: each user runs his own personal root zone and is thus in "
+"complete control of the names he uses. GNS also has many additional features "
+"(to keep names short and enable migration) which don't even make sense in "
+"the context of CoDoNS."
+msgstr ""
+
+#: template/faq.html.j2:304
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr ""
+
+#: template/faq.html.j2:306
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared via "
+"delegation, and thus mappings will only change if the user responsible for "
+"the name (the authority) manually changes the record."
+msgstr ""
+
+#: template/faq.html.j2:320
+msgid "What is the difference between GNS and ODDNS?"
+msgstr ""
+
+#: template/faq.html.j2:322
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+
+#: template/faq.html.j2:333
+msgid "What is the difference between GNS and Namecoin?"
+msgstr ""
+
+#: template/faq.html.j2:340
+msgid "What is the difference between GNS and Handshake?"
+msgstr ""
+
+#: template/faq.html.j2:346
+msgid "What is the difference between GNS and ENS?"
+msgstr ""
+
+#: template/faq.html.j2:352
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr ""
+
+#: template/faq.html.j2:354
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks on "
+"DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from "
+"the DNS hierarchy."
+msgstr ""
+
+#: template/faq.html.j2:367
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the style "
+"of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:369
+msgid ""
+"A: For security, it is well known that an initial trust path between the two "
+"parties must exist. However, for applications where this is not required, "
+"weaker mechanisms can be used. For example, we have implemented a first-come-"
+"first-served (FCFS) authority which allows arbitrary users to register "
+"arbitrary names. The key of this authority is included with every GNUnet "
+"installation. Thus, any name registered with FCFS is in fact global and "
+"requires no further introduction. However, the security of these names "
+"depends entirely on the trustworthiness of the FCFS authority. The authority "
+"can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:384
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name in "
+"GNS?"
+msgstr ""
+
+#: template/faq.html.j2:386
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "legitimate" "
+"domain owner. Any user can claim any name (as his preferred name or ""
+"pseudonym") in his NICK record. Similarly, all other users can choose "
+"to ignore this preference and use a name of their choice (or even assign no "
+"name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:397
+msgid ""
+"Did you consider the privacy implications of making your personal GNS zone "
+"visible?"
+msgstr ""
+
+#: template/faq.html.j2:399
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not set. "
+"Thus, users have full control over what information about their zones is "
+"made public."
+msgstr ""
+
+#: template/faq.html.j2:409
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:411
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary because "
+"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
+"of virtual hosting. However, LEHOs are also useful to help with X.509 "
+"certificate validation (as they specify for which legacy hostname the "
+"certificate should be valid). Also, even with IPv6 fully deployed and ""
+"infinite" IP addresses being available, we're not sure that virtual "
+"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
+"become commonplace, GNS should work with today's networks."
+msgstr ""
+
+#: template/faq.html.j2:425
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:427
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. As "
+"trust relationships evolve, mappings would change their meaning as they "
+"cross each others thresholds. We decided that the resulting unpredictability "
+"of the resolution process was not acceptable. Furthermore, trust and "
+"consensus might be easy to manipulate by adversaries."
+msgstr ""
+
+#: template/faq.html.j2:438
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:440
+msgid ""
+"A: The owner of a private key can create a revocation message. This one can "
+"then be flooded throughout the overlay network, creating a copy at all "
+"peers. Before using a public key, peers check if that key has been revoked. "
+"All names that involve delegation via a revoked zone will then fail to "
+"resolve. Peers always automatically check for the existence of a revocation "
+"message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:452
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:454
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:468
+msgid ""
+"How can a GNS zone maintain several name servers, e.g. for load balancing?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share "
+"the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:483
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names are "
+"not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on your "
+"application, HTTPS may not be worth the cost. However, for users that are "
+"experiencing censorship (or are concerned about it), giving up globally "
+"unique names may very well be worth the cost. After all, what is a ""
+"globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:499
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:501
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by IANA/ICANN. "
+"This centralization creates vulnerabilities. For example, the US government "
+"was able to reassign the management of the country-TLDs of Afganistan and "
+"Iraq during the wars at the beginning of the 21st century."
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:514
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
+"so blocking a particular IP address causes much more collateral damage than "
+"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
+"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
+"censorship resistant naming system. Accessing Tor's ".onion" "
+"namespace currently requires users to use unmemorable cryptographic "
+"identifiers. With nicer names, Tor and tor2web-like services would be even "
+"easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:533
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:535
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can use "
+"GNS to perform name resolution as well as any normal user. Naturally, while "
+"we typically expect normal users to install custom software for name "
+"resolution, this is unlikely to work for search engines today. However, the "
+"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
+"they can still index GNS resources. However, as using DNS2GNS gateways "
+"breaks the cryptographic chain of trust, legacy search engines will "
+"obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:549
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:551
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was designed "
+"to interoperate with DNS as much as possible, and to also work as much as "
+"possible with the existing Web infrastructure. UIA is not at all concerned "
+"about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:564
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:566
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you know "
+"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
+"and can thus decide how much you trust the result. Naturally, the trusted-"
+"computing base (TCB) can become arbitrarily large this way --- however, "
+"given the name length restriction, for an individual name it is always less "
+"than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:578
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part of "
+"the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:580
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects the "
+""_Service._Proto" syntax, converts "Service" to the "
+"corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when the "
+"result is presented, GNS looks for the GNS-specific "BOX" record "
+"type. A BOX record is a record that contains another record (such as SRV or "
+"TLSA records) and adds a service and protocol number (and the original boxed "
+"record type) to it."
+msgstr ""
+
+#: template/faq.html.j2:596
+msgid ""
+"I receive many "WARNING Calculated flow delay for X at Y for Z". "
+"Should I worry?"
+msgstr ""
+
+#: template/faq.html.j2:598
+msgid ""
+"A: Right now, this is expected and a known cause for high latency in GNUnet. "
+"We have started a major rewrite to address this and other problems, but "
+"until the Transport Next Generation (TNG) is ready, these warnings are "
+"expected."
+msgstr ""
+
+#: template/faq.html.j2:607
+msgid "Error opening `/dev/net/tun': No such file or directory?"
+msgstr ""
+
+#: template/faq.html.j2:609
+msgid ""
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:621
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
+"dns)?"
+msgstr ""
+
+#: template/faq.html.j2:623
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check if "
+"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:635
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:637
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if "
+"your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:645
+msgid ""
+"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:647
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if you "
+"compiled GNUnet the normal way and/or used a binary package, that is highly "
+"unlikely. The more common cause is that you installed GNUnet to a directory "
+"that your linker does not search. There are several ways to fix this that "
+"are described below. If you are 'root' and you installed to a system folder "
+"(such as /usr/local), you want to add the libraries to the system-wide "
+"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
+"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
+"similar path, you obviously have to change \"/usr/local\" accordingly. If "
+"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
+"$USER/\", then you can explicitly tell your linker to search a particular "
+"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
+"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
+"you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:673
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the \"$\") "
+"to your .bashrc or .profile file. You will have to logout and login again to "
+"have this new profile be applied to all shells (including your desktop "
+"environment)."
+msgstr ""
+
+#: template/faq.html.j2:680
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:682
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
+"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
+"always refer to harmless events that require no action. For example, GNUnet "
+"may use an INFO message to indicate that it is currently performing an "
+"expensive operation that will take some time. GNUnet will also use INFO "
+"messages to display information about important configuration values."
+msgstr ""
+
+#: template/faq.html.j2:698
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:700
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
+"P2P networks, GNUnet was designed with security in mind as the highest "
+"priority. We intend on producing a network with comprehensive security "
+"features. Many other P2P networks are open to a wide variety of attacks, and "
+"users have little privacy. GNUnet is also Free Software and thus the source "
+"code is available, so you do not have to worry about being spied upon by the "
+"software. The following table summarises the main differences between GNUnet "
+"and other systems. The information is accurate to the best of our knowledge. "
+"The comparison is difficult since there are sometimes differences between "
+"various implementations of (almost) the same protocol. In general, we pick a "
+"free implementation as the reference implementation since it is possible to "
+"inspect the free code. Also, all of these systems are changing over time and "
+"thus the data below may not be up-to-date. If you find any flaws, please let "
+"us know. Finally, the table is not saying terribly much (it is hard to "
+"compare these systems this briefly), so if you want the real differences, "
+"read the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:814
+msgid ""
+"Another important point of reference are the various anonymous peer-to-peer "
+"networks. Here, there are differences in terms of application domain and how "
+"specifically anonymity is achieved. Anonymous routing is a hard research "
+"topic, so for a superficial comparisson like this one we focus on the "
+"latency. Another important factor is the programming language. Type-safe "
+"languages may offer certain security benefits; however, this may come at the "
+"cost of significant increases in resource consumption which in turn may "
+"reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:827
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:829
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of the "
+"same techniques used to generate reasonable passwords to defend against such "
+"an attack. In any event, we are not trying to hide content; thus, unless the "
+"user is trying to insert information into the network that can only be "
+"shared with a small group of people, there is no real reason to try to "
+"obfuscate the content by choosing a difficult keyword anyway."
+msgstr ""
+
+#: template/faq.html.j2:843
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:845
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all "
+"users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell which "
+"of the peers in the group originated the message. In other words, it should "
+"be difficult to impossible for an adversary to distinguish between the "
+"originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:857
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:859
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
+"its public key) and has a number of addresses it is reachable by (may have "
+"no addresses, for instance when it's behind a NAT). You specify bandwidth "
+"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
+"(how large your on-disk block storage is) . Your node will then proceed to "
+"connect to other nodes, becoming part of the network."
+msgstr ""
+
+#: template/faq.html.j2:874
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:876
+msgid ""
+"A: First, you need to register an account with our weblate system. Please "
+"send an e-mail with the desired target language to translators@gnunet.org or "
+"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
+"sufficient permissions will then grant you access. Naturally, any abuse will "
+"result in the loss of permissions."
+msgstr ""
+
+#: template/faq.html.j2:888
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:890
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly implement. "
+"The best way to actually get a new feature implemented is to do it yourself "
+"--- and to then send us a patch."
+msgstr ""
+
#: template/glossary.html.j2:12
msgid "Ego"
msgstr ""
#: template/glossary.html.j2:14
msgid ""
-"We use the term \"Ego\" to refer to the fact that users in GNUnet can "
-"have multiple unlinkable identities, in the sense of alter egos. The "
-"ability to have more than one identity is crucial, as we may want to keep"
-" our egos for business separate from those we use for political "
-"activities or romance.<br> Egos in GNUnet are technically equivalent to "
-"identities (and the code does not distinguish between them). We simply "
-"sometimes use the term \"ego\" to stress that you can have more than one."
+"We use the term \"Ego\" to refer to the fact that users in GNUnet can have "
+"multiple unlinkable identities, in the sense of alter egos. The ability to "
+"have more than one identity is crucial, as we may want to keep our egos for "
+"business separate from those we use for political activities or romance.<br> "
+"Egos in GNUnet are technically equivalent to identities (and the code does "
+"not distinguish between them). We simply sometimes use the term \"ego\" to "
+"stress that you can have more than one."
msgstr ""
#: template/glossary.html.j2:27
@@ -862,19 +1576,18 @@ msgstr ""
#: template/glossary.html.j2:29
msgid ""
-"In GNUnet users are identified via a public key, and that public key is "
-"then often referred to as the \"Identity\" of the user. However, the "
-"concept is not as draconian as it often is in real life where many are "
-"forced to have one name, one passport and one unique identification "
-"number. <br> As long as identities in GNUnet are simply public keys, "
-"users are free to create any number of identities, and we call those egos"
-" to emphasize the difference. Even though users can create such egos "
-"freely, it is possible to have an ego certified by some certification "
-"authority, resulting in something that more closely resembles the "
-"traditional concept of an identity.<br> For example, a university may "
-"certify the identities of its students such that they can prove that they"
-" are studying. Students may keep their (certified) student identity "
-"separate from other egos that they use for other activities in life."
+"In GNUnet users are identified via a public key, and that public key is then "
+"often referred to as the \"Identity\" of the user. However, the concept is "
+"not as draconian as it often is in real life where many are forced to have "
+"one name, one passport and one unique identification number. <br> As long as "
+"identities in GNUnet are simply public keys, users are free to create any "
+"number of identities, and we call those egos to emphasize the difference. "
+"Even though users can create such egos freely, it is possible to have an ego "
+"certified by some certification authority, resulting in something that more "
+"closely resembles the traditional concept of an identity.<br> For example, a "
+"university may certify the identities of its students such that they can "
+"prove that they are studying. Students may keep their (certified) student "
+"identity separate from other egos that they use for other activities in life."
msgstr ""
#: template/glossary.html.j2:50
@@ -886,10 +1599,10 @@ msgid ""
"A pseudonym is an ego that is specifically intended to not be linked to "
"one's real name. GNUnet users can create many egos, and thus also many "
"pseudonyms. <br> Repeated uses of the same pseudonym are linkable by "
-"definition, as they involve the same public key. Anonymity requires the "
-"use of either the special \"anonymous\" pseudonym (for GNUnet, this is "
-"the neutral element on the elliptic curve) or a throw-away pseudonym that"
-" is only used once."
+"definition, as they involve the same public key. Anonymity requires the use "
+"of either the special \"anonymous\" pseudonym (for GNUnet, this is the "
+"neutral element on the elliptic curve) or a throw-away pseudonym that is "
+"only used once."
msgstr ""
#: template/glossary.html.j2:71
@@ -898,15 +1611,15 @@ msgstr ""
#: template/glossary.html.j2:73
msgid ""
-"The GNU Name System allows every ego (or identity) to securely and "
-"privately associate any number of label-value pairs with an ego. The "
-"values are called record sets following the terminology of the Domain "
-"Name System (DNS). The mapping of labels to record sets for a given ego "
-"is called a namespace. <br> If records are made public and thus "
-"published, it is possible for other users to lookup the record given the "
-"ego's public key and the label. Here, not only the label can thus act as "
-"a passphrase but also the public key -- which despite its name may not be"
-" public knowledge and is never disclosed by the GNS protocol itself."
+"The GNU Name System allows every ego (or identity) to securely and privately "
+"associate any number of label-value pairs with an ego. The values are called "
+"record sets following the terminology of the Domain Name System (DNS). The "
+"mapping of labels to record sets for a given ego is called a namespace. <br> "
+"If records are made public and thus published, it is possible for other "
+"users to lookup the record given the ego's public key and the label. Here, "
+"not only the label can thus act as a passphrase but also the public key -- "
+"which despite its name may not be public knowledge and is never disclosed by "
+"the GNS protocol itself."
msgstr ""
#: template/glossary.html.j2:89
@@ -915,17 +1628,17 @@ msgstr ""
#: template/glossary.html.j2:91
msgid ""
-"A \"peer\" is an instance of GNUnet with its own per-instance public key "
-"and network addresses. Technically, it is possible to run multiple peers "
-"on the same host, but this only makes sense for testing. <br> By design "
-"GNUnet supports multiple users to share the same peer, just as UNIX is a "
-"multi-user system. A \"peer\" typically consists of a set of foundational"
-" GNUnet services running as the \"gnunet\" user and allowing all users in"
-" the \"gnunet\" group to utilize the API. On multi-user systems, "
-"additional \"personalized\" services may be required per user. <br> While"
-" peers are also identified by public keys, these public keys are "
-"completely unrelated to egos or identities. Namespaces cannot be "
-"associated with a peer, only with egos."
+"A \"peer\" is an instance of GNUnet with its own per-instance public key and "
+"network addresses. Technically, it is possible to run multiple peers on the "
+"same host, but this only makes sense for testing. <br> By design GNUnet "
+"supports multiple users to share the same peer, just as UNIX is a multi-user "
+"system. A \"peer\" typically consists of a set of foundational GNUnet "
+"services running as the \"gnunet\" user and allowing all users in the "
+"\"gnunet\" group to utilize the API. On multi-user systems, additional "
+"\"personalized\" services may be required per user. <br> While peers are "
+"also identified by public keys, these public keys are completely unrelated "
+"to egos or identities. Namespaces cannot be associated with a peer, only "
+"with egos."
msgstr ""
#: template/gns.html.j2:13 template/gnurl.html.j2:60
@@ -935,28 +1648,24 @@ msgstr ""
#: template/gns.html.j2:15
msgid ""
"The Domain Name System today enables traffic amplification attacks, "
-"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive "
-"cyber war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as "
-"DoT, DoH, DNSSEC, DPRIVE and the like will not fix this. This is why we "
-"built the GNU Name System (GNS), a secure, decentralized name system "
-"built on top of GNUnet."
+"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive cyber "
+"war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as DoT, DoH, "
+"DNSSEC, DPRIVE and the like will not fix this. This is why we built the GNU "
+"Name System (GNS), a secure, decentralized name system built on top of "
+"GNUnet."
msgstr ""
#: template/gns.html.j2:28
msgid "Overview"
msgstr ""
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
-
#: template/gns.html.j2:39
msgid ""
"The GNU Name System (GNS) is secure and decentralized naming system. It "
-"allows its users to register names as top-level domains (TLDs) and "
-"resolve other namespaces within their TLDs. <br/> GNS is designed to "
-"provide: <ul> <li>Censorship resistance</li> <li>Query privacy</li> "
-"<li>Secure name resolution</li> <li>Compatibility with DNS</li>"
+"allows its users to register names as top-level domains (TLDs) and resolve "
+"other namespaces within their TLDs. <br/> GNS is designed to provide: <ul> "
+"<li>Censorship resistance</li> <li>Query privacy</li> <li>Secure name "
+"resolution</li> <li>Compatibility with DNS</li>"
msgstr ""
#: template/gns.html.j2:52
@@ -965,23 +1674,23 @@ msgstr ""
#: template/gnurl.html.j2:21
msgid ""
-"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support "
-"only HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend "
-"(GnuTLS) to ensure a small footprint and uniform experience for "
-"developers regardless of how libcurl was compiled."
+"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support only "
+"HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend (GnuTLS) to "
+"ensure a small footprint and uniform experience for developers regardless of "
+"how libcurl was compiled."
msgstr ""
#: template/gnurl.html.j2:30
msgid ""
-"Our main usecase is for GNUnet and Taler, but it might be usable for "
-"others, hence we're releasing the code to the general public."
+"Our main usecase is for GNUnet and Taler, but it might be usable for others, "
+"hence we're releasing the code to the general public."
msgstr ""
#: template/gnurl.html.j2:37
msgid ""
"libgnurl is released under the same license as libcurl. Please read the "
-"README for instructions, as you must supply the correct options to "
-"configure to get a proper build of libgnurl."
+"README for instructions, as you must supply the correct options to configure "
+"to get a proper build of libgnurl."
msgstr ""
#: template/gnurl.html.j2:48
@@ -990,58 +1699,55 @@ msgstr ""
#: template/gnurl.html.j2:50
msgid ""
-"Large parts of the following 6 paragraphs are old and need to be "
-"rewritten."
+"Large parts of the following 6 paragraphs are old and need to be rewritten."
msgstr ""
#: template/gnurl.html.j2:62
msgid ""
-"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, "
-"but other variants are used by some distributions. Supporting other "
-"crypto backends would again expose us to a wider array of security "
-"issues, may create licensing issues and most importantly introduce new "
-"bugs as some crypto backends are known to introduce subtle runtime "
-"issues. While it is possible to have two versions of libcurl installed on"
-" the same system, this is error-prone, especially as if we are linked "
-"against the wrong version, the bugs that arise might be rather subtle."
+"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, but "
+"other variants are used by some distributions. Supporting other crypto "
+"backends would again expose us to a wider array of security issues, may "
+"create licensing issues and most importantly introduce new bugs as some "
+"crypto backends are known to introduce subtle runtime issues. While it is "
+"possible to have two versions of libcurl installed on the same system, this "
+"is error-prone, especially as if we are linked against the wrong version, "
+"the bugs that arise might be rather subtle."
msgstr ""
#: template/gnurl.html.j2:75
msgid ""
-"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, "
-"it would anyway be necessary to recompile cURL for GNUnet. But what "
-"happens if one links cURL against this version of GnuTLS? Well, first one"
-" would install GnuTLS by hand in the system. Then, we build cURL. cURL "
-"will build against it just fine, but the linker will eventually complain "
-"bitterly. The reason is that cURL also links against a bunch of other "
-"system libraries (gssapi, ldap, ssh2, rtmp, krb5, sasl2, see discussion "
-"on obscure protocols above), which --- as they are part of the "
-"distribution --- were linked against an older version of GnuTLS. As a "
-"result, the same binary would be linked against two different versions of"
-" GnuTLS. That is typically a recipe for disaster. Thus, in order to avoid"
-" updating a dozen system libraries (and having two versions of those "
-"installed), it is necessary to disable all of those cURL features that "
-"GNUnet does not use, and there are many of those. For GNUnet, the more "
-"obscure protocols supported by cURL are close to dead code --- mostly "
-"harmless, but not useful. However, as some application may use one of "
-"those features, distributions are typically forced to enable all of those"
-" features, and thus including security issues that might arise from that "
-"code."
+"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, it "
+"would anyway be necessary to recompile cURL for GNUnet. But what happens if "
+"one links cURL against this version of GnuTLS? Well, first one would install "
+"GnuTLS by hand in the system. Then, we build cURL. cURL will build against "
+"it just fine, but the linker will eventually complain bitterly. The reason "
+"is that cURL also links against a bunch of other system libraries (gssapi, "
+"ldap, ssh2, rtmp, krb5, sasl2, see discussion on obscure protocols above), "
+"which --- as they are part of the distribution --- were linked against an "
+"older version of GnuTLS. As a result, the same binary would be linked "
+"against two different versions of GnuTLS. That is typically a recipe for "
+"disaster. Thus, in order to avoid updating a dozen system libraries (and "
+"having two versions of those installed), it is necessary to disable all of "
+"those cURL features that GNUnet does not use, and there are many of those. "
+"For GNUnet, the more obscure protocols supported by cURL are close to dead "
+"code --- mostly harmless, but not useful. However, as some application may "
+"use one of those features, distributions are typically forced to enable all "
+"of those features, and thus including security issues that might arise from "
+"that code."
msgstr ""
#: template/gnurl.html.j2:99
msgid ""
-"So to use a modern version of GnuTLS, a sane approach is to disable all "
-"of the \"optional\" features of cURL that drag in system libraries that "
-"link against the older GnuTLS. That works, except that one should then "
-"NEVER install that version of libcurl in say /usr or /usr/local, as that "
-"may break other parts of the system that might depend on these features "
-"that we just disabled. Libtool versioning doesn't help here, as it is not"
-" intended to deal with libraries that have optional features. Naturally, "
-"installing cURL somewhere else is also problematic, as we now need to be "
-"really careful that the linker will link GNUnet against the right "
-"version. Note that none of this can really be trivially fixed by the cURL"
-" developers."
+"So to use a modern version of GnuTLS, a sane approach is to disable all of "
+"the \"optional\" features of cURL that drag in system libraries that link "
+"against the older GnuTLS. That works, except that one should then NEVER "
+"install that version of libcurl in say /usr or /usr/local, as that may break "
+"other parts of the system that might depend on these features that we just "
+"disabled. Libtool versioning doesn't help here, as it is not intended to "
+"deal with libraries that have optional features. Naturally, installing cURL "
+"somewhere else is also problematic, as we now need to be really careful that "
+"the linker will link GNUnet against the right version. Note that none of "
+"this can really be trivially fixed by the cURL developers."
msgstr ""
#: template/gnurl.html.j2:118
@@ -1052,19 +1758,19 @@ msgstr ""
#, python-format
msgid ""
"How does forking fix it? Easy. First, we can get rid of all of the "
-"compatibility issues --- if you use libgnurl, you state that you "
-"don't need anything but HTTP/HTTPS. Those applications that need "
-"more, should stick with the original cURL. Those that do not, can choose "
-"to move to something simpler. As the library gets a new name, we do not "
-"have to worry about tons of packages breaking as soon as one rebuilds it."
-" So renaming itself and saying that \"libgnurl = libcurl with only "
-"HTTP/HTTPS support and GnuTLS\" fixes 99%% of the problems that darkened "
-"my mood. Note that this pretty much CANNOT be done without a fork, as "
-"renaming is an essential part of the fix. Now, there might be creative "
-"solutions to achieve the same thing within the standard cURL build "
-"system, but this was deemed to be too much work when gnurl was originally"
-" started. The changes libgnurl makes to curl are miniscule and can easily"
-" be applied again and again whenever libcurl makes a new release."
+"compatibility issues --- if you use libgnurl, you state that you don't "
+"need anything but HTTP/HTTPS. Those applications that need more, should "
+"stick with the original cURL. Those that do not, can choose to move to "
+"something simpler. As the library gets a new name, we do not have to worry "
+"about tons of packages breaking as soon as one rebuilds it. So renaming "
+"itself and saying that \"libgnurl = libcurl with only HTTP/HTTPS support and "
+"GnuTLS\" fixes 99%% of the problems that darkened my mood. Note that this "
+"pretty much CANNOT be done without a fork, as renaming is an essential part "
+"of the fix. Now, there might be creative solutions to achieve the same thing "
+"within the standard cURL build system, but this was deemed to be too much "
+"work when gnurl was originally started. The changes libgnurl makes to curl "
+"are miniscule and can easily be applied again and again whenever libcurl "
+"makes a new release."
msgstr ""
#: template/gnurl.html.j2:142
@@ -1073,14 +1779,13 @@ msgstr ""
#: template/gnurl.html.j2:144
msgid ""
-"Projects that use cURL only for HTTP/HTTPS and that would work with "
-"GnuTLS should be able to switch to libgnurl by changing \"-lcurl\" to "
-"\"-lgnurl\". That's it. No changes to the source code should be "
-"required, as libgnurl strives for bug-for-bug compatibility with the "
-"HTTP/HTTPS/GnuTLS subset of cURL. We might add new features relating to "
-"this core subset if they are proposed, but so far we have kept our "
-"changes minimal and no additions to the original curl source have been "
-"written."
+"Projects that use cURL only for HTTP/HTTPS and that would work with GnuTLS "
+"should be able to switch to libgnurl by changing \"-lcurl\" to \"-lgnurl\". "
+"That's it. No changes to the source code should be required, as libgnurl "
+"strives for bug-for-bug compatibility with the HTTP/HTTPS/GnuTLS subset of "
+"cURL. We might add new features relating to this core subset if they are "
+"proposed, but so far we have kept our changes minimal and no additions to "
+"the original curl source have been written."
msgstr ""
#: template/gnurl.html.j2:161
@@ -1089,15 +1794,15 @@ msgstr ""
#: template/gnurl.html.j2:163
msgid ""
-"libgnurl and gnurl are not intended to be used as a replacement for curl "
-"for users: <br> This does not mean there is no confidence in the work "
-"done with gnurl, it means that tools which expect curl or libcurl will "
-"not make use of a different named binary and library. If you know what "
-"you are doing, you should be able to use gnurl as part of your tooling in"
-" place of curl. We do not recommend to do so however, as the only usage "
-"it is tested for <em>so far</em> is as part of Taler's and "
-"GNunet's build-system. <br> Since no conflicts in filenames occur you"
-" are not expected to remove curl to make use of gnurl and viceversa."
+"libgnurl and gnurl are not intended to be used as a replacement for curl for "
+"users: <br> This does not mean there is no confidence in the work done with "
+"gnurl, it means that tools which expect curl or libcurl will not make use of "
+"a different named binary and library. If you know what you are doing, you "
+"should be able to use gnurl as part of your tooling in place of curl. We do "
+"not recommend to do so however, as the only usage it is tested for <em>so "
+"far</em> is as part of Taler's and GNunet's build-system. <br> Since "
+"no conflicts in filenames occur you are not expected to remove curl to make "
+"use of gnurl and viceversa."
msgstr ""
#: template/gnurl.html.j2:188
@@ -1110,16 +1815,15 @@ msgstr ""
#: template/gnurl.html.j2:211
msgid ""
-"Releases are published on <a "
-"href=\"https://ftpmirror.gnu.org/gnu/gnunet/\";>ftpmirror.gnu.org/gnu/gnunet</a>."
-" gnurl is available from within a variety of distributions and package "
-"managers. Some Package Managers which include gnurl are: <a "
-"href=\"https://www.gnu.org/software/guix/\";>GNU Guix</a> (available as "
-"\"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> through the "
-"collaborative ebuild collection <a href=\"https://git.gnunet.org";
-"/youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a "
-"href=\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a "
-"href=\"https://pkgsrc.org\";>pkgsrc</a>."
+"Releases are published on <a href=\"https://ftpmirror.gnu.org/gnu/gnunet/";
+"\">ftpmirror.gnu.org/gnu/gnunet</a>. gnurl is available from within a "
+"variety of distributions and package managers. Some Package Managers which "
+"include gnurl are: <a href=\"https://www.gnu.org/software/guix/\";>GNU Guix</"
+"a> (available as \"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> "
+"through the collaborative ebuild collection <a href=\"https://git.gnunet.org/";
+"youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a href="
+"\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a href=\"https://";
+"pkgsrc.org\">pkgsrc</a>."
msgstr ""
#: template/gnurl.html.j2:228
@@ -1128,17 +1832,17 @@ msgstr ""
#: template/gnurl.html.j2:230
msgid ""
-"We suggest to closely follow release announcements, as they might "
-"indicate changes in how gnurl is to be build. <br> If your package "
-"manager provides a binary build or build instructions to build gnurl from"
-" source automated and integrated with your environment, we strongly "
-"suggest to use this binary build. <br> There are two ways to build gnurl."
-" The first one builds from the most recent git tag, the second one uses "
-"the distributed tarball. Distributors generally are supposed to build "
-"from the tarball, but we describe both methods here. Both methods are "
-"written with a NetBSD 9 userland in mind, substitute tools as necessary. "
-"<br> You should <b>avoid</b> building gnurl from the tip of the default "
-"git branch, as only tags are considered to be stable and approved builds."
+"We suggest to closely follow release announcements, as they might indicate "
+"changes in how gnurl is to be build. <br> If your package manager provides a "
+"binary build or build instructions to build gnurl from source automated and "
+"integrated with your environment, we strongly suggest to use this binary "
+"build. <br> There are two ways to build gnurl. The first one builds from the "
+"most recent git tag, the second one uses the distributed tarball. "
+"Distributors generally are supposed to build from the tarball, but we "
+"describe both methods here. Both methods are written with a NetBSD 9 "
+"userland in mind, substitute tools as necessary. <br> You should <b>avoid</"
+"b> building gnurl from the tip of the default git branch, as only tags are "
+"considered to be stable and approved builds."
msgstr ""
#: template/gnurl.html.j2:251
@@ -1147,8 +1851,8 @@ msgstr ""
#: template/gnurl.html.j2:253
msgid ""
-"If you want to verify the signature, install an OpenPGP compatible tool "
-"such as security/gnupgp2 (and set it up). Assuming you use pkgin:"
+"If you want to verify the signature, install an OpenPGP compatible tool such "
+"as security/gnupgp2 (and set it up). Assuming you use pkgin:"
msgstr ""
#: template/gnurl.html.j2:267
@@ -1161,8 +1865,7 @@ msgstr ""
#: template/gnurl.html.j2:276
msgid ""
-"Fetch the release, the signature, the checksum file as well as its "
-"signature:"
+"Fetch the release, the signature, the checksum file as well as its signature:"
msgstr ""
#: template/gnurl.html.j2:295
@@ -1211,8 +1914,8 @@ msgstr ""
#: template/gnurl.html.j2:371
msgid ""
-"Follow the steps above, but instead of downloading the tarball, clone the"
-" git tag you want to build from."
+"Follow the steps above, but instead of downloading the tarball, clone the "
+"git tag you want to build from."
msgstr ""
#: template/gnurl.html.j2:382
@@ -1221,10 +1924,9 @@ msgstr ""
#: template/gnurl.html.j2:384
msgid ""
-"You can report bugs on our bug tracker: <a "
-"href=\"https://bugs.gnunet.org/\";>bugs.gnunet.org</a>. Alternatively you "
-"can use our bug mailinglist, but we prefer to track bugs on the "
-"bugtracker."
+"You can report bugs on our bug tracker: <a href=\"https://bugs.gnunet.org/";
+"\">bugs.gnunet.org</a>. Alternatively you can use our bug mailinglist, but "
+"we prefer to track bugs on the bugtracker."
msgstr ""
#: template/gnurl.html.j2:395
@@ -1235,10 +1937,9 @@ msgstr ""
msgid ""
"gnurl/libgnurl is looking for a new maintainer. Releases after version "
"7.69.1 and up to version 7.72.0 were signed with the OpenPGP Key "
-"<b>0xD6B570842F7E7F8D</b> (<a "
-"href=\"https://keys.openpgp.org/search?q=6115012DEA3026F62A98A556D6B570842F7E7F8D\";>keys.openpgp.org</a>),"
-" with the key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E"
-" 7F8D</b>."
+"<b>0xD6B570842F7E7F8D</b> (<a href=\"https://keys.openpgp.org/search?";
+"q=6115012DEA3026F62A98A556D6B570842F7E7F8D\">keys.openpgp.org</a>), with the "
+"key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E 7F8D</b>."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:7
@@ -1252,68 +1953,65 @@ msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:18
msgid ""
"In the context of Google Summer of Code 2018, my mentor (Martin "
-"Schanzenbach) and I have worked on creating and extending the REST API of"
-" GNUnet. Currently, we mirrored the functionality of following commands:"
+"Schanzenbach) and I have worked on creating and extending the REST API of "
+"GNUnet. Currently, we mirrored the functionality of following commands:"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:32
msgid ""
-"Additionally, we developed a website with the Javascript framework "
-"Angular 6 and the design framework iotaCSS to use the new REST API. The "
-"REST API of GNUnet is now documented with Sphinx."
+"Additionally, we developed a website with the Javascript framework Angular 6 "
+"and the design framework iotaCSS to use the new REST API. The REST API of "
+"GNUnet is now documented with Sphinx."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:41
msgid ""
-"... when you can use the command line tools? We need to keep in mind, "
-"that everyone has the right to stay secure and private but not everyone "
-"feels comfortable using a terminal. The further developed REST access to "
-"GNUnet APIs in addition to the new web application allows new users to "
-"interact with GNUnet over a well known tool: their browsers. This "
-"addition to the C API and the command line tools may attract new users "
-"and developers."
+"... when you can use the command line tools? We need to keep in mind, that "
+"everyone has the right to stay secure and private but not everyone feels "
+"comfortable using a terminal. The further developed REST access to GNUnet "
+"APIs in addition to the new web application allows new users to interact "
+"with GNUnet over a well known tool: their browsers. This addition to the C "
+"API and the command line tools may attract new users and developers."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:54
msgid ""
"<li> The REST API developed in GNUnet<br> The REST API is already merged "
-"into the gnunet.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet.git/\";>GNUnet Main Git</a>).<br /> "
-"To use the new features, clone the repository and follow the <a "
-"href=\"https://gnunet.org/en/install.html\";>Installation</a> on "
-"gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
-"</li> <li> The Web Application<br> The web application is available under"
-" the gnunet-webui.git repository (<a href=\"https://gnunet.org/git";
-"/gnunet-webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the"
-" newest version of 'node' and 'yarn'. Dependent on your system, you may "
-"need to download newer versions and install them manually and not over "
-"your packet manager. After the installation succeeded, you need to clone "
-"the repository. Then, you need to run \"yarn install\" and \"yarn start\""
-" for testing purposes. To deploy the website (keep in mind, that this "
-"website communicates with another localhost instance) use \"yarn build\" "
-"for building the web application and use the output in the 'dist' "
-"directory. </li> <li> The Documentation<br /> The documentation is "
-"available under the gnunet-rest-api.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet-rest-api.git/\";>GNUnet REST API "
-"Docmentation Git</a>).<br /> Clone the repository and \"make html\". Then"
-" open the 'index.html' under 'build/html/'. </li>"
+"into the gnunet.git repository (<a href=\"https://gnunet.org/git/gnunet.git/";
+"\">GNUnet Main Git</a>).<br /> To use the new features, clone the repository "
+"and follow the <a href=\"https://gnunet.org/en/install.html\";>Installation</"
+"a> on gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
+"</li> <li> The Web Application<br> The web application is available under "
+"the gnunet-webui.git repository (<a href=\"https://gnunet.org/git/gnunet-";
+"webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the newest "
+"version of 'node' and 'yarn'. Dependent on your system, you may need to "
+"download newer versions and install them manually and not over your packet "
+"manager. After the installation succeeded, you need to clone the repository. "
+"Then, you need to run \"yarn install\" and \"yarn start\" for testing "
+"purposes. To deploy the website (keep in mind, that this website "
+"communicates with another localhost instance) use \"yarn build\" for "
+"building the web application and use the output in the 'dist' directory. </"
+"li> <li> The Documentation<br /> The documentation is available under the "
+"gnunet-rest-api.git repository (<a href=\"https://gnunet.org/git/gnunet-rest-";
+"api.git/\">GNUnet REST API Docmentation Git</a>).<br /> Clone the repository "
+"and \"make html\". Then open the 'index.html' under 'build/html/'. </li>"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:91
msgid ""
-"Please, give it a try and contact me, if you find any bugs or "
-"unintentional features. ;)"
+"Please, give it a try and contact me, if you find any bugs or unintentional "
+"features. ;)"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:98
msgid ""
"Right now, the build process of the web application may be a little too "
-"complex for a casual user. We may be able to solve this by using "
-"docker.<br /> Additionally, the web application does not prevent wrong "
-"inputs but responds with error messages. Adding GNUnet Records is "
-"currently only usable for people, who know how a GNS Record looks like. "
-"This can be adapted to each record type.<br /> Last but not least, "
-"additional features, design changes, etc..."
+"complex for a casual user. We may be able to solve this by using docker.<br /"
+"> Additionally, the web application does not prevent wrong inputs but "
+"responds with error messages. Adding GNUnet Records is currently only usable "
+"for people, who know how a GNS Record looks like. This can be adapted to "
+"each record type.<br /> Last but not least, additional features, design "
+"changes, etc..."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:111
@@ -1340,100 +2038,95 @@ msgstr ""
msgid ""
"As a GNU project, GNUnet has participated in the Google Summer of Code "
"(GSoC) for a number of years. This page lists all current, past, and "
-"finished projects. If you want to participate and apply for any of the "
-"ideas for 2020 below or any past project which is not yet finished (or "
-"even your own idea), please contact us either in IRC or mailing list."
+"finished projects. If you want to participate and apply for any of the ideas "
+"for 2020 below or any past project which is not yet finished (or even your "
+"own idea), please contact us either in IRC or mailing list."
msgstr ""
#: template/gsoc.html.j2:34
msgid ""
-"The GNUnet team is currently working on a transport layer rewrite in "
-"order to fix core issues with connectivity. This new component is "
-"currently developed under the name \"TNG\". What is currently known as "
-"\"transport plugins\" will in the TNG be represented as "
-"\"communicators\". Communicators are processes with a well defined API "
-"that allow to connect peers over a specific protocol. The primary "
-"protocol which are already implemented are UNIX sockets, UDP sockets, and"
-" TCP sockets. For a truly resilient network, other connectivity options "
-"such as WiFi mesh, Bluetooth, HTTP(S), QUIC or even more obscure "
-"alternatives such as radio are required. In this project, the goal is to "
-"select, implement and test new communicators. While TNG is not yet ready,"
-" communicators can, by design, be developed and tested against the "
-"current API. We expect that this project can be worked on by multiple "
+"The GNUnet team is currently working on a transport layer rewrite in order "
+"to fix core issues with connectivity. This new component is currently "
+"developed under the name \"TNG\". What is currently known as \"transport "
+"plugins\" will in the TNG be represented as \"communicators\". Communicators "
+"are processes with a well defined API that allow to connect peers over a "
+"specific protocol. The primary protocol which are already implemented are "
+"UNIX sockets, UDP sockets, and TCP sockets. For a truly resilient network, "
+"other connectivity options such as WiFi mesh, Bluetooth, HTTP(S), QUIC or "
+"even more obscure alternatives such as radio are required. In this project, "
+"the goal is to select, implement and test new communicators. While TNG is "
+"not yet ready, communicators can, by design, be developed and tested against "
+"the current API. We expect that this project can be worked on by multiple "
"students as there are a lot of protocols to choose from. The tasks would "
"consist of: <ol> <li>Deciding which communicators to implement.</li> "
-"<li>Test the communicators.</li> <li>Documentation.</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of HTTPS, QUIC, Bluetooth or WiFi.</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Average, but depends on selected protocols. "
-"<br/> <strong>Mentors:</strong> Martin Schanzenbach, t3sserakt"
+"<li>Test the communicators.</li> <li>Documentation.</li> </ol> Advantageous "
+"skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge of HTTPS, QUIC, "
+"Bluetooth or WiFi.</li> </ol> <br/> <strong>Difficulty:</strong> Average, "
+"but depends on selected protocols. <br/> <strong>Mentors:</strong> Martin "
+"Schanzenbach, t3sserakt"
msgstr ""
#: template/gsoc.html.j2:79
msgid ""
-"The REST API currently only supports a single user system. This is an "
-"issue as on multi-user systems, access control must be enfoced on a per-"
-"user basis. In this project, the REST service must be extended to support"
-" user authentication. This includes the correct handling of user context "
-"switches. <ol> <li>Implement user authentication.</li> <li>Test the "
-"access control.</li> <li>Document the changes to the REST API.</li> </ol>"
-" Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of user authentication subsystems on Linux/Unix.</li> <li>REST/HTTP "
-"Authentication methods</li> </ol> <br/> <strong>Difficulty:</strong> "
-"Beginner <br/> <strong>Mentors:</strong> Martin Schanzenbach"
+"The REST API currently only supports a single user system. This is an issue "
+"as on multi-user systems, access control must be enfoced on a per-user "
+"basis. In this project, the REST service must be extended to support user "
+"authentication. This includes the correct handling of user context switches. "
+"<ol> <li>Implement user authentication.</li> <li>Test the access control.</"
+"li> <li>Document the changes to the REST API.</li> </ol> Advantageous skills/"
+"languages/frameworks: <ol> <li>C</li> <li>Knowledge of user authentication "
+"subsystems on Linux/Unix.</li> <li>REST/HTTP Authentication methods</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:111
msgid ""
-"reclaimID is a decentralized identity system build on top of the GNU Name"
-" System. Currently, there is a Webextension which uses the GNUnet <a "
-"href=\"https://rest.gnunet.org\";>REST API</a>. In order to improve "
-"adoption and ease of use, this project aims to include a full GNUnet node"
-" within the Webextention as a fallback. GNUnet can be compiled to Web "
-"Assembly or JavaScript as demonstrated <a "
-"href=\"https://gnunet.io\";>here</a>. The idea is to improve upon this "
-"concept and support more of GNUnet's subsystems. The difficulty of this "
-"project largely depends on the students proficiency with build tools, "
-"emscripten and improvisation skills. There non-exhaustive task list would"
-" be: <ol> <li>Improve existing GNUnet emscripten build to include more "
-"subsystems.</li> <li>Integrate the result into a Webextention.</li> "
+"reclaimID is a decentralized identity system build on top of the GNU Name "
+"System. Currently, there is a Webextension which uses the GNUnet <a href="
+"\"https://rest.gnunet.org\";>REST API</a>. In order to improve adoption and "
+"ease of use, this project aims to include a full GNUnet node within the "
+"Webextention as a fallback. GNUnet can be compiled to Web Assembly or "
+"JavaScript as demonstrated <a href=\"https://gnunet.io\";>here</a>. The idea "
+"is to improve upon this concept and support more of GNUnet's subsystems. The "
+"difficulty of this project largely depends on the students proficiency with "
+"build tools, emscripten and improvisation skills. There non-exhaustive task "
+"list would be: <ol> <li>Improve existing GNUnet emscripten build to include "
+"more subsystems.</li> <li>Integrate the result into a Webextention.</li> "
"<li>Integrate the result into the re:claimID Webextension</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> "
-"<li>emscripten</li> <li>Webextensions</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Challenging <br/> <strong>Mentors:</strong> "
-"Martin Schanzenbach"
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>emscripten</"
+"li> <li>Webextensions</li> </ol> <br/> <strong>Difficulty:</strong> "
+"Challenging <br/> <strong>Mentors:</strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:147
msgid ""
-"Currently, the keys in our statistics database are too verbose. For "
-"example: </p> <p> nse # flood messages received: 13<br/> nse # peers "
-"connected: 4<br/> nse # nodes in the network (estimate): 203<br/> nse # "
-"flood messages started: 5<br/> nse # estimated network diameter: 3<br/> "
-"nse # flood messages transmitted: 10<br/> </p> <p> With such verbose keys"
-" there's no easy way to form compact JSON document or entries for time-"
-"series database. And you can't query single stats without having to "
-"copypaste the line exactly and put in quotes. In short, the goals are "
-"to... <ol> <li>Think of a way how statistics entries can be made "
-"canonical.</li> <li>Implement the change and migrate existing uses.</li> "
-"<li>Document the format(s) and define an appropriate registration "
-"mechanism for identifiers</li> </ol> Relevant bugs: <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> "
-"</ol> <br/> <strong>Difficulty:</strong> Beginner <br/> "
-"<strong>Mentors:</strong> Martin Schanzenbach"
+"Currently, the keys in our statistics database are too verbose. For example: "
+"</p> <p> nse # flood messages received: 13<br/> nse # peers connected: 4<br/"
+"> nse # nodes in the network (estimate): 203<br/> nse # flood messages "
+"started: 5<br/> nse # estimated network diameter: 3<br/> nse # flood "
+"messages transmitted: 10<br/> </p> <p> With such verbose keys there's no "
+"easy way to form compact JSON document or entries for time-series database. "
+"And you can't query single stats without having to copypaste the line "
+"exactly and put in quotes. In short, the goals are to... <ol> <li>Think of a "
+"way how statistics entries can be made canonical.</li> <li>Implement the "
+"change and migrate existing uses.</li> <li>Document the format(s) and define "
+"an appropriate registration mechanism for identifiers</li> </ol> Relevant "
+"bugs: <a href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:187
msgid ""
-"The goal is to either build upon the (outdated) <a "
-"href=\"https://github.com/canndrew/gnunet-rs\";>GNUnet Rust bindings</a> "
-"or to follow the path of <a href=\"GNUnet Go\">https://github.com/bfix";
-"/gnunet-go</a> which tries to reimplement most of the GNUnet stack. The "
-"end result should be an extension template for GNUnet in the form of the "
-"existing <a href=\"https://git.gnunet.org/gnunet-ext.git/\";>C "
-"template</a> which allows to quickly start implementing services and "
-"libraries for GNUnet."
+"The goal is to either build upon the (outdated) <a href=\"https://github.com/";
+"canndrew/gnunet-rs\">GNUnet Rust bindings</a> or to follow the path of <a "
+"href=\"GNUnet Go\">https://github.com/bfix/gnunet-go</a> which tries to "
+"reimplement most of the GNUnet stack. The end result should be an extension "
+"template for GNUnet in the form of the existing <a href=\"https://git.gnunet.";
+"org/gnunet-ext.git/\">C template</a> which allows to quickly start "
+"implementing services and libraries for GNUnet."
msgstr ""
#: template/gsoc.html.j2:198 template/gsoc.html.j2:652
@@ -1458,27 +2151,26 @@ msgstr ""
#: template/gsoc.html.j2:229
msgid ""
-"Includes: Implementation of rudimentary Android compatibility for GNUnet,"
-" in part by porting the GNUnet utils scheduler to act as a thin wrapper "
-"over libuv."
+"Includes: Implementation of rudimentary Android compatibility for GNUnet, in "
+"part by porting the GNUnet utils scheduler to act as a thin wrapper over "
+"libuv."
msgstr ""
#: template/gsoc.html.j2:236
msgid ""
-"<strong>Mentors:</strong> <a href=\"https://www.goebel-";
-"consult.de/\">Hartmut Goebel</a>, Jeff Burdges, Christian Grothoff"
+"<strong>Mentors:</strong> <a href=\"https://www.goebel-consult.de/\";>Hartmut "
+"Goebel</a>, Jeff Burdges, Christian Grothoff"
msgstr ""
#: template/gsoc.html.j2:245
msgid ""
-"There is a push for migrating our CI to Gitlab. The CI should eventually "
-"not just run \"make check\" on various platforms, but also perform tests "
-"with multiple peers running in different VMs with specific network "
-"topologies (i.e. NAT) between them being simulated. The CI should also be"
-" integrated with Gauger for performance regression analysis. Running jobs"
-" only when dependencies have changed and scripting more granular triggers"
-" or ideally automatic dependency discovery (as done by the autotools) is "
-"also important."
+"There is a push for migrating our CI to Gitlab. The CI should eventually not "
+"just run \"make check\" on various platforms, but also perform tests with "
+"multiple peers running in different VMs with specific network topologies (i."
+"e. NAT) between them being simulated. The CI should also be integrated with "
+"Gauger for performance regression analysis. Running jobs only when "
+"dependencies have changed and scripting more granular triggers or ideally "
+"automatic dependency discovery (as done by the autotools) is also important."
msgstr ""
#: template/gsoc.html.j2:257
@@ -1487,19 +2179,18 @@ msgstr ""
#: template/gsoc.html.j2:267
msgid ""
-"One great problem of the current Internet is the lack of "
-"disintermediation. When people want to talk they need a chat service. "
-"When they want to share files they need a file transfer service. Although"
-" GNUnet already possesses quite advanced integration into Linux "
-"networking, a little extra work is needed for existing applications like "
-"irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by"
-" using a GNS hostname like friend.gnu. Once people have added a person to"
-" their GNS they can immediately message, exchange files and suchlike "
-"directly, with nothing but the GNUnet in the middle, using applications "
-"that have been distributed with unix systems ever since the 1980's. We "
-"can produce an OS distribution where these things work out of the box "
-"with the nicknames of people instead of cloud services. For more "
-"information and context, read"
+"One great problem of the current Internet is the lack of disintermediation. "
+"When people want to talk they need a chat service. When they want to share "
+"files they need a file transfer service. Although GNUnet already possesses "
+"quite advanced integration into Linux networking, a little extra work is "
+"needed for existing applications like irc, www, ftp, rsh, nntpd to run over "
+"it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. "
+"Once people have added a person to their GNS they can immediately message, "
+"exchange files and suchlike directly, with nothing but the GNUnet in the "
+"middle, using applications that have been distributed with unix systems ever "
+"since the 1980's. We can produce an OS distribution where these things work "
+"out of the box with the nicknames of people instead of cloud services. For "
+"more information and context, read"
msgstr ""
#: template/gsoc.html.j2:288
@@ -1508,8 +2199,7 @@ msgstr ""
#: template/gsoc.html.j2:296
msgid ""
-"Implement the AnycastExit spec to enable GNUnet clients to connect over "
-"Tor."
+"Implement the AnycastExit spec to enable GNUnet clients to connect over Tor."
msgstr ""
#: template/gsoc.html.j2:302 template/gsoc.html.j2:337
@@ -1520,9 +2210,9 @@ msgstr ""
#: template/gsoc.html.j2:307
msgid ""
"Note: There was a Special TLDs spec to allow Tor to resolve domain names "
-"using GNS over Tor too, but currently that's on hold until folks think "
-"more about how names should be moved around the local system. We're "
-"calling this more collaborative approach NSS2 for now."
+"using GNS over Tor too, but currently that's on hold until folks think more "
+"about how names should be moved around the local system. We're calling this "
+"more collaborative approach NSS2 for now."
msgstr ""
#: template/gsoc.html.j2:316 template/gsoc.html.j2:456
@@ -1532,17 +2222,16 @@ msgstr ""
#: template/gsoc.html.j2:329
msgid ""
-"Improve the Rust implementation of GNUnet utils, possibly including "
-"adding support for asynchronous IO using mio, or perhaps a higher level "
-"asynchronous IO library built upon it, such as rotor, mioco, eventual_io,"
-" or gj."
+"Improve the Rust implementation of GNUnet utils, possibly including adding "
+"support for asynchronous IO using mio, or perhaps a higher level "
+"asynchronous IO library built upon it, such as rotor, mioco, eventual_io, or "
+"gj."
msgstr ""
#: template/gsoc.html.j2:345
msgid ""
-"Implementation of a replacement for PANDA (see Pond) with better "
-"security, and maybe integration with the GNU Name System for key "
-"exchange."
+"Implementation of a replacement for PANDA (see Pond) with better security, "
+"and maybe integration with the GNU Name System for key exchange."
msgstr ""
#: template/gsoc.html.j2:357
@@ -1556,8 +2245,8 @@ msgstr ""
#: template/gsoc.html.j2:370
msgid ""
-"Implement different place types and file sharing by creating a new place "
-"for the shared content."
+"Implement different place types and file sharing by creating a new place for "
+"the shared content."
msgstr ""
#: template/gsoc.html.j2:376
@@ -1566,12 +2255,12 @@ msgstr ""
#: template/gsoc.html.j2:380
msgid ""
-"<ul> <li>File: generic file with comments</li> <li>Image: display an "
-"image with comments referencing a region of the image</li> <li>Sound: "
-"play a sound file with comments referencing a timestamp</li> "
-"<li>Directory/Album: pointers to File / Image / Sound places</li> "
-"<li>Event: with RSVP</li> <li>Survey: ask your social neighborhood "
-"questions in a structured form</li> </ul>"
+"<ul> <li>File: generic file with comments</li> <li>Image: display an image "
+"with comments referencing a region of the image</li> <li>Sound: play a sound "
+"file with comments referencing a timestamp</li> <li>Directory/Album: "
+"pointers to File / Image / Sound places</li> <li>Event: with RSVP</li> "
+"<li>Survey: ask your social neighborhood questions in a structured form</li> "
+"</ul>"
msgstr ""
#: template/gsoc.html.j2:391
@@ -1581,16 +2270,16 @@ msgstr ""
#: template/gsoc.html.j2:395
msgid ""
"<ul> <li>Fork existing channels, reorganize people into new chatrooms or "
-"channels.</li> <li>Share a post (edit and repost something elsewhere, on "
-"a fan page for example).</li> <li>Edit a previously published post + "
-"offer edit history to readers.</li> <li>Control expiry of channel "
-"history.</li> </ul>"
+"channels.</li> <li>Share a post (edit and repost something elsewhere, on a "
+"fan page for example).</li> <li>Edit a previously published post + offer "
+"edit history to readers.</li> <li>Control expiry of channel history.</li> </"
+"ul>"
msgstr ""
#: template/gsoc.html.j2:404
msgid ""
-"See also <a "
-"href=\"http://secushare.org/features\";>http://secushare.org/features</a>"
+"See also <a href=\"http://secushare.org/features\";>http://secushare.org/";
+"features</a>"
msgstr ""
#: template/gsoc.html.j2:409
@@ -1603,20 +2292,19 @@ msgstr ""
#: template/gsoc.html.j2:427
msgid ""
-"Implement aggregation of distributed state from various channels in order"
-" to provide for a powerful social graph API capable of producing social "
-"network profiles, dashboards, a calendar out of upcoming event "
-"invitations (if available), social search functionality and most of all "
-"to make it easy for users to adopt cryptographic identities of their "
-"contacts/friends simply by finding them in the social graph of their "
-"existing contacts (\"This is Linda. You have 11 contacts in common with "
-"her. [ADD]\")."
+"Implement aggregation of distributed state from various channels in order to "
+"provide for a powerful social graph API capable of producing social network "
+"profiles, dashboards, a calendar out of upcoming event invitations (if "
+"available), social search functionality and most of all to make it easy for "
+"users to adopt cryptographic identities of their contacts/friends simply by "
+"finding them in the social graph of their existing contacts (\"This is "
+"Linda. You have 11 contacts in common with her. [ADD]\")."
msgstr ""
#: template/gsoc.html.j2:445
msgid ""
-"Related to <a "
-"href=\"http://secushare.org/rendezvous\";>secushare.org/rendezvous</a>"
+"Related to <a href=\"http://secushare.org/rendezvous\";>secushare.org/"
+"rendezvous</a>"
msgstr ""
#: template/gsoc.html.j2:451 template/gsoc.html.j2:491
@@ -1625,21 +2313,21 @@ msgstr ""
#: template/gsoc.html.j2:468
msgid ""
-"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform "
-"traditional mail clients into secushare user interfaces. </li> <li> Think"
-" of ways to map e-mail addresses to secushare identities. </li> <li> "
-"Encode or translate various e-mail features into secushare equivalents. "
-"</li> <li> Parts of secushare are currently written in Rust, therefore "
-"Rust is preferred for this task but it is not an requirement. </li> </ul>"
+"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform traditional "
+"mail clients into secushare user interfaces. </li> <li> Think of ways to map "
+"e-mail addresses to secushare identities. </li> <li> Encode or translate "
+"various e-mail features into secushare equivalents. </li> <li> Parts of "
+"secushare are currently written in Rust, therefore Rust is preferred for "
+"this task but it is not an requirement. </li> </ul>"
msgstr ""
#: template/gsoc.html.j2:509
msgid ""
"Implementation of the GNUnet auction system described in Chapter 3 of <a "
"href=\"https://grothoff.org/christian/teich2017ms.pdf\";>this thesis</a>. "
-"Specific tasks are adding smart contract creation and round time "
-"enforcement to libbrandt as well as creating the GNUnet auction service, "
-"library and the three user interface programs create, info and join."
+"Specific tasks are adding smart contract creation and round time enforcement "
+"to libbrandt as well as creating the GNUnet auction service, library and the "
+"three user interface programs create, info and join."
msgstr ""
#: template/gsoc.html.j2:521
@@ -1648,9 +2336,9 @@ msgstr ""
#: template/gsoc.html.j2:539
msgid ""
-"Implementation of additional transports to make GNUnet communication more"
-" robust in the presence of problematic networks: GNUnet-over-SMTP, "
-"GNUnet-over-DNS"
+"Implementation of additional transports to make GNUnet communication more "
+"robust in the presence of problematic networks: GNUnet-over-SMTP, GNUnet-"
+"over-DNS"
msgstr ""
#: template/gsoc.html.j2:546 template/gsoc.html.j2:560
@@ -1664,16 +2352,16 @@ msgid ""
msgstr ""
#: template/gsoc.html.j2:568
-msgid "<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff
Burdges"
+msgid ""
+"<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff Burdges"
msgstr ""
#: template/gsoc.html.j2:576
msgid ""
-"Improving libaboss to make computation on shared secrets (including "
-"repeated multiplication) based on <a "
-"href=\"https://dl.acm.org/citation.cfm?doid=62212.62213\";>Ben-Or et "
-"al.</a> if possible. This in particular means moving libaboss to bignums "
-"(gcry_mpi)."
+"Improving libaboss to make computation on shared secrets (including repeated "
+"multiplication) based on <a href=\"https://dl.acm.org/citation.cfm?";
+"doid=62212.62213\">Ben-Or et al.</a> if possible. This in particular means "
+"moving libaboss to bignums (gcry_mpi)."
msgstr ""
#: template/gsoc.html.j2:589
@@ -1685,11 +2373,10 @@ msgstr ""
#: template/gsoc.html.j2:602
msgid ""
"Python 2.7 is reaching its end-of-life, and we want to get rid of the "
-"dependency on Python. The existing gnunet-qr tool is a rather simple "
-"wrapper around python-zbar, which itself wraps libzbar. The goal of this "
-"project is to directly use libzbar to scan QR codes for GNUnet / the GNU "
-"Name System (see also <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
+"dependency on Python. The existing gnunet-qr tool is a rather simple wrapper "
+"around python-zbar, which itself wraps libzbar. The goal of this project is "
+"to directly use libzbar to scan QR codes for GNUnet / the GNU Name System "
+"(see also <a href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
msgstr ""
#: template/gsoc.html.j2:612
@@ -1714,11 +2401,11 @@ msgstr ""
#: template/gsoc.html.j2:642
msgid ""
-"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a "
-"yet to be determined framework such as Angular2. This includes the design"
-" and implementation of not yet existing <a "
-"href=\"http://jsonapi.org/\";>REST APIs</a> that expose the <a "
-"href=\"https://docs.gnunet.org/doxygen/modules.html\";>GNUnet API</a>."
+"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a yet "
+"to be determined framework such as Angular2. This includes the design and "
+"implementation of not yet existing <a href=\"http://jsonapi.org/\";>REST "
+"APIs</a> that expose the <a href=\"https://docs.gnunet.org/doxygen/modules.";
+"html\">GNUnet API</a>."
msgstr ""
#: template/gsoc.html.j2:657
@@ -1727,8 +2414,7 @@ msgstr ""
#: template/gsoc.html.j2:667
msgid ""
-"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet "
-"WebUI</a>"
+"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet WebUI</a>"
msgstr ""
#: template/index.html.j2:8
@@ -1750,25 +2436,24 @@ msgstr ""
#: template/index.html.j2:49
msgid ""
"The conventional Internet is currently like a system of roads with deep "
-"potholes and highwaymen all over the place. Even if you still can use the"
-" roads (e.g. send emails, or browse websites) your vehicle might get "
+"potholes and highwaymen all over the place. Even if you still can use the "
+"roads (e.g. send emails, or browse websites) your vehicle might get "
"hijacked, damaged, or long arms might reach into its back and steal your "
-"items (data) to use it against you and sell it to others - while you "
-"can't even notice the thievery nor accuse and hold the scroungers "
-"accountable. <!-- Proposal from Fabian Gerlach: The conventional Internet"
-" is currently like a system of roads with deep potholes and surveillance "
-"cameras all over the place. Even if you still can use the roads (e.g. "
-"send emails, or browse websites) your vehicle might gets damaged. And the"
-" surveillance cameras will create a movement profile about your life: "
-"They recognize your car license plate, track you everywhere you drive, "
-"and save this information in a central data base. --> The Internet was "
-"not designed with security in mind: protecting against address forgery, "
-"routers learning metadata, or choosing trustworthy third parties is "
-"nontrivial and sometimes impossible. <!-- Proposal from Fabian Gerlach: "
-"The Internet is not designed with security in mind: The network generally"
-" learns too much about users; it has insecure defaults and high "
-"complexity; and it is centralized. That makes it very vulnerable for "
-"multiple attacks massively threatening our freedom. -->"
+"items (data) to use it against you and sell it to others - while you can'"
+"t even notice the thievery nor accuse and hold the scroungers accountable. "
+"<!-- Proposal from Fabian Gerlach: The conventional Internet is currently "
+"like a system of roads with deep potholes and surveillance cameras all over "
+"the place. Even if you still can use the roads (e.g. send emails, or browse "
+"websites) your vehicle might gets damaged. And the surveillance cameras will "
+"create a movement profile about your life: They recognize your car license "
+"plate, track you everywhere you drive, and save this information in a "
+"central data base. --> The Internet was not designed with security in mind: "
+"protecting against address forgery, routers learning metadata, or choosing "
+"trustworthy third parties is nontrivial and sometimes impossible. <!-- "
+"Proposal from Fabian Gerlach: The Internet is not designed with security in "
+"mind: The network generally learns too much about users; it has insecure "
+"defaults and high complexity; and it is centralized. That makes it very "
+"vulnerable for multiple attacks massively threatening our freedom. -->"
msgstr ""
#: template/index.html.j2:94
@@ -1778,10 +2463,10 @@ msgstr ""
#: template/index.html.j2:96
msgid ""
"GNUnet is a network protocol stack for building secure, distributed, and "
-"privacy-preserving applications.<br/> With strong roots in <a "
-"class=\"link\" href=\"https://bib.gnunet.org\";>academic research</a>, our"
-" goal is to replace the <a class=\"link\" href=\"https://secushare.org";
-"/broken-internet\">old insecure Internet</a> protocol stack."
+"privacy-preserving applications.<br/> With strong roots in <a class=\"link\" "
+"href=\"https://bib.gnunet.org\";>academic research</a>, our goal is to "
+"replace the <a class=\"link\" href=\"https://secushare.org/broken-internet";
+"\">old insecure Internet</a> protocol stack."
msgstr ""
#: template/index.html.j2:119
@@ -1792,10 +2477,9 @@ msgstr ""
msgid ""
"Your metadata is just as revealing as the actual content; and it gets "
"exposed on the Internet.<br> Even though transport encryption is "
-"increasingly being deployed on the Internet, it still reveals data that "
-"can threaten democracy: the identities of senders and receivers, the "
-"times, frequency and the volume of communication are all still "
-"revealed.<br>"
+"increasingly being deployed on the Internet, it still reveals data that can "
+"threaten democracy: the identities of senders and receivers, the times, "
+"frequency and the volume of communication are all still revealed.<br>"
msgstr ""
#: template/index.html.j2:150
@@ -1804,15 +2488,13 @@ msgstr ""
#: template/index.html.j2:152
msgid ""
-"It provides <a class=\"link\" "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";> improving "
-"addressing, routing, naming and content distribution</a> in a technically"
-" robust manner - as opposed to ad-hoc designs in place today. <!-- "
-"Proposal from fabian gerlach: GNUnet is built <a "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by "
-"design\"</a> and \"distributed by design\". This improves addressing, "
-"routing, naming and content distribution in a technically robust manner. "
-"-->"
+"It provides <a class=\"link\" href=\"https://www.w3.org/2014/strint/";
+"papers/65.pdf\"> improving addressing, routing, naming and content "
+"distribution</a> in a technically robust manner - as opposed to ad-hoc "
+"designs in place today. <!-- Proposal from fabian gerlach: GNUnet is built "
+"<a href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by design"
+"\"</a> and \"distributed by design\". This improves addressing, routing, "
+"naming and content distribution in a technically robust manner. -->"
msgstr ""
#: template/index.html.j2:177
@@ -1822,9 +2504,9 @@ msgstr ""
#: template/index.html.j2:179
msgid ""
"Today, monitoring increasingly centralized infrastructure, proprietary "
-"implementations, traffic shapers and firewalls restrict all of the <a "
-"class=\"link\" href=\"https://www.gnu.org/philosophy/free-";
-"sw.html\">essential freedoms</a> to various degrees."
+"implementations, traffic shapers and firewalls restrict all of the <a class="
+"\"link\" href=\"https://www.gnu.org/philosophy/free-sw.html\";>essential "
+"freedoms</a> to various degrees."
msgstr ""
#: template/index.html.j2:203
@@ -1833,14 +2515,14 @@ msgstr ""
#: template/index.html.j2:205
msgid ""
-"GNUnet is a self-organizing network and it is <a class=\"link\" "
-"href=\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as"
-" in freedom. GNUnet puts you in control of your data. You determine which"
-" data to share with whom, and you're not pressured to accept "
-"compromises. It gives users freedoms to securely access information "
-"(\"run\" the network), to study all aspects of the network's "
-"operation (\"access the code\"), to distribute information (\"copy\"), as"
-" well as the freedom to deploy new applications (\"modify\")."
+"GNUnet is a self-organizing network and it is <a class=\"link\" href="
+"\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as in "
+"freedom. GNUnet puts you in control of your data. You determine which data "
+"to share with whom, and you're not pressured to accept compromises. It "
+"gives users freedoms to securely access information (\"run\" the network), "
+"to study all aspects of the network's operation (\"access the code\"), "
+"to distribute information (\"copy\"), as well as the freedom to deploy new "
+"applications (\"modify\")."
msgstr ""
#: template/index.html.j2:229
@@ -1849,13 +2531,13 @@ msgstr ""
#: template/index.html.j2:232
msgid ""
-"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every "
-"other distributed or P2P project develops its own library stack, covering"
-" transports, stream muxing, discovery and others. This divides effort and"
-" multiplies bug count. --> Instead of sharing common components and tools"
-" for building P2P systems, every P2P project seems to re-invent the "
-"wheel. <!-- TODO: rework this sentence. --> This heightens the effort and"
-" increases the potential number of vulnerabilities."
+"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every other "
+"distributed or P2P project develops its own library stack, covering "
+"transports, stream muxing, discovery and others. This divides effort and "
+"multiplies bug count. --> Instead of sharing common components and tools for "
+"building P2P systems, every P2P project seems to re-invent the wheel. <!-- "
+"TODO: rework this sentence. --> This heightens the effort and increases the "
+"potential number of vulnerabilities."
msgstr ""
#: template/index.html.j2:264
@@ -1864,10 +2546,10 @@ msgstr ""
#: template/index.html.j2:266
msgid ""
-"It offers a metadata-preserving foundation for your application. It "
-"offers components for addressing, reliable encrypted channels with "
-"advanced routing and resource discovery and naming. Our work is based on "
-"continuous research spanning almost two decades."
+"It offers a metadata-preserving foundation for your application. It offers "
+"components for addressing, reliable encrypted channels with advanced routing "
+"and resource discovery and naming. Our work is based on continuous research "
+"spanning almost two decades."
msgstr ""
#: template/index.html.j2:286
@@ -2009,75 +2691,69 @@ msgstr ""
#: template/install.html.j2:12
msgid ""
-"Notice: GNUnet is still undergoing major development. It is largely "
-"<i>not yet ready</i> for usage beyond developers."
+"Notice: GNUnet is still undergoing major development. It is largely <i>not "
+"yet ready</i> for usage beyond developers."
msgstr ""
#: template/install.html.j2:18
msgid ""
-"<p>Please be aware that this project is still in an early alpha stage "
-"when it comes to running software – its not an easy task to rewrite"
-" the whole Internet! We are happy to get your <a "
-"href=\"engage.html\">helping hand</a> anytime! Further information is "
-"available in our <a href=\"https://docs.gnunet.org/#toc-Using-";
-"GNUnet-1\">handbook</a>. If you have any queries about the installation "
-"or the usage, please <a href=\"engage.html\">get in touch!</a></p>"
+"<p>Please be aware that this project is still in an early alpha stage when "
+"it comes to running software – its not an easy task to rewrite the "
+"whole Internet! We are happy to get your <a href=\"engage.html\">helping "
+"hand</a> anytime! Further information is available in our <a href=\"https://";
+"docs.gnunet.org/#toc-Using-GNUnet-1\">handbook</a>. If you have any queries "
+"about the installation or the usage, please <a href=\"engage.html\">get in "
+"touch!</a></p>"
msgstr ""
#: template/install.html.j2:30
msgid ""
"We recommend to use binary packages provided by the package manager "
-"integrated within your Operating System. GNUnet is reportedly available "
-"for at least: <ul> <li><a "
-"href=\"https://pkgs.alpinelinux.org/package/edge/testing/x86_64/gnunet\";>Alpine</a></li>"
-" <li><a "
-"href=\"https://www.archlinux.org/packages/community/x86_64/gnunet/\";>Arch</a></li>"
-" <li><a "
-"href=\"https://packages.debian.org/search?keywords=gnunet\";>Debian</a></li>"
-" <li><a "
-"href=\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora "
-"(Copr)</a></li> <li><a "
-"href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
-"href=\"https://github.com/Homebrew/homebrew-";
-"core/blob/master/Formula/gnunet.rb\">Homebrew</a></li> <li><a "
-"href=\"https://nixos.org/nixos/packages.html?attr=gnunet&channel=nixpkgs-";
-"unstable&query=gnunet\">NixOS</a></li> <li><a href=\"install-on-"
-"openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is available for your "
-"Operating System and it is missing, send us feedback so that we can add "
-"it to this list. Furthermore, if you are interested in packaging GNUnet "
-"for your Operating System, get in touch with us at gnunet-"
-"developers@gnu.org if you require help with this job. If you were using "
-"an Operating System with the Alpine package manager, GNUnet could be "
-"installed as simple as:"
+"integrated within your Operating System. GNUnet is reportedly available for "
+"at least: <ul> <li><a href=\"https://pkgs.alpinelinux.org/package/edge/";
+"testing/x86_64/gnunet\">Alpine</a></li> <li><a href=\"https://www.archlinux.";
+"org/packages/community/x86_64/gnunet/\">Arch</a></li> <li><a href=\"https://";
+"packages.debian.org/search?keywords=gnunet\">Debian</a></li> <li><a href="
+"\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora (Copr)</a></"
+"li> <li><a href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
+"href=\"https://github.com/Homebrew/homebrew-core/blob/master/Formula/gnunet.";
+"rb\">Homebrew</a></li> <li><a href=\"https://nixos.org/nixos/packages.html?";
+"attr=gnunet&channel=nixpkgs-unstable&query=gnunet\">NixOS</a></li> <li><a "
+"href=\"install-on-openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is "
+"available for your Operating System and it is missing, send us feedback so "
+"that we can add it to this list. Furthermore, if you are interested in "
+"packaging GNUnet for your Operating System, get in touch with us at gnunet-"
+"developers@gnu.org if you require help with this job. If you were using an "
+"Operating System with the Alpine package manager, GNUnet could be installed "
+"as simple as:"
msgstr ""
#: template/install.html.j2:61
msgid ""
-"Next we describe a generic way to install from source. If you are using "
-"one of the following Operating Systems these step-by-step guides might be"
-" useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href"
-"=\"install-on-debian9.html\">Debian 9</a>, <a href=\"install-on-"
-"macos.html\">Mac OS</a>, <a href=\"install-on-netbsd.html\">NetBSD</a>, "
-"<a href=\"install-on-ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not"
-" all of them might be totally up-to-date! Please <a "
-"href=\"engage.html\">ask us</a> if you get stuck."
+"Next we describe a generic way to install from source. If you are using one "
+"of the following Operating Systems these step-by-step guides might be "
+"useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href=\"install-on-"
+"debian9.html\">Debian 9</a>, <a href=\"install-on-macos.html\">Mac OS</a>, "
+"<a href=\"install-on-netbsd.html\">NetBSD</a>, <a href=\"install-on-"
+"ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not all of them might be "
+"totally up-to-date! Please <a href=\"engage.html\">ask us</a> if you get "
+"stuck."
msgstr ""
#: template/install.html.j2:75
msgid ""
-"First, install the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>required "
-"dependencies</a> of GNUnet. There are base requirements and optional "
-"requirements."
+"First, install the <a href=\"https://git.gnunet.org/gnunet.git/tree/README";
+"\">required dependencies</a> of GNUnet. There are base requirements and "
+"optional requirements."
msgstr ""
#: template/install.html.j2:81
msgid ""
"Now, you need to decide if you want to install GNUnet from the release "
"tarball or from git. If you want to use GNUnet and there is no binary "
-"package available for your OS, you should stick with the release tarball."
-" If you want to develop using the most recent build, you should go with "
-"the <a href=\"https://git.gnunet.org/\";>git repository</a>."
+"package available for your OS, you should stick with the release tarball. If "
+"you want to develop using the most recent build, you should go with the <a "
+"href=\"https://git.gnunet.org/\";>git repository</a>."
msgstr ""
#: template/install.html.j2:98
@@ -2086,8 +2762,8 @@ msgstr ""
#: template/install.html.j2:106
msgid ""
-"Before building GNUnet, make sure that you setup the required groups and "
-"add your user to the group <code>gnunet</code>:"
+"Before building GNUnet, make sure that you setup the required groups and add "
+"your user to the group <code>gnunet</code>:"
msgstr ""
#: template/install.html.j2:117
@@ -2096,9 +2772,8 @@ msgstr ""
#: template/install.html.j2:128
msgid ""
-"You can find more configuration flags in the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>README</a>.<br> "
-"Install GNUnet with:"
+"You can find more configuration flags in the <a href=\"https://git.gnunet.";
+"org/gnunet.git/tree/README\">README</a>.<br> Install GNUnet with:"
msgstr ""
#: template/install.html.j2:138
@@ -2108,9 +2783,8 @@ msgstr ""
#: template/install.html.j2:146
msgid ""
"Check the <a href=\"https://docs.gnunet.org/handbook/gnunet.html#Minimal-";
-"configuration\">handbook</a> for detailed documentation. For a more "
-"hands-on experience, <a href=\"https://gnunet.org/en/use.html\";>continue "
-"here</a>."
+"configuration\">handbook</a> for detailed documentation. For a more hands-on "
+"experience, <a href=\"https://gnunet.org/en/use.html\";>continue here</a>."
msgstr ""
#: template/livingstandards.html.j2:11
diff --git a/locale/messages.pot b/locale/messages.pot
index c129e8f..e218f8d 100644
--- a/locale/messages.pot
+++ b/locale/messages.pot
@@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2021-03-03 21:41+0100\n"
+"POT-Creation-Date: 2021-03-12 16:12+0100\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"
@@ -63,6 +63,7 @@ msgid "About"
msgstr ""
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
msgstr ""
@@ -155,17 +156,20 @@ msgstr ""
msgid "FAQ"
msgstr ""
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
msgstr ""
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
msgstr ""
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
msgstr ""
@@ -792,11 +796,133 @@ msgid ""
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
-#: template/faq.html.j2:12
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
+msgstr ""
+
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
+msgstr ""
+
+#: template/faq.html.j2:15 template/faq.html.j2:695
+msgid "Error messages"
+msgstr ""
+
+#: template/faq.html.j2:16 template/faq.html.j2:797
+msgid "File-sharing"
+msgstr ""
+
+#: template/faq.html.j2:17 template/faq.html.j2:973
+msgid "Contributing"
+msgstr ""
+
+#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr ""
+
+#: template/faq.html.j2:28
+msgid ""
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list"
+" or the #gnunet IRC on irc.freenode.net."
+msgstr ""
+
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
+msgstr ""
+
+#: template/faq.html.j2:38
+msgid ""
+"A: The general answer is, when it is ready. A better answer may be: "
+"earlier if you contribute (test, debug, code, document). Every release "
+"will be anounced on the info-gnunet@gnu.org mailing list and on <a "
+"href=\"https://planet.gnu.org\";>planet GNU</a>. You can subscribe to the "
+"mailing list or the RSS feed of this site to automatically receive a "
+"notification."
+msgstr ""
+
+#: template/faq.html.j2:49
+msgid "Is the code free?"
+msgstr ""
+
+#: template/faq.html.j2:51
+msgid ""
+"A: GNUnet is free software, available under the <a "
+"href=\"https://www.gnu.org/licenses/agpl-3.0.en.html\";>GNU Affero Public "
+"License (AGPL)</a>."
+msgstr ""
+
+#: template/faq.html.j2:58
+msgid "Are there any known bugs?"
+msgstr ""
+
+#: template/faq.html.j2:60
+msgid ""
+"A: We track the list of currently known bugs in the <a "
+"href=\"https://bugs.gnunet.org/\";>Mantis system</a>. Some bugs are "
+"occasionally reported directly to developers or the developer mailing "
+"list. This is discouraged since developers often do not have the time to "
+"feed these bugs back into the Mantis database. Please report bugs "
+"directly to the bug tracking system. If you believe a bug is sensitive, "
+"you can set its view status to private (this should be the exception)."
+msgstr ""
+
+#: template/faq.html.j2:73 template/faq.html.j2:193
+msgid "Is there a graphical user interface?"
+msgstr ""
+
+#: template/faq.html.j2:75
+msgid ""
+"A: gnunet-gtk is a separate download. The package contains various GTK+ "
+"based graphical interfaces, including a graphical tool for configuration."
+msgstr ""
+
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr ""
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called "
+""proof-of-work" which is used to convince the network that your"
+" peer is real (or, rather, make it expensive for an adversary to mount a "
+"Sybil attack on the network size estimator). The calculation is expected "
+"to take a few days, depending on how fast your CPU is. If the CPU load is"
+" creating a problem for you, you can set the value "WORKDELAY" "
+"in the "nse" section of your configuration file to a higher "
+"value. The default is "5 ms"."
+msgstr ""
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr ""
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for "
+"TCP connections and, with the Tor Browser Bundle, for the Web in "
+"particular. GNUnet does not really have one focus; our theme is secure "
+"decentralized networking, but that is too broad to be called a focus."
+msgstr ""
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr ""
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost "
+"no overlaps. <br><br> I2P is written in Java, and has (asymmetric) "
+"tunnels using onion (or garlic) routing as the basis for various "
+"(anonymized) applications. I2P is largely used via a Web frontend."
+msgstr ""
+
+#: template/faq.html.j2:124
msgid "Is GNUnet ready for use on production systems?"
msgstr ""
-#: template/faq.html.j2:14
+#: template/faq.html.j2:126
msgid ""
"A: GNUnet is still undergoing major development. It is largely not yet "
"ready for usage beyond developers. Your mileage will vary depending on "
@@ -806,24 +932,474 @@ msgid ""
"[TNG]")"
msgstr ""
-#: template/faq.html.j2:24
+#: template/faq.html.j2:136
msgid "Is GNUnet build using distributed ledger technologies?"
msgstr ""
-#: template/faq.html.j2:26
+#: template/faq.html.j2:138
msgid ""
"A: No. GNUnet is a new network protocol stack for building secure, "
"distributed, and privacy-preserving applications. While a ledger could be"
" built using GNUnet, we currently have no plans in doing so."
msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:151
+msgid "What can I do with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it "
+"can do more than just one thing. Naturally, the implementation and "
+"documentation of some of the features that exist are more advanced than "
+"others."
+msgstr ""
+
+#: template/faq.html.j2:160
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a "
+"fully decentralized and censorship-resistant replacement for DNS and a "
+"mechanism for IPv4-IPv6 protocol translation and tunneling (NAT-PT with "
+"DNS-ALG)."
+msgstr ""
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We"
+" recommend that you use Tor for anonymous surfing."
+msgstr ""
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr ""
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+
+#: template/faq.html.j2:195
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the"
+" gnunet-gtk package, which is a separate download. gnunet-gtk is a meta "
+"GUI that integrates most of the other GUIs in one window. One exception "
+"is gnunet-setup, which must still be run separately at this time (as "
+"setup requires the peer to be stopped)."
+msgstr ""
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr ""
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux."
+" Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch,"
+" FreeBSD and macOS. We have reports of working versions on many other "
+"GNU/Linux distributions; in the past we had reports of working versions "
+"on NetBSD, OpenBSD and Solaris. However, not all of those reports are "
+"recent, so if you cannot get GNUnet to work on those systems please let "
+"us know."
+msgstr ""
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr ""
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a "
+"default configuration of top-level domains. The governance of this "
+"default configuration is not yet established. In any case, the user will "
+"be able to modify this configuration at will. We expect normal users to "
+"have no need to edit their own GNS zone(s) unless they host services "
+"themselves."
+msgstr ""
+
+#: template/faq.html.j2:241
+msgid "Where is the per-user GNS database kept?"
+msgstr ""
+
+#: template/faq.html.j2:243
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet "
+"peer. Now, a user may run multiple GNUnet peers, in which case the "
+"database could be kept at each peer (however, we don't have code for "
+"convenient replication). Similarly, multiple GNUnet peers can share one "
+"instance of the database --- the "gnunet-service-namestore" can"
+" be accessed from remote (via TCP). The actual data can be stored in a "
+"Postgres database, for which various replication options are again "
+"applicable. Ultimately, there are many options for how users can store "
+"(and secure) their GNS database."
+msgstr ""
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases"
+" will only grow to a few tens of thousands of entries, small enough to "
+"fit even on mobile devices."
+msgstr ""
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr ""
+
+#: template/faq.html.j2:272
+msgid ""
+"A: We believe so, as there is no entity that any government could force "
+"to change the mapping for a name except for each individual user (and "
+"then the changes would only apply to the names that this user is the "
+"authority for). So if everyone used GNS, the only practical attack of a "
+"government would be to force the operator of a server to change the GNS "
+"records for his server to point elsewhere. However, if the owner of the "
+"private key for a zone is unavailable for enforcement, the respective "
+"zone cannot be changed and any other zone delegating to this zone will "
+"achieve proper resolution."
+msgstr ""
+
+#: template/faq.html.j2:286
+msgid "How does GNS compare to other name systems"
+msgstr ""
+
+#: template/faq.html.j2:288
+msgid ""
+"A: A scientific paper on this topic <a "
+"href=\"https://grothoff.org/christian/ns2018.pdf\";>has been published "
+"</a> and below is a table from the publication. For detailed descriptions"
+" please refer to the paper."
+msgstr ""
+
+#: template/faq.html.j2:392
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr ""
+
+#: template/faq.html.j2:394
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, "
+"and there are still registrars that determine who owns a name. <br><br> "
+"With GNS, we decentralize the database and also decentralize the "
+"responsibility for naming: each user runs his own personal root zone and "
+"is thus in complete control of the names he uses. GNS also has many "
+"additional features (to keep names short and enable migration) which "
+"don't even make sense in the context of CoDoNS."
+msgstr ""
+
+#: template/faq.html.j2:410
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr ""
+
+#: template/faq.html.j2:412
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared "
+"via delegation, and thus mappings will only change if the user "
+"responsible for the name (the authority) manually changes the record."
+msgstr ""
+
+#: template/faq.html.j2:426
+msgid "What is the difference between GNS and ODDNS?"
+msgstr ""
+
+#: template/faq.html.j2:428
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+
+#: template/faq.html.j2:439
+msgid "What is the difference between GNS and Handshake?"
+msgstr ""
+
+#: template/faq.html.j2:441
+msgid ""
+"A: Handshake is a blockchain-based method for root zone governance. "
+"Hence, it does not address the name resolution process itself but "
+"delegates resolution into DNS after the initial TLD resolution. Not "
+"taking sustainablility considerations into account, handshake could be "
+"used as an additional supporting GNS root zone governance model but we "
+"currently do not have such plans in mind."
+msgstr ""
+
+#: template/faq.html.j2:453
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr ""
+
+#: template/faq.html.j2:455
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks "
+"on DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from"
+" the DNS hierarchy."
+msgstr ""
+
+#: template/faq.html.j2:468
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the "
+"style of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: For security, it is well known that an initial trust path between the "
+"two parties must exist. However, for applications where this is not "
+"required, weaker mechanisms can be used. For example, we have implemented"
+" a first-come-first-served (FCFS) authority which allows arbitrary users "
+"to register arbitrary names. The key of this authority is included with "
+"every GNUnet installation. Thus, any name registered with FCFS is in fact"
+" global and requires no further introduction. However, the security of "
+"these names depends entirely on the trustworthiness of the FCFS "
+"authority. The authority can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name "
+"in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:487
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "
+""legitimate" domain owner. Any user can claim any name (as his "
+"preferred name or "pseudonym") in his NICK record. Similarly, "
+"all other users can choose to ignore this preference and use a name of "
+"their choice (or even assign no name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:498
+msgid ""
+"Did you consider the privacy implications of making your personal GNS "
+"zone visible?"
+msgstr ""
+
+#: template/faq.html.j2:500
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not "
+"set. Thus, users have full control over what information about their "
+"zones is made public."
+msgstr ""
+
+#: template/faq.html.j2:510
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary "
+"because of IPv4 address scarcity, and (b) that LEHOs are only useful in "
+"the context of virtual hosting. However, LEHOs are also useful to help "
+"with X.509 certificate validation (as they specify for which legacy "
+"hostname the certificate should be valid). Also, even with IPv6 fully "
+"deployed and "infinite" IP addresses being available, we're not"
+" sure that virtual hosting would disappear. Finally, we don't want to "
+"have to wait for IPv6 to become commonplace, GNS should work with today's"
+" networks."
+msgstr ""
+
+#: template/faq.html.j2:526
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:528
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. "
+"As trust relationships evolve, mappings would change their meaning as "
+"they cross each others thresholds. We decided that the resulting "
+"unpredictability of the resolution process was not acceptable. "
+"Furthermore, trust and consensus might be easy to manipulate by "
+"adversaries."
+msgstr ""
+
+#: template/faq.html.j2:539
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:541
+msgid ""
+"A: The owner of a private key can create a revocation message. This one "
+"can then be flooded throughout the overlay network, creating a copy at "
+"all peers. Before using a public key, peers check if that key has been "
+"revoked. All names that involve delegation via a revoked zone will then "
+"fail to resolve. Peers always automatically check for the existence of a "
+"revocation message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:553
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:555
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:569
+msgid "How can a GNS zone maintain several name servers, e.g. for load
balancing?"
+msgstr ""
+
+#: template/faq.html.j2:571
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share"
+" the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:584
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:586
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names "
+"are not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on "
+"your application, HTTPS may not be worth the cost. However, for users "
+"that are experiencing censorship (or are concerned about it), giving up "
+"globally unique names may very well be worth the cost. After all, what is"
+" a "globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:600
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:602
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by "
+"IANA/ICANN. This centralization creates vulnerabilities. For example, the"
+" US government was able to reassign the management of the country-TLDs of"
+" Afganistan and Iraq during the wars at the beginning of the 21st "
+"century."
+msgstr ""
+
+#: template/faq.html.j2:613
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:615
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual "
+"hosting, so blocking a particular IP address causes much more collateral "
+"damage than blocking a DNS name. It thus raises the cost of "
+"censorship.</li> <li> Existing layer-3 circumvention solutions (such as "
+"Tor) would benefit from a censorship resistant naming system. Accessing "
+"Tor's ".onion" namespace currently requires users to use "
+"unmemorable cryptographic identifiers. With nicer names, Tor and tor2web-"
+"like services would be even easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:634
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:636
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can "
+"use GNS to perform name resolution as well as any normal user. Naturally,"
+" while we typically expect normal users to install custom software for "
+"name resolution, this is unlikely to work for search engines today. "
+"However, the DNS2GNS gateway allows search engines to use DNS to resolve "
+"GNS names, so they can still index GNS resources. However, as using "
+"DNS2GNS gateways breaks the cryptographic chain of trust, legacy search "
+"engines will obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:650
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:652
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was "
+"designed to interoperate with DNS as much as possible, and to also work "
+"as much as possible with the existing Web infrastructure. UIA is not at "
+"all concerned about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:665
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:667
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you "
+"know if a name you are resolving belongs to a friend, or a friend-"
+"of-a-friend, and can thus decide how much you trust the result. "
+"Naturally, the trusted-computing base (TCB) can become arbitrarily large "
+"this way --- however, given the name length restriction, for an "
+"individual name it is always less than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:679
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part "
+"of the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:681
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects "
+"the "_Service._Proto" syntax, converts "Service" to "
+"the corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when "
+"the result is presented, GNS looks for the GNS-specific "BOX" "
+"record type. A BOX record is a record that contains another record (such "
+"as SRV or TLSA records) and adds a service and protocol number (and the "
+"original boxed record type) to it."
+msgstr ""
+
+#: template/faq.html.j2:697
msgid ""
"I receive many "WARNING Calculated flow delay for X at Y for "
"Z". Should I worry?"
msgstr ""
-#: template/faq.html.j2:37
+#: template/faq.html.j2:699
msgid ""
"A: Right now, this is expected and a known cause for high latency in "
"GNUnet. We have started a major rewrite to address this and other "
@@ -831,14 +1407,195 @@ msgid ""
"warnings are expected."
msgstr ""
-#: template/faq.html.j2:46
-msgid "Is there a graphical user interface?"
+#: template/faq.html.j2:708
+msgid "Error opening `/dev/net/tun': No such file or directory?"
msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:710
msgid ""
-"A: gnunet-gtk is a separate download. The package contains various GTK+ "
-"based graphical interfaces, including a graphical tool for configuration."
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:722
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-"
+"service-dns)?"
+msgstr ""
+
+#: template/faq.html.j2:724
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check"
+" if your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:736
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:738
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if"
+" your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:746
+msgid "I'm getting an 'error while loading shared libraries:
libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:748
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if "
+"you compiled GNUnet the normal way and/or used a binary package, that is "
+"highly unlikely. The more common cause is that you installed GNUnet to a "
+"directory that your linker does not search. There are several ways to fix"
+" this that are described below. If you are 'root' and you installed to a "
+"system folder (such as /usr/local), you want to add the libraries to the "
+"system-wide search path. This is done by adding a line "
+"\"/usr/local/lib/\" to /etc/ld.so.conf and running \"ldconfig\". If you "
+"installed GNUnet to /opt or any other similar path, you obviously have to"
+" change \"/usr/local\" accordingly. If you do not have 'root' rights or "
+"if you installed GNUnet to say \"/home/$USER/\", then you can explicitly "
+"tell your linker to search a particular directory for libraries using the"
+" \"LD_LIBRARY_PATH\" environment variable. For example, if you configured"
+" GNUnet using a prefix of \"$HOME/gnunet/\" you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:774
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the "
+"\"$\") to your .bashrc or .profile file. You will have to logout and "
+"login again to have this new profile be applied to all shells (including "
+"your desktop environment)."
+msgstr ""
+
+#: template/faq.html.j2:781
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:783
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries "
+"built for end-users and can always be ignored. Error messages flagged as "
+"\"INFO\" always refer to harmless events that require no action. For "
+"example, GNUnet may use an INFO message to indicate that it is currently "
+"performing an expensive operation that will take some time. GNUnet will "
+"also use INFO messages to display information about important "
+"configuration values."
+msgstr ""
+
+#: template/faq.html.j2:799
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:801
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most "
+"other P2P networks, GNUnet was designed with security in mind as the "
+"highest priority. We intend on producing a network with comprehensive "
+"security features. Many other P2P networks are open to a wide variety of "
+"attacks, and users have little privacy. GNUnet is also Free Software and "
+"thus the source code is available, so you do not have to worry about "
+"being spied upon by the software. The following table summarises the main"
+" differences between GNUnet and other systems. The information is "
+"accurate to the best of our knowledge. The comparison is difficult since "
+"there are sometimes differences between various implementations of "
+"(almost) the same protocol. In general, we pick a free implementation as "
+"the reference implementation since it is possible to inspect the free "
+"code. Also, all of these systems are changing over time and thus the data"
+" below may not be up-to-date. If you find any flaws, please let us know. "
+"Finally, the table is not saying terribly much (it is hard to compare "
+"these systems this briefly), so if you want the real differences, read "
+"the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:915
+msgid ""
+"Another important point of reference are the various anonymous peer-to-"
+"peer networks. Here, there are differences in terms of application domain"
+" and how specifically anonymity is achieved. Anonymous routing is a hard "
+"research topic, so for a superficial comparisson like this one we focus "
+"on the latency. Another important factor is the programming language. "
+"Type-safe languages may offer certain security benefits; however, this "
+"may come at the cost of significant increases in resource consumption "
+"which in turn may reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:928
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:930
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of "
+"the same techniques used to generate reasonable passwords to defend "
+"against such an attack. In any event, we are not trying to hide content; "
+"thus, unless the user is trying to insert information into the network "
+"that can only be shared with a small group of people, there is no real "
+"reason to try to obfuscate the content by choosing a difficult keyword "
+"anyway."
+msgstr ""
+
+#: template/faq.html.j2:944
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:946
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all"
+" users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell "
+"which of the peers in the group originated the message. In other words, "
+"it should be difficult to impossible for an adversary to distinguish "
+"between the originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:958
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:960
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash "
+"of its public key) and has a number of addresses it is reachable by (may "
+"have no addresses, for instance when it's behind a NAT). You specify "
+"bandwidth limits (how much traffic GNUnet is allowed to consume) and "
+"datastore quote (how large your on-disk block storage is) . Your node "
+"will then proceed to connect to other nodes, becoming part of the "
+"network."
+msgstr ""
+
+#: template/faq.html.j2:975
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:977
+msgid ""
+"A: First, you need to register an account with our weblate system. Please"
+" send an e-mail with the desired target language to "
+"translators@gnunet.org or ask for help on the #gnunet chat on "
+"irc.freenode.net. Typically someone with sufficient permissions will then"
+" grant you access. Naturally, any abuse will result in the loss of "
+"permissions."
+msgstr ""
+
+#: template/faq.html.j2:989
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:991
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly "
+"implement. The best way to actually get a new feature implemented is to "
+"do it yourself --- and to then send us a patch."
msgstr ""
#: template/glossary.html.j2:12
@@ -946,10 +1703,6 @@ msgstr ""
msgid "Overview"
msgstr ""
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
-
#: template/gns.html.j2:39
msgid ""
"The GNU Name System (GNS) is secure and decentralized naming system. It "
diff --git a/locale/pt/LC_MESSAGES/messages.po
b/locale/pt/LC_MESSAGES/messages.po
index a9323b4..0de29b7 100644
--- a/locale/pt/LC_MESSAGES/messages.po
+++ b/locale/pt/LC_MESSAGES/messages.po
@@ -7,13 +7,13 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2021-03-03 21:41+0100\n"
+"POT-Creation-Date: 2021-03-12 15:55+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
"Language: pt\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.9.0\n"
@@ -63,6 +63,7 @@ msgid "About"
msgstr ""
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
msgstr ""
@@ -155,17 +156,20 @@ msgstr ""
msgid "FAQ"
msgstr ""
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
msgstr ""
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
msgstr ""
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
msgstr ""
@@ -180,39 +184,38 @@ msgstr ""
#: template/about.html.j2:13
msgid ""
-"GNUnet is an alternative network stack for building secure, decentralized"
-" and privacy-preserving distributed applications. Our goal is to replace "
-"the old insecure Internet protocol stack. Starting from an application "
-"for secure publication of files, it has grown to include all kinds of "
-"basic protocol components and applications towards the creation of a GNU "
-"internet."
+"GNUnet is an alternative network stack for building secure, decentralized "
+"and privacy-preserving distributed applications. Our goal is to replace the "
+"old insecure Internet protocol stack. Starting from an application for "
+"secure publication of files, it has grown to include all kinds of basic "
+"protocol components and applications towards the creation of a GNU internet."
msgstr ""
#: template/about.html.j2:23
msgid ""
-"Today, the actual use and thus the social requirements for a global "
-"network differs widely from those goals of 1970. While the Internet "
-"remains suitable for military use, where the network equipment is "
-"operated by a command hierarchy and when necessary isolated from the rest"
-" of the world, the situation is less tenable for civil society."
+"Today, the actual use and thus the social requirements for a global network "
+"differs widely from those goals of 1970. While the Internet remains suitable "
+"for military use, where the network equipment is operated by a command "
+"hierarchy and when necessary isolated from the rest of the world, the "
+"situation is less tenable for civil society."
msgstr ""
#: template/about.html.j2:32
msgid ""
"Due to fundamental Internet design choices, Internet traffic can be "
-"misdirected, intercepted, censored and manipulated by hostile routers on "
-"the network. And indeed, the modern Internet has evolved exactly to the "
-"point where, as Matthew Green put it, <a "
-"href=\"https://blog.cryptographyengineering.com/2015/08/16/the-network-";
-"is-hostile/\">\"the network is hostile\"</a>."
+"misdirected, intercepted, censored and manipulated by hostile routers on the "
+"network. And indeed, the modern Internet has evolved exactly to the point "
+"where, as Matthew Green put it, <a href=\"https://blog.";
+"cryptographyengineering.com/2015/08/16/the-network-is-hostile/\">\"the "
+"network is hostile\"</a>."
msgstr ""
#: template/about.html.j2:41
msgid ""
-"We believe liberal societies need a network architecture that uses the "
-"anti-authoritarian decentralized peer-to-peer paradigm and privacy-"
-"preserving cryptographic protocols. The goal of the GNUnet project is to "
-"provide a Free Software realization of this ideal."
+"We believe liberal societies need a network architecture that uses the anti-"
+"authoritarian decentralized peer-to-peer paradigm and privacy-preserving "
+"cryptographic protocols. The goal of the GNUnet project is to provide a Free "
+"Software realization of this ideal."
msgstr ""
#: template/about.html.j2:49
@@ -223,8 +226,8 @@ msgstr ""
#: template/about.html.j2:56
msgid ""
-"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy";
-"/free-sw.html\">Free Software</a>."
+"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy/free-";
+"sw.html\">Free Software</a>."
msgstr ""
#: template/about.html.j2:60
@@ -235,8 +238,8 @@ msgstr ""
#: template/about.html.j2:61
msgid ""
-"GNUnet must be fully distributed and resilient to external attacks and "
-"rogue participants."
+"GNUnet must be fully distributed and resilient to external attacks and rogue "
+"participants."
msgstr ""
#: template/about.html.j2:62
@@ -247,8 +250,8 @@ msgstr ""
#: template/about.html.j2:63
msgid ""
-"GNUnet must inform the user which other participants have to be trusted "
-"when establishing private communications."
+"GNUnet must inform the user which other participants have to be trusted when "
+"establishing private communications."
msgstr ""
#: template/about.html.j2:64
@@ -269,33 +272,28 @@ msgstr ""
#: template/about.html.j2:68
msgid ""
-"GNUnet must provide incentives for peers to contribute more resources "
-"than they consume."
+"GNUnet must provide incentives for peers to contribute more resources than "
+"they consume."
msgstr ""
#: template/about.html.j2:72
msgid ""
-"To get know and learn more, please check our <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, "
-"especially the <a href=\"https://docs.gnunet.org/handbook/gnunet.html";
-"#Key-Concepts\">chapter on \"Key Concepts\"</a>, explaining the "
-"fundamental concepts of GNUnet: <ul> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Authentication\";>Authentication</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Accounting-";
-"to-Encourage-Resource-Sharing\">Accounting to Encourage Resource "
-"Sharing</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Confidentiality\";>Confidentiality</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability\";>Deniability</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Peer-";
-"Identities\">Peer Identities</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-";
-"Name-System-_0028GNS-Zones_0029\">Zones in the GNU Name System (GNS "
-"Zones)</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> "
-"</ul>"
+"To get know and learn more, please check our <a href=\"https://docs.gnunet.";
+"org/handbook/gnunet.html\">handbook</a>, especially the <a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Key-Concepts\">chapter on \"Key Concepts"
+"\"</a>, explaining the fundamental concepts of GNUnet: <ul> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Authentication";
+"\">Authentication</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Accounting-to-Encourage-Resource-Sharing\">Accounting to "
+"Encourage Resource Sharing</a></li> <li><a href=\"https://docs.gnunet.org/";
+"handbook/gnunet.html#Confidentiality\">Confidentiality</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></"
+"li> <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability";
+"\">Deniability</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Peer-Identities\">Peer Identities</a></li> <li><a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-Name-System-_0028GNS-"
+"Zones_0029\">Zones in the GNU Name System (GNS Zones)</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> </ul>"
msgstr ""
#: template/about.html.j2:88
@@ -304,27 +302,27 @@ msgstr ""
#: template/about.html.j2:90
msgid ""
-"There are many more resources to learn about GNUnet besides the <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such "
-"as the <a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers "
-"covering the various layers, many <a "
-"href=\"https://gnunet.org/en/video.html\";>videos</a> or a brief <a "
-"href=\"https://gnunet.org/en/glossary.html\";>glossary</a>."
+"There are many more resources to learn about GNUnet besides the <a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such as the "
+"<a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers covering "
+"the various layers, many <a href=\"https://gnunet.org/en/video.html";
+"\">videos</a> or a brief <a href=\"https://gnunet.org/en/glossary.html";
+"\">glossary</a>."
msgstr ""
#: template/about.html.j2:95
msgid ""
"You are most welcome to <a href=\"engage.html\">get engaged into the "
-"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a "
-"href=\"use.html\">use it</a> and <a href=\"engage.html\">contribute and "
-"get engaged</a> in various ways."
+"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a href=\"use."
+"html\">use it</a> and <a href=\"engage.html\">contribute and get engaged</a> "
+"in various ways."
msgstr ""
#: template/about.html.j2:100
msgid ""
-"Please be aware that this project is (despite of it's age) still in an "
-"early alpha stage when it comes to software – its not an easy task "
-"to rewrite the whole Internet!"
+"Please be aware that this project is (despite of it's age) still in an early "
+"alpha stage when it comes to software – its not an easy task to "
+"rewrite the whole Internet!"
msgstr ""
#: template/about.html.j2:105
@@ -333,24 +331,25 @@ msgstr ""
#: template/about.html.j2:110
msgid ""
-"We're receiving funding from NLnet's Next Generation Internet funding "
-"line to document and implement the GNU Name System protocol in a way "
-"suitable for the IETF standardization process."
+"We're receiving funding from NLnet's Next Generation Internet funding line "
+"to document and implement the GNU Name System protocol in a way suitable for "
+"the IETF standardization process."
msgstr ""
#: template/about.html.j2:123
msgid ""
"This project has received funding from the European Union’s Horizon 2020 "
"research and innovation programme under the NGI_TRUST grant agreement no "
-"825618. The project aims to integrate re:claimID with the GNU Taler "
-"payment system in a pilot in order to demonstrate the practical "
-"feasibility and benefits of privacy enhancing technologies for users and "
-"commercial service providers. The project is called \"Decentralized "
-"Identities for Self-Sovereign End-users\" (DISSENS)."
+"825618. The project aims to integrate re:claimID with the GNU Taler payment "
+"system in a pilot in order to demonstrate the practical feasibility and "
+"benefits of privacy enhancing technologies for users and commercial service "
+"providers. The project is called \"Decentralized Identities for Self-"
+"Sovereign End-users\" (DISSENS)."
msgstr ""
#: template/about.html.j2:141
-msgid "We are grateful for free hosting offered by the following
organizations:"
+msgid ""
+"We are grateful for free hosting offered by the following organizations:"
msgstr ""
#: template/about.html.j2:150
@@ -371,13 +370,13 @@ msgstr ""
#: template/applications.html.j2:15
msgid ""
-"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully "
-"decentralized replacement for the Domain Name System (DNS). Instead of "
-"using a hierarchy, GNS uses a directed graph. Naming conventions are "
-"similar to DNS, but queries and replies are private even with respect to "
-"peers providing the answers. The integrity of records and privacy of "
-"look-ups is cryptographically secured. <!-- Too technical: GNS integrates"
-" a robust, efficient and instant key revocation mechanism. -->"
+"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully decentralized "
+"replacement for the Domain Name System (DNS). Instead of using a hierarchy, "
+"GNS uses a directed graph. Naming conventions are similar to DNS, but "
+"queries and replies are private even with respect to peers providing the "
+"answers. The integrity of records and privacy of look-ups is "
+"cryptographically secured. <!-- Too technical: GNS integrates a robust, "
+"efficient and instant key revocation mechanism. -->"
msgstr ""
#: template/applications.html.j2:38
@@ -386,8 +385,8 @@ msgstr ""
#: template/applications.html.j2:40
msgid ""
-"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized"
-" Identity Provider (IdP) service built in top of the GNU Name System. It "
+"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized "
+"Identity Provider (IdP) service built in top of the GNU Name System. It "
"allows users to securely share personal information with websites using "
"standardized protocols (OpenID Connect)."
msgstr ""
@@ -398,10 +397,9 @@ msgstr ""
#: template/applications.html.j2:59
msgid ""
-"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that "
-"aims to provide censorship-resistant, anonymous filesharing. The "
-"publisher is empowered to make a gradual choice between performance and "
-"anonymity."
+"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that aims "
+"to provide censorship-resistant, anonymous filesharing. The publisher is "
+"empowered to make a gradual choice between performance and anonymity."
msgstr ""
#: template/applications.html.j2:73
@@ -411,8 +409,8 @@ msgstr ""
#: template/applications.html.j2:75
msgid ""
"GNUnet conversation is an application that provides secure voice "
-"communication in a fully decentralized way by employing GNUnet for "
-"routing and transport."
+"communication in a fully decentralized way by employing GNUnet for routing "
+"and transport."
msgstr ""
#: template/applications.html.j2:91
@@ -426,8 +424,8 @@ msgstr ""
#: template/applications.html.j2:99
msgid ""
"<a href=\"https://taler.net/\";>GNU Taler</a> is a new privacy-preserving "
-"electronic payment system. Payments are cryptographically secured and are"
-" confirmed within milliseconds with extremely low transaction costs."
+"electronic payment system. Payments are cryptographically secured and are "
+"confirmed within milliseconds with extremely low transaction costs."
msgstr ""
#: template/applications.html.j2:118
@@ -436,10 +434,10 @@ msgstr ""
#: template/applications.html.j2:120
msgid ""
-"<a href=\"https://secushare.org/\";>secushare</a> is creating a "
-"decentralized social networking application on top of GNUnet. Using "
-"overlay multicast and the extensible PSYC protocol, notifications are "
-"distributed end-to-end encrypted to authorized recipients only."
+"<a href=\"https://secushare.org/\";>secushare</a> is creating a decentralized "
+"social networking application on top of GNUnet. Using overlay multicast and "
+"the extensible PSYC protocol, notifications are distributed end-to-end "
+"encrypted to authorized recipients only."
msgstr ""
#: template/applications.html.j2:139
@@ -448,10 +446,10 @@ msgstr ""
#: template/applications.html.j2:141
msgid ""
-"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) "
-"is creating a usable end-to-end encrypted e-mail solution using "
-"opportunistic key exchange. p≡p will use GNUnet to protect metadata"
-" and exploit new cryptographic protocols to verify keys."
+"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) is "
+"creating a usable end-to-end encrypted e-mail solution using opportunistic "
+"key exchange. p≡p will use GNUnet to protect metadata and exploit new "
+"cryptographic protocols to verify keys."
msgstr ""
#: template/applications.html.j2:160
@@ -460,10 +458,10 @@ msgstr ""
#: template/applications.html.j2:162
msgid ""
-"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> "
-"is a convenient but feature-rich graphical application providing "
-"messaging using especially the CADET subsystem. It is developed using GTK"
-" and libhandy for a convergent design."
+"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> is a "
+"convenient but feature-rich graphical application providing messaging using "
+"especially the CADET subsystem. It is developed using GTK and libhandy for a "
+"convergent design."
msgstr ""
#: template/applications.html.j2:180
@@ -474,8 +472,8 @@ msgstr ""
msgid ""
"<a href=\"https://git.gnunet.org/groupchat.git/\";>groupchat</a> is a "
"terminal user interface providing messaging using especially the CADET "
-"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned"
-" to be compatible."
+"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned to "
+"be compatible."
msgstr ""
#: template/architecture.html.j2:6
@@ -488,11 +486,11 @@ msgstr ""
#: template/architecture.html.j2:22
msgid ""
-"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-"
-"like end-to-end encrypted messaging layer (CADET), a public key "
-"infrastructure (GNS) and a pluggable transport system (TRANSPORT).<br> "
-"Using public keys for addresses and self-organized decentralized routing "
-"algorithms, these subsystems replace the traditional TCP/IP stack."
+"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-like "
+"end-to-end encrypted messaging layer (CADET), a public key infrastructure "
+"(GNS) and a pluggable transport system (TRANSPORT).<br> Using public keys "
+"for addresses and self-organized decentralized routing algorithms, these "
+"subsystems replace the traditional TCP/IP stack."
msgstr ""
#: template/architecture.html.j2:35
@@ -503,9 +501,9 @@ msgstr ""
msgid ""
"GNUnet is implemented using a multi-process architecture. Each subsystem "
"runs as a separate process, providing fault-isolation and enabling tight "
-"permissions to be granted to each subsystem. Naturally, the "
-"implementation is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and"
-" will always remain free software."
+"permissions to be granted to each subsystem. Naturally, the implementation "
+"is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and will always "
+"remain free software."
msgstr ""
#: template/architecture.html.j2:52
@@ -538,11 +536,10 @@ msgstr ""
#: template/contact.html.j2:13
msgid ""
-"An archived, public mailing list for GNUnet is hosted at <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers\">https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>. You can send messages to the list at <a href=\"mailto"
-":gnunet-developers@gnu.org\">gnunet-developers@gnu.org</a>."
+"An archived, public mailing list for GNUnet is hosted at <a href=\"https://";
+"lists.gnu.org/mailman/listinfo/gnunet-developers\">https://lists.gnu.org/";
+"mailman/listinfo/gnunet-developers</a>. You can send messages to the list at "
+"<a href=\"mailto:gnunet-developers@gnu.org\";>gnunet-developers@gnu.org</a>."
msgstr ""
#: template/contact.html.j2:23
@@ -551,10 +548,9 @@ msgstr ""
#: template/contact.html.j2:25
msgid ""
-"<tt>#gnunet</tt> is reachable via <a "
-"href=\"https://freenode.net\";>irc.freenode.net</a>. There is also an <a "
-"href=\"https://view.matrix.org/room/!IjaAfLiruzjxFFzKAV:matrix.org/\";>archive</a>"
-" available."
+"<tt>#gnunet</tt> is reachable via <a href=\"https://freenode.net\";>irc."
+"freenode.net</a>. There is also an <a href=\"https://view.matrix.org/room/!";
+"IjaAfLiruzjxFFzKAV:matrix.org/\">archive</a> available."
msgstr ""
#: template/contact.html.j2:38
@@ -563,11 +559,10 @@ msgstr ""
#: template/contact.html.j2:40
msgid ""
-"GNUnet developers are generally reachable at either "
-"<tt>PSEUDONYM@gnunet.org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us"
-" support receiving GnuPG encrypted Emails. Urgent and sensitive security "
-"issues may be addressed to the GNU maintainers <tt>schanzen</tt> and "
-"<tt>grothoff</tt>."
+"GNUnet developers are generally reachable at either <tt>PSEUDONYM@gnunet."
+"org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us support receiving GnuPG "
+"encrypted Emails. Urgent and sensitive security issues may be addressed to "
+"the GNU maintainers <tt>schanzen</tt> and <tt>grothoff</tt>."
msgstr ""
#: template/contact.html.j2:53
@@ -576,38 +571,37 @@ msgstr ""
#: template/contact.html.j2:55
msgid ""
-"We track open feature requests and bugs for projects within GNUnet in our"
-" <a href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also "
-"report bugs or feature requests to the <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/bug-gnunet\";>bug-gnunet</a>"
-" mailing list. The mailinglist requires no subscription."
+"We track open feature requests and bugs for projects within GNUnet in our <a "
+"href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also report bugs "
+"or feature requests to the <a href=\"https://lists.gnu.org/mailman/listinfo/";
+"bug-gnunet\">bug-gnunet</a> mailing list. The mailinglist requires no "
+"subscription."
msgstr ""
#: template/copyright.html.j2:11
msgid ""
-"<p> Contributors to GNUnet with Git access must sign the <a "
-"href=\"/static/pdf/copyright.pdf\">copyright assignment</a> to ensure "
-"that the <a href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/gnunet_taler_agreement.tex\">GNUnet e.V. --- Taler Systems SA"
-" agreement on licensing and collaborative development</a> of the GNUnet "
-"and GNU Taler projects is satisfied. </p>"
+"<p> Contributors to GNUnet with Git access must sign the <a href=\"/static/"
+"pdf/copyright.pdf\">copyright assignment</a> to ensure that the <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/gnunet_taler_agreement.tex";
+"\">GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative "
+"development</a> of the GNUnet and GNU Taler projects is satisfied. </p>"
msgstr ""
#: template/copyright.html.j2:22
msgid ""
-"<p>The agreements ensure that the code will continue to be made available"
-" under free software licenses, but gives developers the freedom to move "
-"code between GNUnet and GNU Taler without worrying about licenses and to "
-"give the company the ability to dual-license (for example, so that we can"
-" distribute via App-stores that are hostile to free software).</p>"
+"<p>The agreements ensure that the code will continue to be made available "
+"under free software licenses, but gives developers the freedom to move code "
+"between GNUnet and GNU Taler without worrying about licenses and to give the "
+"company the ability to dual-license (for example, so that we can distribute "
+"via App-stores that are hostile to free software).</p>"
msgstr ""
#: template/copyright.html.j2:30
msgid ""
-"<p>Minor contributions (basically, anyone without Git access) do not "
-"require copyright assignment. Pseudonymous contributions are accepted, in"
-" this case simply sign the agreement with your pseudonym. Scanned copies "
-"are sufficient, but snail mail is preferred.</p>"
+"<p>Minor contributions (basically, anyone without Git access) do not require "
+"copyright assignment. Pseudonymous contributions are accepted, in this case "
+"simply sign the agreement with your pseudonym. Scanned copies are "
+"sufficient, but snail mail is preferred.</p>"
msgstr ""
#: template/developers.html.j2:5
@@ -620,14 +614,14 @@ msgstr ""
#: template/developers.html.j2:16
msgid ""
-"A list of our Git repositories can be found on our our <a "
-"href=\"https://git.gnunet.org/\";>Git Server</a>."
+"A list of our Git repositories can be found on our our <a href=\"https://git.";
+"gnunet.org/\">Git Server</a>."
msgstr ""
#: template/developers.html.j2:27
msgid ""
-"Technical papers can be found in our <a "
-"href=\"https://old.gnunet.org/bibliography\";>bibliography</a>."
+"Technical papers can be found in our <a href=\"https://old.gnunet.org/";
+"bibliography\">bibliography</a>."
msgstr ""
#: template/developers.html.j2:34
@@ -636,10 +630,10 @@ msgstr ""
#: template/developers.html.j2:37
msgid ""
-"We have a mailing list for developer discussions. You can subscribe to or"
-" read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo";
-"/gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>."
+"We have a mailing list for developer discussions. You can subscribe to or "
+"read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo/";
+"gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-developers</"
+"a>."
msgstr ""
#: template/developers.html.j2:47
@@ -648,9 +642,9 @@ msgstr ""
#: template/developers.html.j2:50
msgid ""
-"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests "
-"to detect regressions and check for portability at <a "
-"href=\"https://old.gnunet.org/buildbot/gnunet/\";>https://old.gnunet.org/buildbot/gnunet/</a>."
+"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests to "
+"detect regressions and check for portability at <a href=\"https://old.gnunet.";
+"org/buildbot/gnunet/\">https://old.gnunet.org/buildbot/gnunet/</a>."
msgstr ""
#: template/developers.html.j2:59
@@ -659,10 +653,9 @@ msgstr ""
#: template/developers.html.j2:62
msgid ""
-"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> "
-"to analyze the code coverage of our tests, the results are available at "
-"<a "
-"href=\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
+"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> to "
+"analyze the code coverage of our tests, the results are available at <a href="
+"\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
msgstr ""
#: template/developers.html.j2:72
@@ -671,9 +664,9 @@ msgstr ""
#: template/developers.html.j2:75
msgid ""
-"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for "
-"performance regression analysis of the exchange backend at <a "
-"href=\"https://old.gnunet.org/gauger/\";>https://old.gnunet.org/gauger/</a>."
+"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for performance "
+"regression analysis of the exchange backend at <a href=\"https://old.gnunet.";
+"org/gauger/\">https://old.gnunet.org/gauger/</a>."
msgstr ""
#: template/download.html.j2:7 template/gnurl.html.j2:209
@@ -682,8 +675,8 @@ msgstr ""
#: template/download.html.j2:11
msgid ""
-"Here you can download releases of our software and find links to the "
-"various versions."
+"Here you can download releases of our software and find links to the various "
+"versions."
msgstr ""
#: template/download.html.j2:17
@@ -705,7 +698,8 @@ msgid "git"
msgstr ""
#: template/download.html.j2:32
-msgid "You can fetch the git tag of version 0.11.x from our development
server:"
+msgid ""
+"You can fetch the git tag of version 0.11.x from our development server:"
msgstr ""
#: template/engage.html.j2:6
@@ -722,18 +716,17 @@ msgstr ""
#: template/ev.html.j2:13
msgid ""
-"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the"
-" \"Verein zur Förderung von GNUnet e.V.\", an association under "
-"German law to support GNUnet development. The Amtsgericht München "
-"registered the association on the 7th of March under VR 205287."
+"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the "
+"\"Verein zur Förderung von GNUnet e.V.\", an association under German "
+"law to support GNUnet development. The Amtsgericht München registered "
+"the association on the 7th of March under VR 205287."
msgstr ""
#: template/ev.html.j2:22
msgid ""
-"The association is officially dedicated to supporting research, "
-"development and education in the area of secure decentralized networking "
-"in general, and GNUnet specifically. This is the official website for the"
-" association."
+"The association is officially dedicated to supporting research, development "
+"and education in the area of secure decentralized networking in general, and "
+"GNUnet specifically. This is the official website for the association."
msgstr ""
#: template/ev.html.j2:31
@@ -742,15 +735,15 @@ msgstr ""
#: template/ev.html.j2:33
msgid ""
-"GNUnet developers with git (write) access can become members to "
-"participate in the decision process and formally support GNUnet e.V. For "
-"this, all you have to do is update the <tt>members.txt</tt> file in the "
-"<a href=\"https://git.gnunet.org/gnunet-ev.git/\";>gnunet-ev</a> "
-"repository. There are no membership dues; however, members are required "
-"to support GNUnet e.V. and in particularly contribute to the technical "
-"development within their means. For further details, we refer to the <a "
-"href=\"https://git.gnunet.org/gnunet-ev.git/\";>Satzung</a> (currently "
-"only available in German, translations welcome)."
+"GNUnet developers with git (write) access can become members to participate "
+"in the decision process and formally support GNUnet e.V. For this, all you "
+"have to do is update the <tt>members.txt</tt> file in the <a href=\"https://";
+"git.gnunet.org/gnunet-ev.git/\">gnunet-ev</a> repository. There are no "
+"membership dues; however, members are required to support GNUnet e.V. and in "
+"particularly contribute to the technical development within their means. For "
+"further details, we refer to the <a href=\"https://git.gnunet.org/gnunet-ev.";
+"git/\">Satzung</a> (currently only available in German, translations "
+"welcome)."
msgstr ""
#: template/ev.html.j2:52
@@ -759,16 +752,13 @@ msgstr ""
#: template/ev.html.j2:54
msgid ""
-"You can find our \"Satzung\", and the list of members under <a "
-"href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex\">https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex</a>. The current board consists of: "
+"You can find our \"Satzung\", and the list of members under <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex\";>https://git.gnunet.";
+"org/gnunet-ev.git/tree/satzung.tex</a>. The current board consists of: "
"<dl><dt>Vorsitz</dt> <dd><a href=\"https://schanzen.eu\";>Martin "
-"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> "
-"<dd>t3sserakt</dd> <dt>Kassenwart</dt> <dd>Florian Dold</dd> "
-"<dt>Beisitzer</dt> <dd> <a "
-"href=\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 "
-"</dd> </dl>"
+"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> <dd>t3sserakt</dd> "
+"<dt>Kassenwart</dt> <dd>Florian Dold</dd> <dt>Beisitzer</dt> <dd> <a href="
+"\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 </dd> </dl>"
msgstr ""
#: template/ev.html.j2:73
@@ -783,77 +773,801 @@ msgstr ""
msgid ""
"Everybody is welcome to support us via donations. For financial "
"contributions, Europeans are able to donate via SEPA. We hope to setup "
-"accounts in other major currency areas in the future. You can also donate"
-" via Bitcoin, routing details are given below. Please note that we are "
-"unable to provide receipts for your donations. If you are planning to "
-"donate a significant amount of money, please contact us first as it might"
-" be better to come to a custom arrangement. <dl><dt>BitCoin</dt> "
+"accounts in other major currency areas in the future. You can also donate "
+"via Bitcoin, routing details are given below. Please note that we are unable "
+"to provide receipts for your donations. If you are planning to donate a "
+"significant amount of money, please contact us first as it might be better "
+"to come to a custom arrangement. <dl><dt>BitCoin</dt> "
"<dd>1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh</dd> <dt>SEPA/IBAN</dt> "
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
-#: template/faq.html.j2:12
-msgid "Is GNUnet ready for use on production systems?"
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
msgstr ""
-#: template/faq.html.j2:14
-msgid ""
-"A: GNUnet is still undergoing major development. It is largely not yet "
-"ready for usage beyond developers. Your mileage will vary depending on "
-"the functionality you use, but you will always likely run into issues "
-"with our current low-level transport system. We are currently in the "
-"process of rewriting it (Project "Transport Next Generation "
-"[TNG]")"
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
msgstr ""
-#: template/faq.html.j2:24
-msgid "Is GNUnet build using distributed ledger technologies?"
+#: template/faq.html.j2:15 template/faq.html.j2:594
+msgid "Error messages"
+msgstr ""
+
+#: template/faq.html.j2:16 template/faq.html.j2:696
+msgid "File-sharing"
+msgstr ""
+
+#: template/faq.html.j2:17 template/faq.html.j2:872
+msgid "Contributing"
msgstr ""
#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr ""
+
+#: template/faq.html.j2:28
msgid ""
-"A: No. GNUnet is a new network protocol stack for building secure, "
-"distributed, and privacy-preserving applications. While a ledger could be"
-" built using GNUnet, we currently have no plans in doing so."
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
+"the #gnunet IRC on irc.freenode.net."
msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
+msgstr ""
+
+#: template/faq.html.j2:38
msgid ""
-"I receive many "WARNING Calculated flow delay for X at Y for "
-"Z". Should I worry?"
+"A: The general answer is, when it is ready. A better answer may be: earlier "
+"if you contribute (test, debug, code, document). Every release will be "
+"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://";
+"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
+"the RSS feed of this site to automatically receive a notification."
+msgstr ""
+
+#: template/faq.html.j2:49
+msgid "Is the code free?"
msgstr ""
-#: template/faq.html.j2:37
+#: template/faq.html.j2:51
msgid ""
-"A: Right now, this is expected and a known cause for high latency in "
-"GNUnet. We have started a major rewrite to address this and other "
-"problems, but until the Transport Next Generation (TNG) is ready, these "
-"warnings are expected."
+"A: GNUnet is free software, available under the <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
msgstr ""
-#: template/faq.html.j2:46
+#: template/faq.html.j2:58
+msgid "Are there any known bugs?"
+msgstr ""
+
+#: template/faq.html.j2:60
+msgid ""
+"A: We track the list of currently known bugs in the <a href=\"https://bugs.";
+"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
+"directly to developers or the developer mailing list. This is discouraged "
+"since developers often do not have the time to feed these bugs back into the "
+"Mantis database. Please report bugs directly to the bug tracking system. If "
+"you believe a bug is sensitive, you can set its view status to private (this "
+"should be the exception)."
+msgstr ""
+
+#: template/faq.html.j2:73 template/faq.html.j2:193
msgid "Is there a graphical user interface?"
msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:75
msgid ""
"A: gnunet-gtk is a separate download. The package contains various GTK+ "
"based graphical interfaces, including a graphical tool for configuration."
msgstr ""
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr ""
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called ""
+"proof-of-work" which is used to convince the network that your peer is "
+"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
+"on the network size estimator). The calculation is expected to take a few "
+"days, depending on how fast your CPU is. If the CPU load is creating a "
+"problem for you, you can set the value "WORKDELAY" in the ""
+"nse" section of your configuration file to a higher value. The default "
+"is "5 ms"."
+msgstr ""
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr ""
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
+"connections and, with the Tor Browser Bundle, for the Web in particular. "
+"GNUnet does not really have one focus; our theme is secure decentralized "
+"networking, but that is too broad to be called a focus."
+msgstr ""
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr ""
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost no "
+"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
+"using onion (or garlic) routing as the basis for various (anonymized) "
+"applications. I2P is largely used via a Web frontend."
+msgstr ""
+
+#: template/faq.html.j2:124
+msgid "Is GNUnet ready for use on production systems?"
+msgstr ""
+
+#: template/faq.html.j2:126
+msgid ""
+"A: GNUnet is still undergoing major development. It is largely not yet ready "
+"for usage beyond developers. Your mileage will vary depending on the "
+"functionality you use, but you will always likely run into issues with our "
+"current low-level transport system. We are currently in the process of "
+"rewriting it (Project "Transport Next Generation [TNG]")"
+msgstr ""
+
+#: template/faq.html.j2:136
+msgid "Is GNUnet build using distributed ledger technologies?"
+msgstr ""
+
+#: template/faq.html.j2:138
+msgid ""
+"A: No. GNUnet is a new network protocol stack for building secure, "
+"distributed, and privacy-preserving applications. While a ledger could be "
+"built using GNUnet, we currently have no plans in doing so."
+msgstr ""
+
+#: template/faq.html.j2:151
+msgid "What can I do with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
+"do more than just one thing. Naturally, the implementation and documentation "
+"of some of the features that exist are more advanced than others."
+msgstr ""
+
+#: template/faq.html.j2:160
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
+"decentralized and censorship-resistant replacement for DNS and a mechanism "
+"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
+msgstr ""
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We "
+"recommend that you use Tor for anonymous surfing."
+msgstr ""
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr ""
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+
+#: template/faq.html.j2:195
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the "
+"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
+"that integrates most of the other GUIs in one window. One exception is "
+"gnunet-setup, which must still be run separately at this time (as setup "
+"requires the peer to be stopped)."
+msgstr ""
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr ""
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
+"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
+"FreeBSD and macOS. We have reports of working versions on many other GNU/"
+"Linux distributions; in the past we had reports of working versions on "
+"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
+"so if you cannot get GNUnet to work on those systems please let us know."
+msgstr ""
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr ""
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a default "
+"configuration of top-level domains. The governance of this default "
+"configuration is not yet established. In any case, the user will be able to "
+"modify this configuration at will. We expect normal users to have no need to "
+"edit their own GNS zone(s) unless they host services themselves."
+msgstr ""
+
+#: template/faq.html.j2:241
+msgid "Where is the per-user GNS database kept?"
+msgstr ""
+
+#: template/faq.html.j2:243
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet peer. "
+"Now, a user may run multiple GNUnet peers, in which case the database could "
+"be kept at each peer (however, we don't have code for convenient "
+"replication). Similarly, multiple GNUnet peers can share one instance of the "
+"database --- the "gnunet-service-namestore" can be accessed from "
+"remote (via TCP). The actual data can be stored in a Postgres database, for "
+"which various replication options are again applicable. Ultimately, there "
+"are many options for how users can store (and secure) their GNS database."
+msgstr ""
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases "
+"will only grow to a few tens of thousands of entries, small enough to fit "
+"even on mobile devices."
+msgstr ""
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr ""
+
+#: template/faq.html.j2:272
+msgid ""
+"A: We believe so, as there is no entity that any government could force to "
+"change the mapping for a name except for each individual user (and then the "
+"changes would only apply to the names that this user is the authority for). "
+"So if everyone used GNS, the only practical attack of a government would be "
+"to force the operator of a server to change the GNS records for his server "
+"to point elsewhere. However, if the owner of the private key for a zone is "
+"unavailable for enforcement, the respective zone cannot be changed and any "
+"other zone delegating to this zone will achieve proper resolution."
+msgstr ""
+
+#: template/faq.html.j2:286
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr ""
+
+#: template/faq.html.j2:288
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
+"there are still registrars that determine who owns a name. <br><br> With "
+"GNS, we decentralize the database and also decentralize the responsibility "
+"for naming: each user runs his own personal root zone and is thus in "
+"complete control of the names he uses. GNS also has many additional features "
+"(to keep names short and enable migration) which don't even make sense in "
+"the context of CoDoNS."
+msgstr ""
+
+#: template/faq.html.j2:304
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr ""
+
+#: template/faq.html.j2:306
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared via "
+"delegation, and thus mappings will only change if the user responsible for "
+"the name (the authority) manually changes the record."
+msgstr ""
+
+#: template/faq.html.j2:320
+msgid "What is the difference between GNS and ODDNS?"
+msgstr ""
+
+#: template/faq.html.j2:322
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+
+#: template/faq.html.j2:333
+msgid "What is the difference between GNS and Namecoin?"
+msgstr ""
+
+#: template/faq.html.j2:340
+msgid "What is the difference between GNS and Handshake?"
+msgstr ""
+
+#: template/faq.html.j2:346
+msgid "What is the difference between GNS and ENS?"
+msgstr ""
+
+#: template/faq.html.j2:352
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr ""
+
+#: template/faq.html.j2:354
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks on "
+"DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from "
+"the DNS hierarchy."
+msgstr ""
+
+#: template/faq.html.j2:367
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the style "
+"of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:369
+msgid ""
+"A: For security, it is well known that an initial trust path between the two "
+"parties must exist. However, for applications where this is not required, "
+"weaker mechanisms can be used. For example, we have implemented a first-come-"
+"first-served (FCFS) authority which allows arbitrary users to register "
+"arbitrary names. The key of this authority is included with every GNUnet "
+"installation. Thus, any name registered with FCFS is in fact global and "
+"requires no further introduction. However, the security of these names "
+"depends entirely on the trustworthiness of the FCFS authority. The authority "
+"can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:384
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name in "
+"GNS?"
+msgstr ""
+
+#: template/faq.html.j2:386
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "legitimate" "
+"domain owner. Any user can claim any name (as his preferred name or ""
+"pseudonym") in his NICK record. Similarly, all other users can choose "
+"to ignore this preference and use a name of their choice (or even assign no "
+"name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:397
+msgid ""
+"Did you consider the privacy implications of making your personal GNS zone "
+"visible?"
+msgstr ""
+
+#: template/faq.html.j2:399
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not set. "
+"Thus, users have full control over what information about their zones is "
+"made public."
+msgstr ""
+
+#: template/faq.html.j2:409
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:411
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary because "
+"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
+"of virtual hosting. However, LEHOs are also useful to help with X.509 "
+"certificate validation (as they specify for which legacy hostname the "
+"certificate should be valid). Also, even with IPv6 fully deployed and ""
+"infinite" IP addresses being available, we're not sure that virtual "
+"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
+"become commonplace, GNS should work with today's networks."
+msgstr ""
+
+#: template/faq.html.j2:425
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:427
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. As "
+"trust relationships evolve, mappings would change their meaning as they "
+"cross each others thresholds. We decided that the resulting unpredictability "
+"of the resolution process was not acceptable. Furthermore, trust and "
+"consensus might be easy to manipulate by adversaries."
+msgstr ""
+
+#: template/faq.html.j2:438
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:440
+msgid ""
+"A: The owner of a private key can create a revocation message. This one can "
+"then be flooded throughout the overlay network, creating a copy at all "
+"peers. Before using a public key, peers check if that key has been revoked. "
+"All names that involve delegation via a revoked zone will then fail to "
+"resolve. Peers always automatically check for the existence of a revocation "
+"message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:452
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:454
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:468
+msgid ""
+"How can a GNS zone maintain several name servers, e.g. for load balancing?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share "
+"the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:483
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names are "
+"not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on your "
+"application, HTTPS may not be worth the cost. However, for users that are "
+"experiencing censorship (or are concerned about it), giving up globally "
+"unique names may very well be worth the cost. After all, what is a ""
+"globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:499
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:501
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by IANA/ICANN. "
+"This centralization creates vulnerabilities. For example, the US government "
+"was able to reassign the management of the country-TLDs of Afganistan and "
+"Iraq during the wars at the beginning of the 21st century."
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:514
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
+"so blocking a particular IP address causes much more collateral damage than "
+"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
+"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
+"censorship resistant naming system. Accessing Tor's ".onion" "
+"namespace currently requires users to use unmemorable cryptographic "
+"identifiers. With nicer names, Tor and tor2web-like services would be even "
+"easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:533
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:535
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can use "
+"GNS to perform name resolution as well as any normal user. Naturally, while "
+"we typically expect normal users to install custom software for name "
+"resolution, this is unlikely to work for search engines today. However, the "
+"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
+"they can still index GNS resources. However, as using DNS2GNS gateways "
+"breaks the cryptographic chain of trust, legacy search engines will "
+"obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:549
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:551
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was designed "
+"to interoperate with DNS as much as possible, and to also work as much as "
+"possible with the existing Web infrastructure. UIA is not at all concerned "
+"about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:564
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:566
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you know "
+"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
+"and can thus decide how much you trust the result. Naturally, the trusted-"
+"computing base (TCB) can become arbitrarily large this way --- however, "
+"given the name length restriction, for an individual name it is always less "
+"than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:578
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part of "
+"the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:580
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects the "
+""_Service._Proto" syntax, converts "Service" to the "
+"corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when the "
+"result is presented, GNS looks for the GNS-specific "BOX" record "
+"type. A BOX record is a record that contains another record (such as SRV or "
+"TLSA records) and adds a service and protocol number (and the original boxed "
+"record type) to it."
+msgstr ""
+
+#: template/faq.html.j2:596
+msgid ""
+"I receive many "WARNING Calculated flow delay for X at Y for Z". "
+"Should I worry?"
+msgstr ""
+
+#: template/faq.html.j2:598
+msgid ""
+"A: Right now, this is expected and a known cause for high latency in GNUnet. "
+"We have started a major rewrite to address this and other problems, but "
+"until the Transport Next Generation (TNG) is ready, these warnings are "
+"expected."
+msgstr ""
+
+#: template/faq.html.j2:607
+msgid "Error opening `/dev/net/tun': No such file or directory?"
+msgstr ""
+
+#: template/faq.html.j2:609
+msgid ""
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:621
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
+"dns)?"
+msgstr ""
+
+#: template/faq.html.j2:623
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check if "
+"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:635
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:637
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if "
+"your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:645
+msgid ""
+"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:647
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if you "
+"compiled GNUnet the normal way and/or used a binary package, that is highly "
+"unlikely. The more common cause is that you installed GNUnet to a directory "
+"that your linker does not search. There are several ways to fix this that "
+"are described below. If you are 'root' and you installed to a system folder "
+"(such as /usr/local), you want to add the libraries to the system-wide "
+"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
+"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
+"similar path, you obviously have to change \"/usr/local\" accordingly. If "
+"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
+"$USER/\", then you can explicitly tell your linker to search a particular "
+"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
+"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
+"you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:673
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the \"$\") "
+"to your .bashrc or .profile file. You will have to logout and login again to "
+"have this new profile be applied to all shells (including your desktop "
+"environment)."
+msgstr ""
+
+#: template/faq.html.j2:680
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:682
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
+"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
+"always refer to harmless events that require no action. For example, GNUnet "
+"may use an INFO message to indicate that it is currently performing an "
+"expensive operation that will take some time. GNUnet will also use INFO "
+"messages to display information about important configuration values."
+msgstr ""
+
+#: template/faq.html.j2:698
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:700
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
+"P2P networks, GNUnet was designed with security in mind as the highest "
+"priority. We intend on producing a network with comprehensive security "
+"features. Many other P2P networks are open to a wide variety of attacks, and "
+"users have little privacy. GNUnet is also Free Software and thus the source "
+"code is available, so you do not have to worry about being spied upon by the "
+"software. The following table summarises the main differences between GNUnet "
+"and other systems. The information is accurate to the best of our knowledge. "
+"The comparison is difficult since there are sometimes differences between "
+"various implementations of (almost) the same protocol. In general, we pick a "
+"free implementation as the reference implementation since it is possible to "
+"inspect the free code. Also, all of these systems are changing over time and "
+"thus the data below may not be up-to-date. If you find any flaws, please let "
+"us know. Finally, the table is not saying terribly much (it is hard to "
+"compare these systems this briefly), so if you want the real differences, "
+"read the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:814
+msgid ""
+"Another important point of reference are the various anonymous peer-to-peer "
+"networks. Here, there are differences in terms of application domain and how "
+"specifically anonymity is achieved. Anonymous routing is a hard research "
+"topic, so for a superficial comparisson like this one we focus on the "
+"latency. Another important factor is the programming language. Type-safe "
+"languages may offer certain security benefits; however, this may come at the "
+"cost of significant increases in resource consumption which in turn may "
+"reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:827
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:829
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of the "
+"same techniques used to generate reasonable passwords to defend against such "
+"an attack. In any event, we are not trying to hide content; thus, unless the "
+"user is trying to insert information into the network that can only be "
+"shared with a small group of people, there is no real reason to try to "
+"obfuscate the content by choosing a difficult keyword anyway."
+msgstr ""
+
+#: template/faq.html.j2:843
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:845
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all "
+"users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell which "
+"of the peers in the group originated the message. In other words, it should "
+"be difficult to impossible for an adversary to distinguish between the "
+"originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:857
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:859
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
+"its public key) and has a number of addresses it is reachable by (may have "
+"no addresses, for instance when it's behind a NAT). You specify bandwidth "
+"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
+"(how large your on-disk block storage is) . Your node will then proceed to "
+"connect to other nodes, becoming part of the network."
+msgstr ""
+
+#: template/faq.html.j2:874
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:876
+msgid ""
+"A: First, you need to register an account with our weblate system. Please "
+"send an e-mail with the desired target language to translators@gnunet.org or "
+"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
+"sufficient permissions will then grant you access. Naturally, any abuse will "
+"result in the loss of permissions."
+msgstr ""
+
+#: template/faq.html.j2:888
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:890
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly implement. "
+"The best way to actually get a new feature implemented is to do it yourself "
+"--- and to then send us a patch."
+msgstr ""
+
#: template/glossary.html.j2:12
msgid "Ego"
msgstr ""
#: template/glossary.html.j2:14
msgid ""
-"We use the term \"Ego\" to refer to the fact that users in GNUnet can "
-"have multiple unlinkable identities, in the sense of alter egos. The "
-"ability to have more than one identity is crucial, as we may want to keep"
-" our egos for business separate from those we use for political "
-"activities or romance.<br> Egos in GNUnet are technically equivalent to "
-"identities (and the code does not distinguish between them). We simply "
-"sometimes use the term \"ego\" to stress that you can have more than one."
+"We use the term \"Ego\" to refer to the fact that users in GNUnet can have "
+"multiple unlinkable identities, in the sense of alter egos. The ability to "
+"have more than one identity is crucial, as we may want to keep our egos for "
+"business separate from those we use for political activities or romance.<br> "
+"Egos in GNUnet are technically equivalent to identities (and the code does "
+"not distinguish between them). We simply sometimes use the term \"ego\" to "
+"stress that you can have more than one."
msgstr ""
#: template/glossary.html.j2:27
@@ -862,19 +1576,18 @@ msgstr ""
#: template/glossary.html.j2:29
msgid ""
-"In GNUnet users are identified via a public key, and that public key is "
-"then often referred to as the \"Identity\" of the user. However, the "
-"concept is not as draconian as it often is in real life where many are "
-"forced to have one name, one passport and one unique identification "
-"number. <br> As long as identities in GNUnet are simply public keys, "
-"users are free to create any number of identities, and we call those egos"
-" to emphasize the difference. Even though users can create such egos "
-"freely, it is possible to have an ego certified by some certification "
-"authority, resulting in something that more closely resembles the "
-"traditional concept of an identity.<br> For example, a university may "
-"certify the identities of its students such that they can prove that they"
-" are studying. Students may keep their (certified) student identity "
-"separate from other egos that they use for other activities in life."
+"In GNUnet users are identified via a public key, and that public key is then "
+"often referred to as the \"Identity\" of the user. However, the concept is "
+"not as draconian as it often is in real life where many are forced to have "
+"one name, one passport and one unique identification number. <br> As long as "
+"identities in GNUnet are simply public keys, users are free to create any "
+"number of identities, and we call those egos to emphasize the difference. "
+"Even though users can create such egos freely, it is possible to have an ego "
+"certified by some certification authority, resulting in something that more "
+"closely resembles the traditional concept of an identity.<br> For example, a "
+"university may certify the identities of its students such that they can "
+"prove that they are studying. Students may keep their (certified) student "
+"identity separate from other egos that they use for other activities in life."
msgstr ""
#: template/glossary.html.j2:50
@@ -886,10 +1599,10 @@ msgid ""
"A pseudonym is an ego that is specifically intended to not be linked to "
"one's real name. GNUnet users can create many egos, and thus also many "
"pseudonyms. <br> Repeated uses of the same pseudonym are linkable by "
-"definition, as they involve the same public key. Anonymity requires the "
-"use of either the special \"anonymous\" pseudonym (for GNUnet, this is "
-"the neutral element on the elliptic curve) or a throw-away pseudonym that"
-" is only used once."
+"definition, as they involve the same public key. Anonymity requires the use "
+"of either the special \"anonymous\" pseudonym (for GNUnet, this is the "
+"neutral element on the elliptic curve) or a throw-away pseudonym that is "
+"only used once."
msgstr ""
#: template/glossary.html.j2:71
@@ -898,15 +1611,15 @@ msgstr ""
#: template/glossary.html.j2:73
msgid ""
-"The GNU Name System allows every ego (or identity) to securely and "
-"privately associate any number of label-value pairs with an ego. The "
-"values are called record sets following the terminology of the Domain "
-"Name System (DNS). The mapping of labels to record sets for a given ego "
-"is called a namespace. <br> If records are made public and thus "
-"published, it is possible for other users to lookup the record given the "
-"ego's public key and the label. Here, not only the label can thus act as "
-"a passphrase but also the public key -- which despite its name may not be"
-" public knowledge and is never disclosed by the GNS protocol itself."
+"The GNU Name System allows every ego (or identity) to securely and privately "
+"associate any number of label-value pairs with an ego. The values are called "
+"record sets following the terminology of the Domain Name System (DNS). The "
+"mapping of labels to record sets for a given ego is called a namespace. <br> "
+"If records are made public and thus published, it is possible for other "
+"users to lookup the record given the ego's public key and the label. Here, "
+"not only the label can thus act as a passphrase but also the public key -- "
+"which despite its name may not be public knowledge and is never disclosed by "
+"the GNS protocol itself."
msgstr ""
#: template/glossary.html.j2:89
@@ -915,17 +1628,17 @@ msgstr ""
#: template/glossary.html.j2:91
msgid ""
-"A \"peer\" is an instance of GNUnet with its own per-instance public key "
-"and network addresses. Technically, it is possible to run multiple peers "
-"on the same host, but this only makes sense for testing. <br> By design "
-"GNUnet supports multiple users to share the same peer, just as UNIX is a "
-"multi-user system. A \"peer\" typically consists of a set of foundational"
-" GNUnet services running as the \"gnunet\" user and allowing all users in"
-" the \"gnunet\" group to utilize the API. On multi-user systems, "
-"additional \"personalized\" services may be required per user. <br> While"
-" peers are also identified by public keys, these public keys are "
-"completely unrelated to egos or identities. Namespaces cannot be "
-"associated with a peer, only with egos."
+"A \"peer\" is an instance of GNUnet with its own per-instance public key and "
+"network addresses. Technically, it is possible to run multiple peers on the "
+"same host, but this only makes sense for testing. <br> By design GNUnet "
+"supports multiple users to share the same peer, just as UNIX is a multi-user "
+"system. A \"peer\" typically consists of a set of foundational GNUnet "
+"services running as the \"gnunet\" user and allowing all users in the "
+"\"gnunet\" group to utilize the API. On multi-user systems, additional "
+"\"personalized\" services may be required per user. <br> While peers are "
+"also identified by public keys, these public keys are completely unrelated "
+"to egos or identities. Namespaces cannot be associated with a peer, only "
+"with egos."
msgstr ""
#: template/gns.html.j2:13 template/gnurl.html.j2:60
@@ -935,28 +1648,24 @@ msgstr ""
#: template/gns.html.j2:15
msgid ""
"The Domain Name System today enables traffic amplification attacks, "
-"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive "
-"cyber war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as "
-"DoT, DoH, DNSSEC, DPRIVE and the like will not fix this. This is why we "
-"built the GNU Name System (GNS), a secure, decentralized name system "
-"built on top of GNUnet."
+"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive cyber "
+"war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as DoT, DoH, "
+"DNSSEC, DPRIVE and the like will not fix this. This is why we built the GNU "
+"Name System (GNS), a secure, decentralized name system built on top of "
+"GNUnet."
msgstr ""
#: template/gns.html.j2:28
msgid "Overview"
msgstr ""
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
-
#: template/gns.html.j2:39
msgid ""
"The GNU Name System (GNS) is secure and decentralized naming system. It "
-"allows its users to register names as top-level domains (TLDs) and "
-"resolve other namespaces within their TLDs. <br/> GNS is designed to "
-"provide: <ul> <li>Censorship resistance</li> <li>Query privacy</li> "
-"<li>Secure name resolution</li> <li>Compatibility with DNS</li>"
+"allows its users to register names as top-level domains (TLDs) and resolve "
+"other namespaces within their TLDs. <br/> GNS is designed to provide: <ul> "
+"<li>Censorship resistance</li> <li>Query privacy</li> <li>Secure name "
+"resolution</li> <li>Compatibility with DNS</li>"
msgstr ""
#: template/gns.html.j2:52
@@ -965,23 +1674,23 @@ msgstr ""
#: template/gnurl.html.j2:21
msgid ""
-"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support "
-"only HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend "
-"(GnuTLS) to ensure a small footprint and uniform experience for "
-"developers regardless of how libcurl was compiled."
+"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support only "
+"HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend (GnuTLS) to "
+"ensure a small footprint and uniform experience for developers regardless of "
+"how libcurl was compiled."
msgstr ""
#: template/gnurl.html.j2:30
msgid ""
-"Our main usecase is for GNUnet and Taler, but it might be usable for "
-"others, hence we're releasing the code to the general public."
+"Our main usecase is for GNUnet and Taler, but it might be usable for others, "
+"hence we're releasing the code to the general public."
msgstr ""
#: template/gnurl.html.j2:37
msgid ""
"libgnurl is released under the same license as libcurl. Please read the "
-"README for instructions, as you must supply the correct options to "
-"configure to get a proper build of libgnurl."
+"README for instructions, as you must supply the correct options to configure "
+"to get a proper build of libgnurl."
msgstr ""
#: template/gnurl.html.j2:48
@@ -990,58 +1699,55 @@ msgstr ""
#: template/gnurl.html.j2:50
msgid ""
-"Large parts of the following 6 paragraphs are old and need to be "
-"rewritten."
+"Large parts of the following 6 paragraphs are old and need to be rewritten."
msgstr ""
#: template/gnurl.html.j2:62
msgid ""
-"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, "
-"but other variants are used by some distributions. Supporting other "
-"crypto backends would again expose us to a wider array of security "
-"issues, may create licensing issues and most importantly introduce new "
-"bugs as some crypto backends are known to introduce subtle runtime "
-"issues. While it is possible to have two versions of libcurl installed on"
-" the same system, this is error-prone, especially as if we are linked "
-"against the wrong version, the bugs that arise might be rather subtle."
+"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, but "
+"other variants are used by some distributions. Supporting other crypto "
+"backends would again expose us to a wider array of security issues, may "
+"create licensing issues and most importantly introduce new bugs as some "
+"crypto backends are known to introduce subtle runtime issues. While it is "
+"possible to have two versions of libcurl installed on the same system, this "
+"is error-prone, especially as if we are linked against the wrong version, "
+"the bugs that arise might be rather subtle."
msgstr ""
#: template/gnurl.html.j2:75
msgid ""
-"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, "
-"it would anyway be necessary to recompile cURL for GNUnet. But what "
-"happens if one links cURL against this version of GnuTLS? Well, first one"
-" would install GnuTLS by hand in the system. Then, we build cURL. cURL "
-"will build against it just fine, but the linker will eventually complain "
-"bitterly. The reason is that cURL also links against a bunch of other "
-"system libraries (gssapi, ldap, ssh2, rtmp, krb5, sasl2, see discussion "
-"on obscure protocols above), which --- as they are part of the "
-"distribution --- were linked against an older version of GnuTLS. As a "
-"result, the same binary would be linked against two different versions of"
-" GnuTLS. That is typically a recipe for disaster. Thus, in order to avoid"
-" updating a dozen system libraries (and having two versions of those "
-"installed), it is necessary to disable all of those cURL features that "
-"GNUnet does not use, and there are many of those. For GNUnet, the more "
-"obscure protocols supported by cURL are close to dead code --- mostly "
-"harmless, but not useful. However, as some application may use one of "
-"those features, distributions are typically forced to enable all of those"
-" features, and thus including security issues that might arise from that "
-"code."
+"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, it "
+"would anyway be necessary to recompile cURL for GNUnet. But what happens if "
+"one links cURL against this version of GnuTLS? Well, first one would install "
+"GnuTLS by hand in the system. Then, we build cURL. cURL will build against "
+"it just fine, but the linker will eventually complain bitterly. The reason "
+"is that cURL also links against a bunch of other system libraries (gssapi, "
+"ldap, ssh2, rtmp, krb5, sasl2, see discussion on obscure protocols above), "
+"which --- as they are part of the distribution --- were linked against an "
+"older version of GnuTLS. As a result, the same binary would be linked "
+"against two different versions of GnuTLS. That is typically a recipe for "
+"disaster. Thus, in order to avoid updating a dozen system libraries (and "
+"having two versions of those installed), it is necessary to disable all of "
+"those cURL features that GNUnet does not use, and there are many of those. "
+"For GNUnet, the more obscure protocols supported by cURL are close to dead "
+"code --- mostly harmless, but not useful. However, as some application may "
+"use one of those features, distributions are typically forced to enable all "
+"of those features, and thus including security issues that might arise from "
+"that code."
msgstr ""
#: template/gnurl.html.j2:99
msgid ""
-"So to use a modern version of GnuTLS, a sane approach is to disable all "
-"of the \"optional\" features of cURL that drag in system libraries that "
-"link against the older GnuTLS. That works, except that one should then "
-"NEVER install that version of libcurl in say /usr or /usr/local, as that "
-"may break other parts of the system that might depend on these features "
-"that we just disabled. Libtool versioning doesn't help here, as it is not"
-" intended to deal with libraries that have optional features. Naturally, "
-"installing cURL somewhere else is also problematic, as we now need to be "
-"really careful that the linker will link GNUnet against the right "
-"version. Note that none of this can really be trivially fixed by the cURL"
-" developers."
+"So to use a modern version of GnuTLS, a sane approach is to disable all of "
+"the \"optional\" features of cURL that drag in system libraries that link "
+"against the older GnuTLS. That works, except that one should then NEVER "
+"install that version of libcurl in say /usr or /usr/local, as that may break "
+"other parts of the system that might depend on these features that we just "
+"disabled. Libtool versioning doesn't help here, as it is not intended to "
+"deal with libraries that have optional features. Naturally, installing cURL "
+"somewhere else is also problematic, as we now need to be really careful that "
+"the linker will link GNUnet against the right version. Note that none of "
+"this can really be trivially fixed by the cURL developers."
msgstr ""
#: template/gnurl.html.j2:118
@@ -1052,19 +1758,19 @@ msgstr ""
#, python-format
msgid ""
"How does forking fix it? Easy. First, we can get rid of all of the "
-"compatibility issues --- if you use libgnurl, you state that you "
-"don't need anything but HTTP/HTTPS. Those applications that need "
-"more, should stick with the original cURL. Those that do not, can choose "
-"to move to something simpler. As the library gets a new name, we do not "
-"have to worry about tons of packages breaking as soon as one rebuilds it."
-" So renaming itself and saying that \"libgnurl = libcurl with only "
-"HTTP/HTTPS support and GnuTLS\" fixes 99%% of the problems that darkened "
-"my mood. Note that this pretty much CANNOT be done without a fork, as "
-"renaming is an essential part of the fix. Now, there might be creative "
-"solutions to achieve the same thing within the standard cURL build "
-"system, but this was deemed to be too much work when gnurl was originally"
-" started. The changes libgnurl makes to curl are miniscule and can easily"
-" be applied again and again whenever libcurl makes a new release."
+"compatibility issues --- if you use libgnurl, you state that you don't "
+"need anything but HTTP/HTTPS. Those applications that need more, should "
+"stick with the original cURL. Those that do not, can choose to move to "
+"something simpler. As the library gets a new name, we do not have to worry "
+"about tons of packages breaking as soon as one rebuilds it. So renaming "
+"itself and saying that \"libgnurl = libcurl with only HTTP/HTTPS support and "
+"GnuTLS\" fixes 99%% of the problems that darkened my mood. Note that this "
+"pretty much CANNOT be done without a fork, as renaming is an essential part "
+"of the fix. Now, there might be creative solutions to achieve the same thing "
+"within the standard cURL build system, but this was deemed to be too much "
+"work when gnurl was originally started. The changes libgnurl makes to curl "
+"are miniscule and can easily be applied again and again whenever libcurl "
+"makes a new release."
msgstr ""
#: template/gnurl.html.j2:142
@@ -1073,14 +1779,13 @@ msgstr ""
#: template/gnurl.html.j2:144
msgid ""
-"Projects that use cURL only for HTTP/HTTPS and that would work with "
-"GnuTLS should be able to switch to libgnurl by changing \"-lcurl\" to "
-"\"-lgnurl\". That's it. No changes to the source code should be "
-"required, as libgnurl strives for bug-for-bug compatibility with the "
-"HTTP/HTTPS/GnuTLS subset of cURL. We might add new features relating to "
-"this core subset if they are proposed, but so far we have kept our "
-"changes minimal and no additions to the original curl source have been "
-"written."
+"Projects that use cURL only for HTTP/HTTPS and that would work with GnuTLS "
+"should be able to switch to libgnurl by changing \"-lcurl\" to \"-lgnurl\". "
+"That's it. No changes to the source code should be required, as libgnurl "
+"strives for bug-for-bug compatibility with the HTTP/HTTPS/GnuTLS subset of "
+"cURL. We might add new features relating to this core subset if they are "
+"proposed, but so far we have kept our changes minimal and no additions to "
+"the original curl source have been written."
msgstr ""
#: template/gnurl.html.j2:161
@@ -1089,15 +1794,15 @@ msgstr ""
#: template/gnurl.html.j2:163
msgid ""
-"libgnurl and gnurl are not intended to be used as a replacement for curl "
-"for users: <br> This does not mean there is no confidence in the work "
-"done with gnurl, it means that tools which expect curl or libcurl will "
-"not make use of a different named binary and library. If you know what "
-"you are doing, you should be able to use gnurl as part of your tooling in"
-" place of curl. We do not recommend to do so however, as the only usage "
-"it is tested for <em>so far</em> is as part of Taler's and "
-"GNunet's build-system. <br> Since no conflicts in filenames occur you"
-" are not expected to remove curl to make use of gnurl and viceversa."
+"libgnurl and gnurl are not intended to be used as a replacement for curl for "
+"users: <br> This does not mean there is no confidence in the work done with "
+"gnurl, it means that tools which expect curl or libcurl will not make use of "
+"a different named binary and library. If you know what you are doing, you "
+"should be able to use gnurl as part of your tooling in place of curl. We do "
+"not recommend to do so however, as the only usage it is tested for <em>so "
+"far</em> is as part of Taler's and GNunet's build-system. <br> Since "
+"no conflicts in filenames occur you are not expected to remove curl to make "
+"use of gnurl and viceversa."
msgstr ""
#: template/gnurl.html.j2:188
@@ -1110,16 +1815,15 @@ msgstr ""
#: template/gnurl.html.j2:211
msgid ""
-"Releases are published on <a "
-"href=\"https://ftpmirror.gnu.org/gnu/gnunet/\";>ftpmirror.gnu.org/gnu/gnunet</a>."
-" gnurl is available from within a variety of distributions and package "
-"managers. Some Package Managers which include gnurl are: <a "
-"href=\"https://www.gnu.org/software/guix/\";>GNU Guix</a> (available as "
-"\"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> through the "
-"collaborative ebuild collection <a href=\"https://git.gnunet.org";
-"/youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a "
-"href=\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a "
-"href=\"https://pkgsrc.org\";>pkgsrc</a>."
+"Releases are published on <a href=\"https://ftpmirror.gnu.org/gnu/gnunet/";
+"\">ftpmirror.gnu.org/gnu/gnunet</a>. gnurl is available from within a "
+"variety of distributions and package managers. Some Package Managers which "
+"include gnurl are: <a href=\"https://www.gnu.org/software/guix/\";>GNU Guix</"
+"a> (available as \"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> "
+"through the collaborative ebuild collection <a href=\"https://git.gnunet.org/";
+"youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a href="
+"\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a href=\"https://";
+"pkgsrc.org\">pkgsrc</a>."
msgstr ""
#: template/gnurl.html.j2:228
@@ -1128,17 +1832,17 @@ msgstr ""
#: template/gnurl.html.j2:230
msgid ""
-"We suggest to closely follow release announcements, as they might "
-"indicate changes in how gnurl is to be build. <br> If your package "
-"manager provides a binary build or build instructions to build gnurl from"
-" source automated and integrated with your environment, we strongly "
-"suggest to use this binary build. <br> There are two ways to build gnurl."
-" The first one builds from the most recent git tag, the second one uses "
-"the distributed tarball. Distributors generally are supposed to build "
-"from the tarball, but we describe both methods here. Both methods are "
-"written with a NetBSD 9 userland in mind, substitute tools as necessary. "
-"<br> You should <b>avoid</b> building gnurl from the tip of the default "
-"git branch, as only tags are considered to be stable and approved builds."
+"We suggest to closely follow release announcements, as they might indicate "
+"changes in how gnurl is to be build. <br> If your package manager provides a "
+"binary build or build instructions to build gnurl from source automated and "
+"integrated with your environment, we strongly suggest to use this binary "
+"build. <br> There are two ways to build gnurl. The first one builds from the "
+"most recent git tag, the second one uses the distributed tarball. "
+"Distributors generally are supposed to build from the tarball, but we "
+"describe both methods here. Both methods are written with a NetBSD 9 "
+"userland in mind, substitute tools as necessary. <br> You should <b>avoid</"
+"b> building gnurl from the tip of the default git branch, as only tags are "
+"considered to be stable and approved builds."
msgstr ""
#: template/gnurl.html.j2:251
@@ -1147,8 +1851,8 @@ msgstr ""
#: template/gnurl.html.j2:253
msgid ""
-"If you want to verify the signature, install an OpenPGP compatible tool "
-"such as security/gnupgp2 (and set it up). Assuming you use pkgin:"
+"If you want to verify the signature, install an OpenPGP compatible tool such "
+"as security/gnupgp2 (and set it up). Assuming you use pkgin:"
msgstr ""
#: template/gnurl.html.j2:267
@@ -1161,8 +1865,7 @@ msgstr ""
#: template/gnurl.html.j2:276
msgid ""
-"Fetch the release, the signature, the checksum file as well as its "
-"signature:"
+"Fetch the release, the signature, the checksum file as well as its signature:"
msgstr ""
#: template/gnurl.html.j2:295
@@ -1211,8 +1914,8 @@ msgstr ""
#: template/gnurl.html.j2:371
msgid ""
-"Follow the steps above, but instead of downloading the tarball, clone the"
-" git tag you want to build from."
+"Follow the steps above, but instead of downloading the tarball, clone the "
+"git tag you want to build from."
msgstr ""
#: template/gnurl.html.j2:382
@@ -1221,10 +1924,9 @@ msgstr ""
#: template/gnurl.html.j2:384
msgid ""
-"You can report bugs on our bug tracker: <a "
-"href=\"https://bugs.gnunet.org/\";>bugs.gnunet.org</a>. Alternatively you "
-"can use our bug mailinglist, but we prefer to track bugs on the "
-"bugtracker."
+"You can report bugs on our bug tracker: <a href=\"https://bugs.gnunet.org/";
+"\">bugs.gnunet.org</a>. Alternatively you can use our bug mailinglist, but "
+"we prefer to track bugs on the bugtracker."
msgstr ""
#: template/gnurl.html.j2:395
@@ -1235,10 +1937,9 @@ msgstr ""
msgid ""
"gnurl/libgnurl is looking for a new maintainer. Releases after version "
"7.69.1 and up to version 7.72.0 were signed with the OpenPGP Key "
-"<b>0xD6B570842F7E7F8D</b> (<a "
-"href=\"https://keys.openpgp.org/search?q=6115012DEA3026F62A98A556D6B570842F7E7F8D\";>keys.openpgp.org</a>),"
-" with the key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E"
-" 7F8D</b>."
+"<b>0xD6B570842F7E7F8D</b> (<a href=\"https://keys.openpgp.org/search?";
+"q=6115012DEA3026F62A98A556D6B570842F7E7F8D\">keys.openpgp.org</a>), with the "
+"key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E 7F8D</b>."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:7
@@ -1252,68 +1953,65 @@ msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:18
msgid ""
"In the context of Google Summer of Code 2018, my mentor (Martin "
-"Schanzenbach) and I have worked on creating and extending the REST API of"
-" GNUnet. Currently, we mirrored the functionality of following commands:"
+"Schanzenbach) and I have worked on creating and extending the REST API of "
+"GNUnet. Currently, we mirrored the functionality of following commands:"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:32
msgid ""
-"Additionally, we developed a website with the Javascript framework "
-"Angular 6 and the design framework iotaCSS to use the new REST API. The "
-"REST API of GNUnet is now documented with Sphinx."
+"Additionally, we developed a website with the Javascript framework Angular 6 "
+"and the design framework iotaCSS to use the new REST API. The REST API of "
+"GNUnet is now documented with Sphinx."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:41
msgid ""
-"... when you can use the command line tools? We need to keep in mind, "
-"that everyone has the right to stay secure and private but not everyone "
-"feels comfortable using a terminal. The further developed REST access to "
-"GNUnet APIs in addition to the new web application allows new users to "
-"interact with GNUnet over a well known tool: their browsers. This "
-"addition to the C API and the command line tools may attract new users "
-"and developers."
+"... when you can use the command line tools? We need to keep in mind, that "
+"everyone has the right to stay secure and private but not everyone feels "
+"comfortable using a terminal. The further developed REST access to GNUnet "
+"APIs in addition to the new web application allows new users to interact "
+"with GNUnet over a well known tool: their browsers. This addition to the C "
+"API and the command line tools may attract new users and developers."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:54
msgid ""
"<li> The REST API developed in GNUnet<br> The REST API is already merged "
-"into the gnunet.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet.git/\";>GNUnet Main Git</a>).<br /> "
-"To use the new features, clone the repository and follow the <a "
-"href=\"https://gnunet.org/en/install.html\";>Installation</a> on "
-"gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
-"</li> <li> The Web Application<br> The web application is available under"
-" the gnunet-webui.git repository (<a href=\"https://gnunet.org/git";
-"/gnunet-webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the"
-" newest version of 'node' and 'yarn'. Dependent on your system, you may "
-"need to download newer versions and install them manually and not over "
-"your packet manager. After the installation succeeded, you need to clone "
-"the repository. Then, you need to run \"yarn install\" and \"yarn start\""
-" for testing purposes. To deploy the website (keep in mind, that this "
-"website communicates with another localhost instance) use \"yarn build\" "
-"for building the web application and use the output in the 'dist' "
-"directory. </li> <li> The Documentation<br /> The documentation is "
-"available under the gnunet-rest-api.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet-rest-api.git/\";>GNUnet REST API "
-"Docmentation Git</a>).<br /> Clone the repository and \"make html\". Then"
-" open the 'index.html' under 'build/html/'. </li>"
+"into the gnunet.git repository (<a href=\"https://gnunet.org/git/gnunet.git/";
+"\">GNUnet Main Git</a>).<br /> To use the new features, clone the repository "
+"and follow the <a href=\"https://gnunet.org/en/install.html\";>Installation</"
+"a> on gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
+"</li> <li> The Web Application<br> The web application is available under "
+"the gnunet-webui.git repository (<a href=\"https://gnunet.org/git/gnunet-";
+"webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the newest "
+"version of 'node' and 'yarn'. Dependent on your system, you may need to "
+"download newer versions and install them manually and not over your packet "
+"manager. After the installation succeeded, you need to clone the repository. "
+"Then, you need to run \"yarn install\" and \"yarn start\" for testing "
+"purposes. To deploy the website (keep in mind, that this website "
+"communicates with another localhost instance) use \"yarn build\" for "
+"building the web application and use the output in the 'dist' directory. </"
+"li> <li> The Documentation<br /> The documentation is available under the "
+"gnunet-rest-api.git repository (<a href=\"https://gnunet.org/git/gnunet-rest-";
+"api.git/\">GNUnet REST API Docmentation Git</a>).<br /> Clone the repository "
+"and \"make html\". Then open the 'index.html' under 'build/html/'. </li>"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:91
msgid ""
-"Please, give it a try and contact me, if you find any bugs or "
-"unintentional features. ;)"
+"Please, give it a try and contact me, if you find any bugs or unintentional "
+"features. ;)"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:98
msgid ""
"Right now, the build process of the web application may be a little too "
-"complex for a casual user. We may be able to solve this by using "
-"docker.<br /> Additionally, the web application does not prevent wrong "
-"inputs but responds with error messages. Adding GNUnet Records is "
-"currently only usable for people, who know how a GNS Record looks like. "
-"This can be adapted to each record type.<br /> Last but not least, "
-"additional features, design changes, etc..."
+"complex for a casual user. We may be able to solve this by using docker.<br /"
+"> Additionally, the web application does not prevent wrong inputs but "
+"responds with error messages. Adding GNUnet Records is currently only usable "
+"for people, who know how a GNS Record looks like. This can be adapted to "
+"each record type.<br /> Last but not least, additional features, design "
+"changes, etc..."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:111
@@ -1340,100 +2038,95 @@ msgstr ""
msgid ""
"As a GNU project, GNUnet has participated in the Google Summer of Code "
"(GSoC) for a number of years. This page lists all current, past, and "
-"finished projects. If you want to participate and apply for any of the "
-"ideas for 2020 below or any past project which is not yet finished (or "
-"even your own idea), please contact us either in IRC or mailing list."
+"finished projects. If you want to participate and apply for any of the ideas "
+"for 2020 below or any past project which is not yet finished (or even your "
+"own idea), please contact us either in IRC or mailing list."
msgstr ""
#: template/gsoc.html.j2:34
msgid ""
-"The GNUnet team is currently working on a transport layer rewrite in "
-"order to fix core issues with connectivity. This new component is "
-"currently developed under the name \"TNG\". What is currently known as "
-"\"transport plugins\" will in the TNG be represented as "
-"\"communicators\". Communicators are processes with a well defined API "
-"that allow to connect peers over a specific protocol. The primary "
-"protocol which are already implemented are UNIX sockets, UDP sockets, and"
-" TCP sockets. For a truly resilient network, other connectivity options "
-"such as WiFi mesh, Bluetooth, HTTP(S), QUIC or even more obscure "
-"alternatives such as radio are required. In this project, the goal is to "
-"select, implement and test new communicators. While TNG is not yet ready,"
-" communicators can, by design, be developed and tested against the "
-"current API. We expect that this project can be worked on by multiple "
+"The GNUnet team is currently working on a transport layer rewrite in order "
+"to fix core issues with connectivity. This new component is currently "
+"developed under the name \"TNG\". What is currently known as \"transport "
+"plugins\" will in the TNG be represented as \"communicators\". Communicators "
+"are processes with a well defined API that allow to connect peers over a "
+"specific protocol. The primary protocol which are already implemented are "
+"UNIX sockets, UDP sockets, and TCP sockets. For a truly resilient network, "
+"other connectivity options such as WiFi mesh, Bluetooth, HTTP(S), QUIC or "
+"even more obscure alternatives such as radio are required. In this project, "
+"the goal is to select, implement and test new communicators. While TNG is "
+"not yet ready, communicators can, by design, be developed and tested against "
+"the current API. We expect that this project can be worked on by multiple "
"students as there are a lot of protocols to choose from. The tasks would "
"consist of: <ol> <li>Deciding which communicators to implement.</li> "
-"<li>Test the communicators.</li> <li>Documentation.</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of HTTPS, QUIC, Bluetooth or WiFi.</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Average, but depends on selected protocols. "
-"<br/> <strong>Mentors:</strong> Martin Schanzenbach, t3sserakt"
+"<li>Test the communicators.</li> <li>Documentation.</li> </ol> Advantageous "
+"skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge of HTTPS, QUIC, "
+"Bluetooth or WiFi.</li> </ol> <br/> <strong>Difficulty:</strong> Average, "
+"but depends on selected protocols. <br/> <strong>Mentors:</strong> Martin "
+"Schanzenbach, t3sserakt"
msgstr ""
#: template/gsoc.html.j2:79
msgid ""
-"The REST API currently only supports a single user system. This is an "
-"issue as on multi-user systems, access control must be enfoced on a per-"
-"user basis. In this project, the REST service must be extended to support"
-" user authentication. This includes the correct handling of user context "
-"switches. <ol> <li>Implement user authentication.</li> <li>Test the "
-"access control.</li> <li>Document the changes to the REST API.</li> </ol>"
-" Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of user authentication subsystems on Linux/Unix.</li> <li>REST/HTTP "
-"Authentication methods</li> </ol> <br/> <strong>Difficulty:</strong> "
-"Beginner <br/> <strong>Mentors:</strong> Martin Schanzenbach"
+"The REST API currently only supports a single user system. This is an issue "
+"as on multi-user systems, access control must be enfoced on a per-user "
+"basis. In this project, the REST service must be extended to support user "
+"authentication. This includes the correct handling of user context switches. "
+"<ol> <li>Implement user authentication.</li> <li>Test the access control.</"
+"li> <li>Document the changes to the REST API.</li> </ol> Advantageous skills/"
+"languages/frameworks: <ol> <li>C</li> <li>Knowledge of user authentication "
+"subsystems on Linux/Unix.</li> <li>REST/HTTP Authentication methods</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:111
msgid ""
-"reclaimID is a decentralized identity system build on top of the GNU Name"
-" System. Currently, there is a Webextension which uses the GNUnet <a "
-"href=\"https://rest.gnunet.org\";>REST API</a>. In order to improve "
-"adoption and ease of use, this project aims to include a full GNUnet node"
-" within the Webextention as a fallback. GNUnet can be compiled to Web "
-"Assembly or JavaScript as demonstrated <a "
-"href=\"https://gnunet.io\";>here</a>. The idea is to improve upon this "
-"concept and support more of GNUnet's subsystems. The difficulty of this "
-"project largely depends on the students proficiency with build tools, "
-"emscripten and improvisation skills. There non-exhaustive task list would"
-" be: <ol> <li>Improve existing GNUnet emscripten build to include more "
-"subsystems.</li> <li>Integrate the result into a Webextention.</li> "
+"reclaimID is a decentralized identity system build on top of the GNU Name "
+"System. Currently, there is a Webextension which uses the GNUnet <a href="
+"\"https://rest.gnunet.org\";>REST API</a>. In order to improve adoption and "
+"ease of use, this project aims to include a full GNUnet node within the "
+"Webextention as a fallback. GNUnet can be compiled to Web Assembly or "
+"JavaScript as demonstrated <a href=\"https://gnunet.io\";>here</a>. The idea "
+"is to improve upon this concept and support more of GNUnet's subsystems. The "
+"difficulty of this project largely depends on the students proficiency with "
+"build tools, emscripten and improvisation skills. There non-exhaustive task "
+"list would be: <ol> <li>Improve existing GNUnet emscripten build to include "
+"more subsystems.</li> <li>Integrate the result into a Webextention.</li> "
"<li>Integrate the result into the re:claimID Webextension</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> "
-"<li>emscripten</li> <li>Webextensions</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Challenging <br/> <strong>Mentors:</strong> "
-"Martin Schanzenbach"
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>emscripten</"
+"li> <li>Webextensions</li> </ol> <br/> <strong>Difficulty:</strong> "
+"Challenging <br/> <strong>Mentors:</strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:147
msgid ""
-"Currently, the keys in our statistics database are too verbose. For "
-"example: </p> <p> nse # flood messages received: 13<br/> nse # peers "
-"connected: 4<br/> nse # nodes in the network (estimate): 203<br/> nse # "
-"flood messages started: 5<br/> nse # estimated network diameter: 3<br/> "
-"nse # flood messages transmitted: 10<br/> </p> <p> With such verbose keys"
-" there's no easy way to form compact JSON document or entries for time-"
-"series database. And you can't query single stats without having to "
-"copypaste the line exactly and put in quotes. In short, the goals are "
-"to... <ol> <li>Think of a way how statistics entries can be made "
-"canonical.</li> <li>Implement the change and migrate existing uses.</li> "
-"<li>Document the format(s) and define an appropriate registration "
-"mechanism for identifiers</li> </ol> Relevant bugs: <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> "
-"</ol> <br/> <strong>Difficulty:</strong> Beginner <br/> "
-"<strong>Mentors:</strong> Martin Schanzenbach"
+"Currently, the keys in our statistics database are too verbose. For example: "
+"</p> <p> nse # flood messages received: 13<br/> nse # peers connected: 4<br/"
+"> nse # nodes in the network (estimate): 203<br/> nse # flood messages "
+"started: 5<br/> nse # estimated network diameter: 3<br/> nse # flood "
+"messages transmitted: 10<br/> </p> <p> With such verbose keys there's no "
+"easy way to form compact JSON document or entries for time-series database. "
+"And you can't query single stats without having to copypaste the line "
+"exactly and put in quotes. In short, the goals are to... <ol> <li>Think of a "
+"way how statistics entries can be made canonical.</li> <li>Implement the "
+"change and migrate existing uses.</li> <li>Document the format(s) and define "
+"an appropriate registration mechanism for identifiers</li> </ol> Relevant "
+"bugs: <a href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:187
msgid ""
-"The goal is to either build upon the (outdated) <a "
-"href=\"https://github.com/canndrew/gnunet-rs\";>GNUnet Rust bindings</a> "
-"or to follow the path of <a href=\"GNUnet Go\">https://github.com/bfix";
-"/gnunet-go</a> which tries to reimplement most of the GNUnet stack. The "
-"end result should be an extension template for GNUnet in the form of the "
-"existing <a href=\"https://git.gnunet.org/gnunet-ext.git/\";>C "
-"template</a> which allows to quickly start implementing services and "
-"libraries for GNUnet."
+"The goal is to either build upon the (outdated) <a href=\"https://github.com/";
+"canndrew/gnunet-rs\">GNUnet Rust bindings</a> or to follow the path of <a "
+"href=\"GNUnet Go\">https://github.com/bfix/gnunet-go</a> which tries to "
+"reimplement most of the GNUnet stack. The end result should be an extension "
+"template for GNUnet in the form of the existing <a href=\"https://git.gnunet.";
+"org/gnunet-ext.git/\">C template</a> which allows to quickly start "
+"implementing services and libraries for GNUnet."
msgstr ""
#: template/gsoc.html.j2:198 template/gsoc.html.j2:652
@@ -1458,27 +2151,26 @@ msgstr ""
#: template/gsoc.html.j2:229
msgid ""
-"Includes: Implementation of rudimentary Android compatibility for GNUnet,"
-" in part by porting the GNUnet utils scheduler to act as a thin wrapper "
-"over libuv."
+"Includes: Implementation of rudimentary Android compatibility for GNUnet, in "
+"part by porting the GNUnet utils scheduler to act as a thin wrapper over "
+"libuv."
msgstr ""
#: template/gsoc.html.j2:236
msgid ""
-"<strong>Mentors:</strong> <a href=\"https://www.goebel-";
-"consult.de/\">Hartmut Goebel</a>, Jeff Burdges, Christian Grothoff"
+"<strong>Mentors:</strong> <a href=\"https://www.goebel-consult.de/\";>Hartmut "
+"Goebel</a>, Jeff Burdges, Christian Grothoff"
msgstr ""
#: template/gsoc.html.j2:245
msgid ""
-"There is a push for migrating our CI to Gitlab. The CI should eventually "
-"not just run \"make check\" on various platforms, but also perform tests "
-"with multiple peers running in different VMs with specific network "
-"topologies (i.e. NAT) between them being simulated. The CI should also be"
-" integrated with Gauger for performance regression analysis. Running jobs"
-" only when dependencies have changed and scripting more granular triggers"
-" or ideally automatic dependency discovery (as done by the autotools) is "
-"also important."
+"There is a push for migrating our CI to Gitlab. The CI should eventually not "
+"just run \"make check\" on various platforms, but also perform tests with "
+"multiple peers running in different VMs with specific network topologies (i."
+"e. NAT) between them being simulated. The CI should also be integrated with "
+"Gauger for performance regression analysis. Running jobs only when "
+"dependencies have changed and scripting more granular triggers or ideally "
+"automatic dependency discovery (as done by the autotools) is also important."
msgstr ""
#: template/gsoc.html.j2:257
@@ -1487,19 +2179,18 @@ msgstr ""
#: template/gsoc.html.j2:267
msgid ""
-"One great problem of the current Internet is the lack of "
-"disintermediation. When people want to talk they need a chat service. "
-"When they want to share files they need a file transfer service. Although"
-" GNUnet already possesses quite advanced integration into Linux "
-"networking, a little extra work is needed for existing applications like "
-"irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by"
-" using a GNS hostname like friend.gnu. Once people have added a person to"
-" their GNS they can immediately message, exchange files and suchlike "
-"directly, with nothing but the GNUnet in the middle, using applications "
-"that have been distributed with unix systems ever since the 1980's. We "
-"can produce an OS distribution where these things work out of the box "
-"with the nicknames of people instead of cloud services. For more "
-"information and context, read"
+"One great problem of the current Internet is the lack of disintermediation. "
+"When people want to talk they need a chat service. When they want to share "
+"files they need a file transfer service. Although GNUnet already possesses "
+"quite advanced integration into Linux networking, a little extra work is "
+"needed for existing applications like irc, www, ftp, rsh, nntpd to run over "
+"it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. "
+"Once people have added a person to their GNS they can immediately message, "
+"exchange files and suchlike directly, with nothing but the GNUnet in the "
+"middle, using applications that have been distributed with unix systems ever "
+"since the 1980's. We can produce an OS distribution where these things work "
+"out of the box with the nicknames of people instead of cloud services. For "
+"more information and context, read"
msgstr ""
#: template/gsoc.html.j2:288
@@ -1508,8 +2199,7 @@ msgstr ""
#: template/gsoc.html.j2:296
msgid ""
-"Implement the AnycastExit spec to enable GNUnet clients to connect over "
-"Tor."
+"Implement the AnycastExit spec to enable GNUnet clients to connect over Tor."
msgstr ""
#: template/gsoc.html.j2:302 template/gsoc.html.j2:337
@@ -1520,9 +2210,9 @@ msgstr ""
#: template/gsoc.html.j2:307
msgid ""
"Note: There was a Special TLDs spec to allow Tor to resolve domain names "
-"using GNS over Tor too, but currently that's on hold until folks think "
-"more about how names should be moved around the local system. We're "
-"calling this more collaborative approach NSS2 for now."
+"using GNS over Tor too, but currently that's on hold until folks think more "
+"about how names should be moved around the local system. We're calling this "
+"more collaborative approach NSS2 for now."
msgstr ""
#: template/gsoc.html.j2:316 template/gsoc.html.j2:456
@@ -1532,17 +2222,16 @@ msgstr ""
#: template/gsoc.html.j2:329
msgid ""
-"Improve the Rust implementation of GNUnet utils, possibly including "
-"adding support for asynchronous IO using mio, or perhaps a higher level "
-"asynchronous IO library built upon it, such as rotor, mioco, eventual_io,"
-" or gj."
+"Improve the Rust implementation of GNUnet utils, possibly including adding "
+"support for asynchronous IO using mio, or perhaps a higher level "
+"asynchronous IO library built upon it, such as rotor, mioco, eventual_io, or "
+"gj."
msgstr ""
#: template/gsoc.html.j2:345
msgid ""
-"Implementation of a replacement for PANDA (see Pond) with better "
-"security, and maybe integration with the GNU Name System for key "
-"exchange."
+"Implementation of a replacement for PANDA (see Pond) with better security, "
+"and maybe integration with the GNU Name System for key exchange."
msgstr ""
#: template/gsoc.html.j2:357
@@ -1556,8 +2245,8 @@ msgstr ""
#: template/gsoc.html.j2:370
msgid ""
-"Implement different place types and file sharing by creating a new place "
-"for the shared content."
+"Implement different place types and file sharing by creating a new place for "
+"the shared content."
msgstr ""
#: template/gsoc.html.j2:376
@@ -1566,12 +2255,12 @@ msgstr ""
#: template/gsoc.html.j2:380
msgid ""
-"<ul> <li>File: generic file with comments</li> <li>Image: display an "
-"image with comments referencing a region of the image</li> <li>Sound: "
-"play a sound file with comments referencing a timestamp</li> "
-"<li>Directory/Album: pointers to File / Image / Sound places</li> "
-"<li>Event: with RSVP</li> <li>Survey: ask your social neighborhood "
-"questions in a structured form</li> </ul>"
+"<ul> <li>File: generic file with comments</li> <li>Image: display an image "
+"with comments referencing a region of the image</li> <li>Sound: play a sound "
+"file with comments referencing a timestamp</li> <li>Directory/Album: "
+"pointers to File / Image / Sound places</li> <li>Event: with RSVP</li> "
+"<li>Survey: ask your social neighborhood questions in a structured form</li> "
+"</ul>"
msgstr ""
#: template/gsoc.html.j2:391
@@ -1581,16 +2270,16 @@ msgstr ""
#: template/gsoc.html.j2:395
msgid ""
"<ul> <li>Fork existing channels, reorganize people into new chatrooms or "
-"channels.</li> <li>Share a post (edit and repost something elsewhere, on "
-"a fan page for example).</li> <li>Edit a previously published post + "
-"offer edit history to readers.</li> <li>Control expiry of channel "
-"history.</li> </ul>"
+"channels.</li> <li>Share a post (edit and repost something elsewhere, on a "
+"fan page for example).</li> <li>Edit a previously published post + offer "
+"edit history to readers.</li> <li>Control expiry of channel history.</li> </"
+"ul>"
msgstr ""
#: template/gsoc.html.j2:404
msgid ""
-"See also <a "
-"href=\"http://secushare.org/features\";>http://secushare.org/features</a>"
+"See also <a href=\"http://secushare.org/features\";>http://secushare.org/";
+"features</a>"
msgstr ""
#: template/gsoc.html.j2:409
@@ -1603,20 +2292,19 @@ msgstr ""
#: template/gsoc.html.j2:427
msgid ""
-"Implement aggregation of distributed state from various channels in order"
-" to provide for a powerful social graph API capable of producing social "
-"network profiles, dashboards, a calendar out of upcoming event "
-"invitations (if available), social search functionality and most of all "
-"to make it easy for users to adopt cryptographic identities of their "
-"contacts/friends simply by finding them in the social graph of their "
-"existing contacts (\"This is Linda. You have 11 contacts in common with "
-"her. [ADD]\")."
+"Implement aggregation of distributed state from various channels in order to "
+"provide for a powerful social graph API capable of producing social network "
+"profiles, dashboards, a calendar out of upcoming event invitations (if "
+"available), social search functionality and most of all to make it easy for "
+"users to adopt cryptographic identities of their contacts/friends simply by "
+"finding them in the social graph of their existing contacts (\"This is "
+"Linda. You have 11 contacts in common with her. [ADD]\")."
msgstr ""
#: template/gsoc.html.j2:445
msgid ""
-"Related to <a "
-"href=\"http://secushare.org/rendezvous\";>secushare.org/rendezvous</a>"
+"Related to <a href=\"http://secushare.org/rendezvous\";>secushare.org/"
+"rendezvous</a>"
msgstr ""
#: template/gsoc.html.j2:451 template/gsoc.html.j2:491
@@ -1625,21 +2313,21 @@ msgstr ""
#: template/gsoc.html.j2:468
msgid ""
-"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform "
-"traditional mail clients into secushare user interfaces. </li> <li> Think"
-" of ways to map e-mail addresses to secushare identities. </li> <li> "
-"Encode or translate various e-mail features into secushare equivalents. "
-"</li> <li> Parts of secushare are currently written in Rust, therefore "
-"Rust is preferred for this task but it is not an requirement. </li> </ul>"
+"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform traditional "
+"mail clients into secushare user interfaces. </li> <li> Think of ways to map "
+"e-mail addresses to secushare identities. </li> <li> Encode or translate "
+"various e-mail features into secushare equivalents. </li> <li> Parts of "
+"secushare are currently written in Rust, therefore Rust is preferred for "
+"this task but it is not an requirement. </li> </ul>"
msgstr ""
#: template/gsoc.html.j2:509
msgid ""
"Implementation of the GNUnet auction system described in Chapter 3 of <a "
"href=\"https://grothoff.org/christian/teich2017ms.pdf\";>this thesis</a>. "
-"Specific tasks are adding smart contract creation and round time "
-"enforcement to libbrandt as well as creating the GNUnet auction service, "
-"library and the three user interface programs create, info and join."
+"Specific tasks are adding smart contract creation and round time enforcement "
+"to libbrandt as well as creating the GNUnet auction service, library and the "
+"three user interface programs create, info and join."
msgstr ""
#: template/gsoc.html.j2:521
@@ -1648,9 +2336,9 @@ msgstr ""
#: template/gsoc.html.j2:539
msgid ""
-"Implementation of additional transports to make GNUnet communication more"
-" robust in the presence of problematic networks: GNUnet-over-SMTP, "
-"GNUnet-over-DNS"
+"Implementation of additional transports to make GNUnet communication more "
+"robust in the presence of problematic networks: GNUnet-over-SMTP, GNUnet-"
+"over-DNS"
msgstr ""
#: template/gsoc.html.j2:546 template/gsoc.html.j2:560
@@ -1664,16 +2352,16 @@ msgid ""
msgstr ""
#: template/gsoc.html.j2:568
-msgid "<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff
Burdges"
+msgid ""
+"<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff Burdges"
msgstr ""
#: template/gsoc.html.j2:576
msgid ""
-"Improving libaboss to make computation on shared secrets (including "
-"repeated multiplication) based on <a "
-"href=\"https://dl.acm.org/citation.cfm?doid=62212.62213\";>Ben-Or et "
-"al.</a> if possible. This in particular means moving libaboss to bignums "
-"(gcry_mpi)."
+"Improving libaboss to make computation on shared secrets (including repeated "
+"multiplication) based on <a href=\"https://dl.acm.org/citation.cfm?";
+"doid=62212.62213\">Ben-Or et al.</a> if possible. This in particular means "
+"moving libaboss to bignums (gcry_mpi)."
msgstr ""
#: template/gsoc.html.j2:589
@@ -1685,11 +2373,10 @@ msgstr ""
#: template/gsoc.html.j2:602
msgid ""
"Python 2.7 is reaching its end-of-life, and we want to get rid of the "
-"dependency on Python. The existing gnunet-qr tool is a rather simple "
-"wrapper around python-zbar, which itself wraps libzbar. The goal of this "
-"project is to directly use libzbar to scan QR codes for GNUnet / the GNU "
-"Name System (see also <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
+"dependency on Python. The existing gnunet-qr tool is a rather simple wrapper "
+"around python-zbar, which itself wraps libzbar. The goal of this project is "
+"to directly use libzbar to scan QR codes for GNUnet / the GNU Name System "
+"(see also <a href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
msgstr ""
#: template/gsoc.html.j2:612
@@ -1714,11 +2401,11 @@ msgstr ""
#: template/gsoc.html.j2:642
msgid ""
-"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a "
-"yet to be determined framework such as Angular2. This includes the design"
-" and implementation of not yet existing <a "
-"href=\"http://jsonapi.org/\";>REST APIs</a> that expose the <a "
-"href=\"https://docs.gnunet.org/doxygen/modules.html\";>GNUnet API</a>."
+"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a yet "
+"to be determined framework such as Angular2. This includes the design and "
+"implementation of not yet existing <a href=\"http://jsonapi.org/\";>REST "
+"APIs</a> that expose the <a href=\"https://docs.gnunet.org/doxygen/modules.";
+"html\">GNUnet API</a>."
msgstr ""
#: template/gsoc.html.j2:657
@@ -1727,8 +2414,7 @@ msgstr ""
#: template/gsoc.html.j2:667
msgid ""
-"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet "
-"WebUI</a>"
+"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet WebUI</a>"
msgstr ""
#: template/index.html.j2:8
@@ -1750,25 +2436,24 @@ msgstr ""
#: template/index.html.j2:49
msgid ""
"The conventional Internet is currently like a system of roads with deep "
-"potholes and highwaymen all over the place. Even if you still can use the"
-" roads (e.g. send emails, or browse websites) your vehicle might get "
+"potholes and highwaymen all over the place. Even if you still can use the "
+"roads (e.g. send emails, or browse websites) your vehicle might get "
"hijacked, damaged, or long arms might reach into its back and steal your "
-"items (data) to use it against you and sell it to others - while you "
-"can't even notice the thievery nor accuse and hold the scroungers "
-"accountable. <!-- Proposal from Fabian Gerlach: The conventional Internet"
-" is currently like a system of roads with deep potholes and surveillance "
-"cameras all over the place. Even if you still can use the roads (e.g. "
-"send emails, or browse websites) your vehicle might gets damaged. And the"
-" surveillance cameras will create a movement profile about your life: "
-"They recognize your car license plate, track you everywhere you drive, "
-"and save this information in a central data base. --> The Internet was "
-"not designed with security in mind: protecting against address forgery, "
-"routers learning metadata, or choosing trustworthy third parties is "
-"nontrivial and sometimes impossible. <!-- Proposal from Fabian Gerlach: "
-"The Internet is not designed with security in mind: The network generally"
-" learns too much about users; it has insecure defaults and high "
-"complexity; and it is centralized. That makes it very vulnerable for "
-"multiple attacks massively threatening our freedom. -->"
+"items (data) to use it against you and sell it to others - while you can'"
+"t even notice the thievery nor accuse and hold the scroungers accountable. "
+"<!-- Proposal from Fabian Gerlach: The conventional Internet is currently "
+"like a system of roads with deep potholes and surveillance cameras all over "
+"the place. Even if you still can use the roads (e.g. send emails, or browse "
+"websites) your vehicle might gets damaged. And the surveillance cameras will "
+"create a movement profile about your life: They recognize your car license "
+"plate, track you everywhere you drive, and save this information in a "
+"central data base. --> The Internet was not designed with security in mind: "
+"protecting against address forgery, routers learning metadata, or choosing "
+"trustworthy third parties is nontrivial and sometimes impossible. <!-- "
+"Proposal from Fabian Gerlach: The Internet is not designed with security in "
+"mind: The network generally learns too much about users; it has insecure "
+"defaults and high complexity; and it is centralized. That makes it very "
+"vulnerable for multiple attacks massively threatening our freedom. -->"
msgstr ""
#: template/index.html.j2:94
@@ -1778,10 +2463,10 @@ msgstr ""
#: template/index.html.j2:96
msgid ""
"GNUnet is a network protocol stack for building secure, distributed, and "
-"privacy-preserving applications.<br/> With strong roots in <a "
-"class=\"link\" href=\"https://bib.gnunet.org\";>academic research</a>, our"
-" goal is to replace the <a class=\"link\" href=\"https://secushare.org";
-"/broken-internet\">old insecure Internet</a> protocol stack."
+"privacy-preserving applications.<br/> With strong roots in <a class=\"link\" "
+"href=\"https://bib.gnunet.org\";>academic research</a>, our goal is to "
+"replace the <a class=\"link\" href=\"https://secushare.org/broken-internet";
+"\">old insecure Internet</a> protocol stack."
msgstr ""
#: template/index.html.j2:119
@@ -1792,10 +2477,9 @@ msgstr ""
msgid ""
"Your metadata is just as revealing as the actual content; and it gets "
"exposed on the Internet.<br> Even though transport encryption is "
-"increasingly being deployed on the Internet, it still reveals data that "
-"can threaten democracy: the identities of senders and receivers, the "
-"times, frequency and the volume of communication are all still "
-"revealed.<br>"
+"increasingly being deployed on the Internet, it still reveals data that can "
+"threaten democracy: the identities of senders and receivers, the times, "
+"frequency and the volume of communication are all still revealed.<br>"
msgstr ""
#: template/index.html.j2:150
@@ -1804,15 +2488,13 @@ msgstr ""
#: template/index.html.j2:152
msgid ""
-"It provides <a class=\"link\" "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";> improving "
-"addressing, routing, naming and content distribution</a> in a technically"
-" robust manner - as opposed to ad-hoc designs in place today. <!-- "
-"Proposal from fabian gerlach: GNUnet is built <a "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by "
-"design\"</a> and \"distributed by design\". This improves addressing, "
-"routing, naming and content distribution in a technically robust manner. "
-"-->"
+"It provides <a class=\"link\" href=\"https://www.w3.org/2014/strint/";
+"papers/65.pdf\"> improving addressing, routing, naming and content "
+"distribution</a> in a technically robust manner - as opposed to ad-hoc "
+"designs in place today. <!-- Proposal from fabian gerlach: GNUnet is built "
+"<a href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by design"
+"\"</a> and \"distributed by design\". This improves addressing, routing, "
+"naming and content distribution in a technically robust manner. -->"
msgstr ""
#: template/index.html.j2:177
@@ -1822,9 +2504,9 @@ msgstr ""
#: template/index.html.j2:179
msgid ""
"Today, monitoring increasingly centralized infrastructure, proprietary "
-"implementations, traffic shapers and firewalls restrict all of the <a "
-"class=\"link\" href=\"https://www.gnu.org/philosophy/free-";
-"sw.html\">essential freedoms</a> to various degrees."
+"implementations, traffic shapers and firewalls restrict all of the <a class="
+"\"link\" href=\"https://www.gnu.org/philosophy/free-sw.html\";>essential "
+"freedoms</a> to various degrees."
msgstr ""
#: template/index.html.j2:203
@@ -1833,14 +2515,14 @@ msgstr ""
#: template/index.html.j2:205
msgid ""
-"GNUnet is a self-organizing network and it is <a class=\"link\" "
-"href=\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as"
-" in freedom. GNUnet puts you in control of your data. You determine which"
-" data to share with whom, and you're not pressured to accept "
-"compromises. It gives users freedoms to securely access information "
-"(\"run\" the network), to study all aspects of the network's "
-"operation (\"access the code\"), to distribute information (\"copy\"), as"
-" well as the freedom to deploy new applications (\"modify\")."
+"GNUnet is a self-organizing network and it is <a class=\"link\" href="
+"\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as in "
+"freedom. GNUnet puts you in control of your data. You determine which data "
+"to share with whom, and you're not pressured to accept compromises. It "
+"gives users freedoms to securely access information (\"run\" the network), "
+"to study all aspects of the network's operation (\"access the code\"), "
+"to distribute information (\"copy\"), as well as the freedom to deploy new "
+"applications (\"modify\")."
msgstr ""
#: template/index.html.j2:229
@@ -1849,13 +2531,13 @@ msgstr ""
#: template/index.html.j2:232
msgid ""
-"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every "
-"other distributed or P2P project develops its own library stack, covering"
-" transports, stream muxing, discovery and others. This divides effort and"
-" multiplies bug count. --> Instead of sharing common components and tools"
-" for building P2P systems, every P2P project seems to re-invent the "
-"wheel. <!-- TODO: rework this sentence. --> This heightens the effort and"
-" increases the potential number of vulnerabilities."
+"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every other "
+"distributed or P2P project develops its own library stack, covering "
+"transports, stream muxing, discovery and others. This divides effort and "
+"multiplies bug count. --> Instead of sharing common components and tools for "
+"building P2P systems, every P2P project seems to re-invent the wheel. <!-- "
+"TODO: rework this sentence. --> This heightens the effort and increases the "
+"potential number of vulnerabilities."
msgstr ""
#: template/index.html.j2:264
@@ -1864,10 +2546,10 @@ msgstr ""
#: template/index.html.j2:266
msgid ""
-"It offers a metadata-preserving foundation for your application. It "
-"offers components for addressing, reliable encrypted channels with "
-"advanced routing and resource discovery and naming. Our work is based on "
-"continuous research spanning almost two decades."
+"It offers a metadata-preserving foundation for your application. It offers "
+"components for addressing, reliable encrypted channels with advanced routing "
+"and resource discovery and naming. Our work is based on continuous research "
+"spanning almost two decades."
msgstr ""
#: template/index.html.j2:286
@@ -2009,75 +2691,69 @@ msgstr ""
#: template/install.html.j2:12
msgid ""
-"Notice: GNUnet is still undergoing major development. It is largely "
-"<i>not yet ready</i> for usage beyond developers."
+"Notice: GNUnet is still undergoing major development. It is largely <i>not "
+"yet ready</i> for usage beyond developers."
msgstr ""
#: template/install.html.j2:18
msgid ""
-"<p>Please be aware that this project is still in an early alpha stage "
-"when it comes to running software – its not an easy task to rewrite"
-" the whole Internet! We are happy to get your <a "
-"href=\"engage.html\">helping hand</a> anytime! Further information is "
-"available in our <a href=\"https://docs.gnunet.org/#toc-Using-";
-"GNUnet-1\">handbook</a>. If you have any queries about the installation "
-"or the usage, please <a href=\"engage.html\">get in touch!</a></p>"
+"<p>Please be aware that this project is still in an early alpha stage when "
+"it comes to running software – its not an easy task to rewrite the "
+"whole Internet! We are happy to get your <a href=\"engage.html\">helping "
+"hand</a> anytime! Further information is available in our <a href=\"https://";
+"docs.gnunet.org/#toc-Using-GNUnet-1\">handbook</a>. If you have any queries "
+"about the installation or the usage, please <a href=\"engage.html\">get in "
+"touch!</a></p>"
msgstr ""
#: template/install.html.j2:30
msgid ""
"We recommend to use binary packages provided by the package manager "
-"integrated within your Operating System. GNUnet is reportedly available "
-"for at least: <ul> <li><a "
-"href=\"https://pkgs.alpinelinux.org/package/edge/testing/x86_64/gnunet\";>Alpine</a></li>"
-" <li><a "
-"href=\"https://www.archlinux.org/packages/community/x86_64/gnunet/\";>Arch</a></li>"
-" <li><a "
-"href=\"https://packages.debian.org/search?keywords=gnunet\";>Debian</a></li>"
-" <li><a "
-"href=\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora "
-"(Copr)</a></li> <li><a "
-"href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
-"href=\"https://github.com/Homebrew/homebrew-";
-"core/blob/master/Formula/gnunet.rb\">Homebrew</a></li> <li><a "
-"href=\"https://nixos.org/nixos/packages.html?attr=gnunet&channel=nixpkgs-";
-"unstable&query=gnunet\">NixOS</a></li> <li><a href=\"install-on-"
-"openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is available for your "
-"Operating System and it is missing, send us feedback so that we can add "
-"it to this list. Furthermore, if you are interested in packaging GNUnet "
-"for your Operating System, get in touch with us at gnunet-"
-"developers@gnu.org if you require help with this job. If you were using "
-"an Operating System with the Alpine package manager, GNUnet could be "
-"installed as simple as:"
+"integrated within your Operating System. GNUnet is reportedly available for "
+"at least: <ul> <li><a href=\"https://pkgs.alpinelinux.org/package/edge/";
+"testing/x86_64/gnunet\">Alpine</a></li> <li><a href=\"https://www.archlinux.";
+"org/packages/community/x86_64/gnunet/\">Arch</a></li> <li><a href=\"https://";
+"packages.debian.org/search?keywords=gnunet\">Debian</a></li> <li><a href="
+"\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora (Copr)</a></"
+"li> <li><a href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
+"href=\"https://github.com/Homebrew/homebrew-core/blob/master/Formula/gnunet.";
+"rb\">Homebrew</a></li> <li><a href=\"https://nixos.org/nixos/packages.html?";
+"attr=gnunet&channel=nixpkgs-unstable&query=gnunet\">NixOS</a></li> <li><a "
+"href=\"install-on-openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is "
+"available for your Operating System and it is missing, send us feedback so "
+"that we can add it to this list. Furthermore, if you are interested in "
+"packaging GNUnet for your Operating System, get in touch with us at gnunet-"
+"developers@gnu.org if you require help with this job. If you were using an "
+"Operating System with the Alpine package manager, GNUnet could be installed "
+"as simple as:"
msgstr ""
#: template/install.html.j2:61
msgid ""
-"Next we describe a generic way to install from source. If you are using "
-"one of the following Operating Systems these step-by-step guides might be"
-" useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href"
-"=\"install-on-debian9.html\">Debian 9</a>, <a href=\"install-on-"
-"macos.html\">Mac OS</a>, <a href=\"install-on-netbsd.html\">NetBSD</a>, "
-"<a href=\"install-on-ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not"
-" all of them might be totally up-to-date! Please <a "
-"href=\"engage.html\">ask us</a> if you get stuck."
+"Next we describe a generic way to install from source. If you are using one "
+"of the following Operating Systems these step-by-step guides might be "
+"useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href=\"install-on-"
+"debian9.html\">Debian 9</a>, <a href=\"install-on-macos.html\">Mac OS</a>, "
+"<a href=\"install-on-netbsd.html\">NetBSD</a>, <a href=\"install-on-"
+"ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not all of them might be "
+"totally up-to-date! Please <a href=\"engage.html\">ask us</a> if you get "
+"stuck."
msgstr ""
#: template/install.html.j2:75
msgid ""
-"First, install the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>required "
-"dependencies</a> of GNUnet. There are base requirements and optional "
-"requirements."
+"First, install the <a href=\"https://git.gnunet.org/gnunet.git/tree/README";
+"\">required dependencies</a> of GNUnet. There are base requirements and "
+"optional requirements."
msgstr ""
#: template/install.html.j2:81
msgid ""
"Now, you need to decide if you want to install GNUnet from the release "
"tarball or from git. If you want to use GNUnet and there is no binary "
-"package available for your OS, you should stick with the release tarball."
-" If you want to develop using the most recent build, you should go with "
-"the <a href=\"https://git.gnunet.org/\";>git repository</a>."
+"package available for your OS, you should stick with the release tarball. If "
+"you want to develop using the most recent build, you should go with the <a "
+"href=\"https://git.gnunet.org/\";>git repository</a>."
msgstr ""
#: template/install.html.j2:98
@@ -2086,8 +2762,8 @@ msgstr ""
#: template/install.html.j2:106
msgid ""
-"Before building GNUnet, make sure that you setup the required groups and "
-"add your user to the group <code>gnunet</code>:"
+"Before building GNUnet, make sure that you setup the required groups and add "
+"your user to the group <code>gnunet</code>:"
msgstr ""
#: template/install.html.j2:117
@@ -2096,9 +2772,8 @@ msgstr ""
#: template/install.html.j2:128
msgid ""
-"You can find more configuration flags in the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>README</a>.<br> "
-"Install GNUnet with:"
+"You can find more configuration flags in the <a href=\"https://git.gnunet.";
+"org/gnunet.git/tree/README\">README</a>.<br> Install GNUnet with:"
msgstr ""
#: template/install.html.j2:138
@@ -2108,9 +2783,8 @@ msgstr ""
#: template/install.html.j2:146
msgid ""
"Check the <a href=\"https://docs.gnunet.org/handbook/gnunet.html#Minimal-";
-"configuration\">handbook</a> for detailed documentation. For a more "
-"hands-on experience, <a href=\"https://gnunet.org/en/use.html\";>continue "
-"here</a>."
+"configuration\">handbook</a> for detailed documentation. For a more hands-on "
+"experience, <a href=\"https://gnunet.org/en/use.html\";>continue here</a>."
msgstr ""
#: template/livingstandards.html.j2:11
diff --git a/locale/zh_Hant/LC_MESSAGES/messages.po
b/locale/zh_Hant/LC_MESSAGES/messages.po
index 134cf36..a135a29 100644
--- a/locale/zh_Hant/LC_MESSAGES/messages.po
+++ b/locale/zh_Hant/LC_MESSAGES/messages.po
@@ -7,13 +7,13 @@ msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2021-03-03 21:41+0100\n"
+"POT-Creation-Date: 2021-03-12 15:55+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: Automatically generated\n"
"Language-Team: none\n"
"Language: zh_Hant\n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
+"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.9.0\n"
@@ -63,6 +63,7 @@ msgid "About"
msgstr ""
#: common/navigation.j2.inc:39 news/index.html.j2:8
+#: news/oldnews-2011.html.j2:13 news/oldnews-2013.html.j2:13
#: news/oldnews-2018.html.j2:13 news/oldnews-2019.html.j2:13
msgid "News"
msgstr ""
@@ -155,17 +156,20 @@ msgstr ""
msgid "FAQ"
msgstr ""
-#: news/index.html.j2:11 news/oldnews-2018.html.j2:16
+#: news/index.html.j2:11 news/oldnews-2011.html.j2:16
+#: news/oldnews-2013.html.j2:16 news/oldnews-2018.html.j2:16
#: news/oldnews-2019.html.j2:16
msgid "News posts about changes related to GNUnet such as releases and events"
msgstr ""
-#: news/index.html.j2:16 news/oldnews-2018.html.j2:21
+#: news/index.html.j2:16 news/oldnews-2011.html.j2:21
+#: news/oldnews-2013.html.j2:21 news/oldnews-2018.html.j2:21
#: news/oldnews-2019.html.j2:21
msgid "subscribe to our RSS feed"
msgstr ""
-#: news/index.html.j2:36 news/oldnews-2018.html.j2:40
+#: news/index.html.j2:36 news/oldnews-2011.html.j2:40
+#: news/oldnews-2013.html.j2:40 news/oldnews-2018.html.j2:40
#: news/oldnews-2019.html.j2:40
msgid "read more"
msgstr ""
@@ -180,39 +184,38 @@ msgstr ""
#: template/about.html.j2:13
msgid ""
-"GNUnet is an alternative network stack for building secure, decentralized"
-" and privacy-preserving distributed applications. Our goal is to replace "
-"the old insecure Internet protocol stack. Starting from an application "
-"for secure publication of files, it has grown to include all kinds of "
-"basic protocol components and applications towards the creation of a GNU "
-"internet."
+"GNUnet is an alternative network stack for building secure, decentralized "
+"and privacy-preserving distributed applications. Our goal is to replace the "
+"old insecure Internet protocol stack. Starting from an application for "
+"secure publication of files, it has grown to include all kinds of basic "
+"protocol components and applications towards the creation of a GNU internet."
msgstr ""
#: template/about.html.j2:23
msgid ""
-"Today, the actual use and thus the social requirements for a global "
-"network differs widely from those goals of 1970. While the Internet "
-"remains suitable for military use, where the network equipment is "
-"operated by a command hierarchy and when necessary isolated from the rest"
-" of the world, the situation is less tenable for civil society."
+"Today, the actual use and thus the social requirements for a global network "
+"differs widely from those goals of 1970. While the Internet remains suitable "
+"for military use, where the network equipment is operated by a command "
+"hierarchy and when necessary isolated from the rest of the world, the "
+"situation is less tenable for civil society."
msgstr ""
#: template/about.html.j2:32
msgid ""
"Due to fundamental Internet design choices, Internet traffic can be "
-"misdirected, intercepted, censored and manipulated by hostile routers on "
-"the network. And indeed, the modern Internet has evolved exactly to the "
-"point where, as Matthew Green put it, <a "
-"href=\"https://blog.cryptographyengineering.com/2015/08/16/the-network-";
-"is-hostile/\">\"the network is hostile\"</a>."
+"misdirected, intercepted, censored and manipulated by hostile routers on the "
+"network. And indeed, the modern Internet has evolved exactly to the point "
+"where, as Matthew Green put it, <a href=\"https://blog.";
+"cryptographyengineering.com/2015/08/16/the-network-is-hostile/\">\"the "
+"network is hostile\"</a>."
msgstr ""
#: template/about.html.j2:41
msgid ""
-"We believe liberal societies need a network architecture that uses the "
-"anti-authoritarian decentralized peer-to-peer paradigm and privacy-"
-"preserving cryptographic protocols. The goal of the GNUnet project is to "
-"provide a Free Software realization of this ideal."
+"We believe liberal societies need a network architecture that uses the anti-"
+"authoritarian decentralized peer-to-peer paradigm and privacy-preserving "
+"cryptographic protocols. The goal of the GNUnet project is to provide a Free "
+"Software realization of this ideal."
msgstr ""
#: template/about.html.j2:49
@@ -223,8 +226,8 @@ msgstr ""
#: template/about.html.j2:56
msgid ""
-"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy";
-"/free-sw.html\">Free Software</a>."
+"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy/free-";
+"sw.html\">Free Software</a>."
msgstr ""
#: template/about.html.j2:60
@@ -235,8 +238,8 @@ msgstr ""
#: template/about.html.j2:61
msgid ""
-"GNUnet must be fully distributed and resilient to external attacks and "
-"rogue participants."
+"GNUnet must be fully distributed and resilient to external attacks and rogue "
+"participants."
msgstr ""
#: template/about.html.j2:62
@@ -247,8 +250,8 @@ msgstr ""
#: template/about.html.j2:63
msgid ""
-"GNUnet must inform the user which other participants have to be trusted "
-"when establishing private communications."
+"GNUnet must inform the user which other participants have to be trusted when "
+"establishing private communications."
msgstr ""
#: template/about.html.j2:64
@@ -269,33 +272,28 @@ msgstr ""
#: template/about.html.j2:68
msgid ""
-"GNUnet must provide incentives for peers to contribute more resources "
-"than they consume."
+"GNUnet must provide incentives for peers to contribute more resources than "
+"they consume."
msgstr ""
#: template/about.html.j2:72
msgid ""
-"To get know and learn more, please check our <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, "
-"especially the <a href=\"https://docs.gnunet.org/handbook/gnunet.html";
-"#Key-Concepts\">chapter on \"Key Concepts\"</a>, explaining the "
-"fundamental concepts of GNUnet: <ul> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Authentication\";>Authentication</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Accounting-";
-"to-Encourage-Resource-Sharing\">Accounting to Encourage Resource "
-"Sharing</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Confidentiality\";>Confidentiality</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></li>"
-" <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability\";>Deniability</a></li>"
-" <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Peer-";
-"Identities\">Peer Identities</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-";
-"Name-System-_0028GNS-Zones_0029\">Zones in the GNU Name System (GNS "
-"Zones)</a></li> <li><a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> "
-"</ul>"
+"To get know and learn more, please check our <a href=\"https://docs.gnunet.";
+"org/handbook/gnunet.html\">handbook</a>, especially the <a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Key-Concepts\">chapter on \"Key Concepts"
+"\"</a>, explaining the fundamental concepts of GNUnet: <ul> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Authentication";
+"\">Authentication</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Accounting-to-Encourage-Resource-Sharing\">Accounting to "
+"Encourage Resource Sharing</a></li> <li><a href=\"https://docs.gnunet.org/";
+"handbook/gnunet.html#Confidentiality\">Confidentiality</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\";>Anonymity</a></"
+"li> <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability";
+"\">Deniability</a></li> <li><a href=\"https://docs.gnunet.org/handbook/";
+"gnunet.html#Peer-Identities\">Peer Identities</a></li> <li><a href=\"https://";
+"docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-Name-System-_0028GNS-"
+"Zones_0029\">Zones in the GNU Name System (GNS Zones)</a></li> <li><a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html#Egos\";>Egos</a></li> </ul>"
msgstr ""
#: template/about.html.j2:88
@@ -304,27 +302,27 @@ msgstr ""
#: template/about.html.j2:90
msgid ""
-"There are many more resources to learn about GNUnet besides the <a "
-"href=\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such "
-"as the <a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers "
-"covering the various layers, many <a "
-"href=\"https://gnunet.org/en/video.html\";>videos</a> or a brief <a "
-"href=\"https://gnunet.org/en/glossary.html\";>glossary</a>."
+"There are many more resources to learn about GNUnet besides the <a href="
+"\"https://docs.gnunet.org/handbook/gnunet.html\";>handbook</a>, such as the "
+"<a href=\"https://bib.gnunet.org/\";>bibliography</a> with papers covering "
+"the various layers, many <a href=\"https://gnunet.org/en/video.html";
+"\">videos</a> or a brief <a href=\"https://gnunet.org/en/glossary.html";
+"\">glossary</a>."
msgstr ""
#: template/about.html.j2:95
msgid ""
"You are most welcome to <a href=\"engage.html\">get engaged into the "
-"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a "
-"href=\"use.html\">use it</a> and <a href=\"engage.html\">contribute and "
-"get engaged</a> in various ways."
+"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a href=\"use."
+"html\">use it</a> and <a href=\"engage.html\">contribute and get engaged</a> "
+"in various ways."
msgstr ""
#: template/about.html.j2:100
msgid ""
-"Please be aware that this project is (despite of it's age) still in an "
-"early alpha stage when it comes to software – its not an easy task "
-"to rewrite the whole Internet!"
+"Please be aware that this project is (despite of it's age) still in an early "
+"alpha stage when it comes to software – its not an easy task to "
+"rewrite the whole Internet!"
msgstr ""
#: template/about.html.j2:105
@@ -333,24 +331,25 @@ msgstr ""
#: template/about.html.j2:110
msgid ""
-"We're receiving funding from NLnet's Next Generation Internet funding "
-"line to document and implement the GNU Name System protocol in a way "
-"suitable for the IETF standardization process."
+"We're receiving funding from NLnet's Next Generation Internet funding line "
+"to document and implement the GNU Name System protocol in a way suitable for "
+"the IETF standardization process."
msgstr ""
#: template/about.html.j2:123
msgid ""
"This project has received funding from the European Union’s Horizon 2020 "
"research and innovation programme under the NGI_TRUST grant agreement no "
-"825618. The project aims to integrate re:claimID with the GNU Taler "
-"payment system in a pilot in order to demonstrate the practical "
-"feasibility and benefits of privacy enhancing technologies for users and "
-"commercial service providers. The project is called \"Decentralized "
-"Identities for Self-Sovereign End-users\" (DISSENS)."
+"825618. The project aims to integrate re:claimID with the GNU Taler payment "
+"system in a pilot in order to demonstrate the practical feasibility and "
+"benefits of privacy enhancing technologies for users and commercial service "
+"providers. The project is called \"Decentralized Identities for Self-"
+"Sovereign End-users\" (DISSENS)."
msgstr ""
#: template/about.html.j2:141
-msgid "We are grateful for free hosting offered by the following
organizations:"
+msgid ""
+"We are grateful for free hosting offered by the following organizations:"
msgstr ""
#: template/about.html.j2:150
@@ -371,13 +370,13 @@ msgstr ""
#: template/applications.html.j2:15
msgid ""
-"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully "
-"decentralized replacement for the Domain Name System (DNS). Instead of "
-"using a hierarchy, GNS uses a directed graph. Naming conventions are "
-"similar to DNS, but queries and replies are private even with respect to "
-"peers providing the answers. The integrity of records and privacy of "
-"look-ups is cryptographically secured. <!-- Too technical: GNS integrates"
-" a robust, efficient and instant key revocation mechanism. -->"
+"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully decentralized "
+"replacement for the Domain Name System (DNS). Instead of using a hierarchy, "
+"GNS uses a directed graph. Naming conventions are similar to DNS, but "
+"queries and replies are private even with respect to peers providing the "
+"answers. The integrity of records and privacy of look-ups is "
+"cryptographically secured. <!-- Too technical: GNS integrates a robust, "
+"efficient and instant key revocation mechanism. -->"
msgstr ""
#: template/applications.html.j2:38
@@ -386,8 +385,8 @@ msgstr ""
#: template/applications.html.j2:40
msgid ""
-"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized"
-" Identity Provider (IdP) service built in top of the GNU Name System. It "
+"<a href=\"https://reclaim.gnunet.org/\";>re:claimID</a> is a decentralized "
+"Identity Provider (IdP) service built in top of the GNU Name System. It "
"allows users to securely share personal information with websites using "
"standardized protocols (OpenID Connect)."
msgstr ""
@@ -398,10 +397,9 @@ msgstr ""
#: template/applications.html.j2:59
msgid ""
-"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that "
-"aims to provide censorship-resistant, anonymous filesharing. The "
-"publisher is empowered to make a gradual choice between performance and "
-"anonymity."
+"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that aims "
+"to provide censorship-resistant, anonymous filesharing. The publisher is "
+"empowered to make a gradual choice between performance and anonymity."
msgstr ""
#: template/applications.html.j2:73
@@ -411,8 +409,8 @@ msgstr ""
#: template/applications.html.j2:75
msgid ""
"GNUnet conversation is an application that provides secure voice "
-"communication in a fully decentralized way by employing GNUnet for "
-"routing and transport."
+"communication in a fully decentralized way by employing GNUnet for routing "
+"and transport."
msgstr ""
#: template/applications.html.j2:91
@@ -426,8 +424,8 @@ msgstr ""
#: template/applications.html.j2:99
msgid ""
"<a href=\"https://taler.net/\";>GNU Taler</a> is a new privacy-preserving "
-"electronic payment system. Payments are cryptographically secured and are"
-" confirmed within milliseconds with extremely low transaction costs."
+"electronic payment system. Payments are cryptographically secured and are "
+"confirmed within milliseconds with extremely low transaction costs."
msgstr ""
#: template/applications.html.j2:118
@@ -436,10 +434,10 @@ msgstr ""
#: template/applications.html.j2:120
msgid ""
-"<a href=\"https://secushare.org/\";>secushare</a> is creating a "
-"decentralized social networking application on top of GNUnet. Using "
-"overlay multicast and the extensible PSYC protocol, notifications are "
-"distributed end-to-end encrypted to authorized recipients only."
+"<a href=\"https://secushare.org/\";>secushare</a> is creating a decentralized "
+"social networking application on top of GNUnet. Using overlay multicast and "
+"the extensible PSYC protocol, notifications are distributed end-to-end "
+"encrypted to authorized recipients only."
msgstr ""
#: template/applications.html.j2:139
@@ -448,10 +446,10 @@ msgstr ""
#: template/applications.html.j2:141
msgid ""
-"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) "
-"is creating a usable end-to-end encrypted e-mail solution using "
-"opportunistic key exchange. p≡p will use GNUnet to protect metadata"
-" and exploit new cryptographic protocols to verify keys."
+"<a href=\"https://pep.foundation/\";>pretty Easy privacy</a> (p≡p) is "
+"creating a usable end-to-end encrypted e-mail solution using opportunistic "
+"key exchange. p≡p will use GNUnet to protect metadata and exploit new "
+"cryptographic protocols to verify keys."
msgstr ""
#: template/applications.html.j2:160
@@ -460,10 +458,10 @@ msgstr ""
#: template/applications.html.j2:162
msgid ""
-"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> "
-"is a convenient but feature-rich graphical application providing "
-"messaging using especially the CADET subsystem. It is developed using GTK"
-" and libhandy for a convergent design."
+"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\";>Cadet-GTK</a> is a "
+"convenient but feature-rich graphical application providing messaging using "
+"especially the CADET subsystem. It is developed using GTK and libhandy for a "
+"convergent design."
msgstr ""
#: template/applications.html.j2:180
@@ -474,8 +472,8 @@ msgstr ""
msgid ""
"<a href=\"https://git.gnunet.org/groupchat.git/\";>groupchat</a> is a "
"terminal user interface providing messaging using especially the CADET "
-"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned"
-" to be compatible."
+"subsystem. It is developed using nim. Cadet-GTK and groupchat are planned to "
+"be compatible."
msgstr ""
#: template/architecture.html.j2:6
@@ -488,11 +486,11 @@ msgstr ""
#: template/architecture.html.j2:22
msgid ""
-"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-"
-"like end-to-end encrypted messaging layer (CADET), a public key "
-"infrastructure (GNS) and a pluggable transport system (TRANSPORT).<br> "
-"Using public keys for addresses and self-organized decentralized routing "
-"algorithms, these subsystems replace the traditional TCP/IP stack."
+"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-like "
+"end-to-end encrypted messaging layer (CADET), a public key infrastructure "
+"(GNS) and a pluggable transport system (TRANSPORT).<br> Using public keys "
+"for addresses and self-organized decentralized routing algorithms, these "
+"subsystems replace the traditional TCP/IP stack."
msgstr ""
#: template/architecture.html.j2:35
@@ -503,9 +501,9 @@ msgstr ""
msgid ""
"GNUnet is implemented using a multi-process architecture. Each subsystem "
"runs as a separate process, providing fault-isolation and enabling tight "
-"permissions to be granted to each subsystem. Naturally, the "
-"implementation is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and"
-" will always remain free software."
+"permissions to be granted to each subsystem. Naturally, the implementation "
+"is a <a href=\"https://www.gnu.org/\";>GNU</a> package, and will always "
+"remain free software."
msgstr ""
#: template/architecture.html.j2:52
@@ -538,11 +536,10 @@ msgstr ""
#: template/contact.html.j2:13
msgid ""
-"An archived, public mailing list for GNUnet is hosted at <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers\">https://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>. You can send messages to the list at <a href=\"mailto"
-":gnunet-developers@gnu.org\">gnunet-developers@gnu.org</a>."
+"An archived, public mailing list for GNUnet is hosted at <a href=\"https://";
+"lists.gnu.org/mailman/listinfo/gnunet-developers\">https://lists.gnu.org/";
+"mailman/listinfo/gnunet-developers</a>. You can send messages to the list at "
+"<a href=\"mailto:gnunet-developers@gnu.org\";>gnunet-developers@gnu.org</a>."
msgstr ""
#: template/contact.html.j2:23
@@ -551,10 +548,9 @@ msgstr ""
#: template/contact.html.j2:25
msgid ""
-"<tt>#gnunet</tt> is reachable via <a "
-"href=\"https://freenode.net\";>irc.freenode.net</a>. There is also an <a "
-"href=\"https://view.matrix.org/room/!IjaAfLiruzjxFFzKAV:matrix.org/\";>archive</a>"
-" available."
+"<tt>#gnunet</tt> is reachable via <a href=\"https://freenode.net\";>irc."
+"freenode.net</a>. There is also an <a href=\"https://view.matrix.org/room/!";
+"IjaAfLiruzjxFFzKAV:matrix.org/\">archive</a> available."
msgstr ""
#: template/contact.html.j2:38
@@ -563,11 +559,10 @@ msgstr ""
#: template/contact.html.j2:40
msgid ""
-"GNUnet developers are generally reachable at either "
-"<tt>PSEUDONYM@gnunet.org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us"
-" support receiving GnuPG encrypted Emails. Urgent and sensitive security "
-"issues may be addressed to the GNU maintainers <tt>schanzen</tt> and "
-"<tt>grothoff</tt>."
+"GNUnet developers are generally reachable at either <tt>PSEUDONYM@gnunet."
+"org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us support receiving GnuPG "
+"encrypted Emails. Urgent and sensitive security issues may be addressed to "
+"the GNU maintainers <tt>schanzen</tt> and <tt>grothoff</tt>."
msgstr ""
#: template/contact.html.j2:53
@@ -576,38 +571,37 @@ msgstr ""
#: template/contact.html.j2:55
msgid ""
-"We track open feature requests and bugs for projects within GNUnet in our"
-" <a href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also "
-"report bugs or feature requests to the <a "
-"href=\"https://lists.gnu.org/mailman/listinfo/bug-gnunet\";>bug-gnunet</a>"
-" mailing list. The mailinglist requires no subscription."
+"We track open feature requests and bugs for projects within GNUnet in our <a "
+"href=\"https://bugs.gnunet.org/\";>Bug tracker</a>. You can also report bugs "
+"or feature requests to the <a href=\"https://lists.gnu.org/mailman/listinfo/";
+"bug-gnunet\">bug-gnunet</a> mailing list. The mailinglist requires no "
+"subscription."
msgstr ""
#: template/copyright.html.j2:11
msgid ""
-"<p> Contributors to GNUnet with Git access must sign the <a "
-"href=\"/static/pdf/copyright.pdf\">copyright assignment</a> to ensure "
-"that the <a href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/gnunet_taler_agreement.tex\">GNUnet e.V. --- Taler Systems SA"
-" agreement on licensing and collaborative development</a> of the GNUnet "
-"and GNU Taler projects is satisfied. </p>"
+"<p> Contributors to GNUnet with Git access must sign the <a href=\"/static/"
+"pdf/copyright.pdf\">copyright assignment</a> to ensure that the <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/gnunet_taler_agreement.tex";
+"\">GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative "
+"development</a> of the GNUnet and GNU Taler projects is satisfied. </p>"
msgstr ""
#: template/copyright.html.j2:22
msgid ""
-"<p>The agreements ensure that the code will continue to be made available"
-" under free software licenses, but gives developers the freedom to move "
-"code between GNUnet and GNU Taler without worrying about licenses and to "
-"give the company the ability to dual-license (for example, so that we can"
-" distribute via App-stores that are hostile to free software).</p>"
+"<p>The agreements ensure that the code will continue to be made available "
+"under free software licenses, but gives developers the freedom to move code "
+"between GNUnet and GNU Taler without worrying about licenses and to give the "
+"company the ability to dual-license (for example, so that we can distribute "
+"via App-stores that are hostile to free software).</p>"
msgstr ""
#: template/copyright.html.j2:30
msgid ""
-"<p>Minor contributions (basically, anyone without Git access) do not "
-"require copyright assignment. Pseudonymous contributions are accepted, in"
-" this case simply sign the agreement with your pseudonym. Scanned copies "
-"are sufficient, but snail mail is preferred.</p>"
+"<p>Minor contributions (basically, anyone without Git access) do not require "
+"copyright assignment. Pseudonymous contributions are accepted, in this case "
+"simply sign the agreement with your pseudonym. Scanned copies are "
+"sufficient, but snail mail is preferred.</p>"
msgstr ""
#: template/developers.html.j2:5
@@ -620,14 +614,14 @@ msgstr ""
#: template/developers.html.j2:16
msgid ""
-"A list of our Git repositories can be found on our our <a "
-"href=\"https://git.gnunet.org/\";>Git Server</a>."
+"A list of our Git repositories can be found on our our <a href=\"https://git.";
+"gnunet.org/\">Git Server</a>."
msgstr ""
#: template/developers.html.j2:27
msgid ""
-"Technical papers can be found in our <a "
-"href=\"https://old.gnunet.org/bibliography\";>bibliography</a>."
+"Technical papers can be found in our <a href=\"https://old.gnunet.org/";
+"bibliography\">bibliography</a>."
msgstr ""
#: template/developers.html.j2:34
@@ -636,10 +630,10 @@ msgstr ""
#: template/developers.html.j2:37
msgid ""
-"We have a mailing list for developer discussions. You can subscribe to or"
-" read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo";
-"/gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-";
-"developers</a>."
+"We have a mailing list for developer discussions. You can subscribe to or "
+"read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo/";
+"gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-developers</"
+"a>."
msgstr ""
#: template/developers.html.j2:47
@@ -648,9 +642,9 @@ msgstr ""
#: template/developers.html.j2:50
msgid ""
-"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests "
-"to detect regressions and check for portability at <a "
-"href=\"https://old.gnunet.org/buildbot/gnunet/\";>https://old.gnunet.org/buildbot/gnunet/</a>."
+"We have <a href=\"https://buildbot.net/\";>Buildbot</a> automation tests to "
+"detect regressions and check for portability at <a href=\"https://old.gnunet.";
+"org/buildbot/gnunet/\">https://old.gnunet.org/buildbot/gnunet/</a>."
msgstr ""
#: template/developers.html.j2:59
@@ -659,10 +653,9 @@ msgstr ""
#: template/developers.html.j2:62
msgid ""
-"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> "
-"to analyze the code coverage of our tests, the results are available at "
-"<a "
-"href=\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
+"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\";>LCOV</a> to "
+"analyze the code coverage of our tests, the results are available at <a href="
+"\"https://old.gnunet.org/coverage/\";>https://old.gnunet.org/coverage/</a>."
msgstr ""
#: template/developers.html.j2:72
@@ -671,9 +664,9 @@ msgstr ""
#: template/developers.html.j2:75
msgid ""
-"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for "
-"performance regression analysis of the exchange backend at <a "
-"href=\"https://old.gnunet.org/gauger/\";>https://old.gnunet.org/gauger/</a>."
+"We use <a href=\"https://old.gnunet.org/gauger\";>Gauger</a> for performance "
+"regression analysis of the exchange backend at <a href=\"https://old.gnunet.";
+"org/gauger/\">https://old.gnunet.org/gauger/</a>."
msgstr ""
#: template/download.html.j2:7 template/gnurl.html.j2:209
@@ -682,8 +675,8 @@ msgstr ""
#: template/download.html.j2:11
msgid ""
-"Here you can download releases of our software and find links to the "
-"various versions."
+"Here you can download releases of our software and find links to the various "
+"versions."
msgstr ""
#: template/download.html.j2:17
@@ -705,7 +698,8 @@ msgid "git"
msgstr ""
#: template/download.html.j2:32
-msgid "You can fetch the git tag of version 0.11.x from our development
server:"
+msgid ""
+"You can fetch the git tag of version 0.11.x from our development server:"
msgstr ""
#: template/engage.html.j2:6
@@ -722,18 +716,17 @@ msgstr ""
#: template/ev.html.j2:13
msgid ""
-"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the"
-" \"Verein zur Förderung von GNUnet e.V.\", an association under "
-"German law to support GNUnet development. The Amtsgericht München "
-"registered the association on the 7th of March under VR 205287."
+"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the "
+"\"Verein zur Förderung von GNUnet e.V.\", an association under German "
+"law to support GNUnet development. The Amtsgericht München registered "
+"the association on the 7th of March under VR 205287."
msgstr ""
#: template/ev.html.j2:22
msgid ""
-"The association is officially dedicated to supporting research, "
-"development and education in the area of secure decentralized networking "
-"in general, and GNUnet specifically. This is the official website for the"
-" association."
+"The association is officially dedicated to supporting research, development "
+"and education in the area of secure decentralized networking in general, and "
+"GNUnet specifically. This is the official website for the association."
msgstr ""
#: template/ev.html.j2:31
@@ -742,15 +735,15 @@ msgstr ""
#: template/ev.html.j2:33
msgid ""
-"GNUnet developers with git (write) access can become members to "
-"participate in the decision process and formally support GNUnet e.V. For "
-"this, all you have to do is update the <tt>members.txt</tt> file in the "
-"<a href=\"https://git.gnunet.org/gnunet-ev.git/\";>gnunet-ev</a> "
-"repository. There are no membership dues; however, members are required "
-"to support GNUnet e.V. and in particularly contribute to the technical "
-"development within their means. For further details, we refer to the <a "
-"href=\"https://git.gnunet.org/gnunet-ev.git/\";>Satzung</a> (currently "
-"only available in German, translations welcome)."
+"GNUnet developers with git (write) access can become members to participate "
+"in the decision process and formally support GNUnet e.V. For this, all you "
+"have to do is update the <tt>members.txt</tt> file in the <a href=\"https://";
+"git.gnunet.org/gnunet-ev.git/\">gnunet-ev</a> repository. There are no "
+"membership dues; however, members are required to support GNUnet e.V. and in "
+"particularly contribute to the technical development within their means. For "
+"further details, we refer to the <a href=\"https://git.gnunet.org/gnunet-ev.";
+"git/\">Satzung</a> (currently only available in German, translations "
+"welcome)."
msgstr ""
#: template/ev.html.j2:52
@@ -759,16 +752,13 @@ msgstr ""
#: template/ev.html.j2:54
msgid ""
-"You can find our \"Satzung\", and the list of members under <a "
-"href=\"https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex\">https://git.gnunet.org/gnunet-";
-"ev.git/tree/satzung.tex</a>. The current board consists of: "
+"You can find our \"Satzung\", and the list of members under <a href="
+"\"https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex\";>https://git.gnunet.";
+"org/gnunet-ev.git/tree/satzung.tex</a>. The current board consists of: "
"<dl><dt>Vorsitz</dt> <dd><a href=\"https://schanzen.eu\";>Martin "
-"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> "
-"<dd>t3sserakt</dd> <dt>Kassenwart</dt> <dd>Florian Dold</dd> "
-"<dt>Beisitzer</dt> <dd> <a "
-"href=\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 "
-"</dd> </dl>"
+"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> <dd>t3sserakt</dd> "
+"<dt>Kassenwart</dt> <dd>Florian Dold</dd> <dt>Beisitzer</dt> <dd> <a href="
+"\"https://grothoff.org/christian/\";>Christian Grothoff</a>, ch3 </dd> </dl>"
msgstr ""
#: template/ev.html.j2:73
@@ -783,77 +773,801 @@ msgstr ""
msgid ""
"Everybody is welcome to support us via donations. For financial "
"contributions, Europeans are able to donate via SEPA. We hope to setup "
-"accounts in other major currency areas in the future. You can also donate"
-" via Bitcoin, routing details are given below. Please note that we are "
-"unable to provide receipts for your donations. If you are planning to "
-"donate a significant amount of money, please contact us first as it might"
-" be better to come to a custom arrangement. <dl><dt>BitCoin</dt> "
+"accounts in other major currency areas in the future. You can also donate "
+"via Bitcoin, routing details are given below. Please note that we are unable "
+"to provide receipts for your donations. If you are planning to donate a "
+"significant amount of money, please contact us first as it might be better "
+"to come to a custom arrangement. <dl><dt>BitCoin</dt> "
"<dd>1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh</dd> <dt>SEPA/IBAN</dt> "
"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
msgstr ""
-#: template/faq.html.j2:12
-msgid "Is GNUnet ready for use on production systems?"
+#: template/faq.html.j2:12 template/faq.html.j2:23
+msgid "General"
msgstr ""
-#: template/faq.html.j2:14
-msgid ""
-"A: GNUnet is still undergoing major development. It is largely not yet "
-"ready for usage beyond developers. Your mileage will vary depending on "
-"the functionality you use, but you will always likely run into issues "
-"with our current low-level transport system. We are currently in the "
-"process of rewriting it (Project "Transport Next Generation "
-"[TNG]")"
+#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
+msgid "Features"
msgstr ""
-#: template/faq.html.j2:24
-msgid "Is GNUnet build using distributed ledger technologies?"
+#: template/faq.html.j2:15 template/faq.html.j2:594
+msgid "Error messages"
+msgstr ""
+
+#: template/faq.html.j2:16 template/faq.html.j2:696
+msgid "File-sharing"
+msgstr ""
+
+#: template/faq.html.j2:17 template/faq.html.j2:872
+msgid "Contributing"
msgstr ""
#: template/faq.html.j2:26
+msgid "What do I do if my question is not answered here?"
+msgstr ""
+
+#: template/faq.html.j2:28
msgid ""
-"A: No. GNUnet is a new network protocol stack for building secure, "
-"distributed, and privacy-preserving applications. While a ledger could be"
-" built using GNUnet, we currently have no plans in doing so."
+"A: There are many other sources of information. You can read additional "
+"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
+"the #gnunet IRC on irc.freenode.net."
msgstr ""
-#: template/faq.html.j2:35
+#: template/faq.html.j2:36
+msgid "When are you going to release the next version?"
+msgstr ""
+
+#: template/faq.html.j2:38
msgid ""
-"I receive many "WARNING Calculated flow delay for X at Y for "
-"Z". Should I worry?"
+"A: The general answer is, when it is ready. A better answer may be: earlier "
+"if you contribute (test, debug, code, document). Every release will be "
+"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://";
+"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
+"the RSS feed of this site to automatically receive a notification."
+msgstr ""
+
+#: template/faq.html.j2:49
+msgid "Is the code free?"
msgstr ""
-#: template/faq.html.j2:37
+#: template/faq.html.j2:51
msgid ""
-"A: Right now, this is expected and a known cause for high latency in "
-"GNUnet. We have started a major rewrite to address this and other "
-"problems, but until the Transport Next Generation (TNG) is ready, these "
-"warnings are expected."
+"A: GNUnet is free software, available under the <a href=\"https://www.gnu.";
+"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
msgstr ""
-#: template/faq.html.j2:46
+#: template/faq.html.j2:58
+msgid "Are there any known bugs?"
+msgstr ""
+
+#: template/faq.html.j2:60
+msgid ""
+"A: We track the list of currently known bugs in the <a href=\"https://bugs.";
+"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
+"directly to developers or the developer mailing list. This is discouraged "
+"since developers often do not have the time to feed these bugs back into the "
+"Mantis database. Please report bugs directly to the bug tracking system. If "
+"you believe a bug is sensitive, you can set its view status to private (this "
+"should be the exception)."
+msgstr ""
+
+#: template/faq.html.j2:73 template/faq.html.j2:193
msgid "Is there a graphical user interface?"
msgstr ""
-#: template/faq.html.j2:48
+#: template/faq.html.j2:75
msgid ""
"A: gnunet-gtk is a separate download. The package contains various GTK+ "
"based graphical interfaces, including a graphical tool for configuration."
msgstr ""
+#: template/faq.html.j2:83
+msgid "Why does gnunet-service-nse create a high CPU load?"
+msgstr ""
+
+#: template/faq.html.j2:85
+msgid ""
+"A: The gnunet-service-nse process will initially compute a so-called ""
+"proof-of-work" which is used to convince the network that your peer is "
+"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
+"on the network size estimator). The calculation is expected to take a few "
+"days, depending on how fast your CPU is. If the CPU load is creating a "
+"problem for you, you can set the value "WORKDELAY" in the ""
+"nse" section of your configuration file to a higher value. The default "
+"is "5 ms"."
+msgstr ""
+
+#: template/faq.html.j2:99
+msgid "How does GNUnet compare to Tor?"
+msgstr ""
+
+#: template/faq.html.j2:101
+msgid ""
+"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
+"connections and, with the Tor Browser Bundle, for the Web in particular. "
+"GNUnet does not really have one focus; our theme is secure decentralized "
+"networking, but that is too broad to be called a focus."
+msgstr ""
+
+#: template/faq.html.j2:111
+msgid "How does GNUnet compare to I2P?"
+msgstr ""
+
+#: template/faq.html.j2:113
+msgid ""
+"A: Both GNUnet and I2P want to build a better, more secure, more "
+"decentralized Internet. However, on the technical side, there are almost no "
+"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
+"using onion (or garlic) routing as the basis for various (anonymized) "
+"applications. I2P is largely used via a Web frontend."
+msgstr ""
+
+#: template/faq.html.j2:124
+msgid "Is GNUnet ready for use on production systems?"
+msgstr ""
+
+#: template/faq.html.j2:126
+msgid ""
+"A: GNUnet is still undergoing major development. It is largely not yet ready "
+"for usage beyond developers. Your mileage will vary depending on the "
+"functionality you use, but you will always likely run into issues with our "
+"current low-level transport system. We are currently in the process of "
+"rewriting it (Project "Transport Next Generation [TNG]")"
+msgstr ""
+
+#: template/faq.html.j2:136
+msgid "Is GNUnet build using distributed ledger technologies?"
+msgstr ""
+
+#: template/faq.html.j2:138
+msgid ""
+"A: No. GNUnet is a new network protocol stack for building secure, "
+"distributed, and privacy-preserving applications. While a ledger could be "
+"built using GNUnet, we currently have no plans in doing so."
+msgstr ""
+
+#: template/faq.html.j2:151
+msgid "What can I do with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:153
+msgid ""
+"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
+"do more than just one thing. Naturally, the implementation and documentation "
+"of some of the features that exist are more advanced than others."
+msgstr ""
+
+#: template/faq.html.j2:160
+msgid ""
+"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
+"decentralized and censorship-resistant replacement for DNS and a mechanism "
+"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
+msgstr ""
+
+#: template/faq.html.j2:171
+msgid "Is it possible to surf the WWW anonymously with GNUnet?"
+msgstr ""
+
+#: template/faq.html.j2:173
+msgid ""
+"A: It is not possible use GNUnet for anonymous browsing at this point. We "
+"recommend that you use Tor for anonymous surfing."
+msgstr ""
+
+#: template/faq.html.j2:181
+msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
+msgstr ""
+
+#: template/faq.html.j2:183
+msgid ""
+"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
+"would make it accessible with a browser. It is possible to build such a "
+"proxy and all one needs to know is the protocol used between browser and "
+"proxy and a swift look at the GNUnet code for file-sharing."
+msgstr ""
+
+#: template/faq.html.j2:195
+msgid ""
+"A: There are actually a few graphical user interfaces for different "
+"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
+"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
+"importance. Note that in order to obtain the GUI, you need to install the "
+"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
+"that integrates most of the other GUIs in one window. One exception is "
+"gnunet-setup, which must still be run separately at this time (as setup "
+"requires the peer to be stopped)."
+msgstr ""
+
+#: template/faq.html.j2:210
+msgid "On top of which operating systems does GNUnet run?"
+msgstr ""
+
+#: template/faq.html.j2:212
+msgid ""
+"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
+"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
+"FreeBSD and macOS. We have reports of working versions on many other GNU/"
+"Linux distributions; in the past we had reports of working versions on "
+"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
+"so if you cannot get GNUnet to work on those systems please let us know."
+msgstr ""
+
+#: template/faq.html.j2:228
+msgid "Who runs the GNS root zone?"
+msgstr ""
+
+#: template/faq.html.j2:230
+msgid ""
+"A: Short answer: you. The long answer is the GNUnet will ship with a default "
+"configuration of top-level domains. The governance of this default "
+"configuration is not yet established. In any case, the user will be able to "
+"modify this configuration at will. We expect normal users to have no need to "
+"edit their own GNS zone(s) unless they host services themselves."
+msgstr ""
+
+#: template/faq.html.j2:241
+msgid "Where is the per-user GNS database kept?"
+msgstr ""
+
+#: template/faq.html.j2:243
+msgid ""
+"A: The short answer is that the database is kept at the user's GNUnet peer. "
+"Now, a user may run multiple GNUnet peers, in which case the database could "
+"be kept at each peer (however, we don't have code for convenient "
+"replication). Similarly, multiple GNUnet peers can share one instance of the "
+"database --- the "gnunet-service-namestore" can be accessed from "
+"remote (via TCP). The actual data can be stored in a Postgres database, for "
+"which various replication options are again applicable. Ultimately, there "
+"are many options for how users can store (and secure) their GNS database."
+msgstr ""
+
+#: template/faq.html.j2:258
+msgid "What is the expected average size of a GNS namestore database?"
+msgstr ""
+
+#: template/faq.html.j2:260
+msgid ""
+"A: Pretty small. Based on our user study where we looked at browser "
+"histories and the number of domains visited, we expect that GNS databases "
+"will only grow to a few tens of thousands of entries, small enough to fit "
+"even on mobile devices."
+msgstr ""
+
+#: template/faq.html.j2:270
+msgid "Is GNS resistant to the attacks on DNS used by the US?"
+msgstr ""
+
+#: template/faq.html.j2:272
+msgid ""
+"A: We believe so, as there is no entity that any government could force to "
+"change the mapping for a name except for each individual user (and then the "
+"changes would only apply to the names that this user is the authority for). "
+"So if everyone used GNS, the only practical attack of a government would be "
+"to force the operator of a server to change the GNS records for his server "
+"to point elsewhere. However, if the owner of the private key for a zone is "
+"unavailable for enforcement, the respective zone cannot be changed and any "
+"other zone delegating to this zone will achieve proper resolution."
+msgstr ""
+
+#: template/faq.html.j2:286
+msgid "What is the difference between GNS and CoDoNS?"
+msgstr ""
+
+#: template/faq.html.j2:288
+msgid ""
+"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
+"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
+"there are still registrars that determine who owns a name. <br><br> With "
+"GNS, we decentralize the database and also decentralize the responsibility "
+"for naming: each user runs his own personal root zone and is thus in "
+"complete control of the names he uses. GNS also has many additional features "
+"(to keep names short and enable migration) which don't even make sense in "
+"the context of CoDoNS."
+msgstr ""
+
+#: template/faq.html.j2:304
+msgid "What is the difference between GNS and SocialDNS?"
+msgstr ""
+
+#: template/faq.html.j2:306
+msgid ""
+"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
+"with SocialDNS the mappings are shared through the social network and "
+"subjected to ranking. As the social relationships evolve, names can thus "
+"change in surprising ways. <br><br> With GNS, names are primarily shared via "
+"delegation, and thus mappings will only change if the user responsible for "
+"the name (the authority) manually changes the record."
+msgstr ""
+
+#: template/faq.html.j2:320
+msgid "What is the difference between GNS and ODDNS?"
+msgstr ""
+
+#: template/faq.html.j2:322
+msgid ""
+"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
+"registries (such as those for \".com\" and \".org\"). Instead of using "
+"those, each user is expected to maintain a database of (second-level) "
+"domains (like \"gnu.org\") and the IP addresses of the respective name "
+"servers. Resolution will fail if the target name servers change IPs."
+msgstr ""
+
+#: template/faq.html.j2:333
+msgid "What is the difference between GNS and Namecoin?"
+msgstr ""
+
+#: template/faq.html.j2:340
+msgid "What is the difference between GNS and Handshake?"
+msgstr ""
+
+#: template/faq.html.j2:346
+msgid "What is the difference between GNS and ENS?"
+msgstr ""
+
+#: template/faq.html.j2:352
+msgid "What is the difference between GNS and TrickleDNS?"
+msgstr ""
+
+#: template/faq.html.j2:354
+msgid ""
+"A: TrickleDNS pushes ("critical") DNS records between DNS "
+"resolvers of participating domains to provide "better availability, "
+"lower query resolution times, and faster update propagation". Thus "
+"TrickleDNS is focused on defeating attacks on the availability (and "
+"performance) of record propagation in DNS, for example via DDoS attacks on "
+"DNS root servers. TrickleDNS is thus concerned with how to ensure "
+"distribution of authoritative records, and authority remains derived from "
+"the DNS hierarchy."
+msgstr ""
+
+#: template/faq.html.j2:367
+msgid ""
+"Does GNS require real-world introduction (secure PKEY exchange) in the style "
+"of the PGP web of trust?"
+msgstr ""
+
+#: template/faq.html.j2:369
+msgid ""
+"A: For security, it is well known that an initial trust path between the two "
+"parties must exist. However, for applications where this is not required, "
+"weaker mechanisms can be used. For example, we have implemented a first-come-"
+"first-served (FCFS) authority which allows arbitrary users to register "
+"arbitrary names. The key of this authority is included with every GNUnet "
+"installation. Thus, any name registered with FCFS is in fact global and "
+"requires no further introduction. However, the security of these names "
+"depends entirely on the trustworthiness of the FCFS authority. The authority "
+"can be queried under the ".pin" TLD."
+msgstr ""
+
+#: template/faq.html.j2:384
+msgid ""
+"How can a legitimate domain owner tell other people to not use his name in "
+"GNS?"
+msgstr ""
+
+#: template/faq.html.j2:386
+msgid ""
+"A: Names have no owners in GNS, so there cannot be a "legitimate" "
+"domain owner. Any user can claim any name (as his preferred name or ""
+"pseudonym") in his NICK record. Similarly, all other users can choose "
+"to ignore this preference and use a name of their choice (or even assign no "
+"name) for this user."
+msgstr ""
+
+#: template/faq.html.j2:397
+msgid ""
+"Did you consider the privacy implications of making your personal GNS zone "
+"visible?"
+msgstr ""
+
+#: template/faq.html.j2:399
+msgid ""
+"A: Each record in GNS has a flag "private". Records are shared "
+"with other users (via DHT or zone transfers) only if this flag is not set. "
+"Thus, users have full control over what information about their zones is "
+"made public."
+msgstr ""
+
+#: template/faq.html.j2:409
+msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
+msgstr ""
+
+#: template/faq.html.j2:411
+msgid ""
+"A: The question presumes that (a) virtual hosting is only necessary because "
+"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
+"of virtual hosting. However, LEHOs are also useful to help with X.509 "
+"certificate validation (as they specify for which legacy hostname the "
+"certificate should be valid). Also, even with IPv6 fully deployed and ""
+"infinite" IP addresses being available, we're not sure that virtual "
+"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
+"become commonplace, GNS should work with today's networks."
+msgstr ""
+
+#: template/faq.html.j2:425
+msgid ""
+"Why does GNS not use a trust metric or consensus to determine globally "
+"unique names?"
+msgstr ""
+
+#: template/faq.html.j2:427
+msgid ""
+"A: Trust metrics have the fundamental problem that they have thresholds. As "
+"trust relationships evolve, mappings would change their meaning as they "
+"cross each others thresholds. We decided that the resulting unpredictability "
+"of the resolution process was not acceptable. Furthermore, trust and "
+"consensus might be easy to manipulate by adversaries."
+msgstr ""
+
+#: template/faq.html.j2:438
+msgid "How do you handle compromised zone keys in GNS?"
+msgstr ""
+
+#: template/faq.html.j2:440
+msgid ""
+"A: The owner of a private key can create a revocation message. This one can "
+"then be flooded throughout the overlay network, creating a copy at all "
+"peers. Before using a public key, peers check if that key has been revoked. "
+"All names that involve delegation via a revoked zone will then fail to "
+"resolve. Peers always automatically check for the existence of a revocation "
+"message when resolving names."
+msgstr ""
+
+#: template/faq.html.j2:452
+msgid "Could the signing algorithm of GNS be upgraded in the future?"
+msgstr ""
+
+#: template/faq.html.j2:454
+msgid ""
+"A: Yes. In our efforts to standardize GNS, we have already modified the "
+"protocol to support alternative delegation records. <br> <br> Naturally, "
+"deployed GNS implementations would have to be updated to support the new "
+"signature scheme. The new scheme can then be run in parallel with the "
+"existing system by using a new record type to indicate the use of a "
+"different cipher system."
+msgstr ""
+
+#: template/faq.html.j2:468
+msgid ""
+"How can a GNS zone maintain several name servers, e.g. for load balancing?"
+msgstr ""
+
+#: template/faq.html.j2:470
+msgid ""
+"A: We don't expect this to be necessary, as GNS records are stored (and "
+"replicated) in the R5N DHT. Thus the authority will typically not be "
+"contacted whenever clients perform a lookup. Even if the authority goes "
+"(temporarily) off-line, the DHT will cache the records for some time. "
+"However, should having multiple servers for a zone be considered truly "
+"necessary, the owner of the zone can simply run multiple peers (and share "
+"the zone's key and database among them)."
+msgstr ""
+
+#: template/faq.html.j2:483
+msgid ""
+"Why do you believe it is worth giving up unique names for censorship "
+"resistance?"
+msgstr ""
+
+#: template/faq.html.j2:485
+msgid ""
+"A: The GNU Name system offers an alternative to DNS that is censorship "
+"resistant. As with any security mechanism, this comes at a cost (names are "
+"not globally unique). To draw a parallel, HTTPS connections use more "
+"bandwidth and have higher latency than HTTP connections. Depending on your "
+"application, HTTPS may not be worth the cost. However, for users that are "
+"experiencing censorship (or are concerned about it), giving up globally "
+"unique names may very well be worth the cost. After all, what is a ""
+"globally" unique name worth, if it does not resolve?"
+msgstr ""
+
+#: template/faq.html.j2:499
+msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
+msgstr ""
+
+#: template/faq.html.j2:501
+msgid ""
+"A: We say that DNS is 'centralized' because it has a central component / "
+"central point of failure --- the root zone and its management by IANA/ICANN. "
+"This centralization creates vulnerabilities. For example, the US government "
+"was able to reassign the management of the country-TLDs of Afganistan and "
+"Iraq during the wars at the beginning of the 21st century."
+msgstr ""
+
+#: template/faq.html.j2:512
+msgid "How does GNS protect against layer-3 censorship?"
+msgstr ""
+
+#: template/faq.html.j2:514
+msgid ""
+"A: GNS does not directly help with layer-3 censorship, but it does help "
+"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
+"so blocking a particular IP address causes much more collateral damage than "
+"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
+"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
+"censorship resistant naming system. Accessing Tor's ".onion" "
+"namespace currently requires users to use unmemorable cryptographic "
+"identifiers. With nicer names, Tor and tor2web-like services would be even "
+"easier to use. </ol>"
+msgstr ""
+
+#: template/faq.html.j2:533
+msgid "Does GNS work with search engines?"
+msgstr ""
+
+#: template/faq.html.j2:535
+msgid ""
+"A: GNS creates no significant problems for search engines, as they can use "
+"GNS to perform name resolution as well as any normal user. Naturally, while "
+"we typically expect normal users to install custom software for name "
+"resolution, this is unlikely to work for search engines today. However, the "
+"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
+"they can still index GNS resources. However, as using DNS2GNS gateways "
+"breaks the cryptographic chain of trust, legacy search engines will "
+"obviously not obtain censorship-resistant names."
+msgstr ""
+
+#: template/faq.html.j2:549
+msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
+msgstr ""
+
+#: template/faq.html.j2:551
+msgid ""
+"A: UIA and GNS both share the same basic naming model, which actually "
+"originated with Rivest's SDSI. However, UIA is not concerned about "
+"integration with legacy applications and instead focuses on universal "
+"connectivity between a user's many machines. In contrast, GNS was designed "
+"to interoperate with DNS as much as possible, and to also work as much as "
+"possible with the existing Web infrastructure. UIA is not at all concerned "
+"about legacy systems (clean slate)."
+msgstr ""
+
+#: template/faq.html.j2:564
+msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
+msgstr ""
+
+#: template/faq.html.j2:566
+msgid ""
+"A: First of all, in GNS you can explicitly see the trust chain, so you know "
+"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
+"and can thus decide how much you trust the result. Naturally, the trusted-"
+"computing base (TCB) can become arbitrarily large this way --- however, "
+"given the name length restriction, for an individual name it is always less "
+"than about 128 entities."
+msgstr ""
+
+#: template/faq.html.j2:578
+msgid ""
+"How does GNS handle SRV/TLSA records where service and protocol are part of "
+"the domain name?"
+msgstr ""
+
+#: template/faq.html.j2:580
+msgid ""
+"A: When GNS splits a domain name into labels for resolution, it detects the "
+""_Service._Proto" syntax, converts "Service" to the "
+"corresponding port number and "Proto" to the corresponding "
+"protocol number. The rest of the name is resolved as usual. Then, when the "
+"result is presented, GNS looks for the GNS-specific "BOX" record "
+"type. A BOX record is a record that contains another record (such as SRV or "
+"TLSA records) and adds a service and protocol number (and the original boxed "
+"record type) to it."
+msgstr ""
+
+#: template/faq.html.j2:596
+msgid ""
+"I receive many "WARNING Calculated flow delay for X at Y for Z". "
+"Should I worry?"
+msgstr ""
+
+#: template/faq.html.j2:598
+msgid ""
+"A: Right now, this is expected and a known cause for high latency in GNUnet. "
+"We have started a major rewrite to address this and other problems, but "
+"until the Transport Next Generation (TNG) is ready, these warnings are "
+"expected."
+msgstr ""
+
+#: template/faq.html.j2:607
+msgid "Error opening `/dev/net/tun': No such file or directory?"
+msgstr ""
+
+#: template/faq.html.j2:609
+msgid ""
+"A: If you get this error message, the solution is simple. Issue the "
+"following commands (as root) to create the required device file"
+msgstr ""
+
+#: template/faq.html.j2:621
+msgid ""
+"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
+"dns)?"
+msgstr ""
+
+#: template/faq.html.j2:623
+msgid ""
+"A: For GNUnet DNS, your iptables needs to have "owner" match "
+"support. This is accomplished by having the correct kernel options. Check if "
+"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
+"'m' (and the module is loaded)."
+msgstr ""
+
+#: template/faq.html.j2:635
+msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
+msgstr ""
+
+#: template/faq.html.j2:637
+msgid ""
+"A: If you get an error stating that the VPN timeout was reached, check if "
+"your firewall is enabled and blocking the connections."
+msgstr ""
+
+#: template/faq.html.j2:645
+msgid ""
+"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
+msgstr ""
+
+#: template/faq.html.j2:647
+msgid ""
+"A: This error usually occurs when your linker fails to locate one of "
+"GNUnet's libraries. This can have two causes. First, it is theoretically "
+"possible that the library is not installed on your system; however, if you "
+"compiled GNUnet the normal way and/or used a binary package, that is highly "
+"unlikely. The more common cause is that you installed GNUnet to a directory "
+"that your linker does not search. There are several ways to fix this that "
+"are described below. If you are 'root' and you installed to a system folder "
+"(such as /usr/local), you want to add the libraries to the system-wide "
+"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
+"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
+"similar path, you obviously have to change \"/usr/local\" accordingly. If "
+"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
+"$USER/\", then you can explicitly tell your linker to search a particular "
+"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
+"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
+"you want to run:"
+msgstr ""
+
+#: template/faq.html.j2:673
+msgid ""
+"to ensure GNUnet's binaries and libraries are found. In order to avoid "
+"having to do so each time, you can add the above lines (without the \"$\") "
+"to your .bashrc or .profile file. You will have to logout and login again to "
+"have this new profile be applied to all shells (including your desktop "
+"environment)."
+msgstr ""
+
+#: template/faq.html.j2:680
+msgid "What error messages can be ignored?"
+msgstr ""
+
+#: template/faq.html.j2:682
+msgid ""
+"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
+"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
+"always refer to harmless events that require no action. For example, GNUnet "
+"may use an INFO message to indicate that it is currently performing an "
+"expensive operation that will take some time. GNUnet will also use INFO "
+"messages to display information about important configuration values."
+msgstr ""
+
+#: template/faq.html.j2:698
+msgid "How does GNUnet compare to other file-sharing applications?"
+msgstr ""
+
+#: template/faq.html.j2:700
+msgid ""
+"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
+"P2P networks, GNUnet was designed with security in mind as the highest "
+"priority. We intend on producing a network with comprehensive security "
+"features. Many other P2P networks are open to a wide variety of attacks, and "
+"users have little privacy. GNUnet is also Free Software and thus the source "
+"code is available, so you do not have to worry about being spied upon by the "
+"software. The following table summarises the main differences between GNUnet "
+"and other systems. The information is accurate to the best of our knowledge. "
+"The comparison is difficult since there are sometimes differences between "
+"various implementations of (almost) the same protocol. In general, we pick a "
+"free implementation as the reference implementation since it is possible to "
+"inspect the free code. Also, all of these systems are changing over time and "
+"thus the data below may not be up-to-date. If you find any flaws, please let "
+"us know. Finally, the table is not saying terribly much (it is hard to "
+"compare these systems this briefly), so if you want the real differences, "
+"read the research papers (and probably the code)."
+msgstr ""
+
+#: template/faq.html.j2:814
+msgid ""
+"Another important point of reference are the various anonymous peer-to-peer "
+"networks. Here, there are differences in terms of application domain and how "
+"specifically anonymity is achieved. Anonymous routing is a hard research "
+"topic, so for a superficial comparisson like this one we focus on the "
+"latency. Another important factor is the programming language. Type-safe "
+"languages may offer certain security benefits; however, this may come at the "
+"cost of significant increases in resource consumption which in turn may "
+"reduce anonymity."
+msgstr ""
+
+#: template/faq.html.j2:827
+msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
+msgstr ""
+
+#: template/faq.html.j2:829
+msgid ""
+"A: Generally, there is the possibility of a known plaintext attack on "
+"keywords, but since the user has control over the keywords that are "
+"associated with the content he inserts, the user can take advantage of the "
+"same techniques used to generate reasonable passwords to defend against such "
+"an attack. In any event, we are not trying to hide content; thus, unless the "
+"user is trying to insert information into the network that can only be "
+"shared with a small group of people, there is no real reason to try to "
+"obfuscate the content by choosing a difficult keyword anyway."
+msgstr ""
+
+#: template/faq.html.j2:843
+msgid "What do you mean by anonymity?"
+msgstr ""
+
+#: template/faq.html.j2:845
+msgid ""
+"A: Anonymity is the lack of distinction of an individual from a (large) "
+"group. A central goal for anonymous file-sharing in GNUnet is to make all "
+"users (peers) form a group and to make communications in that group "
+"anonymous, that is, nobody (but the initiator) should be able to tell which "
+"of the peers in the group originated the message. In other words, it should "
+"be difficult to impossible for an adversary to distinguish between the "
+"originating peer and all other peers."
+msgstr ""
+
+#: template/faq.html.j2:857
+msgid "What does my system do when participating in GNUnet file sharing?"
+msgstr ""
+
+#: template/faq.html.j2:859
+msgid ""
+"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
+"its public key) and has a number of addresses it is reachable by (may have "
+"no addresses, for instance when it's behind a NAT). You specify bandwidth "
+"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
+"(how large your on-disk block storage is) . Your node will then proceed to "
+"connect to other nodes, becoming part of the network."
+msgstr ""
+
+#: template/faq.html.j2:874
+msgid "How can I help translate this webpage into other languages?"
+msgstr ""
+
+#: template/faq.html.j2:876
+msgid ""
+"A: First, you need to register an account with our weblate system. Please "
+"send an e-mail with the desired target language to translators@gnunet.org or "
+"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
+"sufficient permissions will then grant you access. Naturally, any abuse will "
+"result in the loss of permissions."
+msgstr ""
+
+#: template/faq.html.j2:888
+msgid "I have some great idea for a new feature, what should I do?"
+msgstr ""
+
+#: template/faq.html.j2:890
+msgid ""
+"A: Sadly, we have many more feature requests than we can possibly implement. "
+"The best way to actually get a new feature implemented is to do it yourself "
+"--- and to then send us a patch."
+msgstr ""
+
#: template/glossary.html.j2:12
msgid "Ego"
msgstr ""
#: template/glossary.html.j2:14
msgid ""
-"We use the term \"Ego\" to refer to the fact that users in GNUnet can "
-"have multiple unlinkable identities, in the sense of alter egos. The "
-"ability to have more than one identity is crucial, as we may want to keep"
-" our egos for business separate from those we use for political "
-"activities or romance.<br> Egos in GNUnet are technically equivalent to "
-"identities (and the code does not distinguish between them). We simply "
-"sometimes use the term \"ego\" to stress that you can have more than one."
+"We use the term \"Ego\" to refer to the fact that users in GNUnet can have "
+"multiple unlinkable identities, in the sense of alter egos. The ability to "
+"have more than one identity is crucial, as we may want to keep our egos for "
+"business separate from those we use for political activities or romance.<br> "
+"Egos in GNUnet are technically equivalent to identities (and the code does "
+"not distinguish between them). We simply sometimes use the term \"ego\" to "
+"stress that you can have more than one."
msgstr ""
#: template/glossary.html.j2:27
@@ -862,19 +1576,18 @@ msgstr ""
#: template/glossary.html.j2:29
msgid ""
-"In GNUnet users are identified via a public key, and that public key is "
-"then often referred to as the \"Identity\" of the user. However, the "
-"concept is not as draconian as it often is in real life where many are "
-"forced to have one name, one passport and one unique identification "
-"number. <br> As long as identities in GNUnet are simply public keys, "
-"users are free to create any number of identities, and we call those egos"
-" to emphasize the difference. Even though users can create such egos "
-"freely, it is possible to have an ego certified by some certification "
-"authority, resulting in something that more closely resembles the "
-"traditional concept of an identity.<br> For example, a university may "
-"certify the identities of its students such that they can prove that they"
-" are studying. Students may keep their (certified) student identity "
-"separate from other egos that they use for other activities in life."
+"In GNUnet users are identified via a public key, and that public key is then "
+"often referred to as the \"Identity\" of the user. However, the concept is "
+"not as draconian as it often is in real life where many are forced to have "
+"one name, one passport and one unique identification number. <br> As long as "
+"identities in GNUnet are simply public keys, users are free to create any "
+"number of identities, and we call those egos to emphasize the difference. "
+"Even though users can create such egos freely, it is possible to have an ego "
+"certified by some certification authority, resulting in something that more "
+"closely resembles the traditional concept of an identity.<br> For example, a "
+"university may certify the identities of its students such that they can "
+"prove that they are studying. Students may keep their (certified) student "
+"identity separate from other egos that they use for other activities in life."
msgstr ""
#: template/glossary.html.j2:50
@@ -886,10 +1599,10 @@ msgid ""
"A pseudonym is an ego that is specifically intended to not be linked to "
"one's real name. GNUnet users can create many egos, and thus also many "
"pseudonyms. <br> Repeated uses of the same pseudonym are linkable by "
-"definition, as they involve the same public key. Anonymity requires the "
-"use of either the special \"anonymous\" pseudonym (for GNUnet, this is "
-"the neutral element on the elliptic curve) or a throw-away pseudonym that"
-" is only used once."
+"definition, as they involve the same public key. Anonymity requires the use "
+"of either the special \"anonymous\" pseudonym (for GNUnet, this is the "
+"neutral element on the elliptic curve) or a throw-away pseudonym that is "
+"only used once."
msgstr ""
#: template/glossary.html.j2:71
@@ -898,15 +1611,15 @@ msgstr ""
#: template/glossary.html.j2:73
msgid ""
-"The GNU Name System allows every ego (or identity) to securely and "
-"privately associate any number of label-value pairs with an ego. The "
-"values are called record sets following the terminology of the Domain "
-"Name System (DNS). The mapping of labels to record sets for a given ego "
-"is called a namespace. <br> If records are made public and thus "
-"published, it is possible for other users to lookup the record given the "
-"ego's public key and the label. Here, not only the label can thus act as "
-"a passphrase but also the public key -- which despite its name may not be"
-" public knowledge and is never disclosed by the GNS protocol itself."
+"The GNU Name System allows every ego (or identity) to securely and privately "
+"associate any number of label-value pairs with an ego. The values are called "
+"record sets following the terminology of the Domain Name System (DNS). The "
+"mapping of labels to record sets for a given ego is called a namespace. <br> "
+"If records are made public and thus published, it is possible for other "
+"users to lookup the record given the ego's public key and the label. Here, "
+"not only the label can thus act as a passphrase but also the public key -- "
+"which despite its name may not be public knowledge and is never disclosed by "
+"the GNS protocol itself."
msgstr ""
#: template/glossary.html.j2:89
@@ -915,17 +1628,17 @@ msgstr ""
#: template/glossary.html.j2:91
msgid ""
-"A \"peer\" is an instance of GNUnet with its own per-instance public key "
-"and network addresses. Technically, it is possible to run multiple peers "
-"on the same host, but this only makes sense for testing. <br> By design "
-"GNUnet supports multiple users to share the same peer, just as UNIX is a "
-"multi-user system. A \"peer\" typically consists of a set of foundational"
-" GNUnet services running as the \"gnunet\" user and allowing all users in"
-" the \"gnunet\" group to utilize the API. On multi-user systems, "
-"additional \"personalized\" services may be required per user. <br> While"
-" peers are also identified by public keys, these public keys are "
-"completely unrelated to egos or identities. Namespaces cannot be "
-"associated with a peer, only with egos."
+"A \"peer\" is an instance of GNUnet with its own per-instance public key and "
+"network addresses. Technically, it is possible to run multiple peers on the "
+"same host, but this only makes sense for testing. <br> By design GNUnet "
+"supports multiple users to share the same peer, just as UNIX is a multi-user "
+"system. A \"peer\" typically consists of a set of foundational GNUnet "
+"services running as the \"gnunet\" user and allowing all users in the "
+"\"gnunet\" group to utilize the API. On multi-user systems, additional "
+"\"personalized\" services may be required per user. <br> While peers are "
+"also identified by public keys, these public keys are completely unrelated "
+"to egos or identities. Namespaces cannot be associated with a peer, only "
+"with egos."
msgstr ""
#: template/gns.html.j2:13 template/gnurl.html.j2:60
@@ -935,28 +1648,24 @@ msgstr ""
#: template/gns.html.j2:15
msgid ""
"The Domain Name System today enables traffic amplification attacks, "
-"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive "
-"cyber war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as "
-"DoT, DoH, DNSSEC, DPRIVE and the like will not fix this. This is why we "
-"built the GNU Name System (GNS), a secure, decentralized name system "
-"built on top of GNUnet."
+"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive cyber "
+"war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as DoT, DoH, "
+"DNSSEC, DPRIVE and the like will not fix this. This is why we built the GNU "
+"Name System (GNS), a secure, decentralized name system built on top of "
+"GNUnet."
msgstr ""
#: template/gns.html.j2:28
msgid "Overview"
msgstr ""
-#: template/gns.html.j2:37
-msgid "Features"
-msgstr ""
-
#: template/gns.html.j2:39
msgid ""
"The GNU Name System (GNS) is secure and decentralized naming system. It "
-"allows its users to register names as top-level domains (TLDs) and "
-"resolve other namespaces within their TLDs. <br/> GNS is designed to "
-"provide: <ul> <li>Censorship resistance</li> <li>Query privacy</li> "
-"<li>Secure name resolution</li> <li>Compatibility with DNS</li>"
+"allows its users to register names as top-level domains (TLDs) and resolve "
+"other namespaces within their TLDs. <br/> GNS is designed to provide: <ul> "
+"<li>Censorship resistance</li> <li>Query privacy</li> <li>Secure name "
+"resolution</li> <li>Compatibility with DNS</li>"
msgstr ""
#: template/gns.html.j2:52
@@ -965,23 +1674,23 @@ msgstr ""
#: template/gnurl.html.j2:21
msgid ""
-"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support "
-"only HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend "
-"(GnuTLS) to ensure a small footprint and uniform experience for "
-"developers regardless of how libcurl was compiled."
+"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support only "
+"HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend (GnuTLS) to "
+"ensure a small footprint and uniform experience for developers regardless of "
+"how libcurl was compiled."
msgstr ""
#: template/gnurl.html.j2:30
msgid ""
-"Our main usecase is for GNUnet and Taler, but it might be usable for "
-"others, hence we're releasing the code to the general public."
+"Our main usecase is for GNUnet and Taler, but it might be usable for others, "
+"hence we're releasing the code to the general public."
msgstr ""
#: template/gnurl.html.j2:37
msgid ""
"libgnurl is released under the same license as libcurl. Please read the "
-"README for instructions, as you must supply the correct options to "
-"configure to get a proper build of libgnurl."
+"README for instructions, as you must supply the correct options to configure "
+"to get a proper build of libgnurl."
msgstr ""
#: template/gnurl.html.j2:48
@@ -990,58 +1699,55 @@ msgstr ""
#: template/gnurl.html.j2:50
msgid ""
-"Large parts of the following 6 paragraphs are old and need to be "
-"rewritten."
+"Large parts of the following 6 paragraphs are old and need to be rewritten."
msgstr ""
#: template/gnurl.html.j2:62
msgid ""
-"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, "
-"but other variants are used by some distributions. Supporting other "
-"crypto backends would again expose us to a wider array of security "
-"issues, may create licensing issues and most importantly introduce new "
-"bugs as some crypto backends are known to introduce subtle runtime "
-"issues. While it is possible to have two versions of libcurl installed on"
-" the same system, this is error-prone, especially as if we are linked "
-"against the wrong version, the bugs that arise might be rather subtle."
+"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, but "
+"other variants are used by some distributions. Supporting other crypto "
+"backends would again expose us to a wider array of security issues, may "
+"create licensing issues and most importantly introduce new bugs as some "
+"crypto backends are known to introduce subtle runtime issues. While it is "
+"possible to have two versions of libcurl installed on the same system, this "
+"is error-prone, especially as if we are linked against the wrong version, "
+"the bugs that arise might be rather subtle."
msgstr ""
#: template/gnurl.html.j2:75
msgid ""
-"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, "
-"it would anyway be necessary to recompile cURL for GNUnet. But what "
-"happens if one links cURL against this version of GnuTLS? Well, first one"
-" would install GnuTLS by hand in the system. Then, we build cURL. cURL "
-"will build against it just fine, but the linker will eventually complain "
-"bitterly. The reason is that cURL also links against a bunch of other "
-"system libraries (gssapi, ldap, ssh2, rtmp, krb5, sasl2, see discussion "
-"on obscure protocols above), which --- as they are part of the "
-"distribution --- were linked against an older version of GnuTLS. As a "
-"result, the same binary would be linked against two different versions of"
-" GnuTLS. That is typically a recipe for disaster. Thus, in order to avoid"
-" updating a dozen system libraries (and having two versions of those "
-"installed), it is necessary to disable all of those cURL features that "
-"GNUnet does not use, and there are many of those. For GNUnet, the more "
-"obscure protocols supported by cURL are close to dead code --- mostly "
-"harmless, but not useful. However, as some application may use one of "
-"those features, distributions are typically forced to enable all of those"
-" features, and thus including security issues that might arise from that "
-"code."
+"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, it "
+"would anyway be necessary to recompile cURL for GNUnet. But what happens if "
+"one links cURL against this version of GnuTLS? Well, first one would install "
+"GnuTLS by hand in the system. Then, we build cURL. cURL will build against "
+"it just fine, but the linker will eventually complain bitterly. The reason "
+"is that cURL also links against a bunch of other system libraries (gssapi, "
+"ldap, ssh2, rtmp, krb5, sasl2, see discussion on obscure protocols above), "
+"which --- as they are part of the distribution --- were linked against an "
+"older version of GnuTLS. As a result, the same binary would be linked "
+"against two different versions of GnuTLS. That is typically a recipe for "
+"disaster. Thus, in order to avoid updating a dozen system libraries (and "
+"having two versions of those installed), it is necessary to disable all of "
+"those cURL features that GNUnet does not use, and there are many of those. "
+"For GNUnet, the more obscure protocols supported by cURL are close to dead "
+"code --- mostly harmless, but not useful. However, as some application may "
+"use one of those features, distributions are typically forced to enable all "
+"of those features, and thus including security issues that might arise from "
+"that code."
msgstr ""
#: template/gnurl.html.j2:99
msgid ""
-"So to use a modern version of GnuTLS, a sane approach is to disable all "
-"of the \"optional\" features of cURL that drag in system libraries that "
-"link against the older GnuTLS. That works, except that one should then "
-"NEVER install that version of libcurl in say /usr or /usr/local, as that "
-"may break other parts of the system that might depend on these features "
-"that we just disabled. Libtool versioning doesn't help here, as it is not"
-" intended to deal with libraries that have optional features. Naturally, "
-"installing cURL somewhere else is also problematic, as we now need to be "
-"really careful that the linker will link GNUnet against the right "
-"version. Note that none of this can really be trivially fixed by the cURL"
-" developers."
+"So to use a modern version of GnuTLS, a sane approach is to disable all of "
+"the \"optional\" features of cURL that drag in system libraries that link "
+"against the older GnuTLS. That works, except that one should then NEVER "
+"install that version of libcurl in say /usr or /usr/local, as that may break "
+"other parts of the system that might depend on these features that we just "
+"disabled. Libtool versioning doesn't help here, as it is not intended to "
+"deal with libraries that have optional features. Naturally, installing cURL "
+"somewhere else is also problematic, as we now need to be really careful that "
+"the linker will link GNUnet against the right version. Note that none of "
+"this can really be trivially fixed by the cURL developers."
msgstr ""
#: template/gnurl.html.j2:118
@@ -1052,19 +1758,19 @@ msgstr ""
#, python-format
msgid ""
"How does forking fix it? Easy. First, we can get rid of all of the "
-"compatibility issues --- if you use libgnurl, you state that you "
-"don't need anything but HTTP/HTTPS. Those applications that need "
-"more, should stick with the original cURL. Those that do not, can choose "
-"to move to something simpler. As the library gets a new name, we do not "
-"have to worry about tons of packages breaking as soon as one rebuilds it."
-" So renaming itself and saying that \"libgnurl = libcurl with only "
-"HTTP/HTTPS support and GnuTLS\" fixes 99%% of the problems that darkened "
-"my mood. Note that this pretty much CANNOT be done without a fork, as "
-"renaming is an essential part of the fix. Now, there might be creative "
-"solutions to achieve the same thing within the standard cURL build "
-"system, but this was deemed to be too much work when gnurl was originally"
-" started. The changes libgnurl makes to curl are miniscule and can easily"
-" be applied again and again whenever libcurl makes a new release."
+"compatibility issues --- if you use libgnurl, you state that you don't "
+"need anything but HTTP/HTTPS. Those applications that need more, should "
+"stick with the original cURL. Those that do not, can choose to move to "
+"something simpler. As the library gets a new name, we do not have to worry "
+"about tons of packages breaking as soon as one rebuilds it. So renaming "
+"itself and saying that \"libgnurl = libcurl with only HTTP/HTTPS support and "
+"GnuTLS\" fixes 99%% of the problems that darkened my mood. Note that this "
+"pretty much CANNOT be done without a fork, as renaming is an essential part "
+"of the fix. Now, there might be creative solutions to achieve the same thing "
+"within the standard cURL build system, but this was deemed to be too much "
+"work when gnurl was originally started. The changes libgnurl makes to curl "
+"are miniscule and can easily be applied again and again whenever libcurl "
+"makes a new release."
msgstr ""
#: template/gnurl.html.j2:142
@@ -1073,14 +1779,13 @@ msgstr ""
#: template/gnurl.html.j2:144
msgid ""
-"Projects that use cURL only for HTTP/HTTPS and that would work with "
-"GnuTLS should be able to switch to libgnurl by changing \"-lcurl\" to "
-"\"-lgnurl\". That's it. No changes to the source code should be "
-"required, as libgnurl strives for bug-for-bug compatibility with the "
-"HTTP/HTTPS/GnuTLS subset of cURL. We might add new features relating to "
-"this core subset if they are proposed, but so far we have kept our "
-"changes minimal and no additions to the original curl source have been "
-"written."
+"Projects that use cURL only for HTTP/HTTPS and that would work with GnuTLS "
+"should be able to switch to libgnurl by changing \"-lcurl\" to \"-lgnurl\". "
+"That's it. No changes to the source code should be required, as libgnurl "
+"strives for bug-for-bug compatibility with the HTTP/HTTPS/GnuTLS subset of "
+"cURL. We might add new features relating to this core subset if they are "
+"proposed, but so far we have kept our changes minimal and no additions to "
+"the original curl source have been written."
msgstr ""
#: template/gnurl.html.j2:161
@@ -1089,15 +1794,15 @@ msgstr ""
#: template/gnurl.html.j2:163
msgid ""
-"libgnurl and gnurl are not intended to be used as a replacement for curl "
-"for users: <br> This does not mean there is no confidence in the work "
-"done with gnurl, it means that tools which expect curl or libcurl will "
-"not make use of a different named binary and library. If you know what "
-"you are doing, you should be able to use gnurl as part of your tooling in"
-" place of curl. We do not recommend to do so however, as the only usage "
-"it is tested for <em>so far</em> is as part of Taler's and "
-"GNunet's build-system. <br> Since no conflicts in filenames occur you"
-" are not expected to remove curl to make use of gnurl and viceversa."
+"libgnurl and gnurl are not intended to be used as a replacement for curl for "
+"users: <br> This does not mean there is no confidence in the work done with "
+"gnurl, it means that tools which expect curl or libcurl will not make use of "
+"a different named binary and library. If you know what you are doing, you "
+"should be able to use gnurl as part of your tooling in place of curl. We do "
+"not recommend to do so however, as the only usage it is tested for <em>so "
+"far</em> is as part of Taler's and GNunet's build-system. <br> Since "
+"no conflicts in filenames occur you are not expected to remove curl to make "
+"use of gnurl and viceversa."
msgstr ""
#: template/gnurl.html.j2:188
@@ -1110,16 +1815,15 @@ msgstr ""
#: template/gnurl.html.j2:211
msgid ""
-"Releases are published on <a "
-"href=\"https://ftpmirror.gnu.org/gnu/gnunet/\";>ftpmirror.gnu.org/gnu/gnunet</a>."
-" gnurl is available from within a variety of distributions and package "
-"managers. Some Package Managers which include gnurl are: <a "
-"href=\"https://www.gnu.org/software/guix/\";>GNU Guix</a> (available as "
-"\"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> through the "
-"collaborative ebuild collection <a href=\"https://git.gnunet.org";
-"/youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a "
-"href=\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a "
-"href=\"https://pkgsrc.org\";>pkgsrc</a>."
+"Releases are published on <a href=\"https://ftpmirror.gnu.org/gnu/gnunet/";
+"\">ftpmirror.gnu.org/gnu/gnunet</a>. gnurl is available from within a "
+"variety of distributions and package managers. Some Package Managers which "
+"include gnurl are: <a href=\"https://www.gnu.org/software/guix/\";>GNU Guix</"
+"a> (available as \"gnurl\"), <a href=\"https://gentoo.org\";>Gentoo</a> "
+"through the collaborative ebuild collection <a href=\"https://git.gnunet.org/";
+"youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a href="
+"\"https://nixos.org/nix/\";>Nix</a>, and as www/gnurl in <a href=\"https://";
+"pkgsrc.org\">pkgsrc</a>."
msgstr ""
#: template/gnurl.html.j2:228
@@ -1128,17 +1832,17 @@ msgstr ""
#: template/gnurl.html.j2:230
msgid ""
-"We suggest to closely follow release announcements, as they might "
-"indicate changes in how gnurl is to be build. <br> If your package "
-"manager provides a binary build or build instructions to build gnurl from"
-" source automated and integrated with your environment, we strongly "
-"suggest to use this binary build. <br> There are two ways to build gnurl."
-" The first one builds from the most recent git tag, the second one uses "
-"the distributed tarball. Distributors generally are supposed to build "
-"from the tarball, but we describe both methods here. Both methods are "
-"written with a NetBSD 9 userland in mind, substitute tools as necessary. "
-"<br> You should <b>avoid</b> building gnurl from the tip of the default "
-"git branch, as only tags are considered to be stable and approved builds."
+"We suggest to closely follow release announcements, as they might indicate "
+"changes in how gnurl is to be build. <br> If your package manager provides a "
+"binary build or build instructions to build gnurl from source automated and "
+"integrated with your environment, we strongly suggest to use this binary "
+"build. <br> There are two ways to build gnurl. The first one builds from the "
+"most recent git tag, the second one uses the distributed tarball. "
+"Distributors generally are supposed to build from the tarball, but we "
+"describe both methods here. Both methods are written with a NetBSD 9 "
+"userland in mind, substitute tools as necessary. <br> You should <b>avoid</"
+"b> building gnurl from the tip of the default git branch, as only tags are "
+"considered to be stable and approved builds."
msgstr ""
#: template/gnurl.html.j2:251
@@ -1147,8 +1851,8 @@ msgstr ""
#: template/gnurl.html.j2:253
msgid ""
-"If you want to verify the signature, install an OpenPGP compatible tool "
-"such as security/gnupgp2 (and set it up). Assuming you use pkgin:"
+"If you want to verify the signature, install an OpenPGP compatible tool such "
+"as security/gnupgp2 (and set it up). Assuming you use pkgin:"
msgstr ""
#: template/gnurl.html.j2:267
@@ -1161,8 +1865,7 @@ msgstr ""
#: template/gnurl.html.j2:276
msgid ""
-"Fetch the release, the signature, the checksum file as well as its "
-"signature:"
+"Fetch the release, the signature, the checksum file as well as its signature:"
msgstr ""
#: template/gnurl.html.j2:295
@@ -1211,8 +1914,8 @@ msgstr ""
#: template/gnurl.html.j2:371
msgid ""
-"Follow the steps above, but instead of downloading the tarball, clone the"
-" git tag you want to build from."
+"Follow the steps above, but instead of downloading the tarball, clone the "
+"git tag you want to build from."
msgstr ""
#: template/gnurl.html.j2:382
@@ -1221,10 +1924,9 @@ msgstr ""
#: template/gnurl.html.j2:384
msgid ""
-"You can report bugs on our bug tracker: <a "
-"href=\"https://bugs.gnunet.org/\";>bugs.gnunet.org</a>. Alternatively you "
-"can use our bug mailinglist, but we prefer to track bugs on the "
-"bugtracker."
+"You can report bugs on our bug tracker: <a href=\"https://bugs.gnunet.org/";
+"\">bugs.gnunet.org</a>. Alternatively you can use our bug mailinglist, but "
+"we prefer to track bugs on the bugtracker."
msgstr ""
#: template/gnurl.html.j2:395
@@ -1235,10 +1937,9 @@ msgstr ""
msgid ""
"gnurl/libgnurl is looking for a new maintainer. Releases after version "
"7.69.1 and up to version 7.72.0 were signed with the OpenPGP Key "
-"<b>0xD6B570842F7E7F8D</b> (<a "
-"href=\"https://keys.openpgp.org/search?q=6115012DEA3026F62A98A556D6B570842F7E7F8D\";>keys.openpgp.org</a>),"
-" with the key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E"
-" 7F8D</b>."
+"<b>0xD6B570842F7E7F8D</b> (<a href=\"https://keys.openpgp.org/search?";
+"q=6115012DEA3026F62A98A556D6B570842F7E7F8D\">keys.openpgp.org</a>), with the "
+"key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E 7F8D</b>."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:7
@@ -1252,68 +1953,65 @@ msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:18
msgid ""
"In the context of Google Summer of Code 2018, my mentor (Martin "
-"Schanzenbach) and I have worked on creating and extending the REST API of"
-" GNUnet. Currently, we mirrored the functionality of following commands:"
+"Schanzenbach) and I have worked on creating and extending the REST API of "
+"GNUnet. Currently, we mirrored the functionality of following commands:"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:32
msgid ""
-"Additionally, we developed a website with the Javascript framework "
-"Angular 6 and the design framework iotaCSS to use the new REST API. The "
-"REST API of GNUnet is now documented with Sphinx."
+"Additionally, we developed a website with the Javascript framework Angular 6 "
+"and the design framework iotaCSS to use the new REST API. The REST API of "
+"GNUnet is now documented with Sphinx."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:41
msgid ""
-"... when you can use the command line tools? We need to keep in mind, "
-"that everyone has the right to stay secure and private but not everyone "
-"feels comfortable using a terminal. The further developed REST access to "
-"GNUnet APIs in addition to the new web application allows new users to "
-"interact with GNUnet over a well known tool: their browsers. This "
-"addition to the C API and the command line tools may attract new users "
-"and developers."
+"... when you can use the command line tools? We need to keep in mind, that "
+"everyone has the right to stay secure and private but not everyone feels "
+"comfortable using a terminal. The further developed REST access to GNUnet "
+"APIs in addition to the new web application allows new users to interact "
+"with GNUnet over a well known tool: their browsers. This addition to the C "
+"API and the command line tools may attract new users and developers."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:54
msgid ""
"<li> The REST API developed in GNUnet<br> The REST API is already merged "
-"into the gnunet.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet.git/\";>GNUnet Main Git</a>).<br /> "
-"To use the new features, clone the repository and follow the <a "
-"href=\"https://gnunet.org/en/install.html\";>Installation</a> on "
-"gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
-"</li> <li> The Web Application<br> The web application is available under"
-" the gnunet-webui.git repository (<a href=\"https://gnunet.org/git";
-"/gnunet-webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the"
-" newest version of 'node' and 'yarn'. Dependent on your system, you may "
-"need to download newer versions and install them manually and not over "
-"your packet manager. After the installation succeeded, you need to clone "
-"the repository. Then, you need to run \"yarn install\" and \"yarn start\""
-" for testing purposes. To deploy the website (keep in mind, that this "
-"website communicates with another localhost instance) use \"yarn build\" "
-"for building the web application and use the output in the 'dist' "
-"directory. </li> <li> The Documentation<br /> The documentation is "
-"available under the gnunet-rest-api.git repository (<a "
-"href=\"https://gnunet.org/git/gnunet-rest-api.git/\";>GNUnet REST API "
-"Docmentation Git</a>).<br /> Clone the repository and \"make html\". Then"
-" open the 'index.html' under 'build/html/'. </li>"
+"into the gnunet.git repository (<a href=\"https://gnunet.org/git/gnunet.git/";
+"\">GNUnet Main Git</a>).<br /> To use the new features, clone the repository "
+"and follow the <a href=\"https://gnunet.org/en/install.html\";>Installation</"
+"a> on gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
+"</li> <li> The Web Application<br> The web application is available under "
+"the gnunet-webui.git repository (<a href=\"https://gnunet.org/git/gnunet-";
+"webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the newest "
+"version of 'node' and 'yarn'. Dependent on your system, you may need to "
+"download newer versions and install them manually and not over your packet "
+"manager. After the installation succeeded, you need to clone the repository. "
+"Then, you need to run \"yarn install\" and \"yarn start\" for testing "
+"purposes. To deploy the website (keep in mind, that this website "
+"communicates with another localhost instance) use \"yarn build\" for "
+"building the web application and use the output in the 'dist' directory. </"
+"li> <li> The Documentation<br /> The documentation is available under the "
+"gnunet-rest-api.git repository (<a href=\"https://gnunet.org/git/gnunet-rest-";
+"api.git/\">GNUnet REST API Docmentation Git</a>).<br /> Clone the repository "
+"and \"make html\". Then open the 'index.html' under 'build/html/'. </li>"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:91
msgid ""
-"Please, give it a try and contact me, if you find any bugs or "
-"unintentional features. ;)"
+"Please, give it a try and contact me, if you find any bugs or unintentional "
+"features. ;)"
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:98
msgid ""
"Right now, the build process of the web application may be a little too "
-"complex for a casual user. We may be able to solve this by using "
-"docker.<br /> Additionally, the web application does not prevent wrong "
-"inputs but responds with error messages. Adding GNUnet Records is "
-"currently only usable for people, who know how a GNS Record looks like. "
-"This can be adapted to each record type.<br /> Last but not least, "
-"additional features, design changes, etc..."
+"complex for a casual user. We may be able to solve this by using docker.<br /"
+"> Additionally, the web application does not prevent wrong inputs but "
+"responds with error messages. Adding GNUnet Records is currently only usable "
+"for people, who know how a GNS Record looks like. This can be adapted to "
+"each record type.<br /> Last but not least, additional features, design "
+"changes, etc..."
msgstr ""
#: template/gsoc-2018-gnunet-webui.html.j2:111
@@ -1340,100 +2038,95 @@ msgstr ""
msgid ""
"As a GNU project, GNUnet has participated in the Google Summer of Code "
"(GSoC) for a number of years. This page lists all current, past, and "
-"finished projects. If you want to participate and apply for any of the "
-"ideas for 2020 below or any past project which is not yet finished (or "
-"even your own idea), please contact us either in IRC or mailing list."
+"finished projects. If you want to participate and apply for any of the ideas "
+"for 2020 below or any past project which is not yet finished (or even your "
+"own idea), please contact us either in IRC or mailing list."
msgstr ""
#: template/gsoc.html.j2:34
msgid ""
-"The GNUnet team is currently working on a transport layer rewrite in "
-"order to fix core issues with connectivity. This new component is "
-"currently developed under the name \"TNG\". What is currently known as "
-"\"transport plugins\" will in the TNG be represented as "
-"\"communicators\". Communicators are processes with a well defined API "
-"that allow to connect peers over a specific protocol. The primary "
-"protocol which are already implemented are UNIX sockets, UDP sockets, and"
-" TCP sockets. For a truly resilient network, other connectivity options "
-"such as WiFi mesh, Bluetooth, HTTP(S), QUIC or even more obscure "
-"alternatives such as radio are required. In this project, the goal is to "
-"select, implement and test new communicators. While TNG is not yet ready,"
-" communicators can, by design, be developed and tested against the "
-"current API. We expect that this project can be worked on by multiple "
+"The GNUnet team is currently working on a transport layer rewrite in order "
+"to fix core issues with connectivity. This new component is currently "
+"developed under the name \"TNG\". What is currently known as \"transport "
+"plugins\" will in the TNG be represented as \"communicators\". Communicators "
+"are processes with a well defined API that allow to connect peers over a "
+"specific protocol. The primary protocol which are already implemented are "
+"UNIX sockets, UDP sockets, and TCP sockets. For a truly resilient network, "
+"other connectivity options such as WiFi mesh, Bluetooth, HTTP(S), QUIC or "
+"even more obscure alternatives such as radio are required. In this project, "
+"the goal is to select, implement and test new communicators. While TNG is "
+"not yet ready, communicators can, by design, be developed and tested against "
+"the current API. We expect that this project can be worked on by multiple "
"students as there are a lot of protocols to choose from. The tasks would "
"consist of: <ol> <li>Deciding which communicators to implement.</li> "
-"<li>Test the communicators.</li> <li>Documentation.</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of HTTPS, QUIC, Bluetooth or WiFi.</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Average, but depends on selected protocols. "
-"<br/> <strong>Mentors:</strong> Martin Schanzenbach, t3sserakt"
+"<li>Test the communicators.</li> <li>Documentation.</li> </ol> Advantageous "
+"skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge of HTTPS, QUIC, "
+"Bluetooth or WiFi.</li> </ol> <br/> <strong>Difficulty:</strong> Average, "
+"but depends on selected protocols. <br/> <strong>Mentors:</strong> Martin "
+"Schanzenbach, t3sserakt"
msgstr ""
#: template/gsoc.html.j2:79
msgid ""
-"The REST API currently only supports a single user system. This is an "
-"issue as on multi-user systems, access control must be enfoced on a per-"
-"user basis. In this project, the REST service must be extended to support"
-" user authentication. This includes the correct handling of user context "
-"switches. <ol> <li>Implement user authentication.</li> <li>Test the "
-"access control.</li> <li>Document the changes to the REST API.</li> </ol>"
-" Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge "
-"of user authentication subsystems on Linux/Unix.</li> <li>REST/HTTP "
-"Authentication methods</li> </ol> <br/> <strong>Difficulty:</strong> "
-"Beginner <br/> <strong>Mentors:</strong> Martin Schanzenbach"
+"The REST API currently only supports a single user system. This is an issue "
+"as on multi-user systems, access control must be enfoced on a per-user "
+"basis. In this project, the REST service must be extended to support user "
+"authentication. This includes the correct handling of user context switches. "
+"<ol> <li>Implement user authentication.</li> <li>Test the access control.</"
+"li> <li>Document the changes to the REST API.</li> </ol> Advantageous skills/"
+"languages/frameworks: <ol> <li>C</li> <li>Knowledge of user authentication "
+"subsystems on Linux/Unix.</li> <li>REST/HTTP Authentication methods</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:111
msgid ""
-"reclaimID is a decentralized identity system build on top of the GNU Name"
-" System. Currently, there is a Webextension which uses the GNUnet <a "
-"href=\"https://rest.gnunet.org\";>REST API</a>. In order to improve "
-"adoption and ease of use, this project aims to include a full GNUnet node"
-" within the Webextention as a fallback. GNUnet can be compiled to Web "
-"Assembly or JavaScript as demonstrated <a "
-"href=\"https://gnunet.io\";>here</a>. The idea is to improve upon this "
-"concept and support more of GNUnet's subsystems. The difficulty of this "
-"project largely depends on the students proficiency with build tools, "
-"emscripten and improvisation skills. There non-exhaustive task list would"
-" be: <ol> <li>Improve existing GNUnet emscripten build to include more "
-"subsystems.</li> <li>Integrate the result into a Webextention.</li> "
+"reclaimID is a decentralized identity system build on top of the GNU Name "
+"System. Currently, there is a Webextension which uses the GNUnet <a href="
+"\"https://rest.gnunet.org\";>REST API</a>. In order to improve adoption and "
+"ease of use, this project aims to include a full GNUnet node within the "
+"Webextention as a fallback. GNUnet can be compiled to Web Assembly or "
+"JavaScript as demonstrated <a href=\"https://gnunet.io\";>here</a>. The idea "
+"is to improve upon this concept and support more of GNUnet's subsystems. The "
+"difficulty of this project largely depends on the students proficiency with "
+"build tools, emscripten and improvisation skills. There non-exhaustive task "
+"list would be: <ol> <li>Improve existing GNUnet emscripten build to include "
+"more subsystems.</li> <li>Integrate the result into a Webextention.</li> "
"<li>Integrate the result into the re:claimID Webextension</li> </ol> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> "
-"<li>emscripten</li> <li>Webextensions</li> </ol> <br/> "
-"<strong>Difficulty:</strong> Challenging <br/> <strong>Mentors:</strong> "
-"Martin Schanzenbach"
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>emscripten</"
+"li> <li>Webextensions</li> </ol> <br/> <strong>Difficulty:</strong> "
+"Challenging <br/> <strong>Mentors:</strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:147
msgid ""
-"Currently, the keys in our statistics database are too verbose. For "
-"example: </p> <p> nse # flood messages received: 13<br/> nse # peers "
-"connected: 4<br/> nse # nodes in the network (estimate): 203<br/> nse # "
-"flood messages started: 5<br/> nse # estimated network diameter: 3<br/> "
-"nse # flood messages transmitted: 10<br/> </p> <p> With such verbose keys"
-" there's no easy way to form compact JSON document or entries for time-"
-"series database. And you can't query single stats without having to "
-"copypaste the line exactly and put in quotes. In short, the goals are "
-"to... <ol> <li>Think of a way how statistics entries can be made "
-"canonical.</li> <li>Implement the change and migrate existing uses.</li> "
-"<li>Document the format(s) and define an appropriate registration "
-"mechanism for identifiers</li> </ol> Relevant bugs: <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
-"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> "
-"</ol> <br/> <strong>Difficulty:</strong> Beginner <br/> "
-"<strong>Mentors:</strong> Martin Schanzenbach"
+"Currently, the keys in our statistics database are too verbose. For example: "
+"</p> <p> nse # flood messages received: 13<br/> nse # peers connected: 4<br/"
+"> nse # nodes in the network (estimate): 203<br/> nse # flood messages "
+"started: 5<br/> nse # estimated network diameter: 3<br/> nse # flood "
+"messages transmitted: 10<br/> </p> <p> With such verbose keys there's no "
+"easy way to form compact JSON document or entries for time-series database. "
+"And you can't query single stats without having to copypaste the line "
+"exactly and put in quotes. In short, the goals are to... <ol> <li>Think of a "
+"way how statistics entries can be made canonical.</li> <li>Implement the "
+"change and migrate existing uses.</li> <li>Document the format(s) and define "
+"an appropriate registration mechanism for identifiers</li> </ol> Relevant "
+"bugs: <a href=\"https://bugs.gnunet.org/view.php?id=5650\";>#5650</a><br/> "
+"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> </"
+"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
+"strong> Martin Schanzenbach"
msgstr ""
#: template/gsoc.html.j2:187
msgid ""
-"The goal is to either build upon the (outdated) <a "
-"href=\"https://github.com/canndrew/gnunet-rs\";>GNUnet Rust bindings</a> "
-"or to follow the path of <a href=\"GNUnet Go\">https://github.com/bfix";
-"/gnunet-go</a> which tries to reimplement most of the GNUnet stack. The "
-"end result should be an extension template for GNUnet in the form of the "
-"existing <a href=\"https://git.gnunet.org/gnunet-ext.git/\";>C "
-"template</a> which allows to quickly start implementing services and "
-"libraries for GNUnet."
+"The goal is to either build upon the (outdated) <a href=\"https://github.com/";
+"canndrew/gnunet-rs\">GNUnet Rust bindings</a> or to follow the path of <a "
+"href=\"GNUnet Go\">https://github.com/bfix/gnunet-go</a> which tries to "
+"reimplement most of the GNUnet stack. The end result should be an extension "
+"template for GNUnet in the form of the existing <a href=\"https://git.gnunet.";
+"org/gnunet-ext.git/\">C template</a> which allows to quickly start "
+"implementing services and libraries for GNUnet."
msgstr ""
#: template/gsoc.html.j2:198 template/gsoc.html.j2:652
@@ -1458,27 +2151,26 @@ msgstr ""
#: template/gsoc.html.j2:229
msgid ""
-"Includes: Implementation of rudimentary Android compatibility for GNUnet,"
-" in part by porting the GNUnet utils scheduler to act as a thin wrapper "
-"over libuv."
+"Includes: Implementation of rudimentary Android compatibility for GNUnet, in "
+"part by porting the GNUnet utils scheduler to act as a thin wrapper over "
+"libuv."
msgstr ""
#: template/gsoc.html.j2:236
msgid ""
-"<strong>Mentors:</strong> <a href=\"https://www.goebel-";
-"consult.de/\">Hartmut Goebel</a>, Jeff Burdges, Christian Grothoff"
+"<strong>Mentors:</strong> <a href=\"https://www.goebel-consult.de/\";>Hartmut "
+"Goebel</a>, Jeff Burdges, Christian Grothoff"
msgstr ""
#: template/gsoc.html.j2:245
msgid ""
-"There is a push for migrating our CI to Gitlab. The CI should eventually "
-"not just run \"make check\" on various platforms, but also perform tests "
-"with multiple peers running in different VMs with specific network "
-"topologies (i.e. NAT) between them being simulated. The CI should also be"
-" integrated with Gauger for performance regression analysis. Running jobs"
-" only when dependencies have changed and scripting more granular triggers"
-" or ideally automatic dependency discovery (as done by the autotools) is "
-"also important."
+"There is a push for migrating our CI to Gitlab. The CI should eventually not "
+"just run \"make check\" on various platforms, but also perform tests with "
+"multiple peers running in different VMs with specific network topologies (i."
+"e. NAT) between them being simulated. The CI should also be integrated with "
+"Gauger for performance regression analysis. Running jobs only when "
+"dependencies have changed and scripting more granular triggers or ideally "
+"automatic dependency discovery (as done by the autotools) is also important."
msgstr ""
#: template/gsoc.html.j2:257
@@ -1487,19 +2179,18 @@ msgstr ""
#: template/gsoc.html.j2:267
msgid ""
-"One great problem of the current Internet is the lack of "
-"disintermediation. When people want to talk they need a chat service. "
-"When they want to share files they need a file transfer service. Although"
-" GNUnet already possesses quite advanced integration into Linux "
-"networking, a little extra work is needed for existing applications like "
-"irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by"
-" using a GNS hostname like friend.gnu. Once people have added a person to"
-" their GNS they can immediately message, exchange files and suchlike "
-"directly, with nothing but the GNUnet in the middle, using applications "
-"that have been distributed with unix systems ever since the 1980's. We "
-"can produce an OS distribution where these things work out of the box "
-"with the nicknames of people instead of cloud services. For more "
-"information and context, read"
+"One great problem of the current Internet is the lack of disintermediation. "
+"When people want to talk they need a chat service. When they want to share "
+"files they need a file transfer service. Although GNUnet already possesses "
+"quite advanced integration into Linux networking, a little extra work is "
+"needed for existing applications like irc, www, ftp, rsh, nntpd to run over "
+"it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. "
+"Once people have added a person to their GNS they can immediately message, "
+"exchange files and suchlike directly, with nothing but the GNUnet in the "
+"middle, using applications that have been distributed with unix systems ever "
+"since the 1980's. We can produce an OS distribution where these things work "
+"out of the box with the nicknames of people instead of cloud services. For "
+"more information and context, read"
msgstr ""
#: template/gsoc.html.j2:288
@@ -1508,8 +2199,7 @@ msgstr ""
#: template/gsoc.html.j2:296
msgid ""
-"Implement the AnycastExit spec to enable GNUnet clients to connect over "
-"Tor."
+"Implement the AnycastExit spec to enable GNUnet clients to connect over Tor."
msgstr ""
#: template/gsoc.html.j2:302 template/gsoc.html.j2:337
@@ -1520,9 +2210,9 @@ msgstr ""
#: template/gsoc.html.j2:307
msgid ""
"Note: There was a Special TLDs spec to allow Tor to resolve domain names "
-"using GNS over Tor too, but currently that's on hold until folks think "
-"more about how names should be moved around the local system. We're "
-"calling this more collaborative approach NSS2 for now."
+"using GNS over Tor too, but currently that's on hold until folks think more "
+"about how names should be moved around the local system. We're calling this "
+"more collaborative approach NSS2 for now."
msgstr ""
#: template/gsoc.html.j2:316 template/gsoc.html.j2:456
@@ -1532,17 +2222,16 @@ msgstr ""
#: template/gsoc.html.j2:329
msgid ""
-"Improve the Rust implementation of GNUnet utils, possibly including "
-"adding support for asynchronous IO using mio, or perhaps a higher level "
-"asynchronous IO library built upon it, such as rotor, mioco, eventual_io,"
-" or gj."
+"Improve the Rust implementation of GNUnet utils, possibly including adding "
+"support for asynchronous IO using mio, or perhaps a higher level "
+"asynchronous IO library built upon it, such as rotor, mioco, eventual_io, or "
+"gj."
msgstr ""
#: template/gsoc.html.j2:345
msgid ""
-"Implementation of a replacement for PANDA (see Pond) with better "
-"security, and maybe integration with the GNU Name System for key "
-"exchange."
+"Implementation of a replacement for PANDA (see Pond) with better security, "
+"and maybe integration with the GNU Name System for key exchange."
msgstr ""
#: template/gsoc.html.j2:357
@@ -1556,8 +2245,8 @@ msgstr ""
#: template/gsoc.html.j2:370
msgid ""
-"Implement different place types and file sharing by creating a new place "
-"for the shared content."
+"Implement different place types and file sharing by creating a new place for "
+"the shared content."
msgstr ""
#: template/gsoc.html.j2:376
@@ -1566,12 +2255,12 @@ msgstr ""
#: template/gsoc.html.j2:380
msgid ""
-"<ul> <li>File: generic file with comments</li> <li>Image: display an "
-"image with comments referencing a region of the image</li> <li>Sound: "
-"play a sound file with comments referencing a timestamp</li> "
-"<li>Directory/Album: pointers to File / Image / Sound places</li> "
-"<li>Event: with RSVP</li> <li>Survey: ask your social neighborhood "
-"questions in a structured form</li> </ul>"
+"<ul> <li>File: generic file with comments</li> <li>Image: display an image "
+"with comments referencing a region of the image</li> <li>Sound: play a sound "
+"file with comments referencing a timestamp</li> <li>Directory/Album: "
+"pointers to File / Image / Sound places</li> <li>Event: with RSVP</li> "
+"<li>Survey: ask your social neighborhood questions in a structured form</li> "
+"</ul>"
msgstr ""
#: template/gsoc.html.j2:391
@@ -1581,16 +2270,16 @@ msgstr ""
#: template/gsoc.html.j2:395
msgid ""
"<ul> <li>Fork existing channels, reorganize people into new chatrooms or "
-"channels.</li> <li>Share a post (edit and repost something elsewhere, on "
-"a fan page for example).</li> <li>Edit a previously published post + "
-"offer edit history to readers.</li> <li>Control expiry of channel "
-"history.</li> </ul>"
+"channels.</li> <li>Share a post (edit and repost something elsewhere, on a "
+"fan page for example).</li> <li>Edit a previously published post + offer "
+"edit history to readers.</li> <li>Control expiry of channel history.</li> </"
+"ul>"
msgstr ""
#: template/gsoc.html.j2:404
msgid ""
-"See also <a "
-"href=\"http://secushare.org/features\";>http://secushare.org/features</a>"
+"See also <a href=\"http://secushare.org/features\";>http://secushare.org/";
+"features</a>"
msgstr ""
#: template/gsoc.html.j2:409
@@ -1603,20 +2292,19 @@ msgstr ""
#: template/gsoc.html.j2:427
msgid ""
-"Implement aggregation of distributed state from various channels in order"
-" to provide for a powerful social graph API capable of producing social "
-"network profiles, dashboards, a calendar out of upcoming event "
-"invitations (if available), social search functionality and most of all "
-"to make it easy for users to adopt cryptographic identities of their "
-"contacts/friends simply by finding them in the social graph of their "
-"existing contacts (\"This is Linda. You have 11 contacts in common with "
-"her. [ADD]\")."
+"Implement aggregation of distributed state from various channels in order to "
+"provide for a powerful social graph API capable of producing social network "
+"profiles, dashboards, a calendar out of upcoming event invitations (if "
+"available), social search functionality and most of all to make it easy for "
+"users to adopt cryptographic identities of their contacts/friends simply by "
+"finding them in the social graph of their existing contacts (\"This is "
+"Linda. You have 11 contacts in common with her. [ADD]\")."
msgstr ""
#: template/gsoc.html.j2:445
msgid ""
-"Related to <a "
-"href=\"http://secushare.org/rendezvous\";>secushare.org/rendezvous</a>"
+"Related to <a href=\"http://secushare.org/rendezvous\";>secushare.org/"
+"rendezvous</a>"
msgstr ""
#: template/gsoc.html.j2:451 template/gsoc.html.j2:491
@@ -1625,21 +2313,21 @@ msgstr ""
#: template/gsoc.html.j2:468
msgid ""
-"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform "
-"traditional mail clients into secushare user interfaces. </li> <li> Think"
-" of ways to map e-mail addresses to secushare identities. </li> <li> "
-"Encode or translate various e-mail features into secushare equivalents. "
-"</li> <li> Parts of secushare are currently written in Rust, therefore "
-"Rust is preferred for this task but it is not an requirement. </li> </ul>"
+"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform traditional "
+"mail clients into secushare user interfaces. </li> <li> Think of ways to map "
+"e-mail addresses to secushare identities. </li> <li> Encode or translate "
+"various e-mail features into secushare equivalents. </li> <li> Parts of "
+"secushare are currently written in Rust, therefore Rust is preferred for "
+"this task but it is not an requirement. </li> </ul>"
msgstr ""
#: template/gsoc.html.j2:509
msgid ""
"Implementation of the GNUnet auction system described in Chapter 3 of <a "
"href=\"https://grothoff.org/christian/teich2017ms.pdf\";>this thesis</a>. "
-"Specific tasks are adding smart contract creation and round time "
-"enforcement to libbrandt as well as creating the GNUnet auction service, "
-"library and the three user interface programs create, info and join."
+"Specific tasks are adding smart contract creation and round time enforcement "
+"to libbrandt as well as creating the GNUnet auction service, library and the "
+"three user interface programs create, info and join."
msgstr ""
#: template/gsoc.html.j2:521
@@ -1648,9 +2336,9 @@ msgstr ""
#: template/gsoc.html.j2:539
msgid ""
-"Implementation of additional transports to make GNUnet communication more"
-" robust in the presence of problematic networks: GNUnet-over-SMTP, "
-"GNUnet-over-DNS"
+"Implementation of additional transports to make GNUnet communication more "
+"robust in the presence of problematic networks: GNUnet-over-SMTP, GNUnet-"
+"over-DNS"
msgstr ""
#: template/gsoc.html.j2:546 template/gsoc.html.j2:560
@@ -1664,16 +2352,16 @@ msgid ""
msgstr ""
#: template/gsoc.html.j2:568
-msgid "<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff
Burdges"
+msgid ""
+"<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff Burdges"
msgstr ""
#: template/gsoc.html.j2:576
msgid ""
-"Improving libaboss to make computation on shared secrets (including "
-"repeated multiplication) based on <a "
-"href=\"https://dl.acm.org/citation.cfm?doid=62212.62213\";>Ben-Or et "
-"al.</a> if possible. This in particular means moving libaboss to bignums "
-"(gcry_mpi)."
+"Improving libaboss to make computation on shared secrets (including repeated "
+"multiplication) based on <a href=\"https://dl.acm.org/citation.cfm?";
+"doid=62212.62213\">Ben-Or et al.</a> if possible. This in particular means "
+"moving libaboss to bignums (gcry_mpi)."
msgstr ""
#: template/gsoc.html.j2:589
@@ -1685,11 +2373,10 @@ msgstr ""
#: template/gsoc.html.j2:602
msgid ""
"Python 2.7 is reaching its end-of-life, and we want to get rid of the "
-"dependency on Python. The existing gnunet-qr tool is a rather simple "
-"wrapper around python-zbar, which itself wraps libzbar. The goal of this "
-"project is to directly use libzbar to scan QR codes for GNUnet / the GNU "
-"Name System (see also <a "
-"href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
+"dependency on Python. The existing gnunet-qr tool is a rather simple wrapper "
+"around python-zbar, which itself wraps libzbar. The goal of this project is "
+"to directly use libzbar to scan QR codes for GNUnet / the GNU Name System "
+"(see also <a href=\"https://bugs.gnunet.org/view.php?id=5562\";>#5562</a>)."
msgstr ""
#: template/gsoc.html.j2:612
@@ -1714,11 +2401,11 @@ msgstr ""
#: template/gsoc.html.j2:642
msgid ""
-"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a "
-"yet to be determined framework such as Angular2. This includes the design"
-" and implementation of not yet existing <a "
-"href=\"http://jsonapi.org/\";>REST APIs</a> that expose the <a "
-"href=\"https://docs.gnunet.org/doxygen/modules.html\";>GNUnet API</a>."
+"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a yet "
+"to be determined framework such as Angular2. This includes the design and "
+"implementation of not yet existing <a href=\"http://jsonapi.org/\";>REST "
+"APIs</a> that expose the <a href=\"https://docs.gnunet.org/doxygen/modules.";
+"html\">GNUnet API</a>."
msgstr ""
#: template/gsoc.html.j2:657
@@ -1727,8 +2414,7 @@ msgstr ""
#: template/gsoc.html.j2:667
msgid ""
-"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet "
-"WebUI</a>"
+"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet WebUI</a>"
msgstr ""
#: template/index.html.j2:8
@@ -1750,25 +2436,24 @@ msgstr ""
#: template/index.html.j2:49
msgid ""
"The conventional Internet is currently like a system of roads with deep "
-"potholes and highwaymen all over the place. Even if you still can use the"
-" roads (e.g. send emails, or browse websites) your vehicle might get "
+"potholes and highwaymen all over the place. Even if you still can use the "
+"roads (e.g. send emails, or browse websites) your vehicle might get "
"hijacked, damaged, or long arms might reach into its back and steal your "
-"items (data) to use it against you and sell it to others - while you "
-"can't even notice the thievery nor accuse and hold the scroungers "
-"accountable. <!-- Proposal from Fabian Gerlach: The conventional Internet"
-" is currently like a system of roads with deep potholes and surveillance "
-"cameras all over the place. Even if you still can use the roads (e.g. "
-"send emails, or browse websites) your vehicle might gets damaged. And the"
-" surveillance cameras will create a movement profile about your life: "
-"They recognize your car license plate, track you everywhere you drive, "
-"and save this information in a central data base. --> The Internet was "
-"not designed with security in mind: protecting against address forgery, "
-"routers learning metadata, or choosing trustworthy third parties is "
-"nontrivial and sometimes impossible. <!-- Proposal from Fabian Gerlach: "
-"The Internet is not designed with security in mind: The network generally"
-" learns too much about users; it has insecure defaults and high "
-"complexity; and it is centralized. That makes it very vulnerable for "
-"multiple attacks massively threatening our freedom. -->"
+"items (data) to use it against you and sell it to others - while you can'"
+"t even notice the thievery nor accuse and hold the scroungers accountable. "
+"<!-- Proposal from Fabian Gerlach: The conventional Internet is currently "
+"like a system of roads with deep potholes and surveillance cameras all over "
+"the place. Even if you still can use the roads (e.g. send emails, or browse "
+"websites) your vehicle might gets damaged. And the surveillance cameras will "
+"create a movement profile about your life: They recognize your car license "
+"plate, track you everywhere you drive, and save this information in a "
+"central data base. --> The Internet was not designed with security in mind: "
+"protecting against address forgery, routers learning metadata, or choosing "
+"trustworthy third parties is nontrivial and sometimes impossible. <!-- "
+"Proposal from Fabian Gerlach: The Internet is not designed with security in "
+"mind: The network generally learns too much about users; it has insecure "
+"defaults and high complexity; and it is centralized. That makes it very "
+"vulnerable for multiple attacks massively threatening our freedom. -->"
msgstr ""
#: template/index.html.j2:94
@@ -1778,10 +2463,10 @@ msgstr ""
#: template/index.html.j2:96
msgid ""
"GNUnet is a network protocol stack for building secure, distributed, and "
-"privacy-preserving applications.<br/> With strong roots in <a "
-"class=\"link\" href=\"https://bib.gnunet.org\";>academic research</a>, our"
-" goal is to replace the <a class=\"link\" href=\"https://secushare.org";
-"/broken-internet\">old insecure Internet</a> protocol stack."
+"privacy-preserving applications.<br/> With strong roots in <a class=\"link\" "
+"href=\"https://bib.gnunet.org\";>academic research</a>, our goal is to "
+"replace the <a class=\"link\" href=\"https://secushare.org/broken-internet";
+"\">old insecure Internet</a> protocol stack."
msgstr ""
#: template/index.html.j2:119
@@ -1792,10 +2477,9 @@ msgstr ""
msgid ""
"Your metadata is just as revealing as the actual content; and it gets "
"exposed on the Internet.<br> Even though transport encryption is "
-"increasingly being deployed on the Internet, it still reveals data that "
-"can threaten democracy: the identities of senders and receivers, the "
-"times, frequency and the volume of communication are all still "
-"revealed.<br>"
+"increasingly being deployed on the Internet, it still reveals data that can "
+"threaten democracy: the identities of senders and receivers, the times, "
+"frequency and the volume of communication are all still revealed.<br>"
msgstr ""
#: template/index.html.j2:150
@@ -1804,15 +2488,13 @@ msgstr ""
#: template/index.html.j2:152
msgid ""
-"It provides <a class=\"link\" "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";> improving "
-"addressing, routing, naming and content distribution</a> in a technically"
-" robust manner - as opposed to ad-hoc designs in place today. <!-- "
-"Proposal from fabian gerlach: GNUnet is built <a "
-"href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by "
-"design\"</a> and \"distributed by design\". This improves addressing, "
-"routing, naming and content distribution in a technically robust manner. "
-"-->"
+"It provides <a class=\"link\" href=\"https://www.w3.org/2014/strint/";
+"papers/65.pdf\"> improving addressing, routing, naming and content "
+"distribution</a> in a technically robust manner - as opposed to ad-hoc "
+"designs in place today. <!-- Proposal from fabian gerlach: GNUnet is built "
+"<a href=\"https://www.w3.org/2014/strint/papers/65.pdf\";>\"privacy by design"
+"\"</a> and \"distributed by design\". This improves addressing, routing, "
+"naming and content distribution in a technically robust manner. -->"
msgstr ""
#: template/index.html.j2:177
@@ -1822,9 +2504,9 @@ msgstr ""
#: template/index.html.j2:179
msgid ""
"Today, monitoring increasingly centralized infrastructure, proprietary "
-"implementations, traffic shapers and firewalls restrict all of the <a "
-"class=\"link\" href=\"https://www.gnu.org/philosophy/free-";
-"sw.html\">essential freedoms</a> to various degrees."
+"implementations, traffic shapers and firewalls restrict all of the <a class="
+"\"link\" href=\"https://www.gnu.org/philosophy/free-sw.html\";>essential "
+"freedoms</a> to various degrees."
msgstr ""
#: template/index.html.j2:203
@@ -1833,14 +2515,14 @@ msgstr ""
#: template/index.html.j2:205
msgid ""
-"GNUnet is a self-organizing network and it is <a class=\"link\" "
-"href=\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as"
-" in freedom. GNUnet puts you in control of your data. You determine which"
-" data to share with whom, and you're not pressured to accept "
-"compromises. It gives users freedoms to securely access information "
-"(\"run\" the network), to study all aspects of the network's "
-"operation (\"access the code\"), to distribute information (\"copy\"), as"
-" well as the freedom to deploy new applications (\"modify\")."
+"GNUnet is a self-organizing network and it is <a class=\"link\" href="
+"\"https://www.gnu.org/philosophy/free-sw.html\";>free software</a> as in "
+"freedom. GNUnet puts you in control of your data. You determine which data "
+"to share with whom, and you're not pressured to accept compromises. It "
+"gives users freedoms to securely access information (\"run\" the network), "
+"to study all aspects of the network's operation (\"access the code\"), "
+"to distribute information (\"copy\"), as well as the freedom to deploy new "
+"applications (\"modify\")."
msgstr ""
#: template/index.html.j2:229
@@ -1849,13 +2531,13 @@ msgstr ""
#: template/index.html.j2:232
msgid ""
-"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every "
-"other distributed or P2P project develops its own library stack, covering"
-" transports, stream muxing, discovery and others. This divides effort and"
-" multiplies bug count. --> Instead of sharing common components and tools"
-" for building P2P systems, every P2P project seems to re-invent the "
-"wheel. <!-- TODO: rework this sentence. --> This heightens the effort and"
-" increases the potential number of vulnerabilities."
+"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every other "
+"distributed or P2P project develops its own library stack, covering "
+"transports, stream muxing, discovery and others. This divides effort and "
+"multiplies bug count. --> Instead of sharing common components and tools for "
+"building P2P systems, every P2P project seems to re-invent the wheel. <!-- "
+"TODO: rework this sentence. --> This heightens the effort and increases the "
+"potential number of vulnerabilities."
msgstr ""
#: template/index.html.j2:264
@@ -1864,10 +2546,10 @@ msgstr ""
#: template/index.html.j2:266
msgid ""
-"It offers a metadata-preserving foundation for your application. It "
-"offers components for addressing, reliable encrypted channels with "
-"advanced routing and resource discovery and naming. Our work is based on "
-"continuous research spanning almost two decades."
+"It offers a metadata-preserving foundation for your application. It offers "
+"components for addressing, reliable encrypted channels with advanced routing "
+"and resource discovery and naming. Our work is based on continuous research "
+"spanning almost two decades."
msgstr ""
#: template/index.html.j2:286
@@ -2009,75 +2691,69 @@ msgstr ""
#: template/install.html.j2:12
msgid ""
-"Notice: GNUnet is still undergoing major development. It is largely "
-"<i>not yet ready</i> for usage beyond developers."
+"Notice: GNUnet is still undergoing major development. It is largely <i>not "
+"yet ready</i> for usage beyond developers."
msgstr ""
#: template/install.html.j2:18
msgid ""
-"<p>Please be aware that this project is still in an early alpha stage "
-"when it comes to running software – its not an easy task to rewrite"
-" the whole Internet! We are happy to get your <a "
-"href=\"engage.html\">helping hand</a> anytime! Further information is "
-"available in our <a href=\"https://docs.gnunet.org/#toc-Using-";
-"GNUnet-1\">handbook</a>. If you have any queries about the installation "
-"or the usage, please <a href=\"engage.html\">get in touch!</a></p>"
+"<p>Please be aware that this project is still in an early alpha stage when "
+"it comes to running software – its not an easy task to rewrite the "
+"whole Internet! We are happy to get your <a href=\"engage.html\">helping "
+"hand</a> anytime! Further information is available in our <a href=\"https://";
+"docs.gnunet.org/#toc-Using-GNUnet-1\">handbook</a>. If you have any queries "
+"about the installation or the usage, please <a href=\"engage.html\">get in "
+"touch!</a></p>"
msgstr ""
#: template/install.html.j2:30
msgid ""
"We recommend to use binary packages provided by the package manager "
-"integrated within your Operating System. GNUnet is reportedly available "
-"for at least: <ul> <li><a "
-"href=\"https://pkgs.alpinelinux.org/package/edge/testing/x86_64/gnunet\";>Alpine</a></li>"
-" <li><a "
-"href=\"https://www.archlinux.org/packages/community/x86_64/gnunet/\";>Arch</a></li>"
-" <li><a "
-"href=\"https://packages.debian.org/search?keywords=gnunet\";>Debian</a></li>"
-" <li><a "
-"href=\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora "
-"(Copr)</a></li> <li><a "
-"href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
-"href=\"https://github.com/Homebrew/homebrew-";
-"core/blob/master/Formula/gnunet.rb\">Homebrew</a></li> <li><a "
-"href=\"https://nixos.org/nixos/packages.html?attr=gnunet&channel=nixpkgs-";
-"unstable&query=gnunet\">NixOS</a></li> <li><a href=\"install-on-"
-"openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is available for your "
-"Operating System and it is missing, send us feedback so that we can add "
-"it to this list. Furthermore, if you are interested in packaging GNUnet "
-"for your Operating System, get in touch with us at gnunet-"
-"developers@gnu.org if you require help with this job. If you were using "
-"an Operating System with the Alpine package manager, GNUnet could be "
-"installed as simple as:"
+"integrated within your Operating System. GNUnet is reportedly available for "
+"at least: <ul> <li><a href=\"https://pkgs.alpinelinux.org/package/edge/";
+"testing/x86_64/gnunet\">Alpine</a></li> <li><a href=\"https://www.archlinux.";
+"org/packages/community/x86_64/gnunet/\">Arch</a></li> <li><a href=\"https://";
+"packages.debian.org/search?keywords=gnunet\">Debian</a></li> <li><a href="
+"\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\";>Fedora (Copr)</a></"
+"li> <li><a href=\"https://guix.gnu.org/en/packages/G/\";>Guix</a></li> <li><a "
+"href=\"https://github.com/Homebrew/homebrew-core/blob/master/Formula/gnunet.";
+"rb\">Homebrew</a></li> <li><a href=\"https://nixos.org/nixos/packages.html?";
+"attr=gnunet&channel=nixpkgs-unstable&query=gnunet\">NixOS</a></li> <li><a "
+"href=\"install-on-openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is "
+"available for your Operating System and it is missing, send us feedback so "
+"that we can add it to this list. Furthermore, if you are interested in "
+"packaging GNUnet for your Operating System, get in touch with us at gnunet-"
+"developers@gnu.org if you require help with this job. If you were using an "
+"Operating System with the Alpine package manager, GNUnet could be installed "
+"as simple as:"
msgstr ""
#: template/install.html.j2:61
msgid ""
-"Next we describe a generic way to install from source. If you are using "
-"one of the following Operating Systems these step-by-step guides might be"
-" useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href"
-"=\"install-on-debian9.html\">Debian 9</a>, <a href=\"install-on-"
-"macos.html\">Mac OS</a>, <a href=\"install-on-netbsd.html\">NetBSD</a>, "
-"<a href=\"install-on-ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not"
-" all of them might be totally up-to-date! Please <a "
-"href=\"engage.html\">ask us</a> if you get stuck."
+"Next we describe a generic way to install from source. If you are using one "
+"of the following Operating Systems these step-by-step guides might be "
+"useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href=\"install-on-"
+"debian9.html\">Debian 9</a>, <a href=\"install-on-macos.html\">Mac OS</a>, "
+"<a href=\"install-on-netbsd.html\">NetBSD</a>, <a href=\"install-on-"
+"ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not all of them might be "
+"totally up-to-date! Please <a href=\"engage.html\">ask us</a> if you get "
+"stuck."
msgstr ""
#: template/install.html.j2:75
msgid ""
-"First, install the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>required "
-"dependencies</a> of GNUnet. There are base requirements and optional "
-"requirements."
+"First, install the <a href=\"https://git.gnunet.org/gnunet.git/tree/README";
+"\">required dependencies</a> of GNUnet. There are base requirements and "
+"optional requirements."
msgstr ""
#: template/install.html.j2:81
msgid ""
"Now, you need to decide if you want to install GNUnet from the release "
"tarball or from git. If you want to use GNUnet and there is no binary "
-"package available for your OS, you should stick with the release tarball."
-" If you want to develop using the most recent build, you should go with "
-"the <a href=\"https://git.gnunet.org/\";>git repository</a>."
+"package available for your OS, you should stick with the release tarball. If "
+"you want to develop using the most recent build, you should go with the <a "
+"href=\"https://git.gnunet.org/\";>git repository</a>."
msgstr ""
#: template/install.html.j2:98
@@ -2086,8 +2762,8 @@ msgstr ""
#: template/install.html.j2:106
msgid ""
-"Before building GNUnet, make sure that you setup the required groups and "
-"add your user to the group <code>gnunet</code>:"
+"Before building GNUnet, make sure that you setup the required groups and add "
+"your user to the group <code>gnunet</code>:"
msgstr ""
#: template/install.html.j2:117
@@ -2096,9 +2772,8 @@ msgstr ""
#: template/install.html.j2:128
msgid ""
-"You can find more configuration flags in the <a "
-"href=\"https://git.gnunet.org/gnunet.git/tree/README\";>README</a>.<br> "
-"Install GNUnet with:"
+"You can find more configuration flags in the <a href=\"https://git.gnunet.";
+"org/gnunet.git/tree/README\">README</a>.<br> Install GNUnet with:"
msgstr ""
#: template/install.html.j2:138
@@ -2108,9 +2783,8 @@ msgstr ""
#: template/install.html.j2:146
msgid ""
"Check the <a href=\"https://docs.gnunet.org/handbook/gnunet.html#Minimal-";
-"configuration\">handbook</a> for detailed documentation. For a more "
-"hands-on experience, <a href=\"https://gnunet.org/en/use.html\";>continue "
-"here</a>."
+"configuration\">handbook</a> for detailed documentation. For a more hands-on "
+"experience, <a href=\"https://gnunet.org/en/use.html\";>continue here</a>."
msgstr ""
#: template/livingstandards.html.j2:11
diff --git a/news/2013-11-15-special-use-gns.html.j2
b/news/2013-11-15-special-use-gns.html.j2
new file mode 100644
index 0000000..329e74d
--- /dev/null
+++ b/news/2013-11-15-special-use-gns.html.j2
@@ -0,0 +1,14 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+ <h1>Special-Use Domain Names of Peer-to-Peer Name Systems</h1>
+<p>
+ <b>This is an imported news item from the old Drupal GNUnet homepage.</b>
+</p>
+<p>
+We just submitted our draft for
+<a
href="https://web.archive.org/web/20140901155643/https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/";>Special-Use
Domain Names of Peer-to-Peer Name Systems</a> to IETF.
+The intention is to reserve the TLDs ".exit", ".i2p", ".gnu",
+".onion" and ".zkey" for use by the GNUnet, I2P and Tor peer-to-peer overlay
+networks.
+</p>
+{% endblock body_content %}
diff --git a/template/faq.html.j2 b/template/faq.html.j2
index f23a9d7..7c395dc 100644
--- a/template/faq.html.j2
+++ b/template/faq.html.j2
@@ -3,63 +3,1012 @@
<div class="container-fluid">
<div class="container text-center">
<h1>FAQs<h1>
- <h2><i>This page is a work-in-progress</i></h2>
- </div>
</div>
+</div>
<div class="container">
- <article>
- <section>
- <h3>{{ _("Is GNUnet ready for use on production systems?") }}</h3>
- <p>
- {% trans %}
- A: GNUnet is still undergoing major development. It is largely not yet
ready
- for usage beyond developers. Your mileage will vary depending on the
- functionality you use, but you will always likely run into issues with
- our current low-level transport system. We are currently in the process of
- rewriting it (Project "Transport Next Generation [TNG]")
- {% endtrans %}
- </p>
- </section>
- <section>
- <h3>{{ _("Is GNUnet build using distributed ledger technologies?")
}}</h3>
- <p>
- {% trans %}
- A: No. GNUnet is a new network protocol stack for building secure,
- distributed, and privacy-preserving applications.
- While a ledger could be built using GNUnet, we currently have no plans in
- doing so.
- {% endtrans %}
- </p>
- </section>
- <section>
- <h3>{{ _("I receive many "WARNING Calculated flow delay for X at Y
for Z". Should I worry?") }}</h3>
- <p>
- {% trans %}
- A: Right now, this is expected and a known cause for high
- latency in GNUnet. We have started a major rewrite to address
- this and other problems, but until the Transport Next
- Generation (TNG) is ready, these warnings are expected.
- {% endtrans %}
- </p>
- </section>
- <section>
- <h3>{{ _("Is there a graphical user interface?") }}</h3>
- <p>
- {% trans %}
- A: gnunet-gtk is a separate download. The package
- contains various GTK+ based graphical interfaces, including a
- graphical tool for configuration.
- {% endtrans %}
- </p>
- </section>
- </article>
-<!--
-<h2>{{ ("Q?") }}</h2>
-
-<h2>{{ ("Q?") }}</h2>
-
-<h2>{{ ("Q?") }}</h2>
--->
+ <div class="row">
+ <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu
for better orientation -->
+ <nav class="nav subnav position-fixed flex-column border-right"
style="position:fixed">
+ <a class="nav-link" href="#general">{{ _("General") }}</a>
+ <a class="nav-link" href="#features">{{ _("Features") }}</a>
+ <a class="nav-link" href="#gns">GNU Name System</a>
+ <a class="nav-link" href="#errors">{{ _("Error messages") }}</a>
+ <a class="nav-link" href="#fs">{{ _("File-sharing") }}</a>
+ <a class="nav-link" href="#contrib">{{ _("Contributing") }}</a>
+ </nav>
+ </div>
+
+ <div class="col">
+ <article>
+ <h2><a name="general" class="subnav-anchor"></a>{{ _("General") }}</h2>
+ General questions about the project.
+ <section>
+ <h3>{{ _("What do I do if my question is not answered here?") }}</h3>
+ <p>
+ {% trans %}
+ A: There are many other sources of information. You can read
additional
+ documentation or ask the question on the help-gnunet@gnu.org mailing
list or
+ the #gnunet IRC on irc.freenode.net.
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("When are you going to release the next version?") }}</h3>
+ <p>
+ {% trans %}
+ A: The general answer is, when it is ready. A better answer may be:
earlier
+ if you contribute (test, debug, code, document). Every release will
be
+ anounced on the info-gnunet@gnu.org mailing list and on
+ <a href="https://planet.gnu.org";>planet GNU</a>. You can subscribe
to the
+ mailing list or the RSS feed of this site to automatically receive a
+ notification.
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("Is the code free?") }}</h3>
+ <p>
+ {% trans %}
+ A: GNUnet is free software, available under the
+ <a href="https://www.gnu.org/licenses/agpl-3.0.en.html";>GNU Affero
Public License (AGPL)</a>.
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("Are there any known bugs?") }}</h3>
+ <p>
+ {% trans %}
+ A: We track the list of currently known bugs in the
+ <a href="https://bugs.gnunet.org/";>Mantis system</a>.
+
+ Some bugs are occasionally reported directly to developers or the
developer
+ mailing list. This is discouraged since developers often do not have
the time
+ to feed these bugs back into the Mantis database. Please report bugs
directly
+ to the bug tracking system. If you believe a bug is sensitive, you
can set its
+ view status to private (this should be the exception).
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("Is there a graphical user interface?") }}</h3>
+ <p>
+ {% trans %}
+ A: gnunet-gtk is a separate download. The package
+ contains various GTK+ based graphical interfaces, including a
+ graphical tool for configuration.
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("Why does gnunet-service-nse create a high CPU load?")
}}</h3>
+ <p>
+ {% trans %}
+ A: The gnunet-service-nse process will initially compute a so-called
+ "proof-of-work" which is used to convince the network that
your
+ peer is real (or, rather, make it expensive for an adversary to
mount a Sybil
+ attack on the network size estimator). The calculation is expected
to take a
+ few days, depending on how fast your CPU is. If the CPU load is
creating a
+ problem for you, you can set the value "WORKDELAY" in the
+ "nse" section of
+ your configuration file to a higher value. The default is "5
ms".
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("How does GNUnet compare to Tor?") }}</h3>
+ <p>
+ {% trans %}
+ A: Tor focuses on anonymous communication and censorship-resistance
for TCP
+ connections and, with the Tor Browser Bundle, for the Web in
particular.
+ GNUnet does not really have one focus; our theme is secure
decentralized
+ networking, but that is too broad to be called a focus.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("How does GNUnet compare to I2P?") }}</h3>
+ <p>
+ {% trans %}
+ A: Both GNUnet and I2P want to build a better, more secure, more
decentralized
+ Internet. However, on the technical side, there are almost no
overlaps.
+ <br><br>
+ I2P is written in Java, and has (asymmetric) tunnels using onion (or
garlic)
+ routing as the basis for various (anonymized) applications. I2P is
largely used
+ via a Web frontend.
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("Is GNUnet ready for use on production systems?") }}</h3>
+ <p>
+ {% trans %}
+ A: GNUnet is still undergoing major development. It is largely not
yet ready
+ for usage beyond developers. Your mileage will vary depending on the
+ functionality you use, but you will always likely run into issues
with
+ our current low-level transport system. We are currently in the
process of
+ rewriting it (Project "Transport Next Generation [TNG]")
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("Is GNUnet build using distributed ledger technologies?")
}}</h3>
+ <p>
+ {% trans %}
+ A: No. GNUnet is a new network protocol stack for building secure,
+ distributed, and privacy-preserving applications.
+ While a ledger could be built using GNUnet, we currently have no
plans in
+ doing so.
+ {% endtrans %}
+ </p>
+ </section>
+
+
+ <hr/>
+ <h2><a name="features" class="subnav-anchor"></a>{{ _("Features")
}}</h2>
+ <section>
+ <h3>{{ _("What can I do with GNUnet?") }}</h3>
+ <p>
+ {% trans %}
+ A: GNUnet is a peer-to-peer framework, by which we mostly mean that
it can do
+ more than just one thing. Naturally, the implementation and
documentation of
+ some of the features that exist are more advanced than others.
+ {% endtrans %}
+ </p>
+ <p>
+ {% trans %}
+ For users, GNUnet offers anonymous and non-anonymous file-sharing, a
fully
+ decentralized and censorship-resistant replacement for DNS and a
mechanism for
+ IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG).
+ {% endtrans %}
+ See also: <a href="{{ url_localized('applications.html')
}}">Applications</a>.
+
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Is it possible to surf the WWW anonymously with GNUnet?")
}}</h3>
+ <p>
+ {% trans %}
+ A: It is not possible use GNUnet for anonymous browsing at this
point.
+ We recommend that you use Tor for anonymous surfing.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Is it possible to access GNUnet via a browser as an
anonymous WWW?") }}</h3>
+ <p>
+ {% trans %}
+ A: There is currently no proxy (like fproxy in Freenet) for GNUnet
that would
+ make it accessible with a browser. It is possible to build such a
proxy and
+ all one needs to know is the protocol used between browser and proxy
and a
+ swift look at the GNUnet code for file-sharing.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Is there a graphical user interface?") }}</h3>
+ <p>
+ {% trans %}
+ A: There are actually a few graphical user interfaces for different
functions.
+ gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for
file-sharing.
+ There are a few other gnunet-XXX-gtk GUIs of lesser importance.
+ Note that in order to obtain the GUI, you need to install the
gnunet-gtk
+ package, which is a separate download.
+
+ gnunet-gtk is a meta GUI that integrates most of the other GUIs in
one window.
+ One exception is gnunet-setup, which must still be run separately at
this time
+ (as setup requires the peer to be stopped).
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("On top of which operating systems does GNUnet run?")
}}</h3>
+ <p>
+ {% trans %}
+ A: GNUnet is being developed and tested primarily under Debian
GNU/Linux.
+ Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu,
Arch,
+ FreeBSD and macOS.
+
+ We have reports of working versions on many other GNU/Linux
distributions;
+ in the past we had reports of working versions on NetBSD, OpenBSD
and Solaris.
+ However, not all of those reports are recent, so if you cannot get
GNUnet to
+ work on those systems please let us know.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <hr/>
+ <h2><a name="gns" class="subnav-anchor"></a>GNU Name System</h2>
+ <section>
+ <h3>{{ _("Who runs the GNS root zone?") }}</h3>
+ <p>
+ {% trans %}
+ A: Short answer: you. The long answer is the GNUnet will ship with a
+ default configuration of top-level domains. The governance of this
default
+ configuration is not yet established. In any case, the user will be
able
+ to modify this configuration at will. We expect normal users to have
+ no need to edit their own GNS zone(s) unless they host services
themselves.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Where is the per-user GNS database kept?") }}</h3>
+ <p>
+ {% trans %}
+ A: The short answer is that the database is kept at the user's
GNUnet peer.
+ Now, a user may run multiple GNUnet peers, in which case the
database could be
+ kept at each peer (however, we don't have code for convenient
replication).
+ Similarly, multiple GNUnet peers can share one instance of the
database ---
+ the "gnunet-service-namestore" can be accessed from remote
+ (via TCP). The actual data can be stored in a Postgres database, for
which
+ various replication options are again applicable. Ultimately, there
are many
+ options for how users can store (and secure) their GNS database.
+ {% endtrans %}
+ </p>
+ </section>
+
+
+ <section>
+ <h3>{{ _("What is the expected average size of a GNS namestore
database?") }}</h3>
+ <p>
+ {% trans %}
+ A: Pretty small. Based on our user study where we looked at browser
histories
+ and the number of domains visited, we expect that GNS databases will
only
+ grow to a few tens of thousands of entries, small enough to fit even
on mobile
+ devices.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Is GNS resistant to the attacks on DNS used by the US?")
}}</h3>
+ <p>
+ {% trans %}
+ A: We believe so, as there is no entity that any government could
force to
+ change the mapping for a name except for each individual user (and
then the
+ changes would only apply to the names that this user is the
authority for).
+ So if everyone used GNS, the only practical attack of a government
would be to
+ force the operator of a server to change the GNS records for his
server to
+ point elsewhere. However, if the owner of the private key for a zone
is
+ unavailable for enforcement, the respective zone cannot be changed
and any
+ other zone delegating to this zone will achieve proper resolution.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("How does GNS compare to other name systems") }}</h3>
+ <p>
+ {% trans %}
+ A: A scientific paper on this topic
+ <a href="https://grothoff.org/christian/ns2018.pdf";>has been
published
+ </a> and below is a table from the publication.
+ For detailed descriptions please refer to the paper.
+ {% endtrans %}
+ <table>
+ <thead>
+ <td></td>
+ <td>MitM manipulation</td>
+ <td>Zone walk</td>
+ <td>Client observation (network)</td>
+ <td>Client observation (operator)</td>
+ <td>Traffic amplification</td>
+ <td>Censorship/legal attacks</td>
+ <td>Ease of migration</td>
+ <thead>
+ <tbody>
+ <tr>
+ <td>DNS</td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td>+++</td>
+ </tr>
+ <tr>
+ <td>DNSSEC</td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td>+</td>
+ </tr>
+ <tr>
+ <td>DNSCurve</td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td>+</td>
+ </tr>
+ <tr>
+ <td>DoT/DoH</td>
+ <td><i class="fa fa-check"></i></td>
+ <td>n/a</td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td>+</td>
+ </tr>
+ <tr>
+ <td>Confid. DNS</td>
+ <td><i class="fa fa-times"></i></td>
+ <td>n/a</td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td>++</td>
+ </tr>
+ <tr>
+ <td>Namecoin</td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td>-</td>
+ </tr>
+ <tr>
+ <td>GNS</td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td>--</td>
+ </tr>
+ <tr>
+ <td>RAINS</td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td><i class="fa fa-check"></i></td>
+ <td><i class="fa fa-times"></i></td>
+ <td>--</td>
+ </tr>
+
+ </tbody>
+ </table>
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("What is the difference between GNS and CoDoNS?") }}</h3>
+ <p>
+ {% trans %}
+ A: CoDoNS decentralizes the DNS database (using a DHT) but preserves
the
+ authority structure of DNS. With CoDoNS, IANA/ICANN are still in
charge, and
+ there are still registrars that determine who owns a name.
+ <br><br>
+ With GNS, we decentralize the database and also decentralize the
+ responsibility for naming: each user runs his own personal root zone
and is
+ thus in complete control of the names he uses. GNS also has many
additional
+ features (to keep names short and enable migration) which don't even
make
+ sense in the context of CoDoNS.
+
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("What is the difference between GNS and SocialDNS?") }}</h3>
+ <p>
+ {% trans %}
+ A: Like GNS, SocialDNS allows each user to create DNS mappings.
However, with
+ SocialDNS the mappings are shared through the social network and
subjected to
+ ranking. As the social relationships evolve, names can thus change in
+ surprising ways.
+ <br><br>
+ With GNS, names are primarily shared via delegation, and thus
mappings will
+ only change if the user responsible for the name (the authority)
manually
+ changes the record.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("What is the difference between GNS and ODDNS?") }}</h3>
+ <p>
+ {% trans %}
+ A: ODDNS is primarily designed to bypass the DNS root zone and the
TLD
+ registries (such as those for ".com" and ".org"). Instead of using
those,
+ each user is expected to maintain a database of (second-level)
domains
+ (like "gnu.org") and the IP addresses of the respective name servers.
+ Resolution will fail if the target name servers change IPs.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("What is the difference between GNS and Handshake?") }}</h3>
+ <p>
+ {% trans %}
+ A: Handshake is a blockchain-based method for root zone governance.
+ Hence, it does not address the name resolution process itself but
+ delegates resolution into DNS after the initial TLD resolution.
+ Not taking sustainablility considerations into account, handshake
+ could be used as an additional supporting GNS root zone governance
+ model but we currently do not have such plans in mind.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("What is the difference between GNS and TrickleDNS?")
}}</h3>
+ <p>
+ {% trans %}
+ A: TrickleDNS pushes ("critical") DNS records between DNS
resolvers
+ of participating domains to provide "better availability, lower
query
+ resolution times, and faster update propagation". Thus
TrickleDNS is
+ focused on defeating attacks on the availability (and performance)
of record
+ propagation in DNS, for example via DDoS attacks on DNS root servers.
+ TrickleDNS is thus concerned with how to ensure distribution of
authoritative
+ records, and authority remains derived from the DNS hierarchy.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Does GNS require real-world introduction (secure PKEY
exchange) in the style of the PGP web of trust?") }}</h3>
+ <p>
+ {% trans %}
+ A: For security, it is well known that an initial trust path between
the two
+ parties must exist. However, for applications where this is not
required,
+ weaker mechanisms can be used. For example, we have implemented a
+ first-come-first-served (FCFS) authority which allows arbitrary
users to
+ register arbitrary names. The key of this authority is included with
every
+ GNUnet installation. Thus, any name registered with FCFS is in fact
global and
+ requires no further introduction. However, the security of these
names
+ depends entirely on the trustworthiness of the FCFS authority.
+ The authority can be queried under the ".pin" TLD.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("How can a legitimate domain owner tell other people to not
use his name in GNS?") }}</h3>
+ <p>
+ {% trans %}
+ A: Names have no owners in GNS, so there cannot be a
"legitimate"
+ domain owner. Any user can claim any name (as his preferred name or
+ "pseudonym") in his NICK record. Similarly, all other
users can
+ choose to ignore this preference and use a name of their choice (or
even
+ assign no name) for this user.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Did you consider the privacy implications of making your
personal GNS zone visible?") }}</h3>
+ <p>
+ {% trans %}
+ A: Each record in GNS has a flag "private". Records are
shared with
+ other users (via DHT or zone transfers) only if this flag is not set.
+ Thus, users have full control over what information about their
zones is made
+ public.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Are \"Legacy Host\" (LEHO) records not going to be
obsolete with IPv6?") }}</h3>
+ <p>
+ {% trans %}
+ A: The question presumes that (a) virtual hosting is only necessary
because of
+ IPv4 address scarcity, and (b) that LEHOs are only useful in the
context of
+ virtual hosting. However, LEHOs are also useful to help with X.509
certificate
+ validation (as they specify for which legacy hostname the
certificate should
+ be valid). Also, even with IPv6 fully deployed and
"infinite" IP
+ addresses being available, we're not sure that virtual hosting would
+ disappear. Finally, we don't want to have to wait for IPv6 to become
+ commonplace, GNS should work with today's networks.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Why does GNS not use a trust metric or consensus to
determine globally unique names?") }}</h3>
+ <p>
+ {% trans %}
+ A: Trust metrics have the fundamental problem that they have
thresholds.
+ As trust relationships evolve, mappings would change their meaning
as they
+ cross each others thresholds. We decided that the resulting
unpredictability
+ of the resolution process was not acceptable. Furthermore, trust and
consensus
+ might be easy to manipulate by adversaries.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("How do you handle compromised zone keys in GNS?") }}</h3>
+ <p>
+ {% trans %}
+ A: The owner of a private key can create a revocation message. This
one can
+ then be flooded throughout the overlay network, creating a copy at
all peers.
+ Before using a public key, peers check if that key has been revoked.
+ All names that involve delegation via a revoked zone will then fail
to
+ resolve. Peers always automatically check for the existence of a
revocation
+ message when resolving names.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Could the signing algorithm of GNS be upgraded in the
future?") }}</h3>
+ <p>
+ {% trans %}
+ A: Yes. In our efforts to standardize GNS, we have already modified
the protocol
+ to support alternative delegation records.
+ <br>
+ <br>
+ Naturally, deployed GNS implementations would have to be updated to
support
+ the new signature scheme. The new scheme can then be run in parallel
with
+ the existing system by using a new record type to indicate the use
of a
+ different cipher system.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("How can a GNS zone maintain several name servers, e.g. for
load balancing?") }}</h3>
+ <p>
+ {% trans %}
+ A: We don't expect this to be necessary, as GNS records are stored
(and
+ replicated) in the R5N DHT. Thus the authority will typically not be
contacted
+ whenever clients perform a lookup. Even if the authority goes
(temporarily)
+ off-line, the DHT will cache the records for some time. However,
should having
+ multiple servers for a zone be considered truly necessary, the owner
of the
+ zone can simply run multiple peers (and share the zone's key and
database
+ among them).
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Why do you believe it is worth giving up unique names for
censorship resistance?") }}</h3>
+ <p>
+ {% trans %}
+ A: The GNU Name system offers an alternative to DNS that is
censorship
+ resistant. As with any security mechanism, this comes at a cost
(names are not
+ globally unique). To draw a parallel, HTTPS connections use more
bandwidth and
+ have higher latency than HTTP connections. Depending on your
application,
+ HTTPS may not be worth the cost. However, for users that are
experiencing
+ censorship (or are concerned about it), giving up globally unique
names may
+ very well be worth the cost. After all, what is a
"globally" unique
+ name worth, if it does not resolve?
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Why do you say that DNS is 'centralized' and
'distributed'?") }}</h3>
+ <p>
+ {% trans %}
+ A: We say that DNS is 'centralized' because it has a central
component /
+ central point of failure --- the root zone and its management by
IANA/ICANN.
+ This centralization creates vulnerabilities. For example, the US
government
+ was able to reassign the management of the country-TLDs of
Afganistan and Iraq
+ during the wars at the beginning of the 21st century.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("How does GNS protect against layer-3 censorship?") }}</h3>
+ <p>
+ {% trans %}
+ A: GNS does not directly help with layer-3 censorship, but it does
help
+ indirectly in two ways:
+
+ <ol>
+ <li> Many websites today use virtual hosting, so blocking a
particular IP
+ address causes much more collateral damage than blocking a DNS
name.
+ It thus raises the cost of censorship.</li>
+ <li> Existing layer-3 circumvention solutions (such as Tor) would
benefit from
+ a censorship resistant naming system. Accessing Tor's
".onion"
+ namespace currently requires users to use unmemorable
cryptographic
+ identifiers. With nicer names, Tor and tor2web-like services
would be even
+ easier to use.
+ </ol>
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Does GNS work with search engines?") }}</h3>
+ <p>
+ {% trans %}
+ A: GNS creates no significant problems for search engines, as they
can use GNS
+ to perform name resolution as well as any normal user. Naturally,
while we
+ typically expect normal users to install custom software for name
resolution,
+ this is unlikely to work for search engines today. However, the
DNS2GNS
+ gateway allows search engines to use DNS to resolve GNS names, so
they can
+ still index GNS resources. However, as using DNS2GNS gateways breaks
the
+ cryptographic chain of trust, legacy search engines will obviously
not obtain
+ censorship-resistant names.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("How does GNS compare to the Unmanaged Internet
Architecture (UIA)?") }}</h3>
+ <p>
+ {% trans %}
+ A: UIA and GNS both share the same basic naming model, which actually
+ originated with Rivest's SDSI. However, UIA is not concerned about
integration
+ with legacy applications and instead focuses on universal
connectivity between
+ a user's many machines. In contrast, GNS was designed to
interoperate with DNS
+ as much as possible, and to also work as much as possible with the
existing
+ Web infrastructure. UIA is not at all concerned about legacy systems
(clean
+ slate).
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("Doesn't GNS increase the trusted-computing base compared
to DNS(SEC)?") }}</h3>
+ <p>
+ {% trans %}
+ A: First of all, in GNS you can explicitly see the trust chain, so
you know if
+ a name you are resolving belongs to a friend, or a
friend-of-a-friend, and can
+ thus decide how much you trust the result. Naturally, the
trusted-computing
+ base (TCB) can become arbitrarily large this way --- however, given
the name
+ length restriction, for an individual name it is always less than
about 128
+ entities.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("How does GNS handle SRV/TLSA records where service and
protocol are part of the domain name?") }}</h3>
+ <p>
+ {% trans %}
+ A: When GNS splits a domain name into labels for resolution, it
detects the
+ "_Service._Proto" syntax, converts "Service" to
the
+ corresponding port number and "Proto" to the corresponding
protocol
+ number. The rest of the name is resolved as usual. Then, when the
result is
+ presented, GNS looks for the GNS-specific "BOX" record
type.
+ A BOX record is a record that contains another record (such as SRV
or TLSA
+ records) and adds a service and protocol number (and the original
boxed record
+ type) to it.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <hr/>
+ <h2><a name="errors" class="subnav-anchor"></a>{{ _("Error messages")
}}</h2>
+ <section>
+ <h3>{{ _("I receive many "WARNING Calculated flow delay for X
at Y for Z". Should I worry?") }}</h3>
+ <p>
+ {% trans %}
+ A: Right now, this is expected and a known cause for high
+ latency in GNUnet. We have started a major rewrite to address
+ this and other problems, but until the Transport Next
+ Generation (TNG) is ready, these warnings are expected.
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("Error opening `/dev/net/tun': No such file or directory?")
}}</h3>
+ <p>
+ {% trans %}
+ A: If you get this error message, the solution is simple. Issue the
following
+ commands (as root) to create the required device file
+ {% endtrans %}
+ <code class="block">
+ # mkdir /dev/net<br>
+ # mknod /dev/net/tun c 10 200<br>
+ </code>
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("'iptables: No chain/target/match by that name.' (when
running gnunet-service-dns)?") }}</h3>
+ <p>
+ {% trans %}
+ A: For GNUnet DNS, your iptables needs to have "owner"
match
+ support.
+
+ This is accomplished by having the correct kernel options. Check if
your
+ kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or 'm'
(and the
+ module is loaded).
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("'Timeout was reached' when running PT on Fedora (and
possibly others)?") }}</h3>
+ <p>
+ {% trans %}
+ A: If you get an error stating that the VPN timeout was reached,
check if your
+ firewall is enabled and blocking the connections.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("I'm getting an 'error while loading shared libraries:
libgnunetXXX.so.X'") }}</h3>
+ <p>
+ {% trans %}
+ A: This error usually occurs when your linker fails to locate one of
GNUnet's
+ libraries. This can have two causes. First, it is theoretically
possible that
+ the library is not installed on your system; however, if you
compiled GNUnet
+ the normal way and/or used a binary package, that is highly
unlikely. The more
+ common cause is that you installed GNUnet to a directory that your
linker
+ does not search. There are several ways to fix this that are
described below.
+
+ If you are 'root' and you installed to a system folder (such as
/usr/local),
+ you want to add the libraries to the system-wide search path. This
is done by
+ adding a line "/usr/local/lib/" to /etc/ld.so.conf and running
"ldconfig".
+ If you installed GNUnet to /opt or any other similar path, you
obviously have
+ to change "/usr/local" accordingly.
+
+ If you do not have 'root' rights or if you installed GNUnet to say
+ "/home/$USER/", then you can explicitly tell your linker to search a
+ particular directory for libraries using the "LD_LIBRARY_PATH"
environment
+ variable. For example, if you configured GNUnet using a prefix of
+ "$HOME/gnunet/" you want to run:
+ {% endtrans %}
+ </p>
+ <code>
+ $ export LD_LIBRARY_PATH=$HOME/gnunet/lib:$LD_LIBRARY_PATH<br>
+ $ export PATH=$HOME/gnunet/bin:$PATH
+ </code>
+ </p>
+ {% trans %}
+ to ensure GNUnet's binaries and libraries are found. In order to
avoid having to do so each time, you can add the above lines (without the "$")
to your .bashrc or .profile file. You will have to logout and login again to
have this new profile be applied to all shells (including your desktop
environment).
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("What error messages can be ignored?") }}</h3>
+ <p>
+ {% trans %}
+ A: Error messages flagged as "DEBUG" should be disabled in binaries
+ built for end-users and can always be ignored.
+
+ Error messages flagged as "INFO" always refer to harmless events that
+ require no action. For example, GNUnet may use an INFO message to
+ indicate that it is currently performing an expensive operation that
+ will take some time. GNUnet will also use INFO messages to display
+ information about important configuration values.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <hr/>
+ <h2><a name="fs" class="subnav-anchor"></a>{{ _("File-sharing")}}</h2>
+ <section>
+ <h3>{{ _("How does GNUnet compare to other file-sharing
applications?") }}</h3>
+ <p>
+ {% trans %}
+ A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and
most
+ other P2P networks, GNUnet was designed with security in mind as the
+ highest priority. We intend on producing a network with comprehensive
+ security features. Many other P2P networks are open to a wide variety
+ of attacks, and users have little privacy. GNUnet is also Free
+ Software and thus the source code is available, so you do not have to
+ worry about being spied upon by the software. The following table
+ summarises the main differences between GNUnet and other systems.
+ The information is accurate to the best of our knowledge.
+ The comparison is difficult since there are sometimes differences
+ between various implementations of (almost) the same protocol.
+ In general, we pick a free implementation as the reference
+ implementation since it is possible to inspect the free code. Also,
+ all of these systems are changing over time and thus the data below
+ may not be up-to-date. If you find any flaws, please let us know.
+ Finally, the table is not saying terribly much (it is hard to compare
+ these systems this briefly), so if you want the real differences,
read
+ the research papers (and probably the code).
+ {% endtrans %}
+ </p>
+ <table width="90%" border="0" cellpadding="0"
cellspacing="0"><tbody><tr><th >Network</th>
+ <th ><a>GNUnet FS</a></th>
+ <th ><a>OneSwarm</th>
+ <th ><a>Napster</th>
+ <th ><a>Direct Connect</th>
+ <th ><a>FastTrack</th>
+ <th ><a>eDonkey</th>
+ <th ><a>Gnutella</th>
+ <th ><a>Freenet</th>
+ </tr><tr><th >Distributed Queries</th>
+ <td >yes</td>
+ <td >yes</td>
+ <td >no</td>
+ <td >hubs</td>
+ <td >super-peers</td>
+ <td >DHT (eMule)</td>
+ <td >yes</td>
+ <td >yes</td>
+ </tr><tr><th >Multisource Download</th>
+ <td >yes</td>
+ <td >yes</td>
+ <td >no</td>
+ <td >no</td>
+ <td >yes</td>
+ <td >yes</td>
+ <td >yes</td>
+ <td >no</td>
+ </tr><tr><th >Economics</th>
+ <td >yes</td>
+ <td >yes</td>
+ <td >no</td>
+ <td >no</td>
+ <td >no</td>
+ <td >yes</td>
+ <td >no</td>
+ <td >no</td>
+ </tr><tr><th >Anonymity</th>
+ <td >yes</td>
+ <td >maybe</td>
+ <td >no</td>
+ <td >no</td>
+ <td >no</td>
+ <td >no</td>
+ <td >no</td>
+ <td >yes</td>
+ </tr><tr><th >Language</th>
+ <td >C</td>
+ <td >Java</td>
+ <td >often C</td>
+ <td >C++</td>
+ <td >C</td>
+ <td >C++</td>
+ <td >often C</td>
+ <td >Java</td>
+ </tr><tr><th >Transport Protocol</th>
+ <td >UDP, TCP, SMTP, HTTP</td>
+ <td >TCP</td>
+ <td >TCP</td>
+ <td >TCP?</td>
+ <td >UDP, TCP</td>
+ <td >UDP, TCP</td>
+ <td >TCP</td>
+ <td >TCP</td>
+ </tr><tr><th >Query Format (UI)</th>
+ <td >keywords / CHK</td>
+ <td >filename / SHA?</td>
+ <td >keywords</td>
+ <td >filename, THEX</td>
+ <td >filename, SHA</td>
+ <td >filename, MD4?</td>
+ <td >filename, SHA</td>
+ <td >secret key, CHK</td>
+ </tr><tr><th >Routing</th>
+ <td >dynamic (indirect, direct)</td>
+ <td >static (indirect, direct)</td>
+ <td >always direct</td>
+ <td >always direct</td>
+ <td >always direct</td>
+ <td >always direct</td>
+ <td >always direct</td>
+ <td >always indirect</td>
+ </tr><tr><th >License</th>
+ <td >GPL</td>
+ <td >GPL</td>
+ <td >GPL (knapster)</td>
+ <td >GPL (Valknut)</td>
+ <td >GPL (giFT)</td>
+ <td >GPL (eMule)</td>
+ <td >GPL (gtk-gnutella)</td>
+ <td >GPL</td>
+ </tr></tbody>
+ </table>
+ <p>
+ {% trans %}
+ Another important point of reference are the various anonymous
+ peer-to-peer networks.
+ Here, there are differences in terms of application domain and how
+ specifically anonymity is achieved.
+ Anonymous routing is a hard research topic, so for a superficial
+ comparisson like this one we focus on the latency.
+ Another important factor is the programming language.
+ Type-safe languages may offer certain security benefits; however,
this may come at the cost of significant increases in resource consumption
which in turn may reduce anonymity.
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("Are there any known attacks (on GNUnet's file-sharing
application)?") }}</h3>
+ <p>
+ {% trans %}
+ A: Generally, there is the possibility of a known plaintext attack on
+ keywords, but since the user has control over the keywords that are
+ associated with the content he inserts, the user can take advantage
of
+ the same techniques used to generate reasonable passwords to defend
+ against such an attack. In any event, we are not trying to hide
+ content; thus, unless the user is trying to insert information into
+ the network that can only be shared with a small group of people,
+ there is no real reason to try to obfuscate the content by choosing a
+ difficult keyword anyway.
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("What do you mean by anonymity?") }}</h3>
+ <p>
+ {% trans %}
+ A: Anonymity is the lack of distinction of an individual from a
+ (large) group. A central goal for anonymous file-sharing in GNUnet is
+ to make all users (peers) form a group and to make communications in
+ that group anonymous, that is, nobody (but the initiator) should be
+ able to tell which of the peers in the group originated the message.
+ In other words, it should be difficult to impossible for an adversary
+ to distinguish between the originating peer and all other peers.
+ {% endtrans %}
+ </p>
+ </section>
+ <section>
+ <h3>{{ _("What does my system do when participating in GNUnet file
sharing?") }}</h3>
+ <p>
+ {% trans %}
+ A: In GNUnet you set up a node (a peer). It is identified by an ID
(hash
+ of its public key) and has a number of addresses it is reachable by
+ (may have no addresses, for instance when it's behind a NAT).
+ You specify bandwidth limits (how much traffic GNUnet is allowed to
+ consume) and datastore quote (how large your on-disk block storage
is)
+ . Your node will then proceed to connect to other nodes, becoming
+ part of the network.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <hr/>
+ <h2><a name="contrib" class="subnav-anchor"></a>{{
_("Contributing")}}</h2>
+ <section>
+ <h3>{{ _("How can I help translate this webpage into other
languages?") }}</h3>
+ <p>
+ {% trans %}
+ A: First, you need to register an account with our weblate system.
+ Please send an e-mail with the desired target language to
+ translators@gnunet.org or ask for help on the #gnunet chat on
+ irc.freenode.net. Typically someone with sufficient permissions will
+ then grant you access. Naturally, any abuse will result in the loss
+ of permissions.
+ {% endtrans %}
+ </p>
+ </section>
+
+ <section>
+ <h3>{{ _("I have some great idea for a new feature, what should I
do?") }}</h3>
+ <p>
+ {% trans %}
+ A: Sadly, we have many more feature requests than we can possibly
+ implement. The best way to actually get a new feature implemented is
+ to do it yourself --- and to then send us a patch.
+ {% endtrans %}
+ </p>
+ </section>
+
+
+ </article>
+ </div> <!-- col -->
+ </div> <!-- row-->
+
+
+ <!--
+ <h2>{{ ("Q?") }}</h2>
+
+ <h2>{{ ("Q?") }}</h2>
+
+ <h2>{{ ("Q?") }}</h2>
+ -->
</div>
{% endblock body_content %}
diff --git a/www.yml b/www.yml
index 76aaec9..bde212f 100644
--- a/www.yml
+++ b/www.yml
@@ -9,10 +9,20 @@ siteconf:
rsslang:
langs_full: &langs
en: English
+ ar: عربي
fr: Français
it: Italiano
es: Español
de: Deutsch
+ zh_Hant: Chinese
+ hi: Hindi
+ ja: 日本語
+ ko: Korean
+ pt: Português
+ pt_BR: Português (Brazil)
+ ru: Ру́сский язы́к
+ sv: Svenska
+ tr: Türk
symlinks:
- file: frontpage.html
targets:
@@ -201,6 +211,9 @@ newsposts:
- page: 2013-12-28-archived-typos-pkeys.html
date: 2013-12-28
title: Typo-Protected Public Keys
+ - page: 2013-11-15-special-use-gns.html
+ date: 2013-11-15
+ title: Special-Use Domain Names of Peer-to-Peer Name Systems
- page: 2011-11-24-archived-vfork.html
date: 2011-11-24
title: vfork and the signal race
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [www] branch stable updated (eb0a5c7 -> a89a27b),
gnunet <=