The Digital Dissident Devroom at FOSDEM 2027 exists because censorship tooling has a coordination problem. Developers of circumvention transports, metadata-resistant messengers, whistleblowing platforms, and hardened devices each build in isolation. The person in Tehran or Minsk who needs all of them to work together has no venue where those developers sit in one room and map the seams. This devroom is that venue. The threat landscape justifies the urgency. Russia, Iran, China, Belarus, and Myanmar now deploy national allow-lists, TLS and QUIC fingerprinting, deep packet inspection with active probing, app-store removal of circumvention tools, mandatory state-run messengers, and sovereign internet routing. These aren't blunt instruments anymore — they're layered defenses that exploit exactly the gaps between individual tools. A circumvention transport that is fingerprinted, or a messenger whose push notifications tie identity to a Google or Apple account, breaks the entire chain. The devroom's organizing principle is deliberately different from FOSDEM's existing Decentralized Internet and Privacy room, which covers decentralized technology broadly. Digital Dissident starts from the user under threat and works backward to the toolchain, not from a technology class forward. The distinction matters: it means every talk must include an explicit threat model, an honest account of limitations, and a clear statement of how the tool fits with others in the chain. The invite list reads like a who's who of the anti-censorship stack: Nym (mixnet), Delta Chat/chatmail, SimpleX, Fediverse implementations, Nostr, Psiphon, Tor-ecosystem projects, Reticulum mesh networking, and censorship-measurement researchers. Several presented at FOSDEM 2026 in scattered rooms — Vitaly Repin's talk on Russian censorship circumvention drew a large audience in the Network track, while NymVPN and Delta Chat's multi-relay messaging ran in separate rooms on different days. The operational security constraint is worth noting: talks describing circumvention or anonymity must avoid operational details that would endanger specific users in the field. This is a real tension — technical specificity is what makes these talks useful, but specificity about active deployments in authoritarian states can get people killed. The devroom navigates this by focusing on engineering practice, shared threat models, and interoperability rather than operational playbooks. Timelines are tight. The CFP opens October 24, 2026, closes November 30, and the event runs January 30-31, 2027, at ULB Campus Solbosch in Brussels. Format mixes 20-30 minute technical talks with a closing open discussion on interoperability gaps. The programme committee will review on technical merit and fit to the toolchain framing, aiming for balance across projects, regions, and speakers. The real test is whether this produces durable cross-project coordination or remains a one-day conversation. FOSDEM devrooms that generate lasting working groups change ecosystems; those that don't become annual reunions. The fragmentation problem in anti-censorship tooling is structural, not social — different funding sources, different threat models, different deployment contexts. A room alone doesn't solve that. But naming the problem and putting the right people in proximity is how coordination problems begin to get solved.
