Tom,
Yes, that code works perfectly for me exactly as is. You might want to
change the connect timeout from 10 to 30 seconds.
How long are you waiting before calling it quits? It does take a few
seconds for /track to start sending your results.
-Joel
On Sun, Aug 9, 2009 at 8:17 PM, Tom Fitzg
> I looked through the API, the online discussion, and wrote test code
> to check both the authorize and authenticate methods. I have not been
> able to find any difference between the two, apart from the request
> URL (and, perhaps, some differences in language between Twitter's
> authorize and
hi All,
here is the link - https://sourceforge.net/projects/twitter-to-pdf/
This does following:
1. incremental archival of user tweets(3200 at a time- due to
limitation set by twitter) into single/muliple HTMLs, Text and single
PDF per user.
2. round robin(based on last user tweet retrieved
While trying to post tweets from my iPhone app. i can do it easily by
basic authentication, but for oauth, i donot get any access token no
matter what.
My flow is like this
Set the consumer key and secret
Obtain request token
Use this request token to obtain access token
Obtain auth_req from
The difference between authenticate and authorize is that if the user is
already logged into Twitter and previously approved your application when
hitting the authenticate URL they will bounce directly back to your
application without seeing the allow prompt or any page from Twitter. With
authorize
I agree that this seems like a bug and added my thoughts to the issue
report.
Abraham
2009/8/9 Jeff Dairiki
>
> On Sun, Aug 09, 2009 at 03:50:44PM -0700, David Cramer wrote:
> >
> > So short story I've been changing our application from Read to Read/
> > Write access, and I cannot get it workin
Great! But unfortunately my Twitter client doesn't work still. :( I
can't log in.
I just started getting timeouts again. (the verify_credentials issue I
mentioned before never got fixed either)
Jesse
On Mon, Aug 10, 2009 at 1:54 AM, Vignesh wrote:
>
> 25% of my requests are still getting timed out..is there any rate
> limit in place?
>
> On Aug 9, 9:11 pm, Patrick wrote:
> >
Sorry (it's early and I'm tired), not timeouts - it's only allowing 150
requests per hour again.
Jesse
On Mon, Aug 10, 2009 at 4:47 AM, Jesse Stay wrote:
> I just started getting timeouts again. (the verify_credentials issue I
> mentioned before never got fixed either)
> Jesse
>
>
> On Mon, Aug
I am using the search API,
-- getting 409 conflict, once in a while.
-- getting "no json could be decoded" sometimes, I guess thats coz of
the HTML in response error.
JV
On Aug 9, 10:34 pm, Ryan Sarver wrote:
> I wanted to send an update to everyone who is monitoring this thread and
> keep you
what is the error that you are recieving when requesting your access
token? Are you sending the oauth_verifier parameter with that request
which should come back when the user authorises the app to access
their account.
On Aug 10, 7:41 am, SaraZaidi wrote:
> While trying to post tweets from my i
I am calling and getting the whole way up to getting the access token
just fine in my app (one im writing myself in c#), but when i try and
call the update status URL im getting an 'Invalid/used nonce' error in
my response data. Im not sure why this is, im calling the update
method in the exact sa
i basically have the same problem with ff 3.5 but it was working a
week or so ago. i have to logon via safari but i use firefox
predominantly so its a bit of a pain.
please tell me somebody is on it
The API is currently counting down X-RateLimit-Remaining using the
logic of 20k requests per hour per IP, not per user per IP.
That makes sense and I believe it is how it should work.
Dewald
On Aug 10, 2:17 am, Bob Fishel wrote:
> Since we have a lot of devs monitoring this now I'd like to bri
I think the twitter service is still down due to the DDOS attacks. Its
not allowing to register new applications. I am trying to make my
application work for the past 2 days now and without any success.
Fails during authentication. Some issue with the oauth module.
On Aug 10, 3:23 am, Eric wrot
i've been trying to post tweet from my client application, but it wont
allow access. The access tokens are always returned null. Somewhere
this morning, i read that Twitter no more allows registering new
applications, maybe this has something to do with the DDoS.
Whatever, my application is stuck
i think the reprecussions of the DDOS attack on twitter are still
prevailing. My application is still unable to access anything and i
cannot register my new application. Some issue with api limit and the
oauth module. The past 2 days have been frustrating for me. When will
twitter fix all issues?
i just read somewhere this morning that twitter is temporarily
blocking new applications from registering because of the DDoS issue.
Maybe this is the reason you are not being granted accessToken.
i was facing the same problem, but cant help it
--cheers
Lorriane ~*
On Aug 10, 4:18 pm, gracea
Yes, i am sending the oauth-verifier ... but still its of no help at
all :(
worried :(
Sara
On Aug 10, 4:18 pm, graceawalker wrote:
> what is the error that you are recieving when requesting your access
> token? Are you sending the oauth_verifier parameter with that request
> which should com
take the URL that it is producing to request the access token in your
web client, put it into your internet explorer and paste the xml
returned into here...
On Aug 10, 1:31 pm, SaraZaidi wrote:
> Yes, i am sending the oauth-verifier ... but still its of no help at
> all :(
>
> worried :(
> Sara
I am seeing tons of requests that return 200 OK plus the expected JSON
data, but the headers have no X-RateLimit entries.
Dewald
Sultan,
All functionality should have been restored on Sunday before noon, but
various actions may be slow and sometimes time out.
Have you read:
http://groups.google.com/group/twitter-development-talk/browse_frm/thread/3ada5cc250fbe256
?
Please retest your app and send a...@twitter.com detail
You can always recommend your friends use the "Filter this column" feature
of TweetDeck. Not the best solution for your exact scenario, but at least
it's something.
You also may want to take a look at a product that my team recently
developed called TidyTweet (http://tidytweet.com). It allows e
Just to let you guys know that 502 Bad Gateway responses are coming
thick and fast this morning (Monday).
Dewald
I don't work on the API team, and normally don't respond to REST API
questions, so please bear with any inaccuracies:
I haven't heard anything about Twitter explicitly turning application
registration off. I believe that all parts of Twitter.com should be
working correctly -- albeit sometimes slo
Why am I getting this! Not sure it's for me
On Mon, Aug 10, 2009 at 10:29 AM, John Kalucki wrote:
>
> I don't work on the API team, and normally don't respond to REST API
> questions, so please bear with any inaccuracies:
>
> I haven't heard anything about Twitter explicitly turning application
Since we're pimping our stuff... :)
Quitter is a quiet little Twitter client for Windows that provides
filtering.
- You can filter specific hashtags
- You can filter specific users (doesn't block - just hides their
tweets in Quitter)
- You can filter specific words
Conversely, you can also choos
Timmy!
On Mon, Aug 10, 2009 at 10:41 AM, timothy willan wrote:
> Why am I getting this! Not sure it's for me
>
>
> On Mon, Aug 10, 2009 at 10:29 AM, John Kalucki wrote:
>
>>
>> I don't work on the API team, and normally don't respond to REST API
>> questions, so please bear with any inaccuracie
Hi there !
i'm trying to configure a twitter scheduled script and i having
problem to send accented char !
I know that i have to encode and utf8 encode before sending, and I do
it :
$status = urlencode(utf8_encode($status));
my request :
http://twitter.com/statuses/update
I'm using curl
The pro
I am still getting
"HTTP Error 409: Conflict"
from the search API, once every 15mins on an average.
JV
On Aug 10, 12:13 am, Ryan Sarver wrote:
> *Finally* have what we hope is good news for everyone. As of about 10
> minutes ago we have been able to restore critical parts of API operation
> th
Hello Ryan I'm timothy not surwe why I'm receiving all twitter Development
emails, let me know Thanks
On Sun, Aug 9, 2009 at 3:13 PM, Ryan Sarver wrote:
> *Finally* have what we hope is good news for everyone. As of about 10
> minutes ago we have been able to restore critical parts of API operat
I'm still having API issues
On Aug 10, 10:11 am, John Kalucki wrote:
> Sultan,
>
> All functionality should have been restored on Sunday before noon, but
> various actions may be slow and sometimes time out.
>
> Have you
> read:http://groups.google.com/group/twitter-development-talk/browse_frm/
most likely because you subscribed to the group
you can go to http://groups.google.com/group/twitter-development-talk/ to
manage your subscription status
Marco
2009/8/10 timothy willan
> Hello Ryan I'm timothy not surwe why I'm receiving all twitter Development
> emails, let me know Thanks
>
>
you're obviously subscribed to the group. either you subscribed or someone
did for you. log in to groups.google.com and unsubscribe.
On Mon, Aug 10, 2009 at 08:59, timothy willan wrote:
> Hello Ryan I'm timothy not surwe why I'm receiving all twitter Development
> emails, let me know Thanks
>
> O
My users are seeing these as well.
On Aug 10, 10:22 am, Dewald Pretorius wrote:
> Just to let you guys know that 502 Bad Gateway responses are coming
> thick and fast this morning (Monday).
>
> Dewald
Can you all provide full packet dumps of the issues you are seeing? That
will help us debug the type of request you are making and what the full
response looks like.
Thanks, Ryan
On Mon, Aug 10, 2009 at 8:15 AM, Duane Roelands wrote:
>
> My users are seeing these as well.
>
> On Aug 10, 10:22 am,
Abraham, thanks for a quick reply...
I see what you are saying...
Here is my follow up question - if my user have been previously
authenticated, and I now have the access token and secret, why would I
use the "authenticate" call vs. just using the "view credentials"
call? In other words, by usi
Duane,
I posted it in another thread, but can you please provide full packet dumps
of the issues you are seeing? Also, please provide more detail around what
API you are calling, how many times an hour and
the exact issue you are seeing.
Thanks, Ryan
On Mon, Aug 10, 2009 at 8:02 AM, Duane Roeland
Ryan,
The 502s don't really bother me. It just slows me down a bit. My
Twitter lib automatically retries a request that 502'd.
The 200 OK responses that come back with the X-RateLimit headers
missing happen on all kinds of requests, both GETs and POSTs (more on
GETs as far as I can tell), and as
Hello twitter developers:
Just posting here to announce a library for python I have been putting
together.
It supports pretty much the entire twitter API's endpoints. This includes
the search
and streaming APIs. The library also works fine with OAuth authentication.
I have the library hosted here
I'd like to thank those of you who have released your own APIs for the
apps you've built on top of Twitter. If you're using Ruby, we've
bundled up our wrappers for many of them into a new gem called
TwitterLand. Please check it out and let us know if you'd like to see
new APIs added or fork us on
Does the API team have a "test third-party app", from where you can
experience and test the API from a consumer's perspective?
If not, I think it may be helpful to you to have something like that.
You don't need to run it at full stress all the time.
When you roll out a mod to the API, or at tim
Thanks Dewald. Generally speaking if you see a 502/503 you should do a
geometric back off instead of just immediately re-requesting.
Is anyone else seeing the X-RateLimit header not showing up some times?
Thanks, Ryan
On Mon, Aug 10, 2009 at 8:35 AM, Dewald Pretorius wrote:
>
> Ryan,
>
> The 50
I'm getting the same response. All weekend, I chalked it up to being an
issue during recovery of the systems, but I'm still seeing it this morning
on 100% of my calls. It was working before the attack.
401:Authentication credentials were missing or incorrect.
/followers/ids.xml Invalid / used n
I began to use twitter one year ago. I have been posted statuses no
less than 3000, but today I found my statuses count become 84! Then I
go to twitter homepage to see my statuses, I can only see 84
statuses. why does this happend? Can I have my missing statuses
again?
Wanted to send out a status update and let everyone know where the situation
stands as of today at noon.
- Most developers are reporting being back in operation as of noon on Sunday
- We have changed our defenses to make sure API developers are better
supported. As such the system has more general
2009/8/10 sasha
> Here is my follow up question - if my user have been previously
> authenticated, and I now have the access token and secret, why would I
> use the "authenticate" call vs. just using the "view credentials"
> call? In other words, by using "view credentials" I am just making
> su
On Aug 10, 3:57 pm, Ryan Sarver wrote:
> As such the system has more general strain on it and thus will
> produce some more 502/503 errors. If you see them, you should do a geometric
> back off instead of just sending a new request.
Ryan,
What starting value and what common ratio of a geometric
All,
I don't want to kick this subject to death, as there was a lengthy
thread on general OAuth vs. Basic auth -- I want to restrict this
question strictly to the scope of iPhone apps. Having pored over the
OAuth vs. Basic authentication process, I have a question, given the
following as
Twitter recently started suspending accounts which bulk unfollow those
who don't follow back for Terms of Service Violation (see:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/1aeb1f40ff665f78/955da80afd36ca4d?lnk=gst&q=follower+churn#955da80afd36ca4d).
This policy h
Hi,
For a last month, I collected followers of social graph API (http://
apiwiki.twitter.com/Twitter-REST-API-Method:-followers%C2%A0ids).
By examining a log file, I faced a very long user id.
I found that these ids seldom appear and not consistently appear for
even the same user.
For example, i
Interesting. Can you please create an issue at:
http://code.google.com/p/twitter-api/issues/list
so we can track this?
Thanks,
-Chad
On Mon, Aug 10, 2009 at 4:59 PM, Haewoon wrote:
>
> Hi,
>
> For a last month, I collected followers of social graph API (http://
> apiwiki.twitter.com/Twitter-RE
> What are the specific rules regarding the type, quantity, and timing
> of bulk unfollowing that will result in account suspension? It's very
> difficult to manage twitter accounts with the specter of seemingly
> arbitrary account suspensions looming without having more specific
> guidance on ho
Yes, I am also having x-ratelimit not show up after I have received
"OK: 200" errors.
I believe this is due to timeout issues.
Specifically, I often find that I am returned partial JSON (lack of
closing syntax) without the ratelimit header, e.g.:
'_rc' => 200,
'_headers' => bless( {
'connectio
On Mon, Aug 10, 2009 at 3:36 PM, Dewald Pretorius wrote:
>
> On Aug 10, 3:57 pm, Ryan Sarver wrote:
> > As such the system has more general strain on it and thus will
> > produce some more 502/503 errors. If you see them, you should do a
> geometric
> > back off instead of just sending a new req
Dewald,
Respectfully, I must (now) disagree that rate limiting should not be
per user, i.e., that it *SHOULD* be per user based.
When my site, twxlate.com, was white-listed and I saw how the white-
listing worked, namely that for authenticated requests each user of
each white-listed IP address g
On Aug 10, 11:02 pm, "jim.renkel" wrote:
> My logic is now: "If rate limiting is not per user, then all users of
> an IP address will share one pool of 20k requests per hour. If a site
> has a 1,000 users at one time, then each user will get an average of
> 20 requests per hour. This is clearly n
On Mon, 10 Aug 2009 04:14:43 -0700 (PDT)
graceawalker wrote:
> I am calling and getting the whole way up to getting the access token
> just fine in my app (one im writing myself in c#), but when i try and
> call the update status URL im getting an 'Invalid/used nonce' error in
> my response data
Yup, when you do back-offs, ya can't do them deterministically, ya
gotta do them for a random amount, generally uniformly distributed
between some upper and lower bounds.
It's the bounds that increase geometrically or exponentially, up to
some limit, but the each back-off should be random between
If you're coding in PHP then it is extremely easy to switch IP
addresses in your scripts. You simply set the IP address from where
the call is made with CURLOPT_INTERFACE, provided that your different
IP addresses are on the same server.
There are two ways you can control your 20,000 per hour rat
Hmmm! We seem to have conflicting evidence here!
I just (again) verified that twxlate.com is getting 20k requests per
hour per user.
How long ago was it that Alex and other API team members made the
recommendation that you mentioned? Is it possible that twitter changed
policy since then?
Either
Jim,
I don't know exactly what you're looking at and how you get to that
answer.
My system is making thousands of GET calls per hour, and I can see how
X-RateLimit-Remaining is decrementing regardless of which Twitter user
credentials are used.
So, on my side I am seeing solid evidence that the
On Aug 10, 8:15 pm, Cameron Kaiser wrote:
> As soon as you do that, the naughties will set up their software to do just
> that, -1, to keep them just under the limit.
Amen.
Besides, I wish people would realize that Twitter is actually about
what you can learn from the people you follow. It is n
what is troublesome about your post is that you highlight the possible
favoritism that Twitter has. Could you provide some details on the
number of followers your friends unfollowed when they got suspended,
and what method they used to do the unfollow? It looks like Scoble
unfollowed 106,000 peo
On Mon, 10 Aug 2009 08:02:33 -0700 (PDT)
sasha wrote:
> All in all, I agree with Chris - ideally, access and authentication
> should be very distinct. Twitter Oauth is still a step in the right
> direction vs. basic HTTP auth, but would be nice to have a strictly
> authentication-based call tha
> As soon as you do that, the naughties will set up their software to do just
> that, -1, to keep them just under the limit.
That would be fine since anything under the limit is, by definition,
not "naughty".
A fundamental principal of well ordered societies is having
transparent rules. Imagine
Doug,
Can you specify what constitutes a PATTERN of following and
unfollowing (in terms of the number of follows/unfollows per day, the
nature of the accounts unfollowed such as whether they follow back or
not, etc.)? I am aware of accounts that were suspended for
"restarting" by removing all th
Can someone post a link to some online resources explaining more about
geometric back-offs? Did a search, did not find a whole lot.
Thx
Sven
On Aug 10, 7:18 pm, "jim.renkel" wrote:
> Yup, when you do back-offs, ya can't do them deterministically, ya
> gotta do them for a random amount, generall
I believe sometimes the IP address can be user-based, even for white-
listed IPs. E.G., if the user himself has a whitelisted IP.
On Aug 10, 7:57 pm, Dewald Pretorius wrote:
> Jim,
>
> I don't know exactly what you're looking at and how you get to that
> answer.
>
> My system is making thousan
On Mon, 10 Aug 2009 22:01:16 -0700 (PDT)
hansamann wrote:
> Can someone post a link to some online resources explaining more about
> geometric back-offs? Did a search, did not find a whole lot.
Retry intervals grow in a geometric progression:
http://en.wikipedia.org/wiki/Geometric_progression
Come on.
For its auto-follow, tweetlater.com specifically states: "[w]e have
limits in place to ensure that your daily following remains well
within the limits imposed by Twitter." So you are presumably touching
the rate limit then going back -1, -2, -3, or whatever. How is that
different than
Just wanted to report that we are back up and running for the most
part as well, BUT quite a number of our servers are still experiencing
some BlackOut periods where twitter fails to respond and connections
time out. They seem to last about 5-10 minutes each. We are running
quite a few s
72 matches
Mail list logo
