Discussing Diaspora’s Future

Tuesday, 2012-January-03 at 05:55 6 comments

I have seen lots of discussion about the future of !Diaspora lately. Here is my first attempt to really weigh in. We need to distinguish between several things that are all called Diaspora. First of all, there is Diaspora the project (DProj), the Diaspora core development team (DCore), Diaspora the corporation (DStar), and DStar’s Diaspora pod, JoinDiaspora.com (JD). There are also several independently-operated pods, such as Diasp.org (DiaspO) and Diasp.eu (DiaspE).

First of all, DProj, can really benefit from more contributors. Sadly, I cannot help. I messed around with Ruby for a while, realized that its soup of special characters with special meanings was not going to ever match my brain (like Perl, which has the same problem), and put it down quickly.

DProj is almost synonymous with DCore and DStar, as is usual in a cathedral-type of project. However, DStar is also distracted with the financial and administrative burden of operating JD. This, I think, is the chief problem that Diaspora (overall) faces. Even with a cathedral model, they could be very successful. But they’ll have to be very careful.

DStar must, absolutely must start to create a business model. They need to wake up and realize that centralizing around JD, a site that charges its users nothing and accepts no advertising, is suicidal. Likewise, owners of other Diaspora pods, including both DiaspO and DiaspE, should be thinking about their own business models.

Once you realize that hosting a zero-price site for yourself and a few friends and family is considerably different from hosting a zero-price site for tens or even hundreds of thousands of people you do not know, you will realize that all large Diaspora pods will need some kind of business model. Hosting costs money. Bandwidth costs money. Having someone to administer the site, to respond to issues and outages all day, every day costs money. By refusing to face this issue up front, JD may have seriously damaged the future of both DStar and DProj.

Diaspora, particularly the JD pod, has attracted a large number of people who cannot contribute code, cannot or will not contribute funds, and will not tolerate advertising on the site. Unless the JD pod finds a billionaire sponsor or forces the freeloaders to leave or change, that pod will continue to be a severe drain upon DStar, and to consume resources that DProj and DCore need.

I understand the founders wanted Diaspora to be more of a non-profit foundation, and I understand this. Putting DProj development in a NPO would be the best way to go, but pod-hosting (JD) is killing the project.

People are complaining about the instability of the JD pod, which seems to be down several times each day. As a user of that pod, but a non-participant in DProj itself, my estimation is that the influx of JD users is straining the already-tight finances and server administration resources of DStar.

What should be done about all of this? I am glad you asked.

Number one, DStar must put DProj into a non-profit organization funded primarily by DStar. That will free DProj to seek grants and sponsors. DCore needs to open up DProj a little, so that people who can grok Ruby are more willing to contribute code.

Number two, DStar must emphasize federation. People need to be encouraged to start new pods and to choose to join other pods instead of JD. In fact, I would encourage DProj and DCore to get in touch with the people trying to patch XMPP into the Diaspora codebase. Get in touch with Friendica’s Mike. Get in touch with the StatusNet, OStatus, and RStatus people. Work to make it possible for Diaspora pods to interfederate with OStatus-using federations, such as StatusNet and RStatus; make it possible to interfederate with Friendica using its Zot protocol; and to interfederate with XMPP-using federated social networks, such as Jappix. Many have argued that Diaspora lost its chance to ever become popular. I do not believe that displacing one or more of the big commercial socnets is or ever was on DStar’s agenda, but to the degree that Diaspora or any other federated socnet succeeds in attracting active and sustainable communities, they all benefit, and all the more if they can interfederate. Diaspora, the Zot-using networks (currently just Friendica), the OStatus-using networks (including Identica and other StatusNet instances, and RStatus, at least), and the XMPP-using networks together can form a network with no vulnerable central hub, no corporation or organization in control, and no way for patent and copyright trolls to buy government-sponsored tollbooths.

Number three, JD absolutely needs to immediately post a privacy policy, even if it is a work in progress. Privacy and users controlling their own data is part of Diaspora’s “USP” (unique selling point), as your introductory college marketing class will tell you about. Without a privacy policy and TOS (terms of service) policy on JD, many who would otherwise be willing to help out are avoiding not just JD, but all Diaspora pods.

Number four, DStar must take action to place JD on a sound financial footing. I see two ways to do this: (1) advertising, and (2) subscriptions. Most likely, both will be needed.

Analytics: Nearly every site uses some sort of analytics, if only to help with allocation of server resources and deploying anti-spam and anti-cracking defenses. I imagine that some idea of what features are used and in which sequence they get used is going to strongly influence which features get the most developer attention, also. JD should implement a solution like Piwik, until effective analytics can be integrated into the Diaspora software as a plugin. Without analytics, JD will have no way to know how to adjust the appearance and operation site to enable it to become profitable.

Advertising: Although Google’s adsense is said to be the more profitable ad network, there is absolutely no way that JD can use it. JD is going to have to build its own ad network (using OpenX or a similar application) or contract another ad network to service the site. However this is done, ads shown on JD need to respect its users’ privacy and the integrity of the Diaspora experience. This means no expanders, none of those popups when you roll over text, no “please view this ad while the page loads”, and positively no “you were discussing cats so we’ll show an ad for XYZ cat food”.

Subscriptions: Subscriptions are an excellent way to pay for some of the costs of operation. Subscription-only would chase away those who cannot afford it, or those who object to paid-only sites. Subscriptions as a “see fewer ads, subscribe” would be the best option.

I would like to encourage DStar to get in touch with Automattic, which is thriving with a similar business and funding model to the one which the various Diaspora entities will need to adopt in order to keep themselves going.

Number five, the various entities mentioned above that are individually and collectively known as ‘Diaspora’ need to be transparent. We know that the developers need to eat, drink, commute, sleep, and do all the other things that any other human needs to do. We know that DStar and any other legal entities need to have a space they operate out of. We know that operating high-traffic servers is expensive. We also know that no one involved in Diaspora is getting rich or trying to put something over on us.

So I would hope that DStar and all other legal entities, along with JD and other major pods, will make it a point to be transparent about what their needs are and what resources are available. Perhaps in doing so, people like me, who really want to see them succeed in producing a viable alternative to centralized networks, will find ways to help them do so.

Please be aware that this is not meant in any way to trash-talk anyone involved in Diaspora. It is meant to spur others to think about the financial needs of developing code full-time and of running large, resource-intensive pods, and to persuade them to be supportive of the people behind Diaspora as JD and other large pods move to find the revenues they need to continue operating.


Entry filed under: Federated Social Networks, Open Source. Tags: , , , , , .

Thinking About Independence Day 2011 in review


  • 1. Jim Morgan  |  Tuesday, 2012-January-03 at 18:54

    Reblogged this on Musings from the Manhut and commented:
    My friend lnxwalt shares his thoughts about the free/open social blogging platform Diaspora.

  • 2. Patrick Niedzielski  |  Wednesday, 2012-January-04 at 01:53

    A calm and well-thought out summation of the problems facing Diaspora, both as a project and corporation.

    An additional point that I’ve noticed is that the community of current Diaspora users, those vocal at the very least, have attempted to create a bazaar-style movement outside the core team of Diaspora. This seemed to grow up around the now slow diaspora-grassroots mailing list under Yosem Companys, with the intent of spreading interest in Diaspora. This is in sharp contrast to the core project, which is a cathedral-style project, as you mentioned. Diaspora as a project will need to reconcile the differences between these two models in some way, even if it is just increased connection between the two or specific delegation of goals to each, if it is to strengthen its current situation.

  • 3. lnxwalt  |  Wednesday, 2012-January-04 at 02:10

    Jim, Patrick, thank you for your comments. I hope we can all work together to bring respect for privacy and control of one’s own data into the mainstream thought process.

  • 4. Terry Hancock  |  Thursday, 2012-February-23 at 19:13

    Although it may seem to fly in the face of the main features of Diaspora, I think it will be necessary to implement some “local pod” features — i.e. aspects of a local pod which can be customized, and an ability to localize conversations or other features to the local pod.

    I think this will be important because it creates an incentive to run your own pod instead of just using an existing one.

    Without such an incentive, it seems to me that the Diaspora universe will be constantly trying to implode onto a few (or even just one) pod, eliminating the principle advantage of decentralization.

  • 5. Ryan Brockey  |  Friday, 2012-February-24 at 05:22

    This is a terrific post. Great summary of the issues facing the Diaspora endeavor. And I really appreciate your extensive suggestions of how to address those issues.

    Particularly, I agree that tools for user-pods need to be made a priority. I would already have a pod of my own up and going if it was made straight-forward enough.

    Your suggestion about interfederation is quite astute. Those other open social networks are not really competitors, and they should be allies. One of the primary tenets of Diaspora is to move away from the walled-garden social networks that exist today. That requires interfederation. And it cannot be just expected that others will adopt Diaspora’s federation protocol. They need to actively connect to others. I was very encouraged by the ability to post to tumblr, Facebook, and Twitter. We need more of that, and the connections need to be deeper.

    Great post. I’m sharing this.

  • 6. flohack  |  Monday, 2012-May-21 at 08:49

    I fully agree to this post. What concerns myself here is that the developers chose to implement a sound, bright and very promising idea with tools which are not widely used: Ruby and mongodb. While I have experience different SQL flavors and different programming languages, both of these tools distract me to even theoretically contribute to this project.
    It was not even possible to install the showcase pod according the instructions into Ubuntu, yet to link with other pods etc.
    So, For me the bottom line ist: Diaspora is proof-of-concept that an open-source public social network can be made, but to get world-wide attention it would need to support “ordinary developers” better, and not just be the playground of the “nerd developers”.
    Do they use git?

    regards Florian

RSS Slingshot

  • An error has occurred; the feed is probably down. Try again later.

RSS Unknown Feed

  • An error has occurred; the feed is probably down. Try again later.

RSS Unknown Feed

  • An error has occurred; the feed is probably down. Try again later.

RSS Owner Managed Business

  • An error has occurred; the feed is probably down. Try again later.


Recent Posts

Blog Stats

  • 598,850 hits

Top Clicks

  • None


%d bloggers like this: