[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kopete-devel
Subject:    Re: [Kopete-devel] kdenonbeta/kopete/protocols
From:       Daniel Stone <dstone () trinity ! unimelb ! edu ! au>
Date:       2003-01-03 0:50:40
[Download RAW message or body]

On Thu, Jan 02, 2003 at 07:44:32PM -0500, Benjamin Meyer scrawled:
> > > TOC is:
> > > a) losing features day by day (yes, features are actually
> > > *disappearing*), b) often broken (many login troubles can be traced down
> > > to TOC breakage), c) superseded by OSCAR, which we have a perfectly fine
> > > library for, d) not used by any serious IM client but ours, making us
> > > somewhat of a joke among the IM world (you have no idea the amount of
> > > shit I got until Kopete got OSCAR support, and still do because TOC's
> > > still there), e) useless.
> 
> Well I will have to take offence to statement D.  I am the author of Kinkatta 
> which is a aim client that uses TOC.  Although Kinkatta can't transfer file 
> or get *icons* I think that the client is pretty darn good.  Some of the 
> applications's design is a little ruff, but it was a learning project.

Sorry, I didn't know Kinkatta was still around. I enquired as to a KDE3
port and was told Kinkatta was dead (can't remember who by tho),
*shrug*.

> But 
> above all else *I* didn't leave the Linux community with yet another half 
> finshed application.  Kinkatta reached 1.0 stable.  Yes there is a bunch in 
> cvs if I ever release 1.1, but 1.0 is out and released.  I know plenty of 
> people who use Kinkatta and use it because they don't care to have something 
> that is buggy or crashes on them.  I used TOC because I didn't care to play 
> the legal game especially after AOL thretened to sue me.  

AOL threatened to sue you? Fun. Was it for a name violation? They
haven't gone after anyone for OSCAR support, including GAIM.

> Honestly I don't really see the point of including anything other then a 
> Jabber client in KDE.

I do, and I'm the author of the Jabber plugin in Kopete. While
transports are a nice idea, they are stupidly flawed in implementation,
and generally blocked; not to mention horrifically buggy.

While I would definitely like to see Kopete's Jabber support hugely
improved (I've not had a home net connection for 5 months), I think that
your suggestion is definitely not the way to go. Hardly any end-users
use Jabber: they use MSN, ICQ, or AIM, depending what country they're
in, and/or when they went to high school (Messenger is the shit here
these days, but if you graduated from high school about 3 years ago, ICQ
was the shit, and still is; apparently AIM is it in America).

-d

-- 
Daniel Stone                                     <dstone@trinity.unimelb.edu.au>
Developer, Trinity College, University of Melbourne

[Attachment #3 (application/pgp-signature)]
_______________________________________________
Kopete-devel mailing list
Kopete-devel@mail.kde.org
http://mail.kde.org/mailman/listinfo/kopete-devel

[prev in list] [next in list] [prev in thread] [next in thread]