I'm not sure what sort of "Verification" you're looking for - however,
you might want to take steps on your own end to reassure users why
they're being sent to Twitter. See, for example, Favstar.


It's the your job as an application developer to instil confidence in
the user to feel happy entering their credentials.


On Oct 24, 12:56 am, loretoparisi <loretopar...@gmail.com> wrote:
> Hi,
> I'm cto for stickphone.me and lyricsmood.me, oauth based twitter apps.
> Many users told us that they just don't use our oauth sign in service,
> since it seems to them to be unsafe with this kind of sign in (single
> sign-on from oauth client site)
> This is not a design problem I guess, but a people misunderstanding
> problem, about the authorization protocol (going away from people like
> developers, engineers, etc, who really knows what oAuth is about?),
> even if we tried to explain this process as well in our sites tos.
> I was wondering if you @twitter have any idea in the future to
> certificate an app in order this app to be "verified" by twitter (in
> the same way some accounts are).
> In this ways app users would not be scared when clickin on "Sign in to
> Twitter" buttons.
> Of course using Twitter's button styles would be a better experience
> for the user in order to trust the thirdy-party service, but this is
> not possibile in all cases.
> Thanks,
> Loreto Parisi
> CTO at stickphone, lyricsmood
> lor...@stickphone.me
> lor...@lyricsmood.me

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: 

Reply via email to