aboutsummaryrefslogtreecommitdiffstats
path: root/doc/user-guide/Installation.xml
diff options
context:
space:
mode:
authordequis <dx@dxzone.com.ar>2018-01-10 00:05:23 -0300
committerdequis <dx@dxzone.com.ar>2018-01-10 00:05:23 -0300
commit7ec2ce8fd7d30a536823ef9e08a3dad80ce76d4e (patch)
tree15f0ad9918bd45898308683f6c549af5fa8e79f4 /doc/user-guide/Installation.xml
parent4a9c6b0b15eb3738897dc1635fda2e4be67414ad (diff)
Remove MSN. Use the skypeweb purple plugin instead.
RIP As per http://ismsndeadyet.com/ all versions up to MSNP22 died a few months ago. We had a MSNP21 implementation, bought us two extra years. Implementing MSNP24 is technically possible but also pointless given skypeweb, and the authentication requires some fairly messed up crypto and legacy old-skype-protocol servers. For a long time I tried to reverse a potentially simpler method, and got fairly close, but never completed that. I haven't done any attempts to continue it in the last year, so I'm fine with giving up at this point.
Diffstat (limited to 'doc/user-guide/Installation.xml')
-rw-r--r--doc/user-guide/Installation.xml5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/user-guide/Installation.xml b/doc/user-guide/Installation.xml
index 9d555d46..879649f6 100644
--- a/doc/user-guide/Installation.xml
+++ b/doc/user-guide/Installation.xml
@@ -35,7 +35,7 @@ specify them all separately, just specifying prefix (or keeping the default
<listitem><para>config - The place where BitlBee will save all the per-user
settings and buddy information. <filename>/var/lib/bitlbee/</filename>
is the default value.</para></listitem>
-<listitem><para>msn, jabber, oscar, twitter - By default, support for all
+<listitem><para>jabber, oscar, twitter - By default, support for all
these IM-protocols (OSCAR is the protocol used by both ICQ and AIM) will
be compiled in. To make the binary a bit smaller, you can use these options
to leave out support for protocols you're not planning to use.</para></listitem>
@@ -49,8 +49,7 @@ will be stripped out to make it as small as possible. If you don't want this
<listitem><para>flood - To secure your BitlBee server against flooding attacks,
you can use this option. It's not compiled in by default because it needs
more testing first.</para></listitem>
-<listitem><para>ssl - The MSN and Jabber modules require an SSL library for
-some of their tasks. BitlBee can use three different SSL libraries: GnuTLS,
+<listitem><para>ssl - BitlBee can use three different SSL libraries: GnuTLS,
mozilla-nss and OpenSSL. (OpenSSL is, however, a bit troublesome because of
licensing issues, so don't forget to read the information configure will
give you when you try to use OpenSSL!) By default, configure will try to