Re: [twitter-dev] Re: Rate limit HTTP response
Now the problem is different. The headers in the timeline request response headers have a limit set to 350, while the response to the get_rate_limit request still says 150... 2010/1/28 Michael Steuer mste...@gmail.com We see this too now on a bunch of our test accounts.. Does Twitter have a resolution time? It's making the use and development efforts of our application all but impossible... On Jan 28, 2010, at 1:51 PM, Rich wrote: Interesting my whitelisted account is still working, but the non whitelisted ones are broken over oAuth On Jan 28, 9:48 pm, Rich rhyl...@gmail.com wrote: Just run it through my debugger, it's absolutely returning an HTTP 400 response On Jan 28, 9:46 pm, Rich rhyl...@gmail.com wrote: Looks like they are in the process of upping the oAuth rate limit as now I'm getting different results but still a 400 error On Jan 28, 9:41 pm, Shelkie eshel...@gmail.com wrote: Are others having trouble with Ratelimits? Suddenly the X-Ratelimit-Limit has changed to 0 for several accounts I have checked. Here are some sample HTTP headers: [Date] = Thu, 28 Jan 2010 21:27:55 GMT [Server] = hi [X-Ratelimit-Limit] = 0 [Status] = 400 Bad Request [X-Ratelimit-Remaining] = 0 [X-Runtime] = 0.02640 [Content-Type] = application/json; charset=utf-8 [Content-Length] = 412 [X-Ratelimit-Class] = api_identified [Cache-Control] = no-cache, max-age=300 [X-Ratelimit-Reset] = 1264716226 Notice that X-Ratelimit-Reset is also out of date when compared to [Date] Any ideas? Could our app have been blacklisted for some reason, or is this a more widespread problem? Eric.
Re: [twitter-dev] Deleting a list...
looks like this bug : http://code.google.com/p/twitter-api/issues/detail?id=1239 twitter team keeps ignoring it's a blocking bug... 2010/1/19 Tunde Ashafa tunde.ash...@gmail.com I can't seem to get authenticated to perform a list destroy using OAuth with POST and _method=DELETE, within my app and using 'curl'. Anyone else experience this? Thanks in advance for any help, Tunde.
Re: [twitter-dev] Re: Twitter Oauth Issues
Yes actually a 10 minutes difference may be enough to break OAuth 2010/1/16 Mark McBride mmcbr...@twitter.com Is the system time on your machine correct? We've heard reports of issues when system clocks are wildly divergent from reality. ---Mark http://twitter.com/mccv On Fri, Jan 15, 2010 at 11:51 AM, Proxdeveloper prox.develo...@gmail.com wrote: Hey man, What do you mean by that ? On Jan 13, 6:59 pm, Andrew Badera and...@badera.us wrote: Server timestamp difference? ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Wed, Jan 13, 2010 at 4:16 PM, Proxdeveloper prox.develo...@gmail.com wrote: Hello folks, I'm developing atwitterdesktop client for windows using theOauthmethod, but for some reason I'm getting this error while requesting an Access token The remote server returned an error: (401) Unauthorized.. This issue is only happening in my development PC, I've tried the app in other computers and Internet Connections and it works great, I'm guessing this is happening because I make too much requests totwitter from the same computer. Could anyone help me on this issue ? Thanks.
Re: [twitter-dev] Re: Tweets with !, ', and other characters refused..
There must be an issue in the OAuth signature computing, which is why you are requested to provide your login again... 2010/1/14 thetwitmaniac alon.a.ta...@gmail.com We are using UTF-8 and still have this issue! Really can't understand why, all help would be greatly appreciated! On Dec 23 2009, 6:04 pm, Abraham Williams 4bra...@gmail.com wrote: Make sure you are properly encoding the characters before you send them to Twitter. Abraham On Tue, Dec 22, 2009 at 23:49, thetwitmaniac alon.a.ta...@gmail.com wrote: Hi, I'm building a desktop twitter client and for some reason whenever I try to post a tweet with an exclamation mark or apostrophe, the tweet is rejected and I am presented with a request to provide login credential for the Twitter API. Has anyone run into this issue or have any idea why this would occur? Thanks! -- Abraham Williams | Awesome Lists |http://awesomeli.st Project | Intersect |http://intersect.labs.poseurtech.com Hacker |http://abrah.am|http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] oAuth new stuff?
Yoono desktop application (and firefox add-on) is using OAuth too. 2009/12/30 Isaiah supp...@yourhead.com i understand that you have to tow the line. i agree with it — at least in principle. i like oauth. i understand it. i *want* to put it in my app. aside from my desktop client, i released an open source oAuth solution: http://thurly.net//5nl yet, of the prominent mac clients (tweetie, twitteriffic, socialite, beak, bluebird, kiwi) only one is currently using oAuth. the reasons are painfully obvious and have been discussed here and elsewhere ad nauseum: http://groups.google.com/group/twitter-development-talk/search?hl=engroup=twitter-development-talkq=oauth+desktopqt_g=Search+this+group i suspect that other desktop app devs feel like i do: that the announced oauth addendum was a sea change that looked like a realistic way forward. i was ready to hi-five the first person i saw when i read about it: http://groups.google.com/group/twitter-development-talk/msg/18b38db599f6ad98?hl=en i'm not asking for anything new or different from what has already been announced. i was just hoping for a bit more detail, that's all. isaiah On Dec 29, 2009, at 3:19 PM, Raffi Krikorian wrote: if your application has access to a web browser, then i would strongly suggest that you implement a workflow where your user goes to a twitter.com page -- this workflow is intended to protect the usernames and passwords of Twitter users because they can trust that an unknown app does not have access to their passwords. On Tue, Dec 29, 2009 at 2:31 PM, Isaiah Carew isa...@mac.com wrote: bummer. i don't mean to be rude, but it sure feels like there is a large gap between the PR announcement a couple weeks ago and the reality on the ground. i'm trying to be patient in letting the info trickle down. i guess i'll ask again in a couple weeks? twiddling thumbs waiting hmmm hmm hmmm until then, my app is limping along with basic auth without attribution. isaiah On Dec 29, 2009, at 1:30 PM, Raffi Krikorian wrote: i don't know. sorry that i forgot to address your question. On Tue, Dec 29, 2009 at 1:18 PM, Isaiah Carew isa...@mac.com wrote: and how 'bout that off topic question? a non-silent-treatment sort of answer would be really great -- even if it's i can't tell you or i don't know or that's on a need to know basis and you don't need to know. or you want the truth, you can't handle the truth! or whatever. my biggest concern is that it won't come before the deprecation of oAuth -- and I'll have to implement a pin bases solution in the interim, then rip that out, then implement the new flow if/when it's finally included in the twitter api. if that's the case, then i'm going to need to budget some more $$ for this effort. i'm just looking at what sort of effort and money i'm going to have to spend on this in the next six months. thanks, isaiah On Dec 29, 2009, at 1:06 PM, Raffi Krikorian wrote: Also, off topic: Any news on when we can expect the new oAuth with username/password flow to make its way into the API? If you can't let me know, or you don't know, I understand, but it would be good to hear whatever the case. Thanks, Isaiah -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
