-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
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 find the others. There is no algorithm trying to guess what you want without your participation.
-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
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 diff --git a/manual/manual.md b/manual/manual.md index 95cdbde4e..44b1597f2 100644 --- a/manual/manual.md +++ b/manual/manual.md @@ -672,16 +672,20 @@ The great thing about running a small instance is that you can do things in what  -## 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.