View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004427 | unreal | ircd | public | 2015-10-17 17:13 | 2015-10-26 11:00 |
| Reporter | blank | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Summary | 0004427: Add modes to official-channels {}; | ||||
| Description | Add modes to official-channels{}; so that +P could be set on boot. official-channels { "#channel" { topic "The default topic"; modes +ntP; }; }; | ||||
| 3rd party modules | |||||
|
|
Hmm, also rename that block to just channels {}; the 'official' seems pointless ... |
|
|
The topic is fake, and so would be the mode, it would be gone as soon as the first person joins. This is how official-channels works, see the documentation. I actually think the feature should be removed entirely. It's confusing. It's not meant as a replacement for services. It was a bad idea. |
|
|
Rather than removing it, can't it just be done 'properly'? Create the channel, set the modes, set the topic ... InspIRCd does it well, and not all networks have services. |
|
|
Well I think this would be useful to have settable modes. Syzop, When the user joins an empty channel now, They do not see any mode changes, but are Channel Operators (@) Surely this could be applied to the suggestion above, if for example "+sntM" are set, then they could be set server-side before the user joins, along with Channel Ops? I actually think this is a great idea if I'm honest, Would be good if implemented. Example: JOIN #Chan <server sets Channel modes +sntM> <server sets User +o> Channel Op <server now joins User into Channel> - user does not "visibly" see the modes set Server sends to client (as normal): <channel topic> <topic set by> <channel modes> eg. Channel #chan Modes: +ntr <creationdate> eg. Channel #chan Created: Tue 16th Mar 2010 11:31:35 It could also be done this way (as it is currently) -> Now talking in #dsfgdsgf -- ServerMode change [+sntM] on #dsfgdsgf by irc.net |
|
|
Problem is you (still) end up doing something "half". Like, then someone will ask "but hey the first joiner can then change all the channel modes and topic etc, they shouldn't get ops".. then we end up implementing an op list (AOP)... etc. etc.. Shouldn't bans be stored too? So now you have an AKICK list. Then when you have multiple servers this also becomes less manageable. So you have to create a central database. And now you have created something called services :D Sorry guys, I'm closing this one. If you want your channels managed you should run a services package. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-10-17 17:13 | blank | New Issue | |
| 2015-10-17 17:14 | blank | Note Added: 0018769 | |
| 2015-10-17 17:14 | blank | Note Edited: 0018769 | |
| 2015-10-17 18:02 | syzop | Note Added: 0018770 | |
| 2015-10-17 18:02 | syzop | Severity | minor => feature |
| 2015-10-17 21:40 | blank | Note Added: 0018771 | |
| 2015-10-20 22:52 | Amiga600 | Note Added: 0018772 | |
| 2015-10-20 22:54 | Amiga600 | Note Edited: 0018772 | |
| 2015-10-20 23:16 | Amiga600 | Note Edited: 0018772 | |
| 2015-10-20 23:18 | Amiga600 | Note Edited: 0018772 | |
| 2015-10-20 23:18 | Amiga600 | Note Edited: 0018772 | |
| 2015-10-26 11:00 | syzop | Note Added: 0018792 | |
| 2015-10-26 11:00 | syzop | Status | new => closed |
| 2015-10-26 11:00 | syzop | Assigned To | => syzop |
| 2015-10-26 11:00 | syzop | Resolution | open => no change required |
