Re: [twitter-dev] Incorrect signature while getting user time line
I didn't get a proper solution. Anybody please help me. Regards, George On Thu, Dec 16, 2010 at 7:11 PM, Georgooty varghese georgo...@gmail.comwrote: Ok. Thanks Tom. What wrong I have made in this. I didn't find any issue. Could u please check the issue. I am waiting for your reply. Regards, George On Thu, Dec 16, 2010 at 1:58 PM, Tom van der Woerdt i...@tvdw.eu wrote: They look fine, and since the rest of the requests work fine (which you said), I have to assume that it's not the signature generation. Also, since you're not the only one to mention this in the past 12 hours, I have to leave open the possibility of Twitter being the issue. However, before looking at that, please double check that the Base String matches what you are actually doing! Tom On 12/16/10 7:25 AM, Georgooty varghese wrote: Thanks twitter for your quick reply. I have make only one modification into my code. Other code changes do only when I get your reply. I have changed url for user time line http to https. Here I have copied my user time line base url and signature and base string. Please suggest to me a correct way for this. *Base URL* :oauth_consumer_key=*oauth_nonce=EF2k_xwovJInFfqoauth_signature_method=HMAC-SHA1oauth_timestamp=1292480095oauth_token=*oauth_version=1.0page=1screen_name=Sanoop_SP * Signature*:FcKenujneOtQklp6HZYDkRc7BYzelW9Fsadj324REpV1owATZgqcsx3R6FaM0qGilyBRkkP95zwNVosGoSnc *Base string*:GEThttps%3A%2F%2Fapi.twitter.com http://2Fapi.twitter.com %2F1%2Fstatuses%2Fuser_timeline.jsonoauth_consumer_key%%26oauth_nonce%3DEF2k_xwovJInFfq%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1292480095%26oauth_token%**%26oauth_version%3D1.0%26page%3D1%26screen_name%3DSanoop_SP What mistake I have made in this. Please reply. I am waiting for your reply. Regards, George On Wed, Dec 15, 2010 at 11:21 PM, Tom van der Woerdt i...@tvdw.eu mailto:i...@tvdw.eu wrote: Hi George, There have been some changes to Twitter's API and while not all of them have been activated yet, some of them may apply to you. Incorrect signature usually means that your signature is bad. This can mean a lot of things, but if only your user_timeline part is broken, you can start by looking at these : * Make sure that the URL in the Base String does not contain the query part of an URL (= anything after (and including) the ? part of the URL) - Good: https://api.twitter.com/1/statuses/user_timeline.json - Bad: https://api.twitter.com/1/statuses/user_timeline.json?count=200 Of course, this only applies to the Base String. Making a GET request is still fine. * Make sure that you specify the correct method in the Base String. - If you are making a GET request, put GET in the Base String. * Make sure that you properly URL-encode all values in the Base String - Good: Hello%20Twitter - Bad: Hello+Twitter - (This does not really apply to user_timeline) If you checked the above and the issue is still there, please show us a sample Base String and a dump of the request you make to the Twitter API. Tom On 12/15/10 6:06 PM, Georgooty varghese wrote: Dear Twitter, I have been created a twitter application. I got xauth token for my application. I have implemented twitter functionalities like home tweets, user info, follower details, following details, user time line. These functionalities working smoothly. Also get each user time line . But Todat, usser time url is not working right now. I got incorrect signature exception.. Though usertime line qury is not working yesterday. I have no change any line code. If any change need to my coding? Anybody please help me.. I am waiting for your reply. Regards, George -- 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 -- 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 -- 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
Re: [twitter-dev] 4294967295
Check this out...today sometime between 4:01:43 AM PST and 4:01:53 AM PST (sorry for the ambiguity, those are our every 10 sec logging timestamps for other stuff), we saw the unsigned equivalent of -2 (4294967294) being sent by twitter in user.listed_count... Exception in thread Twitter Stream Handling Thread[Receiving stream] java.lang .NumberFormatException: For input string: 4294967294 at java.lang.NumberFormatException.forInputString(NumberFormatException. java:48) at java.lang.Integer.parseInt(Integer.java:459) at java.lang.Integer.valueOf(Integer.java:553) at twitter4j.internal.util.ParseUtil.getInt(ParseUtil.java:120) at twitter4j.UserJSONImpl.init(UserJSONImpl.java:103) at twitter4j.UserJSONImpl.init(UserJSONImpl.java:86) at twitter4j.StatusJSONImpl.init(StatusJSONImpl.java:101) at twitter4j.StatusJSONImpl.init(StatusJSONImpl.java:84) at twitter4j.StatusJSONImpl.init(StatusJSONImpl.java:118) at twitter4j.StatusJSONImpl.init(StatusJSONImpl.java:84) at twitter4j.StatusStreamImpl.handleNextElement(StatusStreamImpl.java:116) at twitter4j.StatusStreamImpl.next(StatusStreamImpl.java:89) at twitter4j.TwitterStream$StreamHandlingThread.run(TwitterStream.java:529) Any idea what's going on and/or when it might be fixed? Thanks, Dan On Tue, Dec 14, 2010 at 8:10 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks! This is being looked into. I'll update when I have news. Taylor On Tuesday, December 14, 2010, Dan Checkoway dchecko...@gmail.com wrote: Yeah, you bet. Twitter4j isn't logging a timestamp when it happens, but here are a handful of timestamps for unrelated stuff that got logged no more than 10 seconds *prior* to the 4294967295 error popping out...so they're fairly close: Dec 14, 2010 12:34:11 PM PST Dec 14, 2010 1:13:07 PM PST Dec 14, 2010 1:22:48 PM PST Dec 14, 2010 1:27:22 PM PST Dec 14, 2010 1:29:48 PM PST Dec 14, 2010 1:33:36 PM PST Based on the twitter4j stack trace, I can tell you that it was *always* user.listed_count that had the funky value: Exception in thread Twitter Stream Handling Thread[Receiving stream] java.lang .NumberFormatException: For input string: 4294967295 at java.lang.NumberFormatException.forInputString(NumberFormatException. java:48) at java.lang.Integer.parseInt(Integer.java:459) at java.lang.Integer.valueOf(Integer.java:553) at twitter4j.internal.util.ParseUtil.getInt(ParseUtil.java:120) at twitter4j.UserJSONImpl.init(UserJSONImpl.java:103) Thanks, Dan On Tue, Dec 14, 2010 at 6:42 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Understandable, Dan. Can you tell me the last time an event like this happened? Taylor On Tue, Dec 14, 2010 at 3:41 PM, Dan Checkoway dchecko...@gmail.com wrote: I know this is the weenie answer, but I haven't been able to track a specific offending JSON object down yet, since it only seems to happen on the firehose, and we're using twitter4j to process that. If we were able to connect to the firehose more than once at a time, I could easily write a tool to detect and highlight the issue. Short of that, I'll try watching the sample stream for a while to see if the same issue pops up there. Will report any findings... Thanks, Dan On Tue, Dec 14, 2010 at 6:19 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Dan, Do you continue to see events like this happening? Can you provide a recent example in as-provided JSON or XML? Thanks, Taylor On Tue, Dec 14, 2010 at 2:13 PM, Dan Checkoway dchecko...@gmail.com wrote: Anybody else seeing user.listed_count occasionally coming back as 4294967295? That value just happens to equate to: 1 + (2 * Integer.MAX_VALUE) Sure looks like an unsigned version of -1 to me... Anyway, it's breaking twitter4j.TwitterStream stuff. I've mentioned that separately on the twitter4j list, but I wanted to raise the issue here since the root cause is twitter sending the weird value. Thanks, Dan -- 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 -- 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 -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi
[twitter-dev] Twitter API
My development environment is MS Visual Studio 2010, using VB.NET. All I need to do is post a Tweet for some of the identified status changes within my web application. I don't need user verification as the app is designed to automatically post the status change Tweet whenever it occurs. I added all 4 required values, ConsumerKey, ConsumerSecret, OAuthToken, and OAuthTokenSecret to the web.config file in the appSettings section of the configuration section. appSettings !-- Twitter and BitLy access keys -- add key=ConsumerKey value=MYCONSUMERKEY / add key=ConsumerSecret value=MYCONSUMERSECRETKEY / add key=OAuthToken value=MYAPPSOAUTHTOKENKEY / add key=OAuthTokenSecret value=MYAPPSOAUTHTOKENSECRETKEY / /appSettings I found that by going to twitter.com and signing into the account that is using the application, then go to the Settings page, go to the bottom of the page and click on the API menu option. Once the API page appears you will click on the button 2, Register An App. On the right side on the new page, you will see a button View Your Applications. If you have previously registered your app, click this button, If not fill out the application for a new app. Now at the View your Applications page, select the app you want to get the authorization keys for where is says Edit Details. Now click on the button to the right that says, Application Detail. Here you will find your Consumer Key and your Consumer Secret Key. On the right side of this page you will see the menu option My Access Token, click it and you will find your oauth_token and your oauth_token_secret keys! Now that you have all the keys, put them in the appSettings section of the web.config file. I add Dim twConn As New TwitterVB2.TwitterAPI at the top of the code behind web page. I then created a subroutine where I pass in the Tweet: Public Sub PostOnTwitter(ByVal Tweet As String) 'Retrieve Keys from web.config Dim twitterKey As String = System.Configuration.ConfigurationManager.AppSettings(ConsumerKey) Dim twitterSecret As String = System.Configuration.ConfigurationManager.AppSettings(ConsumerSecret) Dim twitterOAuthToken As String = System.Configuration.ConfigurationManager.AppSettings(OAuthToken) Dim twitterOAuthTokenSecret As String = System.Configuration.ConfigurationManager.AppSettings(OAuthTokenSecret) Try twConn.AuthenticateWith(twitterKey, twitterSecret, twitterOAuthToken, twitterOAuthTokenSecret) twConn.Update(Trim(Tweet)) Catch ex As Exception lblError.Text = Twitter Returned: ex.Message End Try End Sub This code works great on my local development, an environment that allows Full trust level. However it appears when I publish my application to my host, Rackspace.com which uses an environment of Cloud Hosting , the Trust Level is less than Full and I get an error. Twitter Returned: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. Can anyone HELP? -- 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
[twitter-dev] t.co URL Shortener removing valid characters from URLs
Hey (first post!), We recently launched a community site for LittleBigPlanet and are having a few problems with the tweet button shortening our links but removing characters from the end of the URL. So I start with this URL: http://lbp.me/v/0b6z- The tweet button then converts this to: http://t.co/m1kHX6D ...which then redirects to (missing the hyphen): http://lbp.me/v/0b6z ...and results in a 404 as that url doesn't exist. The original URL is perfectly valid - so is this expected functionality? Is there any way to force the URL shortener to respect the full URL, or should we consider rejigging our URL hashes? Help much appreciated thanks! :) -- 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
[twitter-dev] Bad access token?
I'm getting this error when trying to authorize: Woah there! This page is no longer valid. It looks like someone already used the token information you provided. Please return to the site that sent you to this page and try again … it was probably an honest mistake. This seems to be the standard message for a bad access token because replacing the token with random jibberish from the url in my browser produces the same result. I am using the oauth_token specified on my application's Access Token Requisition page. I've tried with an without the oauth_callback param specified. I just set up the application today. -- 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
[twitter-dev] how can i upload a tweet with a photo?
hi all i am using twitter4j api, and i can upload a tweet ,but I can not find a function that upload a tweet with photo , somebody can help me？ -- 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
Re: [twitter-dev] how can i upload a tweet with a photo?
Hi, Twitter itself does not host any photos for tweets, so this is not implemented in Twitter4j. You should look at (for example) the TwitPic documentation for more information about uploading pictures. Tom On 12/17/10 8:06 AM, aqua wrote: hi all i am using twitter4j api, and i can upload a tweet ,but I can not find a function that upload a tweet with photo , somebody can help me？ -- 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
Re: [twitter-dev] Bad access token?
I've never seen that error before, but I assume that it's your oauth_nonce that is invalid (not unique). If it is not the oauth_nonce, you should re-check your oauth_timestamp value. It should be in Unix Timestamp format (UTC) and it should not be more than 5 minutes off. Tom On 12/17/10 9:48 AM, oz wrote: I'm getting this error when trying to authorize: Woah there! This page is no longer valid. It looks like someone already used the token information you provided. Please return to the site that sent you to this page and try again … it was probably an honest mistake. This seems to be the standard message for a bad access token because replacing the token with random jibberish from the url in my browser produces the same result. I am using the oauth_token specified on my application's Access Token Requisition page. I've tried with an without the oauth_callback param specified. I just set up the application today. -- 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
Re: [twitter-dev] Bad access token?
It sounds like you might be using the wrong tokens in a few places. Just a quick review of what tokens are used where in these steps: Your consumer key and consumer secret are used in every step of the OAuth negotiation process and every API call you make. Access tokens are only used on resource-based requests to the API itself. Your first request, to /oauth/request_token, should not include a value for oauth_token (but you should be including an oauth_callback, regardless of whether you set it on you application record or not). The request token step yields the first oauth_token and oauth_token_secret (request token) as its response. The second step is then sending that request token as an oauth_token (properly integrated into your OAuth headers, basestring, and signature) to the /oauth/authorize page (with no oauth_callback specified at this phase, as the value is taken from the previous step). When this step succeeds, it redirects to the oauth_callback specified on the request token step. The callback will receive an oauth_verifier, in addition to the same oauth_token request token value. Now the request token is sent to the /oauth/access_token (again properly signed) in exchange for an access token (represented again, by key/value pairs for oauth_token and oauth_token_secret). These are the two values that you need to persist. Finally, if you registered your application, and then went to the My Access Token feature on the right-hand pane, you would have the oauth_token and oauth_token_secret values that would be produced in the final step for your own account.. essentially, you start from the point of being able to use the access token to make API calls. Hope this helps. Taylor On Fri, Dec 17, 2010 at 12:48 AM, oz oser...@comcast.net wrote: I'm getting this error when trying to authorize: Woah there! This page is no longer valid. It looks like someone already used the token information you provided. Please return to the site that sent you to this page and try again … it was probably an honest mistake. This seems to be the standard message for a bad access token because replacing the token with random jibberish from the url in my browser produces the same result. I am using the oauth_token specified on my application's Access Token Requisition page. I've tried with an without the oauth_callback param specified. I just set up the application today. -- 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 -- 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
Re: [twitter-dev] t.co URL Shortener removing valid characters from URLs
Thanks for the report, we'll investigate. I can't think of a workaround at the moment unfortunately. On Fri, Dec 17, 2010 at 3:51 AM, Tom_Molecule commun...@mediamolecule.comwrote: Hey (first post!), We recently launched a community site for LittleBigPlanet and are having a few problems with the tweet button shortening our links but removing characters from the end of the URL. So I start with this URL: http://lbp.me/v/0b6z- The tweet button then converts this to: http://t.co/m1kHX6D ...which then redirects to (missing the hyphen): http://lbp.me/v/0b6z ...and results in a 404 as that url doesn't exist. The original URL is perfectly valid - so is this expected functionality? Is there any way to force the URL shortener to respect the full URL, or should we consider rejigging our URL hashes? Help much appreciated thanks! :) -- 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 -- 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
Re: [twitter-dev] how can i upload a tweet with a photo?
Hi, Example codes are packaged in the archive. Try bin/media/*.sh|cmd. Those examples use twitter4j.media.* package. https://github.com/yusuke/twitter4j/tree/master/twitter4j-examples/src/main/java/twitter4j/examples/media And please post further question to Twitter4J's mailing list as Twitter4J isn't an official library. http://twitter4j.org/en/index.html#mailingList Thanks, -- Yusuke Yamamoto yus...@mac.com this email is: [x] bloggable/tweetable [ ] private follow me on : http://twitter.com/yusukeyamamoto subscribe me at : http://samuraism.jp/ On Dec 17, 2010, at 16:06 , aqua wrote: hi all i am using twitter4j api, and i can upload a tweet ,but I can not find a function that upload a tweet with photo , somebody can help me？ -- 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 -- 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
[twitter-dev] Managing Multiple Users and /account/geo Woes
I'm storing access_tokens for a number of users in my application. When I switch from one account to another for management, I run a background AJAX request on account/verify_credentials to determine if the active user is geo enabled (parameter geo_enabled). If the user isn't geo enabled, I open a lightbox asking them if they'd like to turn on location. I then fire off a redirect to /account/geo if they clicked yes so they can enable location. The problem, at this point, is that the user may be logged into Twitter with a different account. Is there any way for me to do some trickery to switch the logged in user on twitter (i.e. you allow force_login on authentication) to ensure they're logged in as the proper user? Perhaps even some handling to determine the currently logged in user and check if it matches the access_token user? The current handling poses a very big drawback to this beautiful geo page when managing multiple accounts. I need a way of ensuring that / account/geo pertains to the proper user (and not some other managed user account). Any help, solutions, workarounds, or suggestions would be much appreciated. -- 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
[twitter-dev] firehose exception: the end of stream has been reached
Our app is using twitter4j 2.1.9-SNAPSHOT against the twitter firehose, and
lately we are having problems with the stream just ending out of the
blue. It happens several times a day lately with no rhyme or reason.
Here's an example of what we see:
Stream closed.TwitterException{exceptionCode=[a3652dee-000a1c7a
a3652dee-000a1c35], statusCode=-1, retryAfter=0, rateLimitStatus=null,
version=2.1.9-SNAPSHOT}
at
twitter4j.AbstractStreamImplementation.handleNextElement(AbstractStreamImplementation.java:149)
at twitter4j.StatusStreamImpl.next(StatusStreamImpl.java:74)
at
twitter4j.TwitterStream$TwitterStreamConsumer.run(TwitterStream.java:687)
Caused by: java.io.IOException: the end of the stream has been reached
at
twitter4j.AbstractStreamImplementation.handleNextElement(AbstractStreamImplementation.java:80)
... 2 more
We call cleanUp and then reconnect to the firehose, and then the same thing
happens again. Eventually we get temporarily rate limited due to the
reconnect attempts.
I'm wondering if anybody else out there has seen this issue on the firehose,
or if anybody has a suggestion on how to avoid or work around it? Is the
likely cause on twitter's side, or could something on the client side be
causing this?
Thanks,
Dan
--
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
Re: [twitter-dev] firehose exception: the end of stream has been reached
Not seeing these issues, but I'm not using the firehose, so that
probably explains it. However :
* To avoid being rate limited, please read this document (and
implement it, because reading the document won't solve it):
http://dev.twitter.com/pages/user_streams_suggestions#StreamingConnectionFailure
* These errors are probably because the firehose stream has to restart
sometimes, for example for updates.
Tom
On 12/17/10 5:52 PM, Dan Checkoway wrote:
Our app is using twitter4j 2.1.9-SNAPSHOT against the twitter firehose,
and lately we are having problems with the stream just ending out of
the blue. It happens several times a day lately with no rhyme or
reason. Here's an example of what we see:
Stream closed.TwitterException{exceptionCode=[a3652dee-000a1c7a
a3652dee-000a1c35], statusCode=-1, retryAfter=0, rateLimitStatus=null,
version=2.1.9-SNAPSHOT}
at
twitter4j.AbstractStreamImplementation.handleNextElement(AbstractStreamImplementation.java:149)
at twitter4j.StatusStreamImpl.next(StatusStreamImpl.java:74)
at
twitter4j.TwitterStream$TwitterStreamConsumer.run(TwitterStream.java:687)
Caused by: java.io.IOException: the end of the stream has been reached
at
twitter4j.AbstractStreamImplementation.handleNextElement(AbstractStreamImplementation.java:80)
... 2 more
We call cleanUp and then reconnect to the firehose, and then the same
thing happens again. Eventually we get temporarily rate limited due to
the reconnect attempts.
I'm wondering if anybody else out there has seen this issue on the
firehose, or if anybody has a suggestion on how to avoid or work around
it? Is the likely cause on twitter's side, or could something on the
client side be causing this?
Thanks,
Dan
--
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
--
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
Re: [twitter-dev] PHP OAuth app stopped working magically
Make sure your OAuth library is up-to-date. Not having it up-to-date can cause a *lot* of issues. Tom On 12/17/10 7:34 PM, Nicolás López Zerpa wrote: Hello everyone. About a month ago, I've added to our news website the feature to login using Twitter. It uses OAuth to get the Twitter user data. However, since a few days ago, it doesn't work anymore. Nobody changed that feature recently; when I want to sign in, I get an 401 error: Failed to validate oauth signature and token. The script fails when it makes a request to https://api.twitter.com/oauth/request_token I've also made some little test with PHP OAuth classes I've found on the Internet and I couldn't either make my app work. Please, let me know if you need more info, or if Twitter changed something and I have to modify my app. Thanks in advance :) -- 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
[twitter-dev] Sporadic 401s?
I have been getting sporadic 401s interleaved with 200s while connected to Site Streams. I'll either open up a connection and it'll return 401s for a while, then eventually start returning normal responses, or vice versa. This issue started cropping up yesterday after the Site Stream restarts. Other users in the IRC channel seem to be reporting 401s across other endpoints somewhat sporadically as well. Is this a known issue? Any help would be greatly appreciated! Best, David -- 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
Re: [twitter-dev] firehose exception: the end of stream has been reached
Hey Dan,
If you fall too far behind when receiving the stream we will disconnect
you. Check the timestamp of the Tweets being received to the time on your
computer. If the times are drifting further apart you are falling behind.
The most common reasons for falling behind are:
1. You are attempting to process the stream in the same code that consumes
them - instead of running a queuing system.
2. Your connection is being used by other processes reducing your available
bandwidth.
As Tom suggested, run through the Streaming Documentation linked to from
http://dev.twitter.com/pages/streaming_api and make sure you implement the
suggestions.
Best,
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Dec 17, 2010 at 8:52 AM, Dan Checkoway dchecko...@gmail.com wrote:
Our app is using twitter4j 2.1.9-SNAPSHOT against the twitter firehose, and
lately we are having problems with the stream just ending out of the
blue. It happens several times a day lately with no rhyme or reason.
Here's an example of what we see:
Stream closed.TwitterException{exceptionCode=[a3652dee-000a1c7a
a3652dee-000a1c35], statusCode=-1, retryAfter=0, rateLimitStatus=null,
version=2.1.9-SNAPSHOT}
at
twitter4j.AbstractStreamImplementation.handleNextElement(AbstractStreamImplementation.java:149)
at twitter4j.StatusStreamImpl.next(StatusStreamImpl.java:74)
at
twitter4j.TwitterStream$TwitterStreamConsumer.run(TwitterStream.java:687)
Caused by: java.io.IOException: the end of the stream has been reached
at
twitter4j.AbstractStreamImplementation.handleNextElement(AbstractStreamImplementation.java:80)
... 2 more
We call cleanUp and then reconnect to the firehose, and then the same thing
happens again. Eventually we get temporarily rate limited due to the
reconnect attempts.
I'm wondering if anybody else out there has seen this issue on the
firehose, or if anybody has a suggestion on how to avoid or work around it?
Is the likely cause on twitter's side, or could something on the client side
be causing this?
Thanks,
Dan
--
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
--
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
Re: [twitter-dev] Cell phone tower information
Hi Alex, Tweets don't contain this information so it cannot be tracked or search for. Hope that answers your question, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Thu, Dec 16, 2010 at 2:44 PM, Alex chenzhe@gmail.com wrote: Hi, If tweet is posted from a cell phone. Is there a cell phone tag information when I search it using twitter Stream API? Thanks -- 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 -- 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
Re: [twitter-dev] PHP OAuth app stopped working magically
Hi Nicolás, If you can share your basestring and signature we can take a look at what's going wrong. Alternatively consider using a pre-written PHP library which handles this for you. There are some PHP libraries listed on our developer resources site which are popular with developers: http://dev.twitter.com/pages/oauth_libraries#php Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris 2010/12/17 Nicolás López Zerpa nico89...@gmail.com Hello everyone. About a month ago, I've added to our news website the feature to login using Twitter. It uses OAuth to get the Twitter user data. However, since a few days ago, it doesn't work anymore. Nobody changed that feature recently; when I want to sign in, I get an 401 error: Failed to validate oauth signature and token. The script fails when it makes a request to https://api.twitter.com/oauth/request_token I've also made some little test with PHP OAuth classes I've found on the Internet and I couldn't either make my app work. Please, let me know if you need more info, or if Twitter changed something and I have to modify my app. Thanks in advance :) -- 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 -- 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
[twitter-dev] Re: Unauthorized 401 http://twitter.com/friends/ids.json
I still get the same error 401 with url https://api.twitter.com/1/friends/ids.json Kathy On Dec 17, 9:10 am, Tom van der Woerdt i...@tvdw.eu wrote: Your url is wrong. Instead, use :https://api.twitter.com/1/friends/ids.json Tom On 12/17/10 2:06 AM, Kathy wrote: I keep getting unauthorized 401 error. I have been running my twitter application for months. But past couple of days, I was able to retieve very few friends information. Since Dec. 15, 6pm, I haven't been able to retrieve any. My search url is : http://twitter.com/friends/ids.json?user_id= -- 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
[twitter-dev] TwitterOauth
We've started seeing some errors using TwitteOauth. Specifically, we get an Incorrect signature error when trying to use the followers_ids method. This method worked 3 days ago. Has something changed? Thanks, Gary Zukowski -- 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
Re: [twitter-dev] Re: Unauthorized 401 http://twitter.com/friends/ids.json
Hi Kathy, What is the error we are returning in the response body? It should contain information about why the request failed. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Fri, Dec 17, 2010 at 11:14 AM, Kathy kathylee1...@gmail.com wrote: I still get the same error 401 with url https://api.twitter.com/1/friends/ids.json Kathy On Dec 17, 9:10 am, Tom van der Woerdt i...@tvdw.eu wrote: Your url is wrong. Instead, use : https://api.twitter.com/1/friends/ids.json Tom On 12/17/10 2:06 AM, Kathy wrote: I keep getting unauthorized 401 error. I have been running my twitter application for months. But past couple of days, I was able to retieve very few friends information. Since Dec. 15, 6pm, I haven't been able to retrieve any. My search url is : http://twitter.com/friends/ids.json?user_id= -- 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 -- 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
Re: [twitter-dev] TwitterOauth
Hi Gary, Can you share your basestring and Authorization header so we can investigate further. Thanks, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Fri, Dec 17, 2010 at 11:17 AM, Gary Zukowski ga...@tweetmyjobs.comwrote: We’ve started seeing some errors using TwitteOauth. Specifically, we get an “Incorrect signature” error when trying to use the followers_ids method. This method worked 3 days ago. Has something changed? Thanks, Gary Zukowski -- 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 -- 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
[twitter-dev] Chrome/Chromium vs. Firefox for Promoted Trends and Accounts
I just noticed something last night - when I browse Twitter with Firefox 3.6.12, I see the Promoted Trends and Promoted Accounts. But when I browse with Chrome 10.0.612.1 dev I don't. This may be some ad blocker setting - I haven't dug into that yet. But is there a generic reason why I wouldn't see them in Chrome? -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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
Re: [twitter-dev] Chrome/Chromium vs. Firefox for Promoted Trends and Accounts
On Fri, 17 Dec 2010 11:33:46 -0800, M. Edward (Ed) Borasky zn...@borasky-research.net wrote: I just noticed something last night - when I browse Twitter with Firefox 3.6.12, I see the Promoted Trends and Promoted Accounts. But when I browse with Chrome 10.0.612.1 dev I don't. This may be some ad blocker setting - I haven't dug into that yet. But is there a generic reason why I wouldn't see them in Chrome? -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős OK - disabled AdBlock in Chrome and it still doesn't show Promoted Trends or Promoted Accounts. This is openSUSE Linux 11.3 on a 64-bit machine, BTW - sorry I don't have something more vanilla. ;-) -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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
[twitter-dev] Re: PHP OAuth app stopped working magically
Hiya, I had a similar problem about the same time; it turned out that I had somehow been ignoring the oauth_verifier parameter that Twitter provides. I plugged it back in and hey presto, problem fixed! ...and then the next day I discovered that I wasn't checking to see if oauth_verifier was always passed - sometimes it isn't - so hopefully I've saved you one gotcha there ;-) Cheers, Tom. On Dec 17, 7:34 pm, Nicolás López Zerpa nico89...@gmail.com wrote: Hello everyone. About a month ago, I've added to our news website the feature to login using Twitter. It uses OAuth to get the Twitter user data. However, since a few days ago, it doesn't work anymore. Nobody changed that feature recently; when I want to sign in, I get an 401 error: Failed to validate oauth signature and token. The script fails when it makes a request tohttps://api.twitter.com/oauth/request_token I've also made some little test with PHP OAuth classes I've found on the Internet and I couldn't either make my app work. Please, let me know if you need more info, or if Twitter changed something and I have to modify my app. Thanks in advance :) -- 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
[twitter-dev] Re: Please check you are using the correct API and host
SSL (https) is supported on some but not all hosts. You can use SSL on: * api.twitter.com * userstream.twitter.com * betastream.twitter.com * search.twitter.com SSL is currently not supported on: * platform.twitter.com * widgets.twimg.com * stream.twitter.com Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Dec 16, 4:57 pm, Abraham Williams 4bra...@gmail.com wrote: https should be preferred on many of these especially anything that is transferring protected data. Abraham - Abraham Williams | Hacker Advocate | abrah.am @abraham https://twitter.com/abraham | github.com/abraham | blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Thu, Dec 16, 2010 at 16:54, Matt Harris thematthar...@twitter.comwrote: Hey Developers, We recently reviewed a sample of your API requests, emails and support tickets and found that some of you were not using the correct domains. While undocumented domains and endpoints may respond with data, you should avoid using them as they may be disabled or changed without notice. Our network infrastructure is also updated from time to time. These changes are required for capacity planning or load balancing, but are generally transparent to you if you use the correct API host. To avoid problems or outages with your applications you need to ensure you are using the correct hosts (and base paths) for the Twitter API you want to use. Even if your code is working now, you should check the hosts match those listed below: REST API: http://api.twitter.com/1/RESOURCE OAuth: http://api.twitter.com/oauth/RESOURCE Streaming (Track): http://stream.twitter.com/1/RESOURCE Userstreams: http://userstream.twitter.com/2/user.json SiteStreams Beta: http://betastream.twitter.com/2b/site.json Search: http://search.twitter.com/search.json Tweet Button: http://platform.twitter.com/widgets.js @anywhere: http://platform.twitter.com/anywhere.js Web Widgets: http://widgets.twimg.com/j/2/widget.js Some common errors include: * Incorrectly usinghttp://twitter.cominstead of http://api.twitter.com/1/ * Incorrectly using requests like http://api.twitter.com/account/verify_credentials.jsoninstead of http://api.twitter.com/1/account/verify_credentials.json * Incorrectly directing users tohttp://twitter.com/oauth/authorizeinsteadof http://api.twitter.com/oauth/authorize * Incorrectly queryinghttp://199.16.156.11/search.jsoninstead of http://search.twitter.com/search.json You can find the documented endpoints on our developer resources site: http://dev.twitter.com Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris -- 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 -- 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
Re: [twitter-dev] Re: Different crossdomains for a0.twimg.com a2.twimg.com, a3 etc
Hey Ben, I've checked this with the team and they have corrected the crossdomain file so it is now open on twimg. Our CDN should be returning the correct file now but it's possible some hosts need a bit longer to have their caches cleared. Thanks, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Thu, Dec 16, 2010 at 10:13 PM, WildFoxMedia wildfoxme...@gmail.comwrote: Hi Matt, I appreciate you jumping into this thread and I look forward to your response. -Ben On Dec 16, 2:07 pm, Matt Harris thematthar...@twitter.com wrote: Thanks for letting us know about this. I've asked the team to if this file should be as restrictive as it currently is. Best @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Thu, Dec 16, 2010 at 11:16 AM, WildFoxMedia wildfoxme...@gmail.com wrote: Super, they are all returning the same thing now, which is blocking access from any non-twitter domain which you can see below: cross-domain-policy xsi:noNamespaceSchemaLocation=http:// www.adobe.com/xml/schemas/PolicyFile.xsd allow-access-from domain=twitter.com/ allow-access-from domain=api.twitter.com/ allow-access-from domain=search.twitter.com/ allow-access-from domain=static.twitter.com/ site-control permitted-cross-domain-policies=master-only/ allow-http-request-headers-from domain=*.twitter.com headers=* secure=true/ /cross-domain-policy What is Twitters official stance on this? Are Flash developers SOL and required to use a server-side proxy to grab images, or are we supposed to be able to grab profile images from *.twimg? On Dec 15, 5:57 pm, John Adams j...@twitter.com wrote: a0 through a4 should offer identical crossdomain.xml files. They are all going through a CDN, so it might be the case that the CDN endpoint you are hitting has a stale file. I just checked all of the CDN endpoints from here and they are returning the same data. Try again? -john On Wed, Dec 15, 2010 at 5:20 PM, WildFoxMedia wildfoxme...@gmail.com wrote: Im currently seeing the same issue, however, in completely reverse. As of this moment, a0 a1 are not allowing other domains and a2 a3 are allowing all domains. The other day, all 4 were not allowing other domains. Is there any reason or rhyme for this and more importantly, what is the expectation? Are we supposed to be able to make calls from Flash for profile images or not? On Nov 28, 3:57 pm, stephen sno...@bcm.com.au wrote: Hey, It appears the crossdomains for a2, a3, etc are different and are preventing flash from accessing profile images on these domains. a0 and a1 are fine, however the api returns profile image urls using all of these domains (a0 - a?). Are the crossdomains suppose to be all the same or are we suppose to target only the first two? From the few that I've tested, it seems all profile images are accessible through the a0 or a1 domains despite what the api returns. Crossdomains http://a0.twimg.com/crossdomain.xmlhttp://a1.twimg.com/crossdomain.xm. .. Stephen -- 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 -- 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 -- 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 -- 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
[twitter-dev] OAuth 401 Unauthorized failure
Hi all.
I am working on a web app for Twitter using the Tweepy Python API. My
code has been working for a month, but at some point this week, it
stopped working. Now when I request the access token from the
verification code, I get a 401: Unauthorized failure.
I did see from Matt's post yesterday that Tweepy was using the wrong
URLs. (It was using http://twitter.com/oauth instead of
http://api.twitter.com/oauth.) I fixed that problem and I'm still
seeing the problem.
I see from everyone else who is reporting this that you want to see
the basestring and Authorization header, so here's what I'm using:
URL: http://api.twitter.com/oauth/access_token
Headers: {'Authorization': 'OAuth realm=, oauth_nonce=58011146,
oauth_timestamp=1292624570, oauth_signature_method=HMAC-SHA1,
oauth_consumer_key=bSf2ywUggWN1w7Yx5FtvJg,
oauth_verifier=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_version=1.0,
oauth_token=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_signature=tOqtyU6E%2FulE8xiYBQRzuv2RMog%3D'}
Does anyone see a problem here?
Thank you!
Brian
--
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
Re: [twitter-dev] OAuth 401 Unauthorized failure
Hi Brian,
A couple of questions so we can investigate:
1. What was the response body content we returned with the 401?
2. What was the basestring you used?
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Dec 17, 2010 at 2:30 PM, Brian Gunn gun...@gmail.com wrote:
Hi all.
I am working on a web app for Twitter using the Tweepy Python API. My
code has been working for a month, but at some point this week, it
stopped working. Now when I request the access token from the
verification code, I get a 401: Unauthorized failure.
I did see from Matt's post yesterday that Tweepy was using the wrong
URLs. (It was using http://twitter.com/oauth instead of
http://api.twitter.com/oauth.) I fixed that problem and I'm still
seeing the problem.
I see from everyone else who is reporting this that you want to see
the basestring and Authorization header, so here's what I'm using:
URL: http://api.twitter.com/oauth/access_token
Headers: {'Authorization': 'OAuth realm=, oauth_nonce=58011146,
oauth_timestamp=1292624570, oauth_signature_method=HMAC-SHA1,
oauth_consumer_key=bSf2ywUggWN1w7Yx5FtvJg,
oauth_verifier=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_version=1.0,
oauth_token=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_signature=tOqtyU6E%2FulE8xiYBQRzuv2RMog%3D'}
Does anyone see a problem here?
Thank you!
Brian
--
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
--
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
[twitter-dev] Re: OAuth 401 Unauthorized failure
I was hoping that URL is the basestring. Apparently not.
What do you mean by basestring? I'm using the Tweepy Python library
to hide the details of this from me, but I'm digging through there to
instrument it so I can send you what you want.
Brian
On Dec 17, 2:37 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Brian,
A couple of questions so we can investigate:
1. What was the response body content we returned with the 401?
2. What was the basestring you used?
Best
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Fri, Dec 17, 2010 at 2:30 PM, Brian Gunn gun...@gmail.com wrote:
Hi all.
I am working on a web app for Twitter using the Tweepy Python API. My
code has been working for a month, but at some point this week, it
stopped working. Now when I request the access token from the
verification code, I get a 401: Unauthorized failure.
I did see from Matt's post yesterday that Tweepy was using the wrong
URLs. (It was usinghttp://twitter.com/oauthinstead of
http://api.twitter.com/oauth.) I fixed that problem and I'm still
seeing the problem.
I see from everyone else who is reporting this that you want to see
the basestring and Authorization header, so here's what I'm using:
URL:http://api.twitter.com/oauth/access_token
Headers: {'Authorization': 'OAuth realm=, oauth_nonce=58011146,
oauth_timestamp=1292624570, oauth_signature_method=HMAC-SHA1,
oauth_consumer_key=bSf2ywUggWN1w7Yx5FtvJg,
oauth_verifier=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_version=1.0,
oauth_token=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_signature=tOqtyU6E%2FulE8xiYBQRzuv2RMog%3D'}
Does anyone see a problem here?
Thank you!
Brian
--
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
--
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
[twitter-dev] Re: OAuth 401 Unauthorized failure
Okay--how about this for a basestring:
http://api.twitter.com/oauth/access_token?oauth_nonce=62391593oauth_timestamp=1292628636oauth_signature_method=HMAC-SHA1oauth_consumer_key=bSf2ywUggWN1w7Yx5FtvJgoauth_verifier=zzp3G0k6zoVBI11iCMMGtcpxfhks92vlsXxxZOwAqhsoauth_version=1.0oauth_token=zzp3G0k6zoVBI11iCMMGtcpxfhks92vlsXxxZOwAqhsoauth_signature=LuZt%2FwyR1OAYxO%2F%2BLNRouhP%2Fg%2Fc%3D
I'm still trying to get the text of the response. At the moment, it
looks like it's buried in another Python library somewhere because the
401 error causes an exception. Hopefully I'll be able to get that
shortly.
Brian
On Dec 17, 2:40 pm, Brian Gunn gun...@gmail.com wrote:
I was hoping that URL is the basestring. Apparently not.
What do you mean by basestring? I'm using the Tweepy Python library
to hide the details of this from me, but I'm digging through there to
instrument it so I can send you what you want.
Brian
On Dec 17, 2:37 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Brian,
A couple of questions so we can investigate:
1. What was the response body content we returned with the 401?
2. What was the basestring you used?
Best
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Fri, Dec 17, 2010 at 2:30 PM, Brian Gunn gun...@gmail.com wrote:
Hi all.
I am working on a web app for Twitter using the Tweepy Python API. My
code has been working for a month, but at some point this week, it
stopped working. Now when I request the access token from the
verification code, I get a 401: Unauthorized failure.
I did see from Matt's post yesterday that Tweepy was using the wrong
URLs. (It was usinghttp://twitter.com/oauthinsteadof
http://api.twitter.com/oauth.) I fixed that problem and I'm still
seeing the problem.
I see from everyone else who is reporting this that you want to see
the basestring and Authorization header, so here's what I'm using:
URL:http://api.twitter.com/oauth/access_token
Headers: {'Authorization': 'OAuth realm=, oauth_nonce=58011146,
oauth_timestamp=1292624570, oauth_signature_method=HMAC-SHA1,
oauth_consumer_key=bSf2ywUggWN1w7Yx5FtvJg,
oauth_verifier=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_version=1.0,
oauth_token=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_signature=tOqtyU6E%2FulE8xiYBQRzuv2RMog%3D'}
Does anyone see a problem here?
Thank you!
Brian
--
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
--
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
Re: [twitter-dev] Re: OAuth 401 Unauthorized failure
OK. One other thing I've just noticed looking over your Authorization header
is that your oauth_verifer and oauth_token are set to the same value. This
is unusual and not something I would expect.
Double check your code used the oauth_verifier we return to you in the
callback URL and the token is the one you received in the request_token
request.
Best
@themattharris
Developer Advocate, Twitter
http://twitter.com/themattharris
On Fri, Dec 17, 2010 at 2:40 PM, Brian Gunn gun...@gmail.com wrote:
I was hoping that URL is the basestring. Apparently not.
What do you mean by basestring? I'm using the Tweepy Python library
to hide the details of this from me, but I'm digging through there to
instrument it so I can send you what you want.
Brian
On Dec 17, 2:37 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Brian,
A couple of questions so we can investigate:
1. What was the response body content we returned with the 401?
2. What was the basestring you used?
Best
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Fri, Dec 17, 2010 at 2:30 PM, Brian Gunn gun...@gmail.com wrote:
Hi all.
I am working on a web app for Twitter using the Tweepy Python API. My
code has been working for a month, but at some point this week, it
stopped working. Now when I request the access token from the
verification code, I get a 401: Unauthorized failure.
I did see from Matt's post yesterday that Tweepy was using the wrong
URLs. (It was usinghttp://twitter.com/oauthinstead of
http://api.twitter.com/oauth.) I fixed that problem and I'm still
seeing the problem.
I see from everyone else who is reporting this that you want to see
the basestring and Authorization header, so here's what I'm using:
URL:http://api.twitter.com/oauth/access_token
Headers: {'Authorization': 'OAuth realm=, oauth_nonce=58011146,
oauth_timestamp=1292624570, oauth_signature_method=HMAC-SHA1,
oauth_consumer_key=bSf2ywUggWN1w7Yx5FtvJg,
oauth_verifier=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_version=1.0,
oauth_token=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_signature=tOqtyU6E%2FulE8xiYBQRzuv2RMog%3D'}
Does anyone see a problem here?
Thank you!
Brian
--
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
--
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
--
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
[twitter-dev] Re: OAuth 401 Unauthorized failure
Okay. Very interesting! I'll take a look at that.
Thank you!
Brian
On Dec 17, 3:32 pm, Matt Harris thematthar...@twitter.com wrote:
OK. One other thing I've just noticed looking over your Authorization header
is that your oauth_verifer and oauth_token are set to the same value. This
is unusual and not something I would expect.
Double check your code used the oauth_verifier we return to you in the
callback URL and the token is the one you received in the request_token
request.
Best
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Fri, Dec 17, 2010 at 2:40 PM, Brian Gunn gun...@gmail.com wrote:
I was hoping that URL is the basestring. Apparently not.
What do you mean by basestring? I'm using the Tweepy Python library
to hide the details of this from me, but I'm digging through there to
instrument it so I can send you what you want.
Brian
On Dec 17, 2:37 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Brian,
A couple of questions so we can investigate:
1. What was the response body content we returned with the 401?
2. What was the basestring you used?
Best
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Fri, Dec 17, 2010 at 2:30 PM, Brian Gunn gun...@gmail.com wrote:
Hi all.
I am working on a web app for Twitter using the Tweepy Python API. My
code has been working for a month, but at some point this week, it
stopped working. Now when I request the access token from the
verification code, I get a 401: Unauthorized failure.
I did see from Matt's post yesterday that Tweepy was using the wrong
URLs. (It was usinghttp://twitter.com/oauthinsteadof
http://api.twitter.com/oauth.) I fixed that problem and I'm still
seeing the problem.
I see from everyone else who is reporting this that you want to see
the basestring and Authorization header, so here's what I'm using:
URL:http://api.twitter.com/oauth/access_token
Headers: {'Authorization': 'OAuth realm=, oauth_nonce=58011146,
oauth_timestamp=1292624570, oauth_signature_method=HMAC-SHA1,
oauth_consumer_key=bSf2ywUggWN1w7Yx5FtvJg,
oauth_verifier=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_version=1.0,
oauth_token=8bKG5j8sbzKIkycG61MxtpznR9dOx4L1WQe7rxZ0,
oauth_signature=tOqtyU6E%2FulE8xiYBQRzuv2RMog%3D'}
Does anyone see a problem here?
Thank you!
Brian
--
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
--
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
--
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
[twitter-dev] Application suspended, how long to wait to review and make good again?
Hi everyone, Just under 24 hours ago, my app (TweetingMachine, @machinetweeting) was suspended. I quickly asked for more details, and today reviewed the Twitter TOS and found what I thought was the infraction: auto following. Fair enough - I've now removed the feature and sent an update email to a...@twitter.com asking if this was the reason, along with a clarification about other features on the site (e.g. what's called auto follow is actually a tool for automatically following your new followers, the unfollow tool requires manual work, nothing automatic). I'm feeling a bit stressed as I'm genuinely upset to have fallen foul of the Twitter TOS, and I really want to work and make the tool as awesome and legit as possible, but I'm only hearing a deafening silence. The support ticket is here: http://support.twitter.com/tickets/1428177 How long does it typically take to get back to people about these issues? If you could take a brief look and post any details here or wherever's the more convenient for you, I'd really appreciate it. Thanks! Tom Buck -- 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
[twitter-dev] t.co Posting Questions
Howdy, I'm writing an iPad app that has a Share via Twitter feature. I'm trying to understand how to count characters, including URLs before I post to the API. I thought these might be FAQs, but t.co does not show up in the FAQ and has only two hits via Google's search of this list, so I apologize if these are in fact FAQs. So I tried to post a new status message that was longer than 140 characters, but I counted the URL as only 19 characters, per [this message][] from Raffi. Unfortunately, the API rejected the message as too long. So my questions are: * Should I be counting URLs as only 19 characters? * If so, will the Twitter API be adjusted to count URLs as only 19 characters, and not reject messages that are longer because the URLs are longer? * And if that's the plan, when is it likely to happen? * And should I also count URLs that are less than 19 characters as 19 characters, on the assumption that they will *always* be wrapped? Ah, I just did a search for link wrap and say [this thread][] from September. Doesn't look like there was an official answer from Twitter -- did I miss it? If not, does anyone have any idea when there might be more information on this stuff and how it will affect the API? Thanks, David [this message]: http://groups.google.com/group/twitter-development-talk/msg/9bdd19b025fe0cba? [this thread]: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/dacc3bdc5b1e1d67 -- 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
[twitter-dev] TwitterOauth
I'm getting the following error when trying to do a simple update_profile: client.update_profile(:url = '') JSON::ParserError: 665: unexpected token at '?xml version=1.0 encoding=UTF-8? hash request/1/account/update_profile/request errorCould not authenticate with OAuth./error /hash ' Any ideas? Thanks, Gary Zukowski -- 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
