{"id":1565,"date":"2019-03-11T15:59:41","date_gmt":"2019-03-11T23:59:41","guid":{"rendered":"https:\/\/blog.mozilla.org\/netpolicy\/?p=1565"},"modified":"2019-03-11T15:59:41","modified_gmt":"2019-03-11T23:59:41","slug":"meet-the-newest-walled-garden","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/","title":{"rendered":"Meet the newest walled garden"},"content":{"rendered":"

Recently, Mark Zuckerberg posted a lengthy note outlining Facebook\u2019s <\/a>vision to integrate its three messaging services – WhatsApp, Messenger, and Instagram (through its Direct messaging functionality) – into one privacy and security oriented platform. The post positioned Facebook\u2019s future around individual and small group conversations, rather than the \u201cpublic forum\u201d style communications through Facebook\u2019s newsfeed platform. Initial coverage of the move, largely critical, has focused on the privacy<\/a> and security<\/a> aspects of this integrated platform, the history of broken promises on privacy<\/a> and the changes that would be needed for Facebook\u2019s business model to realize the goal<\/a>. However, there\u2019s a yet darker side to the proposal, one mostly lost in the post and coverage so far: Facebook is taking one step further to make its family of services into the newest walled garden, at the expense of openness and the broader digital economy.<\/p>\n

Here\u2019s the part of the post that highlights the evolution in progress:<\/p>\n

\"\"<\/a>
\nSounds good on its face, right? Except, what Facebook is proposing isn\u2019t interoperability as most use that term<\/a>. It\u2019s more like intraoperability<\/i> – making sure the various messaging services in Facebook\u2019s own walled garden all can communicate with each other, not with other businesses and services. In the context of this post, it seems clear that Facebook will intentionally box out other companies, apps, and networks in the course of this consolidation. Rather than creating the next digital platform to take the entire internet economy forward, encouraging downstream innovation, investment, and growth, Facebook is closing out its competitors and citing privacy and security considerations as its rationale.<\/p>\n

This is not an isolated incident – it\u2019s a trend. For example, on August 1, 2018, Facebook shut off the “publish_actions” feature in one of its core APIs. This change gutted the practical ability of independent companies and developers to interoperate with Facebook\u2019s services. Some services were forced to disconnect Facebook profiles<\/a> or stop interconnecting with Facebook entirely<\/a>. Facebook subsequently changed a long-standing platform policy that had prohibited the use of their APIs to compete<\/a>, but the damage was done, and the company’s restrictive practices continue.<\/p>\n

We can see further evidence of the intent to create a silo under the guise of security in Zuckerberg\u2019s note where he says: \u201cFinally, it would create safety and spam vulnerabilities in an encrypted system to let people send messages from unknown apps where our safety and security systems couldn’t see the patterns of activity.\u201d Security and spam are real problems, but interoperability doesn\u2019t need to mean opening a system up to every incoming message from any service. APIs can be secured by tokens and protected by policies and legal systems.<\/p>\n

Without doubt, Facebook needs to prioritize the privacy of its users. Shutting down overly permissive APIs, even at the cost of some amount of competition and interoperability, can be necessary for that purpose – as with the Cambridge Analytica incident. But there\u2019s a difference between protecting users and building silos. And designing APIs that offer effective interoperability with strong privacy and security guarantees is a solvable problem.<\/p>\n

The long-term challenge we need to be focused on with Facebook isn\u2019t just whether we can trust the company with our privacy and security – it\u2019s also whether they\u2019re using privacy and security simply as a cover to get away with anticompetitive behavior.<\/p>\n

How does this square with the very<\/i> active conversations around competition and centralization in tech<\/a> we\u2019re witnessing around the world today? The German competition authority just issued a decision forcing Facebook to stop sharing data<\/a> amongst its services. This feels like quite the discordant note for Facebook to be casting, even as the company is (presumably) thinking about how to comply with the German decision. Meanwhile, the Federal Trade Commission is actively pursuing an investigation<\/a> into Facebook\u2019s data practices. And regulators in the U.S., the European Union, India, Israel, and Australia are actively reviewing their antitrust and competition laws to ensure they can respond to the challenges posed by technology and data.<\/p>\n

It\u2019s hard to say whether integrating its messaging services will further entrench Facebook\u2019s position, or make it harder to pursue the kinds of remedies directed by the Bundeskartellamt and being considered by politicians around the world. But it seems like Facebook is on a collision course towards finding out.<\/p>\n

If Facebook believes that messaging as a platform offers incredible future innovation, the company has a choice. It could either seek to develop that potential within a silo, the way AT&T fostered innovation in telephones in the 1950s<\/a> – or it could try the way the internet was built to work: offering real interoperability on reasonable terms so that others can innovate downstream.<\/p>\n","protected":false},"excerpt":{"rendered":"

Recently, Mark Zuckerberg posted a lengthy note outlining Facebook\u2019s vision to integrate its three messaging services – WhatsApp, Messenger, and Instagram (through its Direct messaging functionality) – into one privacy … Read more<\/a><\/p>\n","protected":false},"author":665,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"coauthors":[311512],"yoast_head":"\nMeet the newest walled garden - Open Policy & Advocacy<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Chris Riley\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/\",\"url\":\"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/\",\"name\":\"Meet the newest walled garden - Open Policy & Advocacy\",\"isPartOf\":{\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blog.mozilla.org\/netpolicy\/files\/2019\/03\/Screen-Shot-2019-03-07-at-2.30.43-PM-600x184.png\",\"datePublished\":\"2019-03-11T23:59:41+00:00\",\"dateModified\":\"2019-03-11T23:59:41+00:00\",\"author\":{\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/#\/schema\/person\/92c467284d1b178dea38bea5386a5263\"},\"breadcrumb\":{\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/#primaryimage\",\"url\":\"https:\/\/blog.mozilla.org\/netpolicy\/files\/2019\/03\/Screen-Shot-2019-03-07-at-2.30.43-PM.png\",\"contentUrl\":\"https:\/\/blog.mozilla.org\/netpolicy\/files\/2019\/03\/Screen-Shot-2019-03-07-at-2.30.43-PM.png\",\"width\":1250,\"height\":384},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.mozilla.org\/netpolicy\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Meet the newest walled garden\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/#website\",\"url\":\"https:\/\/blog.mozilla.org\/netpolicy\/\",\"name\":\"Open Policy & Advocacy\",\"description\":\"Mozilla's official blog on open Internet policy initiatives and developments\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.mozilla.org\/netpolicy\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/#\/schema\/person\/92c467284d1b178dea38bea5386a5263\",\"name\":\"Chris Riley\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.mozilla.org\/netpolicy\/#\/schema\/person\/image\/559fa836e2ec3814f8e5ac20d5b8cae6\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/4778f215cde88b189620cafd0476b440?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/4778f215cde88b189620cafd0476b440?s=96&d=mm&r=g\",\"caption\":\"Chris Riley\"},\"description\":\"Head of Public Policy, Mozilla\",\"sameAs\":[\"https:\/\/blog.mozilla.org\/netpolicy\/\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Meet the newest walled garden - Open Policy & Advocacy","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/","twitter_misc":{"Written by":"Chris Riley","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/","url":"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/","name":"Meet the newest walled garden - Open Policy & Advocacy","isPartOf":{"@id":"https:\/\/blog.mozilla.org\/netpolicy\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/#primaryimage"},"image":{"@id":"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/#primaryimage"},"thumbnailUrl":"https:\/\/blog.mozilla.org\/netpolicy\/files\/2019\/03\/Screen-Shot-2019-03-07-at-2.30.43-PM-600x184.png","datePublished":"2019-03-11T23:59:41+00:00","dateModified":"2019-03-11T23:59:41+00:00","author":{"@id":"https:\/\/blog.mozilla.org\/netpolicy\/#\/schema\/person\/92c467284d1b178dea38bea5386a5263"},"breadcrumb":{"@id":"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/#primaryimage","url":"https:\/\/blog.mozilla.org\/netpolicy\/files\/2019\/03\/Screen-Shot-2019-03-07-at-2.30.43-PM.png","contentUrl":"https:\/\/blog.mozilla.org\/netpolicy\/files\/2019\/03\/Screen-Shot-2019-03-07-at-2.30.43-PM.png","width":1250,"height":384},{"@type":"BreadcrumbList","@id":"https:\/\/blog.mozilla.org\/netpolicy\/2019\/03\/11\/meet-the-newest-walled-garden\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.mozilla.org\/netpolicy\/"},{"@type":"ListItem","position":2,"name":"Meet the newest walled garden"}]},{"@type":"WebSite","@id":"https:\/\/blog.mozilla.org\/netpolicy\/#website","url":"https:\/\/blog.mozilla.org\/netpolicy\/","name":"Open Policy & Advocacy","description":"Mozilla's official blog on open Internet policy initiatives and developments","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.mozilla.org\/netpolicy\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blog.mozilla.org\/netpolicy\/#\/schema\/person\/92c467284d1b178dea38bea5386a5263","name":"Chris Riley","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.mozilla.org\/netpolicy\/#\/schema\/person\/image\/559fa836e2ec3814f8e5ac20d5b8cae6","url":"https:\/\/secure.gravatar.com\/avatar\/4778f215cde88b189620cafd0476b440?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/4778f215cde88b189620cafd0476b440?s=96&d=mm&r=g","caption":"Chris Riley"},"description":"Head of Public Policy, Mozilla","sameAs":["https:\/\/blog.mozilla.org\/netpolicy\/"]}]}},"_links":{"self":[{"href":"https:\/\/blog.mozilla.org\/netpolicy\/wp-json\/wp\/v2\/posts\/1565"}],"collection":[{"href":"https:\/\/blog.mozilla.org\/netpolicy\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.mozilla.org\/netpolicy\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/netpolicy\/wp-json\/wp\/v2\/users\/665"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.mozilla.org\/netpolicy\/wp-json\/wp\/v2\/comments?post=1565"}],"version-history":[{"count":0,"href":"https:\/\/blog.mozilla.org\/netpolicy\/wp-json\/wp\/v2\/posts\/1565\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.mozilla.org\/netpolicy\/wp-json\/wp\/v2\/media?parent=1565"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.mozilla.org\/netpolicy\/wp-json\/wp\/v2\/categories?post=1565"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.mozilla.org\/netpolicy\/wp-json\/wp\/v2\/tags?post=1565"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blog.mozilla.org\/netpolicy\/wp-json\/wp\/v2\/coauthors?post=1565"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}