Congratulations!

[Valid Atom 1.0] This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.mnot.net/blog/index.atom

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <feed xmlns="http://www.w3.org/2005/Atom">
  3.  <title>mark nottingham</title>
  4.  <link rel="alternate" type="text/html" href="https://www.mnot.net/blog/" />
  5.  <link rel="self" type="application/atom+xml" href="https://www.mnot.net/blog/index.atom" />
  6.  <id>tag:www.mnot.net,2010-11-11:/blog//1</id>
  7.  <updated>2025-09-23T05:28:46Z</updated>
  8.  <subtitle></subtitle>
  9.  
  10.  <entry>
  11.    <title>Bridging the Gap Between Standards and Policy</title>
  12.    <link rel="alternate" type="text/html" href="https://www.mnot.net/blog/2025/09/20/configuration" />
  13.    <id>https://www.mnot.net/blog/2025/09/20/configuration</id>
  14.    <updated>2025-09-20T00:00:00Z</updated>
  15.    <author>
  16.        <name>Mark Nottingham</name>
  17.        <uri>https://www.mnot.net/personal/</uri>
  18.    </author>
  19.    <summary>Achieving policymakers&apos; goals in coordination with Internet standards activity can be difficult. This post explores some of the options and considerations involved.</summary>
  20.    
  21. <category term="Tech Regulation" />
  22.    
  23. <category term="Standards" />
  24.    
  25. <category term="Web and Internet" />
  26.    
  27.    <content type="html" xml:lang="en" xml:base="https://www.mnot.net/blog/2025/09/20/configuration">
  28.    <![CDATA[<p>Internet standards bodies like the IETF and W3C are places where experts can come to agreement about the details of how technology should work. These communities have the deep experience that allows them to guide the evolution of the Internet towards common goals.</p>
  29.  
  30. <p>Policymakers have none of that technical expertise, but are the legitimate source of policy decisions in any functioning society. They don’t have the means to develop new technical proposals: while most countries have a national standard body, their products are a poor fit for a global Internet, and those bodies generally lack specific expertise.</p>
  31.  
  32. <p>So, it might seem logical for policymakers to turn to Internet standards bodies to develop the technical solutions for their policy goals, trusting the open process and community involvement to produce a good solution. Unfortunately, doing so can create problems that will cause such efforts to fail.</p>
  33.  
  34. <h3 id="whats-the-problem">What’s the Problem?</h3>
  35.  
  36. <p>A few different issues often become apparent when policymakers pre-emptively specify a standard.</p>
  37.  
  38. <p>First, as discussed previously the <a href="https://www.mnot.net/blog/2024/03/13/voluntary">voluntary nature of Internet standards</a> acts as a proving function for them: if implementers don’t implement or users don’t use, the standard doesn’t matter. If a legal mandate to use a particular standard precedes that proof of viability, it distorts the incentives for participation in the process, because the power relationships between participants have changed – it’s no longer voluntary for the targets of the regulation, and the tone of the effort shifts from being <a href="https://www.mnot.net/blog/2024/07/16/collaborative_standards">collaborative</a> to competitive.</p>
  39.  
  40. <p>Second, Internet standards are created by <a href="https://www.mnot.net/blog/2024/05/24/consensus">consensus</a>. That approach to decision making is productive when there is reasonable alignment between participants’ motives, but it’s not well suited to handling fundamental conflicts about societal values. That’s because while technical experts might be good at weighing technical arguments and generally adhering to widely agreed-to principles (whether they be regarding Internet architecture or human rights), it’s much more difficult for them to adjudicate direct conflict between values outside their areas of expertise. In these circumstances, the outcome is often simply a lack of consensus.</p>
  41.  
  42. <p>Third, jurisdictions often have differences in their policy goals, but the Internet is global, and so are its standards bodies, who want the Internet to be interoperable regardless of borders. If policy goals aren’t widely shared and aligned between countries, it becomes even more difficult to come to consensus.</p>
  43.  
  44. <p>Fourth, making decisions with societal impact in a technical expert body raises fundamental legitimacy issues. That’s not to say that Internet standards can’t or shouldn’t (or don’t) change society in significant ways, but that’s done from the position of private actors coordinating to achieve a common goal through well-understood processes, within the practical boundaries of the commonalities of the applicable legal frameworks. It’s entirely different for a contentious policy decision to be delegated by policymakers to a non-representative technical body.</p>
  45.  
  46. <p>So, what’s a policymaker to do?</p>
  47.  
  48. <h3 id="patience-is-a-virtue">Patience is a Virtue</h3>
  49.  
  50. <p>One widely repeated recommendation for policymakers is to avoid specifying the work or even a venue for it in regulation or legislation until <em>after</em> it’s been created and its viability is proven by some amount of market adoption. Instead, the policymaker should just hint that an industry standard that serves a particular policy goal would be useful.</p>
  51.  
  52. <p>However, this approach comes with a few caveats:</p>
  53. <ul>
  54.  <li>A set of proponents that drives the standards work has to emerge, and they need to be at least somewhat aligned with the policy goal</li>
  55.  <li>Consensus-based technical standards are slow, so policymakers have to have realistic expectations about the timeline</li>
  56.  <li>If the targets of the regulation don’t participate in the standards process, they may be able to reasonably claim that what results can’t be implemented by them</li>
  57. </ul>
  58.  
  59. <p>These issues aren’t impossible to address: they just require good communication, alignment of incentives, management of expectations, and careful diligence.</p>
  60.  
  61. <h3 id="add-a-configuration-layer">Add a Configuration Layer</h3>
  62.  
  63. <p>Even if the policymaker waits for the outcome of the standards process, it’s rare for the policy decisions to be cleanly separable from the technology that needed to be created. Choices need to be made about how the technology is used and how it maps to the policy goals of a specific jurisdiction.</p>
  64.  
  65. <p>One intriguing way to manage that gap is to span it with a new entity – one that creates neither technical specifications nor policy goals, but instead is explicitly constituted to define how to meet the stated policy goals using already available technology. That leaves policy formation in the hands of policymakers and technical design in the hands of technologists.</p>
  66.  
  67. <p>In technology terms, this is a configuration layer: clearly and cleanly separating the concerns of how the technology is designed from how it is used. It still requires the technology to exist and have the appropriate configuration “interfaces”, but promises to take a large part of the policy pressure off of the standards process.</p>
  68.  
  69. <p>An example of this approach is just being started by the European Commission now. At IETF 123, they explained a proposal for a <a href="https://www.iepg.org/2025-07-20-ietf123/slides-123-iepg-sessa-multi-stakeholder-forum-on-internet-standards-deployment-00.pdf">Multi-stakeholder Forum on Internet Standards Deployment</a> that fills the gap between the definition of Internet security mechanisms and the policy intent of making European networks more secure. Policymakers have no desire to refer to specific RFCs in legislation, and Internet technologists don’t want to define regulatory requirements for Europe, so the idea is that this third entity will make those decisions without defining new technology <em>or</em> policy intent.</p>
  70.  
  71. <p>Getting this right requires the new forum to be constituted in a particular way. It has to be constrained by the policymaker’s intent, and can’t define new technology. That means that the technology has to be amenable to configuration – the relevant options need to be available. The logical host for the discussion is a venue controlled by the policymaker, but it needs to be open to broad participation (including online and asynchronous participation) so that the relevant experts can participate. Transparency will be key, and I suspect that the decision making policy will be critical to get right – ideally something close to a consensus model, but the policymaker may need to reserve the right to overrule objections or handle appeals.</p>
  72.  
  73. <p>Needless to say, I’m excited to see how this forum will work out. If successful, it’s a pattern that could be useful elsewhere.</p>]]>
  74.    </content>
  75.  </entry>
  76.  
  77.  <entry>
  78.    <title>Using AI to Evaluate Internet Standards</title>
  79.    <link rel="alternate" type="text/html" href="https://www.mnot.net/blog/2025/06/04/using_ai" />
  80.    <id>https://www.mnot.net/blog/2025/06/04/using_ai</id>
  81.    <updated>2025-06-04T00:00:00Z</updated>
  82.    <author>
  83.        <name>Mark Nottingham</name>
  84.        <uri>https://www.mnot.net/personal/</uri>
  85.    </author>
  86.    <summary>Is AI a useful option for policymakers who want to evaluate open standards? Let&apos;s take a look.</summary>
  87.    
  88. <category term="Standards" />
  89.    
  90. <category term="Web and Internet" />
  91.    
  92.    <content type="html" xml:lang="en" xml:base="https://www.mnot.net/blog/2025/06/04/using_ai">
  93.    <![CDATA[<p class="intro">One of the reasons I’m writing the <a href="/blog/series/internet-standards/">Nature of Internet Standards</a> series is to give policymakers tools that help them to understand and evaluate open standards efforts. A big part of that is understanding whether a specification (and the effort that led to it) is really a reflection of open deliberation, consensus processes, appropriate governance, and various other hallmarks of open standards.</p>
  94.  
  95. <p>Evaluating these factors requires a fair amount of context and nuance. What’s the most 2025 way to avoid that work? Using AI, of course.</p>
  96.  
  97. <p>Some colleagues were using AI to ask similar questions, and that inspired me to wonder whether it would be a useful option for policymakers who want to evaluate the openness of Internet standards. Let’s find out.</p>
  98.  
  99. <h2 id="the-privacy-sandbox">The Privacy Sandbox</h2>
  100.  
  101. <p>Our first experiment is an effort that I’m fairly familiar with, having engaged with it both professionally and <a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3891335">academically</a> – Google’s Privacy Sandbox. How will AI portray this longstanding and very politicised effort?</p>
  102.  
  103. <h3 id="prompt">Prompt</h3>
  104.  
  105. <p>I started by asking ChatGPT’s “deep research” mode:</p>
  106.  
  107. <blockquote>
  108.  <p>Is the Privacy Sandbox developed in an open standards process? Consider the venue(s) it’s developed in, their governance, openness, and conformance to other widely recognised signifiers of open standards processes, breadth of implementation, and adoption.</p>
  109. </blockquote>
  110.  
  111. <p>It asked for a few clarifications:</p>
  112.  
  113. <blockquote>
  114.  <p>To give you the most accurate and up-to-date analysis, could you clarify a few things:</p>
  115.  
  116.  <ol>
  117.    <li>Are you primarily interested in the Privacy Sandbox on the web (i.e., as developed by Chrome and the W3C), or are you also considering the Android Privacy Sandbox?</li>
  118.    <li>Do you want a comparison to established open standards processes (e.g., W3C, IETF), or just an evaluation of the Privacy Sandbox initiatives on their own merits?</li>
  119.    <li>Are you looking for an overview of industry support (browsers, advertisers, publishers, etc.) and real-world implementation as part of your evaluation of adoption?</li>
  120.  </ol>
  121.  
  122.  <p>This will help me tailor the research more precisely.</p>
  123. </blockquote>
  124.  
  125. <p>To which I replied:</p>
  126.  
  127. <blockquote>
  128.  <p>Just on the Web. A comparison to open standards processes would be good. I don’t need an overview of support and implementation, but the results should take these factors into account.</p>
  129. </blockquote>
  130.  
  131. <h3 id="response">Response</h3>
  132.  
  133. <p>After churning through data (and pushing the boundaries of copyright) for a couple of minutes, ChatGPT came up with <a href="https://chatgpt.com/s/dr_68252c4763a08191b9339f52d244060e">this voluminous report</a>. However, the heart of its response is concise and fairly damning:</p>
  134.  
  135. <blockquote>
  136.  <p>In summary, the Privacy Sandbox has been developed in semi-open forums (W3C community groups, public repos, Google blogs) and invites outside input, but it is not a widely supported multi-vendor standard yet. Only Google’s Chrome (and related browsers) implements the APIs, and other browser vendors have developed their own approaches. The process resembles an open-source Google project more than a classic consensus-driven SDO. As Mozilla and others have noted, standards bodies like the W3C and IETF are the “ideal forum” to vet such proposals with full stakeholder oversight. At present, Privacy Sandbox’s governance does not fully align with those open standards processes – it provides considerable transparency and documentation, but its development and adoption remain largely controlled by Google.</p>
  137. </blockquote>
  138.  
  139. <p>That’s not far off. W3C Community Groups aren’t standards processes; in fact, they’re little more than mailing lists where the proponents get to set almost all of the rules. ChatGPT could have made this more clear, but instead uses lots of hedging phrases like “more than” and “fully align”.</p>
  140.  
  141. <p>Since the full report mentioned the chair of the Business Group that also discussed the Privacy Sandbox, <a href="http://wendy.seltzer.org">Wendy Seltzer</a>, I asked what she thought. Her response:</p>
  142.  
  143. <blockquote>
  144.  <p>It’s fascinating to follow the sources here, because the Wikipedia article appears to have gotten its last substantive updates in 2024, and is mostly focused on older material ([which is] sometimes wrong). A human researcher would recognize that as not the best authority for recent news. A better human researcher would also ask “is this the question you want to ask, since the non-deprecation of third party cookies has changed the landscape around all these initiatives?”</p>
  145.  
  146.  <p>That illuminates a broader issue of missing context. The answer starts from the premise that “Privacy Sandbox” is something that could be developed in an open standards process, rather than parsing the question, is PS more than the set of APIs and proposals that might fit into standards processes? How do open standards fit into the overall strategy? The GPT report can work for you, an expert in the field who can fill in those aspects, but it could be misleading to someone without the same background.</p>
  147.  
  148.  <p>Some of the sentences quoted from other sources seem off without the context of those sources, e.g. “In January 2020 Google invited ad-tech companies to join the W3C’s Improving Web Advertising Business Group (IWABG) to discuss and give feedback on Privacy Sandbox ideas” reads as implying that Google was the only one doing the inviting.</p>
  149. </blockquote>
  150.  
  151. <h2 id="quic">QUIC</h2>
  152.  
  153. <p>Next, let’s try another effort that I’m familiar with: QUIC, the effort to define a new, performance and security-focused transport protocol. I chaired the <a href="https://quicwg.org/">QUIC Working Group</a> (along with Lars Eggert) from its inception until it shipped its core deliverables.</p>
  154.  
  155. <h3 id="prompt-1">Prompt</h3>
  156.  
  157. <p>I asked ChatGPT’s “deep research” mode a similar question for QUIC:</p>
  158.  
  159. <blockquote>
  160.  <p>Is QUIC developed in an open standards process? Consider the venue(s) it’s developed in, their governance, openness, and conformance to other widely recognised signifiers of open standards processes, breadth of implementation, and adoption.</p>
  161. </blockquote>
  162.  
  163. <p>and once again, it asked for a similar clarification:</p>
  164.  
  165. <blockquote>
  166.  <p>To best address your question about QUIC, could you please clarify what aspect you’re most interested in?</p>
  167.  
  168.  <ul>
  169.    <li>Are you focused more on the technical development and governance process (e.g., how open the standardization process is)?</li>
  170.    <li>Or are you more interested in its current implementation and adoption across the industry?</li>
  171.    <li>Should I compare it to other protocols or standards in terms of openness and adoption?</li>
  172.  </ul>
  173.  
  174.  <p>Let me know so I can tailor the research accordingly.</p>
  175. </blockquote>
  176.  
  177. <p>I responded:</p>
  178.  
  179. <blockquote>
  180.  <p>Focus on how open the standardisation process was, but consider implementation and adoption in your answer. A comparison with other relevant standards would be helpful.</p>
  181. </blockquote>
  182.  
  183. <h3 id="response-1">Response</h3>
  184.  
  185. <p>Here’s the <a href="https://chatgpt.com/share/68253995-9f5c-8009-9dae-405a071aed61">full report</a>. The summary is positively glowing:</p>
  186.  
  187. <blockquote>
  188.  <p>In conclusion, QUIC’s standardization has been as open and transparent as any recent IETF protocol. It was developed in the open IETF process, adhering to OpenStand and WTO/TBT ideals of consensus, transparency, and voluntary adoption. Its final RFCs affirm community consensus, and the IETF infrastructure provided public visibility into every stage. This openness is mirrored by QUIC’s broad support: independent implementers from Google, Mozilla, Apple, Cloudflare, Facebook, and beyond have all deployed QUIC. The resulting ecosystem – with multiple browsers, CDNs, servers and apps supporting QUIC – reinforces that it is a truly open standard, not controlled by any single vendor. By contrast, older protocols like HTTP/2 and TCP underwent similar open processes (IETF consensus, public RFCs) and likewise enjoy ubiquitous implementation. Together, the history and adoption of QUIC demonstrate an effective, open standardization process in line with global best practices.</p>
  189. </blockquote>
  190.  
  191. <p>First of all, I love the reference to the “WTO/TBT ideals of consensus, transparency, and voluntary adoption.”</p>
  192.  
  193. <p>But is it accurate? Sort of. The facts here are correct: those companies did participate in the effort, implemented it, and deployed it. The process was open (as can be seen in the minutes and other materials).</p>
  194.  
  195. <p>I don’t know, however, how it justifies its statements about the quality of consensus – as I’ve written before, <a href="/blog/2024/05/24/consensus">consensus can go wrong in a variety of ways</a>. Others have <a href="https://journals.sagepub.com/doi/full/10.1177/14614448251336438">characterised</a> QUIC’s development has with Google firmly in the “driving seat.” Having been there for the whole standards process, I disagree with that assessment, but I’d at least expect academic work like that to be acknowledged.</p>
  196.  
  197. <h2 id="is-ai-useful-for-assessing-open-standards">Is AI Useful for Assessing Open Standards?</h2>
  198.  
  199. <p>I can’t count the number of times that I’ve seen policymakers, journalists, and community members refer to the Privacy Sandbox as “at the W3C” or “being standardised at the W3C.” Given that extremely low bar, ChatGPT’s summary is an improvement. Likewise, I largely agree with its assessment of QUIC, at a high level.</p>
  200.  
  201. <p>What’s lacking here, however, is any kind of nuance. I can’t escape the feeling that it latches onto a few narratives that appear in source materials and augments them into well-worn clichés, like we see for QUIC. The IETF has a great reputation in many sources, so that gets amplified, but there’s a lack of any critical thought.</p>
  202.  
  203. <p>That’s not surprising: AI can’t think. If it could, it might wonder about the criteria we’re using for “open standards” here – are those WTO/TBT ideals still relevant, and are they adequately described? Are the processes actually used in working groups lining up with the rhetoric of openness – and how would you find out if they didn’t? And, how much should all of that count if the result isn’t <a href="https://www.mnot.net/blog/2024/03/13/voluntary">proven by market adoption</a>?</p>
  204.  
  205. <p>In a nutshell: if you must use AI to assess the openness of a standard, only use it for the first pass, check all of the references, and then roll up your sleeves and start talking to people to get the real story.</p>]]>
  206.    </content>
  207.  </entry>
  208.  
  209.  <entry>
  210.    <title>Apple’s Best Option: Decentralize iCloud</title>
  211.    <link rel="alternate" type="text/html" href="https://www.mnot.net/blog/2025/02/09/decentralize-icloud" />
  212.    <id>https://www.mnot.net/blog/2025/02/09/decentralize-icloud</id>
  213.    <updated>2025-02-09T00:00:00Z</updated>
  214.    <author>
  215.        <name>Mark Nottingham</name>
  216.        <uri>https://www.mnot.net/personal/</uri>
  217.    </author>
  218.    <summary>What can Apple do in the face of a UK order to weaken encryption worldwide? Decentralize iCloud, to start.</summary>
  219.    
  220. <category term="Tech Regulation" />
  221.    
  222. <category term="Web and Internet" />
  223.    
  224.    <content type="html" xml:lang="en" xml:base="https://www.mnot.net/blog/2025/02/09/decentralize-icloud">
  225.    <![CDATA[<p class="intro">As has been <a href="https://www.washingtonpost.com/technology/2025/02/07/apple-encryption-backdoor-uk/">widely reported</a>, the government of the United Kingdom has secretly ordered Apple to build a back door into iCloud to allow ‘blanket capability to view fully encrypted material.’</p>
  226.  
  227. <p>Assuming the UK doesn’t back down, what are Apple’s options? This is my personal take: if I’ve missed something, I’d love to hear about it.</p>
  228.  
  229. <h3 id="option-1-comply">Option 1: Comply</h3>
  230.  
  231. <p>Most companies would just comply with the order, but Apple is not most companies.</p>
  232.  
  233. <p>That’s not just because they have <a href="https://www.apple.com/privacy/">marketed themselves as privacy and security conscious</a>, although that presumably factors into their decision. From what I’ve seen from interacting with their engineers and observing how they behave (both in technical standards bodies and in their products), this is a commitment that goes much deeper than just marketing.</p>
  234.  
  235. <p>More significantly, Apple will be considering the secondary and tertiary consequences of compliance. So far, every democratic country around the world has refrained from making such an order; for example, Australia’s <a href="https://www.mnot.net/blog/2018/11/15/trust_australia">widely debated</a> legislation that mirrors the UK “Snooper’s Charter” has an explicit provision to disallow “systemic weakening” of encryption like we see here.</p>
  236.  
  237. <p>If the UK successfully forces Apple’s hand, every other government in the world is likely to take notice and consider making similar (or even more extreme) demands. <a href="https://www.wired.com/story/apple-photo-scanning-csam-communication-safety-messages/">CSAM scanning</a> will just be the start: once access to that much data is available, it’s open season for everything from <a href="https://en.wikipedia.org/wiki/Lèse-majesté_in_Thailand">Lèse-majesté</a> to punishing activists and protesters to policing sexual orientation, abortion, and other socially motivated laws. Even if a particular country doesn’t make the same demand of Apple, arrangements like Five Eyes will allow one agency to peer over another’s shoulders.</p>
  238.  
  239. <p>As I’ve written before, <a href="https://www.mnot.net/blog/2024/04/29/power">no one should have that much power</a>.</p>
  240.  
  241. <p>In the tinderbox that politics has become in many parts of the world, this is gasoline. I’d pay good money to be a fly on the wall in the meetings taking place with the <a href="https://www.gov.uk/government/organisations/foreign-commonwealth-development-office">Foreign Service</a>, because they of all people should understand the potential global impact of a move like this. Of course, in a world where USAID is shut down by Elon Musk and some teenagers, nothing is off the table – and that’s why we should be so concerned about this outcome.</p>
  242.  
  243. <h3 id="option-2-leave">Option 2: Leave</h3>
  244.  
  245. <p>Apple’s second option is to leave the UK. Full stop.</p>
  246.  
  247. <p>Close the Apple stores, online and retail. Stop providing iCloud, stop selling iPhones and all the other various i-gear. Close the <a href="https://www.businessinsider.com/apple-uk-headquarters-14-billion-redevelopment-battersea-power-station-2016-10">beautiful new UK HQ at Battersea</a>, and lay off (or transfer overseas) around 8,000 employees (reportedly).</p>
  248.  
  249. <p>This is (obviously) the nuclear option. It puts Apple outside the jurisdiction of the UK,<sup id="fnref:1"><a href="#fn:1" class="footnote" rel="footnote" role="doc-noteref">1</a></sup> and at the same time orphans every UK Apple user – their phones and computers don’t quite become bricks, but they will definitely have limited utility and lifetime.</p>
  250.  
  251. <p>Given that along with Apple’s claim to <a href="https://www.standard.co.uk/business/apple-s-spectacular-offices-at-battersea-power-station-b1110130.html">support 550,000 UK jobs</a>, it’s likely to be effective – these consequences would make the government extremely unpopular overnight.</p>
  252.  
  253. <p>However, this option is also massively expensive: reportedly, total Apple revenue in the UK is <a href="https://www.retailgazette.co.uk/blog/2023/07/apple-uk-sales/">something like £1.5bn</a>. Add on top the one-time shutting down costs, and even Apple’s balance sheet will notice.</p>
  254.  
  255. <p>Perhaps more importantly, this is also a strategically worrisome direction to go in, because it plays into the narrative that Big Tech is more powerful than sovereign nations. Other countries will take notice, and may coordinate to overcome Apple’s reticence. Apple will now have to choose the markets that it operates in based on how it feels about those country’s commitments to human rights on an ongoing basis – hardly a situation that any CEO wants to be in.</p>
  256.  
  257. <p>Finally, this option simply won’t work if one of those countries is the United States, Apple’s home. I’ll leave it to you, dear reader, to decide how much you trust your predictions of its actions.</p>
  258.  
  259. <h3 id="option-3-open-up">Option 3: Open Up</h3>
  260.  
  261. <p>Apple’s third option is to remove itself as a target in a more subtle way than option two.</p>
  262.  
  263. <p>The UK is presumably interested in Apple providing this functionality because iCloud’s design conveniently makes a massive amount of data convenient to access in one location: Apple’s servers. If that data is instead spread across servers operated by many different parties, it becomes less available.</p>
  264.  
  265. <p>In effect, this is the <strong>decentralize iCloud</strong> option. Apple would open up its implementation of iCloud so that third-party and self-hosted providers could be used for the same functions. They would need to create interfaces to allow switching, publish some specifications and maybe some test suites, and make sure that there weren’t any intellectual property impediments to implementation.</p>
  266.  
  267. <p>There could be some impact on Apple revenue here, but I suspect it’s not huge; many people would continue to buy iCloud for convenience, and for non-storage features that Apple bundles in <a href="https://www.apple.com/icloud/">iCloud+</a>.</p>
  268.  
  269. <p>Think of it this way: Apple provides e-mail service with iCloud, but doesn’t require you to use it: you can use your own or a third party provider without any drama, because they use common protocols and formats. Why should file sync be any different? Why can’t Apple make using a third-party service as seamless and functional as iCloud?</p>
  270.  
  271. <p>This isn’t a perfect option. Orders could still force weakened encryption, but now they’d have to target many different parties (depending on the details of implementation and deployment), and they’d have to get access to the stored data. If you choose a provider in another jurisdiction, that makes doing so more difficult, depending on what legal arrangements are in place between those jurisdictions; if you self-host, they’ll need to get physical access to your disks.</p>
  272.  
  273. <h3 id="what-will-and-should-apple-do">What Will (and Should) Apple Do?</h3>
  274.  
  275. <p>Computer operating systems are fundamental to security: once we lose trust in them, it’s pretty much game over. The UK has chosen a risky and brash path forward, and Apple will need to think carefully about how to navigate it.</p>
  276.  
  277. <p>It should be no surprise that I favour option three. While Apple is notoriously a closed company, it’s not completely averse to collaborating and working in the open when doing so is in its interests – and, given its other options, that’s arguably the case here.</p>
  278.  
  279. <p>Conceivably, Apple might even be forced into taking the “decentralize iCloud” option if regulators like those implementing the Digital Markets Act in the EU decide that doing so is necessary for competition. Apple has been <a href="https://ec.europa.eu/competition/digital_markets_act/cases/202344/DMA_100025_228.pdf">designated as a gatekeeper</a> for the ‘core platform service’ provided by iOS, and while that designation currently doesn’t include file synchronisation services, that might change.</p>
  280.  
  281. <p>Of course, the UK government may back down. However, the barrier to some other government taking similar steps is now smaller, and Apple would do well to consider its longer term options even if action turns out to be unnecessary right now.</p>
  282.  
  283. <p><em>Thanks to <a href="https://eupolicy.social/@1br0wn">Ian Brown</a> for his input to this article.</em></p>
  284.  
  285. <div class="footnotes" role="doc-endnotes">
  286.  <ol>
  287.    <li id="fn:1">
  288.      <p>Presumably. Both inter-jurisdictional coordination and extraterritorial application of the law may complicate that. IANAL. <a href="#fnref:1" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
  289.    </li>
  290.  </ol>
  291. </div>]]>
  292.    </content>
  293.  </entry>
  294.  
  295.  <entry>
  296.    <title>Platform Advantages: Not Just Network Effects</title>
  297.    <link rel="alternate" type="text/html" href="https://www.mnot.net/blog/2024/11/29/platforms" />
  298.    <id>https://www.mnot.net/blog/2024/11/29/platforms</id>
  299.    <updated>2024-11-29T00:00:00Z</updated>
  300.    <author>
  301.        <name>Mark Nottingham</name>
  302.        <uri>https://www.mnot.net/personal/</uri>
  303.    </author>
  304.    <summary>A new book explores an intriguing idea: that there are core processes in some platforms that naturally tilt the table towards being implemented in a single company.</summary>
  305.    
  306. <category term="Tech Regulation" />
  307.    
  308. <category term="Web and Internet" />
  309.    
  310.    <content type="html" xml:lang="en" xml:base="https://www.mnot.net/blog/2024/11/29/platforms">
  311.    <![CDATA[<p class="intro">Over the past few years, there’s been growing legal and academic interest in <em>platforms</em> — their functioning, potential harms, and advantages over competitors.</p>
  312.  
  313. <p>On that last question, most of the literature that I’ve seen has focused on factors like network effects and access to data. However, a forthcoming book by <a href="https://www.hbs.edu/faculty/Pages/profile.aspx?facId=6417">Carliss Baldwin</a> proposes some significant additional – and structural – advantages that accrue to those who control them. <em><a href="https://mitpressbookstore.mit.edu/book/9780262049337">Design Rules Volume 2: How Technology Shapes Organizations</a></em><sup id="fnref:1"><a href="#fn:1" class="footnote" rel="footnote" role="doc-noteref">1</a></sup>
  314. builds on Volume One (which I <a href="https://www.mnot.net/blog/2024/05/10/design-rules-vol-one">wrote about earlier</a>) with a goal to ‘build and defend a general theory explaining how technologies affect the structure and evolution of organizations that implement the technologies.’</p>
  315.  
  316. <p>Baldwin argues that “whether a technology will generate the most value through single, unified corporations, through platform-based business ecosystems, or through open source projects depends on the balance of <em>complementarity</em> within the technical system.” Let’s unpack that (in my words, with apologies for any misinterpretation of her work).</p>
  317.  
  318. <h3 id="modularity">Modularity</h3>
  319. <p>Imagine a technical system, such as a service provided across the Internet, that comprises numerous components. This is a common occurrence because, as mentioned in Volume One, we manage complexity through modularity. We break down tasks into smaller units that can be distributed among many individuals, preventing any single person from having to comprehend the entire system’s intricacies.</p>
  320.  
  321. <p>These components can have various degrees of <em>coupling</em> – i.e., interdependency. While we always strive for <em>loose</em> coupling, which allows for easy modification or replacement of components without affecting others, it’s not always feasible to avoid <em>tight</em> coupling when there are close dependencies.</p>
  322.  
  323. <h3 id="coupling-and-governance">Coupling and Governance</h3>
  324. <p>Baldwin points out that systems with many tightly coupled functions are better situated in a single company due to the ease of managing these relationships within the hierarchical and closely related environment of a modern corporation. Conversely, she suggests that those with very loosely coupled functions are more appropriate for implementation across multiple entities because this arrangement enables the generation of greater overall value.</p>
  325.  
  326. <p>In the middle lies a “Goldilocks zone,” where some amount of coordination is necessary, but there’s still a benefit to distributing functions amongst many actors. These conditions allow formation of a <em>business ecosystem</em> – a set of “independent organizations and individuals engaged in complimentary activities and investments.” As Baldwin points out:</p>
  327.  
  328. <blockquote>
  329.  <p>Ecosystems rely on <em>distributed governance</em>, meaning that each member has the right to make certain decisions according to his or her own interests and perceptions. In place of direct authority, coordination of an ecosystem requires <em>negotiation</em> among members with different priorities and interests.</p>
  330. </blockquote>
  331.  
  332. <h3 id="platforms">Platforms</h3>
  333. <p>There are many examples of such distributed governance schemes, including Open Source and Open Standards. However, it’s hard to ignore the dominance of <em>platforms</em> in the current landscape, which she defines as ‘a technological means of coordinating design, production, and exchange within modular architectures.’ Platforms aren’t so much distributed governance schemes as they are centralised control points (or even <a href="https://www.rfc-editor.org/rfc/rfc9518.html">choke points</a>).</p>
  334.  
  335. <p>She then goes on to break down a typology of platforms, with particular focus on <em>transaction platforms</em>, like eBay, Amazon, and Chrono24 – and <em>communication platforms</em>, such as Facebook, Bluesky, and X.</p>
  336.  
  337. <p>Here’s where things get really interesting. Baldwin argues that certain <em>core processes</em> which are essential to implement these types of platforms are bound to be tightly coupled, thereby heavily tilting the table towards implementation by a single company:</p>
  338.  
  339. <blockquote>
  340.  <p>The need for tight integration of core processes is the first reason for-profit corporations subject to unified governance have replaced organizations subject to distributed governance in almost all digital exchange platforms. Traditional exchange processes did not require the same high degree of synchronization as algorithmic processes.</p>
  341. </blockquote>
  342.  
  343. <p>In transaction platforms, she identifies <em>search and ad placement</em>, <em>dynamic pricing</em>, and <em>data analysis and prediction</em> as processes that must occur within milliseconds to provide a satisfactory user experience. For communication platforms, the relevant core services are <em>search and ad placement</em>, <em>ad selection</em>, <em>dynamic pricing of an ad</em>, and (again) <em>data analysis and prediction</em>.</p>
  344.  
  345. <h3 id="what-this-means-for-the-internet">What this means for the Internet</h3>
  346. <p>Yes, search is more difficult on a federated platform like Mastodon, but it’s possible if you relax the need for immediate updates – as it can be if you <a href="https://berjon.com/fixing-search/#how-does-search-work-">rework the relationships in that arena</a>. When you get past that, it’s also hard not to notice that these core processes are mostly advertising-related.</p>
  347.  
  348. <p>And that’s crucial. These companies have stepped in to solve coordination problems (“How do we communicate around the globe? How do we do transactions with people we haven’t met?”) by creating platforms that fully exploit their centralization. They are supported by real-time advertising systems because the table is tilted towards that outcome, and building a real-time advertising-supported ecosystem with distributed governance is <em>hard</em>.<sup id="fnref:2"><a href="#fn:2" class="footnote" rel="footnote" role="doc-noteref">2</a></sup></p>
  349.  
  350. <p>Much of that friction goes away if you relax the constraint of being advertising-supported, or even remove the real-time requirement from advertising (e.g., by using contextual advertising). However, you still have a coordination problem, and because real-time advertising is the most lucrative way to monetise a centralized position, decentralizing these systems means big companies won’t be nearly as interested in these outcomes.</p>
  351.  
  352. <p>The history of the Internet is illustrative here. We had RSS and Atom feeds, but there wasn’t a business model in that: however, there was in ‘news feeds’ on Facebook. We had open messaging protocols like XMPP, but they were supplanted by proprietary chat platforms that wanted to lock their users in and monetise them. Meanwhile, e-mail is being slowly swallowed by GMail and a few others as we helplessly watch.</p>
  353.  
  354. <p>In short: <strong>there are less-recognised structural forces that push key Internet services into centralized, real-time advertising-supported platforms</strong>. Along with factors like network effects and access to data, they explain some of why the Internet landscape looks like it does.</p>
  355.  
  356. <p>Decentralized alternatives must overcome those forces where they can’t be avoided. They also need to be developed and supported, and to compete with those centralised platforms, they will need to be well-funded. To go back to the RSS/Atom example, there is a <a href="https://www.mnot.net/blog/2024/08/25/feeds">lot of work that could improve that ecosystem</a>, but no one has a strong incentive to do so.</p>
  357.  
  358. <p>In these conditions, ‘build it and they will come’ is insufficient; simply creating Internet standards and Open Source software won’t solve the coordination challenges. Most current Internet companies lack the incentive to fund such efforts since they’re unlikely to accommodate real-time advertising.</p>
  359.  
  360. <p>Who might? My thoughts turn to the various discussions surrounding <a href="https://www.undp.org/digital/digital-public-infrastructure">Digital Public Infrastructure</a>. Exploring how to make that viable is a crucial (and important) topic that I’ll leave for another day.</p>
  361.  
  362. <p>This is just one aspect of <em>Design Rules Volume 2</em>; there’s much more to discover in this excellent book. I’ve been enthusiastically recommending it to anyone who takes the time to listen.</p>
  363.  
  364. <p><em>Thanks to <a href="https://berjon.com/">Robin Berjon</a> for reviewing this article.</em></p>
  365.  
  366. <div class="footnotes" role="doc-endnotes">
  367.  <ol>
  368.    <li id="fn:1">
  369.      <p>To be published on 24 December. Many thanks to Professor Baldwin for an early copy. <a href="#fnref:1" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
  370.    </li>
  371.    <li id="fn:2">
  372.      <p>Again, not necessarily impossible; for example, look at what Mozilla et al are doing in the <a href="https://patcg.github.io">Private Advertising Technology</a> effort. <a href="#fnref:2" class="reversefootnote" role="doc-backlink">&#8617;</a></p>
  373.    </li>
  374.  </ol>
  375. </div>]]>
  376.    </content>
  377.  </entry>
  378.  
  379.  <entry>
  380.    <title>On Opting Out of Copyright</title>
  381.    <link rel="alternate" type="text/html" href="https://www.mnot.net/blog/2024/09/18/opt-out" />
  382.    <id>https://www.mnot.net/blog/2024/09/18/opt-out</id>
  383.    <updated>2024-09-18T00:00:00Z</updated>
  384.    <author>
  385.        <name>Mark Nottingham</name>
  386.        <uri>https://www.mnot.net/personal/</uri>
  387.    </author>
  388.    <summary>The EU AI Act and emerging practice flip copyright’s default opt-in regime to an opt-out one. What effects is this likely to have on the balance of power between rights holders and reuse?</summary>
  389.    
  390. <category term="Tech Regulation" />
  391.    
  392. <category term="Web and Internet" />
  393.    
  394.    <content type="html" xml:lang="en" xml:base="https://www.mnot.net/blog/2024/09/18/opt-out">
  395.    <![CDATA[<p class="intro">The EU AI Act and emerging practice flip copyright’s default opt-in regime to an opt-out one. What effects is this likely to have on the balance of power between rights holders and reuse?</p>
  396.  
  397. <p>Copyright is a default opt-in regime, from the standpoint of the rights holder. If I publish something on this blog, the presumption is that I retain rights unless I specifically license them – for example, by attaching a <a href="http://creativecommons.org">creative commons</a> license. If I don’t do that, you can’t legally reuse my content (unless your use falls within certain exemptions).</p>
  398.  
  399. <p>You can think about this arrangement in terms of protocol design: it’s an agreement between parties whose nature creates certain incentives and barriers to behaviour. Someone who wants to reuse my content has the burden of getting a license from me, and proving that they have one if I challenge them. I have the burden of finding misuse of my content and pursuing it.</p>
  400.  
  401. <p>Technical systems can assist both parties in these tasks. I can use search engines of various sorts to find potential abuses; a licensee can prove that a particular license was available by showing its existence in the cache of a disinterested third party (often, one of the same search engines).</p>
  402.  
  403. <p>This creates an equilibrium: the burdens are balanced to favour certain behaviours. You might argue that the balance is unjust (and many <a href="https://pluralistic.net">do</a>), but it is known and stable.</p>
  404.  
  405. <p class="hero">As <a href="https://www.mnot.net/blog/2024/04/21/ai-control">discussed previously</a>, the EU AI Act and emerging practice flip copyright’s default opt-in regime to an opt-out one. A rights holder now has to take positive action if they want to reserve their rights. While on the face of it they still have the same capability, this ends up being a significant practical shift in power.</p>
  406.  
  407. <p>That’s partly because of the nature of opt-out itself. The burden shifts: now, the rights holder must find misuse of their content, <em>and</em> prove that they opted out.</p>
  408.  
  409. <p>Proving that you consistently opted out at every opportunity is difficult, because it’s effectively proving a negative – that you never failed to opt out. Search engines don’t see every request made on the Internet; they just crawl it periodically, sampling what they see. An AI crawler can plausibly claim that the opt out wasn’t present when they crawled, and the rights holder is reduced to proving that the teapot isn’t in orbit.</p>
  410.  
  411. <p>Notably, this is the case whether the opt-out is attached to the content by a mechanism like robots.txt or if it’s embedded in the content itself as metadata. In the former case, content without the opt-out might be obtained at a different location, or at a different time; in the latter, the opt-out might be stripped from the content or a copy of it, either intentionally or unintentionally (e.g. it is a common to strip metadata from images to optimise performance and improve privacy).</p>
  412.  
  413. <p>On top of that, using this regime for AI makes finding misuse difficult too. There’s no easy way to query an LLM for a particular bit of content in the corpus that was used to train it; instead, you have to trust the vendor to tell you what they used. While transparency measures are being discussed as a policy solution to this issue, they don’t have the same properties as third-party or technical verification, in that they require trusting assertions from the vendor.</p>
  414.  
  415. <p>In this manner, changing copyright’s default opt-in to an opt-out for AI dramatically shifts the burden of compliance to rights holders, and the lack of support for managing those burdens brings into question the practical enforceability of the regime. It could be argued that this is appropriate for policy reasons – in particular, to enable innovation. However, it is a mistake to say it doesn’t represent a change in the balance of power as compared to opt-in.</p>]]>
  416.    </content>
  417.  </entry>
  418.  
  419. </feed>
  420.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.mnot.net/blog/index.atom

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda