Re: [Coder-Com] away not updating on remote servers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > 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 remotely. This should solve our HIS problems > with away messages. (Plain away messages also had potential for > breaking HIS in particular ways.) I agree, this is what I wanted to do the first time around, but I expected users would slaughter me. - -- What is the sound of one hand clapping? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Only when you are sure they have you, can you stop being paranoid iD8DBQE+Yv7scAgRpy8z8UQRAqWdAJ0YMinDwocK40XHZIixX6qI/i+5qwCfRG9l JHxSvnvCYeq9+V2wIu00loM= =G1+r -END PGP SIGNATURE-
Re: [Coder-Com] away not updating on remote servers
Kev wrote: > > > 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 remotely. This should solve our HIS problems > with away messages. (Plain away messages also had potential for > breaking HIS in particular ways.) > -- > Kevin L. Mitchell <[EMAIL PROTECTED]> instead of a umode +a, maybe broadcasting a short fake away string like "-"? saving on umode chars and hassle... (making the "is away" remote whois only must be done first anyway)
Re: [Coder-Com] away not updating on remote servers
Isomer wrote: > > 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 :) > Kev wrote: > 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 remotely. This should solve our HIS problems > with away messages. (Plain away messages also had potential for > breaking HIS in particular ways.) > -- > Kevin L. Mitchell <[EMAIL PROTECTED]> bas wrote: instead of a umode +a, maybe broadcasting a short fake away string like "-"? saving on umode chars and hassle... (making the "is away" remote whois only must be done first anyway) Wouldn't that still leave HIS broken (since the local server and remote server would return different away messages)? -stephen _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
[Coder-Com] +x
Good afternoon all, Got a little question about the +x mode. It seems that some people are not able to log into the x mode or at least set it on there Ip or whatever you may call it. We (some op's in a channel) are having a friendly bot in there who helps us out to keep the channel clean from scary people *grin*. We would have like to put him on +x to have at least a safer way on hiding it's ip. We logged him in and stuff but the +x is not able to be set. Now I wondered if this was a bot matter or not but the fact that some other operators in our channels aren't able either to turn it on made me wonder even more. We suggested them to switch servers and all but still the keep on having the problem. Any suggestions? Greetings, Sofie
RE: [Coder-Com] away not updating on remote servers
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of bas > Sent: Monday, March 03, 2003 12:04 PM > To: [EMAIL PROTECTED] > Subject: Re: [Coder-Com] away not updating on remote servers > > instead of a umode +a, maybe broadcasting a short fake away > string like > "-"? saving on umode chars and hassle... (making the "is away" remote > whois only must be done first anyway) I believe IRCnet already uses mode +a to indicate away status, and perhaps some other nets too, so this isn't anything new.. But if you'd want to go the AWAY message style, why send a string at all? Just send the away token for client X and that will be that. Kind regards -- Tom Rons ([EMAIL PROTECTED]) (http://openircd.org/trons/)
Re: [Coder-Com] +x]
Hi, I have put my egg with +x This is in my eggdrop.conf # script to run (if any) when first connecting to a server set init-server { putserv "MODE $botnick +ix-ws" } And I have made a tcl script that ident my egg to X if is not oped in chan that he have access. I admit that this script is not very advanced. I have made it quickly, modify it like you want. set canal_X(#chanthatmybothaveaccess) "1" proc notc:X_login { nick uhost handle arg asd } { putserv "PRIVMSG [EMAIL PROTECTED] :LOGIN yourusername yourpass" } proc X_needop {canal} { global botnick if [isop X $canal] { puthelp "PRIVMSG x :op $canal $botnick" } } proc X_needinvite {canal} { global botnick puthelp "PRIVMSG X :invite $canal" } proc X_needunban {canal} { global botnick puthelp "PRIVMSG x :unban $canal $botnick" puthelp "JOIN $canal" } proc X_join_rajouter { nick uhost hand chan } { global botnick global canal_X if {$nick == $botnick} { if [info exists canal_X($chan)] { channel set $chan need-op "X_needop $chan" channel set $chan need-invite "X_needinvite $chan" channel set $chan need-unban "X_needunban $chan" } } } bind join - * X_join_rajouter bind notc - "Sorry, You must be logged in to use this command." notc:X_login [EMAIL PROTECTED] wrote: Good afternoon all, Got a little question about the +x mode. It seems that some people are not able to log into the x mode or at least set it on there Ip or whatever you may call it. We (some op's in a channel) are having a friendly bot in there who helps us out to keep the channel clean from scary people *grin*. We would have like to put him on +x to have at least a safer way on hiding it's ip. We logged him in and stuff but the +x is not able to be set. Now I wondered if this was a bot matter or not but the fact that some other operators in our channels aren't able either to turn it on made me wonder even more. We suggested them to switch servers and all but still the keep on having the problem. Any suggestions? Greetings, Sofie
Re: [Coder-Com] away not updating on remote servers
> Kev wrote: > > > 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 remotely. This should solve our HIS problems > > > with away messages. (Plain away messages also had potential for > > > breaking HIS in particular ways.) > > > -- > > > Kevin L. Mitchell <[EMAIL PROTECTED]> > > > bas wrote: > >instead of a umode +a, maybe broadcasting a short fake away string like > >"-"? saving on umode chars and hassle... (making the "is away" remote > >whois only must be done first anyway) > > Wouldn't that still leave HIS broken (since the local server and remote > server would return different away messages)? bas's suggestion would. My scheme would drop the A server<->server token and use the M token instead. A few more bytes than bas's scheme, but the advantage would be that everyone everywhere would see that the user is away, though they wouldn't be able to see the away message until they did a /whois -- Kevin L. Mitchell <[EMAIL PROTECTED]>
Re: [Coder-Com] +x
> Got a little question about the +x mode. > It seems that some people are not able to log into the x mode or at least set > it on there Ip or whatever you may call it. Server admins are very strongly encouraged to have this user mode set to on, but it is not a requirement yet. This means that individual admins may have it turned off, meaning anyone connected to those servers would not be able to use it. -- Kevin L. Mitchell <[EMAIL PROTECTED]>
Re: [Coder-Com] away not updating on remote servers
> > instead of a umode +a, maybe broadcasting a short fake away > > string like > > "-"? saving on umode chars and hassle... (making the "is away" remote > > whois only must be done first anyway) > > I believe IRCnet already uses mode +a to indicate away status, and > perhaps some other nets too, so this isn't anything new.. > But if you'd want to go the AWAY message style, why send a string at > all? Just send the away token for client X and that will be that. AXAAA A :foo Now user with numeric "AXAAA" is away. AXAAA A Now user with numeric "AXAAA" is no longer away. Point is, just sending the token is not enough information. -- Kevin L. Mitchell <[EMAIL PROTECTED]>
RE: [Coder-Com] away not updating on remote servers
On Mon, 2003-03-03 at 06:38, Tom Rons wrote: > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of bas > > Sent: Monday, March 03, 2003 12:04 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [Coder-Com] away not updating on remote servers > > > > instead of a umode +a, maybe broadcasting a short fake away > > string like > > "-"? saving on umode chars and hassle... (making the "is away" remote > > whois only must be done first anyway) all of these things seem to break HIS; wouldn't it just be easier to have it not accept new AWAY messages once you are already in AWAY mode? (ie: you send a AWAY and any further AWAY commands (that have messages) are ignored until you leave AWAY mode) the primary use of sending AWAY commands repeatedly is scripts, and while this would cause some confusion I think that the benefit outweighs it.. however, this would need some form of 'away flood' protection though to prevent people from sending something like: AWAY :been gone for 30s AWAY AWAY :been gone for 31s AWAY AWAY :been gone for 32s AWAY ... etc. // akl ([EMAIL PROTECTED]; irc.progameplayer.com)