View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003985 | unreal | ircd | public | 2010-12-24 05:03 | 2013-01-09 10:43 |
| Reporter | Humanoid | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | duplicate | ||
| Summary | 0003985: Channel Mode Request +u & +U | ||||
| Description | I was just thinking it might be nice to have the option of separating the functions of channel mode +u. The idea is to have little +u still restrict chatter visibility to channel operators but not block the userlist. Capital mode +U would do both of those functions. These two modes would relate to +p and +s in the sense that they cannot be set together. Flexibility can be great and easier to implement when the concept is applied to features that already exist, so that's my two cents. :) | ||||
| Tags | Auditorium, CHMODE | ||||
| 3rd party modules | |||||
|
|
The reason channelmodde +u blocks the userlist entirely on join is because without joins/parts/kicks being sent to clients, the clients have no information to keep the userlist up to date. So if you had +uU set the client would have the same userlist the whole time the user is in the channel, even if new users joined or the original ones left. |
|
|
Mm, well it'd be nice if the server could silently update the client without displaying the events, but that could be difficult to achieve even if it seems like a simple solution. |
|
|
The server could send a NAMES update each time someone joins, but on some clients that would dump more information to the channel window than just normal events. This would also cause the server to send out 3x+ the data needed for a normal event. Another option would be to update the NAMES list internally and provide it to clients when they request, but for users wanting a constantly updated user list they would need to request more garbage than if they just had normal events. In short, I don't see much of anything that could be done efficiently, please provide any other ideas if you have them. |
|
|
Discussion moved to 0004160 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-12-24 05:03 | Humanoid | New Issue | |
| 2010-12-24 05:22 | Humanoid | Tag Attached: CHMODE | |
| 2010-12-24 05:22 | Humanoid | Tag Attached: Auditorium | |
| 2010-12-24 18:03 | Stealth | Note Added: 0016508 | |
| 2011-01-02 04:51 | Humanoid | Note Added: 0016574 | |
| 2011-01-02 04:56 | Stealth | Note Added: 0016575 | |
| 2011-01-02 04:56 | Stealth | Status | new => feedback |
| 2013-01-09 10:41 | syzop | Relationship added | related to 0004160 |
| 2013-01-09 10:43 | syzop | Note Added: 0017330 | |
| 2013-01-09 10:43 | syzop | Status | feedback => closed |
| 2013-01-09 10:43 | syzop | Assigned To | => syzop |
| 2013-01-09 10:43 | syzop | Resolution | open => duplicate |
