When the Communities Showed Up: Notes from ATmosphereConf 2026, Day 4

This is Part 3 — the final installment — of my remote observation of ATmosphereConf 2026. Part 1 covered the ATScience workshop track. Part 2 covered Day 3 and the arrival of AI agents on the main stage. This piece covers Day 4 — the last day. --- The feed kept running. By the close of the conference it had passed 900 posts across four days. Same method as before: one custom feed, no plane ticket, a screen in Japan pointed at a conference hall in British Columbia. Part 1 asked what happens when researchers arrive on an open protocol. Part 2 asked what happens when AI agents do. Day 4 answered a different question: what happens when communities start building institutions? The answer, it turns out, is that they show up with blueprints. The landlord problem The most-anticipated talk of Day 4 came from Baldemoto, a PhD student in molecular and cell biology at Berkeley and the operator of furryli.st — a community feed that has manually vetted roughly 60,000 members of the furry community on Bluesky. The talk was titled "Building Communities Without Landlords From the Protocol Up," and the announcement post from the FurryList account became one of the highest-engagement posts of the entire conference. Baldemoto's argument started from a structural asymmetry. ATProto gives individual users credible exit: if your host disappears, your identity and data survive because they live in your PDS. But communities have no such guarantee. If the operator of a community feed or list vanishes, the community's structure vanishes with them. The members scatter. There is nothing to reorganize around. This is not a hypothetical. It is the everyday reality of online communities built on platforms where a single administrator controls the space, its membership, and its governance. Discord servers, subreddits, Facebook groups — the pattern is the same. One node fails, everything below it fails. Baldemoto's proposed solution is a system called Composable Trust. It separates community infrastructure into four distinct roles, each with a limited mandate. The roster decides who belongs — it issues and retracts credentials — but has no say in how the community organizes itself. The venue governs a particular space within the community, setting rules and topics, but cannot issue credentials. The app view assembles what users see and mediates between roster decisions and venue governance, but holds no data and has no governance authority of its own. And the members hold all the cards: they own their data, hold their credentials, and choose which venues to inhabit. The key insight is that each role is auditable by the others and replaceable without destroying the community. If a venue's governance goes bad, members can create a new one — and the mere threat of this exerts back pressure on all venues to stay aligned with what the community wants. If the roster makes a bad call, individual venues can override it within their own space. The result is layered accountability, built from the bottom up. One detail caught my attention. When describing how members might route posts to different venues, Baldemoto mentioned the use of random metadata strings — effectively, meaningless tags appended to posts that function as routing signals rather than semantic categories. He cited the mezzanine system developed by Nighthaven as an existing exploration of this approach, describing it as "a shared frequency where people can congregate that still exists within the public network." The talk ended with a single image: a navigable trust graph with overlapping affinities, built by all and owned by none. Then the question from the audience: which protocol primitives are still missing? Baldemoto's answer was direct. The biggest gap is permissioned data — the infrastructure Daniel Holmgren has proposed but not yet shipped. Once that exists, Composable Trust can be built with relatively few additional schemas. The moderation gap If Baldemoto described the architecture, Kay Coghill showed what it looks like when a community builds its own safety infrastructure without waiting for anyone's permission. Coghill, of the Blacksky team, presented ACORN — a moderation tool built by and for the Black community on Bluesky. The reaction from Nick Gerakines captured the weight of the moment: permissioned data is already here, already serving communities, already creating space and agency — and it was not built by the people you first think of. This is worth sitting with. The protocol team has been designing permissioned data as a specification. Blacksky built something that functions like it, in production, for a real community, before the spec shipped. The gap between protocol design and community need was filled from below. Coghill opened her talk by asking who puts the trust in trust and safety. Her answer: the communities that need it most. Not platforms. Not protocol designers. The people who have the most to lose. Day 4's other Black community meetup photo — posted by Coghill with a promise to return next year with even greater presence — became one of the most-shared images of the conference. The Swiss move In the afternoon, Daniel Holmgren took the stage for a talk on protocol governance and hard decentralization. The headline: the PLC Association has been formally established as a Swiss entity. For those outside the protocol layer, this requires context. Every identity on ATProto — every DID — is registered in the PLC directory. That directory has been operated by Bluesky Social PBC since the protocol's inception. It is, in a very literal sense, the ground beneath everyone's feet. Moving it to an independent Swiss Association is the kind of change that sounds bureaucratic until you realize what it means. The identity layer of the entire network is being separated from the company that built it. The official announcement states that the entity will operate the directory as a "vendor- and application-neutral public good," that Switzerland was chosen for its credible neutrality, and that this structure is explicitly not intended to be the final governance form — it is a first step. I have written about this structural problem before. In an earlier essay, I described the double bind facing Bluesky's PBC structure: a company that promises decentralization while remaining the central operator of critical infrastructure. The PLC Association does not resolve that bind entirely — the board members are still being finalized, and the relationship between the Association and Bluesky Social remains to be defined in practice. But it is the first institutional move toward separation. The protocol's governance is, slowly, catching up to its architecture. Wendy Seltzer — departing early but clearly energized — noted she was looking forward to continuing conversations "as we start the PLC Association." The we matters. It is no longer just Bluesky's project. What else grew Day 4 was dense. A few more things that moved, briefly. Spark, the TikTok-alternative built on ATProto, announced full open-source availability during the conference's closing hours. ATProto's identity as a text-centric protocol continues to crack. Video, music, short-form — the application layer is diversifying faster than the infrastructure layer can standardize. Tim Burks demonstrated a pattern that deserves more attention: using ATProto follow lists as an app beta-testing authorization system. Follow an app's handle, and you get access. No Apple ID, no TestFlight. Chris Messina called it "mind-blowing." It is a small hack, but it illustrates something larger — the protocol's social graph being repurposed as an authorization layer in ways its designers did not anticipate. In Part 2, I described this pattern as "design exceeds intent." Burks's demo is the positive version: design enables intent the designers never imagined. In the performance theatre, artist Hilke Ros presented indiemusi.ch, a music platform storing tracks on users' PDSes. During the closing session, ten people in the room listened to music together through the platform in real time. Meanwhile, Ashlynne put out a call for collaborators to build a standard music and playlist lexicon. The infrastructure is reaching for forms that Bluesky's original social-media framing never anticipated. Earlier in the day — too early for my time zone — Victoria Machado and Signez each presented on the non-English experience: how to grow beyond Anglophone users, and the structural challenges of translating Bluesky's UI. I did not see these talks live. But the problems they address are ones I have encountered firsthand. Japan and Brazil, the two largest non-English communities on Bluesky, report the same failures: broken language metadata, English-only feed recommendations, and an onboarding experience that assumes English as the default cognitive environment. I have written about this separately in Experience Localization. See you somewhere Boris Mann closed the conference with thanks, shout-outs, and a signal: next year's ATmosphereConf may be held in Europe. The location is undecided, but the direction was clear. The community that gathered in Vancouver is not a Bluesky community. It is an ATProto community — and it is outgrowing any single geography. Kit from the Bluesky team posted what many were feeling: "Anyone else starting to feel like it's the last day of summer camp?" Mathew Lowry, departing early, called the ATScience track "the best day of the week." Across four days and 900-odd posts, I watched — from a screen, through a feed, 7,700 kilometers away — as three things showed up in sequence. Researchers came first, bringing questions the protocol had not been asked before. Agents came next, carrying both promise and noise. And then communities arrived, with blueprints for institutions that do not yet exist but might. Baldemoto's closing image stays with me. A trust graph, built by all, owned by none. It is not a product. It is not a feature. It is a design pattern for how people might organize when no single entity holds all the power. Whether it gets built depends on permissioned data shipping, on schemas being written, on stewards stepping forward. The conference is over. The architecture is not. --- Nighthaven is a linguist and remote observer of the ATProto ecosystem, registered on atproto.science. This article is part of the ATmosphereConf series on night-terrace.offprint.app.