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 presents a working proof of concept for a chat network in which people run instances for their own domains and connect using standard IRC clients. Its creator says instances can discover one another through DNS and exchange signed messages, but the project is not yet hardened for production.
Parley has published a working proof of concept for a federated chat network that users can access with standard IRC clients, according to the project’s report. Its design lets independently run servers discover one another and exchange signed messages, while the creator cautions that the software is not hardened yet.
In Parley’s model, a person or team runs a small server for its own domain. Accounts use email-like addresses, such as alice@foo.com, and a user on another server can address that account from an IRC client. The project says the two instances can establish a connection even if they have not previously encountered one another. Its demonstration uses two instances and unmodified irssi sessions.
Parley connects ordinary IRC clients through an IRC server interface. The report lists support for password or SASL PLAIN login, along with several IRCv3 features, including server time, message tags, message echoes and multiple user prefixes. It also describes cross-instance relaying of client tags, such as typing indicators, and preservation of reply tags. These are capabilities described by the project; the report does not provide independent testing results.
Each instance publishes discovery information through DNS and well-known identity documents. Events are sent as JSON over HTTPS, with detached Ed25519 signatures that receiving instances verify against discovered keys. The project says peering can begin when a user messages someone on a new domain, and linked instances share information about other peers. It also describes history stored in SQLite, with full-text search and retrieval of messages missed while a peer was offline.
A Familiar Client for Federated Chat
Parley’s approach could let users communicate across independently managed servers without giving up the familiar commands and clients of IRC. That matters to communities that want domain-based identities and local control over their infrastructure, while still using tools such as irssi, WeeChat or Textual. The project’s account model also makes a person’s server part of their address, so users can message someone on another domain without first joining the same server.
The design distributes operational responsibility across instance operators. There is no central server in the project’s stated model, and global channels are replicated across linked instances that have members in them. That structure also changes how moderation works: Parley describes bans as account-level or instance-level block lists, rather than actions by channel operators. The practical reliability, security and usability of these choices remain unestablished by the proof-of-concept report.
Top picks for "parley federat decentralis"
As an affiliate, we earn on qualifying purchases.
How Parley Builds Its Network
The project distinguishes between global channels, which replicate among linked instances and have no owner, topic or operators, and local channels, which remain on one instance and can have a topic. Its report says global-channel moderation relies on block lists: users can block an account or a whole domain, while an administrator can apply a block across the instance.
Parley maps its accounts onto familiar IRC identity fields. The project says a user such as Alice appears with a nick and host corresponding to her account and domain; IRC commands including NAMES, WHO and WHOIS are intended to reflect that mapping. A WHOIS lookup can consult the user’s identity document. Users can also access channel and private-message history, with read markers associated with the account so that a client can receive the reading position when it joins.
The report outlines a production setup involving persistent storage for keys, accounts, peer information and channel logs; HTTPS in front of the web service; and a DNS SRV record to help other instances locate the server. It says the IRC listener itself is plaintext, so operators need a separate TLS endpoint for IRC clients. A bundled local demo uses test DNS and a local certificate authority; the project identifies its insecure and manual-resolution options as development tools.
“Federated, decentralised chat that speaks plain IRC.”
— Parley project report
Security and Scale Remain Untested
The report does not provide an independent security review, details of testing at scale, or evidence about how the network performs under sustained use. It explicitly says the proof of concept is not hardened yet. The materials also do not establish how operators will handle abuse across instances, disputes over block lists, or recovery from compromised keys. Although the project describes signed federation and history recovery after outages, those design features alone do not establish their resilience in real-world deployments.
No release schedule, adoption figures, or roadmap milestones are given in the supplied report. It is also unclear what level of compatibility users can expect across the range of IRC clients and optional protocol features. These questions will matter as the project moves beyond its demonstration.
From Demonstration to Deployment
The next step described by the project is for operators to run instances using real domains, TLS certificates and DNS records. Parley provides a container image and a sample Docker Compose configuration, as well as account-management options through a command-line tool, an admin page, an HTTP API or single sign-on. The report also points to setup documentation for authentication and a demo that shows two instances exchanging messages.
The project has not supplied dates for a hardened release or broader deployment. Prospective operators will need to assess the current limitations and deployment requirements, while users will need an instance and an IRC client configured to connect to it. Further security documentation, testing and evidence from real deployments would clarify how well the design holds up outside the proof of concept.
Key Questions
What is Parley?
Parley is a chat project that connects independently run domain-based instances and presents the network through an IRC-compatible interface.
Do users need a special IRC client?
The project says users can connect with ordinary clients such as irssi, WeeChat or Textual, without plugins. The report does not independently verify compatibility across all clients.
How do Parley instances find one another?
Parley describes discovery through DNS records and well-known identity documents. Instances exchange JSON events over HTTPS, with signatures that receiving servers verify against discovered keys.
Is Parley ready for production?
The project calls it a working proof of concept and says it is not hardened yet. The report does not give a production-ready release date.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
