[twitter-dev] Implement a Twitter friends finder (like in instagram)

2010-12-21 Thread Mathieu
Hello,

I have an iphone application with its own authentication system: users
have to provide their login and password, nothing is related to
twitter.

I would like to develop a twitter friends finder like in the
Instangram app. Basically once a user is logged in Twitter, I want to
be able to find all his friends that use the application and provide a
follow button. The follow action is part of my application, it has
nothing to do with Twitter.

It seems like the iphone application Instagram does that. I have no
idea how to achieve that. I could connect the twitter users and my
application users by comparing the email addresses but the email
property is not available in the twitter API when getting followers.

Can you please give me some directions if you know how to do that ?

Thank you

-- 
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] CMS application on each domain

2010-07-13 Thread Mathieu Maes
Hi,

My company has developed its own CMS which we use to develop websites
for customers. I'm working on a Twitter plugin to allow people to send
news to Twitter from within the CMS. For the moment, I'm stuck with
the authentication part.

First question:
When I register an application, I must choose a callback URL. In my
case it doesn't make much sense, since the application will run on
each customer's domain (being part of the CMS).
Should I re-register the application for each implementation, or
should I use a single key and add domains ?

Second question:
I'm working locally on the application. I read it's not possible to
add localhost as a domain. I added a domain (www.test.com) to my
hosts file, and created a virtual host in my local Apache httpd.conf.
This seems to work fine.

I've set the callback URL to http://company.com in the application
settings, but I'm using the oath_callback parameter to make twitter
redirect to www.test.com/file.php.
This isn't working, Twitter is redirecting to company.com, not the
given oauth_callback URL. Is there something I'm missing ?

Kind regards,
Mathew



[twitter-dev] Re: MGTwitterEngine with OAuth and XAuth support

2010-05-16 Thread Mathieu
Thanks Steve!

I'm using it, but I always get back a 401 error when trying to do a
request.

- My apps have been granted xAuth access by Twitter (I tried with
multiple consumer keys and secrets)
- I fetch the token with -[MGTwitterEngine
getXAuthAccessTokenForUsername:password:]
- I get the token back in -[id accessTokenReceved:forRequest:]
- I set it on the Twitter engine with -[MGTwitterEngine
setAccessToken:]
- I try to send an update with -[MGTwitterEngine sendUpdate:] and I
always get a 401 error back (with no description of the 401)

Is it working for someone? Any idea of what is going on in my case?

Thanks a lot,

Mathieu

On May 1, 6:57 pm, Steve Streza stevestr...@gmail.com wrote:
 Hey everyone,

 I'm one of the collaborators on theMGTwitterEngineproject for Mac
 and iPhone developers. We've finished our initial implementation of
 OAuth and XAuth support withinMGTwitterEngine. This uses the
 OAuthConsumer framework to handle the business end of OAuth, meaning
 that there are only a couple newMGTwitterEngineAPIs you need to use
 (and we've got a wiki guide for migrating to OAuth). We expect most
 users of the framework to want to use XAuth to obtain an access token,
 so we have a convenience API for handling that (of course, you'll need
 to obtain the opt-in from Twitter). After getting XAuth access, it
 shouldn't take more than a half hour to get set up to obtain your
 access token and start sending requests.

 We're also planning on releasing a new version ofMGTwitterEnginewith
 support for some new APIs and bug fixes, as well as OAuth. We're
 hoping to get this out by WWDC, or at least before the OAuth deadline.
 We're aware of the buffer needed for App Store approval, so we'll be
 trying to finish this up ASAP.

 You can grab the code from the project page 
 here:http://github.com/mattgemmell/MGTwitterEngine/

 You can read the migration guide 
 here:http://wiki.github.com/mattgemmell/MGTwitterEngine/migrating-from-bas...

 Feedback is always welcome. If you have any issues, please file them
 in the project issue tracker 
 here:http://github.com/mattgemmell/MGTwitterEngine/issues

 Now stop using basic auth already.

 Thanks,
 Steve