I've noticed that in the below, despite that <status>q wen krrete ayer!!!!</status></presence> is shown three times, Growl reports it differently each time.
Once initially to report a log-on, another reports an initial status, and the last report looks like a customized status (the CDATA? or vcard?).
It looks as if this occurs in groups of three, and if this is so ... why not just filter the first two reports out and only display the last custom status?
If each proprietary protocol does this differently (the below "workings in groups of three" is MSN), a different filter for each proprietary service would need to be assigned.
I've noticed that in the below, despite that <status>q wen krrete ayer!!! !</status> </presence> is shown three times, Growl reports it differently each time.
Once initially to report a log-on, another reports an initial status, and the last report looks like a customized status (the CDATA? or vcard?).
It looks as if this occurs in groups of three, and if this is so ... why not just filter the first two reports out and only display the last custom status?
If each proprietary protocol does this differently (the below "workings in groups of three" is MSN), a different filter for each proprietary service would need to be assigned.
RECV: <presence <email address hidden>" from="someone\ <email address hidden>"><status>q wen krrete ayer!!! !</status> </presence> <email address hidden>"/><presence <email address hidden>" from="someone\ <email address hidden>"><status>q wen krrete ayer!!! !</status> </presence>
RECV: <presence <email address hidden>" from="someone\
SEND:
RECV: <presence <email address hidden>" from="someone\ <email address hidden>"><status>q wen krrete ayer!!!!</status><x xmlns=" vcard-temp: x:update" ><photo> <![CDATA[ 78f009e11c0d074 0fc237b5c9b081b 53b2c945a9] ]></photo> <hash>< ![CDATA[ 78f009e11c0d074 0fc237b5c9b081b 53b2c945a9] ]></hash> </x></presence>
SEND: