IRCv3

Original Article ↗ Hacker News Discussion ↗

IRCv3 aims to modernize the decades‑old IRC chat protocol with features like persistent history, multi‑device access, metadata (e.g. avatars), WebSocket transport, and even draft support for file uploads, bringing it closer to Discord- or Slack-style usability. Commenters weigh this effort against the convenience and polish of centralized platforms, debating trade‑offs around mobile support, media sharing, voice, federation, and the friction of bouncers or self‑hosting. While many appreciate IRC’s simplicity, decentralization, and nostalgia, others question whether incremental, fragmented extensions and limited developer capacity can keep it relevant against newer open protocols like Matrix or fully proprietary chat ecosystems.

Role of IRC Today

  • Seen as one of the few “old Internet” protocols still actively used largely unchanged, alongside SMTP, FTP, etc.
  • Use cases: technical communities, internal company comms during outages, hobbyist and nostalgia-driven chat, and small self-hosted friend groups.
  • Some argue IRC is effectively “dead” or niche compared to Discord/Slack/Matrix; others see its persistence as proof of lasting value.

IRCv3 Goals and Capabilities

  • Aims to modernize IRC with extensions like:
    • Persistent history (chathistory) so servers can replay missed messages without a bouncer.
    • Metadata (e.g., avatars) and multi-device access.
    • WebSocket transport and TLS as de facto modern expectations.
    • Drafts for file sharing.
  • Modern servers (e.g., Ergo) and clients (Halloy, Mango, Goguma, The Lounge, IRCCloud, etc.) already implement many extensions.

Mobile, Persistence, and Bouncers

  • Major historical pain points: no offline messages, bad mobile experience, and need for always-on clients or bouncers.
  • IRCv3 history plus servers with built‑in bouncer-like features address this, but require both server and client support.
  • Critics say needing bouncers or special servers is extra friction that drives mainstream users to centralized services.

Media, File Sharing, and Rich Features

  • Many want image/video embeds, file uploads, and even voice/video to compete with Discord/Slack.
  • Others argue this breaks IRC’s appeal as lightweight, text-only, and ephemeral; recommend bolting on separate infrastructure instead.
  • File-sharing extensions exist in draft; some clients already provide uploads backed by external storage.

Decentralization vs Centralization

  • Strong appreciation for IRC’s decentralized, non-corporate nature and optional identities, contrasted with Discord/WhatsApp/Signal.
  • Some note that hosted bouncer services (e.g., IRCCloud) reintroduce centralization, though without protocol lock‑in.
  • Experiments like Parley/Ahoy aim to make IRC-style chat federated between independent servers in a more email-like sense.

Fragmentation, Governance, and Pace

  • Concern that many optional IRCv3 extensions create a fragmented experience (e.g., some users see replies/reactions, others don’t).
  • Comparisons are drawn to XMPP’s problems with too many XEPs.
  • Some feel IRCv3 progresses slowly and may lack strong leadership and developer resources; burnout among IRC devs is mentioned.
  • Others emphasize IRCv3 is a loose working group, not a corporate standards body, and anyone can propose extensions.