client feature support (was: Re: [Standards-JIG] Re: User-Pictures in Jabber)

Peter Saint-Andre stpeter at jabber.org
Thu Jun 22 19:14:36 UTC 2006


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

We have a discussion list where end users can talk about the merits of
various Jabber clients:

http://mail.jabber.org/mailman/listinfo/juser

I agree that it would be great for us to create some pages about feature
support in various clients, as we already do for servers:

http://www.jabber.org/software/servers.shtml

Unfortunately, it's a lot of work to gather all that information, and
there are a lot more clients than there are servers!

I'm cc'ing the JUser list on this message, please discuss the matter
there, not on the Standards list.

Peter

Remko Troncon wrote:
>> But a newbe has really no chance to know what is maybe a lack of features
>> from a client or what is really not implemented yet in the protocol and the
>> clients have no chance then.
> 
> Which features are 'standardized' in a protocol does not really matter from
> the user's point of view. Some things do not have agreed upon protocols,
> and are still present in Jabber clients (for example, whiteboarding). So,
> Jabber clients *always* have 'a chance' to implement something, protocol
> or not.
> 
> As a user, you should just look at clients, see what they can do (either
> by trying, by looking at screenshots, or by looking at the feature list),
> and that's it. As for 'user pictures', almost all Jabber clients support
> them these days.
> 
> cheers,
> Remko
> 


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEmuwbNF1RSzyt3NURAkQ5AKCxUt1+nQZvA66j9yH8dwdkQyD2xACePh3e
39Bntef8949/M4FJU/aD9P4=
=JLzY
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 6866 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060622/3a25d41c/attachment.bin>


More information about the Standards mailing list