View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001640 | unreal | ircd | public | 2004-03-10 19:20 | 2004-03-14 16:24 |
| Reporter | w00t | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-RC1 | ||||
| Summary | 0001640: View/Change Modes | ||||
| Description | I dont know about others, but I would definatly find it useful to be able to view and change the exact modes of a channel or user. like... uh... words fail me. Like when /WHOIS I kinda would almost like to see their modes rather than one line like "Is a network administrator" I would prefer "Modes: +NOoCaAW" or something... | ||||
| Additional Information | I know this sounds stupid, but I would really find it useful. | ||||
| 3rd party modules | |||||
|
|
If you have the eyes snomask (+s +e) you can see modes of a user in '/whois <user>'. As for chanmodes just do /mode #chan. As for changing chanmodes.. well you know how :P. As for chaning usermodes, we only allow that for services (SVSMODE/SVS2MODE). |
|
|
Thanks syzop. Nice to see a general lack of hostility. Ummm... I didnt know about those snomasks (snomasks have confused me some since they got introduced) and didnt know about /mode #chan either. Thanks. But usermodes...... If a user has +aN or something, shouldnt they be permitted to run /mode <user> +/-<modes>? |
|
|
Well I've never actually seen a reason why an oper needs to change another user's modes... |
|
|
This is suggested, as it is apparantly used. I dont, but some I work with do use it. It is an anope thing (operserv/umode) and auspice (operserv/unmode), so why do we not have a command equivilant? |
|
|
You know, in case services die or they dont support it or something... You get my meaning? |
|
|
But why (regardless of whether it is in the IRCd, or in services) do you ever need to change someone else's modes? That's the part I don't understand. |
|
|
The only time I've had to change a users mode is when he ilegally used the +B (bla bla is a bot), and he used the flag to trick other people into thinking he was offically supported by the network... ... But that's a long time ago.. |
|
|
Mmm... Unfortunatly, we have some issues from time to time where we want to seemingly "upgrade" a users status temporarily (i.e. that whole HalfOp thing I was telling you about.) To do that, we samode them +o, so their whois has a nice little status line and then throw them in #help and see how they do. It sounds pointless, but hey, it works. Look, if the usermodes thing is too difficult, then lets drop it. But viewing modes... |
|
|
We already told you how to view the modes: If you have the eyes snomask (+s +e) you can see modes of a user in '/whois <user>'. |
|
|
Whoops! Sorry, I missed that bit of the post. Must put the glasses on next time. Hm. Perhaps I need to start writing some of this stuff down so that other people dont ask it... Would it be too much for me to start an [unofficial] documentation project? |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2004-03-10 19:20 | w00t | New Issue | |
| 2004-03-10 19:26 | syzop | Note Added: 0005402 | |
| 2004-03-10 19:39 | w00t | Note Added: 0005403 | |
| 2004-03-10 20:08 |
|
Note Added: 0005404 | |
| 2004-03-10 20:16 | w00t | Note Added: 0005405 | |
| 2004-03-10 20:57 | w00t | Note Added: 0005406 | |
| 2004-03-10 22:21 |
|
Note Added: 0005408 | |
| 2004-03-11 11:17 | devil | Note Added: 0005414 | |
| 2004-03-11 17:30 | w00t | Note Added: 0005430 | |
| 2004-03-11 17:36 |
|
Note Added: 0005431 | |
| 2004-03-11 17:38 | w00t | Note Added: 0005432 | |
| 2004-03-14 16:24 | syzop | Status | new => closed |
