In my opinion, the syntax for those commands is going to be just as difficult for most of the newbies to learn as /mode #example +b or /whois badguy. Learning how to create an effective targeted ban is something that channel operators should take the time to learn, if they want to be effective operators.
Specifically, though, neither helpers in a channel nor any service can tell someone WHY they were banned. A favorite kick message of mine is "Nope." Whatever behavior they were doing at the time is why they got banned. As helpers, we can point them to go ask the op that banned them why they were banned.
A Service doing this same thing, however, can be taken by users to understand that if they ask to be unbanned, they will be. This is not the case. If we're going to have coders doing things to services, I'd rather they take the time to fix some of the existing functionality, like Enforce. If the current behavior is how they want services to behave by default, then the current implementation isn't that great. It's more of a hack that puts the functionality in. It'd be better to take the time to properly hardcode the behavior in, instead of leaving the option there, and finding various ways to enforce it on. We still get questions about how to turn it off, because it still looks like an option.
On Fri, Jan 1, 2010 at 10:56 PM, James Hess <mysidia@gmail.com> wrote:
On Fri, Jan 1, 2010 at 10:29 AM, PapaSmurf <freedried@yahoo.com> wrote:
> Well, as helpers on help channels (#help, #dalnethelp, #irchelp, etc), we
> help users with this information all the time. A user joins and asks why
> they are banned from channel #*****. As helpers, we do a simple command
> to find the person who banned them.
> /mode #***** b
Hm.. here's a really dumb question. Why don't we have a service
that can answer that question, so the novice can see why they were
banned, without having to learn all the commands involved?
/msg HelpServ whybanned #example
-HelpServ- You were banned from #example, by OpNickname
-HelpServ- If you type /mode #example :b
-HelpServ- You will see:
-HelpServ- -- A ban for the pattern: *!*@*.example.com
-HelpServ- was added by OpNick on Fri Jan 1 2010, 3:33
-HelpServ-
-HelpServ- The above ban effects you.
-HelpServ- If you type /USERHOST yournick
-HelpServ- You will see your host address of the form nick!user@host is:
-HelpServ- yournick!yourusername@my.example.com
-HelpServ-
-HelpServ- If you wish to be unbanned, you may want to contact
-HelpServ- OpNickname and politely request to be allowed to rejoin the channel
/msg HelpServ howcanIban badguy from #example
-HelpServ- Badguy currently has a hostmask of:
-HelpServ- yournick!yourusername@my.example.com
-HelpServ-
-HelpServ- To ban badguy from #example, it is suggested to choose
one of the following:
-HelpServ- A ban of badguy's current username from any host:
-HelpServ- /mode #example b *!yourusername@*
-HelpServ-
-HelpServ- A ban of badguy's nickname from any host:
-HelpServ- /mode #example b badguy!*@*
-HelpServ-
-HelpServ- A ban of badguy's username, from example.com:
-HelpServ- /mode #example b *!yourusername@*.example.com
-HelpServ-
-HelpServ- A ban based on from badguy's current host address:
-HelpServ- /mode #example b *!*@my.example.com
-HelpServ-
-HelpServ- A domain-wide ban of badguy's site:
-HelpServ- /mode #example b *!*@*.example.com
---
-J
_______________________________________________
DALnet-services mailing list
DALnet-services@lists.dal.net
https://lists.dal.net/mailman/listinfo/dalnet-services