> If people set themselves /away multiple times only the first is
> broadcast to all servers. If I had my way, we wouldn't broadcast /away
> at all :)
I recommend storing the away message locally only, making it only
available on a /whois , and using a user mode (+a) to
mark the user away remote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I notice that when a user sets their away message it propagates to the
> remote servers. If a user does not clear their away message, but sets it
> to a new one, it updates on the local server *only*. Remote servers still
> hold the old away mes
You're absolutely right. This breaks HIS.
> I notice that when a user sets their away message it propagates to the
> remote servers. If a user does not clear their away message, but sets it
> to
> a new one, it updates on the local server *only*. Remote servers still
> hold
> the old away mes
I notice that when a user sets their away message it propagates to the
remote servers. If a user does not clear their away message, but sets it to
a new one, it updates on the local server *only*. Remote servers still hold
the old away message. (Clearing the away message, and then setting a ne
