commit: 7d3549cb350731990c6e23840fd6c586cc09952a
parent c162dd3f758b81086e14a3b1a61e926dab9790c6
Author: Drew DeVault <sir@cmpwn.com>
Date: Sun, 20 Sep 2020 10:19:26 -0400
Remove references to Star Trek because people are fucking assholes
This was not an invitation to listen to your essay on why the United
Federation of Planets is actually an autocratic government and I should
read your book on the subject, fuck off
Diffstat:
1 file changed, 6 insertions(+), 14 deletions(-)
diff --git a/content/blog/The-potential-of-federation.md b/content/blog/The-potential-of-federation.md
@@ -12,20 +12,12 @@ social problems?
**Federation** is an idea which takes a swing at all of these problems.
-To understand the software metaphor of federation, let's review what it means to
-the rest of the world. Consider the most well-known federation: the United
-Federation of Planets.
-
-
-
-In the Star Trek universe, the Federation is a group of sovereign planets (and
-species) with strong diplomatic ties, trade, and shared laws. A software system
-which is *federated* is similar, in that the servers are controlled by
-independent, sovereign entities, and that they exist together under a common web
-of communication protocols and social agreements. This occupies a sort of middle
-ground between the centralized architecture and the peer-to-peer (or
-"decentralized") architecture. Federation enjoys the advantages of both, and few
-of the drawbacks.
+The key trait of a software system which is *federated* is that the servers are
+controlled by independent, sovereign entities, and that they exist together
+under a common web of communication protocols and social agreements. This
+occupies a sort of middle ground between the centralized architecture and the
+peer-to-peer (or "decentralized") architecture. Federation enjoys the advantages
+of both, and few of the drawbacks.
In a federated software system, groups of users are built around small,
neighborly instances of servers. These are usually small servers, sporting only
