TL;DR
Get the latest gadgets delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
Parley is a new federated, decentralised chat network that presents itself to ordinary IRC clients while instances discover each other via DNS and exchange ed25519-signed messages over HTTPS. Its developer describes it as a working proof of concept that is not yet hardened for production use.
Developer James Mills has released Parley, a federated, decentralised chat network whose instances speak plain IRC to clients such as irssi, WeeChat and Textual, with no plugins required. According to the project’s repository, every person or team runs a small instance for their own domain, instances find each other through DNS and well-known identity documents, and messages are exchanged as ed25519-signed JSON documents over HTTPS. The project is described as a working proof of concept that “is not hardened yet.”
Parley’s design puts ordinary IRC in front and federation behind it. A user connects with any IRC client, authenticating via PASS or SASL PLAIN, and the instance offers IRCv3 extensions including server-time, message-tags, echo-message, multi-prefix, setname and TAGMSG, which relays client-only tags such as typing indicators across the federation. Tags attached to messages are preserved, so a +reply remains a reply when replayed from history, and draft/multiline keeps a pasted paragraph as one message.
Identities resemble email addresses: alice@foo.com runs on foo.com, bob@bar.com on bar.com. According to the repository, Bob can type /msg alice@foo.com hi and the two instances federate on the spot, even if they have never encountered each other before. Discovery uses a _parley._tcp SRV record plus a well-known JSON document publishing the instance’s ed25519 public key and inbox — an approach the project says mirrors how Salty IM finds people.
Parley also implements per-account scrollback: CHATHISTORY pages through channels and private messages, joins replay unread history, and draft/read-marker stores read positions on the account, so marking a channel read on one device clears it on another. Each instance stores channel history in SQLite with a full-text index, served as a feed, and peers that return after downtime pull what they missed. Channels come in two kinds: global channels such as #dev are replicated across linked instances and have no owner, topic or operators, while local channels such as ¬es never leave the instance. Moderation replaces channel ownership with block lists by mask — a single user or an entire instance — applied per account or instance-wide by an admin.
Why IRC Compatibility Matters Here
Most federated chat systems — Matrix being the most prominent — require their own clients or protocols, which fragments the user base and raises the barrier to adoption. Parley’s core bet is that existing, decades-old IRC clients work unmodified, which means anyone already running irssi, WeeChat or Textual can join a federated network without installing anything new. If the design proves robust, it offers a path to decentralised chat that reuses one of the oldest and most widely implemented chat protocols rather than replacing it.
The moderation model is also a deliberate departure from IRC tradition. Because global channels have no owner, nobody can be kicked from them; enforcement shifts entirely to mask-based blocking at the account or instance level. That inverts the usual operator hierarchy and puts filtering decisions in the hands of each user and admin — a design choice that will be tested as the network grows.
Top picks for "parley federat decentralis"
As an affiliate, we earn on qualifying purchases.
The Design Choices Behind Parley
: “Parley draws on several existing patterns. Its DNS-plus-well-known-document discovery follows the approach used by Salty IM, an earlier project by the same developer. Its signed-HTTP event delivery — JSON documents POSTed to a peer’s /inbox with detached ed25519 signatures — resembles the delivery model of ActivityPub-based systems, though Parley is its own protocol. Federation is open by design: according to the repository, any instance whose signature checks out can talk to you, and linked instances exchange peer lists through gossip, forming a mesh without central configuration.
The project ships with deployment aids: a Docker image (prologic/parley), an example docker-compose file, and a demo under demo/ that brings up CoreDNS with SRV records, a local CA and two instances, then runs scripted IRC sessions between them. Accounts can be created via the parleyctl tool, an admin page, an HTTP API, or through single sign-on with any OpenID Connect provider or reverse-proxy identity headers. On first start, the daemon logs a one-time setup URL for creating the first administrator.
“Bob types /msg alice@foo.com hi and it just works, even if the two instances have never heard of each other before.”
— Parley project repository
Limits of the Current Proof of Concept
The project itself flags that Parley is not hardened, and refers readers to a Limitations section, though specific limitations were not detailed in the material reviewed. It is not clear how the system performs under load, how many instances have actually deployed it beyond the developer’s own, or how the open-federation model holds up against spam or hostile instances once blocks are the only moderation tool. Security review of the ed25519 signature verification and the SQLite-backed history storage has not been independently confirmed. The single-sign-on and read-marker features are described in the repository but their interoperability across varied IRC clients is unverified.
Road to a Hardened Network
The logical next steps, based on the project’s own status note, are hardening and wider testing: addressing the documented limitations, obtaining external security review of the federation protocol, and gathering real-world deployments beyond the demo. Interested operators can already run an instance using the published Docker image, provided they configure a domain, TLS termination, persistent storage and an SRV record. Whether a community forms around the project — and whether global, operator-less channels remain workable at scale — will determine if Parley moves beyond proof of concept.
Key Questions
Do I need a special client to use Parley?
No. According to the project, any IRC client works — irssi, WeeChat, Textual and others — with no plugins. Clients that support IRCv3 extensions such as server-time and CHATHISTORY get additional features like cross-device scrollback.
How do Parley instances find each other?
Through DNS: a _parley._tcp SRV record points at the instance, and a well-known JSON document publishes its public key and inbox. Once two instances exchange messages, they also gossip about other peers they know, forming a mesh without manual configuration.
Is Parley ready for production use?
The project describes itself as a working proof of concept that demonstrates the design end to end but “is not hardened yet.” It is best treated as experimental software.
How does moderation work if nobody owns a channel?
Global channels have no operators or topics. Instead, users and admins maintain block lists by mask — blocking a single user or an entire instance domain. A user’s blocks cover their account; an admin’s cover the whole instance.
How is message history handled?
Each instance stores channel history in SQLite with a full-text search index. Peers returning after downtime pull missed messages, and clients receive recent history replayed on join, with read markers synced per account across devices.
Source: hn
Evergreen bestsellers Picks
bestsellers
As an affiliate, we earn on qualifying purchases.
