Re:IRC turns thirty
by lmm on Friday August 24, 2018 @07:48AM
(#17834304)
IRC can't ever have authentication, because most clients won't support it. You can't have conversations that rely on rich text, code blocks with syntax highlighting, embedded images, or web previews: these things are possible (in some cases there's more than one way of doing them) but some users will always be using clients that don't support them, and will regard you as the problem if you try to create an expectation that clients should support those things. In turn this makes useful integrations hard: you can have a bot that sends an alert message that heap usage is high on your server, but it's not going to be able to include a graph. IRC can't ever have server-side history and synchronise read status between devices; you can run another server that does that for you (whether that be IRCCloud, ZNC or something else), but at that point you're not actually using IRC, you're using that server's protocol.
[ Parent
| on HN ]
Having to share Gists instead of inlining code blocks, and (of less importance) reaction gifs, was a huge non-starter.
"Most" important clients support SASL authentication already.
Sure. But good luck persuading a network to go authenticated-only, or even configuring your private server that way. It's not impossible but it's very much not the culture and not where the documentation/support will guide you.