View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001379 | unreal | ircd | public | 2003-11-23 06:40 | 2003-12-17 18:08 |
| Reporter | Special | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Summary | 0001379: owner should be able to kick in +Q channel | ||||
| Description | I think the channel owner (person with channel mode +q) should be able to kick if +Q is set in the channel. | ||||
| 3rd party modules | |||||
|
|
Any opinions on this idea? |
|
|
/mode #chan -Q /kick #chan nick reason /mode #chan +Q Plus, it defeats the purpose... I could understand an oper... but the owner can easily op and remove the mode. |
|
|
make an alias... if ur on PC /Alias //Qkick //mode $chan -Q | //Kick $chan $1- | //mode $chan +Q just type that into the text bar to make it th alias then use //Qkick nickname reason and it`ll do what u want. Only be beneifcal for 1) mode lock and 2) webtv users, but even webtv IRCS can store " button commands " where the user types in a command, and push the button it preforms the 1 command, so 2 buttons 1 for -Q one for +Q ... Not worth it |
|
|
Special: Its a good idea. Praetorian_: It makes less typing. White_Magic: Not everyone is a fan of alias's... |
|
|
+Q states that no kicks are permitted. Why should the owner be special? As already mentioned, IRCops are a special case. You may as well not set this mode if it doesn't apply to everyone. Or just get services to kick. |
|
|
lol, its not a case of if " its less typing " or " not everyone is a fan of aliases " if the coders dont add it in, what are you gonna do?? prolly do what either myself or Praetorian_ has written on -_- |
|
|
+Q is pretty stupid at the moment.. I mean, what does it do? someone can just unset it... Except halfops.. so you can make it that halfops cannot kick anyone (but they can ban).. uh.. right... Actually it has been considered to just remove +Q (see unreal-users archives if you are bored)... so my question is, when did you actually use +Q? :). The only example someone was able to come up with is during a eggdrop kick fight... not exactly a good point to leave a whole channelmode in place. Perhaps it could be made so +q can only kick but also so only +q can set +Q, but then again.. what use is that? you can do anything you want (+i, +l, +b, etc) but not kick... uh? |
|
|
Well, I asked myself too, why there is a channel mode Q. Because it isn't so usefull. But I use it sometimes (as example), when someone want to like to post a text in the channel (with permission), which is as example more than 10 lines, and bots+scripts wants to kickban the user because of flood. But they aren't able because of +Q. Yes, he gets banned, but the messages will arrive (with +v). Better than unsetting every protection, or deop the whole channel ;) And maybe usefull, if there is a channel takeover (with bots!?), but since we have services, that shouldn't be a problem. Thats the only reason, why +Q could be usefull hehe ;) EDIT: Ah yes, and when the owner can kick in +Q Channel, than the channel mode is more useless than it is now :P bearbeitet am: 12-11-03 10:37 |
|
|
I don't agree. That person asking for a permission to flood infers that all other members of the channel will be able to flood while +Q is set. In addition, one solution would be to set the user as a friend in the bot which protects flood. It's still better than a "+b" mode change and that the bot remembers flooders and next time they join the channel, will get kicked automatically... |
|
|
Personally, I use +Q a fair bit in our main server channel, as I dont want any renegades getting pissed and using scripts if they accidentally get opped... But I do believe that +Q should ONLY be able to be set by +q. +q should be able to override +Q. It wouldnt take that much work... Hell... I might consider doing it, if I understood how CVS and all the rest worked. White_Magic: If the coders don't add it, I will. It takes time to customise Unreal, but I have done it in the past. The only problem now is that I am part of a network, not a lone server. |
|
|
As far as I'm concerned this will not be in Unreal. If it were up to me +Q would be gone completely. The "renegade op" idea is stupid to me. If your ops don't have the power to remove problem users, what's the point of making them +o? And if your ops are told not to run any auto-kick scripts and still do, then why are they still ops? And as for the other reason, allowing a flood, this also makes no sense. AngryWolf pointed out that most bots are still going to set +b. And, if +b is set first of all this prevents you from talking so you can't flood anyway, and it will likely remember the ban for the next time you join. And even if you don't have a bot, +f pays no attention to whether +Q is set. So if +f is set, and you flood, +Q can be set and you're still gone. But anyway, that's not the issue here. The issue here is why should +q override +Q? Let's look at the reasons given, "It's less typing" and "Not everyone likes aliases." Umm you know what else is less typing? If we had ban v {} instead of ban version {} or me::num instead of me::numeric, that's not a valid reason for adding it. And as for aliases, yeah there are people who don't like them, but does that mean we should add a /hop command to Unreal? What about /j and /p? That works into the "I don't like aliases" and the "I don't like to type" reasons. If someone can justify this to me, then perhaps I'll consider it, but basically saying "it should be there because I want it" is not a good enough reason. And to w00t, you are free to modify Unreal, the GPL gives you that right, however it is our policy that anyone who is using a modified version of Unreal is NOT able to receive support in any way. So go ahead and do this, but if I notice you asking for support, expect a kick/ban. Oh and in #unreal-support +Q is not set so you will really be kicked. |
|
|
oh-oh, both me and codemastr don't see any reason for this mode to stay in. I guess it's better to close this bug now before we'll actually do it to get rid of the mess/discussion ;p. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-11-23 06:40 | Special | New Issue | |
| 2003-11-23 16:02 | syzop | Summary | owner can kick in +Q channel => owner should be able to kick in +Q channel |
| 2003-12-02 15:39 | Special | Note Added: 0004183 | |
| 2003-12-02 16:09 | Praetorian_ | Note Added: 0004184 | |
| 2003-12-04 18:14 | White_Magic | Note Added: 0004199 | |
| 2003-12-08 01:52 | w00t | Note Added: 0004244 | |
| 2003-12-10 18:39 | cyberCloWn | Note Added: 0004278 | |
| 2003-12-10 18:44 | White_Magic | Note Added: 0004279 | |
| 2003-12-10 23:50 | syzop | Note Added: 0004294 | |
| 2003-12-11 10:34 | Rocko | Note Added: 0004299 | |
| 2003-12-11 10:37 | Rocko | Note Edited: 0004299 | |
| 2003-12-11 17:07 | AngryWolf | Note Added: 0004301 | |
| 2003-12-16 02:47 | w00t | Note Added: 0004355 | |
| 2003-12-16 03:38 |
|
Note Added: 0004360 | |
| 2003-12-17 18:08 | syzop | Status | new => closed |
| 2003-12-17 18:08 | syzop | Note Added: 0004371 |
