[twitter-dev] Re: Best practice for notifying users they need to re-authenticate before June 30th?

2011-06-22 Thread Ryan
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

Re: [twitter-dev] Re: Best practice for notifying users they need to re-authenticate before June 30th?

2011-06-22 Thread Tom van der Woerdt
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: [twitter-dev] Re: Best practice for notifying users they need to re-authenticate before June 30th?

2011-06-22 Thread Ryan
In our situation, once the users configure their accounts during the initial setup, there is no need to revisit our website/app unless they need to change some of their settings. If they have not visited our website between June 15th - June 30th, then unfortunately their GroupTweet accounts

[twitter-dev] Re: Best practice for notifying users they need to re-authenticate before June 30th?

2011-06-21 Thread Orian Marx
I think this has the potential to end up getting you blocked for spamming. You've identified a real problem with the impending OAuth change I think. Would be good to hear a recommendation directly from Twitter as to how to handle your type of situation. On Jun 21, 7:12 pm, Ryan