If you currently have no contact at all with your users, I can see how
it might be a problem. However, almost all other apps have a way to do
this: by simply asking them on the website / app.
For example: my own app is a desktop client and it simply checks for
permission and asks for a re-authentication via a modal popup on
startup. A webapp wouldn't need this because a user simply
re-authenticates on each login.
Tom
On 6/22/11 8:31 PM, Ryan wrote:
Would love to get some guidance from Twitter or any other developers
as I know there are plenty of other 3rd party apps out there that are
in similar situations. I don't want to come across as Spammish, but
is it possible to "Spam" your authenticated users?
Not sure if I have many alternatives other than just waiting for
people to email me angrily/confused why the app is no longer working.
Thats going to be fun! Can't wait for June 30th! :)
At least the fix is easy enough as simply re-authenticating.
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
