View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005267 | unreal | ircd | public | 2019-05-10 07:55 | 2019-10-14 14:49 |
| Reporter | vectr0n | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 5.0.0-alpha3 | ||||
| Summary | 0005267: Ban Forward/Redirect | ||||
| Description | As discussed in #unreal-devel, having the ability to have more control over a mode like +L, having ban forward/redirect would allow a channel op to send only certain users to a different channel. In some cases this can be used to send all web users to a different channel, or some large channels have different channels to deal with ban disputes and being able to forward/redirect them to the correct place when banned would be handy. Also sometimes channels might want to forward/redirect whole ISPs. There are many use cases and I feel a few other people might chime in with their use cases as well. Examples: /mode #chan +b nick!user@host#forwardchan (inspircd) /mode #chan +b nick!user@host$#forwardchan (charybdis/ircd-seven) | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
There's probably a possible enhancement that could be done to +L that would fall into this category. 1) /mode #channel1 +lL 5 #channel2 a) If limit is reached or user is banned redirect to #channel2 (current behaviour is if limit is reached to redirect and if user is banned can't join and no redirect is done) 2) /mode #channel1 +L #channel2 a) if no +l is set, users can join normally unless they match a ban (current behaviour is to redirect instantly) Thoughts? |
|
|
I think it's useless when ban forward/redirect fits more use cases. |
|
|
In 5.0.0-alpha we added +b ~f:#chan:nick!user@host (or even another extban). And +L is now used for all denies not just in case of +l (limit). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-05-10 07:55 | vectr0n | New Issue | |
| 2019-05-10 07:57 | syzop | Description Updated | |
| 2019-05-11 14:42 | PeGaSuS | Note Added: 0020655 | |
| 2019-05-11 17:19 | vectr0n | Note Added: 0020657 | |
| 2019-10-14 14:49 | syzop | Assigned To | => syzop |
| 2019-10-14 14:49 | syzop | Status | new => resolved |
| 2019-10-14 14:49 | syzop | Resolution | open => fixed |
| 2019-10-14 14:49 | syzop | Fixed in Version | => 5.0.0-alpha3 |
| 2019-10-14 14:49 | syzop | Note Added: 0020959 |
