Hi, This is probably a basic question - but what is the best option if you have written an integration for a web-based application that is installed on multiple sites?
The URL is going to change per installation (and won't be publicly accessible), and I would really like to minimise the impact to the application's administrators and users. thanks, Eoin On Apr 24, 4:40 pm, Raffi Krikorian <ra...@twitter.com> wrote: > hi all. > > you're going to be hearing a lot from me over the next 9 weeks. our plan is > to turn off basic authorization on the API by june 30, 2010 -- developers > will have to switch over to OAuth by that time. between now and then, there > will be a *lot* of information coming along with tips on how to use OAuth > Echo, xAuth, etc. we really want to make this transition as easy as we can > for everybody. > > as always, please feel free to reach out to this group, or to @twitterapi > directly. if you need help remembering the date -http://bit.ly/twcountdown > . > > -- > Raffi Krikorian > Twitter Platform Teamhttp://twitter.com/raffi > > -- > Subscription > settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
