Live data from Hacker News

Diaspora Developer Release

joindiaspora.com

191–200 of 202 posts

Re: Diaspora Developer Release

#191

Earlier quoted context omitted.

There is now a security email ID you can contact: exploits@joindiaspora.com It's been added to the README at http://github.com/diaspora/diaspora

Check your email.

Well, I hope they do, and soon. Been reading the code, and it's.. not good :(

Re: Diaspora Developer Release

#192
post #153

Earlier quoted context omitted.

It's gonna be tough to do a Diaspora hosting startup with it being AGPL-licensed.

Why? Look at Heroku; they us all off the shelf software for 90% of their components. People will always pay for convenience.

And in diaspora's case, customizations for your community.

Re: Diaspora Developer Release

#193

Earlier quoted context omitted.

> For a lot of people, their name’s strongest connotation is Jewish persecution. Funny, I think of http://en.wikipedia.org/wiki/African_diaspora

Funny, I think of New Orleans

Funny, I think of how I use social networking to talk to those I can't see, or I'm not around. The entire idea fits the term more than the term fits it. We are all seeking connectedness.

Re: Diaspora Developer Release

#195
post #185

I'm really disappointed to see that the team has decided that instead of learning about an existing standard (XMPP) which fits the purpose perfectly, they've decided to begin defining their own protocol, which will go down the same path but with less rigour and a whole lot of wasted time. Eventually it will have to be trashed in favour of something more robust. If that's what they've spent the last three months worki…

We are indeed all about being pragmatic. I think a lot of our pragmatism has rubbed off on the Diaspora folks, but do keep in mind that we're not really advising them in any formal capacity. (Other than the occasional conversation over breakfast, or when they ask about ideas.) I'm sure if you asked them about their choices, they'd be very happy to take in new ideas. Not to speak for them, but I think they're just try…

I've posted to the diaspora-dev list pointing to this comment, so hopefully one of the Diaspora guys will take a look at this soon.

I'll also follow up shortly with a blog post with more details about how this might be implemented atop a well defined set of standards and the benefits of doing so vs re-inventing the wheel.

Re: Diaspora Developer Release

#196

I'm really disappointed to see that the team has decided that instead of learning about an existing standard (XMPP) which fits the purpose perfectly, they've decided to begin defining their own protocol, which will go down the same path but with less rigour and a whole lot of wasted time. Eventually it will have to be trashed in favour of something more robust. If that's what they've spent the last three months worki…

They actually explicitly dismissed XMPP (see the comment on this video from them: http://vimeo.com/13026173). They were also approached by the onesocialweb.org team to work together and also dismissed the invite.

It seems however that they plan to align with the ostatus.org protocol, but so far no documentation of their architecture and protocol has been delivered. In Ostatus, the server-server messaging is HTTP based and using the PubSubHubBub and Salmon protocols.

Re: Diaspora Developer Release

#197

I'm really disappointed to see that the team has decided that instead of learning about an existing standard (XMPP) which fits the purpose perfectly, they've decided to begin defining their own protocol, which will go down the same path but with less rigour and a whole lot of wasted time. Eventually it will have to be trashed in favour of something more robust. If that's what they've spent the last three months worki…

They actually explicitly dismissed XMPP (see the comment on this video from them: http://vimeo.com/13026173 ). They were also approached by the onesocialweb.org team to work together and also dismissed the invite. It seems however that they plan to align with the ostatus.org protocol, but so far no documentation of their architecture and protocol has been delivered. In Ostatus, the server-server messaging is HTTP bas…

A video demo of "hey look, click here and something happens over there!" is all well and good for impressing your mother, but not entirely useful looking forward. They've mentioned concerns with horizontal scaling and yet they don't consider the obvious option - Erlang.

In their presentation for Pivotal's Tech Talks series, they dismissed XMPP on the basis of not wanting to learn about it(!). Their dismissal of onesocialweb seems inappropriate on technical grounds. Also, HTTP is not the be-all and end-all. Not everything has to be shoehorned onto HTTP...

Re: Diaspora Developer Release

#198

Earlier quoted context omitted.

They actually explicitly dismissed XMPP (see the comment on this video from them: http://vimeo.com/13026173 ). They were also approached by the onesocialweb.org team to work together and also dismissed the invite. It seems however that they plan to align with the ostatus.org protocol, but so far no documentation of their architecture and protocol has been delivered. In Ostatus, the server-server messaging is HTTP bas…

A video demo of "hey look, click here and something happens over there!" is all well and good for impressing your mother, but not entirely useful looking forward. They've mentioned concerns with horizontal scaling and yet they don't consider the obvious option - Erlang. In their presentation for Pivotal's Tech Talks series, they dismissed XMPP on the basis of not wanting to learn about it(!). Their dismissal of oneso…

I second that. All of it.

Re: Diaspora Developer Release

#199
post #4

It looks surprisingly advanced, from a screenshot perspective - more than I admit I would have given them credit for. Is there additional insight into what "aspects" are, though? It confuses me - will it confuse an ordinary user?

Perhaps friend lists

And perhaps the initial aspect names and all other strings should not be hard coded in English into the product. Yes, it is pre-alpha, but it will be a pain later to replace all strings with the #t helper and keywords.

Re: Diaspora Developer Release

#200
post #131

If it's true that for a social network to be successful it needs some quick growth at the beginning to have a critical mass, then Diaspora is in trouble. They're in trouble because they release non-usable alpha versions of their code, loose the buzz ("Diaspora released another version today, X works now, but it's still not good enough to replace Facebook."), and by the time they have a 1.0 version nobody's going to c…

Firefox seems to have survived this — with targeted buzz on big launch days.
Post reply on HN