What techniques are people using to keep their Twitter app's consumer key and consumer secret, um, secret? What lengths are you going to to make sure nasty people can't get at this information? I have a particular problem in that I want my app to be open source - does anyone have any experience of building open source apps that interact with Twitter (or other services that use OAuth)? Thoughts? Suggestions?
Brian -- 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
