TL;DR
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Parley is a working proof of concept for a federated chat network that connects separate domain-run instances while letting people use standard IRC clients. Its report describes signed HTTPS messaging, automatic peer discovery and shared channels, while warning that the software is not hardened yet.
Parley has published a working proof of concept for a federated chat network that connects separate, domain-run instances and lets users participate through standard IRC clients. The project says instances discover one another through DNS and identity documents, then exchange signed messages over HTTPS; it also cautions that the software is not hardened yet.
In Parley’s design, each person or team runs a small instance for its own domain. Accounts use email-like names, such as alice@foo.com, and a user can message someone at another domain with an IRC command such as /msg alice@foo.com. The project says the instances can establish contact even if they have not communicated before. Its demonstration uses two instances and stock irssi sessions; the report also names WeeChat and Textual as compatible clients, with no client plugins required.
Parley presents ordinary IRC features alongside several IRCv3 capabilities. It lists server-time, message-tags, echo-message, multi-prefix and setname, as well as relaying client tags used for typing indicators. The project also describes channel and private-message history, read markers that follow an account between devices, and multiline pastes treated as a single message. These are project-described features; the supplied material does not include independent testing or user adoption figures.
For discovery, an instance can publish a DNS SRV record and well-known JSON documents containing its public key and inbox address. Federation events are JSON documents sent to a peer’s inbox with a detached Ed25519 signature in request headers, which the receiving instance checks against a discovered key. The report says instances share information about their known peers, allowing a mesh to form. Channel history is stored in SQLite, with full-text search and a feed endpoint; a returning peer can retrieve messages it missed during an outage.
IRC Clients Across Separate Domains
Parley’s development matters to people who want to communicate across independently operated services while keeping familiar IRC software. Its approach puts federation at the server level: participants connect to their own domain’s instance, while those instances carry messages between them. If the design works reliably beyond its demonstration, it could let teams share channels without relying on one centrally operated chat service or asking users to replace their clients.
The project also makes choices about control and moderation that differ from conventional IRC networks. It describes global channels as replicated across linked instances, with no owner, topic or channel operators. Instead, a user can block a mask for their own account, while an administrator can apply a block across an instance. That model may suit a network without a central channel authority, but it leaves operational questions about shared governance and abuse response that the source material does not resolve.
Those possibilities remain prospective. A working proof of concept shows that the project’s described components can be demonstrated together, but it does not establish readiness for production use, the size of any user community or how the network would perform under heavy load. The project itself flags the gap: it says the software is not hardened.
Top picks for "parley federat decentralis"
As an affiliate, we earn on qualifying purchases.
How Parley Connects Instances
Parley combines an IRC-facing service with a separate mechanism for finding and communicating with other instances. Users connect to their local instance with a password or an IRC token, or through supported single sign-on arrangements. For an account such as alice@foo.com, the local part becomes the IRC nick and the domain becomes the host portion of the displayed identity. The project says commands including WHOIS can consult a user’s well-known identity document.
Channels have two forms in the report. A global channel, such as #dev, is replicated across linked instances that have members in it. A local channel, such as ¬es, remains on its own instance and can have a topic. Parley’s project page also describes a demonstration that runs two instances with local DNS records, a certificate authority and scripted IRC sessions. It says production deployments instead need a domain, TLS certificate and DNS SRV record; the instance’s data directory holds its key, accounts, peer cache and channel logs.
“Federated, decentralised chat that speaks plain IRC.”
— Parley project report
Production Readiness Remains Open
The report does not establish whether Parley has undergone an independent security review, how it handles large networks, or how administrators would coordinate responses to spam and abuse across domains. Its signed-message design describes how a receiving instance checks a sender’s key, but the supplied material does not document a full threat assessment, key-revocation process or recovery procedures.
It is also unclear how many people or independently operated instances use the project outside its demonstration. The source provides no deployment count, performance results, uptime data or release timeline. The project explicitly says it is not hardened yet, so the proof of concept should not be read as evidence that it is ready for a production service.
Hardening and Deployment Details
The project’s next stated step is not specified in the supplied material. It does describe how operators could try an instance: run the container image, persist its data directory, create an administrator and accounts, provide HTTPS through a reverse proxy or Parley’s TLS options, and configure DNS for discovery. The report says a local demo can exercise two instances without public DNS, while production use depends on domain-based discovery and TLS.
Readers assessing future progress can look for project updates on security hardening, documented deployment requirements and evidence from real-world use. Until those details are available, Parley’s status remains that of a demonstrated design whose broader reliability and operational practices are still unconfirmed.
Key Questions
What is Parley?
Parley is a project for federated chat that presents conversations through ordinary IRC clients while connecting separately run instances across domains.
Do users need a special IRC client?
The project says users can connect with standard clients such as irssi, WeeChat and Textual, without installing client plugins.
How do Parley instances find one another?
The described design uses DNS SRV records and well-known identity documents to locate instances and their public keys. Instances then exchange signed events over HTTPS.
Is Parley ready for production?
The project calls it a working proof of concept and says it is not hardened yet. The supplied report does not establish production readiness.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
