John,
thanx for your comment over at groovyconsole.appspot.com -
http://groovyconsole.appspot.com/view.groovy?id=19003
In case you do not get updates on comments there, let me ask my main
question again. This would make my (our) lives a lot easier when it
comes to retweet tracking, still it woul
I'll update the Wiki to reflect the new reality.
Retweets will begin to flow through all /1/statuses/* resources soon
-- in advance of the full retweet launch. This will give developers
time to test and deploy features in advance. Also, the retweet volume
is very low now, so exceptions should be
John, I assume the method to use would then be
http://stream.twitter.com/1/statuses/filter.format
It does not mention that it includes retweets, but it will once the
API is live?
Cheers
Sven
On Sep 23, 9:38 pm, hansamann wrote:
> Thanx, I'll give that a try.
>
> On Sep 23, 8:11 pm, John Kaluc
Thanx, I'll give that a try.
On Sep 23, 8:11 pm, John Kalucki wrote:
> Retweets will be searched by the follow parameter on the filter
> resource. The intention is that you get all statuses (including
> retweets) where any user_id field matches your predicate list. So,
> tweets, replies and both
Retweets will be searched by the follow parameter on the filter
resource. The intention is that you get all statuses (including
retweets) where any user_id field matches your predicate list. So,
tweets, replies and both ends of retweets.
If GAE cuts you off after 30 seconds, then you shouldn't op
Is there a way to connect to the streaming api and only get my friends
retweets? Or would I get *everyones* retweets and have to filter
millions of unwanted messages out?
On Sep 22, 9:49 pm, John Kalucki wrote:
> Retweetaggregators should use the Streaming API /1/statuses/sample
> method to gath
One reason for example is being on Google App Engine and having a 30
second limit. I cannot keep the connection open.
Another reason is I am not interested in everyones retweets, just the
retweets (and in this case all, not just a sample) of that twitter
user's friends.
What do you think?
Cheer
I think the new RT API is an attempt to turn related tweets into a
computer-parseable conversation. Humans can fairly easily determine
what it part of an existing conversation by reading the different tweets
and using contextual clues, but computers cannot.
The small benefit to us humans is that
> As a regular twitter user, I'm less thrilled. Once this is in place,
> is it going to fundamentally what/how I see my public timeline? If the
> mockups are anything to go by, it looks less useful. If someone I'm
> following retweets something from SarahKSilverman, I don't want to see
> SarahKSil
Maybe this isn't the right place, but...
>From a developer perspective I love the retweet API and it's potential
uses.
As a regular twitter user, I'm less thrilled. Once this is in place,
is it going to fundamentally what/how I see my public timeline? If the
mockups are anything to go by, it loo
I'm seeing retweet_details information appearing in the payload of the
statuses/show call. Is this normal behavior?
Try this curl http://twitter.com/statuses/show/4297637412.xml
Thanks - Martin
On Sep 18, 4:57 pm, Marcel Molina wrote:
> The Retweet API launch is close at hand. You might have a
Retweet aggregators should use the Streaming API /1/statuses/sample
method to gather a sample of Retweets or apply for the full Retweet
stream on /1/statuses/retweet.
The Streaming API may be in Alpha, but the service has been very
reliable.
I'm unaware of any technical issues that would block a
I am still hoping for an answer to the questions in this thread, but
meanwhile here is another idea the Twitter Team might find
interesting.
As it seems many of us want to track retweets. What we are really
interested in is the number of retweets over time so we can find
trending topics, in my ca
Marcel Molina wrote:
> To give you some ideas of how you can use the API to display retweets,
> here is a recent mock up of one of the potential UIs for the retweets
> timeline on twitter.com:
> http://a1.twimg.com/example-retweet-ui-18-sep-09.png
In this example, how did you retrieve the number
Excactly, my main point, too.
The problem is I want to track how tweets 'develop' over time. This
means I would need to pull the status/retweets every minute or so for
every tweet I am tracking. There is a 150 api call limit currently...
without whitelisting I will be doomed.
I was hoping that t
On Fri, Sep 18, 2009 at 1:57 PM, Marcel Molina wrote:
>
>
> Asking developers to collapse retweets in timelines is onerous,
> complicated and confusing. We're not going to do it that way. We are
> going to add a resource that gives you all retweets for a given tweet.
> In timelines you will get o
16 matches
Mail list logo
