Updated Running a public or community server (markdown)

beardy-unixer 2012-06-18 15:30:10 -07:00
parent 0409384e83
commit b812c8950c

@ -483,11 +483,11 @@ This plugin is currently unstable at the moment, so don't allow it.
*Privacy image cache*
When enabled, all external images will be cached on, and served from your own server. This acts as a barrier between your users and unethical networks like Facebook, which include tracking code in their images. Facebook will be able to see your server, but they won't be able to see any of your individual members.
When enabled, all external images will be cached on, and served from your own server. This acts as a barrier between your users and unethical networks like Facebook, which include tracking code in their images. Facebook will be able to see your server, but they won't be able to see any of your individual members. Unfortunately, when using privacy image cache, there is no way to authenticate images with remote servers. This means your users will have to click through to their friends profiles to view private photographs.
Server Impact - there is a noticeable performance hit the first time you activate this as cache for old, but still viewable images is generated in one go. This only happens once, and lasts around an hour. From then on, new images are added "on the fly" rather than lots in one go, and the impact is negligible from this point on. Bandwidth demands are also increased. This is manageable in most cases, but can become a problem if you have lots of users linking lots of external animated gifs.
Impact to support requests - beneficial. Nobody asks why Facebook social graph appears in their stream anymore.
Impact to support requests - beneficial in most cases - nobody asks why Facebook social graph appears in their stream anymore. Possibly higher depending on your users - see the authentication issues above.
-----