Reply-To is broken

What's worse is that in some cases, the reply to doesn't work at all! Talk about frustrating!

This drives me so crazy. I'm not replying because it's useless. The conversation is all fubar'd.

I don;t even see a mention of "we know this isn't working and we're looking into it."

Come on Twitterfolk! Acknowledge the problem and fix it soon, please?

http://identi.ca does it right. No need to wait for Twitter to get their house in order.

identi.ca however does many things wrong, starting with It's Not Twitter.

Twitter did do this right. It's a bug, not a queston of "doing things right" . Yo, Twitter!

Afaik, @replies have always linked our reply to the latest tweet of the user the reply was addressed to. I don't believe the mis-linking was a recently introduced bug (but I can't say that with 100% certainty)

Also, it's my understanding all along that they added the 'swoosh' to the website to save us the trouble of typing "@username." It wasn't meant to give us the ability to specify which tweet we're actually replying to.

Now... having said all that, I do agree that it would be wonderful if @replies were to link to the actual tweet whose swoosh we clicked on. (Although I suppose this kind of linking won't be possible for @replies posted via sms or im).

Anyway, fwiw, I know they're considering the possibility of letting third-party apps set the reply-to-tweet-id via the API so that third-party apps can link to tweets correctly. However, this enhancement is currently listed as low-priority, so it might be a while before we see any third-party apps that actually provide this feature.

mdy - no, it really DID work corredctly for a while there. I know because I asked for this feature and I was sooooooooo hapy when it was put in. And then to have it disappear again. You can imagine my frustration.

I could WRITE this as a very simple get call.

> fwiw, I know they're considering the possibility of letting third-party apps set the reply-to-tweet-id via the API so that third-party apps can link to tweets correctly. However, this enhancement is currently listed as low-priority,

Twitter! Make this a big priority. If I can envision how to code it in about 20 minutes, I can't see it as being difficult.And right now, conversation is broken and I can't use it.

I'm begging you, please!

True.

Replying is pretty pointless unless you do it immediately before the other person has the time to post another tweet.

And even when you get it right, if the tweet you’d have replied to is deleted, your reply automatically points to the previous tweet... which is incorrect.

The Twitter API was recently updated so that @replies posted via the API can link to the correct tweet via an "in_reply_to_status_id" parameter.

I don't think they'll be able to do that for @replies posted via sms or any of the third-party IM gateways, though.

What remains to be seen is whether @replies posted via the Twitter website itself will be able to take advantage of this.

Oh, it's a fact that @replies posted via the Twitter website itself will be ABLE to take advantage of this.It's just a matter of implementation.

Twitter devs are intelligent. If they don't implement this in the Twitter website... that will be a bug. :)

... woohoooo! Greasemonkey script :)

It looks like this has been fixed on the Twitter site. Yay!

It appears that reply behavior changed a little within the last week or two. The end result is still the same, however.

At one point, status IDs appeared in a URL query string, and is now being inserted into the DOM for submission on the "update" action.

Can anyone explain why Twitter doesn't natively allow "in reply to" to reference someone elses tweet unless that person's @reply begins the message? And I don't mean a technical perspective, but a usability / experience perspective.