You can pull the most recent 3200 statuses for a user and that is it.
Abraham
On Tue, Aug 4, 2009 at 00:24, Dharmesh Parikh dharmesh.par...@gmail.comwrote:
So if i user_timeline REST api call and use max_id =X or since_id = Y and
count=200 i can get 3200 messages backwards from X or 3200
This is Basic Auth.
Dan
Seems like you are hitting the follower limit. Twitter regulates the number
of people you can follow based on your follower/following ratio. Try using
another account and see if the issue persists.
On Tue, Aug 4, 2009 at 8:01 AM, Dan Kurszewski dan.kurszew...@gmail.comwrote:
This is Basic
Graphs of more than several thousand users, following or followed by.
On Fri, Jul 31, 2009 at 11:09, Arik Fraimovicharik...@gmail.com wrote:
On Jul 31, 9:03 pm, Alex Payne a...@twitter.com wrote:
To clarify, since several people have asked: this pending change does
NOT mean that pagination
What our infrastructure team has told me is that they can support both
behaviors for a limited period of time.
On Fri, Jul 31, 2009 at 12:06, Isaiahsupp...@yourhead.com wrote:
First off, thanks for the heads up and giving us a large lead time. It's
what I asked for in a previous email, and
It will be a hash with 'ids' as one of the elements.
On Sat, Aug 1, 2009 at 18:26, Dewald Pretoriusdpr...@gmail.com wrote:
Alex,
For non-paged calls, will the result set be [1,2,3,...] or will it be
{ids: [1,2,3]} ?
Dewald
On Jul 31, 3:03 pm, Alex Payne a...@twitter.com wrote:
To
Once we deprecate the page parameter, it will simply be ignored and
the method will attempt to return the entire result set.
On Sun, Aug 2, 2009 at 15:15, janoles...@mobileways.de wrote:
Hi Alex,
In two weeks, we'll be addressing this with a change in back-end
infrastructure. The page
Chiming in: Please do support both methods of access for 'a while
rather than a hard cutover... thx! At least two week would be
appreciated...
jeffrey greenberg
http://www.inventivity.com
http://www.tweettronics.com
On Aug 4, 10:15 am, Alex Payne a...@twitter.com wrote:
What our infrastructure
What about the XML response format? How will it change?
On 8/4/09 1:16 PM, Alex Payne wrote:
It will be a hash with 'ids' as one of the elements.
On Sat, Aug 1, 2009 at 18:26, Dewald Pretoriusdpr...@gmail.com wrote:
Alex,
For non-paged calls, will the result set be [1,2,3,...] or will
LOL
On Aug 4, 1:09 am, Jesse Stay jesses...@gmail.com wrote:
42
On Mon, Aug 3, 2009 at 6:57 PM, George Thiruvathukal
gthir...@gmail.comwrote:
[u...@cl-t090-563cl twitter]$ curl --basic --user UserName:Password -d
screen_name=SpammerJane http://twitter.com/blocks/create.xml
...
span style=font-size:1.8em; font-weight:boldSomething is
technically wrong./spanbr /
div style=font-size:1.2em;margin-top:
Hi all.
I'd like to have a go at creating a site in Dreamweaver similar to
Picfog - where it displays realtime streaming photos of Twitpic and
Yfrog images that have been posted in Tweets.
I'm not sure where to start on this - is there any code you can
recommend? Could this be done in
There are a lot of messages and details around saying that the REST
API is 150 per hour, with whitelisting up to 20k per hour. The Search
API is more than the 150, but no specifics.
Note that the Search API is not limited by the same 150 requests per hour
limit as the REST API.
The number
Re: http://apiwiki.twitter.com/Sign%20in%20with%20Twitter
Would it be practical to change oauth/authenticate, so it's less
challenging to a user who isn't logged in and hasn't authorized the
application? In this case, I'd prefer that the user see a single page
like oauth/authorize, which
Will Statuses/Replies be deprecated in the future (e.g. v2 of the
API?)
On Jul 27, 6:56 pm, Doug Williams d...@twitter.com wrote:
statuses/replies is an alias for statues/mentions. It is completely due to
history where mentions used to be called replies. Rather than break apps
that relied on
Hi All,
I've been reading the API documentation and this support group as well
but I can't find an answer, or a solution, to my problem.
I've been writing some js code using the Twitter API but every time I
perform a call I got back the error in subject: HTTP 400 Bad Request
and no response at
I hate to bump this as it were but does anyone have any insight?
Thanks,
Bob
On Tue, Aug 4, 2009 at 1:45 AM, Bob Fishelb...@bobforthejob.com wrote:
From the api documentation:
Because this method can be a vector for a brute force dictionary
attack to determine a user's password, it is
I had this idea at lunch today and figured I'd share it :)
Right now Twitter will shorten URLs by default and use bit.ly.
However, when you receive the content via the API (stream, search,
etc) you then have to expand the URL by doing a HTTP GET against the
bit.ly servers which causes them load
Hi Steve,
This system sounds like will work well. Your current numbers as stated
should stay within the rate limits. However, you should add logic to
your code which will increase the pause lengths programmatically
should you find that you are getting rate-limited responses.
Thanks,
-Chad
Hello,
Does anyone have a list of RT conventions they are using to track?
Right now, I am seeing:
- RT
- via
- HT (hat tip)
- c/o
Does anyone track anything else?
Thanks
Peter
cool, Thanks!
On Tue, Aug 4, 2009 at 3:30 PM, Chad Etzel c...@twitter.com wrote:
I would add:
Retweet[:]?
Retweeting[:]?
those aren't being used as often now, but I still see them around.
-Chad
On Tue, Aug 4, 2009 at 6:18 PM, Andrew Baderaand...@badera.us wrote:
Witty I think is
Here is what is happening. I am trying to create an app that runs on
my desktop. It does a friendships/destroy on people that have chosen
not to follow me and does a friendships/create on people who are
following me that I have yet to follow. This is supposed to be
similar to Twitter Karma.
I don't believe the consumer token/secret is linked to an ip address. I
don't remember supplying
it during application registration so twitter doesn't really know my ip
anyway. I'm guessing the access
tokens are linked to the IP address which they where issued. This would help
prevent access token
My guess is twitter has a limit on the number of friendship create/destroy
calls you can make with a certain period of time.
This would prevent bots or such from overloading twitter with too many
requests. The fact that you start getting 403 after a while
helps confirm there is a limit blocking
Does anyone know the limit to friendship create/destroy calls per
hour, per day, etc? There has to be a number out there somewhere. If
I knew this number than I could have a counter that stops once the
limit is reached.
Thanks,
Dan
Hello,
Today I started noticing a diference in tweets returned by search vs
their original versions. The difference is noticeable to me because I
combine both sources and I suddenly got a lot of duplicated entries
that were really slightly different. This started happenning today as
far as i can
There is a current issue where the Search API is omitting question
marks from search results. We're looking into it.
-Chad
On Wed, Aug 5, 2009 at 1:17 AM, TCIticoconid...@gmail.com wrote:
Hello,
Today I started noticing a diference in tweets returned by search vs
their original versions. The
27 matches
Mail list logo
