Updated Running a public or community server (markdown)

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

@@ -434,141 +434,206 @@ As the name suggests, this is a plugin for public servers, and it's a vital one
 
 This is essential.  Once your item table gets up to half a million entries, even the best sites grind to a halt.  Hardly any users expire their posts via their personal settings, despite both the massive privacy and performance this offers.  Set a standard expiration time, or you'll regret it.  Users can override this value.
 
-3) Remove NEW users who have registered, but then never logged in after nologin days:
+3) Remove NEW users who have registered, but then never logged in after _nologin_ days:
 
 `$a->config['public_server']['nologin'] = 30;`
 
 Before using this remember what happened when you joined Facebook.  You signed up to look at a photograph, then never looked at your account again for years... until suddenly all your friends turned up, and you got a million friend requests in one day.  It might be best to let never-used accounts live, if you can afford the space. But if you are short of resources, this option removes users who have not logged in for the number of days specified here.
 
-4) Remove users who last logged in over flagusers days ago.  
+4) Remove users who last logged in over _flagusers_ days ago.  
 
 `$a->config['public_server']['flagusers'] = 146;`
 
-This is not useful for new public/community servers - it is intended for sites created _before_ the public server plugin was enabled.  It will flag users for deletion when they haven't logged in for the number of days specified here. If you do use this, make sure you give it a large value.  If somebody goes on holiday to find their account is gone when they come back, they'll be very cross indeed.
+This is not useful for _new_ public/community servers - it is intended for sites created _before_ the public server plugin was enabled.  It will flag users for deletion when they haven't logged in for the number of days specified here. If you do use this, make sure you give it a large value.  If somebody goes on holiday to find their account is gone when they come back, they'll be very cross indeed.
 
-For users who last logged in over flagposts days ago set post expiry days to flagpostsexpire `$a->config['public_server']['flagposts'] = 90;`
+5) Set posts by users who last logged in a long time ago to expire (without expiring their accounts).
+
+For users who last logged in over _flagposts_ days ago set post expiry days to _flagpostsexpire_ 
+
+`$a->config['public_server']['flagposts'] = 90;`
 `$a->config['public_server']['flagpostsexpire'] = 146;`
 
-Use the first option to mark an account as inactive if a user hasn't logged in for that many days.  In the example, an account will be marked inactive if the user hasn't been logged in for 90 days.  Once a user has been marked inactive, we will expire their posts after the number of days specified in flagpostsexpire.  In the example, if an account is inactive, the posts belonging to that account will be deleted after 146 days.
+(Use the first option to mark an account as inactive if a user hasn't logged in for that many days.  In the example, an account will be marked inactive if the user hasn't been logged in for 90 days.  Once a user has been marked inactive, we will expire their posts after the number of days specified in flagpostsexpire.  In the example, the posts belonging to the inactive account will be deleted after 146 days.)
 
-Server impact: beneficial
-Impact to support requests: Low, if you take the above points into consideration.
+-----
 
 *Random Planet Imperial Edition*
-This is the same as random location, but using planets from StarWars or StarTrek, one of the two.
+
+This is the same as random location, but using planets from StarWars or StarTrek.
 
 Server impact - negligible. 
-Impact to support requests - low, but see OpenStreetMap.
+
+Impact to support requests - low.
+
+-----
 
 *Poor Man Cron*
-An alternative poor man's cron. Only use this if you don't have a choice. It is an inferior alternative to a true cron.  Don't run a community/public server if you need this.
 
-Server impact - site killer. 
-Impact to support requests - beneficial; you can't afford to have users if you need this.  No users means no support requests.
+Don't ever run a community/public server if you need this. It's an unefficient cron alternative for personal sites.
+
+-----
 
 *Posterus connector*
+
 Allows cross posting to Posterous.
 
-Server impact - it's unstable at the moment, don't allow it.
-Impact to support requests - high, wait until it's fixed properly.
+This plugin is currently unstable at the moment, so don't allow it.
+
+-----
 
 *Privacy image cache*
-Version 0.1 is buggy, so I don't use it, so I'm not certain.
 
-Server impact - could go either way. 
-Impact to support requests - ridiculously high when images on SSL were replaced to links with images instead.
+Version 0.1 is buggy and should probably not be used on a public/community until it is repaired.
+
+-----
 
 *Quick Comments*
-Allows two click comments.
+
+Allows two click comments with user-defined text or smilies.
 
 Server impact - negligible. 
+
 Impact to support requests - negligible.
 
+-----
+
 *Random place*
+
 Set a random location for each of your posts.
 
 Server impact - low. 
-Impact to support requests - negligible, but see OpenStreetMap.
+
+Impact to support requests - negligible.
+
+-----
 
 *Show more*
+
 Collapses long posts, and offers a "show more" option.
 
 Server impact - negligible. 
+
 Impact to support requests - high. If you can believe it, people have edited themes instead of just turning this off! They'd likely do the same the other way around as well though.
 
-*Smiley pack*
-A bunch of smileys to promote the spread of brain cancer.
+-----
 
-Server impact - low. 
-Impact to support requests - low, but you'll hate yourself for enabling it, and you'll have to spend some time telling sane people how to turn smileys off.
+*Smiley pack*
+
+A pack of emoticons.
+
+Server impact - low.
+ 
+Impact to support requests - low, but you may spend some time telling people how to turn smilies of, if they are annoyed by them.
+
+-----
 
 *Adult smilies*
-A handful of adult smilies. Don't turn this on if you've got kids or self-righteous users.
+
+A handful of adult smilies, not necessarily 'politically correct'. Don't turn this on if you've got kids or sensitive users.
 
 Server impact - negligible. 
+
 Impact to support requests - negligible.
 
+-----
+
 *Sniper*
+
 Inserts the Hot Shot Snipers game into your apps menu.
 
 Server impact - low. 
+
 Impact to support requests - negligible.
 
-*StatusNet Connector*
-This allows users to "remote control" an existing StatusNet account, rather than use the built in StatusNet support which would behave like a new account.
+-----
 
-Server impact - unsure, AFAIK only one person ever used it here. 
-Impact to support requests - setup the app for them, and low, leave them to do it themselves, then high.
+*StatusNet Connector*
+
+This allows users to "remote control" an existing StatusNet account, rather than use the built in StatusNet support which would behave like a separate account when viewed from identi.ca or other StatusNet instances.
+
+Server impact - usually low.
+
+Impact to support requests - users have to set this connector up for themselves when the plugin is enabled. This consists of more than merely entering a username and password, so you may be faced with questions. If you enable the plugin, be sure to try it out yourself in order to have the answers.
+
+-----
 
 *TestDrive*
-Expires accounts after n days. Don't use this on a community server.
+
+Expires accounts after n days. Don't use this on a public or community server. It is for demo sites.
+
+-----
 
 *TicTacToe*
+
 Adds 3D Noughts and Crosses to your apps menu.
 
 Server impact - negligible. 
+
 Impact to support requests - negligible.
 
+-----
+
 *Tumblr connector*
+
 Allows users to cross post to Tumblr.
 
 Server impact - low. Potentially high if you get a lot of users posting to Tumblr with lots of posts, but this rarely happens. 
+
 Impact to support requests - low.
 
+-----
+
 *Twitter connector*
+
 Allows users to post to Twitter.
 
 Server impact - moderate; lots of people use it far too much. 
+
 Impact to support requests - low.
 
-*unhosted remote storage*
-Allows users to connect to unhosted remote storage.
+-----
 
-Server impact - dunno. 
-Impact to support requests - nobody uses it yet, but when they do, this is likely to be high.
+*unhosted remote storage*
+
+Allows users to connect to remote storage using their Friendica identities. This is for use with so-called unhosted apps, of which few currently exist. It may be a very useful addon in future, allowing very easy integration of external functionality. But at the moment, don't enable it on a public/community server.
+
+-----
 
 *Viewsrc*
-Adds a "view source" link to public posts. This is so essential, it should really be in core. You can't live without this addon.
+
+Adds a "view source" link to public posts. This is so essential that it should really be in core. 
 
 Server impact - negligible. 
+
 Impact to support requests - nil.
 
+-----
+
 *Widgets*
+
 Add friend/like widgets to other sites.
 
 Server impact - depends how much they're used. 
+
 Impact to support requests - low.
 
+-----
+
 *WordPress connector*
+
 Allow cross posting to WordPress.
 
 Server impact - low.  Potentially high if you get a lot of users posting to WordPress with lots of posts, but this rarely happens. 
-Impact to support requests - low to moderate. It seems to fart quite a lot on some self-hosted WordPress installs for unknown reasons.
+
+Impact to support requests - low to moderate. For unknown reasons, _some_ self-hosted WordPress installs have problems with this one, but it usually works fine.
+
+-----
 
 *Yourls*
-Specify a yourls shortener for use with StatusNet and Twitter, which work fine without one, so I don't know what this is for, really.
 
-Server impact - dunno. Impact to support requests - dunno.
+Specify a yourls shortener for use with StatusNet and Twitter. This is interesting if you want to use your own URL shortener for privacy reasons or to count clicks. But since only one yourls site can be specified, there is not much use for this plugin on a public or community server.
+
+-----
 
 
 ***Advanced Options***