View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006454 | unreal | ircd | public | 2024-08-17 22:07 | 2024-08-17 22:11 |
| Reporter | PeGaSuS | Assigned To | |||
| Priority | none | Severity | feature | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Linux | OS | Ubuntu | OS Version | 22.04 |
| Product Version | 6.1.7.1 | ||||
| Summary | 0006454: CHATHISTORY command doesn't work if the IRC client doesn't support server-time | ||||
| Description | Currently, CHATHISTORY requires SERVER-TIME capanility to be supported/enabled by the IRC client. If we try to do something like: /CHATHISTORY latest #chan * 10 while having the SERVER-TIME capability disabled we get something like: -- irc.domain.tld: Your IRC client does not support the 'server-time' capability -- irc.domain.tld: https://ircv3.net/specs/extensions/server-time -- irc.domain.tld: History request refused. The spec page, located at https://ircv3.net/specs/extensions/chathistory states: Full support for this extension requires support for the batch, server-time and message-tags capabilities. However, limited functionality is available to clients without support for these CAPs. Servers SHOULD NOT enforce that clients support all related capabilities before using the chathistory extension. This seems to imply that clients should still be able to use CHATHISTORY even if it doesn't support SERVER-TIME? | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
