Forums Feature Suggestions Update address book and use raw 307

Notify options, select which networks (if blank, all networks) a nick is watched on

Then, if a nick is online and a whois is done, if a raw 307 is returned (identified to the nick), options that could/would add the user to a specified user level (using the mask desired) with the notes from the notify list. Also options to add the nick (with that same mask) to the aop/voice/protect or ignore lists.

That way, someone can't just switch to a nick, join a room, and automatically get voiced/op'd - their nick/address would get added only when a whois has returned a 307 (which is an option in the notify, but also, could be scripted to happen frequently for bot usage, as an example).

Already suggested (and very much welcomed) here - Personally I think it's more logical for /notify -w to be used for all networks, otherwise, the specific network you type the command on, but there we go.



What about for networks which don't have RAW 307 available? Most of the top networks do not have it. Also, what about networks that have the +x usermode? Some may not set +x as soon as they connect, so mIRC picks up their real hostname when they logon and you /whois them, then when they join a channel, you see them with their networks vhost.
Personally I think this is better left to a script. On notify was added for a reason :tongue:

My 2 cents.

Regards,

As far as I know, raw307 is a standard (or at least is a reserved raw code for that purpose), thus the suggestion to make use of it - as with many options, some networks may be incompatible, but for IRC's that do support it, it would give the functions (aop/voice/etc) a better chance of being more secure.



As for some IRC's giving vhosts, that and other reasons was why I said it would be the masking of the mirc users choice.

Hm, well in my opinion, security is not an issue...

Voice status does not allow any extra access to a user and so if on the very small off chance someone did slip through the net and got voiced, nothing terrible would happen. If you add an *!*@IP or *!*@hostmask to your /avoice list, then it should be secure enough. Bar cybercafes (and the like), nobody has the same IP.

As for obtaining op in the channel (which is a little more serious), any network I can think of which puts raw 307 to use equally has a channel service with auto-op functions..er go, no need for /aop in the first place!

I can see where you're coming from, but my own personal view is that this is too easy to do through raw events via mIRC scripting. It's not a bad/wrong idea or anything though

Regards,