API TOS clarification

[Charles Connell]

Sorry if this is already said somewhere, but I must have missed it.

I am writing some open-source code that uses the Dipity API. This
means that my Dipity API secret key will be exposed. I understand that
it is important to keep the key safe, but this is a serious problem
for open-source developers. Some sites like Facebook have a special
restriction in their API TOS for open-source developers, so that they
can use their API. What is the situation with Dipity?

Thanks.

- Charles Connell
http://www.captainbeah.name

[BK]

Hi Charles, as with a lot of APIs we have a public and private key,
with an easy way for anyone to request and be granted their own
private key.

We'd prefer that source code is published with an example invalid key
and a link for developers to get their own. We're willing to work
with you on this though.

Can you let us know a little bit about the project?

Thanks,
BK