2023 had been a slow year, so we skipped on our traditional annual update, but it is back this year. here’s a summary of everything that’s been happening since Nov 2022. Most of the progress these last two years have been around making chathistory more suitable for the real world, and reducing bandwidth usage for mobile clients. Specs ratified Sadly, none during this time span. We’ll try to do better next year. New drafts Aug 2023 pre-away - Allows clients to update - or not update - th...| IRCv3 Working Group
Following our tradition of the annual update, here’s a summary of everything that’s been happening since Nov 2021. Specs ratified Feb 2022 WHOX - Allows clients to request additional information on other clients. Apr 2022 Bot mode - Allows identifying clients presenting themselves as bot to other clients Oct 2022 Extended monitor - Extends monitor to more commands and notifications New drafts Jun 2022 channel-context client tag - Allows sending private messages to clients, while displayin...| IRCv3 Working Group
Following our tradition of the annual update, here’s a summary of everything that’s been happening since Feb 2020. Specs ratified Feb 2020 setname - Allows users to change their realname without reconnecting May 2020 Typing notifications - Displays to others when you’re typing Apr 2021 UTF8ONLY isupport key - Indicates that server will only accept UTF8 encoded messages #432 New drafts Apr 2020 Multiline messages - Allows multiple lines per message #398 Sep 2020 Channel renaming - Enable...| IRCv3 Working Group
We’ve finalised the Standard Replies extension which lets us respond with information, warnings, and command errors in a more consistent way. It’s already in use by the SETNAME draft and will enable further development of proposals such as the CHATHISTORY extension which we’re still developing. We’ve also ratified the Labeled responses spec, which lets client software properly track and handle responses to their commands. Check the support tables to see which software is already prepa...| IRCv3 Working Group
Time for our annual blog post! There’s been a lot going on so we’ll summarize what we’ve been up to lately. First, we’ve rewritten the Capability Negotiation spec. Previously, capabilities were described in three separate documents, which made things pretty hard-to-understand for implementers. The updated document makes it a lot easier to understand and write software that negotiates capabilities. We’ve ratified the Message Tags spec, which merges the two separate tag-describing doc...| IRCv3 Working Group
Happy New Year! It’s been a while since we’ve updated, so there’s a heap of changes to go through. First off, in WG news, we’ve introduced a new site design and a new logo for IRCv3, thanks primarily to dan- and jwheare! Here’s our new logo, in a variety of formats: On the spec side, we’ve added the new message-tags draft [link] which introduces the TAGMSG message, allowing clients to pass metadata to each other freely. This spec also increases the size limit on tags from 512 to 4...| IRCv3 Working Group
There’s been a bunch of newly-submitted proposals recently, looking at everything from history retrieval with bouncers to message reactions. Let’s go over the holiday changes. The labeled-response draft [link] was added. This draft links sent commands to returned numerics/messages much more effectively for clients, allowing more complete implementations of echo-message. The message-ids draft [link] was added. This draft provides a network-unique identifier on messages, which allows many n...| IRCv3 Working Group
IRCv3 Development Community| ircv3.net
IRCv3 Development Community| ircv3.net