About FindMeOn's QuickList

QuickList is a way for internet users and developers to rapidly integrate their online accounts with FindMeOn.com's services.

QuickList operates on a very simple premise:

  1. A webservice can offer users a special link to FindMeOn.com that pre-populates a new account entry.
  2. The user can review, modify, and confirm the entry.
  3. The user is then directed back to the originating webservice , along with information about the new node.

When users list their accounts using QuickList, the originating webservice instantly gets information about the user's information repository on FindMeOn.com -- allowing them the full benefit of the FindMeOn API.

You might also be interested in FindMeOn's RapidRegister , which aids cross-registering accounts with FindMeOn

QuickList for Users

In order to use QuickList, you must already be registered with FindMeOn.com

QuickList items are not automatically created -- you have the opportunity to review and modify the listing before it is created.

QuickList for Developers

What?

QuickList lets you 'bind' one of your user accounts to a central repository of information for that user on FindMeOn.com

The account binding is simple and secure. Here's how it works:

  • Our common user clicks a 'FindMeOn QuickList' button on your website. You preformat the link with account specific information for that user and your system.
  • The user is directed to FindMeOn.com, where they review the information and add it to their profile.
  • The user is then redirected back to your website, along with information about their repository on FindMeOn.com

When your user is redirected back to your website, you are given a unique ID for their account on FindMeOn.com . Using that ID, you can query FindMeOn.com using the FindMeOn API ( http://api.FindMeOn.com ) and have full access to your user's aggregate info. The FindMeOn API provides you with: profile information, syndicated account links, syndicated account text. The API will soon offer cross-site friendship data.

Why?

FindMeOn's API helps you keep user profiles up-to-date -- even if that user hasn't logged on in days, weeks or months.

FindMeOn helps you outsource your profile management and end orphaned accounts, letting you focus on content and features. By using FindMeOn's QuickList and RapidRegister offerings you're instantly connected to the FindMeOn API for that particular user, and able to update account status and receive syndicated information and cross-network messages.

Verification

FindMeOn provides 3 reasonably secure methods for verification of the QuickList binding.

  • nonce - if you submit a nonce and the public half of an api_quicklist_key ( available to all registered users ) , we will return a digest of the private half of the key + the nonce. This trivial method will reasonably assure you that the request has not been spoofed.
  • open_id - all quicklist hex_ids are valid OpenID URLS when formatted in a http://findmeon.com/findmeon/%{hex_id}s scheme. You may require users to authenticate against that page to prove ownership.
  • findmeon - our own findmeon node can be used for this purpose. you can request the user to sign a string of your choosing , and verify both that data signature and the signature on the http://findmeon.com/findmeon/%{hex_id}s scheme page with a single public key. alternately you can allow the user to place a findmeon badge on your website and compare signatures on that badge to the findmeon.com record.

QuickList Protocol

All QuickList requests should be directed to the following url:

http://findmeon.com/my/quicklist/add/

The QuickList system will accept the following values as either GET arguments or POST data. Please remember that you must url-escape / url-encode arguments during GET requests.

findmeon node information
this information will be used to contruct a findmeon node for the user
findmeon.resource the url / name of the user's account on your system
findmeon.findmeon_type the findmeon_type according to the findmeon.org specification. currently the system only accepts 'url'
findmeon.findmeon_subtype the findmeon_subtype according to the findmeon.org specification. currently the system only accepts 'url' as type , which correlates to the following subtypes: ['homepage' , 'FOAF' , 'online account', 'blog' , 'webservice' ,'business' ,'social network profile']
findmeon.findmeon_attribute an array of findmeon_attribute according to the findmeon.org specification. ['primary' , 'personal' , 'alternate' , 'work']
 
findmeon node preferences
this information will be used to 'tag' the findmeon node for the user
findmeon.rapidregister_key supply an ID for the user via the FindMeOn RapidRegister system
findmeon.name an optional 'short name' for the account
findmeon.privacysetting a default privacysetting option ['public' , 'private' , 'friends']
 
request originator information
this information will be displayed to the user.
originator.name required the name of your system/service/website
originator.nonce a nonce value to be digested by the private half of the api_quicklist_key
originator.api_quicklist_key public version of your quicklist key. the private half will be used to sign the nonce and the findmeon hex
originator.exit.url required a url we redirect the user to , once we have processed the request.
originator.exit.field.findmeon_hexid we will add the new hexid ( the public FindMeOn.com identifier ) as a GET arg to the originator.exit.url redirect. defaults to 'findmeon_hexid'
originator.exit.field.nonce we will return the submitted nonce with your request in this field. defaults to 'nonce'
originator.exit.field.digest we will submit a md5 hex digest of the nonce and private half of the api_quicklist_key , in the form of "md5_hex( private_key , ':' , nonce )". notice that the 2 values are concatenated/joined on a colon. defaults to 'digest'
originator.api_key your API key for your own metrics
originator.api_application_key your API Application key for your own metrics

The originator.api_key nor originator.api_application_key are not required, but recommended. If supplied, they will be recorded to aid in metrics that we present to the API keyholder's account.

Sample URL

To Submit this information:

  • findmeon.findmeon_type : url
  • findmeon.resource : http://www.roadsound.com/tour?arg1=val1&arg2=val2
  • originator.name : roadsound
  • originator.exit.url : http://www.roadsound.com/quicklist

We use the following URL:

QuickList Usage Recommendations

In order to use the QuickList protocol, simply show users an icon offering them the chance to use QuickList, and generate a URL using the protocol guide above.

Users that are not logged in to FindMeOn.com will be given the chance to login or register.

If you would like to only show the QuickList link to cookied users of FindMeOn.com , you can embed the code below.

This will create a javascript variable fmo__user_is_cookied , which will be set to 1 or 0 based on whether the user is cookied or not ( or -1 if there was an error processing the request );

QuickList Icons

Feel free to either download or link to the QuickList button below.

QuickList Link Icon ( 2007.06.01 )

   

QuickList Link Icon ( 2007.01.09 )