aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Added enough code to handle one class of queries (action-based), enoughWilmer van der Gaast2009-11-25-4/+86
| | | | | | | | to make the "Please accept this SSL certificate" question work. Need to extend the BitlBee API a bit to *really* support this well though (yes/no is not enough).
* Oops, forgot to change one protocol name string pointer..Wilmer van der Gaast2009-11-23-1/+1
|
* Fixed compatibility with non-libpurple version: oscar is now recognizedWilmer van der Gaast2009-11-23-23/+29
| | | | | as a protocol name, and removed prpl- hack from nogaim.c.
* Merging BitlBee 1.2.4+Wilmer van der Gaast2009-11-23-289/+503
|\
| * "chat add", not chat_addWilmer van der Gaast2009-10-24-1/+1
| |
| * Shuffling a few more #includes. Much more shuffling will be needed.Wilmer van der Gaast2009-10-23-4/+8
| |
| * Don't include chat.h from bitlbee.h. make install-dev doesn't installWilmer van der Gaast2009-10-22-1/+11
| | | | | | | | | | | | chat.h and it shouldn't ... but things broke because bitlbee.h includes it. Fixes #534.
| * Hah. Forgot to update the version number in bitlbee.h. I really haven't done1.2.4Wilmer van der Gaast2009-10-17-1/+1
| | | | | | | | | | this for a while.
| * I call you BitlBee 1.2.4. I hope. :-)Wilmer van der Gaast2009-10-17-0/+17
| |
| * If you can't find what you expect in an IQ packet, it doesn't mean it'sWilmer van der Gaast2009-10-17-2/+3
| | | | | | | | | | | | incorrect, so stop spamming. Ideally it should return a feature-not- implemented but I'll do that later.
| * Document password-protected rooms.Wilmer van der Gaast2009-10-17-0/+4
| |
| * Valgrind pointed me at some memory leaks in the Yahoo! codek, including oneWilmer van der Gaast2009-10-17-17/+22
| | | | | | | | | | that existed for a while already. Fixed.
| * Turns out I *did* implement HTTPS auth for Yahoo! myself already, but IWilmer van der Gaast2009-10-13-184/+178
| | | | | | | | | | | | kept it as a patch somewhere in my homedir because I thought I didn't need it. I like this code more so I'll use it instead.
| * Setting Yahoo! away states works again.Wilmer van der Gaast2009-10-10-23/+30
| |
| * Fixed an ugly bug in the write handler that may have caused many weird bugsWilmer van der Gaast2009-10-10-3/+1
| | | | | | | | | | | | for a while already by only sending one packet even if more of them were generated during an event cycle.
| * More Yahoo! fixes: Adding and removing buddies works, and for the firstWilmer van der Gaast2009-10-10-41/+167
| | | | | | | | | | | | | | | | | | time buddy add requests are actually handled; from what I can see this simply didn't exist in libyahoo2 yet so far. :-( I melded pieces of changes from http://geny.sf.net/ to make this stuff work.
| * Added imcb_ask_auth() instead of reimplementing authorization requestsWilmer van der Gaast2009-10-10-15/+63
| | | | | | | | | | in every protocol module.
* | Adding/removing contacts now works.Wilmer van der Gaast2009-11-23-3/+19
| |
* | I think daemon mode and libpurple won't go together very well for now sinceWilmer van der Gaast2009-10-14-1/+9
| | | | | | | | | | | | libpurple seems to keep track of a merged contact list. For now people shouldn't be trying this combination.
* | Store real names in /whois.Wilmer van der Gaast2009-10-12-0/+6
| |
* | Automatically try prpl-$proto if $proto doesn't exist, and disable nativeWilmer van der Gaast2009-10-12-11/+29
| | | | | | | | | | protocol modules if purple is enabled; they don't go together very well.
* | Oops, forgot to drop a printf() of all away states for debugging.Wilmer van der Gaast2009-10-12-3/+0
| |
* | Support for setting away states. Somewhat hackish but this stuff isWilmer van der Gaast2009-10-12-5/+24
| | | | | | | | | | hopelessly complicated in libpurple anyway..
* | Fixed account cleanup (use remove, not destroy) and now using user's accountWilmer van der Gaast2009-10-11-20/+58
| | | | | | | | | | settings.
* | Copy all the string/bool/int account settings with their defaults toWilmer van der Gaast2009-10-11-17/+45
| | | | | | | | | | "account set". They can be changed, but changes don't yet have any effect.
* | Some valgrind cleaning/type safety fixes.Wilmer van der Gaast2009-10-11-6/+21
| |
* | Added handing of away states/messages of contacts.Wilmer van der Gaast2009-10-11-9/+10
| |
* | Fixing a few compiler warnings and cleaning up the last remains ofWilmer van der Gaast2009-10-11-36/+24
| | | | | | | | | | GLib-specific code.
* | Hacked up a B_EV_FLAG_FORCE_REPEAT event handler flag to make libpurpleWilmer van der Gaast2009-10-11-4/+15
| | | | | | | | | | happy.
* | Make purple use BitlBee's event handling API. Since the APIs never reallyWilmer van der Gaast2009-10-11-133/+95
| | | | | | | | | | | | | | | | | | | | diverged too much this is fairly transparent. I did rename and redefine GAIM_INPUT_* variables to really make it work without adding another stupid layer in between. One problem left, the new libpurple input API doesn't care about return values. Fixing that in the next CL.
* | Added some debugging stuff and handling (better said, ignoring) of eventsWilmer van der Gaast2009-10-08-10/+50
| | | | | | | | | | for closed connections where necessary.
* | Support for sending messages.Wilmer van der Gaast2009-10-06-1/+13
| |
* | Receive messages.Wilmer van der Gaast2009-10-06-2/+14
| |
* | Getting a contact list and online status now. Time to handle messages.Wilmer van der Gaast2009-10-06-2/+49
| |
* | Moved some stuff around, got something that logs in and reports status now.Wilmer van der Gaast2009-10-06-43/+109
| |
* | Something that compiles and runs, but otherwise utterly useless. Added aWilmer van der Gaast2009-10-05-0/+303
|/ | | | | | protocols/purple/ module and included it in the build system. Already picks up all the supported protocols and adds them individually.
* Fixed embarassing early free() bug that sat in the WATCH command handlingWilmer van der Gaast2009-10-04-1/+1
| | | | | | for *years*. I guess it took a while for IRC clients to actually use that functionality...
* Fixing a crash bug that causes crashes only with buggy Jabber conferenceWilmer van der Gaast2009-10-04-6/+9
| | | | | | servers, sending a "you left this chat" without first acknowledging you entering it.
* Cleaned up Yahoo! fix: Error handling, and also not crashing when theWilmer van der Gaast2009-10-03-77/+66
| | | | | connection disappears again before authentication finishes.
* Yahoo! can log in again. This code still needs major cleanups, use it onlyWilmer van der Gaast2009-10-03-9/+306
| | | | | if you're very desparate.
* Fixed fd leak in ini.c. How could I miss this one.. :-(Wilmer van der Gaast2009-07-20-2/+6
|
* Fixed another crash bug (this one was triggered by just typing "chat set").Wilmer van der Gaast2009-06-24-0/+2
|
* Fixed crash on setting an unknown setting.Wilmer van der Gaast2009-06-24-1/+1
|
* Fixed compatibility with AIM mobile messages. Should work according toWilmer van der Gaast2009-06-18-1/+12
| | | | | | reports in bug #88 (where this patch comes from) and #bitlbee. Not sure about side effects, one way to find out...
* Fixed a bug that caused crashes when joining certain kinds of Google TalkWilmer van der Gaast2009-06-03-2/+4
| | | | | | | | | chatrooms. Doesn't seem to be Google Talk specific, other than that this is the first time I see empty <x xmlns="http://jabber.org/protocol/muc#user"/> elements that cause this crash. A more proper/efficient fix may be to just move the break outside the inner if.
* Fixed an embarassing typo that even fooled me into believing BitlBee isWilmer van der Gaast2009-01-13-2/+2
| | | | | broken. :-(
* Simplified ini parser code a bit more. Not using strtok() after all sinceWilmer van der Gaast2008-12-25-30/+27
| | | | | | I can't find a guarantee that it's okay with me further mutilating the strings. :-)
* First version of new ini parser. Will just attempt to simplify code a bit.Wilmer van der Gaast2008-12-24-42/+98
|
* Detect disconnects caused by concurrent logins or rate limiting, and disableWilmer van der Gaast2008-12-14-2/+29
| | | | | auto-reconnect in those cases to prevent loops.
* Dropping warnings about unknown JIDs since they're spammy (mostly show upWilmer van der Gaast2008-12-14-4/+6
| | | | | | when the user logs in from mulitple locations) and the irc->debug setting shouldn't be read from inside the IM modules.