[1935] in im locker bugs
Re: AIM clients update
daemon@ATHENA.MIT.EDU (Ken T Takusagawa)
Thu Jun 29 01:10:23 2006
Date: Thu, 29 Jun 2006 01:10:16 -0400 (EDT)
From: Ken T Takusagawa <kenta@MIT.EDU>
To: Matthew Goldstein <austein@MIT.EDU>
cc: bug-im@MIT.EDU
In-Reply-To: <Pine.LNX.4.62L.0606282021240.16369@lockpick.mit.edu>
Hi Matt,
Whereas I don't speak for all the maintainers, I haven't
seen much activity in updating the im locker recently, so I
wouldn't expect much. However, you seem to be interested in
locker maintenance, so I have given you write permissions to
the locker.
If you have any questions, or are not interested in
maintaining the locker, feel free to write.
Are you familiar with "owl" in the ktools locker, which can
be used as a text-based AIM client?
--ken
On Wed, 28 Jun 2006, Matthew Goldstein wrote:
> Hi,
>
> In August of last year, AOL killed the TOC protocol used by many third-party
> clients. This disabled the AIM support on several of the clients in the IM
> locker.
> Two of these, centericq and naim, were switched over to a different protocol
> within a month or two.
> Unfortunately, the IM locker has not been upgraded to these new versions over
> the course of the year, leaving no ncurses-based AIM client functioning in the
> locker.
>
> Are you planning on maintaining the locker with recent clients? What can I do
> to see that the IM locker is usable for this again?
>
> --Matt
>
