As for what happens when I get a flood of status reports of people that are already logged on as per my roster ...
RECV: <presence <email address hidden>" from="someone\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone2\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone3\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone4\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone5\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone6\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone7\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone8\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone9\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone10\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone11\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone12\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone13\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone14\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone15\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone16\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone17\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone18\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></presence><presence <email address hidden>" from="someone19\<email address hidden>" type="unavailable"><x xmlns="vcard-temp:x:update"/></pre
It's nothing odd other. Perhaps Coccinella should look at one's roster before reporting status to Growl, and playing an alert sound --which can be annoying too.
As for what happens when I get a flood of status reports of people that are already logged on as per my roster ...
RECV: <presence <email address hidden>" from="someone\ <email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone2\ <email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone3\ <email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone4\ <email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone5\ <email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone6\ <email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone7\ <email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone8\ <email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone9\ <email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone10 \<email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone11 \<email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone12 \<email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone13 \<email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone14 \<email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone15 \<email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone16 \<email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone17 \<email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone18 \<email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></presence> <presence <email address hidden>" from="someone19 \<email address hidden>" type="unavailab le"><x xmlns=" vcard-temp: x:update" /></pre
It's nothing odd other. Perhaps Coccinella should look at one's roster before reporting status to Growl, and playing an alert sound --which can be annoying too.