killous.blogg.se - Best irc clients 2018

#BEST IRC CLIENTS 2018 UPDATE#
#BEST IRC CLIENTS 2018 REGISTRATION#
#BEST IRC CLIENTS 2018 SOFTWARE#

The proposed SETNAME command is now an IRCv3 draft. We’re also exploring options around preload lists and other ways of protecting users’ connections before plaintext hits the wire. The Strict Transport Security extension is recommended as it can also protect connections after the initial one. The STARTTLS command has been deprecated in favour of sts. The WebIRC command has been documented and extended as a formal standard, letting gateways now flag when an incoming connection is using TLS. This, for example, lets users react or refer to specific messages. We’ve also ratified the Message IDs spec, which lets servers assign IDs to chat messages and any other events sent to clients. Clients can also exchange tag data between themselves with the new TAGMSG message.

The final version includes a boosted size limit for tags and defines the ERR_INPUTTOOLONG (417) numeric, so clients can send more data and know when they’ve reached the limit.

We’ve ratified the Message Tags spec, which merges the two separate tag-describing documents we used to have.

#BEST IRC CLIENTS 2018 SOFTWARE#

The updated document makes it a lot easier to understand and write software that negotiates capabilities. Previously, capabilities were described in three separate documents, which made things pretty hard-to-understand for implementers. Time for our annual blog post! There’s been a lot going on so we’ll summarize what we’ve been up to lately.įirst, we’ve rewritten the Capability Negotiation spec.

#BEST IRC CLIENTS 2018 UPDATE#

In Aug 2021, The charter page had an update to better reflect our loose governance structure, deprecating the concept of the “technical board” and clarifying what it means to be listed as a “contributor” #399įinally, do check the support tables to see how adoption of our specs is coming along, there’ve been a lot of busy implementations over the past year. And we’ve also made a lot of clarifications, improvements and typo fixes to specs that don’t materially affect compatibility, too many to list here. We’ve tidied up the spec structure making URLs, titles, etc more consistent #441. Highlights from our ongoing roadmap milestone Nov 2021 WebIRC - Client certificate fingerprint options #463.May 2020 Message tags - CLIENTTAGDENY isupport token #412.

Nov 2021 Extended monitor - Extends monitor to more commands and notifications #466.

#BEST IRC CLIENTS 2018 REGISTRATION#

Nov 2021 Account registration - Allows account registration without non-standard bot or services messaging #435.

Nov 2021 Client batches - This was split off from multiline into its own framework for use by other specs #454.

Sep 2021 WebSocket - Allows web clients to connect to IRC servers directly #342.

Apr 2021 Bot mode - Indicates that a user is a bot via a mode and WHOIS numeric, and adds a tag to their messages #439.

Nov 2020 chathistory - Allows fetching historical messages from a channel #393.

Sep 2020 Channel renaming - Enables channel renaming #420.

Apr 2020 Multiline messages - Allows multiple lines per message #398.

Apr 2021 UTF8ONLY isupport key - Indicates that server will only accept UTF8 encoded messages #432.

May 2020 Typing notifications - Displays to others when you’re typing.

Feb 2020 setname - Allows users to change their realname without reconnecting.

Following our tradition of the annual update, here’s a summary of everything that’s been happening since Feb 2020.