You're safe to continue using the non-api-subdomain version of OAuth for
awhile longer (it won't disappear on June 30th), but we recommend switching
to using the api subdomain (and SSL!) pro-actively in the event we decide to
be stricter here in the future. But we have no immediate plans to invalidate
such requests at this time.

Taylor Singletary
Developer Advocate, Twitter

On Thu, May 27, 2010 at 3:17 PM, emagic <> wrote:

> We use OAuth login in our application for a long time, but the links
> are sth. like: "";, and we just
> found the new one should be sth. like "
> It seems what we have now is OAuth 1.0A as mentioned in documents. We
> are not sure what should we change to avoid broken after June 30th.
> Any suggestions? Thank you.

Reply via email to