Changeset a906b77 for doc

Timestamp:

2013-01-06T12:55:46Z (12 years ago)

Author:

Wilmer van der Gaast <wilmer@…>

Branches:

master

Children:

955aad8

Parents:

cfbecc9

Message:

Preparing for 3.2 release, hopefully very soon.

Location:

doc

Files:

• CHANGES (modified) (1 diff)
• user-guide/misc.xml (modified) (1 diff)

doc/CHANGES

@@ -3 +3 @@
 
 http://bugs.bitlbee.org/bitlbee/timeline?daysback=90&changeset=on
+
+Version 3.2:
+- By far the most important change, a thorough update to the Twitter
+  module:
+  * Now using Twitter API 1.1,
+  * which means it's now using JSON instead of XML,
+  * which means access to the streaming API (Twitter only, other Twitter
+    API services don't seem to have it). No more 60-second polls, #twitter
+    looks even more like real IRC now!
+  * Also, the streaming API means nice things like receiving DMs.
+  * show_ids, already enabled by default for a while, now uses hexa-
+    decimal numbers, which means a 256-entry backlog instead of just 100.
+  * Added a mode=strict setting which requires everything to be a command.
+    The "post" command should then be used to post a Tweet.
+- Jabber module bugfix that fixes connection issues with at least Google
+  Talk but reportedly some other servers (OpenFire?) as well.
+- SSL modules improved a little bit. GnuTLS module now supports SNI and
+  session caching. Shouldn't change much, but hopefully reduces latency
+  and bandwidth usage a little bit.  
+- A bunch of other fixes/improvements here and there.
+
+Finished ... 2013
 
 Version 3.0.6:

doc/user-guide/misc.xml

@@ -386 +386 @@
 </sect1>
 
+<sect1 id="whatsnew030200">
+<title>New stuff in BitlBee 3.2</title>
+
+<para>
+Upgradeed to Twitter API version 1.1. This is necessary because previous
+versions will stop working from March 2013. At the same time, BitlBee now
+supports the streaming API and incoming direct messages.
+</para>
+</sect1>
+
 </chapter>