Why portability matters....


Published on

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Why portability matters....

  1. 1. Why portability matters... Why we need to look beyond 03/10/08
  2. 2. Overview ● why is the BBC interested in portability ● what is portability ● many examples of good and bad practice ● where to look next
  3. 3. “Get web savvy or we die...”
  4. 4. The user controlled revolution http://www.flickr.com/photos/sinistergiraffee
  5. 5. The era of control has passed http://www.flickr.com/photos/gadgettakesapicture/2240511988/
  6. 6. so we think...
  7. 7. Data portability “As users, our identity, photos, videos and other forms of personal data should be discoverable by, and shared between our chosen (and trusted) tools or vendors.”
  8. 8. Principles ● We should have control over the profiles, relationships, content and media we create and maintain, regardless of what platform they are hosted on ● We should use open formats, APIs, protocols and policies for the data they control ● We want to protect their rights and privacy ● We should be recommending existing standards wherever possible rather than inventing new ones
  9. 9. Bill of rights for social users ● We publicly assert that all users of the social web are entitled to certain fundamental rights, specifically: ● Ownership of their own personal information, including: – their own profile data – the list of people they are connected to – the activity stream of content they create; ● Control of whether and how such personal information is shared with others; and ● Freedom to grant persistent access to their personal information to trusted external sites.
  10. 10. Notations of trust
  11. 11. Find your friends easily
  12. 12. Trust us with your password
  13. 13. In other words phishing
  14. 14. Permission based systems
  15. 15. OpenID is permission based
  16. 16. OpenID and Oauth
  17. 17. Facebook permissions
  18. 18. Identity is difficult
  19. 19. Cloud computing
  20. 20. Amazon Web services
  21. 21. Google services
  22. 22. Live Mesh by Microsoft
  23. 23. Ray Ozzie on Live Mesh ● Just imagine the possibilities enabled by centralized configuration and personalization and remote control of all your devices from just about anywhere. Just imagine the convenience of unified data management, the transparent synchronization of files, folders, documents, and media. The bi-directional synchronization of arbitrary feeds of all kinds across your devices and the Web, a kind of universal file synch. ● http://seekingalpha.com/article/67370-microsoft-mesh-cloud-computing- for-the-masses
  24. 24. Cloud based terminals?
  25. 25. Proprietary tools
  26. 26. Service lock in
  27. 27. Trap in the cloud ● Richard Stallman, founder of the Free Software Foundation and creator of the computer operating system GNU, said that cloud computing was simply a trap aimed at forcing more people to buy into locked, proprietary systems that would cost them more and more over time. ● http://www.guardian.co.uk/technology/2008/sep/29/cloud.computing.richa rd.stallman
  28. 28. Cloud based thinking
  29. 29. Get satisfaction
  30. 30. Yammer
  31. 31. BaseCamp
  32. 32. Getting out of the cloud
  33. 33. Transferring your content
  34. 34. Transferring your content
  35. 35. Forced account removal
  36. 36. Downtime http://www.flickr.com/photos/henkc7/26544
  37. 37. Server errors http://www.flickr.com/photos/silent_e/3777
  38. 38. www.isTwitterDown.com http://www.flickr.com/photos/monstro/2718187284/
  39. 39. Relying on the network
  40. 40. Yahoo! Pipes
  41. 41. Scraping data
  42. 42. Licensing content http://www.flickr.com/photos/peweck/423497311/
  43. 43. Who owns what?
  44. 44. Creative Commons licences
  45. 45. Licences in applications
  46. 46. Other licences
  47. 47. Facebook Eula “By posting User Content to any part of the Site, you automatically grant, and you represent and warrant that you have the right to grant, to the Company an irrevocable, perpetual, non-exclusive, transferable, fully paid, worldwide license (with the right to sublicense) to use, copy, publicly perform, publicly display, reformat, translate, excerpt (in whole or in part) and distribute such User Content for any purpose, commercial, advertising, or otherwise, on or in connection with the Site or the promotion thereof, to prepare derivative works of, or incorporate into other works, such User Content, and to grant and authorize sublicenses of the foregoing.”
  48. 48. Google Chrome Eula
  49. 49. Old Google Chrome Eula 11. Content licence from you 11.1 You retain copyright and any other rights that you already hold in Content that you submit, post or display on or through the Services. By submitting, posting or displaying the content, you give Google a perpetual, irrevocable, worldwide, royalty- free and non-exclusive licence to reproduce, adapt, modify, translate, publish, publicly perform, publicly display and distribute any Content that you submit, post or display on or through the Services. This licence is for the sole purpose of enabling Google to display, distribute and promote the Services and may be revoked for certain Services as defined in the Additional Terms of those Services.
  50. 50. New Google Chrome Eula 11. Content license from you 11.1 You retain copyright and any other rights you already hold in Content which you submit, post or display on or through, the Services.
  51. 51. Open source loophole It's worth noting that the EULA is largely unenforceable because the source code of Chrome is distributed under an open license. Users could simply download the source code, compile it themselves, and use it without having to agree to Google's EULA. The terms of the BSD license under which the source code is distributed are highly permissive and impose virtually no conditions or requirements on end users.
  52. 52. Participating openly http://www.flickr.com/photos/iconolith/145162224/
  53. 53. Open collaboration
  54. 54. Sharing geological information
  55. 55. Collaborative documents
  56. 56. Exporting collaborative works
  57. 57. Careful collaboration
  58. 58. Permanency
  59. 59. Deep linking
  60. 60. Archived media
  61. 61. Perma-linked Media
  62. 62. Deleting all traces of yourself
  63. 63. Another form of lock in?
  64. 64. Facebook overruled ● Facebook users were right to be concerned about the original distinction between deactivation and deletion. While storing the data was legal - at least in the U.S. ● In Europe, it is possible that Facebook may have violated the law by deactivating, rather than deleting accounts. The UK Data Protection stipulates that companies should not retain data for longer than is necessary. And in January of this year, it was reported that Facebook was reportedly facing an investigation by the UK Information Commissioner's Office based on complaints from users who say their profiles were not properly deleted. ● http://writ.lp.findlaw.com/ramasastry/20080229.html
  65. 65. Facebook overruled ● In sum, users who think that simply removing their Facebook profiles will protect their privacy should think again. Until Facebook changes other rules, serious privacy risks will persist on the site.
  66. 66. Time to get web savvy ● dataportability.com ● autonomo.us ● futureoftheinternet.org ● cyber.law.harvard.edu/projectvrm/Main_Page ● opensocialweb.org ● diso-project.org ● sioc-project.org ● microformats.org/wiki/social-network-portability http://www.flickr.com/photos/gadgettakesapicture/2240511988/
  67. 67. Thank you, any questions? http://www.cubicgarden.com Ian Forrester - ian.forrester@bbc.co.uk http://www.flickr.com/photos/dogseat/436402348/ Presentation : CC BY-NC-SA