aboutsummaryrefslogtreecommitdiff
path: root/doc/handbook
diff options
context:
space:
mode:
authorTheJackiMonster <thejackimonster@gmail.com>2022-06-13 21:22:23 +0200
committerTheJackiMonster <thejackimonster@gmail.com>2022-06-13 21:22:23 +0200
commit1c910f64baa91df478dd0b4b4495aa3895efbf06 (patch)
treec7285d240a0a951fe5d5554344d98dc8e907e03f /doc/handbook
parent32064a9ffbc52790b1130e4d96c37c683569bcab (diff)
downloadgnunet-1c910f64baa91df478dd0b4b4495aa3895efbf06.tar.gz
gnunet-1c910f64baa91df478dd0b4b4495aa3895efbf06.zip
-adjusting terms of messenger service documentation in handbook
Signed-off-by: TheJackiMonster <thejackimonster@gmail.com>
Diffstat (limited to 'doc/handbook')
-rw-r--r--doc/handbook/chapters/developer.texi2
-rw-r--r--doc/handbook/chapters/user.texi22
2 files changed, 12 insertions, 12 deletions
diff --git a/doc/handbook/chapters/developer.texi b/doc/handbook/chapters/developer.texi
index 5f91a646e..c8905f2c1 100644
--- a/doc/handbook/chapters/developer.texi
+++ b/doc/handbook/chapters/developer.texi
@@ -9990,7 +9990,7 @@ Also MESSENGER provides multiple features with privacy in mind:
9990 original sender (uses the MESSENGER provided verification) 9990 original sender (uses the MESSENGER provided verification)
9991@item MESSENGER allows using the publicly known anonymous ego instead of any 9991@item MESSENGER allows using the publicly known anonymous ego instead of any
9992 unique identifying ego 9992 unique identifying ego
9993@item MESSENGER allows your node to decide between acting as host of the used 9993@item MESSENGER allows your node to decide between acting as relay of the used
9994 messaging room (sharing your peer's identity with all nodes in the group) 9994 messaging room (sharing your peer's identity with all nodes in the group)
9995 or acting as guest (sharing your peer's identity only with the nodes you 9995 or acting as guest (sharing your peer's identity only with the nodes you
9996 explicitly open a connection to) 9996 explicitly open a connection to)
diff --git a/doc/handbook/chapters/user.texi b/doc/handbook/chapters/user.texi
index 0b44ab57c..d30c94c9b 100644
--- a/doc/handbook/chapters/user.texi
+++ b/doc/handbook/chapters/user.texi
@@ -2365,16 +2365,16 @@ that will terminate at the respective peer's service.
2365@section Using the GNUnet Messenger 2365@section Using the GNUnet Messenger
2366 2366
2367The GNUnet Messenger subsystem allows decentralized message-based 2367The GNUnet Messenger subsystem allows decentralized message-based
2368communication inside of so called rooms. Each room can be hosted by 2368communication inside of so called rooms. Each room can be relayed by
2369a variable amount of peers. Every member of a room has the possibility 2369a variable amount of peers. Every member of a room has the possibility
2370to host the room on its own peer. A peer allows any amount of members 2370to relay the room on its own peer. A peer allows any amount of members
2371to join a room. The amount of members in a room is not restricted. 2371to join a room. The amount of members in a room is not restricted.
2372 2372
2373Messages in a room will be distributed between all peers hosting the 2373Messages in a room will be distributed between all peers relaying the
2374room or being internally (in context of the messenger service) connected 2374room or being internally (in context of the messenger service) connected
2375to a hosting peer. All received or sent messages will be stored on any 2375to a relaying peer. All received or sent messages will be stored on any
2376peer locally which is hosting the respective room or is internally 2376peer locally which is relaying the respective room or is internally
2377connected to such a hosting peer. 2377connected to such a relaying peer.
2378 2378
2379The Messenger service is built on the CADET subsystem to make internal 2379The Messenger service is built on the CADET subsystem to make internal
2380connections between peers using a reliable and encrypted transmission. 2380connections between peers using a reliable and encrypted transmission.
@@ -2411,9 +2411,9 @@ library designed for messenger applications.
2411@node Entering a room 2411@node Entering a room
2412@subsection Entering a room 2412@subsection Entering a room
2413 2413
2414You can enter any room by its ROOMKEY and any PEERIDENTITY of a hosting peer. 2414You can enter any room by its ROOMKEY and any PEERIDENTITY of a relaying
2415Optionally you can provide any IDENTITY which can represent a local ego by 2415peer. Optionally you can provide any IDENTITY which can represent a local
2416its name. 2416ego by its name.
2417 2417
2418@example 2418@example
2419$ gnunet-messenger [-e IDENTITY] -d PEERIDENTITY -r ROOMKEY 2419$ gnunet-messenger [-e IDENTITY] -d PEERIDENTITY -r ROOMKEY
@@ -2441,14 +2441,14 @@ be distributed as your name for the service in any case.
2441@subsection Opening a room 2441@subsection Opening a room
2442 2442
2443You can open any room in a similar way to entering it. You just have to leave 2443You can open any room in a similar way to entering it. You just have to leave
2444out the '-d' parameter and the PEERIDENTITY of the hosting peer. 2444out the '-d' parameter and the PEERIDENTITY of the relaying peer.
2445 2445
2446@example 2446@example
2447$ gnunet-messenger [-e IDENTITY] -r ROOMKEY 2447$ gnunet-messenger [-e IDENTITY] -r ROOMKEY
2448@end example 2448@end example
2449 2449
2450Providing ROOMKEY and IDENTITY is identical to entering a room. Opening a room 2450Providing ROOMKEY and IDENTITY is identical to entering a room. Opening a room
2451will also make your peer to a host of this room. So others can enter the room 2451will also make your peer to a relay of this room. So others can enter the room
2452through your peer if they have the required ROOMKEY and your peer ID. 2452through your peer if they have the required ROOMKEY and your peer ID.
2453 2453
2454If you want to use the zeroed hash as shared secret key for the room you can 2454If you want to use the zeroed hash as shared secret key for the room you can