/kill shouldn't be in a context menu
Reported by kriss | December 3rd, 2007 @ 04:26 PM | in 1.2.2
I think this one was in the old tracker, probably died somewhere along the way.
/kill should not be in a context menu right next to channel commands (too easy to slip or whatnot) - in fact, it makes sense not to include it at all since the target audience is rather small and shouldn't find too much use of that command in the first place.
Comments and changes to this ticket
-

Nicholas Penree December 4th, 2007 @ 10:39 AM
- → Milestone changed from 1.3 to 1.4
- → State changed from new to open
I think we should have an "IRC Oper" pref which enables these contextual menus. This should be off by default.
-

kriss December 4th, 2007 @ 10:52 AM
It'd probably make more sense to give plugins access to the context menus and give ircops who really want to shoot themselves in the head the means to do so through that.
Then again, ymmv. I'm not a client developer :-)
-

Nicolas Lapomarda April 22nd, 2008 @ 04:09 AM
I think the kill menu item is actually nice to have.
Here's why:
- It won't do anything if you're not an oper
- Opers don't use menus and don't risk slipping
- The plus side is it lets you select as many users as you want in the sidebar then press the magic menu shortcut, which you don't risk hitting by mistake either (cmd-option-shift-K)
What gives?
-

kriss April 22nd, 2008 @ 04:25 AM
Pardon me if I missed something here, but did you just say that "users who would use the menu can't use this item anyhow" and "users who can use this item won't use the menu, besides for the magic key combo"? The target audience seemed to be a bit slim all of a sudden :-)
I'm still a bit sceptic re the usage as well - I rarely had the need to kill multiple people, despite serving five+ years as a server admin/irc op on some pretty damn large networks. What I did do though, was remove O-lines from people who did snafus and blamed the client for them. Same thing goes for killing without a writing a reason along with the kill command, unless it's a very peculiar situation.
If there's some operator arguing for multiple kill in a nice context menu right next to bankick, the person probably shouldn't be given an O-line in the first place, imo.
So summarizing: Very, very slim target audience. No good use case. Probably not what the intended audience would want if it's a network of any size worth mentioning.
Very opinionated of course, but I'll at least pretend to be speaking from some kind of experience :-)
-

Nicolas Lapomarda April 22nd, 2008 @ 04:50 AM
Ok you've worn me down ;)
But maybe we can compromise.
How about this: at the bottom of the user menu, we could insert a "Oper" item which would open a submenu with Kill, Gline and what have you.
What do you say mister? :)
-

kriss April 22nd, 2008 @ 04:56 AM
Makes much more sense since there definitely wouldn't be a chance of accidental usage. Both Kill and G-line ought to take arguments though, making them perhaps less than ideal for a context menu in the first place. How that's best sorted, I wouldn't know :-)
-

Nicolas Lapomarda April 22nd, 2008 @ 05:00 AM
Coolios. Thanks for the interest Kriss.
-

Nicolas Lapomarda April 22nd, 2008 @ 05:01 AM
- → Milestone changed from 1.4 to 1.2.2
-

flying_fortress April 22nd, 2008 @ 07:37 AM
Well, selecting them could insert the command in the textline and give a user default preset which can be still edited there if necessary.
-

Nicolas Lapomarda April 26th, 2008 @ 04:00 AM
- → State changed from open to resolved
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
