commit a3fbbcb14aa4b122841e7f016d7fb24f29d512ca
parent b825a5da7cd6dd026bf8068aa4660073491c0de8
Author: rra <rscmbbn@riseup.net>
Date: Sat Feb 1 08:03:27 +0100
todo
Diffstat:1 file changed, 6 insertions(+), 0 deletions(-)
diff --git a/transmediale-2020-7-theses/index.html b/transmediale-2020-7-theses/index.html
@@ -191,6 +191,8 @@ class: inverted, middle, center, contain
# CENTRALIZED DIAGRAM HERE
+TODO
+
???
MENTION THESE ARE FROM THE WORKSHOP AT TM
@@ -200,6 +202,8 @@ On a centralised network, every account relies on a central hub to carry communi
class: inverted, middle, center
# FEDERATED DIAGRAM HERE
+TODO
+
???
But on a federated network like the Fediverse, users can register one or several accounts on different servers (called instances) of the network, and the instances take care of sending and receiving messages between accounts across the network. Likewise power is distributed across the network.
@@ -207,6 +211,8 @@ But on a federated network like the Fediverse, users can register one or several
class: inverted, middle, center
# FEDERATED DIAGRAM HERE
+TODO
+
???
Each instance can be run by anyone or any group of people for any purpose. This means that in practice the Fediverse is a giant mess. Instances can for general purpose and have several thousands users, or they can be focussed on a specific topic, practice, subject with a handful of users. Some instances are even single user. Finally it's up to each instance to decide if they want to be open to registrations, be invite-only, if they want to publish a code of conduct, or not, etc.
