Presumably to do the OAuth vanity plate, you have to do what you described in your "disgruntled developer" post above. I.e., the user registers their own OAuth app and enters the corresponding values in your app, allowing you to masquerade as their app in tweets. Frankly, it seems to run counter to the purposes of OAuth. But the developer of one vanity plate app I found publishes email correspondence with "Brian" from Twitter, and says they have been personally vetted by Twitter, so I guess it is okay...
On Feb 16, 7:58 am, Dewald Pretorius <dpr...@gmail.com> wrote: > I see what you mean. It will be great to know what is the Twitter > approved way of providing vanity plates. It is obviously a feature > that will rock, if we can get a level playing field by that rule being > made public to all of us. > > On Feb 16, 11:04 am, PJB <pjbmancun...@gmail.com> wrote: > > > Vanity plate OAuth is already pretty rampant. And apparently > > acceptable by Twitter, too? That's at least what the leading Desktop > > purveyor of such a system says... something along the lines of > > "officially authorized by Twitter". > >
