Hi there, the way my current (not live yet) twitter OAuth implementation works, it's possible to authenticate the same user more than once, leading to my app storing multiple tokens for the same user. From my testing so far this doesn't seem to be a problem (all tokens still work, and re-authenticating doesn't invalidate any earlier tokens), but I wanted to check if this is by design - in other words, is this likely to continue working in future, or are there some plans to expire tokens when the same app/user requests a new one?
Cheers, Mario.
