#962 closed defect (duplicate)

Replies on don't work with "in context" feature

Reported by: sergiosdj@… Owned by:
Priority: normal Milestone:
Component: Twitter Version: 3.0.5
Keywords:, in context, message, reply Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro: Fedora 16


When someone replies a message using, 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:

and this message:

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.

Attachments (0)

Change History (3)

comment:1 Changed at 2012-05-19T06:17:52Z by 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 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; 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.

comment:2 Changed at 2012-05-19T06:33:11Z by 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.

comment:3 Changed at 2012-11-14T14:56:38Z by wilmer

Resolution: duplicate
Status: newclosed


Sorry for not following up earlier.

Modify Ticket

as closed The ticket will remain with no owner.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.