[twitter-dev] Q: Twitter:warning response on search
Hi Started getting the following warning recently on a Twitter search appliance I built twitter:warningadjusted since_id to id value (2010-10-13 18:00:00 UTC), requested since_id was older than allowed/twitter:warning A sample query which gives the above warning contains the following name value pairs- q tagsome search string or hashtag here lang 'en' since '2010-010-20' 12:27:26 '2010-010-20' rpp '100' Has something changed in the Twitter search API? Can someone enlighten 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-dev] Warning on search requests- has the Search API changed?
Hi Started getting the following warning recently on a Twitter search appliance I built twitter:warningadjusted since_id to id value (2010-10-13 18:00:00 UTC), requested since_id was older than allowed/twitter:warning A sample query which gives the above warning contains the following name value pairs- q tagsome search string or hashtag here lang 'en' since '2010-010-20' 12:27:26 '2010-010-20' rpp '100' Has something changed in the Twitter search API? Can someone enlighten 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-dev] Q: Twitter:warning response on search
Hi Started getting the following warning recently on a Twitter search appliance I built twitter:warningadjusted since_id to id value (2010-10-13 18:00:00 UTC), requested since_id was older than allowed/twitter:warning A sample query which gives the above warning contains the following name value pairs- q tagsome search string or hashtag here lang 'en' since '2010-010-20' 12:27:26 '2010-010-20' rpp '100' Has something changed in the Twitter search API? Can someone enlighten 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-dev] Search API...searching for videos
Hi Currently in beat and viewable at http://www.tweetmasher.com, I am building a Twitter search application and slowly adding new features. One thing I would like to add is the ability to search for video links. Can anyone offer suggestions on what I would use in my search query? I assume the links would be mostly youtube videos.
[twitter-dev] Search API...searching for videos
Hi Currently in beta and viewable at http://www.tweetmasher.com, I am building a Twitter search application and slowly adding new features. One thing I would like to add is the ability to search for video links. Can anyone offer suggestions on what I would use in my search query? I assume the links would be mostly youtube videos.
[twitter-dev] Search and 502 bad gateway status
I notice that I sometimes get a bad gateway status 502 error. When I replicate the search using the Advanced search page, say with only a 'from user', and geocode and since date specified, I also get the 502 error with the Twitter unavailable page. However, if I simply remove some of the undefined query parameters from the search stringit works. Is there a limit in the number of search query parameters??
[twitter-dev] Whats wrong with this search query???
Hi Perplexed as to why I get an 'invalid parameter' returned with the following http://search.twitter.com/search.atom?q=cyclingfrom=ref=lang=ennear=torontowithin=50units=misince=2010-03-09+10%3A51%3A44rpp=100 If I remove the query location info 'near=torontowithin=50units=mi' it works. But when I do the exact same search on Twitter's advanced search page I get the exact same location query string 'near=torontowithin=50units=mi' except it DOES work
[twitter-dev] Re: Whats wrong with this search query???
ok weird For location based searches, I need to change search.atom?q to simply search?q Does anyone know why?
[twitter-dev] Re: Whats wrong with this search query???
more confusion In the Twitter Search api documentation under operators it states near: cannot be used in API search ?? But why is it clearly visible in the query string when using the advanced search page?
[twitter-dev] Re: Whats wrong with this search query???
ok so apparently you must convert locations to a gecode first. Can anyone tell me the best way to do this?
[twitter-dev] web application launch...Tweetmasher
http://tweetmasher.com/ At the moment mostly 3d window dressing on the Twitter search api...but slowly adding new features.
[twitter-dev] Help search works but retrieving user info doesn't...
Hi I'm building a search application in Flash and have encountered a security error when retrieving a user's information using the following... http://api.twitter.com/1/users/show.xml?screen_name= I noticed a crossdomain.xml file returned with the above. This works http://search.twitter.com/search.atom? Can anyone suggest a solution?
[twitter-dev] icon size issue
Anyone know what the eta is for fixing the icon size issue? I just came across 1 that was 432X432 pixels!!! Obviously won't work for mobile...
[twitter-dev] Re: Time to whitelist??
I am only using the Search API, in conjunction with statuses show. http://api.twitter.com/1/statuses/show But do get the error message mentioning 150 maximum requests per IP per hour.
[twitter-dev] Search API..receiving the refresh_url
Hi If you do a search from the official twitter search page, every 10-20 seconds or so, you receive a json response with a refresh_url. I'm building my own Twitter search appliance and want to incorporate this feature. How can I receive this refresh url after every search and is there a way to change the interval that it updates?
[twitter-dev] Why No Chinese in advanced search site?
Just curious why chinese is not a language option in the advanced search page?
[twitter-dev] Search API and total number of matches
Hi You determine the number of tweets per age using the 'rpp' query parameter, with a maximum of I believe, 100 tweets per page, but is there also a way to determine the total number of 'matches' for a given search query?
[twitter-dev] Re: Twitter search history
Hi mark Good question and I haven't been able to get a definitive answer. Originally I thought it should be possible to search back to twitter's birth. Recent tests with the Search API though I haven't been able to go back further than 1 week from today's date. If you DO find an answer, would appreciate if you pass along
[twitter-dev] inconsistency in User Icon pixel sizes and file formats.
Hi In building a twitter search application I was surprised to find out that there is a inconsistency in User Icon actual pixel sizes. Is there any reason for this? Why can't Twitter automatically resize image icons if they are too large? And better yet, convert the occasional .bmp format into .jpg?
[twitter-dev] Questions regarding earliest search date
Hi What is the earliest search date? If I use this date, do I need to remove any date limited search parameters from my query string, such as filter and lang to avoid getting an error?
[twitter-dev] Is Twitter Search limited to past 7 days only?
Hi This is related to a previous post but since I haven't received any response wanted to make a new post. Is Twitter Search API limited to past 7 days only? Or does it vary according to the actual hashtags, search terms used?
[twitter-dev] Advanced search query string alternatives
Hi I'm confused about the differences in query string parameters if you use the advanced search page vs referencing the Twitter search operators page http://search.twitter.com/operators Are both of the following equivalent? http://search.twitter.com/search?q=ands=phrase=near+city http://search.twitter.com/search?q=%22near+city%22;
[twitter-dev] Twitter error requested since_id was older than allowed but not using 'since_id'
Hi Can someone tell me why I seem to sometimes get an erroneous Twitter warning that 'since_id was older than allowed' when I'm not using 'since_id'?? I'm only using 'since'
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
thanks will try that I know there is the beginners guide to OAuth on the OAuth site, but came across this excellent walkthru on Vimeo's site http://www.vimeo.com/api/docs/oauth
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Ryan Still 'Incorrect signature' Here's my BASE signature query string BEFORE % encoding (NOTE all SORTED and asterisks for my consumer key!) oauth_consumer_key=oauth_nonce=16EAFA36-2A91-32A5-4A5C-6BB80EF9B45Boauth_signature_method=HMAC- SHA1oauth_timestamp=1264527609oauth_token=9353572- G8h52Icbe0cjWIMl59fepUofRxoHzHznhzEwo9oqIstatus=having some fun getting OAuth and the Twitter api working This is my final request URL, the %253D at the end of my signature looks suspect, doubly encoded? But pretty sure worked with verify credentials request.url==http://www.bitstream.ca/twitter/proxy.php?path=http%3A%2F %2Ftwitter.com%2Fstatuses%2Fupdate.json%3Foauth_consumer_key %3D%26oauth_nonce %3D16EAFA36-2A91-32A5-4A5C-6BB80EF9B45B%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1264527609%26oauth_token%3D9353572- G8h52Icbe0cjWIMl59fepUofRxoHzHznhzEwo9oqI%26oauth_signature %3D5QuhEDae4gZHAxel8JVwLwkQ5J4%253D
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Ryan Since its a POST its part of my request.data. Didn't think I also needed as part of my query string but will try. Do you know if there is an official Twitter Oauth test page like http://developer.netflix.com/resources/OAuthTest or Google's? http://oauth.googlecode.com/svn/code/javascript/example/signature.html Tried both and getting a different signature value, so my next question is If I receive information back on verify credentials (and no 'incorrect signature' error), am I safe to assume my signature generation is corect?
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Also noticed, minor thing, but your signature ends in '%253d' Mine in uppercase '%253D'
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Hi Ryan Changed to 'GET' and it seems I still get the Incorrect signature. error And the second time I try to update status, I also get 'This method requires a POST.' error.
[twitter-dev] Re: getting more information than 'Could not authenticate...'
Hi Michael Good point. Actionscript 3. Chices are Twitterscript and Tweetr. As far as I know, Twitterscript has no example using OAuth. And Tweetr has no example of working with browser based web authentication WITHOUT also requiring the PIN handshake. If you think I am wrong in NOT choosing either of the above, would appreciate your rationale. After some research, decided to use as a base what Sonke Rohde has done http://soenkerohde.com/2010/01/twitter-as3-oauth-lib-with-flex-4-example/ Sonke's example is Flex4 and for an AIR application, so I've modified it quite a bit to work for an Actionscript only web application. Sonke in turn is using code this open source project to create requests, generate signatures http://code.google.com/p/oauth-as3/ The fact that I've gotten OAuth to work up to the point of verify credentials working would seem to indcate that I am at least on the right path. And I've learned a heck of a lot as well;) Perhaps what I'm trying to do isn't possible (ie creating browser based web OAuth authentication WITHOUT also requiring the PIN handshake) but I'm determined to find out if this is the case.
[twitter-dev] 'Incorrect signature' on status update with OAuth when verify credentials works
Almost there... Already googled this error and changed my request from http to https. Still getting same error... Any suggestions?
[twitter-dev] Re: 'Incorrect signature' on status update with OAuth when verify credentials works
Thanks Ryan I'll have to look into signature creation more closely. Essentially, if I understand correctly, I am most likely missing the status parameter BEFORE creating the signature. Would I need to include the status value as well, or is only the parameter name necessary to create the signature?
[twitter-dev] getting more information than 'Could not authenticate...'
Hi I've spent the last week getting the OAuth sign-In process to work, and I've finallly got it to work(verify credentials correctly returns a user's info), BUT, I am unable to update a user's status. The server always returns 'Could not authenticate...' For obvious reasons, Twitter's server can't return a more specific error message. Is there any way of communcating directly with someone on Twitter's server side (ie a real person), so I can pinpoint exactly why I'm not being authenticated? might save me another 1-2 weeks of hair pulling...
[twitter-dev] Forbidden 40 error with OAuth....SOLVED
Ok Several days of hair pulling but this is what I discovered. When you navigate to the twitter OAuth authticate or authorize page, Twitter sets several cookies. One of these is _twitter_sess If you successfully sign In, this is recorded in the session cookie. If you happen to go back and re-initiate the sign In process (click sign in with Twitter ' on your application). When you get to the Twitter OAuth authorize page, this session cookie will already indicate that you have signed in And clicking the signIn button will always give you the 403 error. Solution? haven't tried, but think some variation of simply deleting this session cookie when you load your application page...
[twitter-dev] Re: Forbidden 40 error with OAuth....SOLVED
ok, think you may need to delete ALL the twitter cookies..need more testing
[twitter-dev] Better understanding of 'signature'
Hi My OAuth sign In process is failing to verify my signature, so I thought I should at least ensure I understand the meaning of the term. Every time my web application launches, it generates a unique signature, which doesn't change for the current session. ie, if I quit the application, then restart, a new signature is generated. This signature should be appended to the end of my initial request token request my access token request my verify credentials request and my status update requests. Am I correct in the above?
[twitter-dev] Verify credentials and verified =false
Trying to troubleshoot Oauth sign in. I get an access token returned, and when I request to verify credentials, I DO get all the correct info EXCEPT verified =false; Can anyone tell me the possible sources for this message? Invalid signature, or?
[twitter-dev] Re: Better understanding of 'signature'
Thanks Ryan
[twitter-dev] Not getting correct access token when using OAuth for sign in
Hi I'm building a flash web application and attempting to get the OAuthSignIn working WITHOUT use of a PIN. I've been told this is possible. http://groups.google.com/group/twitter-development-talk/browse_thread/thread/df3b49523256aaea Immediately after receiving what should be the access token I use verify credentials to verify the access toekn. Verified is always false. This is my request to get the access token (before URL encoding and appending to the url targeting my php proxy) http://twitter.com/oauth/access_token?oauth_consumer_key=QGs6W7DlEx9Q3Ay4DzI0Wgoauth_nonce=70CF413B-CAFE-7B50-2C22-52189FA42108oauth_signature=Agrs1YzPaZ811ptkDGXo%2FCOfWwk%3Doauth_signature_method=HMAC-SHA1oauth_timestamp=1264097730oauth_token=0yoGnyLb1UW37vacZKpzxbTcYmCYm1EUlT3ODp8Y Can anyone tell me if there is anything obvious missing or incorrect? What are the troubleshooting steps when your acces token can't be verified? Thanks in advance!
[twitter-dev] temporarily overloaded 503 Service Unavailable
Noticing quite a few ' temporarily overloaded 503 Service Unavailable messages when trying to log in lately. I assume Twitter is aware of and trying to correct this, but in the meantime, when building applications, are there any guidelines or best practices to follow when your application is presented with a 503 status? SImple tell the user 'the service is unavailable, please try again later'? Or perhaps a more detailed message, explaining why the service is unavailable?
[twitter-dev] Obtaining access token WITHOUT using a PIN
Hi According to the offcial OAuth spec, in order to obtain an access token, the consumer request MUST contain the following parameters 1 oauth_consumer_key:The Consumer Key. 2 oauth_token:The Request Token obtained previously. 3 oauth_signature_method: The signature method the Consumer used to sign the request. 4 oauth_signature: The signature as defined in Signing Requests (Signing Requests). 5 oauth_timestamp: As defined in Nonce and Timestamp (Nonce and Timestamp). 6 oauth_nonce: As defined in Nonce and Timestamp (Nonce and Timestamp). I'm developing a web application in Flash and hence, NOT using the extra pin handshake. (at least I've been told it wasn't necessary, my Application Type is defined as 'Browser'). So far, I've been unsuccessful, 'verified'= false in my access token request handler. Can someone cofirm for me that I in fact don't need the PIN, and if so, do I need to explicitly define all six parametres above in my request? Thanks for any feedback!
[twitter-dev] please help - sporadic '403 Forbidden:' error message when using OAuth Sign-In process
Building an actionscript Twitter client and using OAuth for the sign in process. Having an extrememely frustrating issue with a sporadic error message. '403 Forbidden: The server understood the request, but is refusing to fulfill it.' I'm using, of necessity, a php proxy to get to the Twitter oauth authenticate page at twitter.com/oauth/authenticate/ I get here no problem so I'm assuming there's nothing wrong with my proxy script. However, immediately AFTER clicking 'Sign In' I sometimes get the error message. Also, when I am getting the message, I can even leave the username and password fields blank and click 'Sign In'. I still get the error message, instead of a correct message indicating that the username- password fields are missing. Because this error only seems to happen sporadically, without me having changed anything in my code, it makes it difficult to troubleshoot properly. Anyone else experience this?
[twitter-dev] Re: please help - sporadic '403 Forbidden:' error message when using OAuth Sign-In process
Hi Ryan yeah but didn't get any response so thought my question was not clear enough and required more detailed information, hence the new post. Will make an effort to be more parsimonious moving forward... Actually in testing in Firefox I additionally get a 'Service Temporarily Unavailable' 503 as well as the 403 Forbidden error, so I'm wondering if this is in fact a server issue...
[twitter-dev] Re: please help - sporadic '403 Forbidden:' error message when using OAuth Sign-In process
also think it may have something to do with the HTTP_REFERER header not being explicitly defined in my simple php proxy $url = $_GET['path']; readfile($path); Unfortunately not a php guru so will need more detective work.. Once I resolve will suggest adding to the wiki to benefit other developers...
[twitter-dev] 403 Forbidden: error solved....sort of
I'm using the OAuth Sign In process with a flash browser-based application The following 2 steps ALWAYS work after I click my 'Sign In with Twitter' button, I make it to the Twitter OAuth sign in page so I have the correct request token, etc 1 successfully retrieve request token 2 navigate to Twitter's OAuth login page (following url isn't my actual URL but represents the actual path visible in the browser) http://www.mydomain.com/twitter/proxy.php?path=http%3A%2F%2Ftwitter.com%2Foauth%2Fauthenticate%3Foauth_token%3DiANj2mAYxOwSw9jf1868XmDSSeNZH2UFyB3mioyX5Q But the ONLY way I can proceed further (ie clicking 'Sign In' on the Twitter Oauth sign in page) without getting the 403 error is if the browser has just launched BEFORE navigating to the Twitter OAuth sign in page. Let me explain... ie I have a separate duplicate compiled version of my application on my desktop where I click the 'Sign In with Twitter' button to start the login process. It targets the same php proxy script, retrieves the request token, then issues a navigate to URL command which launches a new browser window, or in this case, launches the browser. Clicking signIn now works correctly, no 403 error Other wise(if the browser has ALREADY been open BEFORE I get to the twitter OAuth Sign In page) I get the 403 forbidden message, even if the username-password fields are blank. What gives? I am totally stumped This occurs in BOTH Safari and Firefox in OSXso I can assume its NOT a browser issue Perhaps a cookie issue...or something to do with my php proxy??? any suggestions welcome...
[twitter-dev] callback URl locked out??
working on a twitter client using OAuth, had it working up to the authorize and callback point Now getting a 403 error 403 Forbidden: The server understood the request, but is refusing to fulfill it. Is it possible my callback URL has been locked out? If so, how do I reset it?
[twitter-dev] Sign in with Twitter and oauth/authenticate
I've registered a new application and trying to get the sign in with twitter workflow working. I've defined my application type as 'Browser' since I want Twiiter to automatically redirect the user back to the application URL after sign- in and user authorization (ie NO PIN handshake). Ive also defined my Callback URL as being the same as my Application Website URL. In the wiki it mentions that 'To take advantage of Sign in with Twitter, applications should send request tokens in the oauth_token parameter to oauth/authenticate instead.' http://apiwiki.twitter.com/Sign-in-with-Twitter But in my application settings I see the Authorize URL as being http://twitter.com/oauth/authorize with no option for changing... Can someone clarify if this is an error in the wiki, or should I simply use 'http://twitter.com/oauth/authenticate' and ignore what it says in my Application Details page? Thanks in advance!
[twitter-dev] OAuth workflow and verify_credentials (http://twitter.com/account/verify_credentials)
Slowly making my way to Twiter-OAuth mastery Broken down into 4 steps and 3 server requests, this is my understanding of the OAuth workflow 1 user/consumer obtains request token http://twitter.com/oauth/request_token 2 user/consumer is redirected to twitter-OAuth url http://twitter.com/oauth/authorize 3 after authorization, user is redirected back to consumer (application) previously defined as callback URL in aplication details page, along with user authorized request token. 4 consumer(application) exchanges user authorized request token for an access token http://twitter.com/oauth/access_token NOW the user can make updates to his her twitter account http://twitter.com/statuses/update.json My question is, when is verify_credentials necessary? Does it need to be called immediatley AFTER obtaining the access token, or is it optional? http://twitter.com/account/verify_credentials.json
[twitter-dev] Re: OAuth workflow and verify_credentials (http://twitter.com/account/verify_credentials)
Thanks Abraham! In that case I will call it automatically after obtaining the access token.
[twitter-dev] Re: Sign in with Twitter and oauth/authenticate
yeah thanks Just curious why that isn't displayed as an option in my Application details page... Might cause some confusion for anyone who hasn't read the wiki in detail.
[twitter-dev] oauth/authenticate authorize broken?
Puzzled by a recurring , but sporadic problem. When trying to sign in at the Twitter Oauth url http://twitter.com/oauth/authenticate or http://twitter.com/oauth/authorize even if I leave my input form fields blank, when clicking 'Sign In' I get a browser error message 403 Forbidden: The server understood the request, but is refusing to fulfill it. instead of an 'incorrect username, password' message. Anyone else experience this?
[twitter-dev] Q: Retrieving and purpose of authenticity_token
Hiu Am building an AS3 based twitter client. Once the user has authorized access at the Twitter OAuth sign in page, 1 Twitter returns an oauth_token and an authenticity_token 2 Twitter redirects the user back to the application URL, appending the oauth_token to the application url. My question is, since by default I am in a new browser window at the authorization stage, how do I retrieve this authenticity_token? Basically after sign In-authorization and returning to my application, ALL I have is the oauth_token stripped from the URL. What is the purpose of the authenticity_token? Is it just application and NOT user specific? Don't I need an access token IN ADDITION TO this oauth_token returned? Thanks in advance!
[twitter-dev] OAuth best practice
I'd like to embed the Twitter OAuth authorization-sign in window WITHIN my application. Is this considered a best practice, or is it always recommended to send the user to a new browser window for the service provider(Twitter in this case) OAuth authentication process?
[twitter-dev] authenticity_token same as access token?
Hi Can someone confirm or deny whether the authenticity_token returned is the same as 'access_token' referred to in the documentation? Thanks in advance!
[twitter-dev] Re: Sign in with Twitter, PIN authentication and Desktop Clients
Thanks Ryan On Jan 17, 5:38 pm, ryan alford ryanalford...@gmail.com wrote: 1. Desktop applications are those that are installed or ran from a PC /Mac/Linux or on a mobile device. They are outside of the browser. 2. One is used for web applications, the other is for desktop applications. 3. You are correct. PIN workflow is only for desktop applications. Ryan Sent from my DROID On Jan 17, 2010 5:00 PM, eco_bach bac...@gmail.com wrote: Hi Building an AS3 based web application using OAuth. So far I've coded a demo that successfully obtains a request token, redirects the user to the oauth url, and, on successful login redirects the user back to the previously supplied consumer- application URL. However somewhat confused by several things. 1)Definition of Desktop Clientshttp://apiwiki.twitter.com/Authentication Is a desktop client any web based application? or does it specifically refer to any application OUTSIDE of the browser (ie AIR based)? 2) SignIn with Twitter Can someone explain the difference between 'oauth/authorize' and 'oauth/authenticate' urls? What is meant by 'normal flow' (2nd paragraph) herehttp://apiwiki.twitter.com/Sign-in-with-Twitter 3) PIN handshake My assumption is that the extra PIN handshake is ONLY necessary for what I understand to be desktop clients (ie #1 above) So 'Sign in with Twitter' for a web-based application shouldn't require the extra PIN handshake. Am I correct? Thanks for any feedback on the above!
[twitter-dev] List of Common Error messages and possible causes, ie 'Failed to validate oauth signature and token'.
Hi I've read the FAQ, and all the documentation. Am attempting to get an AS3 client working using OaUth. I am getting the following error message 'Failed to validate oauth signature and token'. tried resetting my consumer key, secret, and also checked my system clock which seems fine. After a quick search this seems to be a VERY common error message with many possible causes. Is there a list somewhere of common error messages such as this with probable causes?
[twitter-dev] Failed to validate oauth signature and token
Ok Yes this IS a common error message. I've read most of the posts, the entire OAuth beginner's documentation, registered my application, checked for capitalization , checked my system clock. So far, no luck As a base library I am using Sönke Rohde's open source Twitter library http://github.com/srohde/Twitter, though might switch to Tweetr and see if I make better progress. This is my header GET /oauth/request_token? oauth_consumer_key=C4eEz9MqGy28wuCj8hJC4woauth_nonce=0020a00%2001oauth_signature=gX9Uk20RF70D6sxljfvcIK4szr4%3Doauth_signature_method=HMAC- SHA1oauth_timestamp=1263675366 HTTP/1.1 Also , I am testing from the desktop at the moment so needing a proxy for security sandbox issues isn't a problem. Can anyone help with troubleshooting?
[twitter-dev] Re: Failed to validate oauth signature and token
solved, apparently my oauth_nonce value was incorrect, I assumed it was simply a random string and I didn't use the mx.utils.UIDUtil class to generate. I'll try also switching the order so the signature is at the end.
[twitter-dev] AS3 library comparison
For a personal project I am building an AS3 only web based Twitter search and client application. According to Twitter's FAQ, they recommend using Oauth moving forward as a means of authentication. But from what I've seen (and please correct me if I'm wrong), 3rd party libraries (Tweetr, twitterscript, SWX) don't yet implement OAuth. Is anyone aware of any objective comparison between the various Actionscript Twitter libraries available? And can anyone point me to any live as3 web applications currently using Oauth?
[twitter-dev] Re: AS3 library comparison
Thanks Yes, I've seen Sönke's post on a Flex4 AIR based twitter app. Also came across a tutorial using OAuth with the Tweetr library, but confused about the extra handshaking apparently needed to enter the PIN for a web application. I thought this was only necessary for a desktop-AIR application...will need to investigate more...
