Parley: Federated, Decentralised Chat That Speaks Plain IRC

TL;DR

Prime Big Deal Days · Oct 6–7Offer from Amazon

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

Start your free Prime trial →Free trial for eligible customers · Cancel anytime

As an affiliate, we earn on qualifying purchases.Hide

Parley is a working proof of concept for a chat network where independently run instances discover one another and exchange signed messages, while users connect through ordinary IRC clients. Its developer says it demonstrates the design end to end but is not yet hardened for production.

Parley is a working proof of concept for a federated chat network that lets people communicate through ordinary IRC clients while running separate instances under their own domains. Its developer says the system demonstrates discovery, signed message exchange and channel history across instances, but it is not yet hardened.

In Parley, each person or team runs an instance for its domain. Instances use DNS records and well-known identity documents to find one another, then exchange events as JSON documents over HTTPS, with detached Ed25519 signatures. The project says a user can message someone on a domain their instance has not encountered before; the servers discover each other and begin peering automatically.

Users connect with stock clients such as irssi, WeeChat or Textual, without a client plugin. The project maps a user’s local name and domain to familiar IRC identity fields, so a person such as Alice on foo.com appears as alice!alice@foo.com. Parley also describes support for IRCv3 features, including message tags and server time, alongside history replay and account-level read markers.

The project describes two channel types: global channels replicated among linked instances, and local channels that remain on one instance. Its stated moderation approach reflects that distinction: global channels have no owner or operators, while users and administrators can apply block lists. Each instance stores channel history in SQLite, and the project says returning peers can retrieve messages missed during outages.

IRC Clients Across Server Domains

Parley’s design could let people on separate servers communicate without choosing a single central service or replacing the IRC clients they already use. The combination of domain-based identities and automatic peering aims to make cross-server messaging work without users manually configuring each connection.

The proof of concept also makes a practical trade-off visible. Familiar IRC clients provide the user interface, while features such as cross-device read markers and history synchronization depend on Parley’s server and protocol behavior. Whether the system can offer those features reliably and securely at larger scale is not established by the project description.

How Parley Connects Instances

The project says instances publish discovery information through DNS SRV records and documents under a well-known URL. When a message goes to a new domain, servers can exchange peer information and form a mesh. The developer says this approach mirrors how Salty IM finds people.

For a production deployment, the project instructions call for a real domain, TLS, an SRV record and persistent storage for the instance key, accounts, peer cache and channel logs. The IRC listener is described as plaintext by default, so operators need to put TLS in front of it or configure TLS directly. The repository also includes a local two-instance demo, but its development-only settings are not production configuration.

“Federated, decentralised chat that speaks plain IRC.”

— Parley project description

Security and Scale Remain Open

The project explicitly says Parley is not hardened. The supplied material does not give an independent security assessment, deployment scale, reliability measurements or evidence from long-term production use. It also does not establish how the network would handle abuse, disputes between instance operators or malicious peers beyond the described signature checks and block lists.

Those gaps matter because federation allows independently managed servers to connect and exchange content. The project says receivers verify signatures against discovered keys, but the description alone does not show how key changes, compromised instances or larger-scale moderation would be handled in practice. These questions remain unanswered by the available material.

Hardening Before Wider Deployment

The next step indicated by the project is further development beyond the proof-of-concept stage. Operators can already consult its deployment instructions and run the included demo, while the project identifies real DNS records, TLS and persistent storage as requirements for a domain-based setup.

The material does not provide a release schedule or name a date for a hardened version. Until the developer publishes more detail or independent evaluations become available, Parley’s demonstrated capabilities should be understood as a project-reported proof of concept.

Key Questions

What is Parley?

Parley is a project for federated chat: separate instances connect across domains, while users access the network through ordinary IRC clients.

Do users need a special IRC client?

No special client is described as necessary. The project says users can connect with standard clients such as irssi, WeeChat and Textual, without plugins.

How do Parley instances find each other?

The project describes discovery through DNS SRV records and well-known identity documents. Instances exchange signed events over HTTPS and can peer automatically when a user messages someone on a new domain.

Is Parley ready for production?

The developer calls it a working proof of concept and says it is not hardened yet. The supplied material does not include an independent security review or evidence of production use at scale.

Source: hn