I have an open source Twitter client for Google Chrome and this is how I distribute it.
The source is available with no API key. If developers wish to play with the source they must register their own OAuth application. http://github.com/abraham/omnitweet For users there is a packaged download that includes an API key. They just install the extension and off they go. http://github.com/abraham/omnitweet/downloads Abraham ------------- Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Wed, Sep 1, 2010 at 15:58, John Meyer <john.l.me...@gmail.com> wrote: > On 8/19/2010 11:50 AM, briandunnington wrote: > >> as Julio stated above, the official response from Taylor (in another >> thread) was that this solution will *not* be rolled out. there is >> currently no other alternative being offered other. >> >> and just to repeat what has already been said a few time in this >> thread - this is not just a problem with open source apps. any app >> that is distributed (ie: not running on your own web server) has this >> problem. i read on Daring Fireball the other day about a new Twitter >> app called Hibari, so i downloaded it and got the consumer key and >> secret within a couple of minutes. others apps are just as susceptible >> - any time the user has the code, the secret must be considered >> unsecure. >> >> > > 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. > > > -- > 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 > -- 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
