galago

galago-daemon isn't very smart when two feeds are
telling it different things.

Example scenario: Two instances of gaim are running,
and both have an account signed on with one contact.
One account signs off, and galago-daemon gets a
presence change indicating that the contact is no
longer online. It then sends this to all listening
clients. However, the other instance of gaim is still
running, and the contact is indeed signed on still.

Part of this should be solved in gaim-galago. Instead
of marking a contact offline, discard the presence.
Then, before transmitting the signal in galago-daemon,
see if any other presences in the meta-presence still
exist and what the common state is. Set the main
presence to that, and if it's changed, submit that info.