Live data from Hacker News

Trouble with Diaspora

blog.steveklabnik.com

41–50 of 166 posts

Re: Trouble with Diaspora

#41
post #19
post #17

"Release early, release often" (an open source mantra). Here on HN i also find the 'getto launch' being preached -- "if you not embarrest by your product at lauch-time, you should have released earlier". Judging from the noise their release makes here on HN i think the diaspora guys did well opening up their repo 'early'. And to steve: i think you hold 'professional programmers' (which i interpret as programmer that…

There are a few reasons why this is worse: first, they are launching to media attention and a rabid community. BCC sucked at launch, but no one saw it, so yay. (And by sucked, I mean looked ugly, not "Anyone can delete all your documents at will.") Diaspora has thousands of end users already. Some seeds have 200+. They are launched. Not prealpha. Launched. Their entire reason for existing is "Facebook but private". A…

"BCC sucked at launch, but no one saw it"

Strange thing is, the advantage Facebook had is that it launched to a small audience initially with very limited functionality.

Re: Trouble with Diaspora

#43
post #31

I'm not even sure it's worth submitting patches to Diaspora, both because of the fundamental problems with the code, but also because of their "Open Core" licensing scheme (AGPL + contributor agreement): http://www.ebb.org/bkuhn/blog/2009/10/16/open-core-shareware... Looking through the code, it looks like Diaspora is really just putting a front end and "aspects" on top of OStatus. I think it might be good at this po…

At its core, the real value in something like Diaspora is its protocols. If you disagree with the license, or the language they chose, why not make your own implementation from scratch that can federate with it. If it survives, I might do this... I think their approach is fine for rolling out a private enterprise FB or creating an alternative hosting solution, but I'd like to see an even more decentralized solution.…

[deleted]

Re: Trouble with Diaspora

#44
post #31

I'm not even sure it's worth submitting patches to Diaspora, both because of the fundamental problems with the code, but also because of their "Open Core" licensing scheme (AGPL + contributor agreement): http://www.ebb.org/bkuhn/blog/2009/10/16/open-core-shareware... Looking through the code, it looks like Diaspora is really just putting a front end and "aspects" on top of OStatus. I think it might be good at this po…

At its core, the real value in something like Diaspora is its protocols. If you disagree with the license, or the language they chose, why not make your own implementation from scratch that can federate with it. If it survives, I might do this... I think their approach is fine for rolling out a private enterprise FB or creating an alternative hosting solution, but I'd like to see an even more decentralized solution.…

I would totally love to do that. Except the protocol is undocumented and unstable.

Re: Trouble with Diaspora

#45
post #2

It's great that they're getting so much open-source help, but I'm going to ask the obvious question: if a "complete overhaul" is what's needed, as the author seems to imply, and the FOSS community performs said overhaul, then what of the $250k that was given to the Diaspora guys? Is it still even "Diaspora" anymore, as opposed to a FOSS project?

It's an awful lot easier for a bunch of third parties to refactor and fix something that's bad, a piece at a time, than for a bunch of third parties to create something from nothing. Diaspora is a good thing, even if it's bad: the mere fact of its existence and the enthusiasm around making it better gives it a vector of development that a mere idea would never have.

Re: Trouble with Diaspora

#47
post #42

At least somebody's got a sense of humor: Github issue #8: "Facebook has a majority market share" http://github.com/diaspora/diaspora/issues#issue/8

If you didn't catch it, it's referring to Ubuntu Bug #1: Microsoft has a majority market share

https://launchpad.net/ubuntu/+bug/1

Re: Trouble with Diaspora

#48
post #39

This code was written by a bunch of undergraduate college students. This is hiring a bunch of interns (with near zero experience) to implement your product, giving them three months, and then being shocked -- SHOCKED, when the code is not professional grade quality. I was shocked when everyone and their brother was willing to shell out money to a group of completely unproven college students to produce a distributed…

If they re-write, given that they're fairly inexperienced but are probably still sitting on a pile of cash, they run into the Second System Effect.

http://en.wikipedia.org/wiki/Second-system_effect

Re: Trouble with Diaspora

#49
post #38

First people bitch and whine because they are working "in secret" and not releasing code. Then they release and everyone freaks out because it's not finished. I guess the only way everyone would be happy would be if they released a completed project after a week.

Where in this article does the author complain about it not being finished? It's the fact that the Diaspora team is not doing things right. No one cares that this project isn't finished they care about how much it sucks because their whole reason for starting the project was privacy and they don't even come out of the gates with a secure system for people to implement/build upon...

Re: Trouble with Diaspora

#50
post #17

"Release early, release often" (an open source mantra). Here on HN i also find the 'getto launch' being preached -- "if you not embarrest by your product at lauch-time, you should have released earlier". Judging from the noise their release makes here on HN i think the diaspora guys did well opening up their repo 'early'. And to steve: i think you hold 'professional programmers' (which i interpret as programmer that…

> And to steve: i think you hold 'professional programmers' (which i interpret as programmer that get paid) waaay too high..

What I meant was more of "someone who's knowledgeable about their craft," but you're absolutely right anyway.

Post reply on HN