aboutsummaryrefslogtreecommitdiff
path: root/doc/old/handbook/chapters/philosophy.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/old/handbook/chapters/philosophy.texi')
-rw-r--r--doc/old/handbook/chapters/philosophy.texi82
1 files changed, 82 insertions, 0 deletions
diff --git a/doc/old/handbook/chapters/philosophy.texi b/doc/old/handbook/chapters/philosophy.texi
new file mode 100644
index 000000000..180589829
--- /dev/null
+++ b/doc/old/handbook/chapters/philosophy.texi
@@ -0,0 +1,82 @@
1@cindex Philosophy
2@node Philosophy
3@chapter Philosophy
4
5@c NOTE: We should probably re-use some of the images lynX created
6@c for secushare, showing some of the relations and functionalities
7@c of GNUnet.
8The primary goal of the GNUnet project is to provide a reliable, open,
9non-discriminating and censorship-resistant system for information
10exchange.
11We value free speech above state interests and intellectual
12monopoly. GNUnet's long-term goal is to serve as a development
13platform for the next generation of Internet protocols.
14
15Participants are encouraged to
16contribute at least as much resources (storage, bandwidth) to the network
17as they consume, so that their participation does not have a negative
18impact on other users.
19
20@menu
21* Design Principles::
22* Privacy and Anonymity::
23* Practicality::
24@end menu
25
26@cindex Design Principles
27@node Design Principles
28@section Design Principles
29
30These are the GNUnet design principles, in order of importance:
31
32@itemize
33@item GNUnet must be implemented as
34@uref{https://www.gnu.org/philosophy/free-sw.html, Free Software} ---
35This means that you have the four essential freedoms: to run
36the program, to study and change the program in source code form,
37to redistribute exact copies, and to distribute modified versions.
38(@uref{https://www.gnu.org/philosophy/free-sw.html}).
39@item GNUnet must minimize the amount of personally identifiable information exposed.
40@item GNUnet must be fully distributed and resilient to external attacks and rogue participants.
41@item GNUnet must be self-organizing and not depend on administrators or centralized infrastructure.
42@item GNUnet must inform the user which other participants have to be trusted when establishing private communications.
43@item GNUnet must be open and permit new peers to join.
44@item GNUnet must support a diverse range of applications and devices.
45@item GNUnet must use compartmentalization to protect sensitive information.
46@item The GNUnet architecture must be resource efficient.
47@item GNUnet must provide incentives for peers to contribute more resources than they consume.
48@end itemize
49
50
51@cindex Privacy and Anonymity
52@node Privacy and Anonymity
53@section Privacy and Anonymity
54
55The GNUnet protocols minimize the leakage of personally identifiable
56information of participants and do not allow adversaries to control,
57track, monitor or censor users activities. The GNUnet protocols also
58make it as hard as possible to disrupt operations by participating in
59the network with malicious intent.
60
61Analyzing participant's activities becomes more difficult as the
62number of peers and applications that generate traffic on the network
63grows, even if the additional traffic generated is not related to
64anonymous communication. This is one of the reasons why GNUnet is
65developed as a peer-to-peer framework where many applications share
66the lower layers of an increasingly complex protocol stack. The GNUnet
67architecture encourages many different forms of peer-to-peer
68applications.
69
70@cindex Practicality
71@node Practicality
72@section Practicality
73
74Wherever possible GNUnet allows the peer to adjust its operations and
75functionalities to specific use cases. A GNUnet peer running on a
76mobile device with limited battery for example might choose not to
77relay traffic for other participants.
78
79For certain applications like file-sharing GNUnet allows participants
80to trade degrees of anonymity in exchange for increased
81efficiency. However, it is not possible for any user's efficiency
82requirements to compromise the anonymity of any other user.