aboutsummaryrefslogtreecommitdiff
path: root/template/glossary.html.j2
diff options
context:
space:
mode:
authorxrs <xrs@mail36.net>2019-06-29 14:58:43 +0200
committerxrs <xrs@mail36.net>2019-06-29 14:58:43 +0200
commit229be65913beba1d2b2be953eee3b4d814c3aa55 (patch)
tree2af8bbe642cb7ff207f7ab20175b2d3808b10a08 /template/glossary.html.j2
parentbc49d0ac82746f75ab1c90d17e54c00460a55008 (diff)
downloadwww-229be65913beba1d2b2be953eee3b4d814c3aa55.tar.gz
www-229be65913beba1d2b2be953eee3b4d814c3aa55.zip
glossary.html, video.html: fix layout
Diffstat (limited to 'template/glossary.html.j2')
-rw-r--r--template/glossary.html.j2205
1 files changed, 108 insertions, 97 deletions
diff --git a/template/glossary.html.j2 b/template/glossary.html.j2
index d8f6c0e5..9af47d57 100644
--- a/template/glossary.html.j2
+++ b/template/glossary.html.j2
@@ -1,101 +1,112 @@
1{% extends "common/base.j2" %} 1{% extends "common/base.j2" %}
2{% block body_content %} 2{% block body_content %}
3<div class="container"> 3<div class="container text-center">
4<dl> 4 <header>
5<dt>{{ _("Ego") }}</dt> 5 <h1>{{ _("Glossary") }}</h1>
6 <dd> 6 </header>
7 {% trans %}
8 We use the term "Ego" to refer to the fact that users in GNUnet
9 can have multiple unlinkable identities, in the sense of alter egos.
10 The ability to have more than one identity is crucial, as we may
11 want to keep our egos for business separate from those we use
12 for political activities or romance.<br>
13 Egos in GNUnet are technically
14 equivalent to identities (and the code does not distinguish
15 between them). We simply sometimes use the term "ego" to stress
16 that you can have more than one.
17 {% endtrans %}
18 </dd>
19</dt>
20<dt>{{ _("Identity") }}</dt>
21 <dd>
22 {% trans %}
23 In GNUnet users are identified via a public key, and that public
24 key is then often referred to as the "Identity" of the user.
25 However, the concept is not as draconian as it often is in real
26 life where many are forced to have one name, one passport and
27 one unique identification number.
28 <br>
29 As long as identities in GNUnet are simply
30 public keys, users are free to create any number of identities,
31 and we call those egos to emphasize the difference. Even though
32 users can create such egos freely, it is possible to have
33 an ego certified by some certification authority, resulting
34 in something that more closely resembles the traditional concept
35 of an identity.<br>
36 For example, a university may certify the identities of its students
37 such that they can prove that they are studying. Students may
38 keep their (certified) student identity separate from other egos
39 that they use for other activities in life.
40 {% endtrans %}
41 </dd>
42</dt>
43<dt>{{ _("Pseudonym") }}</dt>
44 <dd>
45 {% trans %}
46 A pseudonym is an ego that is specifically intended
47 to not be linked to one's real name. GNUnet users can create
48 many egos, and thus also many pseudonyms.
49 <br>
50 Repeated uses of
51 the same pseudonym are linkable by definition, as they involve
52 the same public key. Anonymity requires the use of either the
53 special "anonymous" pseudonym (for GNUnet, this is the neutral
54 element on the elliptic curve) or a throw-away pseudonym that
55 is only used once.
56 {% endtrans %}
57 </dd>
58</dt>
59<dt>{{ _("Namespaces") }}</dt>
60 <dd>
61 {% trans %}
62 The GNU Name System allows every ego (or identity) to
63 securely and privately associate any number of label-value pairs
64 with an ego. The values are called record sets following the
65 terminology of the Domain Name System (DNS). The mapping of
66 labels to record sets for a given ego is called a namespace.
67 <br>
68 If records are made public and thus published, it is possible
69 for other users to lookup the record given the ego's public key
70 and the label. Here, not only the label can thus act as a
71 passphrase but also the public key -- which despite its name
72 may not be public knowledge and is never disclosed by the GNS
73 protocol itself.
74 {% endtrans %}
75 </dd>
76</dt>
77<dt>{{ _("Peer") }}</dt>
78 <dd>
79 {% trans %}
80 A "peer" is an instance of GNUnet with its own per-instance
81 public key and network addresses. Technically, it is possible
82 to run multiple peers on the same host, but this only makes
83 sense for testing.
84 <br>
85 By design GNUnet supports multiple
86 users to share the same peer, just as UNIX is a multi-user
87 system. A "peer" typically consists of a set of foundational GNUnet
88 services running as the "gnunet" user and allowing all users
89 in the "gnunet" group to utilize the API. On multi-user
90 systems, additional "personalized" services may be required
91 per user.
92 <br>
93 While peers are also identified by public keys, these
94 public keys are completely unrelated to egos or
95 identities. Namespaces cannot be associated with a
96 peer, only with egos.
97 {% endtrans %}
98 </dd>
99</dt>
100</div> 7</div>
8<div class="container">
9 <div class="row">
10 <div class="col">
11 <dl>
12 <dt>{{ _("Ego") }}</dt>
13 <dd>
14 {% trans %}
15 We use the term "Ego" to refer to the fact that users in GNUnet
16 can have multiple unlinkable identities, in the sense of alter egos.
17 The ability to have more than one identity is crucial, as we may
18 want to keep our egos for business separate from those we use
19 for political activities or romance.<br>
20 Egos in GNUnet are technically
21 equivalent to identities (and the code does not distinguish
22 between them). We simply sometimes use the term "ego" to stress
23 that you can have more than one.
24 {% endtrans %}
25 </dd>
26 </dt>
27 <dt>{{ _("Identity") }}</dt>
28 <dd>
29 {% trans %}
30 In GNUnet users are identified via a public key, and that public
31 key is then often referred to as the "Identity" of the user.
32 However, the concept is not as draconian as it often is in real
33 life where many are forced to have one name, one passport and
34 one unique identification number.
35 <br>
36 As long as identities in GNUnet are simply
37 public keys, users are free to create any number of identities,
38 and we call those egos to emphasize the difference. Even though
39 users can create such egos freely, it is possible to have
40 an ego certified by some certification authority, resulting
41 in something that more closely resembles the traditional concept
42 of an identity.<br>
43 For example, a university may certify the identities of its students
44 such that they can prove that they are studying. Students may
45 keep their (certified) student identity separate from other egos
46 that they use for other activities in life.
47 {% endtrans %}
48 </dd>
49 </dt>
50 <dt>{{ _("Pseudonym") }}</dt>
51 <dd>
52 {% trans %}
53 A pseudonym is an ego that is specifically intended
54 to not be linked to one's real name. GNUnet users can create
55 many egos, and thus also many pseudonyms.
56 <br>
57 Repeated uses of
58 the same pseudonym are linkable by definition, as they involve
59 the same public key. Anonymity requires the use of either the
60 special "anonymous" pseudonym (for GNUnet, this is the neutral
61 element on the elliptic curve) or a throw-away pseudonym that
62 is only used once.
63 {% endtrans %}
64 </dd>
65 </dt>
66 </div>
67 <div class="col-lg-6">
68 <dt>{{ _("Namespaces") }}</dt>
69 <dd>
70 {% trans %}
71 The GNU Name System allows every ego (or identity) to
72 securely and privately associate any number of label-value pairs
73 with an ego. The values are called record sets following the
74 terminology of the Domain Name System (DNS). The mapping of
75 labels to record sets for a given ego is called a namespace.
76 <br>
77 If records are made public and thus published, it is possible
78 for other users to lookup the record given the ego's public key
79 and the label. Here, not only the label can thus act as a
80 passphrase but also the public key -- which despite its name
81 may not be public knowledge and is never disclosed by the GNS
82 protocol itself.
83 {% endtrans %}
84 </dd>
85 </dt>
86 <dt>{{ _("Peer") }}</dt>
87 <dd>
88 {% trans %}
89 A "peer" is an instance of GNUnet with its own per-instance
90 public key and network addresses. Technically, it is possible
91 to run multiple peers on the same host, but this only makes
92 sense for testing.
93 <br>
94 By design GNUnet supports multiple
95 users to share the same peer, just as UNIX is a multi-user
96 system. A "peer" typically consists of a set of foundational GNUnet
97 services running as the "gnunet" user and allowing all users
98 in the "gnunet" group to utilize the API. On multi-user
99 systems, additional "personalized" services may be required
100 per user.
101 <br>
102 While peers are also identified by public keys, these
103 public keys are completely unrelated to egos or
104 identities. Namespaces cannot be associated with a
105 peer, only with egos.
106 {% endtrans %}
107 </dd>
108 </dt>
109 </div><!-- END:col -->
110 </div><!-- END:row -->
111</div><!-- END:container -->
101{% endblock body_content %} 112{% endblock body_content %}
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-07 01:01:28 +0000