@rsarver made it very clear in some recent tweets that Twitter's apps will not be subject to the new OAuth requirements as they are part of the 'service' not 3rd party offerings.
On May 19, 6:59 pm, Frank Ash <nut...@gmail.com> wrote: > That would be much better cartmatrix but either way, its a negative and > unnecessary to take this approach. I am still a bit sceptical that everything > will still work fine, just if they try to send a DM it will fail to a 403 > error. There is language in the post that suggests both outcomes as possible. > I would really like someone from Twitter to clarify exactly what will happen. > Very clearly and plainly. > > I am interested also to here the way they will dance around not doing this > themselves as well. They won't, I can guarantee that. I would bet my house on > it. Eiyer way the outcome will be negative in any scenario, so they won't > want any part of that. But they think its fine if we have to. -- 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
