Hello all.
I am PapaSmurf on DALnet. This post has nothing to do with hostmasking for the general public. I have been assisting users, in DALnet help channels, since August/September 1998. Non-oper helpers, ever since I have been on IRC, have been subjected to packeting, DDoS, and computer invasions from annoying individuals.
I believe the IRCd terminology for oper hostmasks (e.g. *(a)staff.dalnet or *@dalnet) is staff_token_address.
Would it be possible for official-help-channel AOps, and above, to receive a token address (to help protect them, for their service in helping the network)?
Possible restrictions to consider:
1. Helpers must be an AOp (or above) in official help channels. >> This will get non-AOp helpers more dedicated to helping, but this can lead to help abuse (e.g. use of scripts to provide fastest help to users, or AOps becoming lazy if wannabe helpers race to answer everything).
2. Token address possibilities: *@helper; *(a)nonstaff.helper >> I do not know IRCd, and I do not know if multiple token addresses can be assigned.
3. If this option can be made available, can said users have special permissions added (beyond the standard user)? >> Examples: more access to Q/q-lined nicknames and other, selected /stats commands, or expanded access to StatServ commands. As helpers, this would offer great flexibility when trying to explain certain matters to users, such as why certain nicknames cannot be used.
4. Conflict of policies. >> Some help channels may not remove AOps in official help channels for certain disciplinary actions, but DALnet decision makers may have different policies. DALnet policies would have to allow for removal of the token address (regardless of helpers remaining as channel staff or not).
If this option is not feasible for DALnet, no worries. I thought I would bring it up to, at the very least, get some discussion going on this mailing list.
PapaSmurf
