Diaspora* Announces It Is Now a "Community Project" 124
History's Coming To writes "Decentralised social network startup Diaspora* announced on their blog today that they will become a 'community project' with the intention of making it an entirely community-driven, community-run project.
Whether this is a sign of the project losing impetus, or whether this will provide the push needed to challenge commercially run social networks, remains to be seen."
* If you're looking for the footnote there isn't one**, the asterisk is part of the name. Sorry, it's been a point of annoyance on /. before.** There are two of them, nested.
Presentation (Score:4, Insightful)
The diasporaproject page needs some sort of overview of the architecture - on a simple level, how does it work technically?
Yet from the joindiaspora website it seems to be too technical - to attract new users we need a page which shows the social aspect of what is possible - most social network users don't care whether they own their data or not - just whether they can waste their time on a page looking at what their friends are doing, and sharing their own lives.
I would love to see this type of open system being taken up as a replacement for something like email - but for me it needs to be very simple in the first instance - just like email
Re:This could *help* fix diaspora but... (Score:5, Insightful)
Untill you bashed Ruby I actually followed what you were saying.
Someone who blames the tools, is a worthless worker, so, sorry, can't take anything you say serious.
XHTML + CSS (Score:4, Insightful)
Will this mean that they will soon also migrate over to XHTML and CSS so that their site will work in more than one or two browsers? I give Diaspora a try every now and again but in most of the browsers I use daily, it flat out refuses to render. Seriously at this late day and age there is no excuse not to be using a foundation of valid, well-formed XHTML. Fancy AJAX bells and whistles can be added on top of that layer, but it should first work across browsers and across platforms to reach the largest possible audience.
Anything short of that is alienating potential users and making the technology look bad. If they are missing such a simple check box, what other problems are they neglecting? I want it to succeed but it will continue to not get anywhere until it can render in regular browsers.
Like my dog (Score:5, Insightful)
I am sure he is still there, writes GNU Hurd device drivers all day and waits for the time when he'll come back to me on his flying car.
Bored.. (Score:5, Insightful)
"Community Project" = developers are now bored and want to move on to new things. It's been what, two or three years since Diaspora started and it hasn't exactly exploded on to the social networking scene and stolen Facebook's crown.
The developers are now working on some lame picture mashup thing called Makr.io, probably hoping Facebook will buy it so they can retire.
Posting anon as I am moderating.
Re:Bored.. (Score:4, Insightful)
Here's the joke about makr.io -- it looks and functions identically to canv.as (which is moot from 4chan's startup). The difference is that makr.io has slightly more hipster-ish imagees and is aiming to be a Facebook app. I wonder if Diaspora users' donations were used to fund the development of makr.io. D:
Re:This could *help* fix diaspora but... (Score:5, Insightful)
Bearing in mind the sites that use Ruby [setfiremedia.com] I don't think so.
Since Twitter is the Ruby poster-child, how about Once Again, Twitter Drops Ruby for Java [readwriteweb.com]:
"Twitter has now moved its entire search stack from Ruby-on-Rails to Java.
That's a big shift. Twitter moved its back end message queue from Ruby to Scala, a Java platform in the 2008-2009 time frame. The move was attributed to issues with reliability on the back-end.
This latest move makes the shift pretty much complete. At Twitter, Ruby is out of the picture."
Hey if they can make the world's largest social network [facebook.com] out of PHP, spit and bailing wire, I don't think technology matters as much as we wish it did. A frighteningly large percentage of business logic still runs on Visual BASIC and Cobol.
I think it is more the lack of skills and that you will probably need some time with your nose in a manual to set up the rails environment to run a node.
Ah yes, just throw more nodes at your unreliable and resource-hungry server code.
Careful, I think there are several patents on that.
Re:This could *help* fix diaspora but... (Score:5, Insightful)
2. The security problems were developer problems, not problems fundamental to Ruby. Early releases of Diaspora had SQL Injection vulnerabilities and Cross-Site-Scripting vulnerabilities, and a poor developer can create those in any language.
3. The reason they picked Ruby on Rails is that four kids were trying to create a distributed social network in less than a year. In order to have a prayer of pulling that off, you need a damn fast rate of development. If they had built the thing in Java using Spring and JSF, at this point they would be almost finished their "Hello World" implementation.
Re:XHTML + CSS (Score:4, Insightful)
XHTML is pretty much dead, and has been for years.
Re:This could *help* fix diaspora but... (Score:4, Insightful)
Hey if they can make the world's largest social network [facebook.com] out of PHP, spit and bailing wire, I don't think technology matters as much as we wish it did. A frighteningly large percentage of business logic still runs on Visual BASIC and Cobol.
And rightly so. The fact is that scalability is just not that important for a startup. Most likely the startup will fail with few customers at all. If they do have customers chances are they won't be on the scale of today's Facebook. If they do have a huge mass of customers and run into scaling issues, then they'll also have gobs of money coming at them from all direction with which they can solve those problems.
The alternative is to burn through all your capital making a really nice infrastructure that could be used to run Facebook, but which nobody will ever use anyway.
In business procrastination often pays off. It is hard to anticipate what your needs will be in 10 years, so don't sacrifice your needs in the next 2 years to get there.