"in reply to" gone from timelines?

[dean.j.robinson]

Have you guys removed the "in reply to" tweets from the timelines?

Just a had a query as to why Hahlo 3 isn't displaying them anymore,
and checked the xml, json feeds etc to find that they aren't being
included anymore, only the id of the status is there.

[Alex Payne]

We never meant to be shipping just the text of the in-reply-to status.
So, yes. Apologies if that messes with your release :(

--
Alex Payne
http://twitter.com/al3x

[David Håsäther]

On Apr 26, 5:36 am, "Alex Payne" <a...@twitter.com> wrote:
> We never meant to be shipping just the text of the in-reply-to status.
>  So, yes.  Apologies if that messes with your release :(

Is there a possibility that something like "in_reply_to_user_name"
could be included? For example, in the Opera widget, I have e.g.
"about 1 hour ago to al3x". This will now require an extra request to
find out the username of "in_reply_to_user_id".

[David Håsäther]

(It could of course be achieved by just parsing out the username from
the text. Having a new field would give the right capitalization
though, for one ;-).

[dean.j.robinson]

It doesn't mess with the release, but it was one of the more popular
'new' features that I had put in, and a lot of people were wondering
why it disappeared.

I could use the "replied to" status id thats returned to retrieve the
message text, but thats going to use up a users 70 requests per hour
pretty quickly.

Before, as you would be aware, all timelines seemed to be returning
the full 'thread' of the conversation, even if the chain of replies
was 10-15 long (rare, but possible).

Is there any chance that the details of just the message directly
"replied to" (and not all those before it) could be returned for all
timelines where appropriate, and then have the full chain returned by
the "statuses/show" method for viewing individual tweets. Maybe this
could even be an option similar to the 'lite' option, you could have
'full' or something to that effect.

I completely understand if it was removed for performance reasons, but
I figured it can't hurt to ask (plenty of people have been asking me
where its gone).

cheers

Dean

On Apr 26, 1:36 pm, "Alex Payne" <a...@twitter.com> wrote:
> We never meant to be shipping just the text of the in-reply-to status.
> So, yes. Apologies if that messes with your release :(
>
> On Fri, Apr 25, 2008 at 8:32 PM, dean.j.robinson
>

[Alex Payne]

I do like the idea of returning an inline representation of
in-reply-to statuses, and returning the whole conversational chain
where applicable. I'll look into what that entails for us.

--
Alex Payne
http://twitter.com/al3x

[dean.j.robinson]

Thanks Alex, it would fantastic if it could be made available again.

:)

[alexkingorg]

Can we count on the current information (reply to status id and reply
to user id) remaining in the JSON stream? Or will that possibly change
depending on what you decide after thinking through this?

My most recent beta of Twitter Tools also used the reply-to data and I
like the feature. I don't mind making additional calls if I have to
(to get the reply-to username), but getting the reply-to username
instead of reply-to user id would mean that I don't have to make any
additional calls to construct the data/links I present.

Though I mainly want to hold off on a full release until I know the
format around this data is relatively stable. :)

Cheers,
--Alex King

> > > > Have you guys removed the "inreplyto" tweets from the timelines?

[jungle]

On Apr 28, 7:36 am, "dean.j.robinson" <Dean.J.Robin...@gmail.com>
wrote:

> I completely understand if it was removed for performance reasons, but
> I figured it can't hurt to ask (plenty of people have been asking me
> where itsgone).

It wasn't removed for performance reasons, but for security reasons:

http://groups.google.com/group/twitter-development-talk/browse_thread/thread/dc22c3ceb5a37c1d/bac3492dd3d26d44

[dean.j.robinson]

Yes I know, I was contacted off list by another user after my original
post.

I'm now making use of the "tweet id" that is available in the feed at
using that as a link to return the tweet in question, but would really
prefer if it could be added back into the feed as it was before
(obviously with the previously mentioned security thingo fixed)

On May 23, 2:40 am, jungle <jha...@gmail.com> wrote:
> On Apr 28, 7:36 am, "dean.j.robinson" <Dean.J.Robin...@gmail.com>
> wrote:
>
> > I completely understand if it was removed for performance reasons, but
> > I figured it can't hurt to ask (plenty of people have been asking me
> > where itsgone).
>
> It wasn't removed for performance reasons, but for security reasons:
>

> http://groups.google.com/group/twitter-development-talk/browse_thread...