View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006054 | unreal | ircd | public | 2022-01-10 12:01 | 2022-01-10 15:36 |
| Reporter | syzop | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Summary | 0006054: set::allowed-channelchars | ||||
| Description | When adding set::allowed-channelchars in UnrealIRCd 5 I thought it was too effort at the time to make it more complex so made it only have the options: utf8, ascii, any. But we can revisit the idea with UnrealIRCd 6 and make the set::allowed-nickchars functionality available in set::allowed-channelchars. Then you can have: set { allowed-channelchars latin-utf8; } See https://www.unrealircd.org/docs/Nick_Character_Sets for more information. This does not deal with CASEMAPPING. Safest option for the paranoid would still be a set::allowed-channelchars setting of "ascii". But maybe it is a good middle ground for some networks? Not sure if people would actually use it, it needs to be worth the effort. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
To me this seems to bring back the idea of a spamfilter or other option to allow/block channel names by regex which would give additional flexibility and additionally allow the ability to block specific characters of an admins choice. |
|
|
Jobe: that's tracked in 0005531 |
