-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday August 04, 2002 10:51, Martijn Klingens wrote:
> And if Jabber was a completely different solution than Kopete then I
> could think of it as an addition. But Jabber is a subset of Kopete, so
> Kopete offers everything that Jabber offers plus the above advantages
> (and many more when used as a chat client).

Jabber supported cross-system interoperability before Kopete ever existed.

As for your comment about proprietary systems blocking Jabber's transports, 
AOL was only blocking centralized transport servers (on the grounds that 
it was compromising their user's passwords, I think).  Local transports 
work the same as ever, as they will be indistinguishable from a free 
software client connecting.  (Is Kopete planning to work with Microsoft 
and AOL to include binary-only plugins or something?)

As for functionality, can you outline what features Kopete supports that 
Jabber doesn't?  File transfers, whiteboards, unicode, multiple 
resources/connections/locations per user, varying single and multi-user 
chat, cross-system interoperability (including IRC and SMTP), and running 
your own server are all possible with Jabber, to my knowledge.

> It centralizes all code, and that can't be bad.

Having a Jabber lib in kdelibs centralizes the code, too.  The difference 
here isn't centralization, but rather whether KDE will standardize one 
service, or rather endorse proprietary systems on equal footing with open 
systems.

- -- 
Neil Stevens - neil@qualityassistant.com
"I always cheer up immensely if an attack is particularly wounding
because I think, well, if they attack one personally, it means they
have not a single political argument left." - Margaret Thatcher
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9TW6gf7mnligQOmERAnohAJwL56mC3BQa0gwR65Rnh4kM5yO+ZQCfR8Bw
vdcAmBY4xQtwvMSI+6t/71w=
=MRsu
-----END PGP SIGNATURE-----