Definitely would suggest going beyond the Klout Score and implementing a mix of topics, topical scores, interest and influence into the Klout calculation. The raw Klout Score is a bit broader than necessary for lead qualification and relevance.

Also worth investigating is http://apis.io/ , a growing repository for API interface design patterns.

What sort of options do you have for curation, filtering? How do you find the wheat from the chafe?

Our peg is simplicity. So really, people can search by keyword, filter out unwanted keywords, ban users, filter RTs, etc.

We don't do any big grouping or the sort yet... we just rely on producers to find the posts they're looking for.

What is a "peg"?

Ha. It's a news term. It means like "why should I care about you".

http://en.wikipedia.org/wiki/Nut_graph - the same thing in print. :)

See also http://journ101.wordpress.com/2009/10/29/what-is-a-news-peg-...

Why? It protects the user's privacy, unlike Facebook. Ask them for their email address after they authenticate and make it an act of volition.

This is silly. You've licensed nearly every game you ever bought since the 90s, likely even before that. You've never owned it; you just felt like you did. Server-side storage and 'online-only' gaming just solidifies this in a technological sense, not a legal one.

But practically no company could ban you from accessing your savegames with your licensed software, since both were in your physical possession. Now they can.

This is my next YC project.

Instagram's Terms essentially say you have to respect the copyright and license of the photos.

However, their API doesn't provide any mechanism to know what those licenses and copyrights are yet, which makes it pretty difficult to honor it. Still, you're bound by the terms, not their execution. If it's a business you plan to make money off of, you should probably consult legal advice and plan ahead to lose it.

Contacting them is your best option. Find some one to talk to, explain what you'd like to do, and how the terms restrict you, and see if you can't find a way to have an exception, clarification, or some other way around it.

The spirit of that is most likely: "You won't resell or grant your access to the API to other people, or allow someone else to to resell or grant access to the API."

Not generally the content you're getting from the API (although you wouldn't be selling or providing that to others, either, you'd be creating some derivative of it).

Well that may be YOUR spirit but for YELP'S spirit I have to rely on the language in the TOS.

I say this as a developer building a product in which yelp's reviews are directly useful.

Which is why it behooves you to contact them and get clarification, exception, etc. The same rules don't apply to everyone equally if you can make the right case. Simply displaying their content is not likely to get a pass, but having a way to brand it well and drive new content creation often will.

Twitter does make money on its API. It's done through channel partnerships. Is it as much as advertising? No. But still significant.

Twitter's API is still sufficiently open. There's plenty of data to be had. The limitations and constraints breeds creativity, and we'll finally see new integrations and ideas that do something new rather than simple enhancements and user-annoyance-fixing-as-a-product.