This topic was merged into another on Sat, 16 Oct 2010 23:47:39 +0000 Click here to see the authoritative topic.

I would like to take APIs of linkedin & onetruefan, normalize the data & tell what content viewed = what jobs people *would* be great for.

I would like to take APIs of @linkedin & @onetruefan, normalize the data & tell what content viewed = what jobs people *would* be great for.
1 person likes
this idea
+1
Reply
  • Great idea! Stay tuned, a OneTrueFan API is in the making
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited

  • I’m worried
    Slightly worried by this, not so sure I want people/apps to be able to access the websites I've visited. I'm presuming we will be able to block access/have to give permission to individual websites/apps?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited

  • EMPLOYEE
    I’m hopeful
    Eric Marcoullier (Co-Founder and Product Guy) October 19, 2010 15:38
    Jon -- no worries.

    While we are pretty excited about the idea of API, we are SUPER concerned about getting privacy right. And I'm not talking some big company "we're talking privacy out of our mouth to distract you from one of our hands giving your data away to partners and the other hand giving you a colonoscopy."

    We haven't even started down the API route yet because we have so much work still to do on the app. So don't worry that this is going to jump up a surprise you shortly.

    We haven't giving things a lot of focused thought, but here's where I personally sit (this will be a team decision ultimately, where "team" = both OneTrueFan and the community):
    1) Information has to age out of the system -- we don't know yet if that's two weeks, two months or two years. It boils down to what our users are comfortable with and we need to just see the thing in action for a while longer.
    2) Site owners can get public information about who's been on their pages -- it's already public, so making them jump through hoops doesn't do anything except piss them off and get them less invested
    3) No one can access your browsing history without your express permission.

    I was initially of the opinion that we should NEVER provide access to the browsing history, even if the user chose, but I've changed my mind since then. There are so many great ideas regarding what someone could provide for you with that data that I've personally said "fuck it, we should see what people can do."

    If I want to let a company have access to my history to see what jobs I'd be good at, or where I'm spending my time online, or to create a music playlist generated from all the pages I've viewed online, or any other sort of thing, that should be my option -- but I should have to agree to that EVERY time I share that data. And so the API, when it's built, will be 100% OAUTH based to give you control of who sees your data and also let you revoke that permission at any time.

    So that's where I'm currently coming from. I'd love to get more of your thoughts as you have time
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated happy, confident, thankful, excited