We are definitely interested in hearing what type of workflow you
would prefer for OAuth-ing desktop applications. We want to make the
experience the best it can be and look for your feedback on how we can
improve it.

Let me start another thread so we can make sure to capture everyone's feedback.

Best, Ryan

On Sun, Oct 11, 2009 at 12:42 PM, Isaiah <> wrote:
> Like Chris, my app uses a similar UI.  I released it as open source several
> months ago:
> It hasn't seen runaway traffic, but it has been downloaded pretty constantly
> for about three months.  There are now also several github clones of the
> project too.
> I think it's safe to assume that there are quite a few developers doing the
> same thing.
> As we've all seen, there is backlash from users and the media about the
> OAuth experience:
> Judging from the feedback I received, it's safe to say that developers are
> looking for ways of making this less painful for the Twitter community, i.e.
> developers are doing this because they believe it will **help** users, not
> for some malicious reason.  Those were definitely my goals.  :-)
> If Twitter thinks this sort of UI is a bad idea, it sure would be nice to
> get some official feedback about it.
> Isaiah
> YourHead Software
> On Oct 11, 2009, at 9:28 AM, Abraham Williams wrote:
> Currently not really. Twitter might start enforcing correct designation at
> some point though.
> Abraham
> On Fri, Sep 25, 2009 at 12:33, cnunciato <> wrote:
>> Hi folks:
>> I'm adding some Twitter integration to a desktop app, and I'm unhappy
>> with the whole "copy/paste this PIN into your application" experience.
>> In my case, I happen to have a browser instance containing the OAuth
>> authentication process embedded within my desktop app, so it's
>> possible to listen for redirection events that happen inside that
>> browser and respond to them -- but when I mark my Twitter app as a
>> "desktop" app (on the app-settings screen on Twitter, where it's
>> defined), I'm forced into using the copy-this-PIN approach (because no
>> callback URL can be specified for desktop apps), which, from a user-
>> experience perspective, kinda sucks.
>> I do notice, though, that if I make my app a "web" app instead, I can
>> specify a callback URL, and have my app watch for redirections to that
>> URL, which works quite well and provides a more seamless user
>> experience.
>> So my question is, is there any disadvanage to marking my installed
>> desktop app a "web" app on Twitter, so I can take advantage of using a
>> callback URL to provide a better user experience?  Is it a violation
>> of terms of use or anything?  Any drawbacks at all?
>> Thanks in advance --
>> Chris
> --
> Abraham Williams | Community Evangelist |
> Hacker | |
> This email is: [ ] blogable [x] ask first [ ] private.
> Sent from Madison, Wisconsin, United States

Reply via email to