{"id":717,"date":"2007-03-09T00:09:50","date_gmt":"2007-03-09T07:09:50","guid":{"rendered":"https:\/\/www.roughtype.com\/wp\/?p=717"},"modified":"2007-03-09T00:09:50","modified_gmt":"2007-03-09T07:09:50","slug":"the_ties_that_b","status":"publish","type":"post","link":"https:\/\/www.roughtype.com\/?p=717","title":{"rendered":"The loose ties that bind"},"content":{"rendered":"<p>Google&#8217;s Matt Cutts <a href=\"http:\/\/www.mattcutts.com\/blog\/not-trapping-users-data-good\/\">gives<\/a> his company and his CEO hearty pats on the back for working to ensure that customers can gain access to the information they feed into Google&#8217;s databases. With Google, he claims, you don&#8217;t feel &#8220;trapped.&#8221; You can always pull your information out of the comapny&#8217;s systems and cart if off to another vendor. He lists the various Google applications that let you &#8211; if you&#8217;re fairly computer-savvy, that is &#8211; export your data: Gmail, Search, Docs, Spreadsheet, Calendar, Talk, Reader, Blogger, AdWords, Groups, Analytics.<\/p>\n<p>The back pats are in general well deserved. Google has a strong record of supporting open formats and data portability.<\/p>\n<p>But reading Cutts&#8217;s laundry list of applications into which customers funnel ever more of their data should also give us pause. As we consolidate more of our personal data into a single company&#8217;s databases &#8211; whether it&#8217;s Google or another firm &#8211; how &#8220;easy&#8221; is it, really, to withdraw our information? The answer is: It&#8217;s not easy at all. In a <a href=\"http:\/\/www.mattcutts.com\/blog\/not-trapping-users-data-good\/#comment-99093\">comment<\/a> on Cutts&#8217;s post, Philipp Lenssen gets at this issue:<\/p>\n<blockquote>\n<p>I agree that Google is rather open in these regards and allows you to export a lot. One thing to remember though is that as soon as Google products cross-integrate \u2014 e.g. a link from Gmail to add an event to Google Calendar \u2014 the costs for users of switching away are increased for any single product. As a practical example, let\u2019s say I love Gmail and I hate Google Calendar, so I want to move to competitor Acme Calendar. Great, you guys offer exporting functionality for my events, so I\u2019ll quickly move them from Acme. But you guys don\u2019t allow me to set my preferred Gmail calendar integration software\u2026 so now I end up with a somewhat broken Gmail feature. This is not at all alarming on this scale, but it can be a problem for users down the road when Google heavily increases cross-integration (Google Checkout is being pushed in search result today, for example, cross-integrating another two theoretically \u201cloosely coupled\u201d services).<\/p><\/blockquote>\n<p>As Lenssen emphasizes in his comment, Google has, as a profit-making company, the right and the incentive to raise its customers&#8217; switching costs. It&#8217;s a smart strategy. But it makes the self-satisifed claims of simple data portability sound at least a little disingenuous. Lenssen points out that &#8220;in the end, any company won\u2019t &#8216;trap data&#8217; for the sheer fun of it, but because they want to create a lock-in situation for their users to increase the costs of switching to competing products. So we need to look at the end result of whether or not the costs of switching are really &#8216;one click.'&#8221;<\/p>\n<p>Google <a href=\"http:\/\/www.readwriteweb.com\/archives\/store_100_googl.php\">said<\/a> last year that one of its core objectives going forward is &#8220;Store 100% of user data.&#8221; By 100%, it means 100%. The company wrote:<\/p>\n<blockquote>\n<p>With infinite storage, we can house all user files, including: emails, web history, pictures, bookmarks, etc and make it accessible from anywhere (any device, any platform, etc) &#8230; As we move toward the &#8220;Store 100%&#8221; reality, the online copy of your data will become your Golden Copy and your local-machine copy serves more like a cache. An important implication &#8230; is that storing 100% of a user&#8217;s data makes each piece of data more valuable because it can be access[ed] across applications. For example: a user&#8217;s Orkut profile has more value when it&#8217;s accessible from Gmail (as addressbook), Lighthouse (as access list), etc.<\/p><\/blockquote>\n<p>There&#8217;s the Faustian rub. Keeping all your data in Google&#8217;s database will make the sharing of that data among different applications much easier and will allow you to do things you couldn&#8217;t do if the data was spread across many companies. At the same time, it raises the cost of extracting any chunk of the data and moving it elsewhere sky high. In a &#8220;Store 100%&#8221; world, the doors may be unlocked, but you ain&#8217;t going nowhere.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google&#8217;s Matt Cutts gives his company and his CEO hearty pats on the back for working to ensure that customers can gain access to the information they feed into Google&#8217;s databases. With Google, he claims, you don&#8217;t feel &#8220;trapped.&#8221; You can always pull your information out of the comapny&#8217;s systems and cart if off to [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1],"tags":[],"class_list":["post-717","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts\/717","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=717"}],"version-history":[{"count":0,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=\/wp\/v2\/posts\/717\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=717"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=717"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.roughtype.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=717"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}