View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006537 | unreal | ircd | public | 2025-07-06 09:31 | 2025-07-06 09:35 |
| Reporter | Valware | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | feedback | Resolution | open | ||
| Summary | 0006537: Tell clients about CHANMODE, PREFIX and STATUSMSG changes at runtime | ||||
| Description | Since there was no bug report for this (only https://github.com/unrealircd/unrealircd/pull/311): "This re-sends these ISUPPORT tokens to let users know about important changes that may affect their display, most notably PREFIX can be problematic; for example if you have a server running and wish to load a module like ojoin or something else that relies on the client knowing the correlation between the mode and the prefix char, and without it the client just doesn't display the nicklist properly from then on until the client reconnects, which as we know can be a while until that happens. The expected client reaction to duplicate ISUPPORT tokens according to the spec is to overwrite the current values. I have tested this in mIRC only and it works as expected." | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Reported as bug and set reporter to Valware. |
|
|
My follow up commit was this: commit ba8c587e44d3e42035f9ac2dbd82bfcb6e1347d9 (HEAD -> unreal60_dev, origin/unreal60_dev, origin/HEAD) Author: Bram Matthys <[email protected]> Date: Sun Jul 6 09:23:24 2025 +0200 Update to previous commit: disable by default, enable via set { send-isupport-updates yes; } I totally agree with the goal to have this enabled, but let's do some more testing with more clients first to see if they misbehave. Last thing I want is a similar situation to when we were the first IRCd that sent "CAP DEL sasl" and "CAP NEW sasl" when services went offline and online and it caused all mIRC clients to reconnect. I don't expect this one to be so bad (also because users would get the 005's when they typed /VERSION) but... let's test to be sure. Should probably deploy this with enabled on irc.unrealircd.org and such :) |
|
|
Other than the testing, I wonder if we can or need to send ISUPPORT updates when someone becomes oper. Are there certain things that opers can do that regular users don't, or stretched limit, that we could re-announce ISUPPORT for? (send it to that particular client) Maybe there are none. I am just suggesting to check. (Too lazy atm myself) (And then the same/reverse should happen on oper down) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-07-06 09:31 | syzop | New Issue | |
| 2025-07-06 09:31 | syzop | Reporter | syzop => Valware |
| 2025-07-06 09:31 | syzop | Note Added: 0023450 | |
| 2025-07-06 09:32 | syzop | Note Added: 0023451 | |
| 2025-07-06 09:32 | syzop | Assigned To | => syzop |
| 2025-07-06 09:32 | syzop | Status | new => feedback |
| 2025-07-06 09:34 | syzop | Note Added: 0023452 | |
| 2025-07-06 09:35 | syzop | Note Edited: 0023452 |
