diaspora*

Distributed social networking server.

Steady · 54
54/100
Steady

Maintained, but at a slower pace than the leaders in its category.

Maintenance 12/40
Releases 25/25
Community 17/20
Momentum 0/15

Commit activity more than 30% of tracked projects; popularity more than 83%. How this is calculated.

Commits, last 11 months

2025-12: 0 commits 2026-01: 0 commits 2026-02: 0 commits 2026-03: 0 commits 2026-04: 108 commits 2026-05: 8 commits 2026-06: 0 commits 2026-07: 3 commits 2026-08: 0 commits 2026-09: 0 commits 2026-10: 0 commits
2025-12 119 total 2026-10
Stars14k
Latest releasev0.10.1 · 18 Nov 2026
Repo updated18 Nov 2026
LicenceAGPL-3.0
Built withRuby

Is diaspora* actively maintained?

diaspora* logged 119 commits over the last 11 months, but none in the most recent quarter. Development has paused rather than stopped outright — worth watching before a production deployment.

The most recent tagged release, v0.10.1, shipped within the last month — a current, installable version exists today.

diaspora* ranks #22 of 40 in Communication - Social Networks and Forums, placing it mid-table for maintenance activity.

What diaspora* actually does

diaspora* is a distributed social networking server that allows you to self-host an independent node within a federated network. It handles user profiles, posts, and interactions across multiple autonomous servers rather than relying on a single centralised platform. The project is written in Ruby and licensed under the AGPL-3.0.

Best fit: It suits individuals or small communities wanting to run an independent social network without depending on commercial platforms. It is also relevant if you specifically prefer the Ruby ecosystem for your federated communication tools.

Worth knowing: Federated software often requires active moderation of incoming content from other nodes and can suffer from low user adoption compared to mainstream alternatives. The project maintains a steady development pace, but federated protocols can occasionally present network-wide synchronization challenges.

Deployment notes

As a Ruby application, it typically requires a dedicated application server such as Puma alongside a database like PostgreSQL and a reverse proxy for TLS termination. You will also need to configure persistent storage for user uploads and ensure background worker queues are running.


Alternatives to diaspora*

Projects in the same categories, ordered by health score.