adam/znc
1
0 Fork 0
mirror of https://github.com/znc/znc.git synced 2026-10-31 01:32:02 +01:00
Code Issues 362 Packages Projects Releases Wiki Activity

Finalize server-time #110

New Issue
Closed
opened 2026-10-05 03:59:29 +02:00 by adam · 5 comments
adam commented 2026-10-05 03:59:29 +02:00
Owner
Copy link
Copy source

Create a final specification for server-time, this should include how a client should handle MODE,JOIN,PART,QUIT,KICK's which have a time set.

Create a final specification for server-time, this should include how a client should handle MODE,JOIN,PART,QUIT,KICK's which have a time set. <!-- github-sync-id:4770176 -->
adam closed this issue 2026-10-05 03:59:29 +02:00
adam commented 2026-10-05 03:59:30 +02:00
Author
Owner
Copy link
Copy source

It handles all such messages as just "happened at the given time".

So the specs were accepted to IRC v3.2: Message Tags and server-time.

Differences from current znc.in/server-time:

  • capability name is server-time instead of znc.in/server-time
  • tags delimiter is ; instead of ,
  • tag name is time instead of t
  • the precision of the timestamp is milliseconds

Need to change it in ZNC. Also need to read the timestamp from IRC server, if it offers such capability.

It handles all such messages as just "happened at the given time". So the specs were accepted to IRC v3.2: [Message Tags](http://ircv3.atheme.org/specification/message-tags-3.2) and [server-time](http://ircv3.atheme.org/extensions/server-time-3.2). Differences from current `znc.in/server-time`: - capability name is `server-time` instead of `znc.in/server-time` - tags delimiter is `;` instead of `,` - tag name is `time` instead of `t` - the precision of the timestamp is milliseconds Need to change it in ZNC. Also need to read the timestamp from IRC server, if it offers such capability. <!-- github-comment-id:7500519 -->
adam commented 2026-10-05 03:59:31 +02:00
Author
Owner
Copy link
Copy source

The spec needs to be updated to use TAI instead of UTC Unix timestamp to defend against leap seconds.
ZNC implementation should be updated too.

The spec needs to be updated to use TAI instead of UTC Unix timestamp to defend against leap seconds. ZNC implementation should be updated too. <!-- github-comment-id:9458544 -->
adam commented 2026-10-05 03:59:31 +02:00
Author
Owner
Copy link
Copy source

Adding server-time to all messages will become easier after #506 is done. I'll start working on it after the release.

Adding server-time to all messages will become easier after #506 is done. I'll start working on it after the release. <!-- github-comment-id:72373601 -->
adam commented 2026-10-05 03:59:32 +02:00
Author
Owner
Copy link
Copy source

This issue has been done, to complete a final specification (which is now in IRCv3).

This issue has been done, to complete a final specification (which is now in IRCv3). <!-- github-comment-id:87342368 -->
adam commented 2026-10-05 03:59:32 +02:00
Author
Owner
Copy link
Copy source

Except the name of cap, which waits for IRC 3.2 to be released, when we can drop the znc.in/ prefix.

Except the name of cap, which waits for IRC 3.2 to be released, when we can drop the `znc.in/` prefix. <!-- github-comment-id:87368224 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#110