@dissonance: let me know if you have any suggestion
@scotopia, hey, Thanks! nope, its not open auth.
I was looking for you, could you manage time on using open auth with iphone? I was totally lost in the open auth section on twitter site...
Yeah I got oAuth working with regular twitter updates; unfortunately image services like twitpic, yfrog etc don't do oAuth with their API so i've had to fall back on basic auth for those. Basically I just modified ben gottlieb's engine here: bengottlieb's Twitter-OAuth-iPhone at master - GitHub
@alon7:
When you add the folders to your project, you have to select 'copy' instead of reference. It worked with me anyway.. here is sample project. What I have done here:
1. Created a new project.
2. from xcode added the TwitterAgent and the BusyAgent folders to the project. Selected copy.
3. added a button to the view.
4. added a touch event inside handler for the button.
5. in the handler code, i used the twitter agent.
btw, don't forget to import TwitterAgent.h where you want to use this.
FacebookAgent and TwitterAgent are very cool,
Is very easy to use, packaged very well.
Thank you for sharing such a good code, so that Facebook and Twitter's programming has become so relaxed and happy.
Very much hope that TwitterAgent can easily upload Image, hope to see even better updates, Thanks again.
The percent sign was missing, and that broke it. You'd get Tiny URLs, but they didn't go anywhere, because it was generating TinyURLs for the link "@" instead of what was intended.
Now, could someone find that one other bug in the Facebook agent for me, that was the limit of my brain power!
I really like your popup dialogs, similar to BiteSMS txt input dialog. I may be 'liberating' that code.
I'd suggest implementing xAuth authentication, which in my opinion is better that oAuth as you can control user/pass input and token management yourself.
Like OAuth xAuth uses a one-off token exchange when the user authorises you app at first use.
xAuth requires you to contact twitter (via email) and perform registration of your app. Twitter posts then say 'from myApp'. Twitter took around a day to respond to my request and authorise my app for xAuth. Until authorised you just get a network error (401 ?) if you try and connect using xAuth.
There is a xAuth framework written and published under MIT license
This framework is itself made up of MGTwitter etc, so I'm sure the author would have no issues with incorporating the authentication section into your own framework - assuming the code was published under the same open license.
I implemented twitter using this xAuth framework and must say it works really well. I used keychain to store the exchanged token, and provided a way to log out which simply deletes the token from the keychain - next access see's there's no token and requests login/authentication again.
Last edited by funkyspider; 04-21-2010 at 04:06 AM.
xAuth - you have to register app with twitter and request xAuth access (via email - link on that blogg page) and control your own login view.
OAuth - handles the login for you if the app hasn't been authorised. You do not have to register your app with twitter via Email. This is the OAuth login page which is automatically displayed. http://blog.trapster.com/wp-content/...tter-oauth.png
Using xAuth/oAuth all you actually store is the single token value which is given to you when the user authorises.
As you are only storing a token value which has been returned from you can hard code the username as 'twituser', the serviceName as 'twitter' etc when using the getPasswordForUsername/ storeUsername / deleteItemForUsername methods. The token is then just stored as the password.
I really like your popup dialogs, similar to BiteSMS txt input dialog. I may be 'liberating' that code.
I'd suggest implementing xAuth authentication, which in my opinion is better that oAuth as you can control user/pass input and token management yourself.
Like OAuth xAuth uses a one-off token exchange when the user authorises you app at first use.
xAuth requires you to contact twitter (via email) and perform registration of your app. Twitter posts then say 'from myApp'. Twitter took around a day to respond to my request and authorise my app for xAuth. Until authorised you just get a network error (401 ?) if you try and connect using xAuth.
There is a xAuth framework written and published under MIT license
This framework is itself made up of MGTwitter etc, so I'm sure the author would have no issues with incorporating the authentication section into your own framework - assuming the code was published under the same open license.
I implemented twitter using this xAuth framework and must say it works really well. I used keychain to store the exchanged token, and provided a way to log out which simply deletes the token from the keychain - next access see's there's no token and requests login/authentication again.
Location: iTunes store : Scrambleface otherwise Scotland
Posts: 262
Hi it all works fine for me apart for when I want to pass in my own values as below - I get the error message 'too many arguments to function twit' - does anyone know how to sort this - thanks