On Sat, Jan 24, 2009 at 12:27 AM, Aditya <[email protected]> wrote:
>
[..snip..]
>
> To re-iterate (for everyone), the new behaviour is just fine, and if
> your app isn't already setting the 'in_reply_to_status_id', it's about
> high time it did.
>
While I'm currently only building some internal applications for
${work}, the next [REDACTED] site redesign might change some of that.
The new release way of handling replies seems the sane way, especially
if you want to show properly threaded context. It would be the way I
expected it should work if I hadn't read the API and messed with it.
I've always found that assuming or guessing you know what the end user
is attempting to do is a sure sign of something going wrong.
-steve
