> I think it's far better developer/business practice to design
> *proprietary* applications that are secure and register them with Twitter
> using xAuth.

As has been said time and time again, "proprietary" is not a solution
for this, as any non-hosted app using OAuth can have the keys
extracted from it.

Additionally, some of us would like to write Free or Open Source
applications, that people can use on their own machines, without
requiring them to register as Twitter developers. It used to be
possible to do this. <sigh>


Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 

Reply via email to