I refuse to accept a censored Internet. Join Me at FOSDEM 27
- ID
- 39326
- Status
- summarized
- Published
- 26 Oct 2026, 1:30 AM
- Fetched
- 26 Oct 2026, 4:08 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://talkweb.eu/openweb/4558/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 3.5
- Created
- 26 Oct 2026, 4:09 AM
- Tags
- Audience
- developersai-agents
What happened
Bogomil Shopov, a manager of FOSDEM's "Digital Dissident" devroom, posted a call for speakers ahead of FOSDEM 27 (article dated October 25, 2026), asking for talks that treat censorship circumvention, anonymity, messaging, publishing and whistleblowing tools as one end-to-end chain rather than isolated projects. The pitch argues the weakest link decides the outcome — citing examples like a fingerprinted circumvention transport, or a messenger whose push notifications tie identity to a Google or Apple account — and says sessions will be judged on interoperability, shared threat models, shared failure data and shared engineering practice. Submissions go through FOSDEM's CFP portal with "Digital Dissident" selected as the track, and acceptance implies the FOSDEM Code of Conduct. The HN thread drew 230 points and 106 comments.
Why it matters
This is a CFP deadline item, not a technical release: if you maintain or depend on privacy, circumvention or messaging tooling, the concrete decision is whether to submit a talk or attend the devroom specifically to argue about the hand-offs between tools — the fingerprinted-transport and push-notification-identity examples are the kind of seam that breaks a chain. For most Malaysian builders shipping SaaS or AI agents, nothing here changes what you build this week; it is relevant only if you work on privacy, anonymity or censorship-resistant infrastructure, or want a cross-project threat-model conversation you can't get from single-project docs.
Discussion angle
The devroom's claim is that no one owns the cross-project view — take the push-notification example and ask: which seams in your own stack (auth, push, telemetry, hosting) silently bind user identity to a third party, and would a talk on that seam be more useful than another single-tool demo?