Replies on Identi.ca don't work with "in context" feature

[sergiosdj@…]

When someone replies a message using Identi.ca, the message does not get included in the general context of other messages of the same conversation. Instead, each reply is treated separately and show up as atomical "message -> reply", instead of global contexts.

Take this message, for example:

​http://identi.ca/conversation/93427035#notice-93802691

and this message:

​http://identi.ca/notice/93803229

The second is a reply to a reply of the first link, so it should appear in the full context of the conversation, but instead they appear separately.

[sergiosdj@…]

After examining network traffic, I think I know what is wrong. When I reply to a user using the nickname: REPLY, the in_reply_to_status_id parameter is not sent in the HTTP headers to Identi.ca servers. Notice that this parameter is sent to Twitter servers, however.

When I try to reply to a user using the message ID, like:

<mynick> reply 50 Testing

bitlbee gives me an error:

<@root> | User `21' does not exist or didn't post any statuses recently

Notice also that this only happens on Identi.ca; Twitter is OK. This last bug is related to #872.

I still did not have time to debug further in order to understand why bitlbee is confusing things.

[sergiosdj@…]

Another fact: just like the reporter in #872 said, the User XX does not exist or didn't post any statuses recently error does not happen every time. Sometimes I can post things without problems by using the reply XX command, and surprisingly this command appears to Do The Right Thing (TM) and set in_reply_to_status_id properly, thus making "in context" work as expected.

If I use nick: style replies, in_reply_to_status_id is not set, as mentioned in the last comment.

[wilmer]

#872

Sorry for not following up earlier.