<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
<title>Presence &amp; Protocol</title>
<link>https://jabberpowered.org/</link>
<description>What XMPP is, where Jabber came from, how to run a federated server and how the XSF turns an idea into a XEP. Written from the RFCs and the specifications.</description>
<language>en</language>
<item><title>Your client's archive on disk, and how to open it</title><link>https://jabberpowered.org/clients/opening-the-archive-on-your-disk/</link><guid>https://jabberpowered.org/clients/opening-the-archive-on-your-disk/</guid><pubDate>Tue, 15 Sep 2026 09:00:00 +0000</pubDate><description>What a desktop client keeps on your own disk, why a plain database file survives, and how to inspect it read only with an ordinary database tool.</description></item>
<item><title>Accessibility in a chat client: what a reader is owed</title><link>https://jabberpowered.org/clients/what-an-accessible-client-owes/</link><guid>https://jabberpowered.org/clients/what-an-accessible-client-owes/</guid><pubDate>Tue, 15 Sep 2026 09:00:00 +0000</pubDate><description>What a chat client owes a reader who did not build it: keyboard use, screen reader labels, contrast, text size, captions, and a first review a volunteer team</description></item>
<item><title>Free-nets: the accounts volunteers kept alive</title><link>https://jabberpowered.org/history/free-nets-and-public-terminals/</link><guid>https://jabberpowered.org/history/free-nets-and-public-terminals/</guid><pubDate>Tue, 15 Sep 2026 09:00:00 +0000</pubDate><description>How free-nets ran on volunteer labour, dial up lines and library terminals, and why a federated address still works the same way.</description></item>
<item><title>Who issues an identity in a network nobody owns</title><link>https://jabberpowered.org/protocol/who-issues-a-digital-identity/</link><guid>https://jabberpowered.org/protocol/who-issues-a-digital-identity/</guid><pubDate>Tue, 15 Sep 2026 09:00:00 +0000</pubDate><description>Authenticating, activating and signing are three different acts. The harder question is who is allowed to issue an identity, and what happens when the issuer</description></item>
<item><title>What one node can see of a federation</title><link>https://jabberpowered.org/servers/what-one-node-can-see/</link><guid>https://jabberpowered.org/servers/what-one-node-can-see/</guid><pubDate>Tue, 15 Sep 2026 09:00:00 +0000</pubDate><description>A server sees its own queues and stanzas in full, and infers the rest. Resolution and revisit set the limits, exactly as they do in Earth observation.</description></item>
<item><title>Agreeing the interface before contact</title><link>https://jabberpowered.org/standards/the-procedure-before-the-transfer/</link><guid>https://jabberpowered.org/standards/the-procedure-before-the-transfer/</guid><pubDate>Tue, 15 Sep 2026 09:00:00 +0000</pubDate><description>Two independent systems can only exchange anything once a published, dated document fixes the coupling, the sequence and the rendezvous in advance.</description></item>
<item><title>What a client does with an animated avatar</title><link>https://jabberpowered.org/clients/animated-avatars-gif/</link><guid>https://jabberpowered.org/clients/animated-avatars-gif/</guid><pubDate>Sat, 12 Sep 2026 09:00:00 +0000</pubDate><description>An avatar is a small image published per account; whether it moves is a client decision. What the standards say and where the animation lives.</description></item>
<item><title>Choosing where your account lives</title><link>https://jabberpowered.org/clients/choosing-where-account-lives/</link><guid>https://jabberpowered.org/clients/choosing-where-account-lives/</guid><pubDate>Sat, 12 Sep 2026 09:00:00 +0000</pubDate><description>On a federated network the first decision is not the app but the server holding the account. How to read a small service like a neighbourhood.</description></item>
<item><title>What community radio teaches a federated network</title><link>https://jabberpowered.org/history/community-radio-federation/</link><guid>https://jabberpowered.org/history/community-radio-federation/</guid><pubDate>Sat, 12 Sep 2026 09:00:00 +0000</pubDate><description>Low-power FM licences put a hundred-watt transmitter in local hands. The structure of that decision is older than federation and explains part of it.</description></item>
<item><title>Digital archaeology on a dead protocol</title><link>https://jabberpowered.org/history/digital-archaeology-protocols/</link><guid>https://jabberpowered.org/history/digital-archaeology-protocols/</guid><pubDate>Sat, 12 Sep 2026 09:00:00 +0000</pubDate><description>Deprecated XEPs, abandoned services and expired domains are a federated network's stratigraphy. Reading them takes a field archaeologist's patience.</description></item>
<item><title>Reading the RFCs the way a historian reads a speech</title><link>https://jabberpowered.org/history/reading-rfcs-like-historian/</link><guid>https://jabberpowered.org/history/reading-rfcs-like-historian/</guid><pubDate>Sat, 12 Sep 2026 09:00:00 +0000</pubDate><description>The RFCs are primary documents and most retellings are secondary. How a historian reads a primary text, and why it applies to a specification.</description></item>
<item><title>A server starts with a name: domain and DNS first</title><link>https://jabberpowered.org/servers/domain-and-dns-first/</link><guid>https://jabberpowered.org/servers/domain-and-dns-first/</guid><pubDate>Sat, 12 Sep 2026 09:00:00 +0000</pubDate><description>Before any XMPP software is installed, a federated node needs a registered domain, DNS records under the operator's control and a host that answers.</description></item>
<item><title>A server is a household: the weekly maintenance round</title><link>https://jabberpowered.org/servers/weekly-maintenance-round/</link><guid>https://jabberpowered.org/servers/weekly-maintenance-round/</guid><pubDate>Sat, 12 Sep 2026 09:00:00 +0000</pubDate><description>A small XMPP server fails by neglect more often than by attack: certificates expire, logs fill, updates wait. A fixed weekly round is the difference.</description></item>
<item><title>When two servers stop talking</title><link>https://jabberpowered.org/servers/when-two-servers-stop-talking/</link><guid>https://jabberpowered.org/servers/when-two-servers-stop-talking/</guid><pubDate>Sat, 12 Sep 2026 09:00:00 +0000</pubDate><description>Federation failures look identical from outside and have four causes underneath. A diagnostic order that reads the pipes before digging.</description></item>
<item><title>When a blocklist bans a name, not a behaviour</title><link>https://jabberpowered.org/standards/blocklists-name-not-behaviour/</link><guid>https://jabberpowered.org/standards/blocklists-name-not-behaviour/</guid><pubDate>Sat, 12 Sep 2026 09:00:00 +0000</pubDate><description>Operators block abusive domains and users block abusive contacts. Whether the block names a category or an act is the difference that matters.</description></item>
<item><title>Message, presence and IQ: the three stanzas</title><link>https://jabberpowered.org/protocol/message-presence-and-iq/</link><guid>https://jabberpowered.org/protocol/message-presence-and-iq/</guid><pubDate>Tue, 01 Sep 2026 09:00:00 +0000</pubDate><description>The three stanza types defined by RFC 6120 and what each one is actually for, with the attributes that decide where a stanza goes.</description></item>
<item><title>How a JID is built, and what breaks it</title><link>https://jabberpowered.org/protocol/how-a-jid-is-built/</link><guid>https://jabberpowered.org/protocol/how-a-jid-is-built/</guid><pubDate>Wed, 26 Aug 2026 09:00:00 +0000</pubDate><description>Localpart, domainpart and resourcepart: what RFC 7622 allows in each, why bare and full addresses behave differently, and where clients get it wrong.</description></item>
<item><title>Presence, rosters and the subscription dance</title><link>https://jabberpowered.org/protocol/presence-and-subscriptions/</link><guid>https://jabberpowered.org/protocol/presence-and-subscriptions/</guid><pubDate>Wed, 19 Aug 2026 09:00:00 +0000</pubDate><description>How a contact list is stored on the server, what the four subscription states mean, and the exact exchange that adds one person to another list.</description></item>
<item><title>From jabberd to the XMPP RFCs: a timeline</title><link>https://jabberpowered.org/history/from-jabberd-to-the-xmpp-rfcs/</link><guid>https://jabberpowered.org/history/from-jabberd-to-the-xmpp-rfcs/</guid><pubDate>Wed, 12 Aug 2026 09:00:00 +0000</pubDate><description>The dated steps between the 1999 announcement of Jabber and the 2004 publication of the first XMPP RFCs, as the XSF records them.</description></item>
<item><title>Who owns the name Jabber</title><link>https://jabberpowered.org/history/who-owns-the-name-jabber/</link><guid>https://jabberpowered.org/history/who-owns-the-name-jabber/</guid><pubDate>Wed, 05 Aug 2026 09:00:00 +0000</pubDate><description>Why the protocol is called XMPP and the community is still called Jabber: the trademark, the foundation that licensed it, and who holds it now.</description></item>
<item><title>ejabberd, Prosody, Openfire: how they differ</title><link>https://jabberpowered.org/servers/ejabberd-prosody-openfire/</link><guid>https://jabberpowered.org/servers/ejabberd-prosody-openfire/</guid><pubDate>Wed, 29 Jul 2026 09:00:00 +0000</pubDate><description>What separates the three servers people deploy, why no neutral body has measured it, and how to run the comparison yourself.</description></item>
<item><title>The DNS records a federated server needs</title><link>https://jabberpowered.org/servers/dns-records-a-federated-server-needs/</link><guid>https://jabberpowered.org/servers/dns-records-a-federated-server-needs/</guid><pubDate>Wed, 22 Jul 2026 09:00:00 +0000</pubDate><description>The SRV records XMPP uses for client and server connections, the fallback rules in RFC 6120, and the mistakes that quietly break federation.</description></item>
<item><title>Encryption on the wire: c2s, s2s and TLS</title><link>https://jabberpowered.org/servers/encryption-on-the-wire/</link><guid>https://jabberpowered.org/servers/encryption-on-the-wire/</guid><pubDate>Wed, 15 Jul 2026 09:00:00 +0000</pubDate><description>The two hops an XMPP message takes, what TLS protects on each, what dialback does and does not prove, and where transport encryption stops.</description></item>
<item><title>What to check before you install a client</title><link>https://jabberpowered.org/clients/what-to-check-before-you-install/</link><guid>https://jabberpowered.org/clients/what-to-check-before-you-install/</guid><pubDate>Wed, 08 Jul 2026 09:00:00 +0000</pubDate><description>The handful of extensions that decide whether an XMPP client feels modern: message archiving, carbons, http upload and encryption support.</description></item>
<item><title>Why mobile XMPP is harder than desktop</title><link>https://jabberpowered.org/clients/why-mobile-xmpp-is-harder/</link><guid>https://jabberpowered.org/clients/why-mobile-xmpp-is-harder/</guid><pubDate>Wed, 01 Jul 2026 09:00:00 +0000</pubDate><description>Long lived streams against aggressive power management: what stream management and push notifications solve, and what they cost.</description></item>
<item><title>How a XEP becomes a standard</title><link>https://jabberpowered.org/standards/how-a-xep-becomes-a-standard/</link><guid>https://jabberpowered.org/standards/how-a-xep-becomes-a-standard/</guid><pubDate>Wed, 24 Jun 2026 09:00:00 +0000</pubDate><description>The states an extension passes through at the XSF, who votes at each step, and how to read the status block at the top of any XEP.</description></item>
<item><title>MUC and MIX: two answers to group chat</title><link>https://jabberpowered.org/standards/muc-and-mix-group-chat/</link><guid>https://jabberpowered.org/standards/muc-and-mix-group-chat/</guid><pubDate>Wed, 17 Jun 2026 09:00:00 +0000</pubDate><description>Why XMPP has two group chat extensions, what each assumes about identity and membership, and what that means for a user with two devices.</description></item>
<item><title>OMEMO and end to end encryption</title><link>https://jabberpowered.org/standards/omemo-and-end-to-end-encryption/</link><guid>https://jabberpowered.org/standards/omemo-and-end-to-end-encryption/</guid><pubDate>Wed, 10 Jun 2026 09:00:00 +0000</pubDate><description>What OMEMO adds on top of transport encryption, how it handles several devices per account, and the parts of a conversation it does not hide.</description></item>
</channel></rss>