Kaynağa Gözat

Federation as a concept

Bob Mottram 7 yıl önce
ebeveyn
işleme
36d39c34a3
3 değiştirilmiş dosya ile 29 ekleme ve 20 silme
  1. 2
    0
      doc/EN/fediverse.org
  2. 0
    1
      src/freedombone-app-xmpp
  3. 27
    19
      website/EN/fediverse.html

+ 2
- 0
doc/EN/fediverse.org Dosyayı Görüntüle

18
 
18
 
19
 Some things you might want to know about the Fediverse:
19
 Some things you might want to know about the Fediverse:
20
 
20
 
21
+* Federation as a concept
22
+The political definition of a federation is "/a union of partially self-governing states or regions under a central (federal) government/". The fediverse isn't exactly like that, in that there is no federal government. However there are protocols which govern the communication between instances and that might be analogized to being a sort of elemantary constitution or mutual agreement binding all participants together. The protocols are merely ways of moving data around though, and don't impose any sort of moral code.
21
 * Keep the number of users on each server small
23
 * Keep the number of users on each server small
22
 The importance of this can't be overstated. Servers with lots of users always eventually have problems where the interests of the users are not the same as the interests of the server administrator. If you are the server administrator, or if there are only a small squad-size group of people on the server, then it's a lot easier to resolve differences and everyone's interests are likely to be similar.
24
 The importance of this can't be overstated. Servers with lots of users always eventually have problems where the interests of the users are not the same as the interests of the server administrator. If you are the server administrator, or if there are only a small squad-size group of people on the server, then it's a lot easier to resolve differences and everyone's interests are likely to be similar.
23
 
25
 

+ 0
- 1
src/freedombone-app-xmpp Dosyayı Görüntüle

210
         DOMAIN=${HOSTNAME}
210
         DOMAIN=${HOSTNAME}
211
     fi
211
     fi
212
     prosodyctl deluser "${remove_username}@${DOMAIN}"
212
     prosodyctl deluser "${remove_username}@${DOMAIN}"
213
-
214
 }
213
 }
215
 
214
 
216
 function add_user_xmpp_client {
215
 function add_user_xmpp_client {

+ 27
- 19
website/EN/fediverse.html Dosyayı Görüntüle

3
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
4
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5
 <head>
5
 <head>
6
-<!-- 2018-01-29 Mon 10:19 -->
6
+<!-- 2018-02-21 Wed 14:52 -->
7
 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
7
 <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
8
 <meta name="viewport" content="width=device-width, initial-scale=1" />
8
 <meta name="viewport" content="width=device-width, initial-scale=1" />
9
 <title>&lrm;</title>
9
 <title>&lrm;</title>
252
 Some things you might want to know about the Fediverse:
252
 Some things you might want to know about the Fediverse:
253
 </p>
253
 </p>
254
 
254
 
255
-<div id="outline-container-org403f1ae" class="outline-2">
256
-<h2 id="org403f1ae">Keep the number of users on each server small</h2>
257
-<div class="outline-text-2" id="text-org403f1ae">
255
+<div id="outline-container-org0e5c3f9" class="outline-2">
256
+<h2 id="org0e5c3f9">Federation as a concept</h2>
257
+<div class="outline-text-2" id="text-org0e5c3f9">
258
+<p>
259
+The political definition of a federation is "<i>a union of partially self-governing states or regions under a central (federal) government</i>". The fediverse isn't exactly like that, in that there is no federal government. However there are protocols which govern the communication between instances and that might be analogized to being a sort of elemantary constitution or mutual agreement binding all participants together. The protocols are merely ways of moving data around though, and don't impose any sort of moral code.
260
+</p>
261
+</div>
262
+</div>
263
+<div id="outline-container-org90385ba" class="outline-2">
264
+<h2 id="org90385ba">Keep the number of users on each server small</h2>
265
+<div class="outline-text-2" id="text-org90385ba">
258
 <p>
266
 <p>
259
 The importance of this can't be overstated. Servers with lots of users always eventually have problems where the interests of the users are not the same as the interests of the server administrator. If you are the server administrator, or if there are only a small squad-size group of people on the server, then it's a lot easier to resolve differences and everyone's interests are likely to be similar.
267
 The importance of this can't be overstated. Servers with lots of users always eventually have problems where the interests of the users are not the same as the interests of the server administrator. If you are the server administrator, or if there are only a small squad-size group of people on the server, then it's a lot easier to resolve differences and everyone's interests are likely to be similar.
260
 </p>
268
 </p>
261
 </div>
269
 </div>
262
 </div>
270
 </div>
263
 
271
 
264
-<div id="outline-container-org4b8c27b" class="outline-2">
265
-<h2 id="org4b8c27b">Drama will happen</h2>
266
-<div class="outline-text-2" id="text-org4b8c27b">
272
+<div id="outline-container-org1f1a75f" class="outline-2">
273
+<h2 id="org1f1a75f">Drama will happen</h2>
274
+<div class="outline-text-2" id="text-org1f1a75f">
267
 <p>
275
 <p>
268
 It's inevitable in any social network, but fortunately your options for dealing with it are better than they are in the giant proprietary monoliths. In the proprietary world Google or Facebook don't give a damn about the fate of individual users. On a server with a small number of users if you're getting griefed then the administrator is likely to care and be able to do something about it.
276
 It's inevitable in any social network, but fortunately your options for dealing with it are better than they are in the giant proprietary monoliths. In the proprietary world Google or Facebook don't give a damn about the fate of individual users. On a server with a small number of users if you're getting griefed then the administrator is likely to care and be able to do something about it.
269
 </p>
277
 </p>
270
 </div>
278
 </div>
271
 </div>
279
 </div>
272
 
280
 
273
-<div id="outline-container-org6bb90e7" class="outline-2">
274
-<h2 id="org6bb90e7">Don't be afraid to block</h2>
275
-<div class="outline-text-2" id="text-org6bb90e7">
281
+<div id="outline-container-org249f254" class="outline-2">
282
+<h2 id="org249f254">Don't be afraid to block</h2>
283
+<div class="outline-text-2" id="text-org249f254">
276
 <p>
284
 <p>
277
 Especially if other servers are publishing content which may not be legal in your jurisdiction then don't be afraid to use domain or user blocking from the <b>Administrator control panel</b>. The same applies if users on other servers are trying to harass you. Blocking creates politics and drama but <span class="underline">this is a feature not a bug</span>. It allows you to craft your own distinct community and user experience while also existing in the wider federation. It's hard to do this on sites like Twitter or Facebook. Try to keep blocking to a minimum though and avoid doing it for insubstantial reasons. If you have other users on your server then publish the blocked domains list somewhere they can see. That avoids disappointment and enables you to have a discussion about the validity of blocking decisions.
285
 Especially if other servers are publishing content which may not be legal in your jurisdiction then don't be afraid to use domain or user blocking from the <b>Administrator control panel</b>. The same applies if users on other servers are trying to harass you. Blocking creates politics and drama but <span class="underline">this is a feature not a bug</span>. It allows you to craft your own distinct community and user experience while also existing in the wider federation. It's hard to do this on sites like Twitter or Facebook. Try to keep blocking to a minimum though and avoid doing it for insubstantial reasons. If you have other users on your server then publish the blocked domains list somewhere they can see. That avoids disappointment and enables you to have a discussion about the validity of blocking decisions.
278
 </p>
286
 </p>
279
 </div>
287
 </div>
280
 </div>
288
 </div>
281
 
289
 
282
-<div id="outline-container-orgded15c7" class="outline-2">
283
-<h2 id="orgded15c7">Network structure maps on to social structure</h2>
284
-<div class="outline-text-2" id="text-orgded15c7">
290
+<div id="outline-container-org16e1345" class="outline-2">
291
+<h2 id="org16e1345">Network structure maps on to social structure</h2>
292
+<div class="outline-text-2" id="text-org16e1345">
285
 <p>
293
 <p>
286
 Over time follows and blocking rules come to match the underlying social geography of affinity groups. Blocking will happen and users will move around or start new servers. Drama related to blocking will dissipate.
294
 Over time follows and blocking rules come to match the underlying social geography of affinity groups. Blocking will happen and users will move around or start new servers. Drama related to blocking will dissipate.
287
 </p>
295
 </p>
288
 </div>
296
 </div>
289
 </div>
297
 </div>
290
 
298
 
291
-<div id="outline-container-orgd6823a8" class="outline-2">
292
-<h2 id="orgd6823a8">Keep your follows under the Dunbar number</h2>
293
-<div class="outline-text-2" id="text-orgd6823a8">
299
+<div id="outline-container-orga5968b2" class="outline-2">
300
+<h2 id="orga5968b2">Keep your follows under the Dunbar number</h2>
301
+<div class="outline-text-2" id="text-orga5968b2">
294
 <p>
302
 <p>
295
 Keep the number of other users you're following and who are also active to under a couple of hundred. Any more than that and you'll just be overwhelmed by irrelevant stuff and whatever community you may have been part of will dissolve in a sea of entropy. There are no algorithmic timelines, and even if they're introduced then they create their own problems as an opaque form of censorship. <span class="underline">Real community happens at tribal scale</span>. It's something which people often don't like to admit because they get fixated upon bigger and bigger numbers, but it definitely seems to be true.
303
 Keep the number of other users you're following and who are also active to under a couple of hundred. Any more than that and you'll just be overwhelmed by irrelevant stuff and whatever community you may have been part of will dissolve in a sea of entropy. There are no algorithmic timelines, and even if they're introduced then they create their own problems as an opaque form of censorship. <span class="underline">Real community happens at tribal scale</span>. It's something which people often don't like to admit because they get fixated upon bigger and bigger numbers, but it definitely seems to be true.
296
 </p>
304
 </p>
297
 </div>
305
 </div>
298
 </div>
306
 </div>
299
 
307
 
300
-<div id="outline-container-org77ec195" class="outline-2">
301
-<h2 id="org77ec195">Avoid big public servers</h2>
302
-<div class="outline-text-2" id="text-org77ec195">
308
+<div id="outline-container-orgc8c8b40" class="outline-2">
309
+<h2 id="orgc8c8b40">Avoid big public servers</h2>
310
+<div class="outline-text-2" id="text-orgc8c8b40">
303
 <p>
311
 <p>
304
 It may seem like a good idea and it may seem like you're doing a service to the community by allowing random strangers to register, but servers with thousands of users only cause problems - social, administrative, financial and possibly also legal. The financial strain of running a powerful server with high reliability may be enough to encourage the administrator to begin pushing advertising onto the system, or sell user content, and then before you know it you have identical problems to Twitter. Instead try to encourage people to set up their own servers. Follow this principle and a lot of arguments and stress will be more easily avoided.
312
 It may seem like a good idea and it may seem like you're doing a service to the community by allowing random strangers to register, but servers with thousands of users only cause problems - social, administrative, financial and possibly also legal. The financial strain of running a powerful server with high reliability may be enough to encourage the administrator to begin pushing advertising onto the system, or sell user content, and then before you know it you have identical problems to Twitter. Instead try to encourage people to set up their own servers. Follow this principle and a lot of arguments and stress will be more easily avoided.
305
 </p>
313
 </p>