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

Updated Running a public or community server (markdown)

MartinFarrent 2012-05-24 23:42:10 -07:00
parent 30785703db
commit 125be55ffc
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -12,7 +12,7 @@ For instance, registration policy is affected by these differences. If you run a
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.
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.
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 - [see here](http://friendica.com/node/43).
***The technical environment - operating system***