aboutsummaryrefslogtreecommitdiffstats
path: root/protocols/yahoo
Commit message (Collapse)AuthorAgeLines
* I'm still bored on a long flight. Wrote a script to automatically updateWilmer van der Gaast2013-02-21-1/+1
| | | | | | | my copyright mentions since some were getting pretty stale. Left files not touched since before 2012 alone so that this change doesn't touch almost EVERY source file.
* Cleaning up some more Yahoo! symbols.Wilmer van der Gaast2012-10-20-20/+18
|
* Some more removals. Using ifdefs instead of read deletions in Yahoo! dir toWilmer van der Gaast2012-10-20-1/+17
| | | | | | not make merges too complicated (although upstream really seems dead at this point :-/).
* Removing some more cruft now that I've (re)discovered ld garbage collection.Wilmer van der Gaast2012-10-20-4861/+1
| | | | | Mostly stuff related to obsolete Y!MSG login obfuscation schemes.
* Allow building position-independent executables. #981, patch from brainsmoke.Wilmer van der Gaast2012-09-15-1/+1
|
* Rename SRCDIR directory to _SRCDIR_. I guess #907 was caused by SRCDIRWilmer van der Gaast2012-02-11-3/+3
| | | | | unexpectedly being set to something already.
* yahoo: unused-but-set-variablesMiklos Vajna2011-12-06-42/+19
|
* Merge mainline stuff.Wilmer van der Gaast2010-08-31-0/+22
|\
| * Use nifty gcc -MD feature to automatically track .h dependencies of all CWilmer van der Gaast2010-08-27-0/+3
| | | | | | | | | | | | | | | | | | | | files, this finally gives proper dependencies, which means the end of getting broken binaries around headerfile changes, etc. Sure, this may not work on obscurux with superawesomeincompatiblecc while autoconf does, but at least BitlBee's configure script still runs in <1s. :-)
| * Better handling of yahoo add responses: libyahoo2 seems to (IMHO) wronglyWilmer van der Gaast2010-08-22-0/+19
| | | | | | | | | | | | assume that a non-0 status means the contact is on the list already and on-line. This causes ugly "imcb_buddy_status() for unknown handle" msgs.
* | First step in this merge. Mostly a bzr merge and then a cleanup of conflictsWilmer van der Gaast2010-08-24-0/+1
|\ \ | |/ |/| | | | | and parts I want to/have to redo (because of ui-fix).
| * merge in bitlbee 1.2.7Sven Moritz Hallberg2010-06-03-0/+9
| |\
| * \ merge in bitlbee 1.2.5Sven Moritz Hallberg2010-06-03-239/+191
| |\ \
| * \ \ merge in bitlbee 1.2.4Sven Moritz Hallberg2010-06-03-63/+479
| |\ \ \
| * \ \ \ pretty blind try at merging in the latest trunkSven Moritz Hallberg2009-03-12-8/+22
| |\ \ \ \
| * | | | | commit updates by ashish shukla <wahjava@gmail.com>Sven Moritz Hallberg2009-03-12-3/+4
| | | | | |
| * | | | | merge in latest trunkSven Moritz Hallberg2008-07-17-24/+14
| |\ \ \ \ \
| * \ \ \ \ \ merge in upstream changesSven Moritz Hallberg2008-02-16-1/+1
| |\ \ \ \ \ \
| * | | | | | | - add support for setting ops/voice according to OTR msgstateSven Moritz Hallberg2008-02-09-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - add 'otr trust' user command - support non-otr messages during keygen - run otr messages through strip_html - interpret <b> and <i> tags in html messages - record max message size in prpl - add 'encrypted' flag to user_t - cosmetics
* | | | | | | | Pick up away info from Yahoo! too.Wilmer van der Gaast2010-08-21-0/+2
| | | | | | | |
* | | | | | | | OpenSolaris (non-gcc) fixes, patches from Dagobert Michelsen <dam@opencsw.org>Wilmer van der Gaast2010-08-07-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | with some changes.
* | | | | | | | Some fixes for compiler warnings that only show up when compiling with -O2,Wilmer van der Gaast2010-08-05-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | and some additions to the Debian package description.
* | | | | | | | Try another way to silence int-pointer cast warnings in the Yahoo! module.Wilmer van der Gaast2010-08-04-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | -Wno-pointer-to-int-cast is not supported by gcc3.
* | | | | | | | Some NULL pointer checks for libyahoo2 - this code's currently crashingWilmer van der Gaast2010-07-25-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | because BitlBee ignores file transfers.
* | | | | | | | Inverting allow_reconnect logic on login failures. Automatic reconnects wereWilmer van der Gaast2010-07-24-4/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | getting im.bitlbee.org IP-banned sometimes. This fix keeps it happy for some time already.
* | | | | | | | Support buddy groups on Yahoo!Wilmer van der Gaast2010-07-24-3/+30
| | | | | | | |
* | | | | | | | New handling of authorization requests. The old one wasn't fully brokenWilmer van der Gaast2010-07-24-13/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | actually, but it needed a reconnect to see new contacts.
* | | | | | | | Merge complete. It still logs in...Wilmer van der Gaast2010-07-24-1985/+2170
| | | | | | | |
* | | | | | | | This should mostly be a no-op, merging *loads* of whitespace changes fromWilmer van der Gaast2010-07-23-866/+973
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | libyahoo2 so that I can see better what really changed.
* | | | | | | | Show idle + login time info in /WHOIS (if available).Wilmer van der Gaast2010-06-07-3/+1
| | | | | | | |
* | | | | | | | Merging killerbee stuff, bringing all the bleeding-edge stuff together.Wilmer van der Gaast2010-06-07-3/+6
|\ \ \ \ \ \ \ \
| * | | | | | | | Allow one to run the configure script from a different directory and put allWilmer van der Gaast2010-05-25-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | build files in there. I need this to properly make Debian package variants (i.e. libpurple and native).
| * | | | | | | | Mainline merge. (Probably mostly irrelevant for this branch, oh well.)Wilmer van der Gaast2010-05-16-0/+9
| |\ \ \ \ \ \ \ \ | | | |_|_|_|_|_|/ | | |/| | | | | |
| * | | | | | | | Merging head. Most changes are not so relevant because they're to IMWilmer van der Gaast2010-03-20-2/+6
| |\ \ \ \ \ \ \ \ | | | |_|_|_|_|_|/ | | |/| | | | | | | | | | | | | | | | | | | | | | | | modules.
| * | | | | | | | Merging in head.Wilmer van der Gaast2010-03-14-197/+158
| |\ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ \ Merging in mainline, including improved away/status stuff.Wilmer van der Gaast2010-03-07-55/+42
| |\ \ \ \ \ \ \ \ \
| * \ \ \ \ \ \ \ \ \ Merging BitlBee 1.2.4+Wilmer van der Gaast2009-11-23-266/+396
| |\ \ \ \ \ \ \ \ \ \ | | | |_|_|_|_|_|_|_|/ | | |/| | | | | | | |
| * | | | | | | | | | Make purple use BitlBee's event handling API. Since the APIs never reallyWilmer van der Gaast2009-10-11-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | | | | | | | | | Merging head.Wilmer van der Gaast2010-06-01-0/+5
|\ \ \ \ \ \ \ \ \ \ \ | | |_|_|_|_|/ / / / / | |/| | | | | | | | |
| * | | | | | | | | | Add a warning when the user included a domain part in his/her Yahoo! username.Wilmer van der Gaast2010-05-14-0/+5
| | | | | | | | | | |
* | | | | | | | | | | Merging mainline, mostly for chatroom fixes I implemented there.Wilmer van der Gaast2010-05-09-0/+4
|\| | | | | | | | | |
| * | | | | | | | | | Yahoo! seems to echo conference room invitations now, huh? No idea what thisWilmer van der Gaast2010-05-09-0/+4
| | |_|_|_|/ / / / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | is but let's ignore them.
* / | | | | | | | | Misc. cleanup. Also updated the Yahoo! module to deal with struct groupchatWilmer van der Gaast2010-05-08-11/+9
|/ / / / / / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in a GSList so that a default config fully compiles again.
* | | | | | | | | Really set Yahoo! status messages properly. YMSG, how I hate you.Wilmer van der Gaast2010-03-16-1/+1
| | | | | | | | |
* | | | | | | | | Deal with stupid (on first sight, at least) Yahoo! server behaviour causingWilmer van der Gaast2010-03-15-1/+5
| |_|_|/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | double free()s on testing ATM. Apparently it's perfectly legal to give buddy information with an "end buddy" marker but no "begin buddy".
* | | | | | | | Fixed handling of contact lists where at least the first contact is not inWilmer van der Gaast2010-03-13-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | any group yet. Crashing is not the right solution.
* | | | | | | | Yahoo! status updates (at least initial ones, I assume) can be too long toWilmer van der Gaast2010-03-12-25/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | fit into one packet. Yahoo! servers will split them up, and not necessarily on buddy boundaries. Trying to handle this a little bit better now. (Sadly I can't test this myself, I can only see this causing troubles on testing sometimes.)
* | | | | | | | Merging in some code from libyahoo2-trunk that deals better with (initial)Wilmer van der Gaast2010-03-12-194/+146
| |_|/ / / / / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | status updates and cleans up some stale stuff.
* | | | | | | Yahoo! fixes. Turns out the protocol really is somewhat odd.Wilmer van der Gaast2010-03-06-5/+6
| | | | | | |
* | | | | | | Fixed up Yahoo! I'll have to do some more thorough testing of this codeWilmer van der Gaast2010-03-06-45/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | since I may have broken something.