Mercurial > pidgin
view src/protocols/oscar/README @ 4269:ff0642fab1d5
[gaim-migrate @ 4520]
Our cable was out again, so I was left doing dull stuff.
I changed the alias_buddy prpl function so that it takes the alias as well as
just the buddy name. It seemed silly not to pass the alias to a function
that changes the alias.
I added a call back for this prpl function in oscar.c. This has the effect
of, when you add/change/remove the alias of a buddy, it also changes the
alias in the server list.
I changed some normalize calls in oscar.c because I think it's better this
way. I could be wrong.
I added the ability to re-request authorization from contacts that have not
authorized you yet. Just right-click on those mofo's.
I shuffled some functions around. oscar.c is a little messy.
Our cable was out some today. Here's the message they have when you call
their customer support:
"All high speed data customers in the 919 and 252 area code may experience
flashing status lights on their cable modems with inability to access
online services at this time."
919 is basically all of Raleigh. I'm going to estimate at least 10,000
people with Time Warner cable. That's a lot of people. Time Warner
sucks. This is from a few hours today:
"15566 packets transmitted, 598 packets received, +8 duplicates, 96% packet loss"
committer: Tailor Script <tailor@pidgin.im>
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Thu, 09 Jan 2003 21:21:00 +0000 |
parents | 424a40f12a6c |
children |
line wrap: on
line source
libfaim pre-0.90 or so ---------------------- This is libfaim, the purpose of which is to implement as much as the AOL AIM/OSCAR protocol as possible (which should be all of it). After over two years of development, its still nowhere close. This is not a full client and never will be. libfaim only implements the routines to implement a client (ie, there's no user interface). Status ------ I would not recommend using this version of libfaim in any form yet. It's beta-quality and I know it leaks memory quite badly. It seems fairly stable, however. YMMV, YAYOR, etc. I suppose I should say regardless of that warning, that several clients use it and people use those clients on a daily basis (in particular, me). Also, you're probably reading this from a CVS version, since I haven't made a release in a very long time. The CVS version changes fairly rapidly when I'm in the mood, so a version you checked out an hour ago may be better or worse than a version you check out now. Building -------- Everything in this libfaim dist should build cleanly on any UNIX(-like) operating system. Originally developed on Linux+glibc. Past versions known to work on Linux+libc5, FreeBSD, HP/UX, Solaris, Mac OS X Server, Win32 using VC++ 98/6 and others. libfaim builds as both libfaim.a and libfaim.so. If your platform for some reason does not support dynamic libraries (eg, you get errors when building libfaim.so), you'll have to tweak the makefiles a bit to get the utils/ directory to build. Otherwise, just do a 'make'. I don't believe I use any specific features GNU make, but if something fails, make sure you have it. And bash too. Accessories ----------- In utils/, you'll find a few things extra: faimtest: very rudimentary front-end. no user interface, but does illustrate the basics of logging in and sending/recieving messages and buddy list notifications. Potential front- end authors start here. aimpasswd: utility to change an AIM password without using a full client. Note that at the time of this writing, this didn't work quite right yet. See the top of the code for latest status. License ------- libfaim is covered under my copyright under the terms of the Lesser GNU Public License, as documented in the file COPYING in the top level directory. Documentation ------------- Unfortunatly, there is not currently any documentation on the libfaim API. Use the source and utils/faimtest/faimtest.c as a reference when coding front-ends. Mailing Lists ------------- Thanks to Sourceforge, we have our mailing lists back. See: http://www.sourceforge.org/mail/?group_id=920 for instructions on subscribing to the lists: libfaim-devel: Discussion of libfaim and its developement. libfaim-aim-protocol: Discussion of the finer points of OSCAR hacking Contact Info ------------ The author (Adam Fritzler), can be reached at mid@auk.cx. Front-end information: http://www.auk.cx/faim/ Protocol information: http://www.auk.cx/faim/protocol/