IRCv3 is shaping to be amazingly good!

in summary, i feel incredibly validated in being a long-time IRC holdout

in summary, i feel incredibly validated in being a long-time IRC holdout

Which network is going to be the first to shift to this, do you speculate?

@whitequark

@futuresprog Libera is rolling out IRCv3 soon, which is going to be big https://libera.chat/news/new-and-upcoming-features-3

Neat! I'm already there. I guess I'd better update my irssi to take full advantage of the features.

@whitequark

IRCv3 is shaping to be amazingly good!

here's the things it offers, today, right now, on a chat server we just set up in one evening:

• you don't need a bouncer (friggin finally)
• there are moblie clients that work well
• you can see backlog when joining a channel
• you can browse chat history
• you can connect from multiple devices with one account and nickname
• if you disconnect, your nickname is still present in a channel you joined, marked as away
• you can highlight or DM people who are away and they'll see your message when they join (without crutches like MemoServ)
• there is a "last read message" marker and it is synchronized between multiple connections
• messages have identifiers (and server timestamps) and replies can be tagged with the message you're replying to
• you don't need to deal with fussy nonsense like NickServ authorization, ghosting, or such; connect with your username and password and that's it
• there are typing notifiers, if you want them
• there are message reactions, if you want them

here's the things it does not offer:

• image, video, or file uploads
• stickers
• complex onboarding tools

caveat: since IRCv3 is a true extension of IRCv2, the features listed above work if they're supported by both the server and the client. in my onboarding experience so far, people do not find it difficult to find a suitable client, but your mileage may vary. on the flipside, legacy clients will work just fine.

unexpectly, i realized that IRCv3 can completely replace Matrix rooms for my own group chat purposes, and i'm probably not going to set up any Matrix homeservers again; it's just not worth it and frankly I should instead put that effort into coming up with a file upload IRCv3 extension or something

@futuresprog @whitequark yeah i need to find myself an ircv3 capable client I'm still using Pidgin which I started for AIM, MSN, Yahoo, and IRC.

Of those, IRC is the only one still around.

@whitequark
> you don't need a bouncer

WHAT

okay now I'm definitely interested

@groxx yeah it just works the way you'd expect haha

@whitequark @groxx

I haven't used IRC in decades. I remember having to deal with nickserv, but what was the bouncer for?

IRCv3 is shaping to be amazingly good!

here's the things it offers, today, right now, on a chat server we just set up in one evening:

• you don't need a bouncer (friggin finally)
• there are moblie clients that work well
• you can see backlog when joining a channel
• you can browse chat history
• you can connect from multiple devices with one account and nickname
• if you disconnect, your nickname is still present in a channel you joined, marked as away
• you can highlight or DM people who are away and they'll see your message when they join (without crutches like MemoServ)
• there is a "last read message" marker and it is synchronized between multiple connections
• messages have identifiers (and server timestamps) and replies can be tagged with the message you're replying to
• you don't need to deal with fussy nonsense like NickServ authorization, ghosting, or such; connect with your username and password and that's it
• there are typing notifiers, if you want them
• there are message reactions, if you want them

here's the things it does not offer:

• image, video, or file uploads
• stickers
• complex onboarding tools

caveat: since IRCv3 is a true extension of IRCv2, the features listed above work if they're supported by both the server and the client. in my onboarding experience so far, people do not find it difficult to find a suitable client, but your mileage may vary. on the flipside, legacy clients will work just fine.

unexpectly, i realized that IRCv3 can completely replace Matrix rooms for my own group chat purposes, and i'm probably not going to set up any Matrix homeservers again; it's just not worth it and frankly I should instead put that effort into coming up with a file upload IRCv3 extension or something

IRCv3 is shaping to be amazingly good!

here's the things it offers, today, right now, on a chat server we just set up in one evening:

• you don't need a bouncer (friggin finally)
• there are moblie clients that work well
• you can see backlog when joining a channel
• you can browse chat history
• you can connect from multiple devices with one account and nickname
• if you disconnect, your nickname is still present in a channel you joined, marked as away
• you can highlight or DM people who are away and they'll see your message when they join (without crutches like MemoServ)
• there is a "last read message" marker and it is synchronized between multiple connections
• messages have identifiers (and server timestamps) and replies can be tagged with the message you're replying to
• you don't need to deal with fussy nonsense like NickServ authorization, ghosting, or such; connect with your username and password and that's it
• there are typing notifiers, if you want them
• there are message reactions, if you want them

here's the things it does not offer:

• image, video, or file uploads
• stickers
• complex onboarding tools

caveat: since IRCv3 is a true extension of IRCv2, the features listed above work if they're supported by both the server and the client. in my onboarding experience so far, people do not find it difficult to find a suitable client, but your mileage may vary. on the flipside, legacy clients will work just fine.

unexpectly, i realized that IRCv3 can completely replace Matrix rooms for my own group chat purposes, and i'm probably not going to set up any Matrix homeservers again; it's just not worth it and frankly I should instead put that effort into coming up with a file upload IRCv3 extension or something

IRCv3 is shaping to be amazingly good!

here's the things it offers, today, right now, on a chat server we just set up in one evening:

• you don't need a bouncer (friggin finally)
• there are moblie clients that work well
• you can see backlog when joining a channel
• you can browse chat history
• you can connect from multiple devices with one account and nickname
• if you disconnect, your nickname is still present in a channel you joined, marked as away
• you can highlight or DM people who are away and they'll see your message when they join (without crutches like MemoServ)
• there is a "last read message" marker and it is synchronized between multiple connections
• messages have identifiers (and server timestamps) and replies can be tagged with the message you're replying to
• you don't need to deal with fussy nonsense like NickServ authorization, ghosting, or such; connect with your username and password and that's it
• there are typing notifiers, if you want them
• there are message reactions, if you want them

here's the things it does not offer:

• image, video, or file uploads
• stickers
• complex onboarding tools

caveat: since IRCv3 is a true extension of IRCv2, the features listed above work if they're supported by both the server and the client. in my onboarding experience so far, people do not find it difficult to find a suitable client, but your mileage may vary. on the flipside, legacy clients will work just fine.

unexpectly, i realized that IRCv3 can completely replace Matrix rooms for my own group chat purposes, and i'm probably not going to set up any Matrix homeservers again; it's just not worth it and frankly I should instead put that effort into coming up with a file upload IRCv3 extension or something

IRCv3 is shaping to be amazingly good!

here's the things it offers, today, right now, on a chat server we just set up in one evening:

• you don't need a bouncer (friggin finally)
• there are moblie clients that work well
• you can see backlog when joining a channel
• you can browse chat history
• you can connect from multiple devices with one account and nickname
• if you disconnect, your nickname is still present in a channel you joined, marked as away
• you can highlight or DM people who are away and they'll see your message when they join (without crutches like MemoServ)
• there is a "last read message" marker and it is synchronized between multiple connections
• messages have identifiers (and server timestamps) and replies can be tagged with the message you're replying to
• you don't need to deal with fussy nonsense like NickServ authorization, ghosting, or such; connect with your username and password and that's it
• there are typing notifiers, if you want them
• there are message reactions, if you want them

here's the things it does not offer:

• image, video, or file uploads
• stickers
• complex onboarding tools

caveat: since IRCv3 is a true extension of IRCv2, the features listed above work if they're supported by both the server and the client. in my onboarding experience so far, people do not find it difficult to find a suitable client, but your mileage may vary. on the flipside, legacy clients will work just fine.

unexpectly, i realized that IRCv3 can completely replace Matrix rooms for my own group chat purposes, and i'm probably not going to set up any Matrix homeservers again; it's just not worth it and frankly I should instead put that effort into coming up with a file upload IRCv3 extension or something

@futuresprog Libera is rolling out IRCv3 soon, which is going to be big https://libera.chat/news/new-and-upcoming-features-3

@whitequark Intriguing. Any recommendations for compatible servers and clients?

If session persistence is a thing now, that feels like a real step forward for IRC (having to use a bouncer or a client running on a server somewhere is a high bar for a lot of people, especially more casual users).

@whitequark @futuresprog they've had "IRCv3 support" since inception AFAIK (I believe even freenode had it)

what they're rolling out is support for some extensions to IRCv3, in particular the `message-tags` specification which will support things like `+draft/reply` by adding a new capability to add a bunch of metadata to a message (which involves bumping the line length up 8191 bytes, allowing for just under 4K of tag data)

IRCv3's capability negotiation is such a powerful way to let the ecosystem continue to grow in a way that allows more granular specifications

@whitequark this is awesome! Which daemon are you using?

@whitequark Hm. Would the server lose the backlog and the rest of the state if it's restarted, or is it supposed to store it all now?

@kevin ergochat