On 9/6/10 5:40 PM, Julio Biason wrote: > On Mon, Sep 6, 2010 at 10:41 AM, Tom van der Woerdt <i...@tvdw.eu> wrote: >> Just put the keys in the executable but not in the source. Really, it's >> your only option. Well, actually that's not true, because you can also >> simply proxy all traffic via a server, but that's not ideal. > > I may be wrong here, but if my memory doesn't fail, if you distribute > a binary package under the GPL, you're required to distribute the > exact same source that created that binary. > > You can distribute your application in GPL and distribute another > binary, closed sourced package with the API keys and such, which you > must then dlopen().
I'm not 100% sure, but I'd assume that the license doesn't apply to the creator. :-) Tom -- 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
