Changeset 85d7b85 for doc/CHANGES
- Timestamp:
- 2008-04-02T14:22:57Z (17 years ago)
- Branches:
- master
- Children:
- f9dbc99
- Parents:
- 875ad42 (diff), dd34575 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/CHANGES
r875ad42 r85d7b85 1 Version 1.2.1: 2 - Fixed proxy support. 3 - Fixed stalling issues while connecting to Jabber when using the OpenSSL 4 module. 5 - Fixed problem with GLib and ForkDaemon where processes didn't die when 6 the client disconnects. 7 - Fixed handling of "set charset none". (Which pretty much breaks the account 8 completely in 1.2.) 9 - You can now automatically identify yourself to BitlBee by setting a server 10 password in your IRC client. 11 - Compatible with all crazy kinds of line endings that clients can send. 12 13 Finished ... 14 15 Version 1.2: 16 - Added ForkDaemon mode next to the existing Daemon- and inetd modes. With 17 ForkDaemon you can run BitlBee as a stand-alone daemon and every connection 18 will run in its own process. No more need to configure inetd, and still you 19 don't get the stability problems BitlBee unfortunately still has in ordinary 20 (one-process) daemon mode. 21 - Added inter-process/connection communication. This made it possible to 22 implement some IRC operator features like WALLOPs, KILL, DIE, REHASH and 23 more. 24 - Added hooks for using libevent instead of GLib for event handling. This 25 should improve scalability, although this won't really be useful yet because 26 the one-process daemon mode is not reliable enough. 27 - BitlBee now makes the buddy quits when doing "account off" look like a 28 netsplit. Modern IRC clients show this in a different, more compact way. 29 (This can be disabled if your client doesn't support this.) 30 - GLib 1.x compatibility was dropped. BitlBee now requires GLib 2.4 or newer. 31 This allows us to use more GLib features (like the XML parser). By now GLib 32 1.x is so old that supporting it really isn't necessary anymore. 33 - Many, many, MANY little changes, improvements, fixes. Using non-blocking 34 I/O as much as possible, replaced the Gaim (0.59, IOW heavily outdated) 35 API, fixed lots of little bugs (including bugs that affected daemon mode 36 stability). See the bzr logs for more information. 37 - One of the user-visible changes from the API change: You can finally see 38 all away states/messages properly. 39 - Added units tests. Test coverage is very minimal for now. 40 - Better charset handling: Everything is just converted from/to UTF-8 right 41 in the IRC core, and charset mismatches are detected (if possible) and the 42 user is asked to resolve this before continuing. Also, UTF-8 is the default 43 setting now, since that's how the world seems to work these days. 44 - One can now keep hashed passwords in bitlbee.conf instead of the cleartext 45 version. 46 - Most important change: New file format for user data (accounts, nicks and 47 settings). Migration to the new format should happen transparently, 48 BitlBee will read the old files and once you quit/save it will save in the 49 new format. It is recommended to delete the old files (BitlBee doesn't do 50 this automatically, it will just ignore them) since they won't be used 51 anymore (and since the old file format is a security risk). Some advantages 52 of this file format switch: 53 * Safer format, since the identify-password is now salted before generating 54 a checksum. This way one can't use MD5 reverse lookup databases to crack 55 passwords. Also, the IM-account passwords are encrypted using RC4 instead 56 of the simple obfuscation scheme which BitlBee used so far. 57 * Easier to extend than the previous format (at least the .nicks format was 58 horribly limited). 59 * Nicknames for buddies are now saved per-account instead of per-protocol. 60 So far having one buddy on multiple accounts of the same protocol was a 61 problem because the nicks generated for the two "instances" of this buddy 62 were very unpredictable. 63 NOTE: This also means that "account del" removes not just the account, 64 BUT ALSO ALL NICKNAMES! If you're changing IM accounts and don't want to 65 lose the nicknames, you can now use "account set" to change the username 66 and password for the existing connection. 67 * Per-account settings (see the new "account set" command). 68 - A brand new Jabber module. Besides the major code cleanup, it also has 69 has these new features: 70 * Pretty complete XMPP support: RFC3920, RFC3921 plus a number of XEPs 71 including XEP45, XEP73 and XEP85. (See http://www.xmpp.org/ for what all 72 these things mean exactly.) Privacy lists are not supported for obvious 73 reasons. 74 * This complete support also includes TLS and SASL support and SRV record 75 lookup. This means that specifying a server tag for connections should 76 (almost) never be necessary anymore, BitlBee can find the server and can 77 automatically convert plaintext connections to TLS-encrypted ones. 78 * XEP45: Jabber chatroom support! 79 * XEP85 means typing notifications. The older XEP22 (still used by some 80 clients including Gaim <2.0) is not supported. 81 * Better handling of buddies who have more than one resource on-line. As 82 long as one resource is on-line (and visible), BitlBee will show this. 83 (The previous module didn't keep track of resources and sent an offline 84 event as soon as any resource disappears.) 85 * You can now set your resource priority. 86 * The info command now gives away state/message information for all 87 resources available for that buddy. (Of course this only works if the 88 buddy is in your contact list.) 89 * An XML console (add xmlconsole to your contact list or see "help set 90 xmlconsole" if you want it permanently). 91 - The Yahoo! module now says it supports YMSG protocol version 12, which will 92 hopefully keep the Yahoo module working after 2008-04-02 (when Yahoo! is 93 dropping support for version 6.x of their client). 94 - MSN switchboard handling changes. Hopefully less messages will get lost now, 95 although things are still not perfect. 96 97 Finished 17 Mar 2008 98 99 Version 1.0.4: 100 - Removed sethostent(), which causes problems for many people, especially on 101 *BSD. This is basically the reason for this release. 102 - "allow" command actually displays the allow list, not the block list. 103 - Yahoo away state/msg fix. 104 - Don't display "Gender: Male" by default if nothing's filled in (OSCAR 105 "info" command) 106 - Fixed account cleanup (possible infinite loop) in irc_free(). 107 - Fixed configdir error message to not always display the compile-time 108 setting. 109 110 Finished 20 Aug 2007 111 112 Version 1.0.3: 113 - Fixed ugliness in block/allow list commands (still not perfect though, the 114 list is empty or not up-to-date for most protocols). 115 - OSCAR module doesn't send the ICQ web-aware flag anymore, which seems to 116 get rid of a lot of ICQ spam. 117 - added show_got_added(), BitlBee asks you, after authorizing someone, if you 118 want to add him/her to your list too. 119 - add -tmp, mainly convenient if you want to talk to people who are not in 120 your list. 121 - Fixed ISON command, should work better with irssi now. 122 - Fixed compilation with tcc. 123 - Fixed xinetd-file. 124 - Misc. (crash)bug fixes, including one in the root command parsing that 125 caused mysterious error messages sometimes. 126 127 Finished 24 Jun 2006 (Happy 4th birthday, BitlBee!) 128 129 Version 1.0.2: 130 - Pieces of code cleanup, fixes for possible problems in error checking. 131 - Fixed an auto-reconnect cleanup problem that caused crashes in daemon mode. 132 - /AWAY in daemon mode now doesn't set the away state for every connection 133 anymore. 134 - Fixed a crash-bug on empty help subjects. 135 - Jabber now correctly sets the current away state when connecting. 136 - Added Invisible and Hidden to the away state alias list, invisible mode 137 should be pretty usable now. 138 - Fixed handling of iconv(): It's now done for everything that goes between 139 BitlBee and the IRC client, instead of doing it (almost) every time 140 something goes to or come from the IM-modules. Should've thought about 141 that before. :-) 142 - When cleaning up MSN switchboards with unsent msgs, it now also says which 143 contact those messages were meant for. 144 - You can now use the block and allow commands to see your current block/ 145 allow list. 146 147 Finished 1 Apr 2006 148 149 Version 1.0.1: 150 - Support for AIM groupchats. 151 - Improved typing notification support for at least AIM. 152 - BitlBee sends a 005 reply when logging in, this informs modern IRC clients 153 of some of BitlBee's capabilities. This might also solve problems some 154 people were having with the new control channel name. 155 - MSN switchboards are now properly reset when talking to a person who is 156 offline. This fixes problems with messages to MSN people that sometimes 157 didn't arrive. 158 - Fixed one of the problems that made BitlBee show online Jabber people as 159 offline. 160 - Fixed problems with commas in MSN passwords. 161 - Added some consts for read-only data, which should make the BitlBee per- 162 process memory footprint a bit smaller. 163 - Other bits of code cleanup. 164 165 Finished 14 Jan 2006 166 1 167 Version 1.0: 2 168 - Removed some crashy debugging code.
Note: See TracChangeset
for help on using the changeset viewer.