[twitter-dev] oAuth problems with GET params - Incorrect Signature

2011-04-03 Thread estrazulas
After autentication using oAuth Adapter (http://developer.appcelerator.com/blog/2010/07/twitter-oauth-implementation-for-titanium-mobile.html), i need use verify_credentials method. This method require GET params. I change code here: var params = ?true=1; for (var p in parameterMap) {

[twitter-dev] OAuth Problems

2010-10-12 Thread Sergio Oropeza
Hi! i'm programming basic http post for twitter. I allready have my applicaton in the app's of twitter developers. Ihave the Consumer key, Consumer secret, Access Token (oauth_token) and Access Token Secret (oauth_token_secret) Here is my code: POST /1/statuses/update.xml HTTP/1.1 Host:

[twitter-dev] Oauth problems?

2010-09-10 Thread MTCoder
i have written code (working code for a client app) up to the point of posting/reading to a twitter timeline. The user has allowed my app access and i have the token and token secret. Also i have double checked the signature and everything else and they all seem correct (

[twitter-dev] OAUTH problems!

2010-05-17 Thread Feras Allaou
Hello I was using Abraham Library for OAUTH , but since yesterday I faced a lot of problems,So I decided to build my own library for OAUTH ! But until now , I couldn't find any sources to make me understand the whole issue ! could anyone help plz ? Regards, Feras Allaou

Re: [twitter-dev] OAUTH problems!

2010-05-17 Thread Abraham Williams
What problems were you running into? Abraham On Mon, May 17, 2010 at 10:24, Feras Allaou feras.all...@gmail.com wrote: Hello I was using Abraham Library for OAUTH , but since yesterday I faced a lot of problems,So I decided to build my own library for OAUTH ! But until now , I couldn't

[twitter-dev] oAuth Problems - 9:36AM EST

2009-04-09 Thread Jason Korkin
Woke up this AM and went to check on a few things on our site... found that all of the oAuth keys had been de-authorized that we had saved in our database. When I went to re-authorize, I got this error: Woah there! This page is no longer valid. It looks like someone already used the token