annotate libfaim/README @ 312:3069be4c291e

[gaim-migrate @ 322] I don't know why I did this. I have homework due in 15 hours that I haven't started yet, and it's in a language I don't know and it's a project I don't understand. If my teacher knew about this, he would be pissed. He looks pissed all the time, even when he's not. When he smiles he looks devilish. Maybe I only think that because literally half the class flunked the midterm. I am not joking about that. More people got F's than A, B, and C combined. It's 2 am and the homework's due at 5 tomorrow so what do I do? Get chat to work. Wow. That's going to look good on my resume. "Why did you flunk this class?" "Because I was getting chat in Instant Messenger to work." Not that that's not something to be proud of, but I wonder which is more important to employers. The big battle, experience versus education. Just because you got good grades in college doesn't mean you're smarter than someone who flunked, it just means you put in the effort necessary to get a better grade and the other person didn't. Maybe the person who flunked was working on real honest-to-god actually *used* software, as opposed to some stupid tree that only gets used for a fringe branch of computer science that doesn't offer much more than a normal heap or binary search tree offers. Maybe the person was out there reverse-engineering protocols and allowing cross- platform communication to occur, creating interoperability and causing a greater demand not only for the product, but for the platform it runs on! Given the choices, who would you pick? Someone who was told how to code a tree and managed to get it to work, or someone who increases your userbase and marketability? Enough of my rant for a while. I've had waaaaay too much sugar (gummy candy is deadly). committer: Tailor Script <[e-mail]>

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 a year 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).


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 [e-mail].

Front-end information:
  http://www.auk.cx/faim/
Protocol information:
  http://www.auk.cx/faim/protocol/