Home › Forums › Calais Forums › The Calais Initiative ›
Tagaroo and API key
Tagaroo and API key
Posted on: Wed, 07/23/2008 - 13:46

Hello,

I don't know if this is the good place in the forum to ask this question. I am building a community offering blog hosting (basically pre packaged wordpress with a selection of plugins/themes already installed and configured, not wordpress mu). I would like to include Tagaroo and was wondering what will be the best strategy regarding API key...

- To have one api key for the all blogs hosted (but we will probably hit the limit of number of requests per day quickly)

- To have one api key per blog (problem in this case to automate the request of new api key)

- To generate manually one api key per x number of blog. (one per 100 blogs created)

Thanks for your suggestions...

Benoit


Comments

Shared keys, etc
Posted on: Thu, 07/24/2008 - 17:32 #1

Benoit:

In general we discourage the use of a shared key across multiple users. The reasons for this have less to do with volumes, etc - and more to do with transparency and privacy.

We want to make certain that every user of Calais has a chance to read and agree to the terms of service before they use Calais. By sharing a key in this fashion - particularly when it involves a user's own content such as a blog posting or email or whatever - we're taking that opportunity away from them.

But - we're open to talking. We understand that having your users have to jump over to opencalais.com, create an account and obtain their own key is not exactly a seamless experience.

Anyone have thoughts on alternative approaches?

Regards,

shared keys
Posted on: Thu, 07/24/2008 - 19:05 #2

Just to give more detail, the service is user oriented, not service oriented. It means that the configuration of blog an interaction will depend of which services the user already use (ex feeds from facebook, myspace, etc). We expect to have a good traffic because of advertising, site name and features.

I see two options:

One suggestion is to add your term of service in our account creation process and to have the ability to create the key, based on a web service request. The issue I see is the number of inactive keys created this way. By experience, only 1 on 20 blogs created will be really active.

Other suggestion is to add OpenCalais term and services in our subscription process and use shared key after. By default all post done trough our service will be licensed by creative commons license. If the user break one of the TOS, his service is terminated. As you hold the key for all users, it will be not our interest to not enforce this policy.

Next phase will be to use the semantic cloud of tags as entry doors for all content generated

First phase of logs (name of the service) will be launched at mid october.

I think you will have probably more questions like this as opencalais will become popular so I keep the topic in the public forum, it will probably be interesting for other users despite my request is very specific.

Thanks

Benoit

Shared keys
Posted on: Fri, 07/25/2008 - 16:13 #3

Well, you've introduced a couple of interesting ideas.

I know we're not planning to support opening the API to allow users access to key issuance. While this is technically feasible the possibility of people being signed up without their explicit consent is a problem. If this was just a few sites we could monitor this manually - but it isn't scalable.

The fact that *all content* on your site is CC licensed does in my view open up the possibility of a shared key solution. In this approach you'd present the Calais TOS as part of your setup process and possibly give users the ability to opt-out of participation.

The volume limits are not an issue. We'll look at increasing the limits on a case by case basis and try to work to come to a reasonable solution.

As we've mentioned elsewhere - we are also working on a "commercial" version of Calais that has the same functionality as Open Calais but bakes in significantly higher transaction limits and SLA's.

Thoughts?

Regards,