Third Party API access to user data

Why do we want this? What API should this be? I think we should try to use other services where possible. So if we have to have an api, its only for these services to get content and push it...but don't think we should focus on this for now.

OK, I learned that there is an affiliated party who is requesting an API for the site. Ok, sure.

###

We need to target just 1-2 services for the api...something that we really need like the fotopedia and/or twitter. This should be targeted at chris' hookup on the ipad...but if there is scrilla involved. JON

###

A single JSON string with an entry for each contact. We can limit this to only contacts who have photos. Each contact would have:

full_name
homepage
services (Twitter and Flickr for now)
  service_name
  service_username
  service_user_id
  user_profile
portraits
  flickr_id
stories
  title
  body

##
do we want to keep it open to anyone to access like on ocal? or should have oAuth for verifying the clients?
I'm working on oAuth provider in aiki so we can use that to limit access from third parties

##

Totally should use oAuth and implement the familiar twitter/facebook allow deny interface. Keep it open, but have to really make sure data is safe. Its also a good demo to show aiki useful for making api. Jon

###

BTW, ocal should get something like this too...there is a guy who expressed interest over there Jon

### Still hashing this out with third party. Moving back.