friendica/friendica
6
0
Fork 1
mirror of https://github.com/friendica/friendica synced 2024-05-12 17:09:39 +02:00
Code Issues Packages Projects Releases 1 Wiki Activity

Updated Running a public or community server (markdown)

MartinFarrent 2012-05-24 23:39:20 -07:00
parent 0283329e1a
commit 30785703db
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
Running-a-public-or-community-server.md

@ -8,11 +8,11 @@ That's because running a public or community Friendica server requires special c
A community server caters for a specific group of people - your community centre, or church, perhaps - whereas a public server caters for the public at large. Both types of site have lots in common, but there are some important differences too.
For instance, registration policy is affected by these differences. If you run a _public_ server and choose to accept or deny registrations arbitrarily, you make the whole Friendica project look unreliable. It is very poor form to be listed on the public server list with a "requires approval" setup if you wish to cherry-pick users. As a public server admin, you may find that you have users you don't really want on your server - but that's the price you pay for serving the public. If you have criteria for accepting or rejecting users, make your requirements clear on your website, and when you refuse an applicant make sure they know why, and they get a link to find other public servers - no email is ever sent to a rejected member unless you do so manually. If you really wish to cherry-pick spontaneously, you should not ask to be listed as a public server
For instance, registration policy is affected by these differences. If you run a _public_ server and choose to accept or deny registrations arbitrarily, you make the whole Friendica project look unreliable. On the other hand, if you had a _community_ server that allowed people from anywhere to sign up, you'd quickly run out of resources and your site would eventually grind to a halt. That's because a community server probably knows how many users it will have and can purchase resources accordingly - a soccer club, for instance, has a defined membership base.
On the other hand, if you had a _community_ server that allowed people from anywhere to sign up, you'd quickly run out of resources and your site would eventually grind to a halt. That's because a community server probably knows how many users it will have and can purchase resources accordingly - a soccer club, for instance, has a defined membership base.
A public server will either have to upgrade frequently, or keep an eye on it's resources carefully to know when to stop accepting sign ups. It is perfectly acceptable for a listed public server to be _closed_ to new registrations if resources are running low. But it is very poor form to resort to cherry picking to combat the problem. As a public server admin, you may find that you have users you don't really want on your server - but that's the price you pay for serving the public. Rejecting or even expelling people arbitrarily contradicts the spirit of service. If you really wish to cherry-pick spontaneously, you should not ask to be listed as a public server.
A public server will either have to upgrade frequently, or keep an eye on it's resources carefully to know when to stop accepting sign ups. It is perfectly acceptable for a listed public server to be closed to new registrations if resources are running low.
Another difference is admin intention. A community server is generally set up to serve a particular community on a permanent basis, whereas many public admins view their sites as interim homes for users who feel unable to run personal/small group Friendica servers.
***The technical environment - operating system***