+Add an addPlugin call to your config.php with your settings. Please read
+the "Pre-requisites" section of what is required for this to work.
+
+Example
+-------
+The example account "update@site.example" is hosted on a machine which
+can be reached at the hostname "xmpp.site.example".
+
+addPlugin('Xmpp', array(
+ 'user' => 'update',
+ 'server' => 'site.example',
+ 'host' => 'xmpp.site.example',
+ 'password' => '...',
+));
+
+Pre-requisites
+==============
+
+0. You may want to strongly consider setting up your own XMPP server.
+ We highly recommend the XMPP server "Prosody" <https://prosody.im/>
+ because it is actively developed and highly secure and efficient. It
+ is of course also free software under the MIT license. The following
+ three pages will help you get it running, even self-hosted at home:
+
+ 0.1 https://prosody.im/doc/dns
+ 0.2 https://prosody.im/doc/install
+ 0.3 https://prosody.im/doc/configure
+
+1. You must register an XMPP user ID (JID) which is used to send and
+ receive messages. Call it something like "update@site.example" or
+ similar to hint at what the account is made for. You may register
+ the account on any public server (jabber.org, jit.si, etc...) if
+ you cannot run one yourself.
+
+ GNU social will not register anything for you, this must be done
+ manually, preferrably using an XMPP client like Swift, Empathy,
+ Jitsi or maybe even the commandline on your own server. With
+ prosody, that'd be (perhaps prepended with 'sudo'):
+
+ prosodyctl adduser update@site.example
+
+2. Configure your site's XMPP variables, as described below in the
+ Settings section below.
+
+3. Learn to use the GNU social daemons for processing notice queues,
+ background checks and other processes which would be too slow to
+ perform on an active site. Using XMPP requires the "imdaemon" to
+ run, since a long-running XMPP connection is somewhat necessary.