4 ms·
So if this is, as some comments are suggesting, an indication that Diaspora is essentially dead… what can we learn from it? What did they do right, what did the
by egypturnash 14y ago
So if this is, as some comments are suggesting, an indication that Diaspora is essentially dead… what can we learn from it? What did they do right, what did they do wrong? Is "distributed social networks" a fundamentally flawed idea, or was their implementation flawed?
I mean, they certainly did something right, given that G+ swiped liberally from Diaspora's design.
(What would a distributed social network that was dead easy to host look like? Imagine something like Diaspora that lives on your phone instead of on a server, for instance. Right now D* is a giant pile of Ruby, which means that interested amateurs are pretty much not gonna be able to play with it.)
- joe_the_user 14y agoWhat I'd take as lessons: 1) It's better to start with a protocol and build an application than just launch into application building. 2) Privacy is wrong motivation for wanting to replace Facebook. A distributed social networking application is certainly possible (one might argue the web itself an example). A secure, distributed sharing scheme makes a social networking app exponentially harder to develop (Project Xanadu tried to create a secure "transclosure" scheme. They had a ten year head-start on the web and still failed. Distributed, revocable sharing is essentially a pathological problem).
- shmerl 14y agoNo, privacy is really required for something that aims to compete with Facebook, simply because Facebook can't compete on privacy.
- 001sky 14y agoAssuming this is true, how much is control rights vs need for de-novo architechture?
- shmerl 14y agoI'm not sure if I understood the question, but if you mean how user control is related to the decentralized structure, then the answer is in the question. Decentralization essentially prevents one entity from being in control, and in edge case control is given to a user who runs a personal pod for single Diaspora account.
- 001sky 14y agoAbout the notion that the data needs to be locally stored/controlled/at the edge. What about the idea of encryption and/or persistence management? (user control) Does this provide more flexibility on Architecture. Edited: for clarity.
- shmerl 14y agoI think encryption is good to have and D* devs had it in some further plans. But it's probably not the first priority, until federation protocol is rock solid.
- motters 14y agoThe things they did wrong were: - During the initial 6-12 months after the Kickstarter there was little or no communication about what they were doing. Blog posts were very scarce. If you want to maintain interest in a project it's a good idea to have some level of communications. - They made initial software choices which meant that the initial release wouldn't run on the target platform (ARM based servers) - Once Diaspora got going it wasn't easy to find pods other than joindiaspora - The Diaspora team were unresponsive to patch submissions and this meant that features which users wanted didn't get implemented. - There were issues with the protocol being undocumented
- jeremyjh 14y ago>The Diaspora team were unresponsive to patch submissions and this meant that features which users wanted didn't get implemented. So you've read pistos blog. Have you look at the contributions though? https://github.com/diaspora/diaspora/graphs/contributors https://github.com/diaspora/diaspora/graphs/contributors No open source project accepts every pull request, but Diaspora has accepted quite a lot.
- deleted 14y ago[deleted]
- joe_the_user 14y agoYes, Ruby is a "good" language but how many people are able to host ruby projects? Ruby is a quick application to develop with and they needed to develop quickly. Usually, there are hundreds of particular aspects of a software production process that an outsider could question but just usually the tradeoffs can't be as easily made calculated from the outside as one would think. I think the OP's idea of completely distributed servers might be as good any IF these weren't website servers but information caches akin to Freenet nodes. Freenet at least does work on some level. http://en.wikipedia.org/wiki/Freenet http://en.wikipedia.org/wiki/Freenet
- chimeracoder 14y agoI think most of the lessons are non-technical, which makes them all the more valuable. 1. Diaspora had all the characteristics of vaporware for the longest time - I remember they were #1 in a HuffPo 'Top Ten Alternatives to Facebook' lineup in May 2010[1]. 2. The source code released that fall seemed to fail Spolsky's second rule of being able to build in a single step, because I remember checking out the repo and then realizing that I'd need to dedicate more than ten minutes to figuring everything out, making a mental note to do that at some point,a and promptly forgetting about it entirely. 3. The officially-hosted version was a victim of poor timing - the first time I saw it was last summer (2011). Aside from the fact that this was more than a year after I had already seen it in a mainstream news source, this was immediately after the release of Google+ and at the height of the 'nymwars'. By that point, Google+ had already gained its reputation as a massive, overhyped soon-to-be-likely-failure[2]. Diaspora's UI was nearly identical to Google+, so it seemed less like an alternative to Facebook and more of an open-source alternative of an alternative to Facebook. I don't think the technical spec of Diaspora as a product is broken at the core (though that doesn't mean that something like what you envision couldn't also be valuable as well). I do think that the end goal is worthwhile, and let's be clear: this does not kill Diaspora - it has every chance to be as much alive as Netscape is, just in a different form (ie, Mozilla/Firefox). That's the beauty of open-source projects, particularly community-driven ones. [1] The lineup is of course indicative of nothing other than the fact that Diaspora was already hyped-up enough to be included in such a lineup! [2] Whether or not you agree with that conclusion now, it was certainly a popular sentiment at the time.
- joe_the_user 14y agoIt seems like you're flagging the results of bad development. The question we need to ask ourselves is, what leads these to unfortunate results. The decision to use two-stage build process might not be bad when a project is in that kind of shape. What leads a project to get into that kind of shape? Well, that is the question. At the same time, I remember the first code-release of diaspora was before G+, it just wasn't usable code. Any project that takes a long time to create is going to have "timing problems". If Diaspora had smoothly working code right now, timing probably wouldn't be an issue.
- fusiongyro 14y agoI was very jazzed about it, but didn't donate, back when it was being kickstarted. Whether or not they were intending to, the publicity quickly took on a flavor of "these wunderkinds are going to save us from FB!" I couldn't say whether that was intentional or not, but the day they first released their code to the public, I read through some of it and was singularly unimpressed, and basically gave up on the project because it looked like their first Rails app, and seemed very insecure. I don't know how many developers lost confidence in them that day, but I certainly did. The punk rock ethic is great for getting things done, but some things are big projects and need to be undertaken with a degree of care and commitment, and those kinds of projects are not conducive environments for all-cylinders-firing wunderkinds. I think a takeaway better model is: produce a beta or a demo that you bring to Kickstarter and ask for double or quadruple the money you think you'll need (because you will). Either make the code open-source last after it's fully developed, or make sure the code you bring to the demo is secure and unembarrassing. Even though I disagree with the idea, I think Light Table is hitting most of the notes Diaspora missed: Chris showed up with a compelling demo, raised way more money than a kid would deem necessary (and then more still with YC) and at least originally was going to make the code available last. He also updates frequently and people are using the software today, which never really seemed to happen with Diaspora.
- charlieok 14y agoOf course it isn't a fundamentally flawed idea. At least, from a technical perspective. Email is a distributed social network. It just doesn't define very many types of actions or objects. You can create "messages" and then you can "send" them. The user sees the guts of the message -- the "from", "to", "subject" and "body" portions, mainly. As far as I know, nobody has extended the standard email formats and protocols to support new message types that have caught on lately. Actions like "Post photo", "Tag photo", "Take a special action defined by this third party which should be displayed like so when rendered in a 'feed'". This seems like mostly a matter of agreeing on some new types of messages and some suggested ways of handling and displaying them. I'm not saying this has to be built on top of existing email protocols -- it's really just independent sites exchanging messages of some sort. But email is a good working example to point at today. The hard part is getting adoption, and getting different implementations to interoperate. Once you dive into this, you find a huge soup of different projects working on different pieces of the puzzle. Some of these projects have a future, others do not. It's going to take some time for this to shake out, and for the developers to resolve issues with bringing this stuff together. A lot of this work has been going on without a lot of fanfare. See for example http://indiewebcamp.com/ http://indiewebcamp.com/ or http://www.internetidentityworkshop.com/ http://www.internetidentityworkshop.com/ Naturally, it couldn't hurt to bring a lot more help into these efforts.
- charlieok 14y agoI should add that the trickiest bits aren't the apps that could "run on top of" a distributed social network like photo tagging or games. It's setting up the social graph those apps use. How do you add a friend? How do you accept or reject a friend request? What sort of authentication and other security features should everyone understand and support? There are proposals for solving these issues but getting it a) secure and b) widely agreed upon and supported would be a Good Thing.
- joe_the_user 14y agoActually, there were some fundamentally flaws in the particular version of a distributed social network that diaspora started with. They imagined a network of web servers that would each host a piece of diaspora and that each of these would provide secure sharing. That system pretty much requires trusting all the server-providers because the decryption happens on the servers.
- stonefroot 14y agoWhy would it mean the project is "dead"? Do you mean that community projects are by nature "dead" projects? What does "dead" mean, exactly? My OS is a community project. OSX/iOS are built from community projects. Lots of scripting languages are community projects. Mozilla is a community project. Wikipedia is a community projects. I could go on. I realise I may think a bit differently than many programmers, but I care less about how much a particular chunk of code is actively changing than whether it works really well over the long term (simple, stable, reliable, secure). I like "timeless" software than quietly continues to work for many years, remaining relatively unchanged. In my experience, well-engineered software like that is often immune from so-called "bit rot". Because it was designed correctly, with minimised complexity and maximised portability as a top priorities, from the beginning. From a design and implementation perspective, there are no real impediments to a decentralised social network that cannot be overcome. However first you have to decide what you mean by "social network"? Does it have to be a clone of FB or G+, save for the centralisation element? Or does your definition allow some changes to their approach? For example, what if the network was private? What if there were no ads? What if it was comprised of lots of smaller networks of maybe 100-200 people (like your "friends" on FB) instead of being one massive, public image gallery/chatbox? What if it didn't require the web, as FB does? What if it was application-agnostic? What do you demand from a "social network"? Does it have to be a FB/G+ clone? Anything is possible, so to speak. But not everything is necessarily ready to be received based solely on technical merit. How much marketing and PR is needed?
- smacktoward 14y agoDo you mean that community projects are by nature "dead" projects? No, but they're not necessarily live projects, either. The key question is how much commit activity is coming from the people who are walking away from the project. If they were doing all the committing, and they're leaving, it's dead. If on the other hand there's an active community of committers outside the original developers, it's alive.
- stonefroot 14y agoSo there is an assumption that number of commits means something? I'm just not quite sure what that something is. What if the software as released is "rock solid"? That is, it's so simple, effective and reliable that it doesn't need to be changed, except for bug fixes? What if the software is merely a "platform"? (And not only in the marketing sense of that word.) That is, the platform only "does one thing and does it well", and does not generally need to be "actively" developed (no commits except bug fixes), but... of course people can easily build things on top of it. For example, Ruby or Python programmers can do whatever they want. Total freedom. We give them the ability to create a connection to a social network they choose and they can send/receive over it to/from other members as they wish. We do not impose rules on that or try to manage it in anyway. We only provide the platform. The platform is application-agnostic. The "platform" basically stays the same. It does what it's supposed to do, create networks, and that's all. If we measure by number of commits, one could say the development of the "platform" is "dead". tl;dr what if someone releases a _platform_ that developers can build on, but number of commits to the _platform_ remains near zero? Because (apart from any bugs found) "it just works." To my knowledge, Diaspora is closely intertwined with Ruby and web development. This makes it difficult to separate the "platform" from lots and lots of Ruby or other scripting language programming, mainly aimed at webpages, and people changing UI stuff to their liking. And personal preferences can vary greatly. (And there's more to the internet than just webpages. FB has to be webpages because it relies on the web, specifically one person's website: Zuckerberg. Another social network (or newtork of networks) might not be so limited.) Does the dynamic, highly personalised aspect of viewing webpages have to be part of the _platform_? Can we separate the personalisation from the basic functional element of the platform? (spawning decentralised networks)