> is due to the logic being that if it isn't blank or unavailable, then it is > subscription related), which is quite confusing.
Indeed, this was fixed only recently. The fact that Psi generated system messages might have caused some frustration amongst users, blaming the faulty spec implementation ;-) > It seems like the only decent solutions are: > 1) ignore packets with an unexpected type > 2) interpret type='available' as having no type > #1 is not tolerant, #2 is not general. I'm afraid there's no good answer > here. True, but that's the downside of piggybacking actions with different semantics on the same element (<presence/>). Anyway, i guess either one is fine if you're dealing with contacts with bad clients, as long as you don't annoy the poor user with bad friends too much by sending empty messages all the time :-) And i think #1 is marginally better than #2. cheers, Remko
