But this depends on how fast you tweet and how/where they see the message, doesn't it?
If you tweeted a question then something completely unrelated (some people's Twitter stream _can_ be likened to verbal diarrhea), and people replied with a simple @ - then those same 6 @replies would have lacked the proper context. When that happens, it's a challenge in any client (especially the web) to click through to an incorrect tweet, back out, look at the old tweet, observe the time, review the user's timeline for a matching time, etc. This process is similar when the "in reply to" metadata doesn't exist, with the exception of misleading the user in the first place. I've always wanted the Twitter web to have forward and next buttons on a tweet status page (for numerous reasons), and that's a great use case (and justification) for linking to incorrect status id's...but it just doesn't exist. I for one appreciate the decision to not automatically set the "in reply to" metadata as I would rather have accurate information than not. Most clients _should_ adopt this behavior. The web is definitely a challenge, but I'm sure some jQuery action could be tossed in to evaluate @user's last tweet on the page, eh Twits? (which _might_ be more accurate than just the most recent status id) dpc (@dacort) On Jan 24, 9:09 pm, simX <[email protected]> wrote: > Just as a data point, of the 20 most recent @replies I have received, > 6 of them lack the "in reply to" metadata when they are clearly > responding to a specific tweet of mine. > > That's a linkage failure rate of 30% due to this change in Twitter's > API behavior. I would say that's pretty severe.
