Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Diaspora Developer Release

joindiaspora.com

Post reply on HN
Print view View original

61–70 of 202 posts

Re: Diaspora Developer Release

#61

Post by glhaynes »

alanh wrote: post #47
xelfer wrote: post #12

They really need to do something about that name. They seem to be having trouble with it themselves: http://github.com/diaspora/diaspora/commit/708e9f88a55cc3713...

For a lot of people, their name’s strongest connotation is Jewish persecution. To me, this is so awkward as to rule out the name for use in serious software.

It's like at my work when I proposed that we could get some benefit from an "interim solution" until we could finish up what we were planning. Of course people started (innocently, ignorantly) calling the original plan the "final solution". Always made me cringe.

Re: Diaspora Developer Release

#62

Post by mark_l_watson »

EGreg wrote: post #58

I've been following this project for a while - these guys are from my school :) Very awesome to see a bunch of undergrad guys come up with this project. I'm still amazed at the PR they got at the time. I'm also kind of working on my own thing ... http://myownstream.com If you set out to make a private social network, though, it's not that easy. Now, instead of trusting facebook, you'll have to trust ALL of your frien…

You are right about having to trust too many different hosting companies or people who install it and make it public, but there should be a way to tunnel directly through to another user with everything in the middle just seeing an encrypted data stream.

However, how about a simpler scenario: you set up on one of your servers and only invite your family to join. Another instance for a club, etc. Have a very easy export/import mechanism to push material in your account in one group to another, under your control.

Re: Diaspora Developer Release

#63

Post by smoody »

Mongodb is an interesting choice. I haven't used Mongodb, so I might be misunderstanding a design decision made by the Mongodb developers, but isn't it possible to get into a situation with Mongodb where the writes are delayed and, as a result, new records (documents) added to a database might not show-up on the following reads (so a user might post a status update, but then he/she might not see it added to his/her status updates page when the pages reloads). Or perhaps the Diaspora developers decided to commit writes to the disk immediately at the cost of performance? Just curious.

Re: Diaspora Developer Release

#64

Post by alttab »

zachrose wrote: post #22
tedkimble wrote: post #20

Earlier quoted context omitted.

Well I believe heroku includes ImageMagick by default, so it seems the only dependency would by MongoDB. Has anyone ever used the MongoHQ add-on? http://addons.heroku.com/mongohq

It's funny, since hearing about Diaspora I understood it as your own portable web app that people run on something like Heroku for non-developers.

You may be on to something there.

Re: Diaspora Developer Release

#65

Post by Pistos2 »

xelfer wrote: post #12

They really need to do something about that name. They seem to be having trouble with it themselves: http://github.com/diaspora/diaspora/commit/708e9f88a55cc3713...

I've found multiple instances of text in more or less official places containing general English problems (spelling, grammar). I'm assuming for the time being it isn't due to outright lack of fluency in English, and so that leads me to think that they just aren't putting in the [little] extra effort to proofread before publishing. It's not that big a deal, but I think it would help for them to look more polished as far as official text goes.

Re: Diaspora Developer Release

#66

Post by alex_c »

patio11 wrote: post #13

Sweet Jesus. Please publish a security reporting page at the earliest possible convenience, because this will have private info on it within a day from now, and that is a very bad idea right now.

>PS:

>Feel free to try to get it running on your machines and use it, but we give no guarantees. We know there are security holes and bugs, and your data is not yet fully exportable. If you do find something, be sure to log it in our bugtracker, and we would love screenshots and browser info.

That seems to cover it, doesn't it?

Re: Diaspora Developer Release

#67

Post by alttab »

rscott wrote: post #29

I'm sorry, but for $200k+ funding you need to do more to impress me than throwing a bunch of gems together and putting it on MongoDB. I like the minimalist design, though.

Don't understand the down voting - for the crowd's investment its arguably all they've done. They did just start however. Releasing at all is more than most expected on their blogs.

Re: Diaspora Developer Release

#68

Post by RossM »

sjtgraham wrote: post #55

Had a 5 minute glance at the code. I don't think they realise that `self` is the default receiver in Ruby, judging by how many times I saw it used superfluously. Anyway, kudos to them for actually releasing some code. I would like to contribute, does anyone know if they are accepting patches?

As far as I know they're accepting patches through github - fork away :)

Re: Diaspora Developer Release

#69

Post by steveklabnik »

tedkimble wrote: post #20
andymoe wrote: post #11

I wonder how hard it would be to get running on a small heroku instance just for fun...

Well I believe heroku includes ImageMagick by default, so it seems the only dependency would by MongoDB. Has anyone ever used the MongoHQ add-on? http://addons.heroku.com/mongohq

I am currently using it for the Hackety Hack site. It's pretty easy to use, check it out:

http://github.com/hacketyhack/hackety-hack.com/blob/master/c...

Post reply on HN