View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005280 | unreal | ircd | public | 2019-05-17 14:51 | 2019-12-28 09:43 |
| Reporter | syzop | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 5.0.0-alpha4 | ||||
| Summary | 0005280: IRCv3 features to implement in U5 | ||||
| Description | This is main goal of UnrealIRCd 5. To implement: - account-tag - batch - echo-message - message-tags - msgid - server-time - labeled-response (draft) To investigate: - invite-notify - draft/setname Not to implement (at this time, anyway): - Monitor See also https://ircv3.net/software/servers.html at the bottom to see what UnrealIRCd does and does not support. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
A lot of the foundation and basic support has been done for: batch, msgid, account-tag, labeled-response, server-time. Most, if not all, of the difficult stuff, anyway. I've added a number of notable FIXME's in the code. The other ones still need to be implemented but are more easy. I'll focus first on getting the existing ones working ok, before concentrating on the rest. (But first I'm looking at U5 in general, what to include, so may still be a few days) |
|
|
Bump. Some of this has been implemented. Some not. Various things need more testing. There have been maaaaany API changes to accommodate the IRCv3 message tags support. Still to do are the hook changes, to pass a MessageTag * in there. That will be "fun". After that, hmm, not sure if there will need to be more API changes, I don't think so.. but.. |
|
|
Bump. Guess I will need to do the hook changes soon. Fun.... |
|
|
Working correctly (seemingly): - account-tag - batch - echo-message - message-tags - msgid - server-time Not working correctly: - labeled-response (draft) <- will be looked at later, not a high priority item To investigate, but likely post-5.0.0: - invite-notify - draft/setname Not to implement (at this time, anyway): - Monitor |
|
|
Labeled-response is now seemingly working properly. I'm fine with the current featureset. Closing. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-05-17 14:51 | syzop | New Issue | |
| 2019-05-17 14:52 | syzop | Relationship added | child of 0005279 |
| 2019-05-17 14:56 | syzop | Note Added: 0020675 | |
| 2019-05-17 14:56 | syzop | Assigned To | => syzop |
| 2019-05-17 14:56 | syzop | Status | new => assigned |
| 2019-05-17 14:58 | syzop | Sticky Issue | No => Yes |
| 2019-07-07 16:19 | syzop | Note Added: 0020761 | |
| 2019-07-13 15:45 | syzop | Relationship added | parent of 0005330 |
| 2019-07-13 15:45 | syzop | Note Added: 0020777 | |
| 2019-08-13 18:51 | syzop | Note Added: 0020814 | |
| 2019-08-18 15:17 | syzop | View Status | private => public |
| 2019-10-06 07:40 | syzop | Status | assigned => resolved |
| 2019-10-06 07:40 | syzop | Resolution | open => fixed |
| 2019-10-06 07:40 | syzop | Fixed in Version | => 5.0.0-alpha4 |
| 2019-10-06 07:40 | syzop | Note Added: 0020935 | |
| 2019-10-06 07:41 | syzop | Note Edited: 0020935 | |
| 2019-12-28 09:43 | syzop | Sticky Issue | Yes => No |
