Changeset a906b77 for doc


Ignore:
Timestamp:
2013-01-06T12:55:46Z (11 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:
2 edited

Legend:

Unmodified
Added
Removed
  • doc/CHANGES

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

    rcfbecc9 ra906b77  
    386386</sect1>
    387387
     388<sect1 id="whatsnew030200">
     389<title>New stuff in BitlBee 3.2</title>
     390
     391<para>
     392Upgradeed to Twitter API version 1.1. This is necessary because previous
     393versions will stop working from March 2013. At the same time, BitlBee now
     394supports the streaming API and incoming direct messages.
     395</para>
     396</sect1>
     397
    388398</chapter>
Note: See TracChangeset for help on using the changeset viewer.