Hi everybody,
thanks for responses..I'll proceed in that way, closing the lib with
keys and opening source remaining...
Regards
2010/9/6 Julio Biason :
> On Mon, Sep 6, 2010 at 12:45 PM, Tom van der Woerdt wrote:
>> I'm not 100% sure, but I'd assume that the license doesn't apply to the
>> crea
On Mon, Sep 6, 2010 at 12:45 PM, Tom van der Woerdt wrote:
> I'm not 100% sure, but I'd assume that the license doesn't apply to the
> creator. :-)
Creator no, it's a distribution license. But, since he's the one
distributing the application...
--
Julio Biason
Twitter: http://twitter.com/julio
On 9/6/10 5:40 PM, Julio Biason wrote:
> On Mon, Sep 6, 2010 at 10:41 AM, Tom van der Woerdt 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 tha
On Mon, Sep 6, 2010 at 10:41 AM, Tom van der Woerdt 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
On 9/6/10 3:03 PM, Andrea Stagi wrote:
> I'm developing a software under gpl, a simple twitter client for GNU/
> Linux
> systems...This software uses some private keys for oAuth
> authentication that no one must know..My idea is to distribute the
> source without keys (or filled by only 'X' charact
I'm developing a software under gpl, a simple twitter client for GNU/
Linux
systems...This software uses some private keys for oAuth
authentication that no one must know..My idea is to distribute the
source without keys (or filled by only 'X' character) and the relative
executable file...But it see
