Re: [twitter-dev] how save twitter login?
if u are using OAuth authenticationu must save u r accesstoken and access secret, usedID And useranme.u can use these details for furthur requests...when the user relogged into the application //kamesh 2011/6/14 Maksim Bunkow bim...@gmail.com I developing Desktop App and use OAuth, how save acc data for logining users without password every time? Thx. -- С уважением, Буньков Максим. bim...@gmail.com -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] how save twitter login?
Save the access token that you get back after passing in the oauth verifier. 2011/6/13 Maksim Bunkow bim...@gmail.com I developing Desktop App and use OAuth, how save acc data for logining users without password every time? Thx. -- С уважением, Буньков Максим. bim...@gmail.com -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine
i Found this API In Deprecated listwe have to use another API's go to this link http://groups.google.com/group/twitter-development-talk/browse_thread/thread/aa465ee6c315e04d# //kamesh On Tue, Jun 14, 2011 at 11:08 AM, Amit Battan Ror batta...@gmail.comwrote: Bill Working fine : https://twitter.com/statuses/friends_timeline.xml Not Working Giving 403 Error : https://twitter.com/statuses/followers.xml On Jun 14, 10:14 am, Amit Battan Ror batta...@gmail.com wrote: Thanks Bill I will check and try to track URL .. On Jun 13, 9:07 pm, Bill Jacobson gabe...@gmail.com wrote: Amit, also seehttp:// www.mailinglistarchive.com/html/twitter-development-talk@googl That's what helped me. -Bill On 06/13/2011 10:44 AM, Bill Jacobson wrote: I'm suggesting that you find out what endpoint (Twitter URL) your app is targeting, and make sure that it matches what is currently documented. If it doesn't match, correct it. That's what worked for me. On 06/13/2011 08:05 AM, Amit Battan Ror wrote: I am not getting the solution. and my API was working fine beofre 2 3 days.. but not now.. all other API except getFollowersIncludingCurrentStatus working ok and return proper output On Jun 13, 5:53 pm, Bill Jacobsongabe...@gmail.com wrote: Amit, I don't know your library, but in my case the 403 was accompanied by the message Not authorized to use this endpoint and the solution was to update to http://api.twitter.com/1[etc.];. Bill Jacobson On 06/13/2011 05:39 AM, Amit Battan Ror wrote: any idea guys On Jun 10, 4:33 pm, Amit Battan Rorbatta...@gmail.comwrote: Hi All I am using Twitter-OAuth-iPhonehttps:// github.com/bengottlieb/Twitter-OAuth-iPhone I am calling [twitterObj getFollowersIncludingCurrentStatus:NO] for getting my friend list which was working fine. But from last two days its giving me the 403 error. -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed with error: Error Domain=HTTP Code=403 The operation couldn t be completed. (HTTP error 403.) As twitter api wiki 403 is due to crossing the limit of updates and DM but here in getFollowersIncludingCurrentStatus Why this error occurring and even list is not comes next day giving same 403 error. Thanks Amit Battan -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Problem With Fetching Followers and Following Id's
Is Anybody have IDEA about the solution of above problem //kamesh On Jun 13, 12:49 pm, kamesh SmartDude kamesh.smartd...@gmail.com wrote: Dear All, I am developing a twitter mobile application, and i have a problem in fetching the followers and following list. earlier i used http://api.twitter.com/version/statuses/friends.formathttp://api.twitter.com/version/statuses/followers.format API's to fecth the Followers and following people list. But now they are depricated. Now i want to use the API's http://api.twitter.com/version/friends/ids.formathttp://api.twitter.com/version/followers/ids.format to fetch the ID's of the follower and following people Id's and http://api.twitter.com/version/users/lookup.format API to get the user List. Now My problem is that i want to fetch the Specific number (as per my requirement it is 16) of follower and following id's using the above two API's (friends/ids.format and followers/ids.format). But these two API's ignoring the count Parameter (suppose if i sent a request to fetch the followers of the user = sachin_rt http://api.twitter.com/1/followers/ids.json/screen_name=sachin_rtcur... it is ignoring the count parameterand returning an amount 5000 followers ID's. ) and returning a huge number of Id's. As i am developing a mobile app i don't want to store this amount of data in my database until user go for showmore/ or scroll to the bottom of the list. please let me know is there any solution to fetch the specific number of ID's of the followers/follwing. Thanks in AdvanceKamesh -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] how save twitter login?
Big thx!!! it came out!!! Secret it is sufficient only key and secret string, without userid. -- С уважением, Буньков Максим. bim...@gmail.com 14.06.2011, в 12:20, kamesh SmartDude написал(а): if u are using OAuth authenticationu must save u r accesstoken and access secret, usedID And useranme.u can use these details for furthur requests...when the user relogged into the application //kamesh 2011/6/14 Maksim Bunkow bim...@gmail.com I developing Desktop App and use OAuth, how save acc data for logining users without password every time? Thx. -- С уважением, Буньков Максим. bim...@gmail.com -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Problem With Fetching Followers and Following Id's
I am facing the same issue.. On Tue, Jun 14, 2011 at 11:56 AM, kamesh SmartDude kamesh.smartd...@gmail.com wrote: Is Anybody have IDEA about the solution of above problem //kamesh On Jun 13, 12:49 pm, kamesh SmartDude kamesh.smartd...@gmail.com wrote: Dear All, I am developing a twitter mobile application, and i have a problem in fetching the followers and following list. earlier i used http://api.twitter.com/version/statuses/friends.formathttp://api.twitter.com/version/statuses/followers.format API's to fecth the Followers and following people list. But now they are depricated. Now i want to use the API's http://api.twitter.com/version/friends/ids.formathttp://api.twitter.com/version/followers/ids.format to fetch the ID's of the follower and following people Id's and http://api.twitter.com/version/users/lookup.format API to get the user List. Now My problem is that i want to fetch the Specific number (as per my requirement it is 16) of follower and following id's using the above two API's (friends/ids.format and followers/ids.format). But these two API's ignoring the count Parameter (suppose if i sent a request to fetch the followers of the user = sachin_rt http://api.twitter.com/1/followers/ids.json/screen_name=sachin_rtcur... it is ignoring the count parameterand returning an amount 5000 followers ID's. ) and returning a huge number of Id's. As i am developing a mobile app i don't want to store this amount of data in my database until user go for showmore/ or scroll to the bottom of the list. please let me know is there any solution to fetch the specific number of ID's of the followers/follwing. Thanks in AdvanceKamesh -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] how save twitter login?
for some of the requests u need to send either user name or userid that's why we need to store that data as well //kamesh 2011/6/14 Maksim Bunkow bim...@gmail.com Big thx!!! it came out!!! Secret it is sufficient only key and secret string, without userid. -- С уважением, Буньков Максим. bim...@gmail.com 14.06.2011, в 12:20, kamesh SmartDude написал(а): if u are using OAuth authenticationu must save u r accesstoken and access secret, usedID And useranme.u can use these details for furthur requests...when the user relogged into the application //kamesh 2011/6/14 Maksim Bunkow bim...@gmail.com I developing Desktop App and use OAuth, how save acc data for logining users without password every time? Thx. -- С уважением, Буньков Максим. bim...@gmail.com -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Follower/Friends ID's count of each request
How to limit the follower/friends i's limit..? How to resolve this issue? Could you please help me? I am waiting for your reply. Regards, George On Mon, Jun 13, 2011 at 9:57 AM, Georgooty varghese georgo...@gmail.comwrote: Dear Twitter, I want to know about the count of follower/friends count of each request. I have using cursor field in each request. In first request , cursor value set to -1. In response I got next next_cursor_str ,previous_cursor_str fields. but values are 0. *I want to limit the count of each request to 20. Is it possible ? how. For this purpose, I have using count field in query, but no hope. I got 24 id's.* *http://api.twitter.com/1/friends/ids.json?count=20cursor=-1oauth_cons umer_key=*oauth_nonce=**oauth_signat ure_method=HMAC-SHA1oauth_timestamp=1307938433oauth_token=*oauth_version=1.0user_id=14471 7423oauth_signature= Could you pleas help me.. Regards, George -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine
Amit, Your endpoint is obsolete and no longer supported by Twitter. That's why you got the 403. Statuses/followers will succeed if you change it to http://api.twitter.com/1/statuses/followers.xml https://api.twitter.com/1/statuses/followers.xml BUT this API is deprecated. Read all about it here: http://dev.twitter.com/doc/get/statuses/followers Bill On 06/14/2011 12:38 AM, Amit Battan Ror wrote: Bill Working fine : https://twitter.com/statuses/friends_timeline.xml Not Working Giving 403 Error : https://twitter.com/statuses/followers.xml On Jun 14, 10:14 am, Amit Battan Rorbatta...@gmail.com wrote: Thanks Bill I will check and try to track URL .. On Jun 13, 9:07 pm, Bill Jacobsongabe...@gmail.com wrote: Amit, also seehttp://www.mailinglistarchive.com/html/twitter-development-talk@googl That's what helped me. -Bill On 06/13/2011 10:44 AM, Bill Jacobson wrote: I'm suggesting that you find out what endpoint (Twitter URL) your app is targeting, and make sure that it matches what is currently documented. If it doesn't match, correct it. That's what worked for me. On 06/13/2011 08:05 AM, Amit Battan Ror wrote: I am not getting the solution. and my API was working fine beofre 2 3 days.. but not now.. all other API except getFollowersIncludingCurrentStatus working ok and return proper output On Jun 13, 5:53 pm, Bill Jacobsongabe...@gmail.comwrote: Amit, I don't know your library, but in my case the 403 was accompanied by the message Not authorized to use this endpoint and the solution was to update to http://api.twitter.com/1[etc.];. Bill Jacobson On 06/13/2011 05:39 AM, Amit Battan Ror wrote: any idea guys On Jun 10, 4:33 pm, Amit Battan Rorbatta...@gmail.com wrote: Hi All I am using Twitter-OAuth-iPhonehttps://github.com/bengottlieb/Twitter-OAuth-iPhone I am calling [twitterObj getFollowersIncludingCurrentStatus:NO] for getting my friend list which was working fine. But from last two days its giving me the 403 error. -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed with error: Error Domain=HTTP Code=403 The operation couldn t be completed. (HTTP error 403.) As twitter api wiki 403 is due to crossing the limit of updates and DM but here in getFollowersIncludingCurrentStatus Why this error occurring and even list is not comes next day giving same 403 error. Thanks Amit Battan -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Twitter OAuth Api Freelance Position
Looking for a Twitter API specialist. You MUST have examples of previous work integrating Twitter OAuth into a LAMP based web application. Specifically we are looking for someone who can take an existing Oauth integration and add additional features included the ability to follow users, retweet, and several other features which require credential validation. PLEASE DO NOT APPLY IF YOU DO NOT MEET THE FOLLOWING CREDENTIALS AS YOUR APPLICATION WILL BE IMMEDIATELY DELETED. THANK YOU. -US BASED -ENGLISH SPEAKING -TWITTER OAUTH EXPERIENCE -WORK EXAMPLES -REFERENCES Payment will be made via Paypal - 50% upfront 50% upon completion. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] data-lang defaults to English when it shouldn't
Hi, The data-lang currently doesn't support Portugese, which, given Brazils huge and very active Twitter community, is very surprising. So currently if you specify data-lang=pt, it will default back to English. This doesn't make sense. Portugese is to all intents and purposes very similar to Spanish. I can obviously deal with this in my code. But if in the near future, Twitter does update the language support, I would have to adapt my code (or probably forget all about it until someone points it out). So, it makes more sense for the Twitter code itself to make this shortcut. My two cents, Marc -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Search all tweets by application
Hi Taylor, thanks for the answer. I'm literally trying to do that, display all the tweets from our app. We are adding some automated text to the tweet, but since we give users the option to modify that text, we could be losing some tweets. Do you have an example of searching that tweet source? Thanks, Juan On Jun 13, 10:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Juan, There's no way to effectively retrieve all tweets sent by a given application using primary methods of any of our APIs. The Search API has some advanced operators that allow you to specify a specific tweet source (effectively the string of text that represents the application that posted the Tweet), but that operator must be used in conjunction with another portion of your query. One could also use the Streaming API to estimate a specific client's tweeting velocity by measuring from the sample hose (which represents 1% of the total tweets being posted) and extrapolate from there, but in the case of measuring a Twitter client's popularity this would not be super-effective since tweeting is just one activity that a client can perform. Is there something with that information you're specifically wanting to accomplish? @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Mon, Jun 13, 2011 at 2:12 PM, Juan Delgado zzzar...@gmail.com wrote: Hi there, I cannot find a way of retrieving all the tweets coming from a given application. For example, can I retrieve all the tweets posted using TweeDeck? Nothings comes up on the documentation or in google, any idea? Cheers! Juan -- Twitter developer documentation and resources:https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Randomly failing OAuth procedure
Hi twitter developing community, I'm using ruby( on rails) to do the oauth dance manually and finally call /1/statuses/update.json to update the status of an authorized user. Every single step during the oauth procedure is confirmed to be working. Actually I already tweeted some messages successfully. But for no obvious reason(to me), oauth sometimes fails at the very beginning while acquiring a request token. Then it just sais: Failed to validate oauth signature and token. Then I retry it several times until it (suddenly) works. The next step, i.e. exchanging the request token for an access token, works perfectly every time. But when it comes to the actual status update(i.e. calling the /1/ statuses/update.json endpoint) it sometimes fails, too, saying Failed to validate oauth signature and token. Again I just retry a few times and all of a sudden it works. I don't change the code during this testing sessions, nor do i change the text I want to be tweetet. It just doesn't work sometimes. I can't reproduce this unwanted behavior. Did Somebody have the same issue? Suggestions are also appreciated. Kind regards, Felix. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Randomly failing OAuth procedure
Hi Felix, Are you using a specific OAuth library for the OAuth portion? I would recommend adding a bit of logging around the OAuth token negotiation process.. find out the signature base string, the exact URL you're executing, and the Authorization header you're sending. Log the response code and body of the response when it fails. With the main OAuth ruby gem that's out there, some of these details are hard to come by because the values are hidden in private methods (PSA to OAuth library developers: don't do this), so you may need to monkey patch the OAuth gem here and there to debug the values. What you're mainly looking for is a specific pattern to your failed requests for a request token -- is some value not being sent correctly? Do you have some kind of problem where in certain conditions a variable you've set like your consumer key gets unset somehow? Is your system clock reliable? Is the library you're using to generate HMAC-SHA1 signatures doing the right thing? Are you using the right kind of URL encoding? Are you accidentally sending double parameters for something? Verify that you're using https://api.twitter.com/oauth/ as the base path for the OAuth negotiation steps. While there have been failures in the past in exchanging a request token for an access token due to some lag, we're not aware of anything specifically wrong with the process for fetching the request token. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jun 14, 2011 at 7:25 AM, Felix Oldenburg oldenburg.fe...@googlemail.com wrote: Hi twitter developing community, I'm using ruby( on rails) to do the oauth dance manually and finally call /1/statuses/update.json to update the status of an authorized user. Every single step during the oauth procedure is confirmed to be working. Actually I already tweeted some messages successfully. But for no obvious reason(to me), oauth sometimes fails at the very beginning while acquiring a request token. Then it just sais: Failed to validate oauth signature and token. Then I retry it several times until it (suddenly) works. The next step, i.e. exchanging the request token for an access token, works perfectly every time. But when it comes to the actual status update(i.e. calling the /1/ statuses/update.json endpoint) it sometimes fails, too, saying Failed to validate oauth signature and token. Again I just retry a few times and all of a sudden it works. I don't change the code during this testing sessions, nor do i change the text I want to be tweetet. It just doesn't work sometimes. I can't reproduce this unwanted behavior. Did Somebody have the same issue? Suggestions are also appreciated. Kind regards, Felix. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] data-lang defaults to English when it shouldn't
Hi Marc, IPortuguese is a relatively new addition to the languages supported by Twitter so some features are not fully translated yet. The team is working on getting those translations added though. If you leave the data-lang as 'pt' your button will automatically receive the translations when we add them. Best, @themattharris On Jun 14, 2011, at 6:41, mschipperheyn m.schipperh...@gmail.com wrote: Hi, The data-lang currently doesn't support Portugese, which, given Brazils huge and very active Twitter community, is very surprising. So currently if you specify data-lang=pt, it will default back to English. This doesn't make sense. Portugese is to all intents and purposes very similar to Spanish. I can obviously deal with this in my code. But if in the near future, Twitter does update the language support, I would have to adapt my code (or probably forget all about it until someone points it out). So, it makes more sense for the Twitter code itself to make this shortcut. My two cents, Marc -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Randomly failing OAuth procedure
Hi Taylor, thanks for many hints on tracking down the problem. I don't use any libraries, neither for Twitter, nor for oauth. I'm doing all by my self, thus printing out some debugging messages is fairly easy. As I'm able to do a status update some times successfully, I was sure to do everything correctly. Of cource, I inspected every detail, like the assembling of the base string and its signing. I followed http://dev.twitter.com/pages/auth and I get the same results for the base string and the final signature string, when I use the same input as in the example. Even using special characters(space, exclamation mark, and so on..) in the text of the tweet is possible, as I already tweeted some cryptic posts - containing different special chars - to my wall. So I pressume my url encoding and signing process should be correct. https://api.twitter.com/oauth/request_token and https://api.twitter.com/oauth/access_token are the paths I use for acquiring the request and access token. The system clock of my Macbook is fine, I think, but I'll check that out on detail. Maybe I should recheck my timestamp and oauth_nonce generation code, because I don't check if a timestamp, or oauth_nonce is being used twice. Though I can't imagine what could go wrong, when simply using a unix timestamp. (Oh.. is it seconds or miliseconds ruby returns when using Time.now.to_i, I'd better check that out oO!!!) I'll check the timestamp thing and if that's not the problem, I'll post some detailed debug report tomorrow. Many thanks for your inspiring reply, Felix! On 14 Jun., 17:10, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Felix, Are you using a specific OAuth library for the OAuth portion? I would recommend adding a bit of logging around the OAuth token negotiation process.. find out the signature base string, the exact URL you're executing, and the Authorization header you're sending. Log the response code and body of the response when it fails. With the main OAuth ruby gem that's out there, some of these details are hard to come by because the values are hidden in private methods (PSA to OAuth library developers: don't do this), so you may need to monkey patch the OAuth gem here and there to debug the values. What you're mainly looking for is a specific pattern to your failed requests for a request token -- is some value not being sent correctly? Do you have some kind of problem where in certain conditions a variable you've set like your consumer key gets unset somehow? Is your system clock reliable? Is the library you're using to generate HMAC-SHA1 signatures doing the right thing? Are you using the right kind of URL encoding? Are you accidentally sending double parameters for something? Verify that you're usinghttps://api.twitter.com/oauth/as the base path for the OAuth negotiation steps. While there have been failures in the past in exchanging a request token for an access token due to some lag, we're not aware of anything specifically wrong with the process for fetching the request token. @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Tue, Jun 14, 2011 at 7:25 AM, Felix Oldenburg oldenburg.fe...@googlemail.com wrote: Hi twitter developing community, I'm using ruby( on rails) to do the oauth dance manually and finally call /1/statuses/update.json to update the status of an authorized user. Every single step during the oauth procedure is confirmed to be working. Actually I already tweeted some messages successfully. But for no obvious reason(to me), oauth sometimes fails at the very beginning while acquiring a request token. Then it just sais: Failed to validate oauth signature and token. Then I retry it several times until it (suddenly) works. The next step, i.e. exchanging the request token for an access token, works perfectly every time. But when it comes to the actual status update(i.e. calling the /1/ statuses/update.json endpoint) it sometimes fails, too, saying Failed to validate oauth signature and token. Again I just retry a few times and all of a sudden it works. I don't change the code during this testing sessions, nor do i change the text I want to be tweetet. It just doesn't work sometimes. I can't reproduce this unwanted behavior. Did Somebody have the same issue? Suggestions are also appreciated. Kind regards, Felix. -- Twitter developer documentation and resources:https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your
[twitter-dev] Twitter search question
Hey all, I understand this is probably the wrong forum for this, but if you could point me in the right direction I'd be appreciative. We have a question for the search side of things. We've had some niche related sites using twitter for a long time now. Here within the last month or two we've noticed some of our accounts getting flagged as not being able to be emailed (Mail server went down) and since then accounts have been going completely missing from search. We were wondering who to talk to about this, as I've gotten a few emails on the issue and I don't know what to tell our users. Thanks! -Casey -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Error with Web Intents Javascript Events
Hey everyone, We have been trying to implement tracking on the tweet buttons that are featured on our sites. We used the method recommended to us on this page: https://dev.twitter.com/pages/intents-events Upon testing, we found that the button sends data to Omniture, our web analytics provider, when we use IE8 and Firefox to access the site, but it does not happen when using IE7. I was wondering if there may be any specific reason as to why, or what might we be doing wrong? Thanks! -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Search all tweets by application
If it's your app, why not have your app notify you of every tweet sent? On Jun 14, 10:03 am, Juan Delgado zzzar...@gmail.com wrote: Hi Taylor, thanks for the answer. I'm literally trying to do that, display all the tweets from our app. We are adding some automated text to the tweet, but since we give users the option to modify that text, we could be losing some tweets. Do you have an example of searching that tweet source? Thanks, Juan On Jun 13, 10:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Juan, There's no way to effectively retrieve all tweets sent by a given application using primary methods of any of our APIs. The Search API has some advanced operators that allow you to specify a specific tweet source (effectively the string of text that represents the application that posted the Tweet), but that operator must be used in conjunction with another portion of your query. One could also use the Streaming API to estimate a specific client's tweeting velocity by measuring from the sample hose (which represents 1% of the total tweets being posted) and extrapolate from there, but in the case of measuring a Twitter client's popularity this would not be super-effective since tweeting is just one activity that a client can perform. Is there something with that information you're specifically wanting to accomplish? @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Mon, Jun 13, 2011 at 2:12 PM, Juan Delgado zzzar...@gmail.com wrote: Hi there, I cannot find a way of retrieving all the tweets coming from a given application. For example, can I retrieve all the tweets posted using TweeDeck? Nothings comes up on the documentation or in google, any idea? Cheers! Juan -- Twitter developer documentation and resources:https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Search all tweets by application
As Orian said, if you want to know every single tweet posted by your application you need to cache them at source. There are no API endpoints which can provide this information for you. On 14 Jun 2011, at 19:43, Orian Marx wrote: If it's your app, why not have your app notify you of every tweet sent? On Jun 14, 10:03 am, Juan Delgado zzzar...@gmail.com wrote: Hi Taylor, thanks for the answer. I'm literally trying to do that, display all the tweets from our app. We are adding some automated text to the tweet, but since we give users the option to modify that text, we could be losing some tweets. Do you have an example of searching that tweet source? Thanks, Juan On Jun 13, 10:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Juan, There's no way to effectively retrieve all tweets sent by a given application using primary methods of any of our APIs. The Search API has some advanced operators that allow you to specify a specific tweet source (effectively the string of text that represents the application that posted the Tweet), but that operator must be used in conjunction with another portion of your query. One could also use the Streaming API to estimate a specific client's tweeting velocity by measuring from the sample hose (which represents 1% of the total tweets being posted) and extrapolate from there, but in the case of measuring a Twitter client's popularity this would not be super-effective since tweeting is just one activity that a client can perform. Is there something with that information you're specifically wanting to accomplish? @episod http://twitter.com/intent/user?screen_name=episod - Taylor Singletary On Mon, Jun 13, 2011 at 2:12 PM, Juan Delgado zzzar...@gmail.com wrote: Hi there, I cannot find a way of retrieving all the tweets coming from a given application. For example, can I retrieve all the tweets posted using TweeDeck? Nothings comes up on the documentation or in google, any idea? Cheers! Juan -- Twitter developer documentation and resources:https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Streaming API w/ two dedicated IP's
It is kosher to connect to the Twitter Streaming API using two dedicated IP's on two separate servers or does this violate the terms of usage? I've looked for something telling me I can't do this and nothing has cropped up, but I'd like to have this confirmed. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Streaming API w/ two dedicated IP's
Connecting from two IPs, with two different users will be perfectly fine and fall within the current rules. On 14 Jun 2011, at 20:39, @dbbradle wrote: It is kosher to connect to the Twitter Streaming API using two dedicated IP's on two separate servers or does this violate the terms of usage? I've looked for something telling me I can't do this and nothing has cropped up, but I'd like to have this confirmed. -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: Twitter search question
Hey Casey, Not all Tweets make it into our search index. For more information, check out this article on our help center: https://support.twitter.com/articles/42646. If you think your account has been affected, please fill out the form linked from the bottom of that page while logged in as the account, and we'll get back to you. Brian Sutorius Twitter API Policy On Jun 14, 9:06 am, Casey Wilson cas...@downlifesroad.com wrote: Hey all, I understand this is probably the wrong forum for this, but if you could point me in the right direction I'd be appreciative. We have a question for the search side of things. We've had some niche related sites using twitter for a long time now. Here within the last month or two we've noticed some of our accounts getting flagged as not being able to be emailed (Mail server went down) and since then accounts have been going completely missing from search. We were wondering who to talk to about this, as I've gotten a few emails on the issue and I don't know what to tell our users. Thanks! -Casey -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] illegal character in json feed
Same thing's happening to me. Check out:
http://search.twitter.com/search.json?q=%23jimromeisburningcallback=doghttp://search.twitter.com/search.json?q=%23jimromeisburningcallback=dog
Should look like this:
dog(
{
- -
results: [
- -
{
- from_user_id_str: 257702817
- profile_image_url:
http://a1.twimg.com/profile_images/1364757456/2011-05-22_13.20.33_normal.jpg
- created_at: Tue, 14 Jun 2011 20:36:33 +
- from_user: ATLienSince1987
- id_str: 80735397449183232
- -
metadata: {
- result_type: recent
}
- to_user_id: null
- text: #JimRomeIsBurning
- id: 80735397449183230
- from_user_id: 257702817
- geo: null
- iso_language_code: is
- to_user_id_str: null
- source: lt;a href=quot;http://levelupstudio.comquot;
rel=quot;nofollowquot;gt;Plume lt;/agt;
} ..
]
- max_id: 80735397449183230
- since_id: 0
- refresh_url: ?since_id=80735397449183232q=%23jimromeisburning
- results_per_page: 15
- page: 1
- completed_in: 0.185672
- since_id_str: 0
- max_id_str: 80735397449183232
- query: %23jimromeisburning
}
)
But 3/5 times it doesn't, it looks like this:
dog( � ݘYo�F ǿʚF݇Z�� 85b�)� M�č�]�� 7�w��.ےl�
҇�A�o�3�oN%��hj���7�_�2nkY�*���r� A�iH �� U��
�2 ȸ�
hϛf��X� 75�w�_� ��@ \� ńt��P �R�2 kS�I�~
`���I#�8i`�^+ Ȏ��.댡_0|���`�}�{���P:�$
���M�8`�E � e K�$Y�$N��� qs=�л��ԍ���i�� NW�E
�ȯֲ�SU~4��_��Vz0Y���,txǧNw��Cg �|VU��H���~MMf�P�sۀ�N��k�V��sP4� �WKk�g�h
�J ��n�L �i+�d1��M� � O �g�E[ʿZ� ���{�m W�g�q ���]؈ � ���9 ���֏A� ]
v9_��͔wi�CF0 a�qHE�+
Ǧ�P#� Um!�=��Y�`�T�� K+��1�� �c �2� =�� t��v߆A� $�� }� *
!b›�| �v9��h- gj( ��. ܇ �2 G���4,� � 5�DcS�
�s3FF��bɄU*f�H��O� ��4��Dd ���X �5ʍ�[0қN���B�|2h#.D�� ��7�� � A@s# ��
O� � �Ę��@љ�@ ��g� Z��py\ Iw)bA�q( ; �S$E � F/e=��O� �%� dG@*A �
m���Թ� K�J~B'?�hTɦ�Fu[I��(;c��; � �Gpʇ�E�
dQ�IH�/ �.�p �E$ �Q�L�� � ���*��Gb{4 �Y� �S��.�/$���۪ �����υ��P
�f��8�OP- ��Z͏�� `ky�'�� D��Lt���D�I� A~ 'M�[ �Od E'5�#:sڥj���
��Dz9.Z��/�� ]Q�Y�~�x d3+���f{���,� JIP�M �=� % h$���圜���m���%|���_M�
���Q�#,�*Osj�V\ �� 7B���C`�p�� r odҡ���M n�Z1�N �p(v)�|p (
�Xd���fȵP �!�@�A �p E��hW �d��*iP�fPY%5J�� �ٯ���џ�Rܶj �eW P 'ۡ� �a
� c ��3b�kc� �p��v i�O�
zB�u��K���r��.r�Do[��uq��zf�ؤ��oSu�� �TM� ۥ${��R u1 ��
E�H 5�-(=�7���ZA� ���ei8*�Tvd�TY���L�� y f�t �� = ��Z�w1�H�@�
p�*v� ~Ru�N�ܶ �C5���!j JmVC��\�� s�ptk��[ w�^2�){.��q �}���j�wI
�K�XնY��3m�Am,/o��7x8� p�` @#�ż��ʸ�/� �lv�#�� vi�-���`2娐
'�aE�Ɗ % � �/m�!�� �
D x );
Stackoverflow question:
http://stackoverflow.com/questions/6348065/sencha-touch-jsonp-error
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: illegal character in json feed
Can confirm this is happening to me too, for this request:
http://search.twitter.com/search.json?q=from%3Atfr%20OR%20from%3ASOIANYCrpp=5callback=jQuery16106527990615355083_1308086280457_=1308086281400
(I'm fetching tweets from two users - tfr and SOIANYC - if I
remove SOIANYC from the query, it returns properly-formatted data.
maybe this helps?)
On Jun 14, 9:51 pm, Mike McNeil michael.r.mcn...@gmail.com wrote:
Same thing's happening to me. Check out:
http://search.twitter.com/search.json?q=%23jimromeisburningcallback=doghttp://search.twitter.com/search.json?q=%23jimromeisburningcallback=dog
Should look like this:
dog(
{
- -
results: [
- -
{
- from_user_id_str: 257702817
- profile_image_url:
http://a1.twimg.com/profile_images/1364757456/2011-05-22_13.20.33_nor...
- created_at: Tue, 14 Jun 2011 20:36:33 +
- from_user: ATLienSince1987
- id_str: 80735397449183232
- -
metadata: {
- result_type: recent
}
- to_user_id: null
- text: #JimRomeIsBurning
- id: 80735397449183230
- from_user_id: 257702817
- geo: null
- iso_language_code: is
- to_user_id_str: null
- source: lt;a href=quot;http://levelupstudio.com;
rel=quot;nofollowquot;gt;Plume lt;/agt;
} ..
]
- max_id: 80735397449183230
- since_id: 0
- refresh_url: ?since_id=80735397449183232q=%23jimromeisburning
- results_per_page: 15
- page: 1
- completed_in: 0.185672
- since_id_str: 0
- max_id_str: 80735397449183232
- query: %23jimromeisburning
}
)
But 3/5 times it doesn't, it looks like this:
dog( ݘYo F ǿʚF݇Z 85b ) M č ] 7 w .ےl ҇ A o 3 oN% hj 7 _ 2nkY * r A
iH U
2 ȸ
hϛf X 75 w _ @ \ ńt P R 2 kS I ~
` I# 8i` ^+ Ȏ .댡_0| ` } { P: $
M 8` E e K $Y $N qs= л ԍ i NW E ȯֲ SU~4 _ Vz0Y ,txǧNw Cg |VU H
~MMf P sۀ N k V sP4 W Kk g h J n L i+ d1 M O g E[ʿZ { m W g q ]؈ 9
֏A ] v9_ ͔wi CF0 a qHE +
Ǧ P# Um! = Y ` T K+ 1 c 2 = t v߆ A $ } * !b› | v9 h- gj( . ܇
2 G 4, 5 DcS
s3FF bɄU*f H O 4 Dd X 5ʍ [0қN B |2h#.D 7 A@s# O Ę @љ @ g Z py\
Iw)bA q( ; S$E F/e= O % d G@*A m Թ K J~B'? hTɦ Fu[I (;c ; Gpʇ E
dQ IH / . p E$ Q L * Gb{4 Y S . /$ ۪ υ P f 8 OP- Z͏ `ky ' D Lt
D I A~ 'M [ Od E'5 #:sڥj Dz9.Z / ]Q Y ~ x d3+ f{ , JIP M = % h$ 圜 m %| _M
Q #, * Osj V\ 7B C` p r odҡ M n Z1 N p(v) |p (
Xd fȵP ! @ A p E hW d *iP fPY%5J ٯ џ R ܶj eW P 'ۡ a
c 3 b kc p v i O z B u K r .r Do[ uq zf ؤ oSu T M ۥ${ R u1 E H 5 -(= 7
ZA ei8* Tvd TY L y f t = Z w1 H @ p *v ~Ru N ܶ C5 !j JmVC \
s ptk [ w ^2 ){. q } j wI
K XնY 3m Am,/o 7x8 p ` @# ż ʸ / l v # vi - `2娐 ' aE Ɗ % / m !
D x );
Stackoverflow
question:http://stackoverflow.com/questions/6348065/sencha-touch-jsonp-error
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: illegal character in json feed
Thanks for all the extra info, folks -- this is very useful and I've now got
a reproducible case. We'll look into this.
Thanks!
@episod http://twitter.com/intent/user?screen_name=episod - Taylor
Singletary
On Tue, Jun 14, 2011 at 2:20 PM, Matt guitarroman...@gmail.com wrote:
Can confirm this is happening to me too, for this request:
http://search.twitter.com/search.json?q=from%3Atfr%20OR%20from%3ASOIANYCrpp=5callback=jQuery16106527990615355083_1308086280457_=1308086281400
(I'm fetching tweets from two users - tfr and SOIANYC - if I
remove SOIANYC from the query, it returns properly-formatted data.
maybe this helps?)
On Jun 14, 9:51 pm, Mike McNeil michael.r.mcn...@gmail.com wrote:
Same thing's happening to me. Check out:
http://search.twitter.com/search.json?q=%23jimromeisburningcallback=dog
http://search.twitter.com/search.json?q=%23jimromeisburningcallback=dog
Should look like this:
dog(
{
- -
results: [
- -
{
- from_user_id_str: 257702817
- profile_image_url:
http://a1.twimg.com/profile_images/1364757456/2011-05-22_13.20.33_nor...
- created_at: Tue, 14 Jun 2011 20:36:33 +
- from_user: ATLienSince1987
- id_str: 80735397449183232
- -
metadata: {
- result_type: recent
}
- to_user_id: null
- text: #JimRomeIsBurning
- id: 80735397449183230
- from_user_id: 257702817
- geo: null
- iso_language_code: is
- to_user_id_str: null
- source: lt;a href=quot;http://levelupstudio.com;
rel=quot;nofollowquot;gt;Plume lt;/agt;
} ..
]
- max_id: 80735397449183230
- since_id: 0
- refresh_url: ?since_id=80735397449183232q=%23jimromeisburning
- results_per_page: 15
- page: 1
- completed_in: 0.185672
- since_id_str: 0
- max_id_str: 80735397449183232
- query: %23jimromeisburning
}
)
But 3/5 times it doesn't, it looks like this:
dog( ݘYo F ǿʚF݇Z 85b ) M č ] 7 w .ےl ҇ A o 3 oN% hj 7 _ 2nkY * r
A iH U
2 ȸ
hϛf X 75 w _ @ \ ńt P R 2 kS I ~
` I# 8i` ^+ Ȏ .댡_0| ` } { P: $
M 8` E e K $Y $N qs= л ԍ i NW E ȯֲ SU~4 _ Vz0Y ,txǧNw Cg |VU
H ~MMf P sۀ N k V sP4 W Kk g h J n L i+ d1 M O g E[ʿZ { m W g q ]؈ 9
֏A ] v9_ ͔wi CF0 a qHE +
Ǧ P# Um! = Y ` T K+ 1 c 2 = t v߆ A $ } * !b› | v9 h- gj(
. ܇ 2 G 4, 5 DcS
s3FF bɄU*f H O 4 Dd X 5ʍ [0қN B |2h#.D 7 A@s#OĘ @љ @ g Z
py\ Iw)bA q( ; S$E F/e= O % d G@*A m Թ K J~B'? hTɦ Fu[I (;c ; Gpʇ E
dQ IH / . p E$ Q L * Gb{4 Y S . /$ ۪ υ P f 8 OP- Z͏ `ky ' D
Lt D I A~ 'M [ Od E'5 #:sڥj Dz9.Z / ]Q Y ~ x d3+ f{ , JIP M = % h$ 圜 m %|
_M Q #, * Osj V\ 7B C` p r odҡ M n Z1N p(v) |p (
Xd fȵP ! @ A p E hW d *iP fPY%5J ٯ џ R ܶj eW P 'ۡ a
c 3 b kc p v i O z B u K r .r Do[ uq zf ؤ oSu T M ۥ${ R u1 E H 5
-(= 7 ZA ei8* Tvd TY L y f t = Z w1 H @ p *v ~Ru N ܶ C5
!j JmVC \ s ptk [ w ^2 ){. q } j wI
K XնY 3m Am,/o 7x8 p ` @# ż ʸ / l v # vi - `2娐 ' aE Ɗ % / m !
D x );
Stackoverflow question:
http://stackoverflow.com/questions/6348065/sencha-touch-jsonp-error
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: illegal character in json feed
We are seeing the same problem on our latest site: http://grb.culturemap.com/senior-games/ It is intermittent; sometimes good JSON is returned and sometimes not. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: illegal character in json feed
Fyi Guys,
The way I worked around this since a try-catch was useless is that I used a
window.oneerror = function(){ to ignore the offending tweet and count errors
etc.
//mh
On Tue, Jun 14, 2011 at 6:17 PM, Paul Bailey paul.m.bai...@gmail.comwrote:
We are seeing the same problem on our latest site:
http://grb.culturemap.com/senior-games/
It is intermittent; sometimes good JSON is returned and sometimes not.
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Thank You,
Michael Hazzard
(954) 247-4461 https://www.google.com/voice#phones
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Intermittent garbled results from search API
When using the search API, I'm intermittently getting back garbled
results. With this search, for example:
https://search.twitter.com/search.json?callback=jsonp1308091691112q=from%3Atwitter+OR+to%3Atwitter+OR+%40twitterpage=1
I get the following data:
jsonp1308091691112( ‹ �� íš sÚH €ÿJ ×fw+ ÌH£ ©Ô 9vâ× WövK5H# -iˆ
±¹Ôþ÷ë ã@bc’ÛlÝQ.ÀÒúñMOO‹O \ UR ö¿5¢\¦~UˆÜ C¿(óF»A-›RfX Æ8—Qœ ?
NùPøUžàíQYŽÛ ךåUœ › L[wÚ -ª;Œ1¢1ÖšõÌdžò¤y1 â A.x)BŸ—8šW‰ ^W h„RÐ
´6³Û …§ _Ø|.!¶¾ Y GÏDRÈLûs©mb™¶aZ¶®;šnØ o¦¢ä!/y£ý©VÚ/'c
s ˆ¬lü¹Ó(å ú 65mf[¦…Wŵ’n÷r ÅY\؆ U ) ¤
ÛgG1xòRf‘(ŠXf€ »h—² 9$2™JØh/·sÇð8smó¹8ùíÜ8ÊPH¥E-þ™ŒQz4¥”y ghNåMÍl
†eì³I“˜¦õ ª ÒOx6¬” ªÞS®Mx Ô jú 3Ì çÁ€DÌ15+Ä õTA\N” ª$ñ3žªK{r’•¨èžàÁh ö
îÚñ £Ú˜Ø¹ U®kIÊç F¹ˆ^ùPÉòy
Sm±)KÛ[P^e‰äa+ dfM! IÝ+“‘L y5ûïÉ°|îÕ d ñÙ
´ NÕâê J·’sMslÍÔ z èúWA×е ‚®Ûh9Ÿj )¶4‹8ŒøÔfÌDŠuÛg3lÛ·ñ†núÙú
+‚:«W„LQ§bÄ/d¾¼ Ç0 ;j9ú#–C†Ÿ/… ^” @ 9/%¤U Ê9êw0_˜ôsÌç¯ žÍ°’Ñ¢
±ÌÔ¬ùZ4Ýr% ÷3ÁˆI‰fÜC ù ºé Ë¡zë —í÷lmL ‚Éa‡é¿½‹šd}Ï }
¥ç ‘õ{KNgŽ¦a¨1 ›Ø›:½çÁîžûþä¥ ð$IE÷]§
»Þù¡ç¹=8?p{. öáø=xÞ3|)ÓBü’çâMœ
÷ ±X ës,j«ß Eö—@¡Y”::¥æ #³c[6k¡ , c ¡ Ñt‹jŽÌˆå[Ô¦:~3}[g T
_C«Ùë cµ [ L9 Ø9ÁXq•M‚enˆcÚºA jhß‚›«XíÑ äf˜È ¢
çâ÷
¥t
µ—–0â! × §:xó UVÂö;‘ÇQ,Â-ðF»,� Ž 2švˆxVl Î G0‘ÕlÔ
\àŽæy©Zm{‚§çS ¶î@¸ ãRlºñò Š¡N
µpœ 3 `ff±Öqçät}´´Õ±èø¥¯ÆÛë žŸ, ¥c Hˆ…)ŽÆ6 Ë… ¾u{§ê ܾçöaÿðè
Ý œ½õðóô6ýê»° Úí 7›‹ ,Jó9 s ß‹À¸| WWWè!!ÊP —ÊK Êo°} Ûß ‰¥i¶mo²… Ñ*k
±Z©ð ’çẠ˜¸o eXˆ¬
æ #Ôb¦ ©1Ã挼ž bcDÈÅXbLà Ya`‰ PŒò8»ÄÝà8‚Š sfÊ /!.`{€Ag$0ËǸâ z £
£÷ Æ ž=Ä4óžó´(ùçÕ®ø¯ ”P|Œ Q€§òº|À¾çè–Áˆm pL†KŽ0 õmƒá¶fùT'
± Ë0Ö K×V‚5 ‰Èø Ï„E—éÂ7L»qZÃü R¢E±–v£ Ûÿ¸I‘i› ³6* ØxJ2, µÊ*
$¹ 5éu÷urI?„ù• Iê „£7œ ãè œ s%'èº¹ß–ë “2 ó1ÂLã eQ¬å´¥öÃÿAy$(l}
P0EÐñx«Îòºö]@9ÄTæăóÎÉI sœW ¸ïÜÞ{8™~gŠ›þÙ©wKÔ‘ëÁÛ3ð \Ø뜬éŽÜ ;’ð|
D)¦î ?†aLUûµN[Ç] S„° ÉÒçÕP#Äñ÷Î}ü\wK2Ú†±’ T„y\ ¸ó.ãc˜„Ùø†±ÿ øX–CíÛ%/
FEŠo0³çáÏ)æ4Q ÄˆÓ †R%;x‚Ú½PUш \ æ9ó¬g7 EÌê¼áM Êbk
à—q³hÂÍé¬Hä g ‡‚·ë™ÎÕ‰ âòç vëοޡmAÍ¥ŠgíÌÅŠç Ç Ø˜Ú¥ñ¿ Î Fò˜p¦3]
opDûB8{srzŽa ƒYç¥ ]·Óƒ¾‡qê—ýÎá‘Û…ž{Üyãþ
Øà »®×‡3ŒkLJ'o= ú o» qdðzîI÷ðäÕmìûB°[Ðêo ìtÊLU¶6©E: µ4M£¥ ÍÖ
Ÿ*2ð²áàÐ:ñu´ c±õëÑF[_ÍÙ«¸ ï£ÒÙ e6s ˶‰F Óð׿W„
Ó F2ç°P Æx—ò Ð ãpÚ†g ! Y‰-e c‘GxЋxR¨ÿd * ÄE Æ O!
â’à М½ áZTf¹ŽPûî»Ö 6€K Y5f°M
š–© Û´Y‹:†nâ¡ÎЙašºiÎ*™š¾V¬® ¼ŽÓc×?K„ø÷oK\ è ‡ Å
mãŠ÷v' ™ª-îžñŽ…¿—T¢
§épZ Äí³ PŒyšŠ¼€K!Æ Š¢àCµÉ¦â @„q¢Š• r�Ox:~ )¿T›% ¥ /’
´(þR ¡vÔw RÕ@=ÇTé «QjA… öêO{=`Ó$ ’aÜ ý pŒh
¥ŽÕr“q¼YduÀ 8Xá ârúÄé.XÌtLÍ´ iö˜4
wx}áYò‘ –´‹2F¤ ªlfaÅ Ì àÅ O¢ F¸uÞÜV@Á8 LD©p»Ìðr!
±Q€¹ ŠQÆÑäNœZÔai ¼qËb vûHïQ9ØTéé U£lƒ Œª§1¶£ëqœ#:ãx¸.Qú—òþc^–Güj N
% å©£ “'sCžOüQU(K¶çy:‚Õ ¦óp.ó$lC7—c¼ÄÃæí£–K$¯€YÚ è”b(ó ÄØg$Á“°? n§F4“
®Çè ^N ã C _7a{/W) .ë {ÞÖ ô ô]Úg.ü볯?Ð üÚÿ¯4Š8 Äô. œ�ý4ª1ûÇͽ Kýž|
x¡´ýIïÔ=í=-åÝÿ bäv©eèU Œz« Õç íÉL¬o1zýƒ sžz u©_‘¤ U íq†Š6©*Ú·Ê×
OCàT¦¯üä “¨|‚÷Ö’ðÏÿ�ìr9â”$��);
Is there currently a known issue?
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: illegal character in json feed
Re: error handling the jsonp script error I started using the previously mentioned window.onerror mechanism wherein I reload the iframe from which I'm initiating the jsonp call, up to 10 times, 3 seconds apart (the average delay in getting the script back from twitter, which triggers the error which in turn starts another jsonp request and so on, up to 10 times) I'm using this approach in addition to my pre-existing 5 retries on general error, 10 seconds apart non-blocking error handler which was able to survive the illegal character error on its own and recover from it, but sometimes it ended up with Sorry, try again later (twitter recovers after a while on its own and my app continues from there but sometimes the error persists with twitter.) The pre- existing handler was using more time on average (about 20-50 seconds) and the newly added window.onerror mechanism, which runs before the self-terminating, non-blocking handler loop, is taking less time on average (6-15 seconds) to go thru the same process for the jsonp script error reported by the browser. However, sometimes, this error persists for too many retries and falls out of the window.onerror but 99% of the time so far it's getting caught by my pre-existing general error handler (now, the second layer of defense) I never thought I had to double up! :) Re: illegal character Wow. Really? you can have the unicode character for delete \u0008 in the response? I have a full dump of the jsonp response in firebug and that's the character that firebug terminates at when reporting the error so I assume that's the culprit, but could be others as well. On a more relevant note, I don't think the illegal character coming back in jsonp have anything to do with the tweet's content. It looks as if some tweets contain some combination of characters that cause twitter to return a binary dump of some sort (in casual terms, it causes it to hallucinate.) Anyway intriguing. :) Marc On Jun 14, 6:53 pm, Romica iordan.rom...@gmail.com wrote: I have the same problem (bad JSON most of the times). The weird thing is that if I access the URL direct from the browser it works (good JSON every time). I'm using jQuery.getJSON and I think that this (or something connected to this) might be the problem. Unfortunately I cannot use window.onerror (as Michael suggested) because I have multiple asynchronous requests at the same time (it would be tricky and expensive to find out which one is bad - at least I suppose so). Good luck in solving this -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] 403 error on request_token [JavaScript]
Hey all, Receiving http 403 response error when trying to get a
request token.
I've checked my base string's singing process, and that's proper. If
I use the default keys on the Twitter dev site, it generates the same
result as they list on the site, so i'm pretty sure that's okay.
Any insight would be much appreciated!
var reqURL = 'https://api.twitter.com/oauth/request_token';
var reqNonce = getNonce();
var reqTimeStamp = getTimeStamp();
var reqSignatureMethod = 'HMAC-SHA1';
var reqConsumerKey = 'ySBPkqxaRlheQKFwejMpqg';
var reqConsumerSecret = 'xxx';
var reqCallback = 'oauth_callback=http%3A%2F%2Flocalhost
%3A3005%2Fthe_dance%2Fprocess_callback%3Fservice_provider_id%3D11'
var reqQuery =
'oauth_consumer_key=ySBPkqxaRlheQKFwejMpqgoauth_nonce=' + reqNonce +
'oauth_signature_method=HMAC-SHA1oauth_timestamp=' + reqTimeStamp +
'oauth_version=1.0';
var reqBaseString = 'POST' + '' + reqURL +
encodeURIComponent(reqCallback) + '' + encodeURIComponent(reqQuery);
var reqSignature = b64_hmac_sha1(reqConsumerSecret,
reqBaseString); // hasing
var reqSignature = reqSignature + '='; // adding = to end of the sig.
var request = new XMLHttpRequest();
request.onreadystatechange = function(data) {
if (request.readyState == 4) {
if (request.status == 200) {
alert ('good response');
}
}
};
request.open(POST, reqURL, true);
request.setRequestHeader(Accept, text/plain, */*);
request.setRequestHeader(Connection, Keep-Alive);
request.setRequestHeader(Authorization, OAuth oauth_consumer_key=
\ + encodeURIComponent(reqConsumerKey) + \, oauth_nonce=\ +
encodeURIComponent(reqNonce) + \,oauth_signature_method=\ +
encodeURIComponent(reqSignatureMethod) + \, oauth_signature=\ +
encodeURIComponent(reqSignature) + \, oauth_timestamp=\ +
encodeURIComponent(reqTimeStamp) + \, oauth_version=\ +
encodeURIComponent(1.0) + \, + oauth_callback=\ +
encodeURIComponent(reqCallback));
request.send();
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: illegal character in json feed
Marc, Nice theory but I'm not so sure since I'm reloading the same exact tweet (I think)over and over again and its getting corrupted. Although I've heard of type of thing before where an application (notepad) tries to do charset encoding detection but fails and outputs a corrupted file upon reopening. On Jun 14, 2011 9:24 PM, marc fawzi marc.fa...@gmail.com wrote: Re: error handling the jsonp script error I started using the previously mentioned window.onerror mechanism wherein I reload the iframe from which I'm initiating the jsonp call, up to 10 times, 3 seconds apart (the average delay in getting the script back from twitter, which triggers the error which in turn starts another jsonp request and so on, up to 10 times) I'm using this approach in addition to my pre-existing 5 retries on general error, 10 seconds apart non-blocking error handler which was able to survive the illegal character error on its own and recover from it, but sometimes it ended up with Sorry, try again later (twitter recovers after a while on its own and my app continues from there but sometimes the error persists with twitter.) The pre- existing handler was using more time on average (about 20-50 seconds) and the newly added window.onerror mechanism, which runs before the self-terminating, non-blocking handler loop, is taking less time on average (6-15 seconds) to go thru the same process for the jsonp script error reported by the browser. However, sometimes, this error persists for too many retries and falls out of the window.onerror but 99% of the time so far it's getting caught by my pre-existing general error handler (now, the second layer of defense) I never thought I had to double up! :) Re: illegal character Wow. Really? you can have the unicode character for delete \u0008 in the response? I have a full dump of the jsonp response in firebug and that's the character that firebug terminates at when reporting the error so I assume that's the culprit, but could be others as well. On a more relevant note, I don't think the illegal character coming back in jsonp have anything to do with the tweet's content. It looks as if some tweets contain some combination of characters that cause twitter to return a binary dump of some sort (in casual terms, it causes it to hallucinate.) Anyway intriguing. :) Marc On Jun 14, 6:53 pm, Romica iordan.rom...@gmail.com wrote: I have the same problem (bad JSON most of the times). The weird thing is that if I access the URL direct from the browser it works (good JSON every time). I'm using jQuery.getJSON and I think that this (or something connected to this) might be the problem. Unfortunately I cannot use window.onerror (as Michael suggested) because I have multiple asynchronous requests at the same time (it would be tricky and expensive to find out which one is bad - at least I suppose so). Good luck in solving this -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: illegal character in json feed
Hey everyone, Thanks for all the information you provided. We were able to reproduce the problem and the engineers have now released a fix. You shouldn't receive any garbled API responses anymore, if you do please let us know. Best, @themattharris On Jun 14, 7:59 pm, michael hazzard miramardes...@gmail.com wrote: Marc, Nice theory but I'm not so sure since I'm reloading the same exact tweet (I think)over and over again and its getting corrupted. Although I've heard of type of thing before where an application (notepad) tries to do charset encoding detection but fails and outputs a corrupted file upon reopening. On Jun 14, 2011 9:24 PM, marc fawzi marc.fa...@gmail.com wrote: Re: error handling the jsonp script error I started using the previously mentioned window.onerror mechanism wherein I reload the iframe from which I'm initiating the jsonp call, up to 10 times, 3 seconds apart (the average delay in getting the script back from twitter, which triggers the error which in turn starts another jsonp request and so on, up to 10 times) I'm using this approach in addition to my pre-existing 5 retries on general error, 10 seconds apart non-blocking error handler which was able to survive the illegal character error on its own and recover from it, but sometimes it ended up with Sorry, try again later (twitter recovers after a while on its own and my app continues from there but sometimes the error persists with twitter.) The pre- existing handler was using more time on average (about 20-50 seconds) and the newly added window.onerror mechanism, which runs before the self-terminating, non-blocking handler loop, is taking less time on average (6-15 seconds) to go thru the same process for the jsonp script error reported by the browser. However, sometimes, this error persists for too many retries and falls out of the window.onerror but 99% of the time so far it's getting caught by my pre-existing general error handler (now, the second layer of defense) I never thought I had to double up! :) Re: illegal character Wow. Really? you can have the unicode character for delete \u0008 in the response? I have a full dump of the jsonp response in firebug and that's the character that firebug terminates at when reporting the error so I assume that's the culprit, but could be others as well. On a more relevant note, I don't think the illegal character coming back in jsonp have anything to do with the tweet's content. It looks as if some tweets contain some combination of characters that cause twitter to return a binary dump of some sort (in casual terms, it causes it to hallucinate.) Anyway intriguing. :) Marc On Jun 14, 6:53 pm, Romica iordan.rom...@gmail.com wrote: I have the same problem (bad JSON most of the times). The weird thing is that if I access the URL direct from the browser it works (good JSON every time). I'm using jQuery.getJSON and I think that this (or something connected to this) might be the problem. Unfortunately I cannot use window.onerror (as Michael suggested) because I have multiple asynchronous requests at the same time (it would be tricky and expensive to find out which one is bad - at least I suppose so). Good luck in solving this -- Twitter developer documentation and resources:https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Twitter Button Torture!
Can you tell us which browsers you are using and explain a little bit about what you mean when you say the button doesn't 'look right'? Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Tue, Jun 14, 2011 at 7:00 PM, 3 rexes t...@threerexes.com wrote: Are there any brilliant button tweakers out there that can help??? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Twitter Button Torture!
Thanks Themattharris, I'm using Firefox. I'll see if I can add the horizontal button code to my site so you can see it. Tara -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Re: 403 error on request_token [JavaScript]
I fixed a few formatting issues with the code, here's the new
version, still produces the same 403 result.
--
var reqURL = 'https://api.twitter.com/oauth/request_token';
var reqNonce = getNonce();
var reqTimeStamp = getTimeStamp();
var reqSignatureMethod = 'HMAC-SHA1';
var reqOauthVersion = '1.0';
var reqConsumerKey = 'ySBPkqxaRlheQKFwejMpqg';
var reqConsumerSecret = '___' // note the at the end..
var reqCallback = 'http%3A%2F%2Flocalhost%3A3005%2Fthe_dance
%2Fprocess_callback%3Fservice_provider_id%3D11'
var reqQuery = 'oauth_callback=' + reqCallback +
'oauth_consumer_key=' + reqConsumerKey + 'oauth_nonce=' + reqNonce +
'oauth_signature_method=' + reqSignatureMethod + 'oauth_timestamp='
+ reqTimeStamp + 'oauth_version=' + reqOauthVersion;
var reqBaseString = 'POST' + reqURL + '' +
encodeURIComponent(reqQuery);
var reqSignature = b64_hmac_sha1(reqConsumerSecret, reqBaseString);
var reqSignature = reqSignature + '=';
var request = new XMLHttpRequest();
request.onreadystatechange = function(data) {
if (request.readyState == 4) {
// Good response, got the xml file
if (request.status == 200) {
alert ('good response');
}
}
};
// alert (reqURL);
// alert (reqBaseString);
var oauthParams = encodeURIComponent(OAuth oauth_callback=\ +
reqCallback + \,oauth_consumer_key=\ + reqConsumerKey +
\,oauth_nonce=\ + reqNonce + \,oauth_signature_method=\ +
reqSignatureMethod + \,oauth_timestamp=\ + reqTimeStamp +
\,oauth_version=\1.0\,oauth_signature=\ + reqSignature + \);
request.open(POST, reqURL, true);
request.setRequestHeader(Accept, text/plain, */*);
request.setRequestHeader(Connection, Keep-Alive);
request.setRequestHeader(Authorization, oauthParams);
request.send();
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Twitter Button Torture!
Hey Tara, Nothing changed our side so it sounds like your browser was the cause. Either way, glad you got it working. Best, @themattharris https://twitter.com/intent/follow?screen_name=themattharris Developer Advocate, Twitter On Tue, Jun 14, 2011 at 9:38 PM, 3 rexes t...@threerexes.com wrote: Themattharris, somehow you fixed it. I spent a good 2 hours trying to figure this out, and now it looks normal. Maybe my browser needed to shut down re-start? Here it is looking normal http://www.threerexes.com/Shop/NecklacePage/Empress-Silver-Gothic-Choker-Necklace.htmlI need to hire a website tech! Thanks!!! -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
