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
are currently two options for OS projects I can think of :
> * Route all your requests via an application on your server (the TweetDeck
> way: just redirect api.tweetdeck.com to api.twitter.com but sign the
> requests with your key. However: this *will* cause issues with POST
> requests, so you&#x
