request for clarification

[esc]

Hi,

i hacked together a tiny tool to use your api that allows me to track
artist and label releases. I was wondering what to do about the api-
key if i give the tool to my mates, or make it available online. Does
each user need his/her own api-key? Or should i distribute the api-key
with the tool? The tool is written in python and i was a bit worried
that if i put the api-key online in clear text, someone might go and
do mischief with it.

thanks

esc

[William Coates]

Hi,

I guess the best idea is to make the key configurable in your code, so
people can use their own key: don't distribute it with your key. You
could make it read from a config file or environment variable or such
thing...



2009/3/11 esc <emergencyse...@googlemail.com>:

[esc]

Thanks for your answer.

I was expecting something like this, and wrote the code to load the
key from a file :-)

cheers

esc

On Mar 11, 11:31 pm, William Coates <william.coa...@gmail.com> wrote:
> Hi,
>
> I guess the best idea is to make the key configurable in your code, so
> people can use their own key: don't distribute it with your key. You
> could make it read from a config file or environment variable or such
> thing...
>

> 2009/3/11 esc <emergencyselfconstr...@googlemail.com>:

[esc]

Hi again,

What would you suggest for users to use as "application name" when
registering for an api-key?

esc

On Mar 11, 11:31 pm, William Coates <william.coa...@gmail.com> wrote:

> Hi,
>
> I guess the best idea is to make the key configurable in your code, so
> people can use their own key: don't distribute it with your key. You
> could make it read from a config file or environment variable or such
> thing...
>

> 2009/3/11 esc <emergencyselfconstr...@googlemail.com>:

[William Coates]

Whatever they want ;)

2009/3/12 esc <emergencyse...@googlemail.com>: