AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Notices limechat1/6/2024 ![]() Often, timezone information and second precision are lost. Some clients can be extended to parse the ZNC timestamp and use it for their own display, but the ZNC timestamp is only meant to be human readable.The ZNC timestamp duplicates any formatting the client may do, causing two timestamps to be displayed.But there are several disadvantages to this: Currently this happens for the PRIVMSG, NOTICE, and WALLOPS commands. ZNC has solved this by reformatting the actual body of messages and appending or prepending a timestamp where possible. This will always be the time at which the client connected, rather than the actual time the message was sent. ![]() The IRC protocol does not communicate time, however, and a client would typically attribute these buffered messages to the time the client received them. When a client reconnects, these buffers are sent back to the client to give the user some chat history from while he/she was away. ![]() ZNC as a bouncer has the built-in ability to log messages to buffers, even while no client is connected. On this page we propose an extension to the IRC protocol, activated at the request of a client, which allows IRC servers to communicate time to clients in a machine readable format. Don't use it as a specs for the extension įinal version of the spec is here: Message Tags and server-time This page is here only for historical reasons. Don't use it as a specs for the extension
0 Comments
Read More
Leave a Reply. |