We've tried to take the approach that for everything you can use the REST-based JSON delivering API (https://github.com/buddycloud/buddycloud-http-api). The federation, domain discovery, message passing between domains, dial-back security etc are all handled at the XMPP layer and can essentially be a black box. Just know that your posts, media, whatever-you-want will get delivered when both domains are online and that servers will catch up on posts when one goes down.
To me this gives developers the best of both worlds - simple to develop web-app combined with solid, tested, it-just-works federation.
Everyone -- Google included -- got really caught up in the tech demo UI when what was really interesting was the stuff going on under the hood.
Wave was based on XMPP, designed to be federated, was designed to be able to handle arbitrary data types, was extensible via robots, had built-in privacy controls, etc.
If you sat down and tried to figure out all the things a distributed social network should do, Wave really had all the right building blocks in place. Instead Google marketed it as next-generation email and it flopped.
1) http://onesocialweb.org (Not sure about their future)
2) http://buddycloud.org (some of their contributors are HNers, but even though they're recipients of Google Summer of Code 2012, they are also quite modest).
These are the approaches that seem to be the most promising to me, even though their use of XMPP has been disparaged as non-developer unfriendly. I simply disagree, as a non-developer (though I am working to change that; I've got simple Django and Rails up and running on my LAN).
I believe the ideal hardware for such a project is:
~1.2GHz ARM CPU
-4GB RAM
-64GB SSD
-2x SataIII HDD (~6TB RAID)
-on a consumer ISP connection with 250GB soft cap