Advice about the fediverse
This commit is contained in:
Bob Mottram
parent
97c48ffa47
commit
4d99772872
|
|
@ -22,6 +22,8 @@ You can host your own GNU Social instance and then "/remote follow/" other users
|
|||
|
||||
You should regard anything posted to GNU Social as being /public communication/ visible to anyone on the internet. There is a direct messaging capability between users but it's not particularly secure, so for one-to-one messages stick to better methods, such as XMPP with OTR/OMEMO or Tox.
|
||||
|
||||
Some general advice about life in the fediverse [[./fediverse.html][can be found here]].
|
||||
|
||||
|
||||
#+BEGIN_CENTER
|
||||
[[file:images/gnusocial_pleroma.jpg]]
|
||||
|
|
|
|||
|
|
@ -18,6 +18,8 @@
|
|||
|
||||
PostActiv is a fork of [[./app_gnusocial.html][GNU Social]] which includes some extra fixes and optimisations to improve performance. It federates just like GNU Social does and so whether you choose GNU Social or PostActiv is really just down to personal prefernce.
|
||||
|
||||
Some general advice about life in the fediverse [[./fediverse.html][can be found here]].
|
||||
|
||||
#+BEGIN_CENTER
|
||||
[[file:images/postactiv_pleroma.jpg]]
|
||||
#+END_CENTER
|
||||
|
|
|
|||
|
|
@ -0,0 +1,37 @@
|
|||
#+TITLE:
|
||||
#+AUTHOR: Bob Mottram
|
||||
#+EMAIL: bob@freedombone.net
|
||||
#+KEYWORDS: freedombone, homestead, fediverse
|
||||
#+DESCRIPTION: Homesteading the Fediverse
|
||||
#+OPTIONS: ^:nil toc:nil
|
||||
#+HTML_HEAD: <link rel="stylesheet" type="text/css" href="freedombone.css" />
|
||||
|
||||
#+BEGIN_CENTER
|
||||
[[file:images/logo.png]]
|
||||
#+END_CENTER
|
||||
|
||||
#+BEGIN_EXPORT html
|
||||
<center>
|
||||
<h1>Homesteading the Fediverse</h1>
|
||||
</center>
|
||||
#+END_EXPORT
|
||||
|
||||
Some things you might want to know about the Fediverse:
|
||||
|
||||
* Keep the number of users on each server small
|
||||
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.
|
||||
|
||||
* Drama will happen
|
||||
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.
|
||||
|
||||
* Don't be afraid to block
|
||||
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 *Administrator control panel*. The same applies if users on other servers are trying to harass you. Blocking creates politics and drama but _this is a feature not a bug_. 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.
|
||||
|
||||
* Network structure maps on to social structure
|
||||
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.
|
||||
|
||||
* Keep your follows under the Dunbar number
|
||||
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. _Real community happens at tribal scale_. 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.
|
||||
|
||||
* Avoid big public servers
|
||||
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.
|
||||
|
|
@ -3,7 +3,7 @@
|
|||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!-- 2017-05-02 Tue 21:48 -->
|
||||
<!-- 2017-05-09 Tue 15:00 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title></title>
|
||||
|
|
@ -260,6 +260,10 @@ You can host your own GNU Social instance and then "<i>remote follow</i>" other
|
|||
You should regard anything posted to GNU Social as being <i>public communication</i> visible to anyone on the internet. There is a direct messaging capability between users but it's not particularly secure, so for one-to-one messages stick to better methods, such as XMPP with OTR/OMEMO or Tox.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Some general advice about life in the fediverse <a href="./fediverse.html">can be found here</a>.
|
||||
</p>
|
||||
|
||||
|
||||
<div class="org-center">
|
||||
|
||||
|
|
@ -270,9 +274,9 @@ You should regard anything posted to GNU Social as being <i>public communication
|
|||
</div>
|
||||
|
||||
|
||||
<div id="outline-container-org863298b" class="outline-2">
|
||||
<h2 id="org863298b">Installation</h2>
|
||||
<div class="outline-text-2" id="text-org863298b">
|
||||
<div id="outline-container-org5123b46" class="outline-2">
|
||||
<h2 id="org5123b46">Installation</h2>
|
||||
<div class="outline-text-2" id="text-org5123b46">
|
||||
<p>
|
||||
Log into your system with:
|
||||
</p>
|
||||
|
|
@ -296,9 +300,9 @@ After the install has completed go to <b>Security settings</b> and select <b>Cre
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orge7edd20" class="outline-2">
|
||||
<h2 id="orge7edd20">Initial setup</h2>
|
||||
<div class="outline-text-2" id="text-orge7edd20">
|
||||
<div id="outline-container-org9477256" class="outline-2">
|
||||
<h2 id="org9477256">Initial setup</h2>
|
||||
<div class="outline-text-2" id="text-org9477256">
|
||||
<p>
|
||||
If you have just obtained a Lets Encrypt certificate as above then go to <b>About</b> on the administrator control panel and you should see your GNU Social domain listed there along with an onion address. You can then navigate to your site in a browser.
|
||||
</p>
|
||||
|
|
@ -325,9 +329,9 @@ GNU Social has a clutter-free mobile user interface which can be accessed via a
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgbfca992" class="outline-2">
|
||||
<h2 id="orgbfca992">Switching user interfaces</h2>
|
||||
<div class="outline-text-2" id="text-orgbfca992">
|
||||
<div id="outline-container-org3314c00" class="outline-2">
|
||||
<h2 id="org3314c00">Switching user interfaces</h2>
|
||||
<div class="outline-text-2" id="text-org3314c00">
|
||||
<p>
|
||||
A few web based user interfaces are available for GNU SOcial. They are selectable by going to the <b>Administrator control panel</b> and choosing <b>App settings</b> then <b>gnusocial</b>.
|
||||
</p>
|
||||
|
|
@ -348,9 +352,9 @@ A few web based user interfaces are available for GNU SOcial. They are selectabl
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgec5c6e2" class="outline-2">
|
||||
<h2 id="orgec5c6e2">Using with Emacs</h2>
|
||||
<div class="outline-text-2" id="text-orgec5c6e2">
|
||||
<div id="outline-container-org52974f0" class="outline-2">
|
||||
<h2 id="org52974f0">Using with Emacs</h2>
|
||||
<div class="outline-text-2" id="text-org52974f0">
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
|
|
@ -531,9 +535,9 @@ Showing timelines:
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgb3d0cfc" class="outline-2">
|
||||
<h2 id="orgb3d0cfc">Blocking controls</h2>
|
||||
<div class="outline-text-2" id="text-orgb3d0cfc">
|
||||
<div id="outline-container-orgd6dab31" class="outline-2">
|
||||
<h2 id="orgd6dab31">Blocking controls</h2>
|
||||
<div class="outline-text-2" id="text-orgd6dab31">
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!-- 2017-05-02 Tue 21:59 -->
|
||||
<!-- 2017-05-09 Tue 15:00 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title></title>
|
||||
|
|
@ -252,6 +252,10 @@ for the JavaScript code in this tag.
|
|||
PostActiv is a fork of <a href="./app_gnusocial.html">GNU Social</a> which includes some extra fixes and optimisations to improve performance. It federates just like GNU Social does and so whether you choose GNU Social or PostActiv is really just down to personal prefernce.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Some general advice about life in the fediverse <a href="./fediverse.html">can be found here</a>.
|
||||
</p>
|
||||
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
|
|
@ -260,9 +264,9 @@ PostActiv is a fork of <a href="./app_gnusocial.html">GNU Social</a> which inclu
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgc07cced" class="outline-2">
|
||||
<h2 id="orgc07cced">Installation</h2>
|
||||
<div class="outline-text-2" id="text-orgc07cced">
|
||||
<div id="outline-container-org26c2bda" class="outline-2">
|
||||
<h2 id="org26c2bda">Installation</h2>
|
||||
<div class="outline-text-2" id="text-org26c2bda">
|
||||
<p>
|
||||
Log into your system with:
|
||||
</p>
|
||||
|
|
@ -286,9 +290,9 @@ After the install has completed go to <b>Security settings</b> and select <b>Cre
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org9b27fa0" class="outline-2">
|
||||
<h2 id="org9b27fa0">Initial setup</h2>
|
||||
<div class="outline-text-2" id="text-org9b27fa0">
|
||||
<div id="outline-container-orgbaf18f8" class="outline-2">
|
||||
<h2 id="orgbaf18f8">Initial setup</h2>
|
||||
<div class="outline-text-2" id="text-orgbaf18f8">
|
||||
<p>
|
||||
If you have just obtained a Lets Encrypt certificate as above then go to <b>About</b> on the administrator control panel and you should see your Postactiv domain listed there along with an onion address. You can then navigate to your site in a browser.
|
||||
</p>
|
||||
|
|
@ -303,9 +307,9 @@ Navigate to your PostActiv domain name and log in.
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org2b5242d" class="outline-2">
|
||||
<h2 id="org2b5242d">Switching user interfaces</h2>
|
||||
<div class="outline-text-2" id="text-org2b5242d">
|
||||
<div id="outline-container-org021b024" class="outline-2">
|
||||
<h2 id="org021b024">Switching user interfaces</h2>
|
||||
<div class="outline-text-2" id="text-org021b024">
|
||||
<p>
|
||||
A few web based user interfaces are available for PostActiv. They are selectable by going to the <b>Administrator control panel</b> and choosing <b>App settings</b> then <b>postactiv</b>.
|
||||
</p>
|
||||
|
|
@ -326,9 +330,9 @@ A few web based user interfaces are available for PostActiv. They are selectable
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org0406a22" class="outline-2">
|
||||
<h2 id="org0406a22">Using with Emacs</h2>
|
||||
<div class="outline-text-2" id="text-org0406a22">
|
||||
<div id="outline-container-org02acac0" class="outline-2">
|
||||
<h2 id="org02acac0">Using with Emacs</h2>
|
||||
<div class="outline-text-2" id="text-org02acac0">
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
|
|
@ -509,9 +513,9 @@ Showing timelines:
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgc583b93" class="outline-2">
|
||||
<h2 id="orgc583b93">Blocking controls</h2>
|
||||
<div class="outline-text-2" id="text-orgc583b93">
|
||||
<div id="outline-container-org5f5a12e" class="outline-2">
|
||||
<h2 id="org5f5a12e">Blocking controls</h2>
|
||||
<div class="outline-text-2" id="text-org5f5a12e">
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
|
|
|
|||
|
|
@ -0,0 +1,334 @@
|
|||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
||||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!-- 2017-05-09 Tue 14:58 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title></title>
|
||||
<meta name="generator" content="Org mode" />
|
||||
<meta name="author" content="Bob Mottram" />
|
||||
<meta name="description" content="Homesteading the Fediverse"
|
||||
/>
|
||||
<meta name="keywords" content="freedombone, homestead, fediverse" />
|
||||
<style type="text/css">
|
||||
<!--/*--><![CDATA[/*><!--*/
|
||||
.title { text-align: center;
|
||||
margin-bottom: .2em; }
|
||||
.subtitle { text-align: center;
|
||||
font-size: medium;
|
||||
font-weight: bold;
|
||||
margin-top:0; }
|
||||
.todo { font-family: monospace; color: red; }
|
||||
.done { font-family: monospace; color: green; }
|
||||
.priority { font-family: monospace; color: orange; }
|
||||
.tag { background-color: #eee; font-family: monospace;
|
||||
padding: 2px; font-size: 80%; font-weight: normal; }
|
||||
.timestamp { color: #bebebe; }
|
||||
.timestamp-kwd { color: #5f9ea0; }
|
||||
.org-right { margin-left: auto; margin-right: 0px; text-align: right; }
|
||||
.org-left { margin-left: 0px; margin-right: auto; text-align: left; }
|
||||
.org-center { margin-left: auto; margin-right: auto; text-align: center; }
|
||||
.underline { text-decoration: underline; }
|
||||
#postamble p, #preamble p { font-size: 90%; margin: .2em; }
|
||||
p.verse { margin-left: 3%; }
|
||||
pre {
|
||||
border: 1px solid #ccc;
|
||||
box-shadow: 3px 3px 3px #eee;
|
||||
padding: 8pt;
|
||||
font-family: monospace;
|
||||
overflow: auto;
|
||||
margin: 1.2em;
|
||||
}
|
||||
pre.src {
|
||||
position: relative;
|
||||
overflow: visible;
|
||||
padding-top: 1.2em;
|
||||
}
|
||||
pre.src:before {
|
||||
display: none;
|
||||
position: absolute;
|
||||
background-color: white;
|
||||
top: -10px;
|
||||
right: 10px;
|
||||
padding: 3px;
|
||||
border: 1px solid black;
|
||||
}
|
||||
pre.src:hover:before { display: inline;}
|
||||
/* Languages per Org manual */
|
||||
pre.src-asymptote:before { content: 'Asymptote'; }
|
||||
pre.src-awk:before { content: 'Awk'; }
|
||||
pre.src-C:before { content: 'C'; }
|
||||
/* pre.src-C++ doesn't work in CSS */
|
||||
pre.src-clojure:before { content: 'Clojure'; }
|
||||
pre.src-css:before { content: 'CSS'; }
|
||||
pre.src-D:before { content: 'D'; }
|
||||
pre.src-ditaa:before { content: 'ditaa'; }
|
||||
pre.src-dot:before { content: 'Graphviz'; }
|
||||
pre.src-calc:before { content: 'Emacs Calc'; }
|
||||
pre.src-emacs-lisp:before { content: 'Emacs Lisp'; }
|
||||
pre.src-fortran:before { content: 'Fortran'; }
|
||||
pre.src-gnuplot:before { content: 'gnuplot'; }
|
||||
pre.src-haskell:before { content: 'Haskell'; }
|
||||
pre.src-hledger:before { content: 'hledger'; }
|
||||
pre.src-java:before { content: 'Java'; }
|
||||
pre.src-js:before { content: 'Javascript'; }
|
||||
pre.src-latex:before { content: 'LaTeX'; }
|
||||
pre.src-ledger:before { content: 'Ledger'; }
|
||||
pre.src-lisp:before { content: 'Lisp'; }
|
||||
pre.src-lilypond:before { content: 'Lilypond'; }
|
||||
pre.src-lua:before { content: 'Lua'; }
|
||||
pre.src-matlab:before { content: 'MATLAB'; }
|
||||
pre.src-mscgen:before { content: 'Mscgen'; }
|
||||
pre.src-ocaml:before { content: 'Objective Caml'; }
|
||||
pre.src-octave:before { content: 'Octave'; }
|
||||
pre.src-org:before { content: 'Org mode'; }
|
||||
pre.src-oz:before { content: 'OZ'; }
|
||||
pre.src-plantuml:before { content: 'Plantuml'; }
|
||||
pre.src-processing:before { content: 'Processing.js'; }
|
||||
pre.src-python:before { content: 'Python'; }
|
||||
pre.src-R:before { content: 'R'; }
|
||||
pre.src-ruby:before { content: 'Ruby'; }
|
||||
pre.src-sass:before { content: 'Sass'; }
|
||||
pre.src-scheme:before { content: 'Scheme'; }
|
||||
pre.src-screen:before { content: 'Gnu Screen'; }
|
||||
pre.src-sed:before { content: 'Sed'; }
|
||||
pre.src-sh:before { content: 'shell'; }
|
||||
pre.src-sql:before { content: 'SQL'; }
|
||||
pre.src-sqlite:before { content: 'SQLite'; }
|
||||
/* additional languages in org.el's org-babel-load-languages alist */
|
||||
pre.src-forth:before { content: 'Forth'; }
|
||||
pre.src-io:before { content: 'IO'; }
|
||||
pre.src-J:before { content: 'J'; }
|
||||
pre.src-makefile:before { content: 'Makefile'; }
|
||||
pre.src-maxima:before { content: 'Maxima'; }
|
||||
pre.src-perl:before { content: 'Perl'; }
|
||||
pre.src-picolisp:before { content: 'Pico Lisp'; }
|
||||
pre.src-scala:before { content: 'Scala'; }
|
||||
pre.src-shell:before { content: 'Shell Script'; }
|
||||
pre.src-ebnf2ps:before { content: 'ebfn2ps'; }
|
||||
/* additional language identifiers per "defun org-babel-execute"
|
||||
in ob-*.el */
|
||||
pre.src-cpp:before { content: 'C++'; }
|
||||
pre.src-abc:before { content: 'ABC'; }
|
||||
pre.src-coq:before { content: 'Coq'; }
|
||||
pre.src-groovy:before { content: 'Groovy'; }
|
||||
/* additional language identifiers from org-babel-shell-names in
|
||||
ob-shell.el: ob-shell is the only babel language using a lambda to put
|
||||
the execution function name together. */
|
||||
pre.src-bash:before { content: 'bash'; }
|
||||
pre.src-csh:before { content: 'csh'; }
|
||||
pre.src-ash:before { content: 'ash'; }
|
||||
pre.src-dash:before { content: 'dash'; }
|
||||
pre.src-ksh:before { content: 'ksh'; }
|
||||
pre.src-mksh:before { content: 'mksh'; }
|
||||
pre.src-posh:before { content: 'posh'; }
|
||||
/* Additional Emacs modes also supported by the LaTeX listings package */
|
||||
pre.src-ada:before { content: 'Ada'; }
|
||||
pre.src-asm:before { content: 'Assembler'; }
|
||||
pre.src-caml:before { content: 'Caml'; }
|
||||
pre.src-delphi:before { content: 'Delphi'; }
|
||||
pre.src-html:before { content: 'HTML'; }
|
||||
pre.src-idl:before { content: 'IDL'; }
|
||||
pre.src-mercury:before { content: 'Mercury'; }
|
||||
pre.src-metapost:before { content: 'MetaPost'; }
|
||||
pre.src-modula-2:before { content: 'Modula-2'; }
|
||||
pre.src-pascal:before { content: 'Pascal'; }
|
||||
pre.src-ps:before { content: 'PostScript'; }
|
||||
pre.src-prolog:before { content: 'Prolog'; }
|
||||
pre.src-simula:before { content: 'Simula'; }
|
||||
pre.src-tcl:before { content: 'tcl'; }
|
||||
pre.src-tex:before { content: 'TeX'; }
|
||||
pre.src-plain-tex:before { content: 'Plain TeX'; }
|
||||
pre.src-verilog:before { content: 'Verilog'; }
|
||||
pre.src-vhdl:before { content: 'VHDL'; }
|
||||
pre.src-xml:before { content: 'XML'; }
|
||||
pre.src-nxml:before { content: 'XML'; }
|
||||
/* add a generic configuration mode; LaTeX export needs an additional
|
||||
(add-to-list 'org-latex-listings-langs '(conf " ")) in .emacs */
|
||||
pre.src-conf:before { content: 'Configuration File'; }
|
||||
|
||||
table { border-collapse:collapse; }
|
||||
caption.t-above { caption-side: top; }
|
||||
caption.t-bottom { caption-side: bottom; }
|
||||
td, th { vertical-align:top; }
|
||||
th.org-right { text-align: center; }
|
||||
th.org-left { text-align: center; }
|
||||
th.org-center { text-align: center; }
|
||||
td.org-right { text-align: right; }
|
||||
td.org-left { text-align: left; }
|
||||
td.org-center { text-align: center; }
|
||||
dt { font-weight: bold; }
|
||||
.footpara { display: inline; }
|
||||
.footdef { margin-bottom: 1em; }
|
||||
.figure { padding: 1em; }
|
||||
.figure p { text-align: center; }
|
||||
.inlinetask {
|
||||
padding: 10px;
|
||||
border: 2px solid gray;
|
||||
margin: 10px;
|
||||
background: #ffffcc;
|
||||
}
|
||||
#org-div-home-and-up
|
||||
{ text-align: right; font-size: 70%; white-space: nowrap; }
|
||||
textarea { overflow-x: auto; }
|
||||
.linenr { font-size: smaller }
|
||||
.code-highlighted { background-color: #ffff00; }
|
||||
.org-info-js_info-navigation { border-style: none; }
|
||||
#org-info-js_console-label
|
||||
{ font-size: 10px; font-weight: bold; white-space: nowrap; }
|
||||
.org-info-js_search-highlight
|
||||
{ background-color: #ffff00; color: #000000; font-weight: bold; }
|
||||
.org-svg { width: 90%; }
|
||||
/*]]>*/-->
|
||||
</style>
|
||||
<link rel="stylesheet" type="text/css" href="freedombone.css" />
|
||||
<script type="text/javascript">
|
||||
/*
|
||||
@licstart The following is the entire license notice for the
|
||||
JavaScript code in this tag.
|
||||
|
||||
Copyright (C) 2012-2017 Free Software Foundation, Inc.
|
||||
|
||||
The JavaScript code in this tag is free software: you can
|
||||
redistribute it and/or modify it under the terms of the GNU
|
||||
General Public License (GNU GPL) as published by the Free Software
|
||||
Foundation, either version 3 of the License, or (at your option)
|
||||
any later version. The code is distributed WITHOUT ANY WARRANTY;
|
||||
without even the implied warranty of MERCHANTABILITY or FITNESS
|
||||
FOR A PARTICULAR PURPOSE. See the GNU GPL for more details.
|
||||
|
||||
As additional permission under GNU GPL version 3 section 7, you
|
||||
may distribute non-source (e.g., minimized or compacted) forms of
|
||||
that code without the copy of the GNU GPL normally required by
|
||||
section 4, provided you include this license notice and a URL
|
||||
through which recipients can access the Corresponding Source.
|
||||
|
||||
|
||||
@licend The above is the entire license notice
|
||||
for the JavaScript code in this tag.
|
||||
*/
|
||||
<!--/*--><![CDATA[/*><!--*/
|
||||
function CodeHighlightOn(elem, id)
|
||||
{
|
||||
var target = document.getElementById(id);
|
||||
if(null != target) {
|
||||
elem.cacheClassElem = elem.className;
|
||||
elem.cacheClassTarget = target.className;
|
||||
target.className = "code-highlighted";
|
||||
elem.className = "code-highlighted";
|
||||
}
|
||||
}
|
||||
function CodeHighlightOff(elem, id)
|
||||
{
|
||||
var target = document.getElementById(id);
|
||||
if(elem.cacheClassElem)
|
||||
elem.className = elem.cacheClassElem;
|
||||
if(elem.cacheClassTarget)
|
||||
target.className = elem.cacheClassTarget;
|
||||
}
|
||||
/*]]>*///-->
|
||||
</script>
|
||||
</head>
|
||||
<body>
|
||||
<div id="preamble" class="status">
|
||||
<a name="top" id="top"></a>
|
||||
</div>
|
||||
<div id="content">
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
<p><img src="images/logo.png" alt="logo.png" />
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<center>
|
||||
<h1>Homesteading the Fediverse</h1>
|
||||
</center>
|
||||
|
||||
<p>
|
||||
Some things you might want to know about the Fediverse:
|
||||
</p>
|
||||
|
||||
<div id="outline-container-org79167d7" class="outline-2">
|
||||
<h2 id="org79167d7">Keep the number of users on each server small</h2>
|
||||
<div class="outline-text-2" id="text-org79167d7">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgbeaecc8" class="outline-2">
|
||||
<h2 id="orgbeaecc8">Drama will happen</h2>
|
||||
<div class="outline-text-2" id="text-orgbeaecc8">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org25d0b82" class="outline-2">
|
||||
<h2 id="org25d0b82">Don't be afraid to block</h2>
|
||||
<div class="outline-text-2" id="text-org25d0b82">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgfaf78d0" class="outline-2">
|
||||
<h2 id="orgfaf78d0">Network structure maps on to social structure</h2>
|
||||
<div class="outline-text-2" id="text-orgfaf78d0">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org7cbda19" class="outline-2">
|
||||
<h2 id="org7cbda19">Keep your follows under the Dunbar number</h2>
|
||||
<div class="outline-text-2" id="text-org7cbda19">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org740ea65" class="outline-2">
|
||||
<h2 id="org740ea65">Avoid big public servers</h2>
|
||||
<div class="outline-text-2" id="text-org740ea65">
|
||||
<p>
|
||||
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.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div id="postamble" class="status">
|
||||
|
||||
<style type="text/css">
|
||||
.back-to-top {
|
||||
position: fixed;
|
||||
bottom: 2em;
|
||||
right: 0px;
|
||||
text-decoration: none;
|
||||
color: #000000;
|
||||
background-color: rgba(235, 235, 235, 0.80);
|
||||
font-size: 12px;
|
||||
padding: 1em;
|
||||
display: none;
|
||||
}
|
||||
|
||||
.back-to-top:hover {
|
||||
background-color: rgba(135, 135, 135, 0.50);
|
||||
}
|
||||
</style>
|
||||
|
||||
<div class="back-to-top">
|
||||
<a href="#top">Back to top</a> | <a href="mailto:bob@freedombone.net">E-mail me</a>
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
Loading…
Reference in New Issue