[wp-hackers] Twitter API and Authentication

[Otto]

On Tue, May 11, 2010 at 8:32 AM, Lew Ayotte - Full Throttle
Development <lew at fullthrottledevelopment.com> wrote:
> It seems like that is the antithesis of user-friendly and would seem like
> the opposite of what Twitter would want. I currently have over 13,000
> downloads for my Twitter Post plugin. Many of those are updates, so let's
> assume that 1/16 of those are legit users. Twitter really wants over 800 app
> requests for the same app? And I'm not the only one with a Twitter Plugin
> that allows you to post to twitter -- Twitter Tools has over 500,000
> downloads.

My users seem to have no problem with it:
http://wordpress.org/extend/plugins/simple-twitter-connect/

There's a fundamental difference in viewpoint here. See, you're
viewing your plugin as the "Application". Twitter views each separate
website sending data to them as its own "application".

I've been doing it this way since the beginning. It works fine. Most
users prefer this, actually, because on their tweets, instead of
saying "posted by Twitter Tools", it says "posted by User's Own
Website" and links back to their website.

If you still want to do it your way, then you should set up a website
of your own that acts as a relay for all your users. Instead of them
talking directly to Twitter, they talk to Twitter through you, and
thus through your application.

If you want to see what it looks like, take a look at
http://twitter.com/ottodestruct. Note how each post says "posted by
Otto on WordPress"? That's the application for my http://ottopress.com
website. If I was to publish something on http://ottodestruct.com, it
would come through a separate application that I created for that
website, and would show "posted by Nothing to See Here" instead, even
though it's on the same account.

-Otto