aboutsummaryrefslogtreecommitdiff
path: root/locale/hi/LC_MESSAGES/messages.po
diff options
context:
space:
mode:
Diffstat (limited to 'locale/hi/LC_MESSAGES/messages.po')
-rw-r--r--locale/hi/LC_MESSAGES/messages.po3028
1 files changed, 3028 insertions, 0 deletions
diff --git a/locale/hi/LC_MESSAGES/messages.po b/locale/hi/LC_MESSAGES/messages.po
new file mode 100644
index 00000000..4e5af9f4
--- /dev/null
+++ b/locale/hi/LC_MESSAGES/messages.po
@@ -0,0 +1,3028 @@
1# Translations template for PROJECT.
2# Copyright (C) 2021 ORGANIZATION
3# This file is distributed under the same license as the PROJECT project.
4# FIRST AUTHOR <EMAIL@ADDRESS>, 2021.
5#
6msgid ""
7msgstr ""
8"Project-Id-Version: PROJECT VERSION\n"
9"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
10"POT-Creation-Date: 2021-05-12 14:14+0200\n"
11"PO-Revision-Date: 2021-03-09 18:35+0000\n"
12"Last-Translator: Jigisha Sharma <jigishas38@gmail.com>\n"
13"Language-Team: Hindi <http://weblate.taler.net/projects/gnunet/website/hi/>\n"
14"Language: hi\n"
15"MIME-Version: 1.0\n"
16"Content-Type: text/plain; charset=UTF-8\n"
17"Content-Transfer-Encoding: 8bit\n"
18"Plural-Forms: nplurals=2; plural=n > 1;\n"
19"X-Generator: Weblate 4.4.2\n"
20"Generated-By: Babel 2.9.0\n"
21
22#: common/base.j2:5 common/news.j2:5
23msgid "GNUnet"
24msgstr "कम्प्यूटिंग नेट"
25
26#: common/base.j2:6 common/news.j2:6
27msgid "GNU's framework for secure p2p networking"
28msgstr "कम्प्यूटिंग का ढाँचा सुरक्षित पीयर टू पीयर नेटवर्क के लिए"
29
30#: common/footer.j2.inc:7
31msgid "Contact"
32msgstr "सम्पर्क"
33
34#: common/footer.j2.inc:8
35msgid "GNUnet e.V."
36msgstr "कम्प्यूटिंग नेट ई.वी."
37
38#: common/footer.j2.inc:9 template/about.html.j2:6
39msgid "About GNUnet"
40msgstr "कप्यूटिंग नेट के बारे में"
41
42#: common/footer.j2.inc:14 common/navigation.j2.inc:64
43msgid "Bug Tracker"
44msgstr "बग ट्रैकेर"
45
46#: common/footer.j2.inc:19 template/copyright.html.j2:6
47msgid "Copyright Assignment"
48msgstr "कौपीराईट कार्य"
49
50#: common/footer.j2.inc:20 common/navigation.j2.inc:90
51#: template/developers.html.j2:24
52msgid "Bibliography"
53msgstr "ग्रन्थसूची"
54
55#: common/footer.j2.inc:31
56msgid "Source code of this site."
57msgstr "सूत्र संहिता इस स्थल का."
58
59#: common/footer.j2.inc:32
60msgid "Report issues with this website."
61msgstr "दर्ज करे समस्या वेबसाईट के."
62
63#: common/navigation.j2.inc:38
64msgid "About"
65msgstr "जानकारी"
66
67#: common/navigation.j2.inc:39 common/old-news.j2.inc:7
68#: template/news/index.html.j2:8
69msgid "News"
70msgstr "समाचार"
71
72#: common/navigation.j2.inc:40 template/index.html.j2:289
73msgid "Applications"
74msgstr "प्रार्थनापत्र"
75
76#: common/navigation.j2.inc:44
77msgid "Community"
78msgstr "समुदाय"
79
80#: common/navigation.j2.inc:47 template/index.html.j2:292
81msgid "Engage"
82msgstr "संलग्न"
83
84#: common/navigation.j2.inc:48
85msgid "GSoC Projects"
86msgstr "ग स ओ क परियोजनाओं"
87
88#: common/navigation.j2.inc:50
89msgid "Copyright for Contributors"
90msgstr "सर्वाधिकार योगदानकर्ताओं के लिए"
91
92#: common/navigation.j2.inc:51
93msgid "IRC Archive"
94msgstr "इ र च पुरालेख"
95
96#: common/navigation.j2.inc:58
97msgid "Development"
98msgstr "विकास"
99
100#: common/navigation.j2.inc:61
101msgid "System Architecture"
102msgstr "प्रणाली स्थापत्य"
103
104#: common/navigation.j2.inc:63 template/roadmap.html.j2:6
105msgid "Roadmap"
106msgstr "नक्शा"
107
108#: common/navigation.j2.inc:65 template/gnurl.html.j2:186
109msgid "Source Code"
110msgstr "सूत्र संहिता"
111
112#: common/navigation.j2.inc:66
113msgid "Source Code Documentation"
114msgstr "सूत्र संहिता प्रलेखन"
115
116#: common/navigation.j2.inc:67
117msgid "Continuous Integration"
118msgstr "लगातार एकीकरण"
119
120#: common/navigation.j2.inc:68
121msgid "Development Tutorial"
122msgstr "विकास उदाहरण"
123
124#: common/navigation.j2.inc:79
125msgid "Documentation"
126msgstr "प्रलेखन"
127
128#: common/navigation.j2.inc:82 template/install.html.j2:6
129msgid "Install"
130msgstr "स्थापित"
131
132#: common/navigation.j2.inc:83 template/install-on-openwrt.html.j2:76
133msgid "Use"
134msgstr "इस्तमाल"
135
136#: common/navigation.j2.inc:84
137msgid "Videos"
138msgstr "वीडियोज़"
139
140#: common/navigation.j2.inc:85 template/glossary.html.j2:6
141msgid "Glossary"
142msgstr "शब्दकोष"
143
144#: common/navigation.j2.inc:86
145msgid "Handbook"
146msgstr "पुस्तिका"
147
148#: common/navigation.j2.inc:88
149msgid "REST API"
150msgstr "र.ई.एस.टी ए .पी .इ"
151
152#: common/navigation.j2.inc:89 template/reclaim/index.html.j2:83
153msgid "FAQ"
154msgstr "अकसर पूछे जाने वाले सवाल"
155
156#: common/old-news.j2.inc:10 template/news/index.html.j2:11
157msgid "News posts about changes related to GNUnet such as releases and events"
158msgstr "समाचार पत्र बदलाव जी॰एन॰यू॰ नेट को लेकर घटना और प्रकाशित के उदाहरण"
159
160#: common/old-news.j2.inc:15 template/news/index.html.j2:16
161msgid "subscribe to our RSS feed"
162msgstr "अभिदाता बने हमारे रस्स वेब फ़ीड पर"
163
164#: common/old-news.j2.inc:34 template/news/index.html.j2:36
165msgid "read more"
166msgstr "और पड़े"
167
168#: template/about.html.j2:11
169msgid "What is GNUnet?"
170msgstr "क्या हे जी॰ एन॰यू॰ नेट?"
171
172#: template/about.html.j2:13
173msgid ""
174"GNUnet is an alternative network stack for building secure, decentralized "
175"and privacy-preserving distributed applications. Our goal is to replace the "
176"old insecure Internet protocol stack. Starting from an application for "
177"secure publication of files, it has grown to include all kinds of basic "
178"protocol components and applications towards the creation of a GNU internet."
179msgstr ""
180
181#: template/about.html.j2:23
182msgid ""
183"Today, the actual use and thus the social requirements for a global network "
184"differs widely from those goals of 1970. While the Internet remains suitable "
185"for military use, where the network equipment is operated by a command "
186"hierarchy and when necessary isolated from the rest of the world, the "
187"situation is less tenable for civil society."
188msgstr ""
189
190#: template/about.html.j2:32
191msgid ""
192"Due to fundamental Internet design choices, Internet traffic can be "
193"misdirected, intercepted, censored and manipulated by hostile routers on the "
194"network. And indeed, the modern Internet has evolved exactly to the point "
195"where, as Matthew Green put it, <a href=\"https://blog."
196"cryptographyengineering.com/2015/08/16/the-network-is-hostile/\">\"the "
197"network is hostile\"</a>."
198msgstr ""
199
200#: template/about.html.j2:41
201msgid ""
202"We believe liberal societies need a network architecture that uses the anti-"
203"authoritarian decentralized peer-to-peer paradigm and privacy-preserving "
204"cryptographic protocols. The goal of the GNUnet project is to provide a Free "
205"Software realization of this ideal."
206msgstr ""
207
208#: template/about.html.j2:49
209msgid ""
210"Specifically, GNUnet tries to follow the following design principles, in "
211"order of importance:"
212msgstr ""
213
214#: template/about.html.j2:56
215msgid ""
216"GNUnet must be implemented as <a href=\"https://www.gnu.org/philosophy/free-"
217"sw.html\">Free Software</a>."
218msgstr ""
219
220#: template/about.html.j2:60
221msgid ""
222"GNUnet must minimize the amount of personally identifiable information "
223"exposed."
224msgstr ""
225
226#: template/about.html.j2:61
227msgid ""
228"GNUnet must be fully distributed and resilient to external attacks and rogue "
229"participants."
230msgstr ""
231
232#: template/about.html.j2:62
233msgid ""
234"GNUnet must be self-organizing and not depend on administrators or "
235"centralized infrastructure."
236msgstr ""
237
238#: template/about.html.j2:63
239msgid ""
240"GNUnet must inform the user which other participants have to be trusted when "
241"establishing private communications."
242msgstr ""
243
244#: template/about.html.j2:64
245msgid "GNUnet must be open and permit new peers to join."
246msgstr ""
247
248#: template/about.html.j2:65
249msgid "GNUnet must support a diverse range of applications and devices."
250msgstr ""
251
252#: template/about.html.j2:66
253msgid "GNUnet must use compartmentalization to protect sensitive information."
254msgstr ""
255
256#: template/about.html.j2:67
257msgid "The GNUnet architecture must be resource efficient."
258msgstr ""
259
260#: template/about.html.j2:68
261msgid ""
262"GNUnet must provide incentives for peers to contribute more resources than "
263"they consume."
264msgstr ""
265
266#: template/about.html.j2:72
267msgid ""
268"To get know and learn more, please check our <a href=\"https://docs.gnunet."
269"org/handbook/gnunet.html\">handbook</a>, especially the <a href=\"https://"
270"docs.gnunet.org/handbook/gnunet.html#Key-Concepts\">chapter on \"Key Concepts"
271"\"</a>, explaining the fundamental concepts of GNUnet: <ul> <li><a href="
272"\"https://docs.gnunet.org/handbook/gnunet.html#Authentication"
273"\">Authentication</a></li> <li><a href=\"https://docs.gnunet.org/handbook/"
274"gnunet.html#Accounting-to-Encourage-Resource-Sharing\">Accounting to "
275"Encourage Resource Sharing</a></li> <li><a href=\"https://docs.gnunet.org/"
276"handbook/gnunet.html#Confidentiality\">Confidentiality</a></li> <li><a href="
277"\"https://docs.gnunet.org/handbook/gnunet.html#Anonymity\">Anonymity</a></"
278"li> <li><a href=\"https://docs.gnunet.org/handbook/gnunet.html#Deniability"
279"\">Deniability</a></li> <li><a href=\"https://docs.gnunet.org/handbook/"
280"gnunet.html#Peer-Identities\">Peer Identities</a></li> <li><a href=\"https://"
281"docs.gnunet.org/handbook/gnunet.html#Zones-in-the-GNU-Name-System-_0028GNS-"
282"Zones_0029\">Zones in the GNU Name System (GNS Zones)</a></li> <li><a href="
283"\"https://docs.gnunet.org/handbook/gnunet.html#Egos\">Egos</a></li> </ul>"
284msgstr ""
285
286#: template/about.html.j2:88
287msgid "More Resources"
288msgstr ""
289
290#: template/about.html.j2:90
291msgid ""
292"There are many more resources to learn about GNUnet besides the <a href="
293"\"https://docs.gnunet.org/handbook/gnunet.html\">handbook</a>, such as the "
294"<a href=\"https://bib.gnunet.org/\">bibliography</a> with papers covering "
295"the various layers, many <a href=\"https://gnunet.org/en/video.html"
296"\">videos</a> or a brief <a href=\"https://gnunet.org/en/glossary.html"
297"\">glossary</a>."
298msgstr ""
299
300#: template/about.html.j2:95
301msgid ""
302"You are most welcome to <a href=\"engage.html\">get engaged into the "
303"conversation</a>, <a href=\"install.html\">install GNUnet</a>, <a href=\"use."
304"html\">use it</a> and <a href=\"engage.html\">contribute and get engaged</a> "
305"in various ways."
306msgstr ""
307
308#: template/about.html.j2:100
309msgid ""
310"Please be aware that this project is (despite of it's age) still in an early "
311"alpha stage when it comes to software &#8211; its not an easy task to "
312"rewrite the whole Internet!"
313msgstr ""
314
315#: template/about.html.j2:105
316msgid "Current funding"
317msgstr ""
318
319#: template/about.html.j2:110
320msgid ""
321"We're receiving funding from NLnet's Next Generation Internet funding line "
322"to document and implement the GNU Name System protocol in a way suitable for "
323"the IETF standardization process."
324msgstr ""
325
326#: template/about.html.j2:123
327msgid ""
328"This project has received funding from the European Union’s Horizon 2020 "
329"research and innovation programme under the NGI_TRUST grant agreement no "
330"825618. The project aims to integrate re:claimID with the GNU Taler payment "
331"system in a pilot in order to demonstrate the practical feasibility and "
332"benefits of privacy enhancing technologies for users and commercial service "
333"providers. The project is called \"Decentralized Identities for Self-"
334"Sovereign End-users\" (DISSENS)."
335msgstr ""
336
337#: template/about.html.j2:141
338msgid ""
339"We are grateful for free hosting offered by the following organizations:"
340msgstr ""
341
342#: template/about.html.j2:150
343msgid "Past funding"
344msgstr ""
345
346#: template/about.html.j2:152
347msgid "We are grateful for past funding from the following organizations:"
348msgstr ""
349
350#: template/applications.html.j2:7
351msgid "Applications provided by GNUnet"
352msgstr ""
353
354#: template/applications.html.j2:13 template/gns.html.j2:7
355msgid "The GNU Name System"
356msgstr ""
357
358#: template/applications.html.j2:15
359msgid ""
360"The <a href=\"gns.html\">GNU Name System (GNS)</a> is a fully decentralized "
361"replacement for the Domain Name System (DNS). Instead of using a hierarchy, "
362"GNS uses a directed graph. Naming conventions are similar to DNS, but "
363"queries and replies are private even with respect to peers providing the "
364"answers. The integrity of records and privacy of look-ups are "
365"cryptographically secured. <!-- Too technical: GNS integrates a robust, "
366"efficient and instant key revocation mechanism. -->"
367msgstr ""
368
369#: template/applications.html.j2:38
370msgid "Self-sovereign, decentralized identity provider"
371msgstr ""
372
373#: template/applications.html.j2:41
374msgid ""
375"is a decentralized Identity Provider (IdP) service built in top of the GNU "
376"Name System. It allows users to securely share personal information with "
377"websites using standardized protocols (OpenID Connect)."
378msgstr ""
379
380#: template/applications.html.j2:57
381msgid "Filesharing (Alpha)"
382msgstr ""
383
384#: template/applications.html.j2:59
385msgid ""
386"GNUnet <a href=\"use.html#fs\">filesharing</a> is an application that aims "
387"to provide censorship-resistant, anonymous filesharing. The publisher is "
388"empowered to make a gradual choice between performance and anonymity."
389msgstr ""
390
391#: template/applications.html.j2:73
392msgid "Conversation (Pre-Alpha)"
393msgstr ""
394
395#: template/applications.html.j2:75
396msgid ""
397"GNUnet conversation is an application that provides secure voice "
398"communication in a fully decentralized way by employing GNUnet for routing "
399"and transport."
400msgstr ""
401
402#: template/applications.html.j2:91
403msgid "Applications utilizing GNUnet"
404msgstr ""
405
406#: template/applications.html.j2:97
407msgid "GNU Taler (Alpha)"
408msgstr ""
409
410#: template/applications.html.j2:99
411msgid ""
412"<a href=\"https://taler.net/\">GNU Taler</a> is a new privacy-preserving "
413"electronic payment system. Payments are cryptographically secured and are "
414"confirmed within milliseconds with extremely low transaction costs."
415msgstr ""
416
417#: template/applications.html.j2:118
418msgid "secushare"
419msgstr ""
420
421#: template/applications.html.j2:120
422msgid ""
423"<a href=\"https://secushare.org/\">secushare</a> is creating a decentralized "
424"social networking application on top of GNUnet. Using overlay multicast and "
425"the extensible PSYC protocol, notifications are distributed end-to-end "
426"encrypted to authorized recipients only."
427msgstr ""
428
429#: template/applications.html.j2:139
430msgid "pretty Easy privacy"
431msgstr ""
432
433#: template/applications.html.j2:141
434msgid ""
435"<a href=\"https://pep.foundation/\">pretty Easy privacy</a> (p&#8801;p) is "
436"creating a usable end-to-end encrypted e-mail solution using opportunistic "
437"key exchange. p&#8801;p will use GNUnet to protect metadata and exploit new "
438"cryptographic protocols to verify keys."
439msgstr ""
440
441#: template/applications.html.j2:160
442msgid "Cadet-GTK"
443msgstr ""
444
445#: template/applications.html.j2:162
446msgid ""
447"<a href=\"https://gitlab.com/gnunet-messenger/cadet-gtk\">Cadet-GTK</a> is a "
448"convenient but feature-rich graphical application providing messaging using "
449"the CADET subsystem. It is developed using GTK and libhandy for a convergent "
450"design."
451msgstr ""
452
453#: template/applications.html.j2:180
454msgid "groupchat"
455msgstr ""
456
457#: template/applications.html.j2:182
458msgid ""
459"<a href=\"https://git.gnunet.org/groupchat.git/\">groupchat</a> is a "
460"terminal user interface providing messaging using the CADET subsystem. It is "
461"developed using nim. Cadet-GTK and groupchat are planned to be compatible."
462msgstr ""
463
464#: template/architecture.html.j2:6
465#, fuzzy
466#| msgid "System Architecture"
467msgid "GNUnet System Architecture"
468msgstr "प्रणाली स्थापत्य"
469
470#: template/architecture.html.j2:20
471#, fuzzy
472#| msgid "Documentation"
473msgid "Foundations"
474msgstr "प्रलेखन"
475
476#: template/architecture.html.j2:22
477msgid ""
478"The foundations of GNUnet are a distributed hash table (R5N), an SCTP-like "
479"end-to-end encrypted messaging layer (CADET), a public key infrastructure "
480"(GNS) and a pluggable transport system (TRANSPORT).<br> Using public keys "
481"for addresses and self-organizing decentralized routing algorithms, these "
482"subsystems replace the traditional TCP/IP stack."
483msgstr ""
484
485#: template/architecture.html.j2:35
486msgid "Security"
487msgstr ""
488
489#: template/architecture.html.j2:38
490msgid ""
491"GNUnet is implemented using a multi-process architecture. Each subsystem "
492"runs as a separate process, providing fault isolation and enabling tight "
493"permissions to be granted to each subsystem. Naturally, the implementation "
494"is a <a href=\"https://www.gnu.org/\">GNU</a> package, and will always "
495"remain free software."
496msgstr ""
497
498#: template/architecture.html.j2:52
499#, fuzzy
500#| msgid "System Architecture"
501msgid "System architecture"
502msgstr "प्रणाली स्थापत्य"
503
504#: template/architecture.html.j2:58
505msgid "Subsystems"
506msgstr ""
507
508#: template/architecture.html.j2:67
509msgid "libgnunetutil"
510msgstr ""
511
512#: template/architecture.html.j2:73
513msgid "APIs"
514msgstr ""
515
516#: template/architecture.html.j2:86
517msgid "Legend"
518msgstr ""
519
520#: template/contact.html.j2:6
521#, fuzzy
522#| msgid "Continuous Integration"
523msgid "Contact information"
524msgstr "लगातार एकीकरण"
525
526#: template/contact.html.j2:11
527msgid "The mailing list"
528msgstr ""
529
530#: template/contact.html.j2:13
531msgid ""
532"An archived, public mailing list for GNUnet is hosted at <a href=\"https://"
533"lists.gnu.org/mailman/listinfo/gnunet-developers\">https://lists.gnu.org/"
534"mailman/listinfo/gnunet-developers</a>. You can send messages to the list at "
535"<a href=\"mailto:gnunet-developers@gnu.org\">gnunet-developers@gnu.org</a>."
536msgstr ""
537
538#: template/contact.html.j2:23
539msgid "The IRC channel"
540msgstr ""
541
542#: template/contact.html.j2:25
543msgid ""
544"<tt>#gnunet</tt> is reachable via <a href=\"https://freenode.net\">irc."
545"freenode.net</a>. There is also an <a href=\"https://view.matrix.org/room/!"
546"IjaAfLiruzjxFFzKAV:matrix.org/\">archive</a> available."
547msgstr ""
548
549#: template/contact.html.j2:38
550msgid "Contacting individuals"
551msgstr ""
552
553#: template/contact.html.j2:40
554msgid ""
555"GNUnet developers are generally reachable at either <tt>PSEUDONYM@gnunet."
556"org</tt> or <tt>LASTNAME@gnunet.org</tt>. Most of us support receiving GnuPG "
557"encrypted Emails. Urgent and sensitive security issues may be addressed to "
558"the GNU maintainers <tt>schanzen</tt> and <tt>grothoff</tt>."
559msgstr ""
560
561#: template/contact.html.j2:53
562msgid "Reporting bugs"
563msgstr ""
564
565#: template/contact.html.j2:55
566msgid ""
567"We track open feature requests and bugs for projects within GNUnet in our <a "
568"href=\"https://bugs.gnunet.org/\">Bug tracker</a>. You can also report bugs "
569"or feature requests to the <a href=\"https://lists.gnu.org/mailman/listinfo/"
570"bug-gnunet\">bug-gnunet</a> mailing list. The mailinglist requires no "
571"subscription."
572msgstr ""
573
574#: template/copyright.html.j2:11
575msgid ""
576"<p> Contributors to GNUnet with Git access must sign the <a href=\"/static/"
577"pdf/copyright.pdf\">copyright assignment</a> to ensure that the <a href="
578"\"https://git.gnunet.org/gnunet-ev.git/tree/gnunet_taler_agreement.tex"
579"\">GNUnet e.V. --- Taler Systems SA agreement on licensing and collaborative "
580"development</a> of the GNUnet and GNU Taler projects is satisfied. </p>"
581msgstr ""
582
583#: template/copyright.html.j2:22
584msgid ""
585"<p>The agreements ensure that the code will continue to be made available "
586"under free software licenses, but gives developers the freedom to move code "
587"between GNUnet and GNU Taler without worrying about licenses and to give the "
588"company the ability to dual-license (for example, so that we can distribute "
589"via App-stores that are hostile to free software).</p>"
590msgstr ""
591
592#: template/copyright.html.j2:30
593msgid ""
594"<p>Minor contributions (basically, anyone without Git access) do not require "
595"copyright assignment. Pseudonymous contributions are accepted, in this case "
596"simply sign the agreement with your pseudonym. Scanned copies are "
597"sufficient, but snail mail is preferred.</p>"
598msgstr ""
599
600#: template/developers.html.j2:5
601msgid "GNUnet for developers"
602msgstr ""
603
604#: template/developers.html.j2:13
605msgid "Repositories"
606msgstr ""
607
608#: template/developers.html.j2:16
609msgid ""
610"A list of our Git repositories can be found on our our <a href=\"https://git."
611"gnunet.org/\">Git Server</a>."
612msgstr ""
613
614#: template/developers.html.j2:27
615msgid ""
616"Technical papers can be found in our <a href=\"https://old.gnunet.org/"
617"bibliography\">bibliography</a>."
618msgstr ""
619
620#: template/developers.html.j2:34
621msgid "Discussion"
622msgstr ""
623
624#: template/developers.html.j2:37
625msgid ""
626"We have a mailing list for developer discussions. You can subscribe to or "
627"read the list archive at <a href=\"http://lists.gnu.org/mailman/listinfo/"
628"gnunet-developers\">http://lists.gnu.org/mailman/listinfo/gnunet-developers</"
629"a>."
630msgstr ""
631
632#: template/developers.html.j2:47
633msgid "Regression Testing"
634msgstr ""
635
636#: template/developers.html.j2:50
637msgid ""
638"We have <a href=\"https://buildbot.net/\">Buildbot</a> automation tests to "
639"detect regressions and check for portability at <a href=\"https://old.gnunet."
640"org/buildbot/gnunet/\">https://old.gnunet.org/buildbot/gnunet/</a>."
641msgstr ""
642
643#: template/developers.html.j2:59
644msgid "Code Coverage Analysis"
645msgstr ""
646
647#: template/developers.html.j2:62
648msgid ""
649"We use <a href=\"http://ltp.sourceforge.net/coverage/lcov.php\">LCOV</a> to "
650"analyze the code coverage of our tests, the results are available at <a href="
651"\"https://old.gnunet.org/coverage/\">https://old.gnunet.org/coverage/</a>."
652msgstr ""
653
654#: template/developers.html.j2:72
655msgid "Performance Analysis"
656msgstr ""
657
658#: template/developers.html.j2:75
659msgid ""
660"We use <a href=\"https://old.gnunet.org/gauger\">Gauger</a> for performance "
661"regression analysis of the exchange backend at <a href=\"https://old.gnunet."
662"org/gauger/\">https://old.gnunet.org/gauger/</a>."
663msgstr ""
664
665#: template/download.html.j2:7 template/gnurl.html.j2:209
666msgid "Downloads"
667msgstr ""
668
669#: template/download.html.j2:11
670msgid ""
671"Here you can download releases of our software and find links to the various "
672"versions."
673msgstr ""
674
675#: template/download.html.j2:17
676msgid "0.11.x series"
677msgstr ""
678
679#: template/download.html.j2:18
680msgid "tarball"
681msgstr ""
682
683#: template/download.html.j2:20
684msgid ""
685"The tarball of the latest version can be obtained from GNU FTP and its "
686"mirrors."
687msgstr ""
688
689#: template/download.html.j2:30
690msgid "git"
691msgstr ""
692
693#: template/download.html.j2:32
694msgid ""
695"You can fetch the git tag of version 0.11.x from our development server:"
696msgstr ""
697
698#: template/engage.html.j2:6
699#, fuzzy
700#| msgid "Engage"
701msgid "Engage!"
702msgstr "संलग्न"
703
704#: template/ev.html.j2:6
705msgid "Verein zur F&ouml;rderung von GNUnet e.V."
706msgstr ""
707
708#: template/ev.html.j2:11
709#, fuzzy
710#| msgid "About GNUnet"
711msgid "About GNUnet e.V."
712msgstr "कप्यूटिंग नेट के बारे में"
713
714#: template/ev.html.j2:13
715msgid ""
716"On December 27th 2013 a group of GNUnet hackers met at 30c3 to create the "
717"\"Verein zur F&ouml;rderung von GNUnet e.V.\", an association under German "
718"law to support GNUnet development. The Amtsgericht M&uuml;nchen registered "
719"the association on the 7th of March under VR 205287."
720msgstr ""
721
722#: template/ev.html.j2:22
723msgid ""
724"The association is officially dedicated to supporting research, development "
725"and education in the area of secure decentralized networking in general, and "
726"GNUnet specifically. This is the official website for the association."
727msgstr ""
728
729#: template/ev.html.j2:31
730msgid "Becoming a Member of GNUnet e.V."
731msgstr ""
732
733#: template/ev.html.j2:33
734msgid ""
735"GNUnet developers with git (write) access can become members to participate "
736"in the decision process and formally support GNUnet e.V. For this, all you "
737"have to do is update the <tt>members.txt</tt> file in the <a href=\"https://"
738"git.gnunet.org/gnunet-ev.git/\">gnunet-ev</a> repository. There are no "
739"membership dues; however, members are required to support GNUnet e.V. and in "
740"particularly contribute to the technical development within their means. For "
741"further details, we refer to the <a href=\"https://git.gnunet.org/gnunet-ev."
742"git/\">Satzung (Charter)</a> (currently only available in German, "
743"translations welcome)."
744msgstr ""
745
746#: template/ev.html.j2:52
747msgid "Governance"
748msgstr ""
749
750#: template/ev.html.j2:54
751msgid ""
752"You can find our charter, and the list of members under <a href=\"https://"
753"git.gnunet.org/gnunet-ev.git/tree/satzung.tex\">https://git.gnunet.org/"
754"gnunet-ev.git/tree/satzung.tex</a>. The current board consists of: "
755"<dl><dt>Vorsitz</dt> <dd><a href=\"https://schanzen.eu\">Martin "
756"Schanzenbach</a></dd> <dt>stellvertretender Vorsitz</dt> <dd>t3sserakt</dd> "
757"<dt>Kassenwart</dt> <dd>Florian Dold</dd> <dt>Beisitzer</dt> <dd> <a href="
758"\"https://grothoff.org/christian/\">Christian Grothoff</a>, ch3 </dd> </dl>"
759msgstr ""
760
761#: template/ev.html.j2:73
762msgid "Official Meeting Notes"
763msgstr ""
764
765#: template/ev.html.j2:86
766msgid "Support Us!"
767msgstr ""
768
769#: template/ev.html.j2:88
770msgid ""
771"Everybody is welcome to support us via donations. For financial "
772"contributions, Europeans are able to donate via SEPA. We hope to setup "
773"accounts in other major currency areas in the future. You can also donate "
774"via Bitcoin, routing details are given below. Please note that we are unable "
775"to provide receipts for your donations. If you are planning to donate a "
776"significant amount of money, please contact us first as it might be better "
777"to come to a custom arrangement. <dl><dt>BitCoin</dt> "
778"<dd>1GNUnetpWeR9Zs3vipdvVywo1GseeksjUh</dd> <dt>SEPA/IBAN</dt> "
779"<dd>DE67830654080004822650 (BIC/SWIFT: GENODEF1SLR)</dd> </dl>"
780msgstr ""
781
782#: template/faq.html.j2:12 template/faq.html.j2:23
783msgid "General"
784msgstr ""
785
786#: template/faq.html.j2:13 template/faq.html.j2:149 template/gns.html.j2:37
787msgid "Features"
788msgstr ""
789
790#: template/faq.html.j2:15 template/faq.html.j2:695
791msgid "Error messages"
792msgstr ""
793
794#: template/faq.html.j2:16 template/faq.html.j2:797
795msgid "File-sharing"
796msgstr ""
797
798#: template/faq.html.j2:17 template/faq.html.j2:973
799msgid "Contributing"
800msgstr ""
801
802#: template/faq.html.j2:26
803msgid "What do I do if my question is not answered here?"
804msgstr ""
805
806#: template/faq.html.j2:28
807msgid ""
808"A: There are many other sources of information. You can read additional "
809"documentation or ask the question on the help-gnunet@gnu.org mailing list or "
810"the #gnunet IRC on irc.freenode.net."
811msgstr ""
812
813#: template/faq.html.j2:36
814msgid "When are you going to release the next version?"
815msgstr ""
816
817#: template/faq.html.j2:38
818msgid ""
819"A: The general answer is, when it is ready. A better answer may be: earlier "
820"if you contribute (test, debug, code, document). Every release will be "
821"anounced on the info-gnunet@gnu.org mailing list and on <a href=\"https://"
822"planet.gnu.org\">planet GNU</a>. You can subscribe to the mailing list or "
823"the RSS feed of this site to automatically receive a notification."
824msgstr ""
825
826#: template/faq.html.j2:49
827msgid "Is the code free?"
828msgstr ""
829
830#: template/faq.html.j2:51
831msgid ""
832"A: GNUnet is free software, available under the <a href=\"https://www.gnu."
833"org/licenses/agpl-3.0.en.html\">GNU Affero Public License (AGPL)</a>."
834msgstr ""
835
836#: template/faq.html.j2:58
837msgid "Are there any known bugs?"
838msgstr ""
839
840#: template/faq.html.j2:60
841msgid ""
842"A: We track the list of currently known bugs in the <a href=\"https://bugs."
843"gnunet.org/\">Mantis system</a>. Some bugs are occasionally reported "
844"directly to developers or the developer mailing list. This is discouraged "
845"since developers often do not have the time to feed these bugs back into the "
846"Mantis database. Please report bugs directly to the bug tracking system. If "
847"you believe a bug is sensitive, you can set its view status to private (this "
848"should be the exception)."
849msgstr ""
850
851#: template/faq.html.j2:73 template/faq.html.j2:193
852msgid "Is there a graphical user interface?"
853msgstr ""
854
855#: template/faq.html.j2:75
856msgid ""
857"A: gnunet-gtk is a separate download. The package contains various GTK+ "
858"based graphical interfaces, including a graphical tool for configuration."
859msgstr ""
860
861#: template/faq.html.j2:83
862msgid "Why does gnunet-service-nse create a high CPU load?"
863msgstr ""
864
865#: template/faq.html.j2:85
866msgid ""
867"A: The gnunet-service-nse process will initially compute a so-called &quot;"
868"proof-of-work&quot; which is used to convince the network that your peer is "
869"real (or, rather, make it expensive for an adversary to mount a Sybil attack "
870"on the network size estimator). The calculation is expected to take a few "
871"days, depending on how fast your CPU is. If the CPU load is creating a "
872"problem for you, you can set the value &quot;WORKDELAY&quot; in the &quot;"
873"nse&quot; section of your configuration file to a higher value. The default "
874"is &quot;5 ms&quot;."
875msgstr ""
876
877#: template/faq.html.j2:99
878msgid "How does GNUnet compare to Tor?"
879msgstr ""
880
881#: template/faq.html.j2:101
882msgid ""
883"A: Tor focuses on anonymous communication and censorship-resistance for TCP "
884"connections and, with the Tor Browser Bundle, for the Web in particular. "
885"GNUnet does not really have one focus; our theme is secure decentralized "
886"networking, but that is too broad to be called a focus."
887msgstr ""
888
889#: template/faq.html.j2:111
890msgid "How does GNUnet compare to I2P?"
891msgstr ""
892
893#: template/faq.html.j2:113
894msgid ""
895"A: Both GNUnet and I2P want to build a better, more secure, more "
896"decentralized Internet. However, on the technical side, there are almost no "
897"overlaps. <br><br> I2P is written in Java, and has (asymmetric) tunnels "
898"using onion (or garlic) routing as the basis for various (anonymized) "
899"applications. I2P is largely used via a Web frontend."
900msgstr ""
901
902#: template/faq.html.j2:124
903msgid "Is GNUnet ready for use on production systems?"
904msgstr ""
905
906#: template/faq.html.j2:126
907msgid ""
908"A: GNUnet is still undergoing major development. It is largely not yet ready "
909"for usage beyond developers. Your mileage will vary depending on the "
910"functionality you use, but you will always likely run into issues with our "
911"current low-level transport system. We are currently in the process of "
912"rewriting it (Project &quot;Transport Next Generation [TNG]&quot;)"
913msgstr ""
914
915#: template/faq.html.j2:136
916msgid "Is GNUnet build using distributed ledger technologies?"
917msgstr ""
918
919#: template/faq.html.j2:138
920msgid ""
921"A: No. GNUnet is a new network protocol stack for building secure, "
922"distributed, and privacy-preserving applications. While a ledger could be "
923"built using GNUnet, we currently have no plans in doing so."
924msgstr ""
925
926#: template/faq.html.j2:151
927#, fuzzy
928#| msgid "What is GNUnet?"
929msgid "What can I do with GNUnet?"
930msgstr "क्या हे जी॰ एन॰यू॰ नेट?"
931
932#: template/faq.html.j2:153
933msgid ""
934"A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can "
935"do more than just one thing. Naturally, the implementation and documentation "
936"of some of the features that exist are more advanced than others."
937msgstr ""
938
939#: template/faq.html.j2:160
940msgid ""
941"For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully "
942"decentralized and censorship-resistant replacement for DNS and a mechanism "
943"for IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG)."
944msgstr ""
945
946#: template/faq.html.j2:171
947msgid "Is it possible to surf the WWW anonymously with GNUnet?"
948msgstr ""
949
950#: template/faq.html.j2:173
951msgid ""
952"A: It is not possible use GNUnet for anonymous browsing at this point. We "
953"recommend that you use Tor for anonymous surfing."
954msgstr ""
955
956#: template/faq.html.j2:181
957msgid "Is it possible to access GNUnet via a browser as an anonymous WWW?"
958msgstr ""
959
960#: template/faq.html.j2:183
961msgid ""
962"A: There is currently no proxy (like fproxy in Freenet) for GNUnet that "
963"would make it accessible via a browser. It is possible to build such a proxy "
964"and all one needs to know is the protocol used between the browser and the "
965"proxy and the GNUnet code for file-sharing."
966msgstr ""
967
968#: template/faq.html.j2:195
969msgid ""
970"A: There are actually a few graphical user interfaces for different "
971"functions. gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for "
972"file-sharing. There are a few other gnunet-XXX-gtk GUIs of lesser "
973"importance. Note that in order to obtain the GUI, you need to install the "
974"gnunet-gtk package, which is a separate download. gnunet-gtk is a meta GUI "
975"that integrates most of the other GUIs in one window. One exception is "
976"gnunet-setup, which must still be run separately at this time (as setup "
977"requires the peer to be stopped)."
978msgstr ""
979
980#: template/faq.html.j2:210
981msgid "Which operating systems does GNUnet run on?"
982msgstr ""
983
984#: template/faq.html.j2:212
985msgid ""
986"A: GNUnet is being developed and tested primarily under Debian GNU/Linux. "
987"Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch, "
988"FreeBSD and macOS. We have reports of working versions on many other GNU/"
989"Linux distributions; in the past we had reports of working versions on "
990"NetBSD, OpenBSD and Solaris. However, not all of those reports are recent, "
991"so if you cannot get GNUnet to work on those systems please let us know."
992msgstr ""
993
994#: template/faq.html.j2:228
995msgid "Who runs the GNS root zone?"
996msgstr ""
997
998#: template/faq.html.j2:230
999msgid ""
1000"A: Short answer: you. The long answer is the GNUnet will ship with a default "
1001"configuration of top-level domains. The governance of this default "
1002"configuration is not yet established. In any case, the user will be able to "
1003"modify this configuration at will. We expect normal users to have no need to "
1004"edit their own GNS zone(s) unless they host services themselves."
1005msgstr ""
1006
1007#: template/faq.html.j2:241
1008msgid "Where is the per-user GNS database kept?"
1009msgstr ""
1010
1011#: template/faq.html.j2:243
1012msgid ""
1013"A: The short answer is that the database is kept at the user's GNUnet peer. "
1014"Now, a user may run multiple GNUnet peers, in which case the database could "
1015"be kept at each peer (however, we don't have code for convenient "
1016"replication). Similarly, multiple GNUnet peers can share one instance of the "
1017"database --- the &quot;gnunet-service-namestore&quot; can be accessed from "
1018"remote (via TCP). The actual data can be stored in a Postgres database, for "
1019"which various replication options are again applicable. Ultimately, there "
1020"are many options for how users can store (and secure) their GNS database."
1021msgstr ""
1022
1023#: template/faq.html.j2:258
1024msgid "What is the expected average size of a GNS namestore database?"
1025msgstr ""
1026
1027#: template/faq.html.j2:260
1028msgid ""
1029"A: Pretty small. Based on our user study where we looked at browser "
1030"histories and the number of domains visited, we expect that GNS databases "
1031"will only grow to a few tens of thousands of entries, small enough to fit "
1032"even on mobile devices."
1033msgstr ""
1034
1035#: template/faq.html.j2:270
1036msgid "Is GNS resistant to the attacks on DNS used by the US?"
1037msgstr ""
1038
1039#: template/faq.html.j2:272
1040msgid ""
1041"A: We believe so, as there is no entity that any government could force to "
1042"change the mapping for a name except for each individual user (and then the "
1043"changes would only apply to the names that this user is the authority for). "
1044"So if everyone used GNS, the only practical attack of a government would be "
1045"to force the operator of a server to change the GNS records for his server "
1046"to point elsewhere. However, if the owner of the private key for a zone is "
1047"unavailable for enforcement, the respective zone cannot be changed and any "
1048"other zone delegating to this zone will achieve proper resolution."
1049msgstr ""
1050
1051#: template/faq.html.j2:286
1052msgid "How does GNS compare to other name systems?"
1053msgstr ""
1054
1055#: template/faq.html.j2:288
1056msgid ""
1057"A: A scientific paper on this topic <a href=\"https://grothoff.org/christian/"
1058"ns2018.pdf\">has been published </a> and below is a table from the "
1059"publication. For detailed descriptions please refer to the paper."
1060msgstr ""
1061
1062#: template/faq.html.j2:392
1063msgid "What is the difference between GNS and CoDoNS?"
1064msgstr ""
1065
1066#: template/faq.html.j2:394
1067msgid ""
1068"A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the "
1069"authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and "
1070"there are still registrars that determine who owns a name. <br><br> With "
1071"GNS, we decentralize the database and also decentralize the responsibility "
1072"for naming: each user runs their own personal root zone and is thus in "
1073"complete control of the names they use. GNS also has many additional "
1074"features (to keep names short and enable migration) which don't even make "
1075"sense in the context of CoDoNS."
1076msgstr ""
1077
1078#: template/faq.html.j2:410
1079msgid "What is the difference between GNS and SocialDNS?"
1080msgstr ""
1081
1082#: template/faq.html.j2:412
1083msgid ""
1084"A: Like GNS, SocialDNS allows each user to create DNS mappings. However, "
1085"with SocialDNS the mappings are shared through the social network and "
1086"subjected to ranking. As the social relationships evolve, names can thus "
1087"change in surprising ways. <br><br> With GNS, names are primarily shared via "
1088"delegation, and thus mappings will only change if the user responsible for "
1089"the name (the authority) manually changes the record."
1090msgstr ""
1091
1092#: template/faq.html.j2:426
1093msgid "What is the difference between GNS and ODDNS?"
1094msgstr ""
1095
1096#: template/faq.html.j2:428
1097msgid ""
1098"A: ODDNS is primarily designed to bypass the DNS root zone and the TLD "
1099"registries (such as those for \".com\" and \".org\"). Instead of using "
1100"those, each user is expected to maintain a database of (second-level) "
1101"domains (like \"gnu.org\") and the IP addresses of the respective name "
1102"servers. Resolution will fail if the target name servers change IPs."
1103msgstr ""
1104
1105#: template/faq.html.j2:439
1106msgid "What is the difference between GNS and Handshake?"
1107msgstr ""
1108
1109#: template/faq.html.j2:441
1110msgid ""
1111"A: Handshake is a blockchain-based method for root zone governance. Hence, "
1112"it does not address the name resolution process itself but delegates "
1113"resolution into DNS after the initial TLD resolution. Not taking "
1114"sustainablility considerations into account, Handshake could be used as an "
1115"additional supporting GNS root zone governance model, but we currently do "
1116"not have such plans in mind."
1117msgstr ""
1118
1119#: template/faq.html.j2:453
1120msgid "What is the difference between GNS and TrickleDNS?"
1121msgstr ""
1122
1123#: template/faq.html.j2:455
1124msgid ""
1125"A: TrickleDNS pushes (&quot;critical&quot;) DNS records between DNS "
1126"resolvers of participating domains to provide &quot;better availability, "
1127"lower query resolution times, and faster update propagation&quot;. Thus "
1128"TrickleDNS is focused on defeating attacks on the availability (and "
1129"performance) of record propagation in DNS, for example via DDoS attacks on "
1130"DNS root servers. TrickleDNS is thus concerned with how to ensure "
1131"distribution of authoritative records, and authority remains derived from "
1132"the DNS hierarchy."
1133msgstr ""
1134
1135#: template/faq.html.j2:468
1136msgid ""
1137"Does GNS require real-world introduction (secure PKEY exchange) in the style "
1138"of the PGP web of trust?"
1139msgstr ""
1140
1141#: template/faq.html.j2:470
1142msgid ""
1143"A: For security, it is well known that an initial trust path between the two "
1144"parties must exist. However, for applications where this is not required, "
1145"weaker mechanisms can be used. For example, we have implemented a first-come-"
1146"first-served (FCFS) authority which allows arbitrary users to register "
1147"arbitrary names. The key of this authority is included with every GNUnet "
1148"installation. Thus, any name registered with FCFS is in fact global and "
1149"requires no further introduction. However, the security of these names "
1150"depends entirely on the trustworthiness of the FCFS authority. The authority "
1151"can be queried under the &quot;.pin&quot; TLD."
1152msgstr ""
1153
1154#: template/faq.html.j2:485
1155msgid ""
1156"How can a legitimate domain owner tell other people to not use his name in "
1157"GNS?"
1158msgstr ""
1159
1160#: template/faq.html.j2:487
1161msgid ""
1162"A: Names have no owners in GNS, so there cannot be a &quot;legitimate&quot; "
1163"domain owner. Any user can claim any name (as his preferred name or &quot;"
1164"pseudonym&quot;) in his NICK record. Similarly, all other users can choose "
1165"to ignore this preference and use a name of their choice (or even assign no "
1166"name) for this user."
1167msgstr ""
1168
1169#: template/faq.html.j2:498
1170msgid ""
1171"Did you consider the privacy implications of making your personal GNS zone "
1172"visible?"
1173msgstr ""
1174
1175#: template/faq.html.j2:500
1176msgid ""
1177"A: Each record in GNS has a flag &quot;private&quot;. Records are shared "
1178"with other users (via DHT or zone transfers) only if this flag is not set. "
1179"Thus, users have full control over what information about their zones is "
1180"made public."
1181msgstr ""
1182
1183#: template/faq.html.j2:510
1184msgid "Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?"
1185msgstr ""
1186
1187#: template/faq.html.j2:512
1188msgid ""
1189"A: The question presumes that (a) virtual hosting is only necessary because "
1190"of IPv4 address scarcity, and (b) that LEHOs are only useful in the context "
1191"of virtual hosting. However, LEHOs are also useful to help with X.509 "
1192"certificate validation (as they specify for which legacy hostname the "
1193"certificate should be valid). Also, even with IPv6 fully deployed and &quot;"
1194"infinite&quot; IP addresses being available, we're not sure that virtual "
1195"hosting would disappear. Finally, we don't want to have to wait for IPv6 to "
1196"become commonplace, GNS should work with today's networks."
1197msgstr ""
1198
1199#: template/faq.html.j2:526
1200msgid ""
1201"Why does GNS not use a trust metric or consensus to determine globally "
1202"unique names?"
1203msgstr ""
1204
1205#: template/faq.html.j2:528
1206msgid ""
1207"A: Trust metrics have the fundamental problem that they have thresholds. As "
1208"trust relationships evolve, mappings would change their meaning as they "
1209"cross each others thresholds. We decided that the resulting unpredictability "
1210"of the resolution process was not acceptable. Furthermore, trust and "
1211"consensus might be easy to manipulate by adversaries."
1212msgstr ""
1213
1214#: template/faq.html.j2:539
1215msgid "How do you handle compromised zone keys in GNS?"
1216msgstr ""
1217
1218#: template/faq.html.j2:541
1219msgid ""
1220"A: The owner of a private key can create a revocation message. This one can "
1221"then be flooded throughout the overlay network, creating a copy at all "
1222"peers. Before using a public key, peers check if that key has been revoked. "
1223"All names that involve delegation via a revoked zone will then fail to "
1224"resolve. Peers always automatically check for the existence of a revocation "
1225"message when resolving names."
1226msgstr ""
1227
1228#: template/faq.html.j2:553
1229msgid "Could the signing algorithm of GNS be upgraded in the future?"
1230msgstr ""
1231
1232#: template/faq.html.j2:555
1233msgid ""
1234"A: Yes. In our efforts to standardize GNS, we have already modified the "
1235"protocol to support alternative delegation records. <br> <br> Naturally, "
1236"deployed GNS implementations would have to be updated to support the new "
1237"signature scheme. The new scheme can then be run in parallel with the "
1238"existing system by using a new record type to indicate the use of a "
1239"different cipher system."
1240msgstr ""
1241
1242#: template/faq.html.j2:569
1243msgid ""
1244"How can a GNS zone maintain several name servers, e.g. for load balancing?"
1245msgstr ""
1246
1247#: template/faq.html.j2:571
1248msgid ""
1249"A: We don't expect this to be necessary, as GNS records are stored (and "
1250"replicated) in the R5N DHT. Thus the authority will typically not be "
1251"contacted whenever clients perform a lookup. Even if the authority goes "
1252"(temporarily) off-line, the DHT will cache the records for some time. "
1253"However, should having multiple servers for a zone be considered truly "
1254"necessary, the owner of the zone can simply run multiple peers (and share "
1255"the zone's key and database among them)."
1256msgstr ""
1257
1258#: template/faq.html.j2:584
1259msgid ""
1260"Why do you believe it is worth giving up unique names for censorship "
1261"resistance?"
1262msgstr ""
1263
1264#: template/faq.html.j2:586
1265msgid ""
1266"A: The GNU Name system offers an alternative to DNS that is censorship "
1267"resistant. As with any security mechanism, this comes at a cost (names are "
1268"not globally unique). To draw a parallel, HTTPS connections use more "
1269"bandwidth and have higher latency than HTTP connections. Depending on your "
1270"application, HTTPS may not be worth the cost. However, for users that are "
1271"experiencing censorship (or are concerned about it), giving up globally "
1272"unique names may very well be worth the cost. After all, what is a &quot;"
1273"globally&quot; unique name worth, if it does not resolve?"
1274msgstr ""
1275
1276#: template/faq.html.j2:600
1277msgid "Why do you say that DNS is 'centralized' and 'distributed'?"
1278msgstr ""
1279
1280#: template/faq.html.j2:602
1281msgid ""
1282"A: We say that DNS is 'centralized' because it has a central component / "
1283"central point of failure --- the root zone and its management by IANA/ICANN. "
1284"This centralization creates vulnerabilities. For example, the US government "
1285"was able to reassign the management of the country-TLDs of Afganistan and "
1286"Iraq during the wars at the beginning of the 21st century."
1287msgstr ""
1288
1289#: template/faq.html.j2:613
1290msgid "How does GNS protect against layer-3 censorship?"
1291msgstr ""
1292
1293#: template/faq.html.j2:615
1294msgid ""
1295"A: GNS does not directly help with layer-3 censorship, but it does help "
1296"indirectly in two ways: <ol> <li> Many websites today use virtual hosting, "
1297"so blocking a particular IP address causes much more collateral damage than "
1298"blocking a DNS name. It thus raises the cost of censorship.</li> <li> "
1299"Existing layer-3 circumvention solutions (such as Tor) would benefit from a "
1300"censorship resistant naming system. Accessing Tor's &quot;.onion&quot; "
1301"namespace currently requires users to use unmemorable cryptographic "
1302"identifiers. With nicer names, Tor and tor2web-like services would be even "
1303"easier to use. </ol>"
1304msgstr ""
1305
1306#: template/faq.html.j2:634
1307msgid "Does GNS work with search engines?"
1308msgstr ""
1309
1310#: template/faq.html.j2:636
1311msgid ""
1312"A: GNS creates no significant problems for search engines, as they can use "
1313"GNS to perform name resolution as well as any normal user. Naturally, while "
1314"we typically expect normal users to install custom software for name "
1315"resolution, this is unlikely to work for search engines today. However, the "
1316"DNS2GNS gateway allows search engines to use DNS to resolve GNS names, so "
1317"they can still index GNS resources. However, as using DNS2GNS gateways "
1318"breaks the cryptographic chain of trust, legacy search engines will "
1319"obviously not obtain censorship-resistant names."
1320msgstr ""
1321
1322#: template/faq.html.j2:650
1323msgid "How does GNS compare to the Unmanaged Internet Architecture (UIA)?"
1324msgstr ""
1325
1326#: template/faq.html.j2:652
1327msgid ""
1328"A: UIA and GNS both share the same basic naming model, which actually "
1329"originated with Rivest's SDSI. However, UIA is not concerned about "
1330"integration with legacy applications and instead focuses on universal "
1331"connectivity between a user's many machines. In contrast, GNS was designed "
1332"to interoperate with DNS as much as possible, and to also work as much as "
1333"possible with the existing Web infrastructure. UIA is not at all concerned "
1334"about legacy systems (clean slate)."
1335msgstr ""
1336
1337#: template/faq.html.j2:665
1338msgid "Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?"
1339msgstr ""
1340
1341#: template/faq.html.j2:667
1342msgid ""
1343"A: First of all, in GNS you can explicitly see the trust chain, so you know "
1344"if a name you are resolving belongs to a friend, or a friend-of-a-friend, "
1345"and can thus decide how much you trust the result. Naturally, the trusted-"
1346"computing base (TCB) can become arbitrarily large this way --- however, "
1347"given the name length restriction, for an individual name it is always less "
1348"than about 128 entities."
1349msgstr ""
1350
1351#: template/faq.html.j2:679
1352msgid ""
1353"How does GNS handle SRV/TLSA records where service and protocol are part of "
1354"the domain name?"
1355msgstr ""
1356
1357#: template/faq.html.j2:681
1358msgid ""
1359"A: When GNS splits a domain name into labels for resolution, it detects the "
1360"&quot;_Service._Proto&quot; syntax, converts &quot;Service&quot; to the "
1361"corresponding port number and &quot;Proto&quot; to the corresponding "
1362"protocol number. The rest of the name is resolved as usual. Then, when the "
1363"result is presented, GNS looks for the GNS-specific &quot;BOX&quot; record "
1364"type. A BOX record is a record that contains another record (such as SRV or "
1365"TLSA records) and adds a service and protocol number (and the original boxed "
1366"record type) to it."
1367msgstr ""
1368
1369#: template/faq.html.j2:697
1370msgid ""
1371"I receive many &quot;WARNING Calculated flow delay for X at Y for Z&quot;. "
1372"Should I worry?"
1373msgstr ""
1374
1375#: template/faq.html.j2:699
1376msgid ""
1377"A: Right now, this is expected and a known cause for high latency in GNUnet. "
1378"We have started a major rewrite to address this and other problems, but "
1379"until the Transport Next Generation (TNG) is ready, these warnings are "
1380"expected."
1381msgstr ""
1382
1383#: template/faq.html.j2:708
1384msgid "Error opening `/dev/net/tun': No such file or directory?"
1385msgstr ""
1386
1387#: template/faq.html.j2:710
1388msgid ""
1389"A: If you get this error message, the solution is simple. Issue the "
1390"following commands (as root) to create the required device file"
1391msgstr ""
1392
1393#: template/faq.html.j2:722
1394msgid ""
1395"'iptables: No chain/target/match by that name.' (when running gnunet-service-"
1396"dns)?"
1397msgstr ""
1398
1399#: template/faq.html.j2:724
1400msgid ""
1401"A: For GNUnet DNS, your iptables needs to have &quot;owner&quot; match "
1402"support. This is accomplished by having the correct kernel options. Check if "
1403"your kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or "
1404"'m' (and the module is loaded)."
1405msgstr ""
1406
1407#: template/faq.html.j2:736
1408msgid "'Timeout was reached' when running PT on Fedora (and possibly others)?"
1409msgstr ""
1410
1411#: template/faq.html.j2:738
1412msgid ""
1413"A: If you get an error stating that the VPN timeout was reached, check if "
1414"your firewall is enabled and blocking the connections."
1415msgstr ""
1416
1417#: template/faq.html.j2:746
1418msgid ""
1419"I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'"
1420msgstr ""
1421
1422#: template/faq.html.j2:748
1423msgid ""
1424"A: This error usually occurs when your linker fails to locate one of "
1425"GNUnet's libraries. This can have two causes. First, it is theoretically "
1426"possible that the library is not installed on your system; however, if you "
1427"compiled GNUnet the normal way and/or used a binary package, that is highly "
1428"unlikely. The more common cause is that you installed GNUnet to a directory "
1429"that your linker does not search. There are several ways to fix this that "
1430"are described below. If you are 'root' and you installed to a system folder "
1431"(such as /usr/local), you want to add the libraries to the system-wide "
1432"search path. This is done by adding a line \"/usr/local/lib/\" to /etc/ld.so."
1433"conf and running \"ldconfig\". If you installed GNUnet to /opt or any other "
1434"similar path, you obviously have to change \"/usr/local\" accordingly. If "
1435"you do not have 'root' rights or if you installed GNUnet to say \"/home/"
1436"$USER/\", then you can explicitly tell your linker to search a particular "
1437"directory for libraries using the \"LD_LIBRARY_PATH\" environment variable. "
1438"For example, if you configured GNUnet using a prefix of \"$HOME/gnunet/\" "
1439"you want to run:"
1440msgstr ""
1441
1442#: template/faq.html.j2:774
1443msgid ""
1444"to ensure GNUnet's binaries and libraries are found. In order to avoid "
1445"having to do so each time, you can add the above lines (without the \"$\") "
1446"to your .bashrc or .profile file. You will have to logout and login again to "
1447"have this new profile be applied to all shells (including your desktop "
1448"environment)."
1449msgstr ""
1450
1451#: template/faq.html.j2:781
1452msgid "What error messages can be ignored?"
1453msgstr ""
1454
1455#: template/faq.html.j2:783
1456msgid ""
1457"A: Error messages flagged as \"DEBUG\" should be disabled in binaries built "
1458"for end-users and can always be ignored. Error messages flagged as \"INFO\" "
1459"always refer to harmless events that require no action. For example, GNUnet "
1460"may use an INFO message to indicate that it is currently performing an "
1461"expensive operation that will take some time. GNUnet will also use INFO "
1462"messages to display information about important configuration values."
1463msgstr ""
1464
1465#: template/faq.html.j2:799
1466msgid "How does GNUnet compare to other file-sharing applications?"
1467msgstr ""
1468
1469#: template/faq.html.j2:801
1470msgid ""
1471"A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most other "
1472"P2P networks, GNUnet was designed with security in mind as the highest "
1473"priority. We intend on producing a network with comprehensive security "
1474"features. Many other P2P networks are open to a wide variety of attacks, and "
1475"users have little privacy. GNUnet is also Free Software and thus the source "
1476"code is available, so you do not have to worry about being spied upon by the "
1477"software. The following table summarises the main differences between GNUnet "
1478"and other systems. The information is accurate to the best of our knowledge. "
1479"The comparison is difficult since there are sometimes differences between "
1480"various implementations of (almost) the same protocol. In general, we pick a "
1481"free implementation as the reference implementation since it is possible to "
1482"inspect the free code. Also, all of these systems are changing over time and "
1483"thus the data below may not be up-to-date. If you find any flaws, please let "
1484"us know. Finally, the table is not saying terribly much (it is hard to "
1485"compare these systems this briefly), so if you want the real differences, "
1486"read the research papers (and probably the code)."
1487msgstr ""
1488
1489#: template/faq.html.j2:915
1490msgid ""
1491"Another important point of reference are the various anonymous peer-to-peer "
1492"networks. Here, there are differences in terms of application domain and how "
1493"specifically anonymity is achieved. Anonymous routing is a hard research "
1494"topic, so for a superficial comparison like this one we focus on the "
1495"latency. Another important factor is the programming language. Type-safe "
1496"languages may offer certain security benefits; however, this may come at the "
1497"cost of significant increases in resource consumption which in turn may "
1498"reduce anonymity."
1499msgstr ""
1500
1501#: template/faq.html.j2:928
1502msgid "Are there any known attacks (on GNUnet's file-sharing application)?"
1503msgstr ""
1504
1505#: template/faq.html.j2:930
1506msgid ""
1507"A: Generally, there is the possibility of a known plaintext attack on "
1508"keywords, but since the user has control over the keywords that are "
1509"associated with the content he inserts, the user can take advantage of the "
1510"same techniques used to generate reasonable passwords to defend against such "
1511"an attack. In any event, we are not trying to hide content; thus, unless the "
1512"user is trying to insert information into the network that can only be "
1513"shared with a small group of people, there is no real reason to try to "
1514"obfuscate the content by choosing a difficult keyword anyway."
1515msgstr ""
1516
1517#: template/faq.html.j2:944
1518msgid "What do you mean by anonymity?"
1519msgstr ""
1520
1521#: template/faq.html.j2:946
1522msgid ""
1523"A: Anonymity is the lack of distinction of an individual from a (large) "
1524"group. A central goal for anonymous file-sharing in GNUnet is to make all "
1525"users (peers) form a group and to make communications in that group "
1526"anonymous, that is, nobody (but the initiator) should be able to tell which "
1527"of the peers in the group originated the message. In other words, it should "
1528"be difficult to impossible for an adversary to distinguish between the "
1529"originating peer and all other peers."
1530msgstr ""
1531
1532#: template/faq.html.j2:958
1533msgid "What does my system do when participating in GNUnet file sharing?"
1534msgstr ""
1535
1536#: template/faq.html.j2:960
1537msgid ""
1538"A: In GNUnet you set up a node (a peer). It is identified by an ID (hash of "
1539"its public key) and has a number of addresses it is reachable by (may have "
1540"no addresses, for instance when it's behind a NAT). You specify bandwidth "
1541"limits (how much traffic GNUnet is allowed to consume) and datastore quote "
1542"(how large your on-disk block storage is) . Your node will then proceed to "
1543"connect to other nodes, becoming part of the network."
1544msgstr ""
1545
1546#: template/faq.html.j2:975
1547msgid "How can I help translate this webpage into other languages?"
1548msgstr ""
1549
1550#: template/faq.html.j2:977
1551msgid ""
1552"A: First, you need to register an account with our weblate system. Please "
1553"send an e-mail with the desired target language to translators@gnunet.org or "
1554"ask for help on the #gnunet chat on irc.freenode.net. Typically someone with "
1555"sufficient permissions will then grant you access. Naturally, any abuse will "
1556"result in the loss of permissions."
1557msgstr ""
1558
1559#: template/faq.html.j2:989
1560msgid "I have some great idea for a new feature, what should I do?"
1561msgstr ""
1562
1563#: template/faq.html.j2:991
1564msgid ""
1565"A: Sadly, we have many more feature requests than we can possibly implement. "
1566"The best way to actually get a new feature implemented is to do it yourself "
1567"--- and to then send us a patch."
1568msgstr ""
1569
1570#: template/glossary.html.j2:12
1571msgid "Ego"
1572msgstr ""
1573
1574#: template/glossary.html.j2:14
1575msgid ""
1576"We use the term \"Ego\" to refer to the fact that users in GNUnet can have "
1577"multiple unlinkable identities, in the sense of alter egos. The ability to "
1578"have more than one identity is crucial, as we may want to keep our egos for "
1579"business separate from those we use for political activities or romance.<br> "
1580"Egos in GNUnet are technically equivalent to identities (and the code does "
1581"not distinguish between them). We simply sometimes use the term \"ego\" to "
1582"stress that you can have more than one."
1583msgstr ""
1584
1585#: template/glossary.html.j2:27
1586msgid "Identity"
1587msgstr ""
1588
1589#: template/glossary.html.j2:29
1590msgid ""
1591"In GNUnet users are identified via a public key, and that public key is then "
1592"often referred to as the \"Identity\" of the user. However, the concept is "
1593"not as draconian as it often is in real life where many are forced to have "
1594"one name, one passport and one unique identification number. <br> As long as "
1595"identities in GNUnet are simply public keys, users are free to create any "
1596"number of identities, and we call those egos to emphasize the difference. "
1597"Even though users can create such egos freely, it is possible to have an ego "
1598"certified by some certification authority, resulting in something that more "
1599"closely resembles the traditional concept of an identity.<br> For example, a "
1600"university may certify the identities of its students such that they can "
1601"prove that they are studying. Students may keep their (certified) student "
1602"identity separate from other egos that they use for other activities in life."
1603msgstr ""
1604
1605#: template/glossary.html.j2:50
1606msgid "Pseudonym"
1607msgstr ""
1608
1609#: template/glossary.html.j2:52
1610msgid ""
1611"A pseudonym is an ego that is specifically intended to not be linked to "
1612"one's real name. GNUnet users can create many egos, and thus also many "
1613"pseudonyms. <br> Repeated uses of the same pseudonym are linkable by "
1614"definition, as they involve the same public key. Anonymity requires the use "
1615"of either the special \"anonymous\" pseudonym (for GNUnet, this is the "
1616"neutral element on the elliptic curve) or a throw-away pseudonym that is "
1617"only used once."
1618msgstr ""
1619
1620#: template/glossary.html.j2:71
1621msgid "Namespaces"
1622msgstr ""
1623
1624#: template/glossary.html.j2:73
1625msgid ""
1626"The GNU Name System allows every ego (or identity) to securely and privately "
1627"associate any number of label-value pairs with an ego. The values are called "
1628"record sets following the terminology of the Domain Name System (DNS). The "
1629"mapping of labels to record sets for a given ego is called a namespace. <br> "
1630"If records are made public and thus published, it is possible for other "
1631"users to lookup the record given the ego's public key and the label. Here, "
1632"not only the label can thus act as a passphrase but also the public key -- "
1633"which despite its name may not be public knowledge and is never disclosed by "
1634"the GNS protocol itself."
1635msgstr ""
1636
1637#: template/glossary.html.j2:89
1638msgid "Peer"
1639msgstr ""
1640
1641#: template/glossary.html.j2:91
1642msgid ""
1643"A \"peer\" is an instance of GNUnet with its own per-instance public key and "
1644"network addresses. Technically, it is possible to run multiple peers on the "
1645"same host, but this only makes sense for testing. <br> By design GNUnet "
1646"supports multiple users to share the same peer, just as UNIX is a multi-user "
1647"system. A \"peer\" typically consists of a set of foundational GNUnet "
1648"services running as the \"gnunet\" user and allowing all users in the "
1649"\"gnunet\" group to utilize the API. On multi-user systems, additional "
1650"\"personalized\" services may be required per user. <br> While peers are "
1651"also identified by public keys, these public keys are completely unrelated "
1652"to egos or identities. Namespaces cannot be associated with a peer, only "
1653"with egos."
1654msgstr ""
1655
1656#: template/gns.html.j2:13 template/gnurl.html.j2:60
1657#: template/reclaim/index.html.j2:80 template/reclaim/motivation.html.j2:6
1658#, fuzzy
1659#| msgid "Documentation"
1660msgid "Motivation"
1661msgstr "प्रलेखन"
1662
1663#: template/gns.html.j2:15
1664msgid ""
1665"The Domain Name System today enables traffic amplification attacks, "
1666"censorship (i.e. China), mass surveillance (MORECOWBELL) and offensive cyber "
1667"war (QUANTUMDNS).<br/> Unfortunately, band aid solutions such as DoT, DoH, "
1668"DNSSEC, DPRIVE and the like will not fix this. This is why we built the GNU "
1669"Name System (GNS), a secure, decentralized name system built on top of "
1670"GNUnet."
1671msgstr ""
1672
1673#: template/gns.html.j2:28 template/reclaim/tech.html.j2:6
1674msgid "Overview"
1675msgstr ""
1676
1677#: template/gns.html.j2:39
1678msgid ""
1679"The GNU Name System (GNS) is secure and decentralized naming system. It "
1680"allows its users to register names as top-level domains (TLDs) and resolve "
1681"other namespaces within their TLDs. <br/> GNS is designed to provide: <ul> "
1682"<li>Censorship resistance</li> <li>Query privacy</li> <li>Secure name "
1683"resolution</li> <li>Compatibility with DNS</li>"
1684msgstr ""
1685
1686#: template/gns.html.j2:52
1687msgid "Resources"
1688msgstr ""
1689
1690#: template/gnurl.html.j2:21
1691msgid ""
1692"libgnurl is a micro fork of libcurl. The goal of libgnurl is to support only "
1693"HTTP and HTTPS (and only HTTP 1.x) with a single crypto backend (GnuTLS) to "
1694"ensure a small footprint and uniform experience for developers regardless of "
1695"how libcurl was compiled."
1696msgstr ""
1697
1698#: template/gnurl.html.j2:30
1699msgid ""
1700"Our main usecase is for GNUnet and Taler, but it might be usable for others, "
1701"hence we&#39;re releasing the code to the general public."
1702msgstr ""
1703
1704#: template/gnurl.html.j2:37
1705msgid ""
1706"libgnurl is released under the same license as libcurl. Please read the "
1707"README for instructions, as you must supply the correct options to configure "
1708"to get a proper build of libgnurl."
1709msgstr ""
1710
1711#: template/gnurl.html.j2:48
1712#, fuzzy
1713#| msgid "About"
1714msgid "About gnurl"
1715msgstr "जानकारी"
1716
1717#: template/gnurl.html.j2:50
1718msgid ""
1719"Large parts of the following 6 paragraphs are old and need to be rewritten."
1720msgstr ""
1721
1722#: template/gnurl.html.j2:62
1723msgid ""
1724"cURL supports many crypto backends. GNUnet requires the use of GnuTLS, but "
1725"other variants are used by some distributions. Supporting other crypto "
1726"backends would again expose us to a wider array of security issues, may "
1727"create licensing issues and most importantly introduce new bugs as some "
1728"crypto backends are known to introduce subtle runtime issues. While it is "
1729"possible to have two versions of libcurl installed on the same system, this "
1730"is error-prone, especially as if we are linked against the wrong version, "
1731"the bugs that arise might be rather subtle."
1732msgstr ""
1733
1734#: template/gnurl.html.j2:75
1735msgid ""
1736"For GNUnet, we also need a particularly modern version of GnuTLS. Thus, it "
1737"would anyway be necessary to recompile cURL for GNUnet. But what happens if "
1738"one links cURL against this version of GnuTLS? Well, first one would install "
1739"GnuTLS by hand in the system. Then, we build cURL. cURL will build against "
1740"it just fine, but the linker will eventually complain bitterly. The reason "
1741"is that cURL also links against a bunch of other system libraries (gssapi, "
1742"ldap, ssh2, rtmp, krb5, sasl2, see discussion on obscure protocols above), "
1743"which --- as they are part of the distribution --- were linked against an "
1744"older version of GnuTLS. As a result, the same binary would be linked "
1745"against two different versions of GnuTLS. That is typically a recipe for "
1746"disaster. Thus, in order to avoid updating a dozen system libraries (and "
1747"having two versions of those installed), it is necessary to disable all of "
1748"those cURL features that GNUnet does not use, and there are many of those. "
1749"For GNUnet, the more obscure protocols supported by cURL are close to dead "
1750"code --- mostly harmless, but not useful. However, as some application may "
1751"use one of those features, distributions are typically forced to enable all "
1752"of those features, and thus including security issues that might arise from "
1753"that code."
1754msgstr ""
1755
1756#: template/gnurl.html.j2:99
1757msgid ""
1758"So to use a modern version of GnuTLS, a sane approach is to disable all of "
1759"the \"optional\" features of cURL that drag in system libraries that link "
1760"against the older GnuTLS. That works, except that one should then NEVER "
1761"install that version of libcurl in say /usr or /usr/local, as that may break "
1762"other parts of the system that might depend on these features that we just "
1763"disabled. Libtool versioning doesn't help here, as it is not intended to "
1764"deal with libraries that have optional features. Naturally, installing cURL "
1765"somewhere else is also problematic, as we now need to be really careful that "
1766"the linker will link GNUnet against the right version. Note that none of "
1767"this can really be trivially fixed by the cURL developers."
1768msgstr ""
1769
1770#: template/gnurl.html.j2:118
1771msgid "Rename to fix"
1772msgstr ""
1773
1774#: template/gnurl.html.j2:120
1775#, python-format
1776msgid ""
1777"How does forking fix it? Easy. First, we can get rid of all of the "
1778"compatibility issues --- if you use libgnurl, you state that you don&#39;t "
1779"need anything but HTTP/HTTPS. Those applications that need more, should "
1780"stick with the original cURL. Those that do not, can choose to move to "
1781"something simpler. As the library gets a new name, we do not have to worry "
1782"about tons of packages breaking as soon as one rebuilds it. So renaming "
1783"itself and saying that \"libgnurl = libcurl with only HTTP/HTTPS support and "
1784"GnuTLS\" fixes 99%% of the problems that darkened my mood. Note that this "
1785"pretty much CANNOT be done without a fork, as renaming is an essential part "
1786"of the fix. Now, there might be creative solutions to achieve the same thing "
1787"within the standard cURL build system, but this was deemed to be too much "
1788"work when gnurl was originally started. The changes libgnurl makes to curl "
1789"are miniscule and can easily be applied again and again whenever libcurl "
1790"makes a new release."
1791msgstr ""
1792
1793#: template/gnurl.html.j2:142
1794msgid "Using libgnurl"
1795msgstr ""
1796
1797#: template/gnurl.html.j2:144
1798msgid ""
1799"Projects that use cURL only for HTTP/HTTPS and that would work with GnuTLS "
1800"should be able to switch to libgnurl by changing \"-lcurl\" to \"-lgnurl\". "
1801"That&#39;s it. No changes to the source code should be required, as libgnurl "
1802"strives for bug-for-bug compatibility with the HTTP/HTTPS/GnuTLS subset of "
1803"cURL. We might add new features relating to this core subset if they are "
1804"proposed, but so far we have kept our changes minimal and no additions to "
1805"the original curl source have been written."
1806msgstr ""
1807
1808#: template/gnurl.html.j2:161
1809msgid "Gotchas"
1810msgstr ""
1811
1812#: template/gnurl.html.j2:163
1813msgid ""
1814"libgnurl and gnurl are not intended to be used as a replacement for curl for "
1815"users: <br> This does not mean there is no confidence in the work done with "
1816"gnurl, it means that tools which expect curl or libcurl will not make use of "
1817"a different named binary and library. If you know what you are doing, you "
1818"should be able to use gnurl as part of your tooling in place of curl. We do "
1819"not recommend to do so however, as the only usage it is tested for <em>so "
1820"far</em> is as part of Taler&#39;s and GNunet&#39;s build-system. <br> Since "
1821"no conflicts in filenames occur you are not expected to remove curl to make "
1822"use of gnurl and viceversa."
1823msgstr ""
1824
1825#: template/gnurl.html.j2:188
1826msgid "You can get the gnurl git repository using:"
1827msgstr ""
1828
1829#: template/gnurl.html.j2:201
1830msgid "The versions are checked in as (signed) git tags."
1831msgstr ""
1832
1833#: template/gnurl.html.j2:211
1834msgid ""
1835"Releases are published on <a href=\"https://ftpmirror.gnu.org/gnu/gnunet/"
1836"\">ftpmirror.gnu.org/gnu/gnunet</a>. gnurl is available from within a "
1837"variety of distributions and package managers. Some Package Managers which "
1838"include gnurl are: <a href=\"https://www.gnu.org/software/guix/\">GNU Guix</"
1839"a> (available as \"gnurl\"), <a href=\"https://gentoo.org\">Gentoo</a> "
1840"through the collaborative ebuild collection <a href=\"https://git.gnunet.org/"
1841"youbroketheinternet-overlay.git/\">youbroketheinternet</a>, <a href="
1842"\"https://nixos.org/nix/\">Nix</a>, and as www/gnurl in <a href=\"https://"
1843"pkgsrc.org\">pkgsrc</a>."
1844msgstr ""
1845
1846#: template/gnurl.html.j2:228
1847msgid "Building gnurl"
1848msgstr ""
1849
1850#: template/gnurl.html.j2:230
1851msgid ""
1852"We suggest to closely follow release announcements, as they might indicate "
1853"changes in how gnurl is to be build. <br> If your package manager provides a "
1854"binary build or build instructions to build gnurl from source automated and "
1855"integrated with your environment, we strongly suggest to use this binary "
1856"build. <br> There are two ways to build gnurl. The first one builds from the "
1857"most recent git tag, the second one uses the distributed tarball. "
1858"Distributors generally are supposed to build from the tarball, but we "
1859"describe both methods here. Both methods are written with a NetBSD 9 "
1860"userland in mind, substitute tools as necessary. <br> You should <b>avoid</"
1861"b> building gnurl from the tip of the default git branch, as only tags are "
1862"considered to be stable and approved builds."
1863msgstr ""
1864
1865#: template/gnurl.html.j2:251
1866msgid "Building from the distributed tarball (prefered method)"
1867msgstr ""
1868
1869#: template/gnurl.html.j2:253
1870msgid ""
1871"If you want to verify the signature, install an OpenPGP compatible tool such "
1872"as security/gnupgp2 (and set it up). Assuming you use pkgin:"
1873msgstr ""
1874
1875#: template/gnurl.html.j2:267
1876msgid "Fetch the signature key from"
1877msgstr ""
1878
1879#: template/gnurl.html.j2:271
1880msgid "or via commandline with gnupg2."
1881msgstr ""
1882
1883#: template/gnurl.html.j2:276
1884msgid ""
1885"Fetch the release, the signature, the checksum file as well as its signature:"
1886msgstr ""
1887
1888#: template/gnurl.html.j2:295
1889msgid ""
1890"verify the signatures, and verify the checksums against the checksums in "
1891"the .sum.txt file."
1892msgstr ""
1893
1894#: template/gnurl.html.j2:301
1895msgid "unpack the tarball:"
1896msgstr ""
1897
1898#: template/gnurl.html.j2:311
1899msgid "Change into the directory"
1900msgstr ""
1901
1902#: template/gnurl.html.j2:321
1903msgid "Now you can either run"
1904msgstr ""
1905
1906#: template/gnurl.html.j2:331
1907msgid "directly (and read configure-gnurl before you do so) or invoke"
1908msgstr ""
1909
1910#: template/gnurl.html.j2:341
1911msgid ""
1912"and pass additional parameters such as a custom PREFIX location. Further "
1913"reference can be the"
1914msgstr ""
1915
1916#: template/gnurl.html.j2:346
1917msgid "Now run"
1918msgstr ""
1919
1920#: template/gnurl.html.j2:356
1921msgid "(this is optional)"
1922msgstr ""
1923
1924#: template/gnurl.html.j2:365
1925msgid "and you are done."
1926msgstr ""
1927
1928#: template/gnurl.html.j2:369
1929msgid "Building from a tagged git commit"
1930msgstr ""
1931
1932#: template/gnurl.html.j2:371
1933msgid ""
1934"Follow the steps above, but instead of downloading the tarball, clone the "
1935"git tag you want to build from."
1936msgstr ""
1937
1938#: template/gnurl.html.j2:382
1939msgid "Reporting Bugs"
1940msgstr ""
1941
1942#: template/gnurl.html.j2:384
1943msgid ""
1944"You can report bugs on our bug tracker: <a href=\"https://bugs.gnunet.org/"
1945"\">bugs.gnunet.org</a>. Alternatively you can use our bug mailinglist, but "
1946"we prefer to track bugs on the bugtracker."
1947msgstr ""
1948
1949#: template/gnurl.html.j2:395
1950msgid "Maintainer and Cryptographic signatures"
1951msgstr ""
1952
1953#: template/gnurl.html.j2:397
1954msgid ""
1955"gnurl/libgnurl is looking for a new maintainer. Releases after version "
1956"7.69.1 and up to version 7.72.0 were signed with the OpenPGP Key "
1957"<b>0xD6B570842F7E7F8D</b> (<a href=\"https://keys.openpgp.org/search?"
1958"q=6115012DEA3026F62A98A556D6B570842F7E7F8D\">keys.openpgp.org</a>), with the "
1959"key fingerprint <b>6115 012D EA30 26F6 2A98 A556 D6B5 7084 2F7E 7F8D</b>."
1960msgstr ""
1961
1962#: template/gsoc-2018-gnunet-webui.html.j2:7
1963msgid "GSoC 2018: GNUnet WebUI (GNUnet Web-based User Interface)"
1964msgstr ""
1965
1966#: template/gsoc-2018-gnunet-webui.html.j2:11
1967msgid "Tue, 08/14/2018 - 07:55, Phil Buschmann"
1968msgstr ""
1969
1970#: template/gsoc-2018-gnunet-webui.html.j2:18
1971msgid ""
1972"In the context of Google Summer of Code 2018, my mentor (Martin "
1973"Schanzenbach) and I have worked on creating and extending the REST API of "
1974"GNUnet. Currently, we mirrored the functionality of following commands:"
1975msgstr ""
1976
1977#: template/gsoc-2018-gnunet-webui.html.j2:32
1978msgid ""
1979"Additionally, we developed a website with the Javascript framework Angular 6 "
1980"and the design framework iotaCSS to use the new REST API. The REST API of "
1981"GNUnet is now documented with Sphinx."
1982msgstr ""
1983
1984#: template/gsoc-2018-gnunet-webui.html.j2:41
1985msgid ""
1986"... when you can use the command line tools? We need to keep in mind, that "
1987"everyone has the right to stay secure and private but not everyone feels "
1988"comfortable using a terminal. The further developed REST access to GNUnet "
1989"APIs in addition to the new web application allows new users to interact "
1990"with GNUnet over a well known tool: their browsers. This addition to the C "
1991"API and the command line tools may attract new users and developers."
1992msgstr ""
1993
1994#: template/gsoc-2018-gnunet-webui.html.j2:54
1995msgid ""
1996"<li> The REST API developed in GNUnet<br> The REST API is already merged "
1997"into the gnunet.git repository (<a href=\"https://gnunet.org/git/gnunet.git/"
1998"\">GNUnet Main Git</a>).<br /> To use the new features, clone the repository "
1999"and follow the <a href=\"https://gnunet.org/en/install.html\">Installation</"
2000"a> on gnunet.org. Then, start the rest service with \"gnunet-arm -i rest\". "
2001"</li> <li> The Web Application<br> The web application is available under "
2002"the gnunet-webui.git repository (<a href=\"https://gnunet.org/git/gnunet-"
2003"webui.git/\">GNUnet WebUI Git</a>).<br /> You need to install the newest "
2004"version of 'node' and 'yarn'. Dependent on your system, you may need to "
2005"download newer versions and install them manually and not over your packet "
2006"manager. After the installation succeeded, you need to clone the repository. "
2007"Then, you need to run \"yarn install\" and \"yarn start\" for testing "
2008"purposes. To deploy the website (keep in mind, that this website "
2009"communicates with another localhost instance) use \"yarn build\" for "
2010"building the web application and use the output in the 'dist' directory. </"
2011"li> <li> The Documentation<br /> The documentation is available under the "
2012"gnunet-rest-api.git repository (<a href=\"https://gnunet.org/git/gnunet-rest-"
2013"api.git/\">GNUnet REST API Docmentation Git</a>).<br /> Clone the repository "
2014"and \"make html\". Then open the 'index.html' under 'build/html/'. </li>"
2015msgstr ""
2016
2017#: template/gsoc-2018-gnunet-webui.html.j2:91
2018msgid ""
2019"Please, give it a try and contact me, if you find any bugs or unintentional "
2020"features. ;)"
2021msgstr ""
2022
2023#: template/gsoc-2018-gnunet-webui.html.j2:98
2024msgid ""
2025"Right now, the build process of the web application may be a little too "
2026"complex for a casual user. We may be able to solve this by using docker.<br /"
2027"> Additionally, the web application does not prevent wrong inputs but "
2028"responds with error messages. Adding GNUnet Records is currently only usable "
2029"for people, who know how a GNS Record looks like. This can be adapted to "
2030"each record type.<br /> Last but not least, additional features, design "
2031"changes, etc..."
2032msgstr ""
2033
2034#: template/gsoc-2018-gnunet-webui.html.j2:111
2035msgid "Thanks for reading."
2036msgstr ""
2037
2038#: template/gsoc.html.j2:6
2039msgid "GNUnet's Google Summer of Code projects"
2040msgstr ""
2041
2042#: template/gsoc.html.j2:12 template/gsoc.html.j2:29
2043msgid "Ideas 2021"
2044msgstr ""
2045
2046#: template/gsoc.html.j2:13 template/gsoc.html.j2:215
2047#, fuzzy
2048#| msgid "GSoC Projects"
2049msgid "Past projects"
2050msgstr "ग स ओ क परियोजनाओं"
2051
2052#: template/gsoc.html.j2:14 template/gsoc.html.j2:596
2053msgid "Finished projects"
2054msgstr ""
2055
2056#: template/gsoc.html.j2:21
2057msgid ""
2058"As a GNU project, GNUnet has participated in the Google Summer of Code "
2059"(GSoC) for a number of years. This page lists all current, past, and "
2060"finished projects. If you want to participate and apply for any of the ideas "
2061"for 2020 below or any past project which is not yet finished (or even your "
2062"own idea), please contact us either in IRC or mailing list."
2063msgstr ""
2064
2065#: template/gsoc.html.j2:34
2066msgid ""
2067"The GNUnet team is currently working on a transport layer rewrite in order "
2068"to fix core issues with connectivity. This new component is currently "
2069"developed under the name \"TNG\". What is currently known as \"transport "
2070"plugins\" will in the TNG be represented as \"communicators\". Communicators "
2071"are processes with a well defined API that allow to connect peers over a "
2072"specific protocol. The primary protocol which are already implemented are "
2073"UNIX sockets, UDP sockets, and TCP sockets. For a truly resilient network, "
2074"other connectivity options such as WiFi mesh, Bluetooth, HTTP(S), QUIC or "
2075"even more obscure alternatives such as radio are required. In this project, "
2076"the goal is to select, implement and test new communicators. While TNG is "
2077"not yet ready, communicators can, by design, be developed and tested against "
2078"the current API. We expect that this project can be worked on by multiple "
2079"students as there are a lot of protocols to choose from. The tasks would "
2080"consist of: <ol> <li>Deciding which communicators to implement.</li> "
2081"<li>Test the communicators.</li> <li>Documentation.</li> </ol> Advantageous "
2082"skills/languages/frameworks: <ol> <li>C</li> <li>Knowledge of HTTPS, QUIC, "
2083"Bluetooth or WiFi.</li> </ol> <br/> <strong>Difficulty:</strong> Average, "
2084"but depends on selected protocols. <br/> <strong>Mentors:</strong> Martin "
2085"Schanzenbach, t3sserakt"
2086msgstr ""
2087
2088#: template/gsoc.html.j2:79
2089msgid ""
2090"The REST API currently only supports a single user system. This is an issue "
2091"as on multi-user systems, access control must be enfoced on a per-user "
2092"basis. In this project, the REST service must be extended to support user "
2093"authentication. This includes the correct handling of user context switches. "
2094"<ol> <li>Implement user authentication.</li> <li>Test the access control.</"
2095"li> <li>Document the changes to the REST API.</li> </ol> Advantageous skills/"
2096"languages/frameworks: <ol> <li>C</li> <li>Knowledge of user authentication "
2097"subsystems on Linux/Unix.</li> <li>REST/HTTP Authentication methods</li> </"
2098"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
2099"strong> Martin Schanzenbach"
2100msgstr ""
2101
2102#: template/gsoc.html.j2:111
2103msgid ""
2104"reclaimID is a decentralized identity system build on top of the GNU Name "
2105"System. Currently, there is a Webextension which uses the GNUnet <a href="
2106"\"https://rest.gnunet.org\">REST API</a>. In order to improve adoption and "
2107"ease of use, this project aims to include a full GNUnet node within the "
2108"Webextention as a fallback. GNUnet can be compiled to Web Assembly or "
2109"JavaScript as demonstrated <a href=\"https://gnunet.io\">here</a>. The idea "
2110"is to improve upon this concept and support more of GNUnet's subsystems. The "
2111"difficulty of this project largely depends on the students proficiency with "
2112"build tools, emscripten and improvisation skills. There non-exhaustive task "
2113"list would be: <ol> <li>Improve existing GNUnet emscripten build to include "
2114"more subsystems.</li> <li>Integrate the result into a Webextention.</li> "
2115"<li>Integrate the result into the re:claimID Webextension</li> </ol> "
2116"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>emscripten</"
2117"li> <li>Webextensions</li> </ol> <br/> <strong>Difficulty:</strong> "
2118"Challenging <br/> <strong>Mentors:</strong> Martin Schanzenbach"
2119msgstr ""
2120
2121#: template/gsoc.html.j2:147
2122msgid ""
2123"Currently, the keys in our statistics database are too verbose. For example: "
2124"</p> <p> nse # flood messages received: 13<br/> nse # peers connected: 4<br/"
2125"> nse # nodes in the network (estimate): 203<br/> nse # flood messages "
2126"started: 5<br/> nse # estimated network diameter: 3<br/> nse # flood "
2127"messages transmitted: 10<br/> </p> <p> With such verbose keys there's no "
2128"easy way to form compact JSON document or entries for time-series database. "
2129"And you can't query single stats without having to copypaste the line "
2130"exactly and put in quotes. In short, the goals are to... <ol> <li>Think of a "
2131"way how statistics entries can be made canonical.</li> <li>Implement the "
2132"change and migrate existing uses.</li> <li>Document the format(s) and define "
2133"an appropriate registration mechanism for identifiers</li> </ol> Relevant "
2134"bugs: <a href=\"https://bugs.gnunet.org/view.php?id=5650\">#5650</a><br/> "
2135"Advantageous skills/languages/frameworks: <ol> <li>C</li> <li>HTML</li> </"
2136"ol> <br/> <strong>Difficulty:</strong> Beginner <br/> <strong>Mentors:</"
2137"strong> Martin Schanzenbach"
2138msgstr ""
2139
2140#: template/gsoc.html.j2:187
2141msgid ""
2142"The goal is to either build upon the (outdated) <a href=\"https://github.com/"
2143"canndrew/gnunet-rs\">GNUnet Rust bindings</a> or to follow the path of <a "
2144"href=\"GNUnet Go\">https://github.com/bfix/gnunet-go</a> which tries to "
2145"reimplement most of the GNUnet stack. The end result should be an extension "
2146"template for GNUnet in the form of the existing <a href=\"https://git.gnunet."
2147"org/gnunet-ext.git/\">C template</a> which allows to quickly start "
2148"implementing services and libraries for GNUnet."
2149msgstr ""
2150
2151#: template/gsoc.html.j2:198 template/gsoc.html.j2:652
2152msgid "<strong>Mentors:</strong> Martin Schanzenbach"
2153msgstr ""
2154
2155#: template/gsoc.html.j2:203
2156msgid "Required Skills: Solid knowledge of Rust and ideally asynchronuous IO."
2157msgstr ""
2158
2159#: template/gsoc.html.j2:208 template/gsoc.html.j2:321
2160#: template/gsoc.html.j2:531 template/gsoc.html.j2:662
2161msgid "Difficulty level: medium"
2162msgstr ""
2163
2164#: template/gsoc.html.j2:222
2165msgid ""
2166"It is time for GNUnet to run properly on Android. Note that GNUnet is "
2167"written in C, and this is not about rewriting GNUnet in Java, but about "
2168"getting the C code to run on Android."
2169msgstr ""
2170
2171#: template/gsoc.html.j2:229
2172msgid ""
2173"Includes: Implementation of rudimentary Android compatibility for GNUnet, in "
2174"part by porting the GNUnet utils scheduler to act as a thin wrapper over "
2175"libuv."
2176msgstr ""
2177
2178#: template/gsoc.html.j2:236
2179msgid ""
2180"<strong>Mentors:</strong> <a href=\"https://www.goebel-consult.de/\">Hartmut "
2181"Goebel</a>, Jeff Burdges, Christian Grothoff"
2182msgstr ""
2183
2184#: template/gsoc.html.j2:245
2185msgid ""
2186"There is a push for migrating our CI to Gitlab. The CI should eventually not "
2187"just run \"make check\" on various platforms, but also perform tests with "
2188"multiple peers running in different VMs with specific network topologies (i."
2189"e. NAT) between them being simulated. The CI should also be integrated with "
2190"Gauger for performance regression analysis. Running jobs only when "
2191"dependencies have changed and scripting more granular triggers or ideally "
2192"automatic dependency discovery (as done by the autotools) is also important."
2193msgstr ""
2194
2195#: template/gsoc.html.j2:257
2196msgid "<strong>Mentors:</strong> TBD"
2197msgstr ""
2198
2199#: template/gsoc.html.j2:267
2200msgid ""
2201"One great problem of the current Internet is the lack of disintermediation. "
2202"When people want to talk they need a chat service. When they want to share "
2203"files they need a file transfer service. Although GNUnet already possesses "
2204"quite advanced integration into Linux networking, a little extra work is "
2205"needed for existing applications like irc, www, ftp, rsh, nntpd to run over "
2206"it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. "
2207"Once people have added a person to their GNS they can immediately message, "
2208"exchange files and suchlike directly, with nothing but the GNUnet in the "
2209"middle, using applications that have been distributed with unix systems ever "
2210"since the 1980's. We can produce an OS distribution where these things work "
2211"out of the box with the nicknames of people instead of cloud services. For "
2212"more information and context, read"
2213msgstr ""
2214
2215#: template/gsoc.html.j2:288
2216msgid "<strong>Mentors:</strong> lynX &amp; dvn"
2217msgstr ""
2218
2219#: template/gsoc.html.j2:296
2220msgid ""
2221"Implement the AnycastExit spec to enable GNUnet clients to connect over Tor."
2222msgstr ""
2223
2224#: template/gsoc.html.j2:302 template/gsoc.html.j2:337
2225#: template/gsoc.html.j2:352
2226msgid "<strong>Mentors:</strong> Jeff Burdges"
2227msgstr ""
2228
2229#: template/gsoc.html.j2:307
2230msgid ""
2231"Note: There was a Special TLDs spec to allow Tor to resolve domain names "
2232"using GNS over Tor too, but currently that's on hold until folks think more "
2233"about how names should be moved around the local system. We're calling this "
2234"more collaborative approach NSS2 for now."
2235msgstr ""
2236
2237#: template/gsoc.html.j2:316 template/gsoc.html.j2:456
2238#: template/gsoc.html.j2:496 template/gsoc.html.j2:526
2239msgid "Required Skills: C"
2240msgstr ""
2241
2242#: template/gsoc.html.j2:329
2243msgid ""
2244"Improve the Rust implementation of GNUnet utils, possibly including adding "
2245"support for asynchronous IO using mio, or perhaps a higher level "
2246"asynchronous IO library built upon it, such as rotor, mioco, eventual_io, or "
2247"gj."
2248msgstr ""
2249
2250#: template/gsoc.html.j2:345
2251msgid ""
2252"Implementation of a replacement for PANDA (see Pond) with better security, "
2253"and maybe integration with the GNU Name System for key exchange."
2254msgstr ""
2255
2256#: template/gsoc.html.j2:357
2257msgid "Required Skills: Rust or C, crypto"
2258msgstr ""
2259
2260#: template/gsoc.html.j2:362 template/gsoc.html.j2:419
2261#: template/gsoc.html.j2:461 template/gsoc.html.j2:501
2262msgid "Difficulty level: high"
2263msgstr ""
2264
2265#: template/gsoc.html.j2:370
2266msgid ""
2267"Implement different place types and file sharing by creating a new place for "
2268"the shared content."
2269msgstr ""
2270
2271#: template/gsoc.html.j2:376
2272msgid "Place types to be implemented:"
2273msgstr ""
2274
2275#: template/gsoc.html.j2:380
2276msgid ""
2277"<ul> <li>File: generic file with comments</li> <li>Image: display an image "
2278"with comments referencing a region of the image</li> <li>Sound: play a sound "
2279"file with comments referencing a timestamp</li> <li>Directory/Album: "
2280"pointers to File / Image / Sound places</li> <li>Event: with RSVP</li> "
2281"<li>Survey: ask your social neighborhood questions in a structured form</li> "
2282"</ul>"
2283msgstr ""
2284
2285#: template/gsoc.html.j2:391
2286msgid "Also provide the following UI functionality:"
2287msgstr ""
2288
2289#: template/gsoc.html.j2:395
2290msgid ""
2291"<ul> <li>Fork existing channels, reorganize people into new chatrooms or "
2292"channels.</li> <li>Share a post (edit and repost something elsewhere, on a "
2293"fan page for example).</li> <li>Edit a previously published post + offer "
2294"edit history to readers.</li> <li>Control expiry of channel history.</li> </"
2295"ul>"
2296msgstr ""
2297
2298#: template/gsoc.html.j2:404
2299msgid ""
2300"See also <a href=\"http://secushare.org/features\">http://secushare.org/"
2301"features</a>"
2302msgstr ""
2303
2304#: template/gsoc.html.j2:409
2305msgid "<strong>Mentors:</strong> lynX"
2306msgstr ""
2307
2308#: template/gsoc.html.j2:414
2309msgid "Required Skills: C/C++"
2310msgstr ""
2311
2312#: template/gsoc.html.j2:427
2313msgid ""
2314"Implement aggregation of distributed state from various channels in order to "
2315"provide for a powerful social graph API capable of producing social network "
2316"profiles, dashboards, a calendar out of upcoming event invitations (if "
2317"available), social search functionality and most of all to make it easy for "
2318"users to adopt cryptographic identities of their contacts/friends simply by "
2319"finding them in the social graph of their existing contacts (\"This is "
2320"Linda. You have 11 contacts in common with her. [ADD]\")."
2321msgstr ""
2322
2323#: template/gsoc.html.j2:445
2324msgid ""
2325"Related to <a href=\"http://secushare.org/rendezvous\">secushare.org/"
2326"rendezvous</a>"
2327msgstr ""
2328
2329#: template/gsoc.html.j2:451 template/gsoc.html.j2:491
2330msgid "<strong>Mentors:</strong> t3sserakt, lynX"
2331msgstr ""
2332
2333#: template/gsoc.html.j2:468
2334msgid ""
2335"<ul> <li> Emulate IMAP/SMTP protocols as necessary to transform traditional "
2336"mail clients into secushare user interfaces. </li> <li> Think of ways to map "
2337"e-mail addresses to secushare identities. </li> <li> Encode or translate "
2338"various e-mail features into secushare equivalents. </li> <li> Parts of "
2339"secushare are currently written in Rust, therefore Rust is preferred for "
2340"this task but it is not an requirement. </li> </ul>"
2341msgstr ""
2342
2343#: template/gsoc.html.j2:509
2344msgid ""
2345"Implementation of the GNUnet auction system described in Chapter 3 of <a "
2346"href=\"https://grothoff.org/christian/teich2017ms.pdf\">this thesis</a>. "
2347"Specific tasks are adding smart contract creation and round time enforcement "
2348"to libbrandt as well as creating the GNUnet auction service, library and the "
2349"three user interface programs create, info and join."
2350msgstr ""
2351
2352#: template/gsoc.html.j2:521
2353msgid "<strong>Mentors:</strong> mate, cg"
2354msgstr ""
2355
2356#: template/gsoc.html.j2:539
2357msgid ""
2358"Implementation of additional transports to make GNUnet communication more "
2359"robust in the presence of problematic networks: GNUnet-over-SMTP, GNUnet-"
2360"over-DNS"
2361msgstr ""
2362
2363#: template/gsoc.html.j2:546 template/gsoc.html.j2:560
2364msgid "<strong>Mentors:</strong> Matthias Wachs"
2365msgstr ""
2366
2367#: template/gsoc.html.j2:554
2368msgid ""
2369"Implementation of ALG-based NAT traversal methods (FTP/SIP-based hole "
2370"punching, better STUN support)"
2371msgstr ""
2372
2373#: template/gsoc.html.j2:568
2374msgid ""
2375"<strong>Mentors:</strong> Matthias Wachs, Christian Grothoff, Jeff Burdges"
2376msgstr ""
2377
2378#: template/gsoc.html.j2:576
2379msgid ""
2380"Improving libaboss to make computation on shared secrets (including repeated "
2381"multiplication) based on <a href=\"https://dl.acm.org/citation.cfm?"
2382"doid=62212.62213\">Ben-Or et al.</a> if possible. This in particular means "
2383"moving libaboss to bignums (gcry_mpi)."
2384msgstr ""
2385
2386#: template/gsoc.html.j2:589
2387msgid ""
2388"Please refer to the description for this project listed under GNU Guix "
2389"project ideas."
2390msgstr ""
2391
2392#: template/gsoc.html.j2:602
2393msgid ""
2394"Python 2.7 is reaching its end-of-life, and we want to get rid of the "
2395"dependency on Python. The existing gnunet-qr tool is a rather simple wrapper "
2396"around python-zbar, which itself wraps libzbar. The goal of this project is "
2397"to directly use libzbar to scan QR codes for GNUnet / the GNU Name System "
2398"(see also <a href=\"https://bugs.gnunet.org/view.php?id=5562\">#5562</a>)."
2399msgstr ""
2400
2401#: template/gsoc.html.j2:612
2402msgid "<strong>Mentors:</strong> Christian Grothoff"
2403msgstr ""
2404
2405#: template/gsoc.html.j2:617
2406msgid "Required Skills:"
2407msgstr ""
2408
2409#: template/gsoc.html.j2:622
2410msgid "Difficulty level:"
2411msgstr ""
2412
2413#: template/gsoc.html.j2:627
2414msgid "Report:"
2415msgstr ""
2416
2417#: template/gsoc.html.j2:632
2418msgid "Unfinished/Abandoned as gnunet-qr was moved to C outside of GSoC."
2419msgstr ""
2420
2421#: template/gsoc.html.j2:642
2422msgid ""
2423"Implementation of a Web-based UI for GNUnet similar to GNUnet-Gtk with a yet "
2424"to be determined framework such as Angular2. This includes the design and "
2425"implementation of not yet existing <a href=\"http://jsonapi.org/\">REST "
2426"APIs</a> that expose the <a href=\"https://docs.gnunet.org/doxygen/modules."
2427"html\">GNUnet API</a>."
2428msgstr ""
2429
2430#: template/gsoc.html.j2:657
2431msgid "Required Skills: C, JavaScript, CSS"
2432msgstr ""
2433
2434#: template/gsoc.html.j2:667
2435msgid ""
2436"Report: <a href=\"gsoc-2018-gnunet-webui.html\">GSoC 2018: GNUnet WebUI</a>"
2437msgstr ""
2438
2439#: template/index.html.j2:8
2440msgid "The Internet of tomorrow needs GNUnet today"
2441msgstr ""
2442
2443#: template/index.html.j2:26
2444msgid "Latest news"
2445msgstr ""
2446
2447#: template/index.html.j2:32
2448msgid "Older news entries"
2449msgstr ""
2450
2451#: template/index.html.j2:47
2452msgid "The Internet is broken"
2453msgstr ""
2454
2455#: template/index.html.j2:49
2456msgid ""
2457"The conventional Internet is currently like a system of roads with deep "
2458"potholes and highwaymen all over the place. Even if you still can use the "
2459"roads (e.g. send emails, or browse websites) your vehicle might get "
2460"hijacked, damaged, or long arms might reach into its back and steal your "
2461"items (data) to use it against you and sell it to others - while you can&#39;"
2462"t even notice the thievery nor accuse and hold the scroungers accountable. "
2463"<!-- Proposal from Fabian Gerlach: The conventional Internet is currently "
2464"like a system of roads with deep potholes and surveillance cameras all over "
2465"the place. Even if you still can use the roads (e.g. send emails, or browse "
2466"websites) your vehicle might gets damaged. And the surveillance cameras will "
2467"create a movement profile about your life: They recognize your car license "
2468"plate, track you everywhere you drive, and save this information in a "
2469"central data base. --> The Internet was not designed with security in mind: "
2470"protecting against address forgery, routers learning metadata, or choosing "
2471"trustworthy third parties is nontrivial and sometimes impossible. <!-- "
2472"Proposal from Fabian Gerlach: The Internet is not designed with security in "
2473"mind: The network generally learns too much about users; it has insecure "
2474"defaults and high complexity; and it is centralized. That makes it very "
2475"vulnerable for multiple attacks massively threatening our freedom. -->"
2476msgstr ""
2477
2478#: template/index.html.j2:94
2479msgid "GNUnet helps building a new Internet"
2480msgstr ""
2481
2482#: template/index.html.j2:96
2483msgid ""
2484"GNUnet is a network protocol stack for building secure, distributed, and "
2485"privacy-preserving applications.<br/> With strong roots in <a class=\"link\" "
2486"href=\"https://bib.gnunet.org\">academic research</a>, our goal is to "
2487"replace the <a class=\"link\" href=\"https://secushare.org/broken-internet"
2488"\">old insecure Internet</a> protocol stack."
2489msgstr ""
2490
2491#: template/index.html.j2:119
2492msgid "Metadata is exposed"
2493msgstr ""
2494
2495#: template/index.html.j2:121
2496msgid ""
2497"Your metadata is just as revealing as the actual content; and it gets "
2498"exposed on the Internet.<br> Even though transport encryption is "
2499"increasingly being deployed on the Internet, it still reveals data that can "
2500"threaten democracy: the identities of senders and receivers, the times, "
2501"frequency and the volume of communication are all still revealed.<br>"
2502msgstr ""
2503
2504#: template/index.html.j2:150
2505msgid "GNUnet provides privacy-by design"
2506msgstr ""
2507
2508#: template/index.html.j2:152
2509msgid ""
2510"It provides <a class=\"link\" href=\"https://www.w3.org/2014/strint/"
2511"papers/65.pdf\"> improving addressing, routing, naming and content "
2512"distribution</a> in a technically robust manner - as opposed to ad-hoc "
2513"designs in place today. <!-- Proposal from fabian gerlach: GNUnet is built "
2514"<a href=\"https://www.w3.org/2014/strint/papers/65.pdf\">\"privacy by design"
2515"\"</a> and \"distributed by design\". This improves addressing, routing, "
2516"naming and content distribution in a technically robust manner. -->"
2517msgstr ""
2518
2519#: template/index.html.j2:177
2520msgid "Freedoms are not respected"
2521msgstr ""
2522
2523#: template/index.html.j2:179
2524msgid ""
2525"Today, monitoring increasingly centralized infrastructure, proprietary "
2526"implementations, traffic shapers and firewalls restrict all of the <a class="
2527"\"link\" href=\"https://www.gnu.org/philosophy/free-sw.html\">essential "
2528"freedoms</a> to various degrees."
2529msgstr ""
2530
2531#: template/index.html.j2:203
2532msgid "GNUnet supports a free and open society"
2533msgstr ""
2534
2535#: template/index.html.j2:205
2536msgid ""
2537"GNUnet is a self-organizing network and it is <a class=\"link\" href="
2538"\"https://www.gnu.org/philosophy/free-sw.html\">free software</a> as in "
2539"freedom. GNUnet puts you in control of your data. You determine which data "
2540"to share with whom, and you&#39;re not pressured to accept compromises. It "
2541"gives users freedoms to securely access information (\"run\" the network), "
2542"to study all aspects of the network&#39;s operation (\"access the code\"), "
2543"to distribute information (\"copy\"), as well as the freedom to deploy new "
2544"applications (\"modify\")."
2545msgstr ""
2546
2547#: template/index.html.j2:229
2548msgid "Decentralization is the key, but hard"
2549msgstr ""
2550
2551#: template/index.html.j2:232
2552msgid ""
2553"<!-- replaced with Proposal from Fabian Gerlach: It seems as if every other "
2554"distributed or P2P project develops its own library stack, covering "
2555"transports, stream muxing, discovery and others. This divides effort and "
2556"multiplies bug count. --> Instead of sharing common components and tools for "
2557"building P2P systems, every P2P project seems to re-invent the wheel. <!-- "
2558"TODO: rework this sentence. --> This heightens the effort and increases the "
2559"potential number of vulnerabilities."
2560msgstr ""
2561
2562#: template/index.html.j2:264
2563msgid "GNUnet is a framework"
2564msgstr ""
2565
2566#: template/index.html.j2:266
2567msgid ""
2568"It offers a metadata-preserving foundation for your application. It offers "
2569"components for addressing, reliable encrypted channels with advanced routing "
2570"and resource discovery and naming. Our work is based on continuous research "
2571"spanning almost two decades."
2572msgstr ""
2573
2574#: template/index.html.j2:286
2575#, fuzzy
2576#| msgid "read more"
2577msgid "Learn more"
2578msgstr "और पड़े"
2579
2580#: template/index.html.j2:295
2581msgid "Get started"
2582msgstr ""
2583
2584#: template/install-on-archpi.html.j2:6
2585msgid "Tutorial: GNUnet on Arch Linux/Pi"
2586msgstr ""
2587
2588#: template/install-on-archpi.html.j2:16
2589msgid "Requirements for Raspberry Pi 3"
2590msgstr ""
2591
2592#: template/install-on-archpi.html.j2:40
2593#, fuzzy
2594#| msgid "Source Code"
2595msgid "Get the Source Code"
2596msgstr "सूत्र संहिता"
2597
2598#: template/install-on-archpi.html.j2:62
2599#: template/install-on-debian9.html.j2:131
2600msgid "In Addition: gnunet-gtk"
2601msgstr ""
2602
2603#: template/install-on-archpi.html.j2:81
2604msgid "Run"
2605msgstr ""
2606
2607#: template/install-on-archpi.html.j2:133
2608#: template/install-on-openwrt.html.j2:111
2609msgid "Make sure, it works!"
2610msgstr ""
2611
2612#: template/install-on-debian9.html.j2:6
2613msgid "Tutorial: GNUnet on Debian 9"
2614msgstr ""
2615
2616#: template/install-on-debian9.html.j2:9
2617#: template/install-on-ubuntu1804.html.j2:9
2618msgid "Introduction"
2619msgstr ""
2620
2621#: template/install-on-debian9.html.j2:29 template/install-on-macos.html.j2:17
2622#: template/install-on-netbsd.html.j2:19
2623#: template/install-on-ubuntu1804.html.j2:26
2624msgid "Requirements"
2625msgstr ""
2626
2627#: template/install-on-debian9.html.j2:46
2628#: template/install-on-ubuntu1804.html.j2:41
2629msgid "Make an installation directory"
2630msgstr ""
2631
2632#: template/install-on-debian9.html.j2:60 template/install-on-macos.html.j2:134
2633#: template/install-on-netbsd.html.j2:237
2634#: template/install-on-ubuntu1804.html.j2:53
2635#, fuzzy
2636#| msgid "Source Code"
2637msgid "Get the source code"
2638msgstr "सूत्र संहिता"
2639
2640#: template/install-on-debian9.html.j2:79 template/install-on-macos.html.j2:142
2641#: template/install-on-netbsd.html.j2:245
2642#: template/install-on-ubuntu1804.html.j2:61
2643msgid "Compile and Install"
2644msgstr ""
2645
2646#: template/install-on-debian9.html.j2:104
2647#: template/install-on-ubuntu1804.html.j2:70
2648msgid "Option 1: GNUnet for testing / usage"
2649msgstr ""
2650
2651#: template/install-on-debian9.html.j2:117
2652#: template/install-on-ubuntu1804.html.j2:82
2653msgid "Option 2: GNUnet for development"
2654msgstr ""
2655
2656#: template/install-on-debian9.html.j2:154
2657#: template/install-on-ubuntu1804.html.j2:97
2658msgid "Install GNUnet plugin for name resolution"
2659msgstr ""
2660
2661#: template/install-on-debian9.html.j2:208
2662#: template/install-on-ubuntu1804.html.j2:134
2663msgid "Create configuration file"
2664msgstr ""
2665
2666#: template/install-on-debian9.html.j2:228
2667#: template/install-on-ubuntu1804.html.j2:156
2668#, fuzzy
2669#| msgid "GNUnet"
2670msgid "Use GNUnet!"
2671msgstr "कम्प्यूटिंग नेट"
2672
2673#: template/install-on-debian9.html.j2:233
2674#: template/install-on-ubuntu1804.html.j2:162
2675msgid "Uninstall GNUnet and its dependencies"
2676msgstr ""
2677
2678#: template/install-on-macos.html.j2:6
2679msgid "Tutorial: GNUnet on macOS 10.14 (Mojave)"
2680msgstr ""
2681
2682#: template/install-on-macos.html.j2:24 template/install-on-netbsd.html.j2:36
2683#: template/install-on-openwrt.html.j2:15
2684#, fuzzy
2685#| msgid "Install"
2686msgid "Installation"
2687msgstr "स्थापित"
2688
2689#: template/install-on-macos.html.j2:42 template/install-on-netbsd.html.j2:115
2690msgid "First steps"
2691msgstr ""
2692
2693#: template/install-on-macos.html.j2:109 template/install-on-netbsd.html.j2:195
2694msgid "Alternative: Installation from source"
2695msgstr ""
2696
2697#: template/install-on-macos.html.j2:154 template/install-on-netbsd.html.j2:265
2698msgid "Option 1: GNUnet for production / usage"
2699msgstr ""
2700
2701#: template/install-on-macos.html.j2:187 template/install-on-netbsd.html.j2:293
2702msgid "Option 2: GNUnet experimental"
2703msgstr ""
2704
2705#: template/install-on-netbsd.html.j2:6
2706msgid "Tutorial: GNUnet on NetBSD 8.0 CURRENT"
2707msgstr ""
2708
2709#: template/install-on-openwrt.html.j2:6
2710msgid "Tutorial: GNUnet on OpenWrt"
2711msgstr ""
2712
2713#: template/install-on-openwrt.html.j2:47
2714#, fuzzy
2715#| msgid "Continuous Integration"
2716msgid "Configuration"
2717msgstr "लगातार एकीकरण"
2718
2719#: template/install-on-ubuntu1804.html.j2:6
2720msgid "Tutorial: GNUnet on Ubuntu 18.04"
2721msgstr ""
2722
2723#: template/install.html.j2:11
2724msgid ""
2725"Notice: GNUnet is still undergoing major development. It is largely <i>not "
2726"yet ready</i> for usage beyond developers."
2727msgstr ""
2728
2729#: template/install.html.j2:16
2730msgid ""
2731"<p>Please be aware that this project is still in an early alpha stage when "
2732"it comes to running software &#8211; its not an easy task to rewrite the "
2733"whole Internet! We are happy to get your <a href=\"engage.html\">helping "
2734"hand</a> anytime! Further information is available in our <a href=\"https://"
2735"docs.gnunet.org/#toc-Using-GNUnet-1\">handbook</a>. If you have any queries "
2736"about the installation or the usage, please <a href=\"engage.html\">get in "
2737"touch!</a></p>"
2738msgstr ""
2739
2740#: template/install.html.j2:28
2741msgid ""
2742"We recommend to use binary packages provided by the package manager "
2743"integrated within your Operating System. GNUnet is reportedly available for "
2744"at least: <ul> <li><a href=\"https://pkgs.alpinelinux.org/package/edge/"
2745"testing/x86_64/gnunet\">Alpine</a></li> <li><a href=\"https://www.archlinux."
2746"org/packages/community/x86_64/gnunet/\">Arch</a></li> <li><a href=\"https://"
2747"packages.debian.org/search?keywords=gnunet\">Debian</a></li> <li><a href="
2748"\"https://copr.fedorainfracloud.org/coprs/yosl/gnunet/\">Fedora (Copr)</a></"
2749"li> <li><a href=\"https://guix.gnu.org/en/packages/G/\">Guix</a></li> <li><a "
2750"href=\"https://github.com/Homebrew/homebrew-core/blob/master/Formula/gnunet."
2751"rb\">Homebrew</a></li> <li><a href=\"https://nixos.org/nixos/packages.html?"
2752"attr=gnunet&channel=nixpkgs-unstable&query=gnunet\">NixOS</a></li> <li><a "
2753"href=\"install-on-openwrt.html\">OpenWrt</a></li> </ul> If GNUnet is "
2754"available for your Operating System and it is missing, send us feedback so "
2755"that we can add it to this list. Furthermore, if you are interested in "
2756"packaging GNUnet for your Operating System, get in touch with us at gnunet-"
2757"developers@gnu.org if you require help with this job. If you were using an "
2758"Operating System with the APT package manager, GNUnet could be installed as "
2759"simple as:"
2760msgstr ""
2761
2762#: template/install.html.j2:59
2763msgid ""
2764"Next we describe a generic way to install from source. If you are using one "
2765"of the following Operating Systems these step-by-step guides might be "
2766"useful: <a href=\"install-on-archpi.html\">ArchPi</a>, <a href=\"install-on-"
2767"debian9.html\">Debian 9</a>, <a href=\"install-on-macos.html\">Mac OS</a>, "
2768"<a href=\"install-on-netbsd.html\">NetBSD</a>, <a href=\"install-on-"
2769"ubuntu1804.html\">Ubuntu 1804</a>. Be aware that not all of them might be "
2770"totally up-to-date! Please <a href=\"engage.html\">ask us</a> if you get "
2771"stuck."
2772msgstr ""
2773
2774#: template/install.html.j2:73
2775msgid ""
2776"First, install the <a href=\"https://git.gnunet.org/gnunet.git/tree/README"
2777"\">required dependencies</a> of GNUnet. There are base requirements and "
2778"optional requirements."
2779msgstr ""
2780
2781#: template/install.html.j2:79
2782msgid ""
2783"Now, you need to decide if you want to install GNUnet from the release "
2784"tarball or from git. If you want to use GNUnet and there is no binary "
2785"package available for your OS, you should stick with the release tarball. If "
2786"you want to develop using the most recent build, you should go with the <a "
2787"href=\"https://git.gnunet.org/\">git repository</a>."
2788msgstr ""
2789
2790#: template/install.html.j2:96
2791msgid "To compile gnunet from the git source you can do so by entering:"
2792msgstr ""
2793
2794#: template/install.html.j2:104
2795msgid ""
2796"Before building GNUnet, make sure that you setup the required groups and add "
2797"your user to the group <code>gnunet</code>:"
2798msgstr ""
2799
2800#: template/install.html.j2:115
2801msgid "To compile GNUnet, execute:"
2802msgstr ""
2803
2804#: template/install.html.j2:126
2805msgid ""
2806"You can find more configuration flags in the <a href=\"https://git.gnunet."
2807"org/gnunet.git/tree/README\">README</a>.<br> Install GNUnet with:"
2808msgstr ""
2809
2810#: template/install.html.j2:136
2811msgid "You can now start GNUnet by running:"
2812msgstr ""
2813
2814#: template/install.html.j2:144
2815msgid ""
2816"Check the <a href=\"https://docs.gnunet.org/handbook/gnunet.html#Minimal-"
2817"configuration\">handbook</a> for detailed documentation. For a more hands-on "
2818"experience, <a href=\"https://gnunet.org/en/use.html\">continue here</a>."
2819msgstr ""
2820
2821#: template/livingstandards.html.j2:11
2822msgid "On this page you can find links to our technical specifications."
2823msgstr ""
2824
2825#: template/use.html.j2:6
2826msgid "How to use GNUnet - in a nutshell"
2827msgstr ""
2828
2829#: template/use.html.j2:12 template/use.html.j2:125
2830msgid "Filesharing"
2831msgstr ""
2832
2833#: template/use.html.j2:13
2834msgid "CADET"
2835msgstr ""
2836
2837#: template/use.html.j2:14
2838msgid "Minimal Groupchat"
2839msgstr ""
2840
2841#: template/use.html.j2:15
2842msgid "GNS with CLI"
2843msgstr ""
2844
2845#: template/use.html.j2:16
2846msgid "GNS with Browser"
2847msgstr ""
2848
2849#: template/use.html.j2:17 template/use.html.j2:448
2850msgid "VPN"
2851msgstr ""
2852
2853#: template/use.html.j2:18 template/use.html.j2:508
2854msgid "Conversation"
2855msgstr ""
2856
2857#: template/use.html.j2:19 template/use.html.j2:519
2858msgid "Trouble Shooting"
2859msgstr ""
2860
2861#: template/use.html.j2:34
2862msgid "Accessing GNUnet"
2863msgstr ""
2864
2865#: template/use.html.j2:78
2866#, fuzzy
2867#| msgid "What is GNUnet?"
2868msgid "Leaving GNUnet"
2869msgstr "क्या हे जी॰ एन॰यू॰ नेट?"
2870
2871#: template/use.html.j2:88
2872msgid "Make sure your GNUnet installation works..."
2873msgstr ""
2874
2875#: template/use.html.j2:107
2876msgid "... and play around with it."
2877msgstr ""
2878
2879#: template/use.html.j2:179
2880msgid "CADET (and Chat)"
2881msgstr ""
2882
2883#: template/use.html.j2:219
2884msgid "Chatting with a (simple) client"
2885msgstr ""
2886
2887#: template/use.html.j2:283
2888msgid "Name resolution using GNS on the command line"
2889msgstr ""
2890
2891#: template/use.html.j2:360
2892msgid "Name resolution using GNS with a browser"
2893msgstr ""
2894
2895#: template/use.html.j2:521
2896msgid "You can't reach other people's nodes"
2897msgstr ""
2898
2899#: template/use.html.j2:557
2900msgid "OMG you guys broke my internet"
2901msgstr ""
2902
2903#: template/video.html.j2:12
2904msgid "Videos related to GNUnet"
2905msgstr ""
2906
2907#: template/news/index.html.j2:45
2908msgid "News archives:"
2909msgstr "समाचार पुरालेख:"
2910
2911#: template/reclaim/faq.html.j2:6
2912msgid "Frequently asked questions"
2913msgstr ""
2914
2915#: template/reclaim/idps.html.j2:6 template/reclaim/index.html.j2:95
2916msgid "For IdPs"
2917msgstr ""
2918
2919#: template/reclaim/index.html.j2:8
2920msgid ""
2921"Self-sovereign, Decentralised Identity Management and Personal Data Sharing"
2922msgstr ""
2923
2924#: template/reclaim/index.html.j2:18
2925msgid "Self-sovereign"
2926msgstr ""
2927
2928#: template/reclaim/index.html.j2:20
2929msgid ""
2930"You manage your identities and attributes locally on your computer. No need "
2931"to trust a third party service with your data."
2932msgstr ""
2933
2934#: template/reclaim/index.html.j2:40
2935msgid "Decentralized"
2936msgstr ""
2937
2938#: template/reclaim/index.html.j2:42
2939msgid ""
2940"You can share your identity attributes securely over a decentralized name "
2941"system. This allows your friends to access your shared data without the need "
2942"of a trusted third party."
2943msgstr ""
2944
2945#: template/reclaim/index.html.j2:58
2946msgid "Standard-compliant"
2947msgstr ""
2948
2949#: template/reclaim/index.html.j2:60
2950msgid "You can use OpenID Connect to integrate reclaim in your web sites."
2951msgstr ""
2952
2953#: template/reclaim/index.html.j2:77
2954msgid "Technology"
2955msgstr ""
2956
2957#: template/reclaim/index.html.j2:89 template/reclaim/users.html.j2:6
2958msgid "For users"
2959msgstr ""
2960
2961#: template/reclaim/index.html.j2:92 template/reclaim/websites.html.j2:6
2962msgid "For websites"
2963msgstr ""
2964
2965#: template/reclaim/tech.html.j2:15
2966msgid "Decentralised identity directory"
2967msgstr ""
2968
2969#: template/reclaim/tech.html.j2:18
2970msgid ""
2971"The decentralised GNU Name System (GNS) gives users full and exclusive "
2972"authority over their attributes by sharing them over user-owned namespaces."
2973msgstr ""
2974
2975#: template/reclaim/tech.html.j2:26
2976msgid "Cryptographic access control"
2977msgstr ""
2978
2979#: template/reclaim/tech.html.j2:30
2980msgid ""
2981"Users regularly publish fresh, up-to-date attributes which can be retrieved "
2982"and read only by authorized relying parties parties without direct user "
2983"interaction -- even if the user is offline!"
2984msgstr ""
2985
2986#: template/reclaim/tech.html.j2:39
2987msgid "Principles"
2988msgstr ""
2989
2990#: template/reclaim/tech.html.j2:46
2991msgid "Identity and attribute management"
2992msgstr ""
2993
2994#: template/reclaim/tech.html.j2:48
2995msgid ""
2996"Users regularly publish fresh, up-to-date attributes which can be retrieved "
2997"by requesting parties without direct user interaction -- even if the user is "
2998"offline! Access to attributes is controlled through an ecryption based "
2999"access control layer."
3000msgstr ""
3001
3002#: template/reclaim/tech.html.j2:71
3003#, fuzzy
3004#| msgid "Documentation"
3005msgid "Authorization"
3006msgstr "प्रलेखन"
3007
3008#: template/reclaim/tech.html.j2:73
3009msgid ""
3010"To access attributes, requesting parties request authorization from the user "
3011"thrugh the use of OpenID Connect. If access is granted, the relying party is "
3012"given the necessary decryption key material. The user may at any time revoke "
3013"this access or modify the authorization decision."
3014msgstr ""
3015
3016#: template/reclaim/tech.html.j2:92
3017msgid "Attribute retrieval"
3018msgstr ""
3019
3020#: template/reclaim/tech.html.j2:94
3021msgid ""
3022"Relying parties retrieve encrypted identity data from the decentralised "
3023"directory. It is able to decrypt all those attributes that the user has "
3024"authorized it to access using the respective key."
3025msgstr ""
3026
3027#~ msgid "Living Standards"
3028#~ msgstr "जीवन स्तर"