Jack Dorsey resigned from Twitter today, his second departure from the company he co-founded, this one voluntary, with a resignation letter arguing against the cult of the founder-CEO itself (“there’s a lot of talk about the importance of a company being ‘founder-led.’ Ultimately I believe that’s severely limiting and a single point of failure,” the man cited SPOF doctrine in his farewell; the archive has never felt more seen by an executive departure). CTO Parag Agrawal inherits the seat, the activist-investor pressure (Elliott’s file has wanted this for years), and the eternal Twitter question: the most culturally load-bearing, financially underperforming platform in the industry (the outrage-optimizer, the deplatforming precedent, the $4.4M-per-word episode, this archive’s index is substantially a Twitter incident log). Dorsey retreats to Block/Square and his bitcoin evangelism (the Web3 wars lose their most interesting combatant on the anti-VC flank). The file’s read: founder-succession is the least-practiced migration in tech (the Basecamp SPOF clause, the incentive-aligned boards), and Twitter is about to run the experiment with maximum observability. The universe, as is its custom with this platform, will make the results interesting beyond anyone’s intent. ...

The us-east-1 Problem (Jul 2020 – Sep 2021) Filed November 25, 2021 — the first anniversary of the Kinesis event, the archetypal us-east-1 story. The incidents in this window share a shape. Something small and deep (a thread limit, a quota system, one customer’s config change) spreads out until half the internet feels it. Readers started asking a new first question: what does everything else quietly depend on? The incidents that defined the period AWS Kinesis / us-east-1, November 25, 2020. Adding capacity to Kinesis’s front-end fleet pushed servers past an OS thread limit. The fleet needed a slow full restart, and services that depended on it (Cognito, CloudWatch, and various vendors’ status pages) went down with it (aws.amazon.com/message/11201). The postmortem taught a lot of engineers what a cell-based architecture is by describing what it looks like to not have one. Google, December 14, 2020. The identity and quota system took down Gmail, YouTube, and Google Cloud auth for about 47 minutes. An automated quota migration reported usage as zero and starved the auth service. Safety systems that can’t tell “no usage” from “no data” became a recurring theme. Slack, January 4, 2021. First workday of the year. Provisioning couldn’t scale up in AWS fast enough, and Slack’s own dashboards were degraded during the response (slack.engineering). OVHcloud fire, March 2021. A Strasbourg datacenter burned, and some customers learned their backups were in the building that was on fire. Physical DR came back into the conversation. Fastly, June 8, 2021. A dormant bug shipped in May was triggered by one customer’s valid config change and dropped about 85% of Fastly’s network. Global outage in seconds, found in minutes, mostly restored within an hour (fastly.com). Reuters, gov.uk, and Amazon went dark together. Forty-nine minutes that made “CDN concentration” a mainstream news topic. Akamai Edge DNS, July 2021. A bug triggered by a config update took down banks and airlines for about an hour. Same lesson, different CDN. What the postmortems reveal Control plane versus data plane became the sharpest way to look at these. Google’s quota system, AWS’s front-end metadata fleet, Fastly’s config distribution: in each case the management machinery failed while the actual capacity was fine. “Static stability,” meaning the data plane keeps working when the control plane is down, became the goal to design toward. ...

Peak fortnight, the archive files it as a peak with the confidence of pattern and the humility of every prior date-unknowable clause: Bitcoin touched ~$69,000 (the meme number, of course it was the meme number) and Ethereum ~$4,800 on the 8th-10th; the total crypto market brushed $3 trillion; NFT volume is annualizing in the tens of billions; a DAO is forming to bid on an actual copy of the US Constitution (ConstitutionDAO, the coordination engine now performing civics); and “Web3” has completed its capture of the discourse, a16z is deploying billions into the thesis that tokenized protocols re-decentralize the internet, while the counter-thesis (that VC-held tokens are shareholder capitalism cosplaying as revolution, with worse liquidity ethics) is being argued by, among others, Jack Dorsey, whose fights with the a16z partners are the season’s best theater. The file’s position, matured across eight years of this thread: the decentralization claim is the thing to audit, follow the token allocations, the infrastructure chokepoints (most “decentralized” apps resolve through two or three RPC providers, the Fastly lesson pre-installed), and the governance quorums, and Web3’s org chart looks remarkably like Web2’s cap table (the renaming doctrine: the pivot announces itself before the architecture changes). The primitives remain real; the winter remains scheduled; the archive remains grateful it filed Dogecoin’s birth and will presumably file its afterlife. ...

Facebook is now Meta. Announced Thursday at Connect: new name, infinity-loop logo, and a keynote staking the company’s identity on the metaverse, legless avatars in virtual meeting rooms, a ten-billion-dollar-a-year Reality Labs burn rate, and Zuckerberg narrating a future where the Fortnite-concert thread becomes the primary human interface. The file’s read requires holding three things at once (staff prerogative): the timing is transparently a narrative rotation, three weeks after the Files, three weeks after the outage, the century’s most scrutinized brand exits stage left (the archive notes Philip Morris to Altria and awaits the comparison aging); the bet is nonetheless real, $10B/year is not a PR line item, and the VR/AR hardware roadmap is the most serious in the industry; and the thesis remains unproven at its core, every metaverse demo answers “can we render presence?” while the market keeps asking “do we want to wear it?” (the Stadia clause: the idea’s inevitability and this instance’s questionability are independent variables). The archive’s own receipts cut both ways: it filed the virtual-concert genre as real culture, and files corporate renamings under “the org chart is the last thing to know it’s pivoting” (Alphabet, which, checking the file, remained a search-ads company wearing a holding structure). Grading window: a decade. Position: the hardware will matter; the brand-name future will be built substantially by other people, likely gaming companies, on the timeline gaming always runs, the fun version ships first. ...

October 4th: Facebook, Instagram, and WhatsApp disappeared, not “slow,” not “erroring,” gone from the internet for nearly six hours, for 3.5 billion users, in the most instructive outage this archive has ever filed (and it files against stiff competition). The mechanism, per Facebook’s own postmortem: a routine backbone-maintenance command (audit tooling bug: the check that should have blocked it, didn’t, the old dropdown lesson at backbone scale) disconnected their datacenters from each other; their DNS servers, designed to withdraw BGP route advertisements when they can’t reach the datacenters (a health-check behaving exactly as specified), dutifully removed Facebook’s nameservers from the internet’s routing table; and then the recovery dependencies detonated in sequence, remote access died with the network it managed, internal tools died with the platform they ran on, and (the detail that made every ops engineer inhale sharply) badge readers on the datacenter doors reportedly failed because they too authenticated against the dead systems. Engineers physically drove to sites and struggled to get into the buildings containing the routers they needed to fix. The map burned with the territory: monitoring, comms, tooling, and doors all downstream of the failure they were needed to repair (my own monitor-moving car trip was this lesson at 1/1,000,000th scale). Every org ran the same audit within the week, ours included: our break-glass runbook lived in a wiki whose auth ran through the SSO that a network partition would… yes. It’s printed now. Printed. Paper: the ultimate out-of-band. ...

The Wall Street Journal has spent the fortnight publishing “The Facebook Files,” a series built on internal research leaked by a then-anonymous source: the company’s own studies showing Instagram’s measured harm to teen-girl wellbeing (slides quantifying it), the “XCheck” program exempting millions of VIPs from moderation rules (a formalized two-tier justice system with a whitelist), anti-vaccine content metrics the public denials contradicted, and engagement-ranking changes (2018’s “meaningful social interactions”) that internal researchers documented as rewarding outrage, with publishers and parties telling Facebook directly they’d shifted to angrier content to survive the algorithm. The source goes public on 60 Minutes this weekend, testimony to follow. The file’s structural read, ahead of the circus: the devastating thing isn’t the harms, it’s that the company measured them, internally, rigorously, and the measurements lost to the growth metrics in every escalation (the Goodhart file, terminal stage: they instrumented the damage and shipped anyway). This archive has said “documentation is power” since the Fowler post; the Files add the corollary that documentation is power only when it escapes the drive, internal research without an external forcing function is a confession awaiting its leak (the subpoenaed-receipts doctrine; the emails are always forever). ...

The Epic v. Apple ruling landed September 10th, and the pre-registration grades almost exactly: a split verdict satisfying no one, Apple won 9 of 10 counts (not a monopolist under the court’s market definition of “digital mobile gaming transactions”), Epic lost its headline war and owes Apple money for its breach-of-contract stunt, but the anti-steering injunction is real: Apple can no longer prohibit developers from linking out to alternative payment flows. The margins moved; the structure held; both sides appealed within days (the “courts move narrower than movements” clause, now with citation). The structural work continues to migrate exactly where forecast, the EU’s Digital Markets Act draft, Korea’s new app-store payment law (passed this fortnight, the world’s first), and Lina Khan’s FTC. Platform-tax erosion will be legislative and geological, not judicial and dramatic. File remains open; grade remains “called it, narrowly.” ...

The month’s cleanest platform-power case study came from OnlyFans: the creator-subscription site announced it would ban sexually explicit content, the content generating the overwhelming share of its revenue, produced by the creators who built the platform’s entire value, citing pressure from banking and payment partners; then, six days of creator revolt and headline incredulity later, reversed, having “secured assurances” from the financial stack. The file’s structural read (the stack-sovereignty series, payments volume): the moderation layer of record for the internet is increasingly not platforms, not app stores, not even clouds, it’s the card networks and banks, whose risk teams’ preferences propagate down through processors to product policy with no appeals process and no press conference. Visa and Mastercard’s acceptable-use posture is the de facto content constitution of the commercial internet (the hostage-revenue metric: OnlyFans’ was ~100%, concentrated in two logos), and creators, who this decade were promised “direct relationships with your audience,” keep discovering the relationship is intermediated at the layer they can’t see (the graveyard gains a near-miss). Payment diversification is the new multi-cloud; the archive expects a crypto-payments pitch renaissance from this exact wound, and pre-files its skepticism alongside its sympathy. ...

Apple, the privacy-as-product company of the earlier FBI standoff, announced it would scan photos on-device for child-sexual-abuse material before iCloud upload, using perceptual hashes matched against a known-CSAM database, with human review past a threshold. The backlash from the security community was immediate, near-unanimous, and not about the target (nobody defends CSAM): it’s about the architecture, client-side scanning builds the searching machinery into the device, and the machinery cannot know what database it matches against (today CSAM hashes from NCMEC; tomorrow, any government’s “terrorist content” list, with compliance leverage Apple has already demonstrated bending to in China). The FBI-standoff principle returns inverted: Apple argued then that a capability built for good guys can’t be contained; critics now quote Apple’s own brief back at it. The file’s read: the cryptographic design is genuinely clever (threshold secret-sharing, safety vouchers, the engineers did careful work); the policy architecture is the vulnerability, and “we would refuse such demands” is a promise, not a mechanism (the AUP lesson: capabilities outlive intentions; the sword you forge is the sword that exists). Apple is already in visible retreat under the pressure — clarification FAQs, hastily scheduled briefings — and the file expects a formal pause within weeks. The precedent debate, where does content-matching belong: device, transit, or cloud, is now permanently open, and every E2E messaging platform’s future runs through it. ...

The meditation held over from the finals weekend, as promised, because it deserved its own entry: Lionel Messi finally won an international trophy, ending Argentina’s 28-year drought at the Copa América — and doing it at the Maracanã, against Brazil, at the venue and against the opponent that had authored so much of the suffering. Di María scored; Messi collapsed in tears; his teammates picked him up off the turf. The drought: ended by a player who left his home country at 13, who stayed with his national team through years of bitter criticism (the economics of national pressure), and whose post-game press conference (“I had this thorn in me… I knew it would happen eventually”) is the healthiest elite-performance psychology the file has ever quoted. Retention as architecture, endurance as legacy code, the whole Proverbs file in one podium. ...