[twitter-dev] Whitelisting and Oauth
Apologies if this question does not make sense. I have a whitelisted account. If I want to make use of the extra API calls, I understand that I must either issue the request from a whitelisted IP address or by authenticating using my approved ID. When I try to use the friends/ids api call as follows http://api.twitter.com/1/friends/ids.json?user_id=OTHER_ID&oauth_nonce=009798&oauth_timestamp=33482&oauth_consumer_key=&oauth_signature_method=HMAC-SHA1&oauth_version=1.0&oauth_token=XXX&user=MYID&oauth_signature=XXX I get the friends/ids information for MYID. I want to get the information for OTHER_ID. How can I correct this mistake ? I would highly appreciate any suggestions. -Ram -- Ramanathan Narayanan Dept. of EECS Northwestern University Evanston IL -- 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: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Question about Authentication/Whitelisting and friends/ids
Hello, I have a whitelisted account. I was under the assumption that I can use either a assigned IP address or authentication in order to make use of the 20,000 API calls per hour. Earlier I used to authenticate using basic authentication and issue a API call from a machine different from my whitelisted IP, and I was able to make that count against my whitelisted account. When I switched to oauth, I have a problem with the friends/ids call. Specifically , when I issue a API call to friends/ids using oauth, I specify the user_id parameter. Now my problem is that this API call returns the friends/ids list for my oauth authenticated user id, and not for the user_id for which I want the friends/ids. Is there a simple solution to this problem. -Ram -- Ramanathan Narayanan Dept. of EECS Northwestern University Evanston IL -- 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: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Introduce yourself!
Hi, I am Ramanathan Narayanan, a graduate student at Northwestern University. I do research in machine learning and text mining. I am interested in finding influential users on twitter for different trending topics. I am also trying to find similar trending topics, and sentiments in tweets. My goal is to devise efficient algorithms and tools to solve these problems. A website based on my work is Pulse of the Tweeters (http:// pulseofthetweeters.com/) . Any feedback about the site is welcome. -Ram On May 16, 10:37 pm, Jonathan wrote: > I'm Jonathan Sachs, and I'm working with a company named Kachingle > (http://www.kachingle.com) that's building a new type of service for > letting users give financial support to the web sites they visit. We > want to use Twitter to keep our member sites and users aware of each > others' activities. > > I've spent about half of my career doing programming, and the other > half doing technical writing. (I'm a big believer in documentation, > and in software design for usability.) I'currently do most of my > programming in PHP, with a little Javascript thrown in. My past > activities have encompassed Java, C++, C, Visual Basic for > Applications, FORTH, PL/I, FORTRAN IV, SNOBOL3, and IBM Basic Assembly > Language. Among other things. > > I'm currently wrestling with the latest (I think) version of Abraham's > implementation of the API, trying to make it do the things that an > older version did.
[twitter-dev] Re: OAuth change at Twitter?
I am having the same problem since yesterday. I have made no changes to my code, but I am getting a 502 error. -Ram On May 19, 9:18 am, Taylor Singletary wrote: > Hi Dossy, > > This is more likely load related than anything else. We've made some > adjustments recently to how we treat requests that are taking a long time -- > they now tend to time out a lot sooner and provide an error rather than run > with a long duration. This problem should lighten when the load lightens, > and we're meanwhile working on improving the situation for everyone. > > Taylor Singletary > Developer Advocate, Twitterhttp://twitter.com/episod > > On Wed, May 19, 2010 at 6:59 AM, Dossy Shiobara wrote: > > Did a change to Twitter's OAuth get deployed very recently (i.e., > > yesterday or today)? > > > I'm now getting "Failed to validate oauth signature and token" in > > response to OAuth requests - I can guarantee my code, that has been > > working for many months now, has not changed. > > > Is anyone else seeing this, right now? > > > -- > > Dossy Shiobara | do...@panoptic.com |http://dossy.org/ > > Panoptic Computer Network |http://panoptic.com/ > > "He realized the fastest way to change is to laugh at your own > > folly -- then you can let go and quickly move on." (p. 70)
