Great news, can't wait to start learning about it, and implementing it
in Hahlo. A PHP example, even a very basic one, would be very much
appreciated as I've never worked with OAuth before. Looking forward to
hearing more details in the next week or so.
thanks
Dean
Hey all:
So, I had been racking my brain as to why my user update code wasn't
working right. Basically, I was getting double entries for screen
names. It took me a while, but I figured out what the issue is.
Basically, the twitter API method: users/show/id.format, looks up the
screen_name field b
I guess this could have been clearer but I ran almost 3000 authenticated
requests and the rate_limit_status counted fine so it is probable that it
will count fin into the 20k range.
On Sun, Feb 8, 2009 at 02:11, Abraham Williams <4bra...@gmail.com> wrote:
> I've not tested in the 20k range but it
Oops, my bad, I have a .curlrc in place that authenticate it.
Unauthenticated it doesn't seem to be counting down. Alex: possible
bug?
-Stuart
2009/2/8 Stuart :
> Here's a crazy thought... try it!!
>
> Here's what the rate_limit_status shows unauthenticated from my dev
> server just now...
>
> s
Here's a crazy thought... try it!!
Here's what the rate_limit_status shows unauthenticated from my dev
server just now...
stu...@dev:~$ curl http://twitter.com/account/rate_limit_status.xml
2
2009-02-08T11:03:45+00:00
1234091025
19425
-Stuart
2009/2/8 Jesse Stay :
> I'm sorry fo
I'm sorry for wasting your time, Abraham. I'll be more specific next time.
That still doesn't answer my question though as to whether there is a
method to get my used-up requests within the new 20k/hour rate limit.
Alex?
On Sun, Feb 8, 2009 at 1:11 AM, Abraham Williams <4bra...@gmail.com> wrote:
I've not tested in the 20k range but it counts into the 2k range. So you
should be fine.
Also for future reference if you are looking for answer A don't ask question
B. Ask question A. The bit bit about working in the 20k range was a key part
of the original question and it was not included.
On S
