Replies with twitter4r

4 views
Skip to first unread message

Dan Simard

unread,
Nov 13, 2007, 6:51:29 PM11/13/07
to twitter4r-users
Does anyone knows how to get the replies? Replies are status updates
prefixed with @username posted by users who are friends with the user
being replied to.

The twitter api call is http://twitter.com/statuses/replies.xml

Thanks a lot.

S Potter

unread,
Nov 13, 2007, 6:56:41 PM11/13/07
to twitter...@googlegroups.com
Hi Dan,

I know I replied to your private email, but I thought I would include
it on the mailing list so that it is out there for people to reference
when needed:
----
Hi Dan,

I just went to the Twitter development talk API Documentation page and
realized that API sneaked in under statuses since the last major
release of Twitter4R in July without me realizing. I apologize for
the oversight, the documentation page doesn't make new API entries
easy to spot, so I need to resort to visual inspection which is
horribly prone to human error (especially in my case:)).

I will add this to my list for a 0.3.1 release (even though it is a
*new* feature, it is from an old component of the API, so I don't feel
so bad sneaking it in, in a minor release). I plan for this to be
added using the following notation:

client.status(:replies)
# OR
client.status(:replies, :page => 3)

Let me know if this seems reasonable before I dig into it tonight.
Thanks,
Susan

--
mailto:m...@susanpotter.net
www:http://susanpotter.net
blog:http://snakesgemscoffee.susanpotter.net
linkedin:http://linkedin.com/in/susanpotter

--
mailto:m...@susanpotter.net
www:http://susanpotter.net
blog:http://snakesgemscoffee.susanpotter.net
linkedin:http://linkedin.com/in/susanpotter

SP

unread,
Nov 15, 2007, 9:33:18 AM11/15/07
to twitter4r-users
Just to let people know that 0.3.1 is taking a little longer than
expected due to my current (day job) work backlog as well as
difficulty fixing the #to_xml defect promised prior to the
#status(:replies) feature. I may be forced to add an extra dependency
(to the builder gem) in order to transparently make Model#to_xml work
as Rails does with all the options supported.

I don't want to do this lightly (adding an extra dependency in a minor
release), so I will investigate more thoroughly over the weekend.

Thanks,
Susan

On Nov 13, 5:56 pm, "S Potter" <mbbx6...@gmail.com> wrote:
> Hi Dan,
>
> I know I replied to your private email, but I thought I would include
> it on the mailing list so that it is out there for people to reference
> when needed:
> ----
> Hi Dan,
>
> I just went to the Twitter development talk API Documentation page and
> realized that API sneaked in under statuses since the last major
> release of Twitter4R in July without me realizing. I apologize for
> the oversight, the documentation page doesn't make new API entries
> easy to spot, so I need to resort to visual inspection which is
> horribly prone to human error (especially in my case:)).
>
> I will add this to my list for a 0.3.1 release (even though it is a
> *new* feature, it is from an old component of the API, so I don't feel
> so bad sneaking it in, in a minor release). I plan for this to be
> added using the following notation:
>
> client.status(:replies)
> # OR
> client.status(:replies, :page => 3)
>
> Let me know if this seems reasonable before I dig into it tonight.
> Thanks,
> Susan
>
> On Nov 13, 2007 5:51 PM, Dan Simard <dsim...@gmail.com> wrote:
>
>
>
> > Does anyone knows how to get the replies? Replies are status updates
> > prefixed with @username posted by users who are friends with the user
> > being replied to.
>
> > The twitter api call ishttp://twitter.com/statuses/replies.xml
Reply all
Reply to author
Forward
0 new messages