A quick scan of the source code suggests that error happens when you don't have sufficient permission to view or write to a stream.
In this case it looks like you're trying to reply to @plindberg's last message but either @plindberg or the last message he sent is private and you're not allowed to reply to it. Either @plindberg is not your contact or his last post was on a thread owned by a private user who isn't your contact.
We should improve the error messages but it's tricky to find a user-friendly way of expressing some of the error scenarios.
In this case, I'm pretty sure it's because @plindberg's last comment was made to a post owned by a user which has her Jaikus set as private.
Ideally, Jaikuengine should iterate through posts and comments starting with the most recent until it finds one that's available. It should return a friendly error message upon reaching posts and comments that are older than, say 6 hours.
@adewale: I added issue 125. Feel free to improve the title and add anything to it, it's tricky to explain these kind of things (especially since English is not my first language :)
Why not do something along the lines of what Friendfeed's IM bot does, where every post gets a number pre-pended to it and then you reply to the number instead of the user? That way you completely eliminate any confusion over what post someone is replying to.
The numeric identifiers have a slight problem. The native Jaiku identifier for this thread is: e96a30b772574e3d8f88c22ef12d9a8f That's not user friendly as most people will mis-type it unless they get in the habit of copy-pasting it.
The other approach is to have a different and shorter number which rolls over every X hours but that has it's own problems.
14 comments so far
A quick scan of the source code suggests that error happens when you don't have sufficient permission to view or write to a stream.
In this case it looks like you're trying to reply to @plindberg's last message but either @plindberg or the last message he sent is private and you're not allowed to reply to it. Either @plindberg is not your contact or his last post was on a thread owned by a private user who isn't your contact.
We should improve the error messages but it's tricky to find a user-friendly way of expressing some of the error scenarios.
4 months, 2 weeks ago by adewale
In this case, I'm pretty sure it's because @plindberg's last comment was made to a post owned by a user which has her Jaikus set as private.
Ideally, Jaikuengine should iterate through posts and comments starting with the most recent until it finds one that's available. It should return a friendly error message upon reaching posts and comments that are older than, say 6 hours.
4 months, 2 weeks ago by lemonad
That's a good idea. Can you file a bug for it. I suspect we would need to make the size of the reply window configurable though.
4 months, 2 weeks ago by adewale
@adewale: I added issue 125. Feel free to improve the title and add anything to it, it's tricky to explain these kind of things (especially since English is not my first language :)
4 months, 2 weeks ago by lemonad
@adewal @lemonad good to see this being looked into. It seems the quick fix would be to reword the error message.
4 months, 2 weeks ago by jyri
so long not rec update from you.. what happen?
4 months, 2 weeks ago by fullfilth
Why not do something along the lines of what Friendfeed's IM bot does, where every post gets a number pre-pended to it and then you reply to the number instead of the user? That way you completely eliminate any confusion over what post someone is replying to.
4 months, 2 weeks ago by CAW
Yes! Good idea! But the problem in Jaiku Bot remains.
4 months, 2 weeks ago by jocap
Oh.. I mean.. It doesn't remain, but your idea is great :)
4 months, 2 weeks ago by jocap
@jocap: Remains after implementing @CAW's suggestion or remains after implementing issue 125?
4 months, 2 weeks ago by lemonad
Ah, okay.
4 months, 2 weeks ago by lemonad
i've been pushing for @CAW since for ever, both here and on identica. I have no idea why no one wants to push it!
4 months, 2 weeks ago by BUGabundo
@termie has suggested a variation of your idea on this issue: http://code.google.com/p/jaikuengine/issues/detail?id=108
The numeric identifiers have a slight problem. The native Jaiku identifier for this thread is: e96a30b772574e3d8f88c22ef12d9a8f That's not user friendly as most people will mis-type it unless they get in the habit of copy-pasting it.
The other approach is to have a different and shorter number which rolls over every X hours but that has it's own problems.
4 months, 2 weeks ago by adewale
@adewale: why not make it beta quality and have ppl test a few variations each week? u will easily get a few beta testers (i'm in!).
4 months, 2 weeks ago by BUGabundo