[twitter-dev] Re: Getting 401 when using one access token with OAuth
Thanks for this response, Taylor. Turns out I was making a noob mistake and it's all squared away. Your trouble shooting tips helped me find that mistake. ~Barry On May 17, 9:58 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Barry, Unfortunately can't go to the logs to figure out what's going wrong -- but happy to help. You don't need xAuth access to get this to work, you are correct. There may be other reasons it is failing for you. One thing to check is that your system clock is synced with a NTP server or reasonably correct -- if the timestamp generated by the OAuth flow doesn't match ours within about 5 minutes, you'll get an invalid request. As for the example: just dotting i's: you've placed your consumer key and secret on line 3 of the example and your oauth_token and oauth_token_secret (access token) on the method call for prepare_access_token? Assuming all is correct, this part should function. After you've checked your clock and if you're still having issues I'll help you debug this further. Thanks, Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Mon, May 17, 2010 at 7:35 AM, bjhess ba...@bjhess.com wrote: I'm not 100% sure that applies. I've been told by Twitter support that I should not be using xAuth. Twitter - any help here? ~Barry On May 15, 8:23 am, @sebagomez sebastiangomezcor...@gmail.com wrote: Take a look in this post at the suggestion Taylor sent me. http://groups.google.com/group/twitter-development-talk/browse_thread... regards On May 14, 5:48 pm, bjhess ba...@bjhess.com wrote: I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test. Both have been set up with an OAuth key and secret. I'm essentially using the identical code to your sample. I contacted Twitter support seeking xAuth access, thinking that was what was leading me to the 401. They've sent me here. Anything you'd like me to share from how I'm calling Twitter would be beneficial. Hopefully you can see my failures in your logs from yesterday, though. Thanks! ~Barry Hesshttp://www.getharvest.com
[twitter-dev] Re: Getting 401 when using one access token with OAuth
I'm not 100% sure that applies. I've been told by Twitter support that I should not be using xAuth. Twitter - any help here? ~Barry On May 15, 8:23 am, @sebagomez sebastiangomezcor...@gmail.com wrote: Take a look in this post at the suggestion Taylor sent me. http://groups.google.com/group/twitter-development-talk/browse_thread... regards On May 14, 5:48 pm, bjhess ba...@bjhess.com wrote: I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test. Both have been set up with an OAuth key and secret. I'm essentially using the identical code to your sample. I contacted Twitter support seeking xAuth access, thinking that was what was leading me to the 401. They've sent me here. Anything you'd like me to share from how I'm calling Twitter would be beneficial. Hopefully you can see my failures in your logs from yesterday, though. Thanks! ~Barry Hesshttp://www.getharvest.com
[twitter-dev] Getting 401 when using one access token with OAuth
I'm trying to implement the following in Ruby: http://dev.twitter.com/pages/oauth_single_token Unfortunately I'm receiving 401's from to Twitter usernames, harvest and harvest_test. Both have been set up with an OAuth key and secret. I'm essentially using the identical code to your sample. I contacted Twitter support seeking xAuth access, thinking that was what was leading me to the 401. They've sent me here. Anything you'd like me to share from how I'm calling Twitter would be beneficial. Hopefully you can see my failures in your logs from yesterday, though. Thanks! ~Barry Hess http://www.getharvest.com
[twitter-dev] Re: Upcoming changes to the way status IDs are sequenced
+1 on IDs being increasing. Sequential doesn't matter to me. I don't actually trust passing since_id to Twitter and having them handle the limiting of my result list. I've gotten into trouble when that feature suddenly quit being recognized and my code wasn't defensive enough to double-check since_id. With that fear in mind, increasing IDs are a must. I'm assuming the direct message ID algorithm will remain unchanged? Thanks, ~Barry http://bjhess.com http://getHarvest.com To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Search problems for from:username searches
We have had some users complain about not being able to find themselves on http://followcost.com. I've dug into the code and it appears the failure is happening on queries to the search API of the form from:username. A couple example queries that return zero results: http://search.twitter.com/search.json?q=from%3A1918 http://search.twitter.com/search.json?q=from%3Athecurrent Yet clearly these users are active, and legitimate, Twitter users: http://twitter.com/1918 http://twitter.com/thecurrent But sadly, is it that these users are not being indexed at all in the search DB? I get zero results doing a simple from:username search for the same users: http://search.twitter.com/search?q=from%3A1918 http://search.twitter.com/search?q=from%3Athecurrent These are just a couple examples. Is it common for legitimate, upstanding Twitter users to be unindexed in the search DB? -- Barry Hess http://followcost.com http://bjhess.com
[twitter-dev] Re: direct_messages since_id parameter doesn't work
Ditto here. Note to self, never trust since_id in the Twitter API. This has burned me before. It really burned me this time. -- Barry http://iridesco.com http://bjhess.com On Mar 30, 2:06 pm, Doug Williams d...@twitter.com wrote: Ben, I can see the same problem. There is now an open issue for this problem [1]. 1.http://code.google.com/p/twitter-api/issues/detail?id=399 Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 11:56 AM, Ben Burleson ben.burle...@gmail.comwrote: I use this URL: http://twitter.com/direct_messages.xml?since_id=82528092 The result includes the message with that ID (when it should only include messages AFTER that ID) AND previous messages. This is very broken. Should I abandon it and just use the since parameter (as date)? If so, fix the API doc!!!1 Cheers, Ben
[twitter-dev] Re: direct_messages since_id parameter doesn't work
Wondering if you possibly broke some sort of ActiveResource (Rails) compatibility here? My call, which worked just fine this morning and the past 12 months, now fails with a 400 Bad Request. DirectMessage.find(:all) Thanks, -- Barry http://iridesco.com http://bjhess.com On Mar 30, 2:13 pm, Doug Williams d...@twitter.com wrote: All, This is being looked into as I type. Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 12:09 PM, bjhess bjh...@gmail.com wrote: Ditto here. Note to self, never trust since_id in the Twitter API. This has burned me before. It really burned me this time. -- Barry http://iridesco.com http://bjhess.com On Mar 30, 2:06 pm, Doug Williams d...@twitter.com wrote: Ben, I can see the same problem. There is now an open issue for this problem [1]. 1.http://code.google.com/p/twitter-api/issues/detail?id=399 Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 11:56 AM, Ben Burleson ben.burle...@gmail.com wrote: I use this URL: http://twitter.com/direct_messages.xml?since_id=82528092 The result includes the message with that ID (when it should only include messages AFTER that ID) AND previous messages. This is very broken. Should I abandon it and just use the since parameter (as date)? If so, fix the API doc!!!1 Cheers, Ben
[twitter-dev] Re: direct_messages since_id parameter doesn't work
Nevermind … rate limit. ~Barry On Mar 30, 3:06 pm, bjhess bjh...@gmail.com wrote: Wondering if you possibly broke some sort of ActiveResource (Rails) compatibility here? My call, which worked just fine this morning and the past 12 months, now fails with a 400 Bad Request. DirectMessage.find(:all) Thanks, -- Barryhttp://iridesco.comhttp://bjhess.com On Mar 30, 2:13 pm, Doug Williams d...@twitter.com wrote: All, This is being looked into as I type. Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 12:09 PM, bjhess bjh...@gmail.com wrote: Ditto here. Note to self, never trust since_id in the Twitter API. This has burned me before. It really burned me this time. -- Barry http://iridesco.com http://bjhess.com On Mar 30, 2:06 pm, Doug Williams d...@twitter.com wrote: Ben, I can see the same problem. There is now an open issue for this problem [1]. 1.http://code.google.com/p/twitter-api/issues/detail?id=399 Thanks, Doug Williams Twitter API Supporthttp://twitter.com/dougw On Mon, Mar 30, 2009 at 11:56 AM, Ben Burleson ben.burle...@gmail.com wrote: I use this URL: http://twitter.com/direct_messages.xml?since_id=82528092 The result includes the message with that ID (when it should only include messages AFTER that ID) AND previous messages. This is very broken. Should I abandon it and just use the since parameter (as date)? If so, fix the API doc!!!1 Cheers, Ben
Re: Change to Twitter API?
I am no longer seeing created_at in the returned user record for http://twitter.com/users/show/id.xml. Naturally, this has broken Follow Cost. :( Thanks, -- Barry http://followcost.com On Dec 10, 7:39 pm, Alex Payne [EMAIL PROTECTED] wrote: Looking into this one further... On Wed, Dec 10, 2008 at 17:21, itcn [EMAIL PROTECTED] wrote: Still the same problem; the XML version of the API no longer seems to be returning the full data. It never made sense that this would be a cache issue; beacuse this should return new data every time we request the XML file; what good is data that is 24 hours old? On Dec 10, 12:23 pm, Alex Payne [EMAIL PROTECTED] wrote: The fix was deployed yesterday, about 17 hours ago. Any incorrect responses are just cached data that will be evicted over time. Nothing should live in the cache longer than 24 hours, so all should be correct within the next 7 hours. On Wed, Dec 10, 2008 at 08:22, itcn [EMAIL PROTECTED] wrote: Is there any ETA on when this bug will be fixed? On Dec 9, 5:59 pm, Alex Payne [EMAIL PROTECTED] wrote: This is a temporary issue. On Tue, Dec 9, 2008 at 14:47, itcn [EMAIL PROTECTED] wrote: This used to work for unauthenticated users to display statuses_count and now it doesn't: http://twitter.com/users/show/(screen_name).xml Any reason this was changed recently? Is there another way to access a user's status count (preferably without requiring the user's authentication)? -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x-Hide quoted text - - Show quoted text - -- Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
follow cost
Hi, Luke Francl and I just released follow cost [1] yesterday. We built it with all-unauthenticated calls to the Twitter and Twitter Search API's. Our understanding, based on the docs, was that these calls are not rate limited. Yet to be good stewards, we cache our results pages for 24 hours. So we are at a theoretical limit of one set of calls to Twitter per user per day. Unfortunately it turns out there is a rate limit for unauthenticated calls - by IP I imagine. Would it be possible to get follow cost whitelisted? We can authenticate our calls (for tracking) if need be. TIA for any help you can provide, ~Barry [1] http://followcost.com
Re: follow cost
Thanks! ~Barry On Oct 14, 10:39 am, Abraham Williams [EMAIL PROTECTED] wrote: http://twitter.com/help/request_whitelisting On Tue, Oct 14, 2008 at 10:12, bjhess [EMAIL PROTECTED] wrote: Hi, Luke Francl and I just released follow cost [1] yesterday. We built it with all-unauthenticated calls to the Twitter and Twitter Search API's. Our understanding, based on the docs, was that these calls are not rate limited. Yet to be good stewards, we cache our results pages for 24 hours. So we are at a theoretical limit of one set of calls to Twitter per user per day. Unfortunately it turns out there is a rate limit for unauthenticated calls - by IP I imagine. Would it be possible to get follow cost whitelisted? We can authenticate our calls (for tracking) if need be. TIA for any help you can provide, ~Barry [1]http://followcost.com -- | Abraham Williams | Web Developer |http://abrah.am | PoseurTech LLC | Mashup Ambassador |http://poseurte.ch | Web608 | Community Evangelist |http://web608.org | This email is: [] blogable [x] ask first [] private
