Diaspora is a free, open-source social network made of independently run servers called pods that interoperate, so no single company controls it. Four New York University students launched it in 2010 as a privacy-minded alternative to Facebook.
It is one of the earliest projects in the wider field of the open source social network, and it shaped many ideas that later federated platforms adopted.
How Diaspora works
The network is a group of independently owned nodes, called pods, that interoperate to form one network. According to the Wikipedia article on the project, “Each pod (node), however, is owned and operated by a different provider.” A person signs up on any pod, and posts reach friends on other pods through federation.
That design has practical consequences. Your account lives on a server you choose, which can be run by a volunteer, a club or an individual. If one pod goes offline, the rest of the network keeps running. Users can also move to a different pod or, in principle, host their own.
The project’s stated aim was blunt. Its developers said that “our distributed design means no big corporation will ever control Diaspora.”
Aspects and sharing control
Diaspora’s best-known feature is the aspect: a user-defined group of contacts that decides who sees a given post. Instead of one undifferentiated friends list, a person can keep family, colleagues and hobby contacts in separate aspects and choose the audience per post. The idea proved influential. In a September 2011 message, the developers noted similarities such as Google+’s “circles”, a version of Diaspora’s aspects.
Origins and the Kickstarter campaign
The project was founded by Dan Grippi, Maxwell Salzberg, Raphael Sofaer and Ilya Zhitomirskiy, students at New York University’s Courant Institute of Mathematical Sciences. Their pitch arrived when concern about the privacy practices of large social platforms was high, and it drew wide attention.
The group received crowdfunding in excess of $200,000 via Kickstarter. Among the donors was Facebook CEO Mark Zuckerberg, who contributed an undisclosed amount. A consumer alpha version was released on 23 November 2010.
The campaign also hit an unusual obstacle. Within days of commencing the campaign over US$45,000 had been raised when PayPal froze Diaspora’s account without explanation. After a large number of complaints from users and the threat of legal action, the account was unfrozen with an apology from a PayPal executive, but still without explanation. The episode became a small parable of the project’s argument: when one company sits in the middle of a service, that company can interrupt it.
The funding came with high expectations. Many observers expected a polished Facebook rival within months, yet the first releases were rough, as is common for an alpha built by a small student team. The gap between the hype and the early software shaped how the project was judged for years, even as the code steadily matured under volunteer care.
From startup to community project
The early team did not stay together as a company. In June 2012 the development team was scheduled to move to Mountain View, California, as part of work with the startup accelerator Y Combinator, and the founders’ attention then turned to other products. In August 2012 the developers’ focus changed to working on makr.io, as part of their Y Combinator class. Development passed to volunteers.
That handover is the central fact of Diaspora’s later history. The project stopped being a startup and became a community-maintained piece of infrastructure, with no venture backing to protect and no growth targets to hit. The trade-off is slower, more cautious development: releases focus on stability, security fixes and compatibility rather than a constant stream of new features.
For a self-hosted network, that conservatism has benefits. Pod administrators need upgrades that do not break federation with other pods, and a predictable versioning scheme makes it easier to plan maintenance. It also means the software is unlikely to be abruptly shut down or sold, since no company owns it.
The community team’s focus has been on stable releases as a basis for further development. That included adopting a semantic versioning system, improving the performance of data federation between pods, and enabling as many volunteers as possible to write code for the project.
Today the software is licensed under GNU-AGPL-3.0, and its development is managed by the Diaspora Foundation, which is part of the Free Software Support Network (FSSN). The AGPL license matters for a network service: anyone who runs a modified version for others must also share the changes. The code is written in Ruby on Rails. Wikipedia’s infobox lists a stable release of 0.9.1.0 dated 7 April 2026 and a user count of more than 859,000, a figure that counts registered accounts rather than active people.
Diaspora in the wider fediverse
Diaspora was built around its own federation protocol, which is not the same as the ActivityPub standard that Mastodon and many newer services use. The practical result is that it forms its own cluster. Some projects bridge the gap: Wikipedia’s navigation box groups Diaspora with Friendica and plugins for WordPress and Drupal under a Diaspora network heading, which shows that a few other tools can talk to its pods.
Readers comparing options can look at friendica, which takes a related multi-protocol approach, or at a broader survey of social network alternatives to see how Diaspora’s design compares with microblogging and group-focused platforms.
Strengths and limits
- Ownership and privacy: data lives on pods rather than in one corporate database, and aspects give fine-grained audience control.
- AGPL source available: the code can be audited, forked and self-hosted.
- Moderation varies: each pod sets its own rules, so experience differs between servers. In August 2014 the Diaspora Foundation stated that “all of the larger pods have removed the [ISIS]-related accounts and posts.”
- Smaller network effect: fewer people and less development momentum than the largest platforms, which can make finding friends harder.
These trade-offs are typical of federated software. Users gain independence and lose the convenience of a single, uniform service. A person who values control over their data and is comfortable choosing a server will find much to like, while someone who mainly wants the largest possible audience may prefer to keep a presence on a mainstream platform too and treat Diaspora as a private, quieter space.
For newcomers, the sensible approach is to pick an established pod, read its rules, and start with a few aspects rather than importing a whole social circle at once.
Frequently asked questions
Who created Diaspora?
A team of four New York University students created it. Grippi, Salzberg, Sofaer and Zhitomirskiy are the names credited.
What is a pod?
A pod is an independently owned and operated server running the Diaspora software. Pods interoperate to form the network, and each one is run by a different provider.
Is Diaspora free and open source?
Yes. The software is licensed under GNU-AGPL-3.0, according to Wikipedia’s 2026 snapshot of the project page, and the Diaspora Foundation manages development.
How was Diaspora funded at the start?
The group received crowdfunding in excess of $200,000 via Kickstarter, with a consumer alpha released on 23 November 2010.
