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,

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 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 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?