When using the &type=xml I saw: 0 538a69bc150b3f3e8206a4912e62b4a2b589f97f
This was in Safari. I though it would have shown me the xml. My mistake.
The source had:
<c node=“http://www.apple.com/ichat/caps” ver=“604” ext=“audio video recauth maudio avcap avavail rdclient rdserver ice auxvideo mvideo”/>
So that made sense.
Also, when one of the default status messages is selected in iChat It returns “null” when &type=text is appended to the url. Seems to be that way for all chat clients. If a custom message is placed in for presence, that appears in the xml and text. If it’s the default “available” or “away” then a null presence status message is sent.
So I guess, I was just expecting different output based on the input I was giving the client.
Not a big deal, although it would be cool if it would have two more “default” messages: Available and Away in addition to the “unavailable”. Of course it would have to be localized. But in order to do that, I would imagine you’d have to detect browser localization settings, and if it’s being run by a script as part of a “in-out” board, then, you’d have no way to know that… Oh boy.
Anyway by the time i figured it out I just felt like I really should have tested more before I posted a comment to the forum.