People fight against or/and ignore the #KISS (Keep It Simple Stupid) approach in tech because simplicity exposes power. Complexity, jargon, and process give cover – they make control look like competence. When paths are simple and transparent, everyone can see who’s blocking, who’s hoarding, who’s acting in bad faith. Many “experts” and institutions are emotionally and professionally invested in keeping things complicated; simplicity threatens their authority, their funding, and their identity.
All the #OMN projects are not directly about social change – they’re about making social change possible. That distinction matters as people don’t step into change unless they first believe change can happen. If the world feels fixed, locked, inevitable, then nothing moves. Our role is simpler, and maybe more important, to open that door a crack, to show that different paths exist.
Think of #OMN as a helping hand, not dragging people forward, not telling them what to do – just making it easier for them to take that first step when they’re ready. But to do this, we need to think more clearly – and more fundamentally – about technology itself. As most of the current “open paths” are cosplay at best, we need a network that links them as flows for there use to be unlocked from the current limits of #stupidindividualism shaping them – to become a native part of the expanding #openweb reboot.
I’ve been working on this for over 20 years, and one thing keeps proving true: we need roughly 90% open and 10% closed, the balance matters. As the current push from the #encryptionists flips this – aiming for 90% closed and 10% open. That isn’t a solution, it’s a retreat. It breaks the social fabric that makes collective tools usable and meaningful. It fragments, isolates, and ultimately shrinks the space where shared culture can exist.
Yes, privacy matters, yes, some things should be closed, that’s the 10%. But the commons – the space where we meet, talk, organise, and build trust – has to be open. Without that, there is no network, just silos. Take a simple example: you’re reading this via #activitypub. That’s a system built on being mostly open, with just enough closure to function safely. And it works, people are here, conversations happen, networks grow.
Compare that to more closed, encryption-heavy systems like old school Diaspora. Technically interesting, sure, but socially? Empty, few people, little flow, no impact. That’s the core point: this isn’t just about functions or features, it’s about culture.
Open federated, networked systems create the possibility of shared culture, and from that, the possibility of social change. Closed systems protect individuals, but they rarely build movements. We need both – but we need to get the balance right. Right now, too many people are getting it the wrong way round.
This Isn’t New: Decentralisation Was the Point All Along
Decentralised servers – what we now call the #Fediverse – are often talked about as if they’re some new, radical innovation. They’re not, they’re a return to the original design of the network. The early internet wasn’t built to be controlled, it was built to survive. The core idea was simple: if parts of the network were destroyed – even something as extreme as a nuclear strike – the rest would keep functioning. No centre, single point of failure or “off switch.”
That’s what decentralisation actually means. And this thinking didn’t even start with the #openweb. Systems like Usenet already embodied this approach: distributed, federated, run by many, owned by none. Messy? Yes. But resilient, open, and hard to capture.
What we’ve been living through for the last 20+ years – the rise of the #dotcons – is the opposite of this. Centralised platforms with single points of control. Easy to use for control and monetise, easy to manipulate, easy to shut down. We didn’t lose the #openweb by accident, we blindly traded it away for this convenience.
What we’re seeing now with the #Fediverse, #ActivityPub, and related projects isn’t innovation in the common sense. It’s a reboot, a return to the path we were on before we derailed it. The difference is that now we’re trying to rebuild this in a world that has spent decades normalising centralisation and control. 40 years of death cult worship has changed people, institutions, social groups and our very internal selves. That’s where the friction comes from, people arrive expecting #dotcons platforms, what they find is networks. People expect control, what they get is responsibility. People expect “free” what they face is shared cost and care.
So, it was never about the tech, the mistake we keep making is ONLY thinking this is a technical shift, it’s not, it’s cultural. You can spin up a decentralised server in minutes, that’s not the hard part, the hard part is everything around it:
Who runs it
Who pays for it
How decisions are made
How conflict is handled
How trust is built and maintained
This is the work the #dotcons hide from us, they wrap control as “free services” paid for with surveillance, extraction, and control. Now that we’re back on the #openweb path, that work becomes visible again, and yes – it’s harder.
Why this matters (Again). Resilience isn’t an abstract idea anymore as we’re living through cascading crises: political instability, #climatechaos, infrastructure fragility. A centralised network fails catastrophically were a decentralised network degrades – but keeps going. That’s the difference between a system you depend on and a system you can trust.
We don’t need to overcomplicate this – Keep It Simple (#KISS)
One builds commons, the other extracts value, everything else is detail. And yes nobody thinks the Fediverse is not messy, uneven, (yet) match the polish of corporate platforms. That’s fine, mess is where growth happens – if we compost it properly.
The #OMN view, we’re not trying to invent something new. We’re trying to make what already works usable at scale for media, trust, and collective action. The infrastructure is there, the protocols exist, the history is long. What’s missing is the shared layer – the commons – where information flows in ways people can actually rely on, that’s what we’re building.
If decentralisation feels radical, it’s only because we’ve spent so long inside systems that forgot #OMN#openweb#KISS
Three years ago I was trying to explain something simple in language liberals might actually hear. They talk about “platform capitalism.” Fine. But I’ve been calling it the #dotcons for 20 years – because that’s what it is – a con.
The last 30 years of tech hasn’t just drifted into this mess. It’s been shaped, step by step, enclosure by enclosure, into systems designed to extract value from us. What we now call the internet is, in large part, a machine built to manipulate, capture, and profit.
The old #openweb got fenced in, and most people, especially polite liberal society, went along with it. So we need to talk about the return and the problem. Now we have a shift of the #mainstreaming is flowing back toward the #openweb, that should be a good thing. But there is a problem: people don’t leave the #dotcons behind when they move, they bring the culture with them.
What we’re seeing is a flood of the same patterns – extractive behaviour, ego performance, status games. Not from one “side,” but from everywhere. The habits built inside the #dotcons don’t magically disappear just because the platform changes.
So the real issue isn’t technical, it’s cultural. If we don’t actively mediate this influx, we won’t rebuild the #openweb – we’ll just recreate the same broken systems in slightly different code.
So why do I talk so much about compost, and mess not being the problem. Mess is necessary, but only if it composts – if it breaks down into something fertile. Right now, we’re mostly just piling it higher.
This is where projects like #indymediaback and #OGB matter. They’re not perfect, but they are native to the #openweb path: grounded in trust, process, and the #4opens rather than control, branding, and capture.
The question isn’t whether #mainstreaming is good or bad. The question is: how do we hold the cultural line so that what grows is something genuinely different? Because if we don’t, the #dotcons don’t need to defeat us. We’ll blindly rebuild them ourselves.
Yes, build the #openweb, but the idea that we should stop organizing inside the #dotcons right now? That’s a trap, because billions of people are still there. The conversations, the communities, the movements, they haven’t magically migrated. Walking away doesn’t free those people, it abandons them, leaving the space to be shaped entirely by the #deathcult and the forces already in control.
This is #nothingnew. The #dotcons are #closedweb infrastructure. They serve power because they were built to serve power. Expecting anything else is misunderstanding the system. The real question has never been: are these platforms good? It’s: what do we do, given that this is where people are?
The #geekproblem and the exodus fantasy, is a persistent fantasy – a classic #geekproblem – that if we just build better tools, people will come. They won’t, not on their own. A clean exodus to the #fediverse or any #openweb space doesn’t happen because we post about it. Movement-building has never worked like that, people move through relationships, trust, and shared struggle – not technical superiority.
So if you abandon the spaces where people already are, you cut those pathways. The #OMN approach has always been simple to use the #dotcons as a bridge, not a home, seed organizing where people already are while focusing energy on building the #openweb in parallel to clearly keep your foundations in the #4opens.
This isn’t about purity, it’s about effectiveness, don’t fall into #stupidindividualism, the idea that personal withdrawal is more important than collective reach. This is about infrastructure and grounding, if the #dotcons can switch you off at any moment, they cannot be your foundation.
That’s why we need:
indymediaback as publishing roots
activitypub and the #fediverse as distributed infrastructure
OMN as a bridge between cultures and spaces
This is the practical expression of the #4opens: not just open code, but open process and open trust. Don’t build your house on someone else’s land, but don’t stop talking to the people still living there either. Stay in the fight, when the #dotcons clamp down, it’s not a surprise, it’s a signal of what they are, and what they’ve always been.
The answer isn’t to run away, it’s to root ourselves somewhere that can’t be shut down, while continuing to show up where the people are.
Build the #openweb, stay in the fight, keep it simple #KISS
When thinking about supporting the #Fediverse, it’s important to understand that the current codebase leadership model is closer to an aristocracy than democracy. This isn’t unusual – most open source projects work this way. A small group of core developers, often a “benevolent dictator,” make key decisions. This model can work up to a point: it enables speed, coherence, and technical direction. But it does not scale in any way easily into a broader public infrastructure.
From the outside, the #Fediverse can look chaotic, and in many ways it is. A useful metaphor is an elephant stampede with people throwing paper planes at each other. That messiness is not a failure; it’s a reflection of a genuinely distributed system.
Democracy is inherently messy. Bureaucracy, by contrast, is tidy.
The tension between those two is at the heart of the challenge outreaching to public institutions faces. Traditional organisational models – especially those involving funding – tend to concentrate power. Once money and status enter the system, decision-making quickly becomes a focus of competition and control.
We have seen this repeatedly over the last 20 years: projects that begin open and collaborative gradually centralise, and in doing so lose the qualities that made them valuable in the first place. If the goal is to support a native Fediverse ecosystem, this pattern needs to be consciously avoided.
This raises a governance question. How are decisions made once resources, funding, and institutional recognition enter the space? Without deliberate design, the default outcome is oligarchy – small groups making decisions on behalf of many. This is not only a moral failure; it is a structural tendency of complex organisations.
The strength of the #Fediverse is that it is radically different from mainstream platforms. It is decentralised, diverse, and resistant to single points of control. The risk is that, in mainstreaming paths trying to support it, we unintentionally reshape it into something more familiar, and less effective. “Common sense” approaches, based on traditional institutional models, push in this direction. If European institutions want to invest meaningfully in this space, the challenge is not simply technical. It is cultural and organisational:
How to support infrastructure without centralising control
How to enable coordination without enforcing uniformity
How to fund development without creating capture points for power
The opportunity is significant, but it requires seeing and recognising that the #Fediverse works because it is different – and ensuring that support mechanisms strengthen that difference, rather than smoothing it away.
The internet’s public square is privatised, algorithmically controlled for “engagement” over any idea of truth, and placed under the control of a handful of American corporations with no accountability to European citizens or values. The #Fediverse is the most credible existing alternative – but it lacks the shared infrastructure to function as a native commons for news and media. #OMN builds that infrastructure: trust-based, community-controlled, transparent, reversible, and owned by nobody. At €45,000 for a proof of concept, it is one of the cheapest possible investments in the long-term health of European digital public life. If it works – and the technical and social groundwork suggests it will – it becomes the plumbing for a Fediverse that can actually be used to serve democratic societies rather than more #techshit alongside the current #dotcons platforms that undermine them.
Why this matters – because the #WWW was stolen – Designed as commons at CERN, decentralised, open, nobody in charge. What we have today is instead is five American corporations controlling the information diet of billions of people. Facebook decides what news you see. YouTube’s algorithm decides which voices get amplified. Twitter/X decides who gets banned. None of these decisions are transparent, accountable, or reversible. They are made by private entities in pursuit of control, advertising revenue and engagement metrics – not truth, not public interest, not democracy.
The #Fediverse exists as a rejection of this, it’s the largest real functioning alternative to corporate social media, with millions of people on thousands of servers, federated together, nobody owning the whole thing. It works. It’s growing. But it has a weakness: it’s kinda fragmented at the commons layer. There’s no shared infrastructure for how news and media actually flows across the network in any trustworthy and coherent way.
That’s the gap #OMN fills, but why? Most people don’t think about internet infrastructure. They think about whether they can trust what they read. Whether the news they see is real. Whether the platform they’re on is working for them or selling them. Whether they can do anything when something goes wrong.
Right now the answer to all of those is: it depends entirely on decisions made by people you’ll never meet, for reasons you’ll never know. OMN proposes something different. If your community trusts a source, a trust flow, you see it. If they don’t, you don’t. And that decision is yours, reversible, transparent, locally controlled.
For a journalist in a small country trying to get independent news out, this is the difference between having infrastructure that works for them and being at the mercy of a platform that can deplatform them overnight. For a community archive trying to keep historical memory alive and accessible, this is the difference between dependence on Google’s goodwill and owning your own distribution. For an ordinary person trying to figure out what’s true, this is the difference between an algorithm designed to maximise your outrage and a network shaped by people you actually trust.
Bureaucracies fund things slowly, in ways that often serve existing power structures rather than challenging them. But digital sovereignty is an existential European concern. The EU has spent years trying to regulate American platforms – GDPR, the Digital Services Act, the Digital Markets Act – and the platforms have responded with compliance theatre, token gestures, and armies of lawyers. Regulation of concentrated private power is a losing path. The only actual answer is to build the alternative infrastructure so that people have somewhere else to go. That’s what the NGI Commons Fund is for and what #OMN does.
The EU should not only be funding products, it needs to fund commons infrastructure – the plumbing that nobody owns and everyone can use. Like funding roads rather than funding a logistics company. The outputs are open source, meaning any European media organisation, any local community, any public institution can pick this up and use it. No lock-in. No dependency on a vendor who will be acquired or shut down.
It’s cheap, with the second stage scaling across Europe with institutional partners, building on European strengths. The Fediverse is disproportionately European. Mastodon was built by a German developer. The culture of digital commons, open standards, and public interest technology is stronger in Europe than anywhere else. This project is native to that tradition. It’s not asking Europe to compete with Silicon Valley on Silicon Valley’s terms – it’s asking Europe to build the alternative on its own terms.
The problem #OMN solves is getting worse, not better. Disinformation, algorithmic radicalisation, platform capture of public discourse – these are not abstract threats. They are actively destabilising European democracies. Funding the technical infrastructure for trustworthy, community-controlled information flows is not a nice-to-have. It is digital public health infrastructure.
Organisation: Open Media Network (unincorporated community project, fiscal hosting in Belgium via OpenCollective) Country: United Kingdom General Project Information Proposal name: Trust-Based Media Flows for the Fediverse (#OMN) Website / wiki: https://unite.openworlds.info/Open-Media-Network/Open-Media-Network
Abstract
Can you explain the whole project and its expected outcome(s)?
The Open Media Network (#OMN) is a protocol-driven, federated media infrastructure built on top of ActivityPub and the Emissary codebase (emissary.dev). It addresses a real gap in the current Fediverse: while platforms like Mastodon, PeerTube, and Lemmy are federated at the instance level, there is little coherent cross-platform layer for trust-based content flows, moderation, or news aggregation. Each instance operates largely as its own silo, moderation is hierarchical and per-server, and there is no shared commons model for media distribution across the ecosystem. #OMN proposes a minimal, compostable interaction model – the Five Functions (#5F): Publish, Subscribe, Moderate, Rollback, and Edit Metadata – implemented as a flow layer on top of existing Fediverse infrastructure. Content moves through the network as objects flowing through pipes and holding tanks, filtered and shaped by trust relationships between nodes rather than by opaque algorithms or centralised authority.
The central R&D question is: can trust-based moderation and distribution flows replace algorithmic amplification in a federated news ecosystem? Expected outcomes of this first-stage grant: By Month 3: A technical specification of the flow architecture; a prototype flow service routing ActivityPub objects between two instances; documentation of existing Fediverse flow patterns; early integration with one platform (likely PeerTube). By Month 6: A cross-platform prototype connecting at least two Fediverse systems; a working demonstration of trust-based moderation flows; a public code repository and documentation; and a user-facing prototype via the #makinghistory test environment (https://unite.openworlds.info/Open-Media-Network/MakingHistory). All outputs will be released under recognised open source licences. The project follows the #4opens framework: open data, open source, open standards, and open process.
Have you been involved with projects or organisations relevant to this project before?
Yes. The project lead, Hamish Campbell, has over 40 years of experience in grassroots media and technology, including early involvement with Indymedia – the pioneering open publishing news network – and more than 8 years working directly with the Fediverse and ActivityPub community. The #OMN conceptual framework has been developed over this time and is documented extensively in the project wiki, SocialHub, and at https://hamishcampbell.com. Developer Michael has contributed to #OMN concepts and logic for 10 years and is currently building the #makinghistory reference implementation. Ben, the core developer of Emissary, brings specific expertise in the codebase that will form the technical foundation of the project. Alex brings potential DAT/distributed storage support, and IKA will work on testing and rollout.
Requested Support Requested Amount: €45,000
Explain what the requested budget will be used for. Does the project have other funding sources, both past and present? A breakdown in the main tasks with associated effort is appreciated. Make rates explicit. The budget covers a lean, seed-stage proof of concept with no prior external funding. There are currently no other funding sources. The budget breakdown can be found in the attached PDF (funding). Roles: Hamish Campbell (project lead, coordination, documentation, community engagement) and Michael Saunders (primary development, UX, system logic). Additional contributors (Ben, Alex, IKA) are contributing on a voluntary/community basis during this seed phase. Work packages and approximate effort: WP1 Research & Specification (Months 1–2, ~25% of effort): Architecture design, gap analysis of existing Fediverse tools and flows (PeerTube, Lemmy, Mastodon), and documentation of trust-flow patterns. Output: Technical design document. WP2 Core Development (Months 2–5, ~45% of effort): Flow service implementation on top of Emissary; ActivityPub integration for the #5F model; and a trust-based moderation layer extending Emissary’s existing block/flag capabilities. Output: Working prototype codebase. WP3 UX & Prototype (Months 3–5, ~20% of effort): #makinghistory user interface; dual-layer UX (simple and advanced modes); and WCAG 2.1 accessibility compliance. Output: Testable user prototype. WP4 Testing & Documentation (Months 5–6, ~10% of effort): Community testing and iteration; public documentation and reports; and an open knowledge base of what works and what fails. Output: Public documentation, reports, and reusable design patterns. LINK PDF and wiki
Compare your own project with existing or historical efforts.
The closest existing efforts are: Mastodon’s built-in moderation tools: per-instance block lists and the Fediblock community blocklist. These are instance-level tools – they do not create cross-platform trust flows or shared content aggregation. #OMN operates at the network layer, not the instance layer. Fediseer: a trust registry allowing instances to vouch for each other. Fediseer addresses instance-level reputation but does not implement content flow logic, rollback, or metadata editing as network functions. #OMN builds a compostable flow model on top of the kind of trust signals that Fediseer represents. GNU Social / Friendica: older federated social platforms with some aggregation capability. These predate ActivityPub’s consolidation as the dominant standard and do not address the cross-platform news/media commons use case. Indymedia (1999–2010s): the historical precedent for open publishing federated media. Within the wider project, #OMN explicitly revives and modernises the Indymedia model for the ActivityPub era via the #indymediaback reference implementation, addressing the unfinished work of that tradition. The #makinghistory project grows from, and shares, this same established workflow. Bonfire networks: likely related, but unclear in scope and function. Attempts to install and use it have not clarified its approach. It may be trying to address similar problems, but this remains uncertain. The key difference of #OMN: it is not building a new platform. It is building a protocol-level flow layer that works across existing Fediverse platforms, implementing trust-based content propagation as commons infrastructure rather than as a product. See included PDFs.
What are significant technical challenges you expect to solve during the project?
Trust flow implementation: Designing and implementing a data model for trust relationships between federated nodes that is lightweight, compostable, and expressible via or alongside ActivityPub. Trust is local and subjective – the system must allow different communities to apply different trust filters to the same content flow without requiring global consensus.
Rollback across federated state: Implementing the rollback function (re-evaluating and reshaping historical content visibility) in a distributed system where content has already propagated to multiple nodes. This requires a time-aware, local re-indexing approach rather than a global delete mechanism.
Cross-platform content normalisation: Aggregating content objects from Mastodon (short-form social), PeerTube (video), and Lemmy (forum) into a common JSON-LD content model with a consistent trust trail, despite these platforms having different ActivityPub implementations and object schemas.
Search actors as push feeds: Implementing the “content finds you” model – where a defined search query becomes a persistent ActivityPub actor that pushes matching new content to subscribers – requires extending Emissary’s existing subscribable search engine capability.
Describe the ecosystem of the project, and how you will engage with relevant actors and promote the outcomes.
The primary ecosystem is the Fediverse: the network of federated, open-source social platforms running ActivityPub, including Mastodon, PeerTube, Lemmy, Friendica, and many others. This ecosystem has grown substantially (estimated 10+ million active users across thousands of instances) but remains technically fragmented at the commons/media layer. The project builds directly on the Emissary codebase (https://emissary.dev), an existing ActivityPub-native Go application. Engagement with the Emissary community is embedded in the team through Ben’s mentoring role.
Wider ecosystem engagement:
The project will contribute design patterns and documentation back to the broader Fediverse developer community via public code repositories, the project wiki, and events. The #makinghistory test phase connects us to existing archives such as Bishupsgate, Maydyroom, the Peace Museum, and the Campbell Family Archive, providing access to extensive datasets as well as outreach to their administrators and users. The five community events included in the budget are specifically designed to recruit contributors, gather real-world feedback, and expand the network of participating nodes.
Promotion of outcomes:
Outcomes will be shared through the Fediverse itself (maintaining an active presence on ActivityPub-native platforms and legacy social media), via open-licensed documentation, and through NGI/NLnet networks and events. This first-stage grant is explicitly designed as a seed and proof-of-concept phase, with a larger second-stage proposal planned to deliver a fully production-ready system once the core architecture is validated.
Hope this helps compost some of the mess building up. It’s something we all need to do and have responsibility for.
Groups don’t usually fail because of external pressure, they fail because they turn inward and burn energy on themselves. If you want a calm, #KISS path that actually holds diversity without collapsing, we need a few simple lived – traditions and mythos – not heavy governance, not ideology battles, just grounded #KISS practice:
Keep the core action very small and clear – a shared purpose. If people can’t easily answer “what are we doing?”, drift and conflict creep in.
In twine “doing” with “talking” Most infighting comes from too much abstract discussion. Doing space – Talking space – Don’t let one swamp the other.
Protect focus like it’s fragile (because it is), the biggest risk isn’t disagreement – it’s distraction. When things start spiralling bring it back to “what are we building this week?” if it doesn’t help, park it
Default to trust, but design for friction, diversity is strength. But unbalanced diversity = chaos. So let people approach things differently, but require shared outputs – If it doesn’t produce something, it doesn’t dominate attention.
No purity tests, this is where diversity dies. People will come with different politics, paths (fluffy vs spiky) and have different priorities, that’s fine – as long as they don’t block others doing the work.
Make conflict low-energy, not zero-conflict – we won’t avoid disagreements. Trying repression = explosion later. Instead, keep arguments short, move unresolved tension into parallel paths (“try both”) and let results decide, not personalities. This is the “compost” approach we need to talk about – don’t fight the mess, process it.
Grow by doing, not convincing, you don’t need everyone to agree. You need visible, working examples. Let people see it working – that’s what grows a community of action.
What we are sketching and building is the hard middle path of not rigid control (kills growth) and not total openness (creates chaos). But a light structure that keeps things moving.
#Oxford example: Oxford boaters are sovereign, keeping the free-flowing life of the river, not bound by the old rules of the landlords.
#Fediverse example: The Fediverse is native to the #openweb path. We judge by the #4opens, and walk with power.
If we want a better web, we have to stop pretending this is just about “bad tech companies doing bad things.” Of course, they are-that’s what capitalist incentives produce. The real question is: what are we doing differently?
That means accepting some uncomfortable truths. The better path will be less convenient, at least at first. We will have to socially support things that used to look free on the #dotcons. Because the cost we didn’t want to face is simple: the #openweb was always going to be harder, someone has to:
The fantasy wasn’t that this work didn’t exist. The fantasy was that the market – advertising – would cover it without consequences.
In the current mess in tech paths, this becomes visible again. Bluesky and #ATproto keep getting lumped in with #ActivityPub under the easy label of “open protocols, yay”… but that’s just not true. Yes, they both sit in the #openweb space, but there’s a real structural problem here, and we’re seeing it play out in real time.
“Why would anyone fund an Atmosphere project if Bluesky, with $100 million in the bank, might ship a competing feature at any moment?”
That’s not an ecosystem. That’s a platform with enough gravity to crush its own edges. And people are noticing. The old pattern is back:
invite the community in
let them build the value
then absorb and replace them
Same playbook, again and again. It feels open – but the centre still holds the power. The same dynamic we saw with Twitter. The DNA is obvious.
The difference really matters. #ActivityPub was built as a commons path from the start – messy, flawed, but natively open. #ATproto is something else: a platform-first model with openness layered on top. That’s why it keeps drifting this way. It’s not a bug, it’s the design.
Too much #techshit, and everything starts to stink. Why would anyone step into the #openweb if that’s the smell? This creates a bigger problem, that it’s a mess that keeps coming back, and as usual we’ll be the ones left to compost it, underfunded, unrecorded, and unthanked.
We’ve been here before – with the #encryptionists and the #blockchain mess. Big promises, lots of noise, overlapping hype cycles. Now there’s a clear overlap with #Bluesky and #AI. The risk isn’t just that this fails. It’s that when it fails, it leaves a miasma behind, making it harder for people to trust the actually working open paths. That’s the real damage.
Neglect is not innocence, this isn’t about blaming users instead of power. Power matters. Monopolies matter. Venture capital mess matters. But still, if the #openweb mattered, why didn’t we support it?
Why do people pay for streaming, cloud, and delivery, but not support publishing tools, independent media, hosting, or open infrastructure?
Why did so many #NGO organisations that talked about openness still push people onto closed platforms the moment growth and analytics are on the table? We keep choosing short-term convenience over long-term stewardship, not just a market failure, a cultural one.
So lets look at this mess again. I’ve been trying to find a way to express my view of the people who took over outreach in the #Fediverse, and in doing so helped shape the current #openweb reboot.
DRAFT: naïve, controlling, and self-interested.
They’ve left a mess that the people they pushed aside now have to compost. It’s really useful to look at how we got here.
In the early years, outreach was organised by a genuinely diverse, native crew. It was a good time – three open conferences, and even getting the EU to adopt the standard. But that group burned out, focus splintered, self-interest crept in, driven by the need to control resources. The balance shifted, and grifters gradually outnumbered them, eventually tearing it apart. In the space left behind, a new crew stepped in – filling the vacuum with centralised power and influence. And that’s where we are today.
We don’t fix this by arguing harder. We fix it by building – and holding – open spaces that don’t follow this pattern.
It should be obvious that we need a path back to good journalism – journalism that sheds light on facts, connects the dots, and lets people trace those dots back to sources. This is what allows us to share, question, and discuss within our own trusted communities, and then spread that knowledge outward through federation, always linking back to the source.
Right now, the #mainstreaming path is broken. It’s sometimes hard for people to see this because the decline has been slow, a gradual death of journalism. Since the early days of the internet, we’ve been told the same story: “People expect news for free, so quality journalism is no longer economically viable.” There’s truth in that. Good journalism is expensive. It takes time, skill, trust, and institutional memory.
But that’s only half the story. What actually happened is this: people kept consuming familiar “news brands,” and those brands were bought, consolidated, and financialised until shareholder value replaced any sense of public value. Slowly, investigative journalists were cut and sidelined, editorial independence eroded, and content shifted toward ads, PR, and narrative management. What we now call “news” is marketing, agenda-setting, and reputation management – a distraction. Journalism, as a public good, has been hollowed out, in part through our own passive acceptance of this shift.
Today, we can see more clearly that if you do real journalism – the kind that challenges power – you have no real career path and face risks: #dotcons blocking, right-wing co-option, and at worst, isolation, exile, prison, or worse. The result is a broken landscape: corporate media that won’t tell the truth, and under-resourced independent media that carries high risk for little or no reward. In that situation, who chooses journalism as a life path?
The deeper problem is articulation and power. The world is complex, most people don’t have the time, energy, or tools to fully articulate what they see, feel, and experience. Into that gap step politicians, corporations, and #fashernista influencers. They have the resources – especially through the #dotcons – to articulate reality, but in ways that divide people, flatten complexity into conflict, and steer perception to serve power and profit. This isn’t just misinformation. It’s structured narrative control.
Why the old models won’t come back, we can’t simply “fix” legacy media. It is structurally tied to advertising, concentrated ownership, and political influence. And we can’t rely on heroic individuals either, that path is too fragile, too dangerous, and too easy to suppress. If journalism is going to survive, it won’t look like the past.
A different path: journalism as networked commons. At #OMN, we’re outlining a different approach decentralised, collective path. Think of it as a second coming of #Indymedia, but more resilient, more sustainable, and better integrated with current networks.
This is where the #openweb and the #Fediverse matter. With protocols like ActivityPub, we already have the foundations for distributed publishing, shared visibility, and cross-community discussion. But tech alone isn’t enough, the missing layer is trust and flow. To rebuild journalism, we need to focus on how information flows socially, not just how it’s published.
Metadata (tags, context, sources, warnings) travels with stories
People can trace information back through the flow
Instead of one “authoritative source,” we get many sources, with visible relationships between them, shaped through community trust and discussion. This is journalism people can actually use to follow a story back to its sources, add context and local knowledge and share and challenge it within trusted spaces.
That’s how we rebuild public understanding – not just publish articles – but from product to process. Journalism should not be a product to consume, it needs to be a process we participate in. When it’s treated as a product it’s optimised for clicks, shaped by incentives and in the end controlled by owners. When it becomes a process it becomes collective, accountable and thus resilient.
So composting the mess, we’re not starting from nothing, we have the ruins of legacy media, the lessons of projects like #Indymedia and the living infrastructure of the #Fediverse. This is compost, from it, we can grow something new – grounded in the #4opens, simple enough to understand (#KISS), and social at its core, not just technical.
The real question isn’t “How do we save journalism?” It’s: How do we rebuild the social systems that make truth-telling possible? Because without those paths, journalism doesn’t just struggle – it disappears.
YOU can’t do social change or challenge without annoying people If you think you can, you’re probably play-acting – and part of the problem – does that annoy you? If it does… maybe sit with that. 🙂 Food for thought, #4opens is a shovel for composting.
The value of the #Fediverse comes from its cultural roots in the #openweb. The tech – like ActivityPub – grew out of that culture. It wasn’t built by #mainstreaming interests.
Now money is flowing in, and with it comes risk of dilution of culture, capture of direction and loss of the commons. As more #mainstreaming users return to the #openweb, we need better tools and processes to handle the mess this brings.
And yes – sometimes the problem is us – when people inside our own spaces act badly, we need ways to respond, mediate, and move forward – without falling into cycles of negativity. That’s part of the work, part of #OMN.
The #Fediverse is native to #openweb thinking, it works. It will likely destroy billions of dollars of #CONTROL, and create billions in actual human value in return. But like the early #openweb, it can also be captured and pulled back into the same old control systems, this is the balance.
So the question is, are you on the side of CONTROL or TRUST?
Our obsession with control is doing real damage, it’s fed by dead-end ideology (#postmodernism), and amplified by #fashernistas pushing surface over substance. Yes – it’s messy. Yes – it’s complex, but ignoring that just makes it worse.
#stupidindividualism and the #deathcult are building an inhuman world, we can do better – but only if we’re willing to do the uncomfortable work.
In #mainstreaming and alt political cultures there’s a constant call in messy times for “strong leaders” to cut through the chaos, but this is the wrong path. What Jeremy Corbyn and Bernie Sanders actually show is something more uncomfortable and more useful that real change doesn’t come from strong individuals – it comes from movements we don’t fully control. They were signals, not saviours.
Both figures emerged on the left because something deeper was already shifting with widespread discontent, a break from #mainstreaming politics and a hunger for alternatives to 40 years of #deathcult worshipping. They didn’t create these conditions – they channelled them. “Weakness” is often misnamed, Corbyn in particular was constantly framed as weak, but what was actually happening? When people treat them as failed “leaders,” they miss the point, at best they were interfaces to movements, rather than top-down commanders. They:
Hold together fragile, diverse coalition
Refusal to impose top-down control
Emphasis on process, participation, and consensus
In a stable system, this might look slow, in a fragile system, it’s often the only thing preventing collapse. In the open vs closed battle, it’s not as simple as it looks – especially in the mess we’re in.
CLOSED → conservative / fear / control OPEN → progressive / hope / trust
We need to keep looking at the underlying path when deciding which way to push the balance.
Where the demand for “strength” usually means more control, less democracy. That path tends to deepen the mess, not fix it, as personality politics is a dead end. When media and institutions focus on personalities where movements are about issues and structures. This mismatch is fatal if your politics depends on a person you are attacked through that person – we all collapse when they falter. You never build lasting power, it is the trap both campaigns fell into, despite trying to avoid it.
Movements without structure (hard or soft) stall, is the harder truth – Horizontal energy alone isn’t enough – Electoral politics alone isn’t enough. Both Corbyn and Sanders mobilised huge grassroots energy, but institutions resisted, internal fragmentation grew – the energy wasn’t fully translated into durable paths, and they fell through the gap.
From a #OMN perspective, the takeaway is clear – Don’t look for better leaders – Don’t rely on existing institutions – Build commons-based infrastructure that movements can stand on. This means: Media we control (#indymedia paths), Governance we participate in (#OGB) and tech that reflects trust, not control (#openweb, #Fediverse)
So in messy times, don’t reach for “Strong Leaders” as this comes from fear, frustration and the desire for simple solutions, history – from left and right – shows where that road leads. In poisoned times, the work is slower, to build trust, to stay grounded in shared issues.
Corbyn and Sanders didn’t fail because they were too weak, they struggled because we don’t yet have the social, technical, and institutional commons needed to carry the kind of change they pointed toward. That’s the work, and it’s not about finding the right leader – it’s about becoming the movement that doesn’t need one.
At #NOAW event I talked a lot about the digital commons so thought it might be useful to write a post grounding this. The digital commons are not a future vision, it’s something we already have. At its simplest, the digital commons are the widely used #4opens digital resources of software, knowledge, data, and culture created collectively, governed by communities, and made available for public (re)use. This is the native path of the #openweb it’s been around for a long time, it might be hard to see but just about all of our current #dotcons mess is built on top of this layer.
There is a long history of commons in wider society. But mostly today we focus on the licences that protect reuse and sharing. None of this is abstract theory, it’s making the practical, working infrastructure that underpins much of what people still find useful online. One of the roots of the current digital commons go back to the 1980s and the emergence of the free software movement, led by Richard Stallman and the Free Software Foundation. This was not just about code, it was a social and political project:
Software should be shared
Users should have control
Improvements should remain in the commons
The creation of the GNU General Public Licence was the first step, enforcing a simple rule that if you benefit from the commons, you give back to the commons. The commons isn’t one thing, it’s an ecosystem – Some #KISS examples include:
Wikis – collectively written and maintained knowledge (#Wikipedia)
Open source software – built in public, shared freely (#FOSS)
Public code repositories like GitHub used to be (name one)
Open licensing systems like Creative Commons
Federated social tools built on ActivityPub (#Mastodon)
The Path is governance by the people who use it. What makes the digital commons different from “just free stuff” is this the people building it can shape how it works, a key distinction it’s not just access – it’s agency. The commons are non-exclusive (available to others), oriented toward use and reuse and governed by its participants, this is why it matters politically.
Today, much of the internet still runs on the digital commons, but the visible layer is dominated by #dotcons platforms. This creates a split of Commons layers → open, slow, sustainable and Platform layers → closed, extractive, growth-driven. People still rely on the commons, but interact through closed systems, this contradiction is unstable.
Policy is our current-missed opportunity, as our institutions see only the surface value. The European Union’s European Commission has pushed open source strategies as part of digital sovereignty, particularly through programmes like Horizon Europe. The idea is native – Share code – Collaborate openly – Build public infrastructure. But in practice, most of this gets lost in #NGO process, bureaucracy, and capture. The money flows, but the commons don’t grow.
The “Tragedy” of the Digital Commons. Like any commons, in the mess we live in today commons can be degraded from overuse (infrastructure strain), pollution (spam, low-quality content, noise) and information overload. The result is a corrupted signal-to-noise ratio, it is a real issue – but it’s to often used as an excuse to centralise control. This is largely solved by horizontal vs virtical scaling, if people can take this real native path.
There are social gaps. The commons reflects the culture that builds it, yes gender imbalance persists, access is uneven, and geek culture is too often exclusionary (#geekproblem). But the bigger problem we face is capture and drift. We’ve already seen it happen once: Free software → “open source” (politics stripped out). Commons → #dotcons platform capture.
Now we see this happening in the #Fediverse and #openweb reboot spaces with the last few years of vertical agendas dominating to meany outreach spaces, #NGO mediation and thus diluten is pushing native grassroots agency out, this is an old cycle repeating – the cycle that we need to compost.
OK, despite all the #mainstreaming mess, the digital commons are still the most viable path we have, we need to see this path not as hypothetical – more as it just works, but is underresourced. From a #OMN perspective, the digital commons are not only infrastructure, it’s the soil. You don’t build movements on platforms, you grow them in commons, but this growth needs care:
Protection from capture
Active governance
Social grounding, not just technical process
And most importantly the commons only survives if people act as commoners. The challenge now isn’t only to explain the digital commons, it’s to defend, rebuild, and extend it. That means funding native projects, keeping governance in the hands of participants to bridge activism, development, and real-world use as a path to push back against the continuing #mainstreaming capture.
This is not about nostalgia, it’s about #KISS recognising that we already have the tools we need, then caring enough not to only exploit them. Please try and be better than the current #mainstreaming on this, thanks.
Today there are a lot of dishonest people – it’s become the default. Finding someone who is actually truthful is rare. So with this in mind, let’s stop being polite about this, what we’re living inside online right now isn’t “social media.” It’s a managed enclosure – a system designed to extract value, shape behaviour, and concentrate power. It’s what I have been saying for the last 20 years. Call it what it is – digital #feudalism – The Lords, the Serfs, and the Server.
When everyone is pushed onto one big virtual server, you don’t get community, you get hierarchy. Platform owners become landlords. Users become tenants. Visibility becomes rent. This is not accidental, it’s the business model and once you see it, you can’t unsee it.
The lie of “Ease of Use”. People say these #closedweb systems are “easy.” They’re not, they hide the cost, what looks simple is just complexity moved out of sight. Advertising Is the rot, a business model moral hazard, when profit depends on attention truth becomes optional and outrage becomes profitable leading to manipulation as the new normal. You don’t get healthy communities from this, you get addiction loops and behavioural engineering. And yes, the inevitable result is screen clutter, noise, and a slow degradation of any meaningful communication, communities are managed, not grown.
So who is going to do the #DIY work? Real moderation works when it’s embedded in the community itself. Algorithmic control is anti-social, the algorithmic timeline is one of the worst ideas we’ve normalised. It drives distraction, by showing you more of what you’ve already seen, it tries to control your desires by interfering with human communication. Over time, this destroys trust, when people stop knowing if they’re being heard, they stop knowing what is real, stop trusting the space. That’s not a bug, it’s the outcome.
The celebrity illusion is how centralised platforms manufacture “importance” for brands and influencers. These only function inside controlled visibility systems, outside of that? They’re often just paper tigers. In a real network – a messy, distributed, human one – influence has to be earned, not bought or algorithmically inflated.
The commodification of human life leads to inevitable decay. Left alone, centralised platforms drift towards monopoly, manipulation and towards the amplification of the worst actors as these actors game the system best. Without constant control from above, the system degrades, with repression, it becomes what we see today, authoritarian. That’s the trap, a community you can buy your way into is not a community, it’s a marketplace.
So what’s the alternative? We don’t fix this by tweaking features. We fix it by changing the ground or tech grows from. This new growth has been seeded by the #Fediverse, It’s where the #OMN comes in, not as another platform, but as a shift back to distributed networks instead of central servers, commons-based paths instead of enclosure, social moderation instead of outsourced control, open protocols instead of locked interfaces. And yes, that means less “slick”, less uniform, more messy. But also more real, accountable and human.
A final point (That should be obvious). The problem is not that the current #dotcons systems are broken, the problem is that they are working exactly as designed. If we want something better, we don’t patch the system, we compost it to grow the #openweb back – this time with the native cultural roots intact.
Hamish Campbell is a long-time #openweb activist and technologist working on grassroots media and digital commons. He was involved in the early development of #Indymedia and continues this work through projects like the Open Media Network (#OMN), which works on how federated tools and community publishing supports public-interest media infrastructure. His focus is balancing building native platforms and on growing the social culture that makes the #openweb work: transparency, decentralisation, and horizontal collaboration. Through writing, workshops, and practical projects, he argues that the future of the Fediverse depends as much on culture, governance, and shared infrastructure as it does on code.
Purpose is to open conversation that many people feel but rarely articulate: the tension between grassroots culture and institutional capture. Start with your simple distinction:
Bad #mainstreaming → corporate/NGO structures reshaping the Fediverse
Then ask: “Which direction are we currently moving?”
Discussion topics – funding and governance, foundations and institutional capture, developer vs user power, infrastructure vs platforms. How to avoid repeating Web 2.0
Activity is to ask participants to map layers: Grassroots – NGO / institutional – Corporate. To discuss where power currently sits and what healthy balance might look like.
Outcome is people leave with language to understand the tensions they are experiencing in the Fediverse.
Workshop 02
Maybe a second one on why #makeinghistory is needed? Translating #OMN from “activist infrastructure” into “missing public digital infrastructure.” That language is what this event is trying to figure out. The Open Media Network (#OMN) proposes a model where grassroots publishing, community moderation, and institutional participation are balanced. Participants can discuss how institutions support shared infrastructure rather than just deploying isolated platforms.
Many institutions are experimenting with the Fediverse as an alternative to #dotcons corporate social media. However, simply running institutional servers risks reproducing the same platform dynamics in a federated form. We need workshops that explore the broader ecosystem of public-interest media infrastructure.
“What happens after institutions join the Fediverse?” The #KISS answer is they need to support the commons infrastructure that makes it socially viable. Running Mastodon is not enough, institutions need to support the wider open media ecosystem.
Talking about #openweb culture in a constructive way is tricky because most #FOSS and Fediverse conversations default to technical framing: code quality, scalability, moderation tooling, and #UX. These things matter, but they are not the foundation that determines whether a network lives or dies.
Maybe a useful way to open the conversation is to shift the starting point. Instead of saying “culture is important too”, say something stronger but practical: The success or failure of open systems is primarily a cultural question, not a technical one. The code only expresses the culture behind it.
Start with a simple historical observation. Many technically strong systems failed because the social layer was weak, while some technically rough systems succeeded because the community culture worked.
Examples from the open web – early open source projects that thrived because communities shared norms of collaboration. Grassroots networks like Indymedia worked socially even when the software was messy. Corporate platforms that succeeded not because they were technically better, but because they built powerful social gravity.
The pattern is clear, that technology enables networks, but culture sustains them. This is the missing step in most Fediverse conversations. Right now to meany discussions focus on: scaling servers, moderation tools, interface design and onboarding. These are all necessary but insufficient.
What way to often goes missing is the deeper questions – What culture are we actually trying to grow? Without answering that, the system tends to drift toward the dominant internet culture, which today is shaped by the #dotcon platform model of engagement optimisation, algorithmic attention markets, influencer dynamics and centralised power. When that culture seeps into the Fediverse, the result is a federated copy of the same problems.
So why is culture harder than code? Code can be written by a few developers, culture requires shared understanding across thousands of people. To grow this we need native governance norms, trust networks, moderation values and expectations about ownership and participation to hold to native paths for how conflict is handled. These things cannot simply be implemented in software, they must be grown socially, fail to address this is why many technically strong projects fail, they assume the social layer will somehow emerge automatically. It rarely does.
To make this constructive, it helps to clearly describe what we mean by #openweb culture. Some core values historically included public-first communication rather than platform ownership, decentralised responsibility instead of central moderation authority, commons thinking rather than product thinking to nurture horizontal participation rather than audience/influencer hierarchies, this need clear #4opens processes rather than opaque decision-making.
These values were never perfect, but they created a different social environment from today’s corporate social media. If we do not actively cultivate these values, the surrounding internet culture will slowly overwrite them. If the Fediverse continues to grow without addressing culture as it currently is, the most likely outcome is large institutional instances dominate, smaller community spaces struggle leading to more moderation being centralised. This all shifts user expectations toward platform-style experiences.
At that point, the system may still be technically federated, but the culture will have drifted back toward Web 2.0. The code will be open, but the social dynamics will not be.
So the “extra step” is simply, we must talk about culture as deliberately as we talk about software architecture. That means asking questions like: What social norms should Fediverse communities encourage? What governance models support open participation? How do we keep the ecosystem diverse rather than dominated by large actors? What responsibilities come with running infrastructure in a commons network?
These conversations are sometimes uncomfortable, because they move beyond engineering into politics, sociology, and ethics. But avoiding them does not make them disappear, it simply means the culture will be shaped by default forces instead of conscious choices.
A simple way to frame this – A phrase that often works well in discussion is – “Code builds the network, but culture decides what the network becomes.” If we want the #openweb to remain something different from the #closedweb platform internet, we need to invest as much thought into the culture as we do into the code and #UX. Otherwise, the technology may succeed technically, but the social project behind it will quietly fail.
Public Money, Public Communication, Public Infrastructure
Public institutions are funded by taxpayers. Their role is to serve the public. So it should be obvious that their communication systems are open, accessible, and accountable to everyone -without requiring people to sign up to proprietary, for-profit platforms.
Yet this is not the world we live in. Today, much of public communication is effectively outsourced to the #dotcons. If you want to follow government updates, participate in consultations, or even access timely public information, you are often expected to create an account on a closed platform – designed for profit, data extraction, and behavioural manipulation. That alone should raise serious questions.
This contradiction is especially stark in Europe as they regularly speak about digital sovereignty, data protection and public accountability. And yet, at the same time, they rely on U.S.-based corporate platforms to communicate with their own citizens. It’s a strange situation:
Public institutions, funded by European taxpayers, using foreign, proprietary infrastructure to mediate public communication.
Not only does this create dependency, it also places public discourse inside systems that are not governed by public interest.
It’s not just ironic. It’s structurally broken, we should think about prosicuting the people who have made this happen.
The access problem, useing closed platforms to access public communication creates real barriers: Not everyone wants to create or maintain dotcons social media accounts. Some people are excluded for ethical, political, or practical reasons. Algorithms decide what is seen and what is not. Public information becomes entangled with advertising and engagement metrics. This undermines a basic democratic principle that public communication should be universally accessible, without conditions.
We already have an alternative to this curupt mess, the #DIY#OpenWeb comes from europe, it offers a different path. Instead of #closedweb platform dependency, it builds on open standards, interoperable systems with multiple access points, no user lock-in. This is not a new path, it is how the web was originally created to work in the EU.
An example project that contines this native mission and supports this is the #OMN whitch creates spaces where public institutions and public communities can meet on equal terms, without one dominating the other, and without relying on closed corporate systems. If institutions instead invest in and support the wider #OMN ecosystem, they help build something fundamentally different, a public communication infrastructure that is open by default, accessible to all, resilient and distributed and aligned with democratic values.
A simple principle, if it is funded by the public, it should be accessible to the public – without restriction. No accounts required, no platform dependency and no hidden gatekeepers.
We need to organise a call to act. Public institutions need to move beyond simply using the #Fediverse. They need to help build and sustain the commons that makes open communication possible. That means, supporting open infrastructure projects, funding shared ecosystems like the #OMN and building real, not facke PR commitment to public-first communication practices.
This is not just a technical shift, it is a political and cultural choice.
A simple #KISS way forward is to shift public social communication onto the #Fediverse. This is already a significant improvement on current platform dependency. However, I want to raise a point that may sound controversial at first, but is actually quite practical: public institutions should not rely exclusively on the existing codebases.
Most current Fediverse platforms have done vital groundwork – particularly in establishing shared protocols, interoperability, and a working culture of federation. That contribution is important and should be recognised. However, many of these tools evolved shaped by the same assumptions as #dotcons and constrained by #NGO project models. As a result, they can be complex, difficult to maintain, and not always well aligned with the long-term needs of public institutions or commons-based infrastructure.
A constructive path forward would be to fund the development of a small number of new, purpose-built codebases focused on commons publishing. Not one, but three parallel implementations.
Why three? Because diversity reduces risk. In practice, not every project will succeed – this is normal and expected. Funding multiple approaches ensures resilience, encourages innovation, and avoids over-reliance on a single solution. The cost of doing this would be minimal relative to existing public digital budgets, yet the potential long-term value is significant.
Importantly, this is not about replacing the existing ecosystem. Because the Fediverse is built on shared protocols, any new tools would remain fully interoperable with current platforms. This means users of existing services can still interact seamlessly, while the overall ecosystem becomes stronger, more diverse, and better aligned with public service values.
In short: build on what exists, but don’t be constrained by it. By investing modestly in new, commons-oriented infrastructure alongside the current tools, public institutions can shape a more robust, sustainable, and genuinely public digital communication space.
Outreach to @newsmast interesting to see the #NGO view of the real alt path we need to take https://hamishcampbell.com/thinking-of-workshops-to-run-at-nodes-on-a-web-noaw-unconference/ you guys might be interested in working on the 3ed workshop outline. The 3 codebase need to be 1) mainstreaming, 2) radical #NGO and 3) native messy grassroots. You guys could be the second codebase. We do need diversity, best not to keep blindly messing up this path in the current globe mess.
Stopped going to in-person general tech conferences around 15 years ago – they’d become beyond pointless. Since then, I’ve stuck to more focused online events.
Now heading back to an in-person one. Curious what I’ll actually find.
I have a feeling it’ll be about 75% pointless, 20% narrow geek, academic and #NGO-focused (slightly useful), and maybe 5% – probably less – actually useful.
Let’s see how that shifts after the event.
UPDATE: The event was posative, people were looking for change.