When your end-users are using the API, are they doing so client-side in
their browser or are you making server-to-server requests on their behalf?

@episod <http://twitter.com/intent/user?screen_name=episod> - Taylor
Singletary


On Tue, Jul 12, 2011 at 10:12 AM, Astralis <astralis...@gmail.com> wrote:

> I might be missing how this works, but I am storing the user tokens and I'm
> able to post through the web app onto Twitter with success.
>
> But, I found that when the user logs out of Twitter (via the Twitter
> website), the user's no longer able to post and the tokens seem to be
> invalid and I receive an error message that oAuth could not authenticate.
>
> When the user logs back into Twitter (again via the Twitter website) the
> tokens work again.
>
> Thoughts?
>
> --
> Have you visited the Developer Discussions feature on
> https://dev.twitter.com/discussions yet?
>
> Twitter developer links:
> Documentation and resources: https://dev.twitter.com/docs
>
> API updates via Twitter: https://twitter.com/twitterapi
>
> Unsubscribe or change your group membership settings:
> http://groups.google.com/group/twitter-development-talk/subscribe
>

-- 
Have you visited the Developer Discussions feature on 
https://dev.twitter.com/discussions yet?

Twitter developer links:
Documentation and resources: https://dev.twitter.com/docs
API updates via Twitter: https://twitter.com/twitterapi

Unsubscribe or change your group membership settings: 
http://groups.google.com/group/twitter-development-talk/subscribe

Reply via email to