[SOLVED] Joindiaspora and me – #FAIL all over the place

Posted 2011-01-04

*UPDATE* My problems are fixed! I am impressed. Finally I can use Diaspora again. Thanks to the devs who finally looked at Bug #734 and fixed my problems.

So I am one of those with an account at joindiaspora. And I have some requests by other users to become my contact.

Which is nice! But since 2 weeks, I cannot accept these requests, I cannot read notifications, I cannot use anything but the homepage. Because everytime I click on the requests, on the notifications, on my aspects, I get a nice Error 500:

I found out after a bit of thinking and searching that the root cause probably is in this bug report:

Not sure, but I think it’s because someone who invited me has deleted their account.

Which could make sense. If someone sends me a request and deletes his account before I accept the request, the now orphaned request seems to cause trouble. Ofcourse this means that the current process of deleting an account in diaspora is a bit sloppy as it seemingly doesn’t care about such orphaned requests. With all that in mind, some other brave soul with is own diaspora node tried my guess and – guess what – it turns out to be reproducible:

“I managed to reproduce the error on my local Diaspora installation by deleting the person from whom the request comes from manually from MongoDB. I get exactly the same error so this I probably the cause.”

OK, so we have the root cause nailed down, we have a bug report. Now the only thing needed is a developer who fixes it and pushes the fix to joindiaspora.com.

And that is where we are. Unfortunately nothing seems to happen. No developer takes the bug, no one reacts. This bug renders my account effectively useless as I can do nothing besides doing a reload on the homepage. As soon as I switch to aspects, try to answer requests or even read my notifications . error 500.

I do hope this blog entry might be read by one of the diaspora devs. Please fix this. I am ready to help. But you need to react on your won bugtracker first. ATM this is a #FAIL situation. 16 days of an open bug and not a single action from the devs.

To those of you that sent me requests and wonder why I don’t act – here you are.

Loading Google+ Comments ...