I have asked our developers to implement the statuses/filter API stream,
however they have come back with the following:
1) We will not be able to fetch previous tweets for the accounts because
count parameter can not be used for default role (but can be used for
increased access level roles e.g.
Hi Neil,
This is where you fallback to the REST API. If you need to catch up you
can do so to the best of your abilities (and availability) via REST (as
you'll have plenty of remaining API calls since you'll only be using REST
for backfill and supplemental metadata).
The implementation is not
On Thu, Nov 18, 2010 at 10:03 AM, Neil Sheth sheth.n...@gmail.com wrote:
I have asked our developers to implement the statuses/filter API stream,
however they have come back with the following:
1) We will not be able to fetch previous tweets for the accounts because
count parameter can not be
Quoting Adam Green 140...@gmail.com:
In general, if you are planning on capturing *all* tweets for a set of
words or users, and *never* losing any, you are setting an impossible
goal. Aiming for a very high level of accuracy is all you are going to
achieve. With the right coding 99% or better
Hi Adam,
Thanks for your advice, just wanted to ask if you have a link to the
solution you mentioned for point 2 i.e. the Search API?
Regards
Neil
On 18 November 2010 15:19, Adam Green 140...@gmail.com wrote:
On Thu, Nov 18, 2010 at 10:03 AM, Neil Sheth sheth.n...@gmail.com wrote:
I have
Neil:
If you mean a link to the Twitter doc on the search API, that is here:
http://dev.twitter.com/doc/get/search
I've also written a detailed comparison of the search API vs. the
streaming API that may help your coders pick the right solution:
This is great advice, many thanks.
Will keep your blog and personal email address in mind for the future
Sent from my iPhone
On 18 Nov 2010, at 21:56, Adam Green 140...@gmail.com wrote:
Neil:
If you mean a link to the Twitter doc on the search API, that is here:
We have previously raised a request to obtain twitter whitelisting but
have been told by Twitter (Brian) that we have built the wrong
solution. Our developers are struggling to understand which solution
they need to build for our site www.mystweet.com in order to get
whitelisted. They have
The Streaming API to which Brian referred is:
http://dev.twitter.com/doc/post/statuses/filter
Tom
On 11/16/10 10:32 PM, Neil wrote:
We have previously raised a request to obtain twitter whitelisting but
have been told by Twitter (Brian) that we have built the wrong
solution. Our developers
Hi Neil,
What are you particularly trying to accomplish with your Twitter
Integration? How are tweets used in the application? What APIs were you
leveraging when you were planning a REST-only solution?
While Site Streams is officially beta right now, it's very reliable -- but
whether it's the
Just wanted to chime in quickly. I've been using Site Streams in
production for over a month now and have found them to be absolutely
fantastic. Really rock solid. If Site Streams are indeed what you're
looking for, I wouldn't let the beta tag scare you away.
Taylor Singletary wrote:
Hi
Hi Taylor,
We are pulling in tweets into our site for various twitter users and
displaying their tweets. The part that confuses me is whether we need to
build the API stream that Brian described in his email (Statuses/Filter) or
the site_streams API as mentioned by our developers? Also, just to
If the only thing you want to do is follow the tweets of some users,
your best option is the filter stream.
Tom
On 11/16/10 11:04 PM, Neil Sheth wrote:
Yes - but it looks like the site_streams API (in beta) does the same
thing, unless I'm missing something. Just wondering whether we need to
Great - thanks Tom. For our site we will be pulling in quite few thousand
tweets per hour. Do you see any limitation with this API?
On 16 November 2010 22:01, Thomas Mango tsma...@gmail.com wrote:
Just wanted to chime in quickly. I've been using Site Streams in production
for over a month
Hi,
as far as I understand the docs there is no limit on the tweets for
stream/filter. However, as a regular user you can only follow up to 5000
users (but you should get all of their tweets). If this limits you, you can
apply for Shadow-role to up this limit to more users (20k afair).
To answer
One way to approach this problem:
For each user's tweets that you want to track -- do you want to require that
user to be an authenticated member of your site and opt-in to having you
track their tweets, likely in the context of providing a (mostly private)
Twitter client experience on the web
I'm using the streaming API to pull in tweets at that rate for several
sites with no problem. The default access level gives you all the
tweets for up to 5,000 users.
http://dev.twitter.com/pages/streaming_api_methods#statuses-filter
From my experience, if you create a useful site for this level
Thanks D - Shadow-role, no doubt I will need to reference this email when
we get there!
On 16 November 2010 22:16, yaemog Dodigo yae...@gmail.com wrote:
Hi,
as far as I understand the docs there is no limit on the tweets for
stream/filter. However, as a regular user you can only follow up to
This is very clear now, thanks for the advice.
On 16 November 2010 22:17, Taylor Singletary
taylorsinglet...@twitter.comwrote:
One way to approach this problem:
For each user's tweets that you want to track -- do you want to require
that user to be an authenticated member of your site and
Quoting Tom van der Woerdt i...@tvdw.eu:
If the only thing you want to do is follow the tweets of some users,
your best option is the filter stream.
Yep - you now get 5000 users from 'filter' without applying for
elevated access, and many more if you qualify for elevated access. In
20 matches
Mail list logo
