How can I reply via IM to specified post? I mean - I can use @user to add comment someones comment but what if he reply to something different in the meantime?
Yeah, it's bitten me a couple of times. I thought I could do
@dpc#jaiku, but that doesn't work.
Being able to say ?33971212 or something would be better than
nothing.
No, ideally it'd use XMPP's native thread. And ideally, clients
would know what to do with that. (For all I know, it might already,
and clients just suck)
I wonder if it is really such a problem to implement such little
things or they are not being implement because it would confure
common users. Nor Jaiku, nor twitter have more than just basic
functionality.
I commented on this a couple of times in the past. UI wise it is
not very straight forward way to provide a reference to use to make
comments with. The proposal to add some (relative) identifier in
messages was not thought to be very nice. I haven't really found a
good solution, so far.
that might be the case for as long as it will remain in one
RDBMS, yes. Not having any insight in that, I think that is likely
to change with the port to Google App Engine.
Valid concerns. One could introduce short id counter for each
user. Each time message is being delivered to user it would come
with incremented id. As they could be valid for short time (a day
maybe) they could be wrapped to 0 so they should stay quite short.
Having sad that - I'd still rather use quite long jaiku-ids. In
fact they are easier to type without mistake than "@ralphm". :)
26 comments so far
You can't
6 days, 16 hours ago by edythemighty.
No possibility to use this magic number generated for each post? :|
6 days, 16 hours ago by dpc.
Nope
6 days, 16 hours ago by edythemighty.
:( waaaaaaaaaaaaaaan to bad, also often it sends message to wrong jaiku while replying from im, and we yehba users all use jaiku with im :((
6 days, 16 hours ago by Aaqil.
@Aaqil which is why I don't use Jaiku though IM
6 days, 16 hours ago by FyreFiend.
That, and @FyreFiend can't type fast and gud
6 days, 16 hours ago by edythemighty.
:-s edy
6 days, 16 hours ago by Aaqil.
LOL
6 days, 15 hours ago by dpc.
I don't know of a way to do that -- it's a bug in the threading model
6 days, 15 hours ago by stpeter.
Yeah, it's bitten me a couple of times. I thought I could do @dpc#jaiku, but that doesn't work. Being able to say ?33971212 or something would be better than nothing.
6 days, 15 hours ago by dwd.
That would be more than nothing, that would be perfectly fine for me. :D
6 days, 15 hours ago by dpc.
No, ideally it'd use XMPP's native thread. And ideally, clients would know what to do with that. (For all I know, it might already, and clients just suck)
6 days, 14 hours ago by dwd.
I see a friendly XMPP-geek here, do I? :D
6 days, 14 hours ago by dpc.
Never heard of it. ;-)
6 days, 14 hours ago by dwd.
So I probably haven't thought of PEP integration, yet. :D
6 days, 14 hours ago by dpc.
I wonder if it is really such a problem to implement such little things or they are not being implement because it would confure common users. Nor Jaiku, nor twitter have more than just basic functionality.
6 days, 14 hours ago by dpc.
I think it's a case of getting the basics working on every client first.
6 days, 14 hours ago by dwd.
In case of xmpp-threads, yes. But not being able to use thread id to reply ... . It is probably matter of 40 line of code somewhere (I'd expect).
6 days, 14 hours ago by dpc.
I commented on this a couple of times in the past. UI wise it is not very straight forward way to provide a reference to use to make comments with. The proposal to add some (relative) identifier in messages was not thought to be very nice. I haven't really found a good solution, so far.
4 days, 17 hours ago by ralphm.
Isn't it? Why? Is it to long?
4 days, 17 hours ago by dpc.
that, and potentially confusing and ugly and such
4 days, 17 hours ago by ralphm.
Knowing that they are constantly auto-incremented one could write down just last 4, 5 digits ... . I don't see any uglynes.
4 days, 17 hours ago by dpc.
well, they are not guaranteed to be monotonicallly increasing, that is just cosmic coincidence in your observation.
4 days, 17 hours ago by ralphm.
I'd be surprised if Jaiku IDs would be just plain auto-incremented keys used in sql database ... .
4 days, 17 hours ago by dpc.
that might be the case for as long as it will remain in one RDBMS, yes. Not having any insight in that, I think that is likely to change with the port to Google App Engine.
4 days, 17 hours ago by ralphm.
Valid concerns. One could introduce short id counter for each user. Each time message is being delivered to user it would come with incremented id. As they could be valid for short time (a day maybe) they could be wrapped to 0 so they should stay quite short. Having sad that - I'd still rather use quite long jaiku-ids. In fact they are easier to type without mistake than "@ralphm". :)
4 days, 17 hours ago by dpc.