-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MODE #channel
does not send 329 RPL_CHANNELCREATED
#130
Comments
spec says "Servers MAY also return the RPL_CREATIONTIME (329) numeric following RPL_CHANNELMODEIS." If Sable is the only server not to do it, then could you amend the spec to SHOULD, and add an irctest for that? |
Channel created makes only sense for networks that store the channel timestamp somewhere. |
Right, irc2 doesn't send it either. |
MAY actually seems correct here, because is this numeric even useful to clients? |
Kinda, yes. At least one client (glirc) processes it to show it to users as part of information about a channel. |
Both hexchat and weechat display it to users as well: Here the response when the user enters Hexchat:
Weechat:
|
Makes sense, I opened a PR here: ircdocs/modern-irc#238 I agree with Val's implicit recommendation that Sable specifically doesn't need to send it. |
In response to a successful
MODE #channel
(i.e. list channel modes), Sable sends324 RPL_CHANNELMODEIS
but not329 RPL_CHANNELCREATED
(also referred to asRPL_CREATIONTIME
):https://modern.ircdocs.horse/#rplcreationtime-329
This numeric is not in either of the RFCs. It seems to have been introduced by Bahamut and become a de facto standard, as per https://www.alien.net.au/irc/irc2numerics.html
The text was updated successfully, but these errors were encountered: