Live data from Hacker News

ShowHN: buddycloud, a distributed social network

news.ycombinator.com

1–10 of 41 posts

ShowHN: buddycloud, a distributed social network

#1
Today we’re releasing a dev-preview of buddycloud and would love your feedback.

buddycloud is an extensible open source distributed social network. A user’s identity looks like user@domain.com and users share content in "channels".

We started buddycloud because of the growing “closed-ness” of existing social networks. For example Twitter’s increasing API contortions about what one can and can’t do with their API or which quadrant one is supposed to operate in. We also think it’s important to build services against a known protocol that works against any buddycloud instance on any domain (not paid-for APIs). Naturally this called for a completely decentralised design built on open standards like Atom, Activitystrea.ms and XMPP.

Each buddycloud-enabled domain runs a suite of servers. Each buddycloud server uses DNS to find, connect, and sync content in realtime with other buddycloud servers. This content can be any kind of structured data or large files.

Today we are releasing open source implementations of the following buddycloud servers: the buddycloud-channel server (shares your channel / your activity stream with trusted followers), a media server (shares anything from a small avatar to a multi-TB file), a push-server (email and mobile updates), and a taste engine (“channels you might like”). Some of the team are working on more servers that will let you suck content in and out of existing social networks.

Our reference implementations are written in Java and node and use Postgres for storing data. The web-client is built on backbone.js. There’s also a console client written in Python.

Next tasks: client speedup using IndexedDB. Following permissions, Android, iOS and Firefox OS clients and release buddycloud.js.

We really hope that some of this could be useful for your project: - https://github.com/buddycloud - wiki https://buddycloud.org - demo instance at https://demo.buddycloud.org - channel https://demo.buddycloud.org/team@topics.buddycloud.org

Re: ShowHN: buddycloud, a distributed social network

#5

Simon ( https://demo.buddycloud.org/simon@buddycloud.org ) from the buddycloud team here. Happy to answer any questions about the bc architecture or our approach.

Obvious question maybe but how does BuddyCloud compare to (and perhaps integrate with) Diaspora?

Re: ShowHN: buddycloud, a distributed social network

#7
post #5

Simon ( https://demo.buddycloud.org/simon@buddycloud.org ) from the buddycloud team here. Happy to answer any questions about the bc architecture or our approach.

Obvious question maybe but how does BuddyCloud compare to (and perhaps integrate with) Diaspora?

I remember another effort in distributed social networking, from some months ago. Forgot the name though.

Re: ShowHN: buddycloud, a distributed social network

#8
post #6

Yet another thing nobody will use, but I guess at least it's a nice learning experience for the devs. Good luck!

"Yet another thing nobody will use" said a active member of the incredibly popular centos remix, stella.

When asked about whats next for stella, nux was heavily focused on just getting his first dollar in revenue.

translation: Do not be a dick about other peoples stuff, especially when you have built things yourself which are less than noteworthy.

* http://li.nux.ro/stella/

Re: ShowHN: buddycloud, a distributed social network

#9
post #5

Simon ( https://demo.buddycloud.org/simon@buddycloud.org ) from the buddycloud team here. Happy to answer any questions about the bc architecture or our approach.

Obvious question maybe but how does BuddyCloud compare to (and perhaps integrate with) Diaspora?

There's two three things that count when building a distributed social network: easy to use client APIs, Server APIs (how do servers find and connect, catch up, etc) and a reference implementation.

I'm not sure that Diaspora has a defined server-to-server API or a client API (can someone more aware of their progress comment). On buddycloud Each domain runs an HTTP API server (https://buddycloud.org/wiki/Buddycloud_HTTP_API) that clients can connect to on their home domain (eg if you are james@giantpeach.com, you connect to something like http-api.giantpeach.com). And servers use XMPP to exchange between one another.

Then there is Tentd. I like what they are doing. I think their approach is that every user is a server (your id is http://me.domain.com). I'm not quit sure how they federate or resync messages when nodes go down. Can anyone comment on how they federate?

Post reply on HN