Chanty
Chanty's feed is an HR statistics content mill, not a product changelog
A side-by-side editorial comparison of diaspora and Stalwart — release velocity, themes, recent moves, and the top alternatives to consider.
The original federated social network now ships roughly once every two years.
diaspora* is a decentralised social network run as independent pods by volunteer administrators. Release cadence has collapsed to near-dormancy: 0.9.0.0 arrived in June 2024 after a two-year gap, and 0.9.1.0 followed in April 2026 — the release notes open with "it's been a while." What still ships reliably is security work, including a fixed SSRF vulnerability in the OpenID Connect implementation and, earlier, image-processing hardening adapted from Mastodon's fix.
Stalwart is chasing mail RFCs and its own storage layer at the same time
Stalwart ships roughly weekly, and the releases divide cleanly between standards implementation and correctness work. v0.16.18 turns toward resource control — bounds on decompressed inbound DMARC and TLS report size, a cap on RocksDB block-cache memory, column families tuned per access pattern, and a queue scheduler that stops rescanning from the earliest pending event. The preceding releases added IMAP UIDONLY, UIDBATCHES and MESSAGELIMIT, plus JMAP email push and VAPID.
diaspora* is a decentralised social network run as independent pods by volunteer administrators. Release cadence has collapsed to near-dormancy: 0.9.0.0 arrived in June 2024 after a two-year gap, and 0.9.1.0 followed in April 2026 — the release notes open with "it's been a while." What still ships reliably is security work, including a fixed SSRF vulnerability in the OpenID Connect implementation and, earlier, image-processing hardening adapted from Mastodon's fix.
The one real forward move in this window was 0.9.0.0, which opened a supported public API and switched configuration to TOML with notice that YAML support ends at 1.0. Everything since has been maintenance. The project's own framing — a minor version described as not too exciting, urging podmins to update because it is a security release — sets the expectation plainly: diaspora* is being kept safe to run rather than developed toward anything new.
A 1.0 release removing YAML configuration support is the stated next milestone, but with two years between the last two releases the timing is unpredictable. The more likely near-term event is another security-driven patch.
Stalwart ships roughly weekly, and the releases divide cleanly between standards implementation and correctness work. v0.16.18 turns toward resource control — bounds on decompressed inbound DMARC and TLS report size, a cap on RocksDB block-cache memory, column families tuned per access pattern, and a queue scheduler that stops rescanning from the earliest pending event. The preceding releases added IMAP UIDONLY, UIDBATCHES and MESSAGELIMIT, plus JMAP email push and VAPID.
Two threads run through every release. One is RFC coverage across IMAP, JMAP, CalDAV and WebDAV, implemented close to the specification including drafts. The other is a long tail of protocol-conformance fixes, many of them cases where JMAP and IMAP disagreed about the same state. The newest release adds a third: memory and scheduling limits, which is what a server codebase starts doing when deployments get large enough for defaults to hurt.
Expect continued RFC additions across the JMAP and IMAP surfaces, with more of the storage-tuning work that v0.16.18 started as RocksDB deployments scale.
Other Comms products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either diaspora or Stalwart.
Chanty's feed is an HR statistics content mill, not a product changelog
Proton Bridge spends its first release in ten weeks on crashes, memory bounds and dead code
Every manual control Mux ships now arrives with a Robots workflow that does it for you
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
mailcow's release notes are almost entirely upstream security currency.
Openfire keeps its XMPP server current without changing what it is.
See all diaspora alternatives → · See all Stalwart alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — self-hosted — within Comms. Stalwart is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Stalwart is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top diaspora alternatives in Comms are ranked by recent ship velocity. Browse the "diaspora alternatives" section above for the current picks, or visit /alternatives/diaspora for the full list with editorial commentary on each.
Top Stalwart alternatives in Comms are ranked by recent ship velocity. Browse the "Stalwart alternatives" section above for the current picks, or visit /alternatives/stalwart for the full list with editorial commentary on each.