Dashboard > The DataPortability Project > ... > Initiatives > Web Site DataPortability Suggestions
  The DataPortability Project Log In | Sign Up   View a printable version of the current page.  
  Web Site DataPortability Suggestions
Added by Julian Bond , last edited by Julian Bond on Mar 23, 2008  (view change)
Labels: 
(None)

This page documents suggestions and critiques of well known web sites


Confluence

  • Support OpenID for signup and login

Google

  • Make it easier to combine accounts into one. It's very easy to end up with lots of Google accounts all with different detail and permissions for various Google properties. There's no way of combining them.
  • Provide a richer and common account profile page across Google Properties
  • Support Skype as an IM type

Google APIs

  • Support OpenID and oAuth sooner rather than later
  • Use a more common profile description in OpenSocial People Data API and the Contacts API rather than creating another one
  • Combine the Contacts API and OpenSocial People Data API
  • Provide a Read-Only view of the Contacts API
  • Support Brad Fitzpatrick with the Socialgraph API and keep developing it.

Google Mail

  • Support oAuth for a request for your contacts list
  • Expand the profile fields
  • Use a standard profile description format rather than creating another

Hotmail

  • Support OpenID for login
  • Support oAuth for authentication
  • Use more REST and less SOAP
  • Provide a Contacts API

LinkedIn

  • Support OpenID for sign up and login
  • Support oAuth for a request for your contacts list
  • Support FOAF for export of social network data

Plaxo

  • Support oAuth
  • Use a common profile description format for the Sync API. And/or turn the MS Outlook layout into an XML namespace

Twitter

  • Support OpenID for sign up and login
  • Support oAuth to avoid every API application needing your Twitter password
  • Support FOAF for export of social network data

Yahoo

  • Support OpenID SReg and AX
  • Support OpenID for login
  • Use more REST and less SOAP
  • Provide a Contacts API
  • Move to oAuth from BBAuth
  • Relax the "non-commercial" restrictions on usage

Common problems

  • Asking the customer to give their ID + Password for a remote site. We have to stop this anti-pattern.

Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators