[wp-hackers] Twitter API and Authentication
jbloch at olympianetworks.com
Wed May 12 04:53:24 UTC 2010
Huh. I got this from twitter tonight:
Thank you for writing in. First, please note that xAuth is dependent upon
> OAuth and cannot be used without registering an application anyways. If your
> goal is for each user to be able to be able have a source parameter similar
> to "from web" or "from API" for their WordPress site, then each user will
> have to register their own application whether it is authorized via OAuth or
> xAuth. If this is not an issue, your application should be able to authorize
> multiple users and manage their access tokens just fine with one OAuth
> Also of note, website-based applications will not be given access to xAuth
> and must use the normal OAuth workflow instead. I apologize for the
> inconvenience. Please let me know if you have any other questions.
Hope that helps,
It looks like we can use oAuth for our one application. Say I registered a
plugin called "My TweetPress" as a twitter application, I could release the
plugin and use the plugin to do all the oAuth work on the one application
for all users. Then all tweets from anybody using "My TweetPress" would say
'posted from My TweetPress'. Now, of course, for security reasons, all oAuth
authorizations would have to go through a third server housing the
application's information, so that I didn't have to publicly release the
application's private key. But that seems like it would result in a fairly
straightforward and user friendly way get twitter integrated (for the user.
We're going to suffer).
John P. Bloch
On Tue, May 11, 2010 at 11:18 PM, Lew Ayotte - Full Throttle Development <
lew at fullthrottledevelopment.com> wrote:
> FYI, for those who might have gotten their hopes up about xAuth...
> Received this from Twitter tonight:
> > Thank you for your interest in xAuth. Unfortunately, browser-based
> > applications will not be given access to xAuth and must use the normal
> > workflow instead. I apologize for the inconvenience.
> > If your plugin has been using basic auth and needs to make a one-time
> > conversion to OAuth for its existing user base, let me know and we can
> > into granting temporary xAuth access for this purpose.
> Lew Ayotte
> Full Throttle Development, LLC
> lew at fullthrottledevelopment.com
> On Tue, May 11, 2010 at 4:12 PM, Thomas Scholz <info at toscho.de> wrote:
> > Otto:
> > On Tue, May 11, 2010 at 3:01 PM, Thomas Scholz <info at toscho.de> wrote:
> >>> My main problem is the captcha: I can describe the other fields in the
> >>> reader’s native language, but I cannot (or at least: shouldn’t) solve
> >>> captcha.
> >> Are your users blind as well?
> > Yes, some are. Of course, the could just ask someone to do this for them,
> > but this a really bad solution.
> > Letters are letters regardless of the language,
> > Even I often can’t read those captchas and prefer the spoken words. But
> > they are just noise on Twitter, unsolvable for non native speakers.
> > Regards
> > Thomas
> > --
> > http://toscho.de
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers