View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003551 | unreal | ircd | public | 2007-12-08 11:51 | 2015-08-08 16:27 |
Reporter | ups | Assigned To | syzop | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
OS | Win | OS Version | Xp | ||
Product Version | 3.2.7 | ||||
Summary | 0003551: Viruschan restrictions | ||||
Description | Hi, I would suggest that the viruschan restrictions should be removed when the user is kicked from the viruschan. Tks for your time. | ||||
Tags | No tags attached. | ||||
3rd party modules | |||||
related to | 0002526 | acknowledged | Command to VIRUSCHAN users |
|
Hm... you mean... once a user is kicked he/she is untagged and is no longer 'virus tagged'? So they can continue as normal? Or do you mean something with rejoining after kick? |
|
I mean, when a user is kicked, that user is untagged and continue as normal :) |
|
I don't know if kicking them should really remove their virus status. However, there are 2 things you may do: You can get the Quarantine (http://www.unrealircd.com/modules/view/51) module, which should allow you to release people from the virus chan; or you can wait for 0002526 to be implemented which would give opers the ability to release people. |
|
I don't think this is a good idea. What if the user is flooding and a bot kicks the user (or the ircd)? Then his restrictions are gone. It would be counter-intuitive. |
Date Modified | Username | Field | Change |
---|---|---|---|
2007-12-08 11:51 | ups | New Issue | |
2007-12-10 09:36 | syzop | Note Added: 0014891 | |
2007-12-10 15:52 | ups | Note Added: 0014897 | |
2008-02-10 16:51 | Stealth | Relationship added | related to 0002526 |
2008-02-10 16:53 | Stealth | Note Added: 0015065 | |
2015-08-08 16:26 | syzop | Note Added: 0018607 | |
2015-08-08 16:26 | syzop | Status | new => closed |
2015-08-08 16:27 | syzop | Assigned To | => syzop |
2015-08-08 16:27 | syzop | Resolution | open => no change required |