On 9/1/2010 6:46 PM, Julio Biason wrote:
On Wed, Sep 1, 2010 at 7:58 PM, John Meyer<john.l.me...@gmail.com> wrote:
And that assumes that you distribute the consumerkey and consumersecret with
the app. Nothing about Open Source requires this. You could just as easily
just distribute the source and require that users obtain their own
ConsumerKey combos.
The problem, in this case, is the awkward UX. "Hello user! Thanks for
downloading application X! To use it, you must register your
application on Twitter, then authorize it to be used! And don't forget
to use the proper options or it won't work, ok?"
That's the way Twitter Tools for Wordpress works, and it isn't ackward
at all. It's description leaves something to be desired, but it ain't
rocket science.
--
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:
http://groups.google.com/group/twitter-development-talk?hl=en
