indymedia
/
epicyon
mirror of https://gitlab.com/bashrc2/epicyon
7
4
Fork 1
Code Issues 14 Releases Wiki Activity

Tidying

merge-requests/30/head
Bob Mottram 2022-10-23 18:27:01 +01:00
parent 9db7e776ac
commit b639184e8f
3 changed files with 12 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
manual/manual.epub
View File

Binary file not shown.

9
manual/manual.html
View File

@ -929,15 +929,14 @@ which may help.</p>
<img src="manual-fediverse.png" alt="Fediverse logo" />
<figcaption aria-hidden="true">Fediverse logo</figcaption>
</figure>
<h2 id="have-a-working-backup-system">Have a working backup system</h2>
<p><strong>Have a working backup system</strong></p>
<p>Keeping backups is very important, and fortunately with Epicyon this
is a simple process. The Epicyon installation consists only of files in
a directory. There is no database. So just backing up the directory
where it resides - typically <em>/opt/epicyon</em> - is all that you
need to do. Once you have a backup system in place, test that it
works.</p>
<h2 id="the-fediverse-is-not-an-open-source-twitter">The fediverse is
not an open source Twitter</h2>
<p><strong>The fediverse is not an open source Twitter</strong></p>
<p>This sounds like a trite comment, but if you have members on your
instance coming from Twitter and expecting it to be the same sort of
thing then they will be disappointed. A major difference is that the
@ -950,14 +949,14 @@ and dump all manner of aggravating trash into your timeline. On the
fediverse if you want to connect with people then you will need to be
more proactive in going out to <em>find the others</em>. There is no
algorithm trying to guess what you want without your participation.</p>
<h2 id="robustly-remove-bad-actors">Robustly remove bad actors</h2>
<p><strong>Robustly remove bad actors</strong></p>
<p>If people are creating a problem or bringing trouble and are not
amenable to changing their ways, whether they are members of your
instance or not, then be prepared to block or suspend their accounts.
Remember that <em>trolls will destroy your community if you let
them</em>. Define your <em>terms of service</em> and apply it
consistently to anyone interacting with your instance.</p>
<h2 id="curate-your-experience">Curate your experience</h2>
<p><strong>Curate your experience</strong></p>
<p>Add links to the left column and blog or podcast feeds to the right.
Choose links which are relevant to your community so that useful
information is one click away. If you have multiple people on your

12
manual/manual.md
View File

@ -672,16 +672,20 @@ The great thing about running a small instance is that you can do things in what
![Fediverse logo](manual-fediverse.png)
## Have a working backup system
**Have a working backup system**
Keeping backups is very important, and fortunately with Epicyon this is a simple process. The Epicyon installation consists only of files in a directory. There is no database. So just backing up the directory where it resides - typically */opt/epicyon* - is all that you need to do. Once you have a backup system in place, test that it works.
## The fediverse is not an open source Twitter
**The fediverse is not an open source Twitter**
This sounds like a trite comment, but if you have members on your instance coming from Twitter and expecting it to be the same sort of thing then they will be disappointed. A major difference is that the fediverse is more about conversation rather than one-way broadcast. Sites like Twitter encourage you to become an "influencer" and adopt a style of communication where you are shouting to a large audience without much expectation of dialogue.
On Twitter there is an algorithm which will make follow suggestions and dump all manner of aggravating trash into your timeline. On the fediverse if you want to connect with people then you will need to be more proactive in going out to *find the others*. There is no algorithm trying to guess what you want without your participation.
## Robustly remove bad actors
**Robustly remove bad actors**
If people are creating a problem or bringing trouble and are not amenable to changing their ways, whether they are members of your instance or not, then be prepared to block or suspend their accounts. Remember that *trolls will destroy your community if you let them*. Define your *terms of service* and apply it consistently to anyone interacting with your instance.
## Curate your experience
**Curate your experience**
Add links to the left column and blog or podcast feeds to the right. Choose links which are relevant to your community so that useful information is one click away. If you have multiple people on your instance then assign roles to them so that they have a stake in maintaining a good experience.