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:44:34 -07:00
parent 125be55ffc
commit 8df96e4a12
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
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 - [see here](http://friendica.com/node/43).
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) for their sentiments. You may wish to link to that document on your own public site.
***The technical environment - operating system***
@ -28,7 +28,7 @@ On a public or community server, you'll need to block the use of the prefix 'www
Decide whether or not you're going to use SSL now. If you are, you need to mandate it. You can't have a public or community site that allows http and https for one reason - Internet Explorer. A considerable number of your members may be using this browser despite its questionable reputation. These people will be presented with mixed content warnings on practically every page (if there is a single non-SSL element on an SSL page, or vice-versa).
Don't use a self-signed certificate. They're very, very annoying for technical users, and a deal breaker for ordinary users (who are scared off by browser warnings). Get a free certificate from StartSSL instead. For more, see the [SSL How-To](https://github.com/friendica/friendica/wiki/Running-Friendica-with-SSL)
Don't use a self-signed certificate. They're very, very annoying for technical users, and a deal breaker for ordinary users (who are scared off by browser warnings). Get a free certificate from StartSSL instead. For more, see the [SSL How-To](https://github.com/friendica/friendica/wiki/Running-Friendica-with-SSL). If you insist on using a self-signed SSL certificate, don't run a public or community server.
***Other tools***