Comments on: iChat Clarifications http://missig.org/julian/blog/2005/05/14/ichat-clarifications/ Former Open Source programmer with experience at companies like IBM and Apple. Now a UI Designer with an education in Cognitive Science and Human-Computer Interaction. Sat, 22 Nov 2008 14:04:34 +0000 http://wordpress.org/?v=2.3.3 By: Sparks http://missig.org/julian/blog/2005/05/14/ichat-clarifications/#comment-7021 Sparks Sun, 15 May 2005 11:12:46 +0000 http://missig.org/julian/blog/2005/05/14/ichat-clarifications/#comment-7021 FWIW, Julian, I only wrote support for iChat's mutant HTML variant on input. I generate strict XHTML-IM on output, no matter what's on the other end. I tend to think this is the 'right' way to do things in terms of client design: be liberal in what you accept as input across the wire, but strict in what you generate as output in return. That said, I probably shouldn't speak too loudly about strict standards, given the Trillian-specific file transfer extensions and whatnot I wrote. (But at least I namespace'd 'em in a Trillian-specific xmlns...!) :) FWIW, Julian, I only wrote support for iChat’s mutant HTML variant on input. I generate strict XHTML-IM on output, no matter what’s on the other end. I tend to think this is the ‘right’ way to do things in terms of client design: be liberal in what you accept as input across the wire, but strict in what you generate as output in return.

That said, I probably shouldn’t speak too loudly about strict standards, given the Trillian-specific file transfer extensions and whatnot I wrote. (But at least I namespace’d ‘em in a Trillian-specific xmlns…!) :)

]]> By: milk http://missig.org/julian/blog/2005/05/14/ichat-clarifications/#comment-6991 milk Sat, 14 May 2005 19:29:07 +0000 http://missig.org/julian/blog/2005/05/14/ichat-clarifications/#comment-6991 it is me or does it seem like the jabber client world is going to end up looking a lot like the web browser world, i.e., with a core group trying to control the standards (w3c, jsf) but with large influential companies creating apps that have non-standardersied ways of doing things or lack some of the more nifty albeit more obscure features of the standard. i wonder what kind of animal the mozilla foundation will rename jabberzilla to when they take it onboard... ;) it is me or does it seem like the jabber client world is going to end up looking a lot like the web browser world, i.e., with a core group trying to control the standards (w3c, jsf) but with large influential companies creating apps that have non-standardersied ways of doing things or lack some of the more nifty albeit more obscure features of the standard.

i wonder what kind of animal the mozilla foundation will rename jabberzilla to when they take it onboard… ;)

]]>