Why most radical tech is pointless, and why #indymediaback isn’t

Almost everything built in today’s alt-radical tech scene is, bluntly, pointless. Despite good intentions, most of it ends up feeding the endless cycle of #fashernista churn, flashy new platforms, bleeding-edge protocols, or encrypted communication tools nobody uses, built by isolated teams disconnected from real-world needs or history. This is the #geekproblem: a culture where novelty is fetishized, and social usefulness is an afterthought, if it appears at all.

Examples:

Secure scrolling tools: Every few months we see new chat apps, usually cryptographic fortresses with no communities. No one’s asking what these tools are for beyond vague abstractions like “privacy” or “freedom.” Tools without context.
Peer-to-peer silos: Projects like Secure Scuttlebutt (SSB) or many DAT spin-offs build entirely new social ecosystems that demand complete buy-in, rather than integrate into existing networks. What results is islands of lonely idealists yelling into empty timelines.
Protocol over people: Many Fediverse projects argue endlessly over specs like #ActivityPub or #Nostr, often prioritizing purity over pragmatism. What good is a protocol if no one actually uses it beyond a few devs congratulating themselves?

Why #indymediaback isn’t a pointless tech project, it offers something truly different. It is not “new.” It doesn’t pretend to invent a whole new ecosystem. It is an act of digital memory, a revival of the still-needed infrastructure that once helped build radical networks globally. #Indymedia worked. It published resistance. It distributed power. It was embedded in real communities and real movements. This is #nothingnew done right.

The #nothingnew approach mediates against the churn by reusing workflows, social trust, and existing cultural practices. It doesn’t ignore tech, it grounds tech. Examples:

#indymediaback uses simple publish-form-comment workflows, already familiar. No #AI, no #blockchain, no obscure identity layer. Just people posting and curating stories.

It connects to existing radical spaces: housing co-ops, street kitchens, climate camps—places where digital tools are needed right now, and where the point isn’t building a unicorn startup but having a place to publish the truth when the cops are lying again.

Why copying #dotcons isn’t enough, in the #fediverse we so far have replicate Twitter, YouTube, and Instagram — Mastodon, PeerTube, PixelFed. This is useful, to a point. But all code is ideology. Copying capitalist infrastructure dose smuggle in capitalist logic. Copying invites the #deathcult right back in through the side door.

indymediaback avoids this trap. It doesn’t replicate any#dotcons logic or UX patterns. It revives a publishing common that worked before Silicon Valley captured this path. And more importantly, it’s embedded in a set of radical social practices: the #PGA hallmarks, the #4opens, and the messy, beautiful legacy of grassroots movements who already knew how to organize.

The value of #indymediaback isn’t just in tech. It’s in trust-based social continuity, the hidden glue of any working movement. Without this, you don’t have a radical tech project. You have a ghost repo on GitHub. That’s the central point, without real community, without continuity, without trust, radical tech is a dead end.

This is the carrot and stick we need now. If you care about the #openweb as a human value network, not just a protocol playground, you have to build things people can use today, and that people want to use, not because it’s encrypted or federated, but because it serves a purpose they already have.

This is where the wider #OMN (Open Media Network) comes in. It’s not another protocol war. It’s a shovel to compost the inhuman mess we’ve inherited. It’s a framework built with the #4opens, to grow digital commons that don’t depend on VC, control freaks, or fashion. It’s where we build bridges between radical tech projects, rather than isolate ourselves in yet another Git-based castle.

In short, it’s a path of people over product, process over platform. We don’t need more “solutions.” We need to stop being prats, pick up the tools we already have, and start rebuilding.

Food for thought, and action.

What should be closed? And what should never be?

A conversation about ideology, sociology, and the #openweb. Let’s start with a basic liberal framework: “Most social interactions should happen in the open. Some personal interactions should remain private.” Seems reasonable, right? That’s the position many of us think we agree on. Yet when we look at how our technology, and by extension, our society, is being built, that balance is totally out of whack. Today, more and more of life is CLOSED:

Closed apps.

Closed data.

Closed social groups.

Closed algorithms.

Closed hardware.

Closed governance.

And on the flip side, the things that should be protected, our intimate conversations, our location, our health data, are often wide open to surveillance capitalism and state control. What the current “common sense” dogma gets wrong? What is missing is the idea that mainstream tech culture, privacy absolutists, and many crypto/anarchist types:

Almost all good social power comes from OPEN.
Most social evils take root in CLOSED spaces.

When people organize together in the open, they create commons, accountability, and momentum. They make movements. When decisions are made behind closed doors, they breed conspiracy, hierarchy, abuse, and alienation.

It’s not just about what is open or closed, it’s about who controls the boundary, and what happens on each side. If we close everything… If we follow the logic of total lockdown, of defaulting to encryption, of mistrust-by-design… then what we’re left with is only the closed. This leads to a brutal truth, the powers that dominate in closed systems are rarely the good ones.
Secrecy benefits the powerful far more than the powerless. Always has.

So when we let the #openweb collapse and treat it as naive, we’re not protecting ourselves. We’re giving up the last space where power might be accountable, where ideas might circulate freely, where we might build something together.

Examples: When openness was lost. Let’s talk about a real-world case of #Diaspora vs. #RSS. 15 years ago, Diaspora emerged with crypto-anarchist hype as the alternative to Facebook. It was secure, decentralized, and… mostly closed. It emphasized encryption and privacy, but lacked network effects, openness, and simple flows of information.

In the same era, we already had #RSS, a beautifully open, decentralized protocol. It powered blogs, podcasts, news aggregators, without permission or centralized control. But the “Young #fashionistas ” of the scene shouted down RSS as old, irrelevant, and too “open.” They wanted to start fresh, with new protocols, new silos, new power. They abandoned the working #openweb to build “secure” ghost towns.

Fast-forward a decade, and now we’re rebuilding in the Fediverse with RSS+ as #ActivityPub. The same functionality. The same ideals, just more code and more complexity. That 10-year gap is the damage caused by the #geekproblem, the failure to build with the past, and for real people.

So what is the #geekproblem? At root, it’s a worldview issue. A failure to think about human beings in real social contexts. Geeks (broadly speaking) assume:

People are adversaries or threats (thus: encrypt everything),
Centralization is evil, but decentralization is always pure (thus: build silos of one),
Social complexity can be reduced to elegant protocols (thus: design first, use later).
But technology isn’t neutral. It reflects ideologies. And if we don’t name those ideologies, they drive the project blindly.

A place to start is to map your ideology, want to understand how you think about openness vs. closedness? Start by reflecting on where you sit ideologically, not in labels, but in instincts. A quick sketch:

Conservatism: Assumes order, tradition, and authority are necessary. Values stability, hierarchy, and often privacy.

Liberalism: Believes in open society, individual freedom, transparency, and market-based solutions.

Anarchism: Rejects imposed authority, promotes mutual aid, horizontal structures, and often radical openness.

None of these are “right,” but understanding where you lean helps clarify why you walk, build or support certain tools. If you’re building tools for the #openweb, these questions matter:

Do you default to closed and secure, or open and messy?

Who do you trust with knowledge—individuals or communities?

Do you believe good things come from control, or emergence?

These are sociological questions, not just technical ones, maybe start here: https://en.wikipedia.org/wiki/Sociology and https://en.wikipedia.org/wiki/List_of_political_ideologies. Where do we go from here? Let’s bring this back to the openweb and the projects we’re trying to build, like:

#OMN (Open Media Network)

#MakingHistory

#indymediaback

#Fediverse

#P2P tools (DAT, Nostr, SSB, etc.)

All of these projects struggle with the tension between openness and privacy, between usability and purity, between federation and anarchy. But if we start with clear values, and an honest reflection on the world we want to create, we can avoid the worst traps. Let’s say it plainly:

Not everything should be open. But if we close everything, we lose what’s worth protecting.

Let’s talk: What do you think should be closed? What must be kept open at all costs? What’s your ideological instinct, and how does it shape your view of the #openweb?

Where’s the Resistance to Algorithmic Monopolies?

The big question need to be highlighted: where will pressure for meaningful regulation of #dotcons algorithmic monopolies actually come from?

Right now, it’s hard to see. Lawmakers generally have a poor grasp of the real problems, decades behind on both the tech and its corrosive social consequences. Most legislation we get is either pre-packaged by lobbyists from the #nastyfew controlled platforms causing the harm, or superficial and narrow, #fashionista focus on headline optics like “online harms” or “child safety,” instead of addressing the deeper crisis of algorithmic control, attention addiction, and social fragmentation for control.

Even worse, and this needs to be said loudly, the civil society institutions that should be resisting this mess are captured. Charities, #NGOs, media orgs, #geekproblem digital rights groups. Whether for funding, publicity, or simple convenience, they’ve tied their missions to the very tools they should be questioning. Rather than building alternatives or even naming the deeper problems, they instead focus on “using platforms better” or “more ethically”, which only serves to legitimise the #techshit they should be dismantling for composted.

This is classic #mainstreaming. It’s how radical energy gets drained, redirected, and eventually used to feed the system it once opposed. Meanwhile, into the vacuum of real critique and action steps, conspiracy-driven nonsense and cynical populism to feed the cycle.

This is why grassroots and native #openweb spaces like the #Fediverse matter, not just as “alternatives” but as active resistance. They are places where we can build different logics, embed different values, and avoid replicating the same centralising, manipulative dynamics.

It’s also why we have to defend these spaces, especially when they’re messy or imperfect. Because if we don’t build and protect something better, we’ll be left with a fight where even the so-called opposition is simply more of the same problem.

Composting the EU Tech Mess: From #NLnet to #Eurostack

First step: Stop being a prat

We have strong passive #blocking forces stopping the real change and challenge we need before we have any hope of changing the world, thus we as a community have to change our stance towards this blocking. And the first step – the most important one – is painfully simple: Stop being a prat.

That means:

Stop pretending you don’t understand the stakes.
Stop making perfect the enemy of good.
Stop whining about how broken things are while refusing to touch the tools that exist.
Stop treating radical, working alternatives like they’re someone else’s hobby project.
Stop waiting for someone else to do it.

You don’t need a degree in political science or coding, or anything to see what’s happening, from floods and fascists to boat evictions and mass precarity. You don’t need permission from a foundation or a blue tick to take part, you don’t need a five-year strategy. Simple, you just need to stop being a prat, and start doing, so, what does “not being a prat” look like?

Instead of doomscrolling, publish one thing that matters using #OMN tools or paths.
Instead of performative politics, help document what’s actually happening around you in a #4opens way.
Instead of building personal brands, build open #Fediverse infrastructure that your community can use.
Instead of hiding behind cynicism, show up and collaborate – messily, imperfectly is fine, just try not to be a prat.

Why it matters, because the #nastyfew people seizing power right now, from JD Vance to the canal eviction bureaucrats, aren’t being prats. They’re serious about building institutions to shape futures. The tragedy is that our side, the ones with the heart, the vision, the history, are too often busy being clever, passive, cool, and precious, kinda like prats….

The first revolutionary act in the 2020s isn’t heroic, it’s just showing up, not being a prat, and doing the obvious things, together. This is simple, most importantly #KISS please don’t be a prat about this, thanks.

The #mainstreaming is talking about the #deathcult – So why are you still waiting?

The #mainstreaming is talking about the #deathcult – So why are you still waiting?

It took four decades of sleepwalking through #neoliberalism, cultural decay, ecological collapse, and social atomisation, but at last, the #mainstreaming is starting to talk about the #deathcult we’ve been worshipping.

Case in point: Steve Coogan – yes, Alan Partridge – is now publicly accusing Keir Starmer and Labour of “paving the way for Reform UK,” the rising hard-right threat. Here’s the article. It’s not satire, it’s despair. Coogan’s right, and a few years ago, such a comment from a mainstream celebrity would’ve seemed extreme. Today? It’s just stating the obvious.

The “centre” has collapsed. The “left” has hollowed itself out in fear. And the space where #lifecult politics might live is now overrun with fear, cynicism, and opportunism. This is the #deathcult in action, the system that tells you there is no alternative while everything burns down around you. For 40 years we’ve been taught to accept decay as progress, control as freedom, and despair as maturity.

But here’s the thing, we told you so, for people like me, and many others working on open networks, digital commons, grassroots media, and post-capitalist systems, this isn’t news. We’ve been working and talking about this for decades.

In the world I am in, we’ve already working on alternatives: Decentralised governance via the #OGB. Federated publishing through the #OMN. Ethical tech rooted in the #4opens. And a cultural path that doesn’t rely on selling your soul to #dotcons or begging #NGOs for scraps.

We weren’t trying to be ahead of the curve. We were trying to get people to notice the damn cliff. Now that we’re tumbling over it, suddenly everyone’s surprised. Now the #mainstreaming, which ridiculed or ignored these grassroots, native paths, is whispering our language, but still to often refuses to take the paths we are on.

On this continuing common sense #blocking, let’s be blunt – now is the time to stop being prats about this necessary change. No more waiting for the next electoral saviour. No more hiding behind polite inaction. No more pretending that rebranded centrism is going to save us from fascism, it won’t.

If you're reading this, you probably already know the centre won't hold. So what's stopping you?

We don’t need more think pieces, what we need is more people to get their hands dirty, pick up the tools we’ve been building, and start doing the real work. This means, in my area of tech activism:

Federating your networks.
Hosting your own content.
Engaging in horizontal governance.
Publishing with principles.
Building trust and commons, not brands and silos.

The good news? The framework paths exist, the seed communities exist, the infrastructure, with the #Fediverse is small but growing solid. What’s been lacking is you, your time, your courage, your refusal to keep being a prat, to become brave enough to take this different path.

This Isn’t about nostalgia – It’s about now. We’re not dreaming of the past, we’re recovering futures that were lost when the #dotcons, the NGOs, and the #neoliberals buried the #opwnweb’s radical possibilities under a mountain of grift and branding. This isn’t utopianism. it’s simple pragmatism, resilience. It’s how we survive the rise of the new right without defaulting into the arms of the old centre – the ones who made this mess in the first place.

And for the record, if you need reminding: In this tech path, we don’t need another “platform.” We don’t need another fake “community” run by venture capital. We don’t need more loud voices doing nothing. What we need is to take paths back to rooted, open, and federated ways of working.

This is what the #OMN and #4opens have always been about. You can ignore it for another year or two, but you won’t outrun what’s coming, better to start planting now – it’s not too late to grow something real.

The time is now, if you’re waiting for permission, this is it. The people who once called us cranks are now writing op-eds about the collapse we have seen coming for years. The centre is falling, the right is mobilising, the old paths are dead ends.

The future will be built by those who show up now.

We need you, not in six months, not after the next election, now. Stop being a prat, pick up the tools to help build the next world – before the current one burns it all down.

First step: Stop being a prat

Rise and Fall of Grassroots #OpenWeb

The #fashionistas are coming https://yewtu.be/embed/u_Lxkt50xOg? It’s time to become more real before this inflow swamps our “native” reboot, if we let them they will consume it and shit it out as more mess. To mediate this shit storm, it’s time to act, please, feel free to repost these web posts, thanks.

To understand where the #Fediverse and the #OpenSocialWeb are heading, and how not to lose our way, we need to reflect on where we’ve come from. The history of grassroots #openweb activism offers both inspiration and hard lessons.

Foundations are built by real people, social movements start local, they begin with people on the margins – those directly affected by injustice – taking action with the tools they have. In the late ’90s and early 2000s, tech projects like #Indymedia were the blueprint: decentralized, radically open, and run by volunteers who trusted each other and worked horizontally. It worked, for a while.

Today, projects like #OMN (Open Media Network), #indymediaback, and #makeinghistory try to learn from that past. They aim to reboot media infrastructure and historical memory, powered by the #4opens: open data, open source, open standards, and open process. We need to remember that this kind of work doesn’t scale by magic, it grows from grounded trust and native infrastructure, not from #VC injections or #NGO grants.

The trap of #NGO thinking is one of the biggest reasons grassroots projects fail, co-optation. When grassroots groups chase funding, they start shifting agendas to fit the funder’s priorities. Slowly, the mission gets neutralized. Culture changes, risk-taking of change and challenge vanishes, the projects to often become empty shells wearing yesterday’s slogans.

This has happened time and again, from later #Indymedia nodes to #EU-funded tech projects that are now more about kickbox reports than what any “user” wonts or the needed basic radical change. We can’t afford to go down this path again in the current #openweb reboot, the Fediverse.

We need Spiky/Fluffy balance, mutual aid that’s not just charity, but infrastructure. That’s where the #Fediverse shines: not just as an alternative platform, but as a parallel public space for organizing, sharing, and then resisting. It has to support both spiky (radical, disruptive) and fluffy (care-focused, relational) approaches.

On these paths, memory matters, projects like #makeinghistory remind us: if we don’t remember our wins and losses, we’ll keep repeating the same mistakes. Documenting not just content but working practice, how decisions were made, what trust looked like, what failed and why – is crucial. History is not just a mirror; it’s compost.

No monoculture, today, #Mastodon is becoming the monoculture of the Fediverse. It’s not evil. But it is dominating to the point of distortion. It’s following NGO-friendly paths and watering down the radical possibilities the #openweb offers. That’s a problem. We need more balance, more useful codebases, more governance experiments. This space is meant to be a garden, not a plantation.

Security isn’t paranoia, it’s culture, security on the #openweb isn’t about creating another bureaucratic nightmare of permissions and logins. It’s about cultural practices, trust, openness, moderation by consent, and keeping things simple. Most of all, it’s about not building what you don’t need, complexity is the enemy of security.

Final thought, to build real alternatives, we need to stop chasing virality and start building resilience. Less hype, more humility. Less “engagement,” more entanglement. And always, a ruthless focus on not becoming the thing we were trying to replace. Let’s not feed the mess. Let’s compost it and grow something better.

The problem of too big, Mastodon

I would start to say, with care, that #Mastodon is now heading in the wrong direction. Not because it’s inherently bad, or malicious, or “captured” in some conspiratorial sense. But because it’s become too dominant, tipping the scales far away from the diversity and messiness that a healthy #Fediverse needs.

This isn’t about blame, it’s about balance. To keep the #openweb alive and meaningful, we need to nurture other codebases, other, paths, cultures, and radically different governance paths alongside Mastodon’s dormant trajectory. Let’s acknowledge where Mastodon succeeded: It has been a gateway into the Fediverse, by mimicking Twitter, it provided a familiar experience that let mainstream users, journalists, #NGOs, and even some governments dip their toes into decentralization. It helped break the suffocating monopoly of Twitter/X. This was useful, necessary even. We needed a bridge.

But now? That bridge is being pushed/mistaken for the destination. And worse, it’s reinforcing the patterns we were trying to escape. Instead of blossoming into a diverse ecosystem and experimental tools, the #Fediverse is shaped by Mastodon’s design limitations and its pushing institutional gravity. That’s the problem, it’s not just a project any more, it’s becoming a bottleneck.

With #NGO-centric thinking shaping many of the newer Fediverse-adjacent events (like #NGI forums or EU funding discussions) which are now populated by the same #NGO/#dotcons crowd and comfortable liberal institutions that avoid risk, fear grassroots control, and domesticate the web for funding reports.

So, Mastodon isn’t “bad” and it played its part well. But its institutional path is now out of alignment with the nature of the Fediverse: the #4opens, radical transparency, permissionless innovation, and native grassroots culture. This is a poisoned balance, not because Mastodon is wrong, but because its gravitational pull is now preventing new paths from taking root.

What’s the alternative? Push for federation that supports collectives, not just individuals. Rebuild spaces for group publishing (like #Indymediaback) and shared authorship, not just influencer-following. Keep pushing the #4opens: Open data, open standards, open governance, open code – not just a logo and a code of conduct. Remember that a monoculture is always a point of vulnerability. Diversity isn’t optional, it’s the core strength of the #openweb.

So yes, Mastodon is a problem on balance, even as it was a solution before. But still, we don’t need to burn the bridge – but we do need to compost the monoculture and grow a thicker forest around it. Because decentralization means divergence, not convergence to one project’s roadmap #KISS

Trying to Remember: A Personal Reflection on Activist Histories and Memory Holes

Actors, Power, and Collective Publishing: Rethinking Fediverse Architecture for Grassroots Media

We recently had an extended and thoughtful discussion on signal between collaborators working on #IndymediaBack and #MakingHistory, a key issue emerged: how should we structure “actors” (ActivityPub identities) in a network where the focus is collective action, not individual performance? This question isn’t just technical. It’s political, and central to the success or failure of rebooting radical grassroots media within the #Fediverse.

The tension is about balancing the individual and the collective. In most current Fediverse platforms (like Mastodon or PeerTube), each user is an “actor” with their own inbox/outbox, mirroring the logic of the mainstream #socialweb where identity and expression are deeply individual. But for platforms rooted in collective publishing, such as a revived #Indymedia, this doesn’t map neatly.

“We are trying to balance individualism with collectivism. People already have all the individualism they can take, we need a structure to support the collective.”

That means maybe moving away from assuming every account needs to be a visible, subscribable actor. Working model: Per-instance actors first, a consensus is emerging around per-instance actors – e.g., the Newswire and Features flows of a local Indymedia site act as the primary publishable entities in the Fediverse. These represent the editorial collective’s curated output – not just anyone shouting into the void.

External trusted contributors (like info@hamishcampbell) would publish content from their own Fediverse accounts using hashtags like #oxfordindymedia, which the local Indymedia instance detects, vets, and republishes.

This brings three key benefits:

Curation over chaos – Stories don’t just flood in via hashtags; they’re filtered through trust relationships.
Permissioned federation – Only trusted flows (or untrusted but manually reviewed ones) are accepted. Hashtag spam is naturally blocked.
Maintaining editorial identity – Subscribing to an Indymedia instance means subscribing to its judgement, not just raw firehose feeds.

Do we need per-user actors? Here’s where things get messy, and interesting. Three models were debated:

Classic Fediverse model: Each user has their own actor. This supports full transparency and traceability of actions, but risks returning to individualist norms and opens the door to abuse or platform drift.
Invisible user accounts: Users exist internally for moderation or curation roles, but aren’t visible in the Fediverse as actors.
Controlled per-user actors: Users do have actors, but these are only used to publish activity logs, not posts. Think: “Editor X approved story Y”, useful for building transparency and trust within an open process.

Option 3 sits nicely with the principles of the #4opens, particularly open process and open governance. It provides a transparent audit trail without pushing users into the spotlight.

UX vs backend architecture, what becomes clear is that the user experience should foreground collective flows – Features, Newswire, Tags – while any per-user mechanics operate in the background, supporting moderation, traceability, or edge-case publishing. Whether those background accounts are AP actors or not might depend on implementation details.

“It’s not about the actors per se — it’s about what shows up in the front-end UX, and how we build trust in the process.”

Final considerations, networks like #IndymediaBack default to collective-first publishing, with user actor functionality off unless needed. #MakingHistory, by contrast, might enable user actor publishing to support mass collaborative storytelling. Both platforms rely on whitelist federation, meaning only trusted instances and users can feed directly into the editorial stream. Abuse prevention comes not just from code, but from the politics of moderation, curation, and shared norms.

We probably need per-user actors, but used sparingly and carefully.
We definitely need per-instance actors for trusted collective outputs.
Hashtags are a start, but the flow must be curated and accountable.
UX should put collectives front and centre, with user identity in the background.
This is a political choice, not just a technical one, and that’s a good thing.

For more on how this fits into the broader reboot of radical media infrastructure, see:
Rebooting Radical Media (YouTube)
Programming: Open Media Network

Dev test work for Makinghistory application

The Mess We Make (Again… and again)

Ten years ago, I remember being told, often condescendingly, with smug certainty, that hosting in the cloud was the future. That what I was working on, #DIY grassroots self and community hosted tech was the dinosaur, a dead end, old obsolete thinking, out of touch. Despite spending years pointing out the obvious flaws in this pushing, for this I got only that my “native” path was irrelevant, for Luddites, they said. Legacy thinking, dead tech walking.

Well, here we are, a decade later. And guess what the cloud: It was expensive, less performant, less secure, and a gateway to increasingly exploitative pricing models. This isn’t hindsight bias, the warning signs were always there. But many #fahernista and #geekproblem people get caught up in the glossy surface and tech hype mess, repeating the same mistake we’ve made across generations of #geekproblem tech, believing scale and #PR buzzwords were synonymous with progress.

Let’s now be clear on what actually happened.

We handed over infrastructure to a handful of giant platforms that lock us in and bleed us dry.
We lost resilience, sovereignty, and basic control over our own data.
We normalized rent-seeking as a business model.
We pushed decentralization off a cliff and called it “abstraction.”

Meanwhile, local compute got cheaper, storage exploded in affordability, bandwidth costs continued to fall, #dotcons threats increased. And guess what? Running things locally started making sense again, just like it always does when the #PR smoke clears and mess composts.

The lesson, which we need to now bring to #crypto and #AI, just because something is fashionable doesn’t make it in any way real or sustainable. That tech #PR hype cycles aren’t innovation, they’re marketing. And when you stop looking at the core trends (cost, control, resilience) and just ride the buzz, you’ll end up where we are now, mess, bloated budgets, shrinking trust, and a growing #techshit pile to clean up.

We need to re-learn the value of #KISS grounded thinking, to remember that local, #4opens, transparent, and interoperable #openweb systems aren’t retro, they’re essential. This isn’t about nostalgia for the old paths, It’s about having power over our basic infrastructure again. The cloud, at the time and in looking over our shoulders, was smoke and mirrors, a detour, it’s now past time to get back on the real progressive #Fediverse path.

History has a lot to say on the peasant revolt vs. liberal half-measures

Can bureaucracies join the #Fediverse? Yes – with WordPress + ActivityPub

Let’s stop pretending every institution has to “go social” by building new habits, communities, and platforms from scratch. We already have a solid, simple tool that can bridge them from the #dotcons into the #Fediverse: WordPress + the ActivityPub plugin.

Institutions want control – That’s OK. Bureaucratic institutions, local councils, unions, media orgs, #NGOs, aren’t designed for fast, messy social interaction. They won’t control over moderation, messaging, and timelines. That’s how they work, the good news is that they don’t have to surrender that control to leave the exploitative corporate platforms.

There is a path to step sideways into the #openweb by using tools they already trust, #WordPress, plugging into the #Fediverse with a few small adjustments. Here is how this works:

Use WordPress as a public publishing hub, it already supports articles, media, comments, and user permissions. It’s familiar to thousands of comms and IT staff.
Install the ActivityPub plugin. This lets every post become a Fediverse-native object. Readers on Mastodon, Lemmy, Friendica etc. can follow and share the content.
Keep moderation tight. Comments from the Fediverse can be held for review by default. Content inflows are closed, moderated, or opened based on trust levels.
Build distribution without chasing followers. The content flows outward. Others can quote, reply, remix – but the source stays under local control.

The alternative? Indie News, if not WordPress, the more adventures could host a dedicated Fediverse news instance (like a rebooted #IndymediaBack) or even set up a microblogging server using software like WriteFreely or Plume. These would support long-form or short-form posts, stay focused on the institution’s goals, avoid chasing engagement metrics from #dotcons. And again, comments and responses could be moderated or disabled, depending on needs. No spam tsunami. No culture wars. Just distribution and visibility – on native #openweb terms.

Why this matters, many public institutions want to move away from Facebook and Twitter, but feel locked in. They know those platforms are toxic, yet all the people are there. But what if we stopped treating the #Fediverse like a chaotic free-for-all and started showing how it can also work for structured, “responsible” publishing? WordPress already has millions of users. The ActivityPub plugin is mature, maintained, and already working. All it takes is will, and a little guidance.

Benefits at a glance:

Maintain editorial control
Publish to a growing #openweb ecosystem
Avoid vendor lock-in and algorithmic censorship
Build real, direct relationships with communities
Help decentralize digital infrastructure for the public good

If an institution can run a blog, it can join the Fediverse. If it can post on Facebook, it can do better. Let’s stop waiting for perfect platforms and start using the tools we already have, WordPress is an underrated bridge from the bureaucratic world into a better, fairer, and more resilient #openweb path.

Why Doesn’t Every City Have a Fediverse Server?

Why Doesn’t Every City Have a Fediverse Server?

A reflection on Oxford, the web, and the invisible gap we’re not naming. It’s a simple question, but one that says a lot about where we’re at with the #Fediverse and the broader #openweb reboot: Why doesn’t every city have its own Fediverse server?

I’ve been looking – specifically for my city: Oxford, UK. And the answer seems to be… Nope. Nothing. Not a single clearly local Mastodon, Lemmy, Pixelfed or similar instance. This might seem trivial, but it’s actually a big red flag about where we are failing to root the #Fediverse in the real world.

Wait – Why should cities have their own servers? Because servers are more than just infrastructure, they’re community spaces. They are places where shared context matters. In a healthy #openweb ecology, you’d expect to see:

A Mastodon instance for Oxford academics and students
A Lemmy server for Oxfordshire campaigners sharing local issues
A Mobilizon instance for local events, climate actions, social meetups
A PeerTube or Castopod space archiving local talks, indie music, alt-news

These are the digital town halls we should be building. But we’re not. Why? Oxford isn’t just any city. It is where the World Wide Web first found public ground in the UK. I used the first web browser in a room set aside for “the internet” here almost 30 years ago, it was a wonder. It’s a place that is full of geeky students, hackers and programmers. With a deep history of academic freedom and radical thought, that has long served as a symbolic cradle for digital culture. If we can’t see clear Fediverse infrastructure here, something’s broken, and not just in Oxford.

What’s holding us back? Possibilities, the myth of spontaneity? We assume that because the Fediverse is “open,” it will naturally emerge everywhere. It won’t. Like any commons, it needs cultivation, volunteers, funding, attention.

Invisible technical barriers, running a Fediverse server isn’t hard, but it’s also not beginner-friendly. And even “geeky” students are under immense pressure, rents, loans, side gigs. Who’s got time to run infra?

Cultural disconnection, we have a user class and a developer class, and they rarely mix. No one’s stepping up to build for their community, because the tech feels distant, or worse, owned by someone else.

#NGO capture & misplaced focus, a lot of #FOSS energy gets eaten up by grant-funded projects that serve other bureaucratic ends. Meanwhile, grassroots needs, like “a city-based server for sharing local stuff”, get overlooked or dismissed as unscalable.

What do we do? Let’s flip the question around. Why NOT have a Fediverse server in every city? If we started treating servers like digital community gardens, then:

Local campaigns could run Lemmy or Mastodon spaces
Libraries could host Pixelfed galleries of community art
Climate groups could run Mobilizon for mutual aid and action
Neighbours could share events and info, outside of corporate silos

Oxford needs a server, so does your city. This is a callout – and a call-in, if you’re a sysadmin, activist, student, tinkerer, or just someone who cares about your city and the #openweb, start asking: where’s our server? Let’s build it. Let’s map it. Let’s make the Fediverse a place of places, not just a cloud of abstract URLs. We need to get the #Fediverse out of “nerd island” and into the towns and cities we actually live in.

On the history of the web and Oxford (BBC). Want to help start a #MastodonOxford or similar? Let’s talk. We have the tools. We just need the will.

Programming Mission: Let’s Fix the Fediverse Discovery Gap

Programming Mission: Let’s Fix the Fediverse Discovery Gap

Here’s a small but powerful challenge for #openweb builders – and a perfect #DIY project if you’re fed up with the current #geekproblem. I’ve been trying to find #Fediverse instances that actually cover my town, Oxford, UK, so I can help promote and grow them locally. You’d think this would be simple, right? But… nope.

Tried the standard “instance pickers”? Dead ends. Tried generic web searches? Useless #SEO sludge. Tried maps like this one, a good start https://umap.openstreetmap.fr/en/map/fediverse-near-me_828094#7/52.076/-1.714, but nothing covering Oxford.

Why is this happening? Because our current tools focus only on technical facts (server specs, software used, uptime, etc.) and ignore the uncontrolled (dangerous) metadata that actually makes discovery meaningful:

What’s the instance for?
Who does it serve?
What community does it represent?
Where is it rooted geographically or socially?

This is the #geekproblem in action: great code, but no way to find things people actually want to use. What’s the fix? Someone (maybe you?) could create a community-focused discovery tool that:

Encourages instance admins to tag with location, community, topics, etc.
Provides search/filter UI that works for real people, not sysadmins
Uses the Fediverse’s open standards (#ActivityPub + #microformats) to pull this info in
Maybe even integrates with OpenStreetMap or a simple opt-in geo-tagged registry
Outputs something friendly – like “Find your Fediverse community in your town”

This is not a hard project, it’s a weekend hack for someone who cares, but it has real social value as it helps bridge infrastructure to lived communities. That’s the core of the #openweb reboot.

So for people who can’t see why this matter. If we want the Fediverse to grow beyond techies and Twitter refugees, we need to help people find their people. Local discovery is key. Place-based communities are still powerful, especially when rebuilding trust, mutual aid, and shared media in a collapsing world.

So, want a simple mission? Build a tool that helps people find #Fediverse instances by town, city, or region. Start with Oxford, but make it global. Make it open. Make it federated. And when you do? I’ll be the first to push it out.

#Fediverse #OMN #openweb #4opens #FediverseDiscovery #programmingchallenge #Geekproblem #MutualAid #CodeForGood #FOSS #localweb #trustnotcontrol #KISS

Update: my suggestion of path, a simple UX:

A few dropdowns over the map,

Region (countries are regions, anti-nationalistic)
City/area (a county or city)
local (village, area in city)
Them maybe latter hyper local (but not for now)

Then we have subject – it would be normal to have a multi subject hashtag map, that updates on each click – adding the clicks to a list on the side – with “new button” to jump back to start.

Then you have advanced for the normal tech stuff… which currently is the front end on most pickers. This would also be displayed on the info box for each instance on the map, so still central, just not AT THE FRONT.

UPDATE: can just pull all the existing data out of the current sites like https://instances.social/list#lang=en&allowed=&prohibited=&min-users=&max-users= as these are all #4opens. So the projected site could be up and running with full data in little time. Yes, you would have to ask people to tag their installs to geolocate their instances. This could be done a hard way or a simple #KISS way like any admin in the instance adding a #hashtag with a geolocation hashtag after it. Then periodically go through the instance list and spider all admins on each instance if you find the hashtag – add the next hashtag as a geolocation or something as simple as this.

Ideas in comments, please.

UPDATE: this is this one https://fediverse.observer/map works better still nothing in Oxford – it seems to be pretty random with little relevance to subject and area, is it by IP address, that would be #geekproblem

Why Doesn’t Every City Have a Fediverse Server?