Hey guys,
maybe this question has been asked before, but I just joined the
group. I just ran into a little problem that threw me off. I'm
developing a website that uses the REST API extensively. The
documentation says that anonymous requests get limited to 150 requests/
hour/IP and authenticated
Hey Alin,
What do you mean by *I authenticated, verified the credentials and **
queried*? In this context (API call) authenticating means signing your
request using OAuth. Signing-in with your account on twitter.com is a
completely different thing and has no effect on your API requests.
Arnaud /
How do this work because i'm new to this?
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
Hi everybody,
Hopefully this question hasn't been asked a million times already and
I was just searching for it badly, but here goes.
I played around with the twitter API back in basic authentication
days, and I was asked by a friend to put something together for him.
In the old days it would
It's actually very simple.
1. Download Abraham's TwitterOAuth from
https://github.com/abraham/twitteroauth
2. Get API keys from http://dev.twitter.com/
3. Open a new .php file, include and initialize TwitterOAuth:
$connection = new TwitterOAuth('consumer key', 'consumer secret', 'user
key',
If you need a step by step tutorial on doing this with PHP, and want
something that shows you exactly where to get the right OAuth keys and
use them in the code, you can try this tutorial:
http://140dev.com/twitter-api-programming-tutorials/hello-twitter-oauth-php/
The sample code uses Matt
I don't know if you already ran across this but I too am a newbie to Twitter
API.
I was just using this to test twitter post from processing.
It shows how to setup Twitter app to get 0Auth keys - you can use the
wordprayr twitter account as the app.
I'm confused about the OAuth docs linked to from http://apiwiki.twitter.com/
-- especially these:
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-oauth-request_token
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-oauth-access_token
Both of these link to the OAuth 1.0 spec for a list
If you look at the very top of the 1.0 spec, you will see a yellow box...
This specification was obsoleted by OAuth Core 1.0 Revision
Ahttp://oauth.net/core/1.0a on
June 24th, 2009 to address a session fixation
attackhttp://oauth.net/advisories/2009-1/.
The OAuth Core 1.0 Revision A specification
Yup, I know, that's what I'm asking. Why not link to and tell people to use
1.0a (or the IETF draft) rather than 1.0?
For the record I checked all the other code examples and none of them support
oauth_verifier (some do send oauth_callback with the first request), unless I'm
missing something.
most likely, Twitter has other things to do and updating the API
documentation isn't very high on the list.
Ryan
On Fri, Jan 22, 2010 at 4:40 PM, Marc Hedlund marcprecip...@gmail.comwrote:
Yup, I know, that's what I'm asking. Why not link to and tell people to use
1.0a (or the IETF draft)
http://github.com/abraham/twitteroauth/ supports oauth_varifier.
Abraham
On Fri, Jan 22, 2010 at 13:40, Marc Hedlund marcprecip...@gmail.com wrote:
Yup, I know, that's what I'm asking. Why not link to and tell people to use
1.0a (or the IETF draft) rather than 1.0?
For the record I checked
Ah, sorry, my mistake.
-M
On Jan 22, 2010, at 1:57 PM, Abraham Williams wrote:
http://github.com/abraham/twitteroauth/ supports oauth_varifier.
Abraham
On Fri, Jan 22, 2010 at 13:40, Marc Hedlund marcprecip...@gmail.com wrote:
Yup, I know, that's what I'm asking. Why not link to and
13 matches
Mail list logo
