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

UPDATE: On this needed path, let’s try and focus on diversity of codebases. As the is currently too much focus on vertical, #Mastodon is locked into its own trajectory, a closed loop of PR, hierarchy, and “favourites over merit”, so trying to wrestle it into something else is a waste of energy.

The smart path is to let it drift into its own #mainstreaming Fediverse while we work on the #openweb reboot without importing it mess path. The wider challenge is making sure our reboot isn’t just “not Mastodon” but actually functional, grounded, and healthy, with native governance, trust-based collaboration, and the #4opens at the core.

If we’re talking plan, I’d frame it as:

Draw the line – Publicly define what’s “native” openweb culture and what’s toxic carry-over from #geekproblem and #NGOcapture.

Build in public – Open docs, open processes, open code, open governance (#4opens), so trust compounds over time.

Seed alternative centres of gravity – Forge small, working nodes that can federate and interoperate without depending on a single code-base and Dev crew.

Culture over code – Prioritize conviviality, generosity, and horizontal decision-making before feature creep.

Pull people sideways – Attract users and devs who are frustrated with the PR-walled gardens, not by attacking mainstreaming Mastodon but by showing something that feels better to use and be part of.

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?

This is a story of power, plain and simple

Over the last few years, we’ve been watching a familiar story unfold, we’ve seen repeat itself in radical spaces, tech movements, and grassroots networks for decades. It starts in the grassroots with “progressive” #fashernistas (yes, them) pushing themselves into the front to speak for “us.” They talk the talk of decentralisation, care, community, and #FOSS ethics. They wear all the right hashtags: #opensocialmedia, #Fediverse, #commons, #techforgood. But when you look at how power is actually exercised behind the scenes, it’s something else entirely. This is a story of power, plain and simple. Not in the dramatic “revolutionary” sense. But in the subtle creep of careerism, institutional capture, and “safe” social capital games that flatten the radical and uplifts the “palatable”.

Let’s take a few examples from the #activertypub world, first with the #SocialHub stagnation, this open space was originally created by the grassroots crew to shape the standards of the decentralised web, It was originally a commons, protocol-building and governance exploration space. So, what happened? The people now “leading” came from lifestyle #fashionista activism and wannabe NGO circuits, who in the end were all trying to be embedded in the institutional funding environments, or visiting from the safe academic bubble. And thus they brought with them the dogmas of safe spaces, of “emotional consensus,” “hidden affinity group governance,” and “(ex)inclusive dialogue”… that JUST SO happened to exclude the radical and messy paths that are actually native to the #openweb, the bad mess they then made, ended up only pushing the dogma of the #geekprolem as it was the ONLY path they could imagine controlling in a way that would not threaten the thin connection to the institutions they were feeding from. This behaviour so often slips into forms of parasitism, which is not a good thing at all.

Then we have the current #Fediverse outreach infrastructure capture, where we’ve seen the same class of actors attach themselves to the most visible projects – like Mastodon, ActivityPub standards, and now “Fediverse governance.” They secure seats on boards. They host conferences with glossy branding and friendly logos. They use these controlled spaces to then push out “code of conduct” documents and “safe space” branding… while closing and excluding the very messy native infrastructure of discussion and direction that is both native and needed.

Examples? #Mastodon’s GitHub, issue tracking, and moderation are all tightly controlled by a small clique around the project founder. Community voices are kinda tolerated at best, discarded at worst. The project is moving onto the #NGO path, no bad thing in its self, but with its years of pushing its own branding as THE Fediverse, it becomes a bad thing. In this, there is a very real debt of damage they need to pay back – as a part of a functioning gift economy – saying sorry and admitting mistakes would be a good first step.

Then we have the example of the #FediForum events, pushing into the space blindly, with zero historical context or any actual knowledge, to represent the #activertypub ecosystem. The problem is they paywalled, which lead “naturally” to increasingly gate keeping with #NGO commercial interests being pushed to the front to represent “us”. When the radical and experienced grassroots voices obviously don’t get involved, as they simply refuse to step over the paywall. This is an ongoing mess, that we do need to compost and not only with #fashionista outrage but with real working paths, we used to do this, but we can’t any more – why?

Over the last few years we have had proposals for genuine horizontal governance, that could have been used to shift this mess making and to actually shifts power outward – but these were labelled “too messy,” “too political,” or “not the right time.” This is not accidental, it is liberalism functioning as control – with a smile. So… what can we do? Let’s be clear: This is a power issue. It’s not about bad intentions. It’s about how power is used, and then abused, even in the so-called “horizontal” paths.

The first thing we have to do is recognise the smell of #NGO-style liberalism that so easily hides itself in good intentions, grants, DEI language, and “process.” But it then ends up:

Disempowering community autonomy
Replacing radical potential with “professionalism”
Marginalising away activists and messy real-world projects
Recreating the same vertical hierarchies, just with better “open” branding

Composting this mess is needed to break the cycle:

Build and back native projects. The only way to push back against capture is to grow infrastructure from within our communities, like: #OMN (Open Media Network) #OGB (Open Governance Body). These must be trust-based, not credential-based. That means supporting those doing the work without demanding they translate it into pointless and most importantly powerless NGO-speak to be taken seriously.
Use the #4opens as a filter, this simple social retelling of #FOSS is designed precisely to push out the 95% of #techshit and focus energy on projects with: Open source Open data Open standards Open governance. Apply these consistently, and the parasite class will struggle to keep and find a foothold.
Push for messy, lived governance, stop waiting for perfect systems. We need to prototype imperfect, transparent, accountable governance now. It should be: Based on trust, not rules-lawyering Driven by use, not representation Grounded in solidarity, not status
Refuse the “leader class”, just because someone has a title, a grant, or a #dotcons following, doesn’t mean they speak for us. Call out the unaccountable influence. Politely or not. Let’s not let careerists write our futures.:

The Fediverse path could be the most important #openweb reboot of the commons of this decade. But it will only be that if we keep it rooted in social power, not polished #PR and #NGO mess. We don’t need new kings. We need more gardeners, to work together to compost the piles of #techshit and keep the space open and safe.

I think when our #fahernistas say to us “what have we done, please be nice to us, you’re not welcoming.” We need to reply: Am happy to be nice #KISS, just stop being a prat in this space please.

It’s really simple, please stop being (an often nasty) prat.

The Mess We Make (Again… and again)

Getting through this era of collapse with anything humane intact

The discussions on sovereignty at #NGIForum2025 make me wonder: what year are we in? It’s as if we’re rebooting grassroots conversations we’ve had for decades – but without the mess, memory, or movement that gave them meaning in the first place.

A breath of clarity came from @renchap, who said it plainly:

We need to focus our efforts on funding and supporting public value network infrastructure… THAT CANNOT BE BOUGHT. 💪

Absolutely. If that idea resonates with you, try starting with the #4opens – a pragmatic path to build tech with real accountability and openness. It’s not a utopia, it’s a filter designed to push out 95% of the #techshit we’re constantly drowning in. The rest? That’s the work: compromise, community, governance.

For those curious about mapping this stuff, I appreciate the attempt to formalize governance components of digital commons here: https://commons.mattischneider.fr/2-constituants It’s useful, but my take? Still not messy enough to reflect how real-world horizontal projects actually work. As the site rightly says:

“If you already have experience in operating commons, you or your organisation will probably have specific practices that are more appropriate to your context.”

Exactly, why context matters, and why real commons need trust-based governance, not just metrics and diagrams. Let’s remember:

Tools are only useful if people use them.
And that’s our real problem right now.

Take this audience question as a clear example: What should we do when a US company acquires an EU one – like Cisco buying Slido? It hits the core issue:

Centralized, vertical control is always the endgame of VC funding and the mainstream tech stack.

What’s the mainstream response? Push more AI. Push more “innovation.” Push more #stupidindividualism. This story is heavily funded and constantly amplified. Why? Because it keeps us distracted, divided, and demobilized. We need to compost this garbage.

Let’s stop pretending #opensource is the goal. It’s only useful if it lives in common infrastructure, owned and governed collectively, with embedded solidarity, not slogans. Yes, someone pointed out that:

"Open source licensing permits continued operation of the software with an EU provider."

That’s technically true, but in practice, how many such transitions actually happen? How many of these tools become hollowed-out ghost projects after the buyout? We need the EU to fund #4opens #FOSS and commons-native projects directly, not startups chasing exit strategies.

And yes, I’ll be blunt here:

There’s likely a whole class of people who should be prosecuted for fraud.

Because the current “innovation” circuit is knowingly wasting public money on private gain under “our” banner of openness. It’s a con. A parasitic class living off the #countercultures they parasitise. So let’s call this out, not to “disrupt” for disruption’s sake, but to open up space for what actually matters:

Native projects with shared roots in code, care, and community.
Activism that isn’t tacked on for #PR, but central to the infrastructure itself.
Horizontal governance that embraces mess, rather than paving over it.

We don’t need more products, we don’t need more platforms, we don’t need more panels pushing safe #neoliberal “common sense.” What we do need is to build and protect infrastructure that can’t be bought, captured, or silenced. Because that’s the only way we’re getting through this era of collapse with anything humane intact.

#NGIForum #NGIForum25 #4opens #OMN #openweb #techshit #commonsnotplatforms #mutualaid #FOSS #trustnotcontrol #liberalcapture #activismtech #geekproblem

Oxford: Going with The Flow

A call-out for collective tech with teeth

It’s important to be honest about the landscape we’re working in. Just about every so-called “alternative tech” or #opensocialweb event – especially those run under the #NGO banner – is riddled with institutional parasites. They talk a big game about ethics, governance, and decentralisation, but their main role is to capture energy, not release it. The value in these spaces is minimal, maybe a few decent corridor chats, but structurally, they serve the status quo.

What we’re seeing is an attempt to #mainstream change by reshaping it into something more passive and marketable. It’s branding, not building. It’s funding cycles, not freedom. And people are so used to the #feudalism of current #FOSS governance models, full of gatekeepers, toxic meritocracy, and internalised hierarchy, that they don’t see the need to move past this. They double down instead, its just #blocking masked as principled caution.

That’s why the #OGB project (Open Governance Body) takes a radically different approach: build it permissionless and let it loose. No waiting for gatekeepers, no begging for funding, no asking nicely. Just making space for people to actually do the thing – together, in the open. If it works, people will come. If not, we try something else. But we stop wasting energy on the #mainstreaming rituals.

The key is to recognise that there’s a different and much larger group of people, beyond the usual suspects, who can be empowered by tech if the structures are simple, human, and social enough. People who want to work together, share power, and build resilience, not just ship code. Yes, the tools need to exist, the ideas already exist, what’s been missing is a path that doesn’t instantly collapse into control.

That’s why #OGB is a #KISS project, it’s not about perfection. It’s about functioning enough to seed community processes that can grow over time. Something you can pick up and use, rather than argue about forever in a GitHub issue or a grant proposal.

Let’s be real, people are up shit creek without a paddle right now. And most of what’s presented to them as “solutions” are just more mess dressed up in new UX. If we want people to find different ways out, we have to build different places to look. That means creating tech ecosystems rooted in social trust, creativity, and actual autonomy, not more extractive platforms or performative NGOs.

We also need to deal with the deeper issue of apathy and Laissez-faire fatalism. People feel the system’s broken but don’t believe it can be changed. They’ve internalised the idea that trying is pointless. So we need to design structures that take this into account. Systems that don’t rely on constant enthusiasm or perfect participation. That hold space through thick and thin, for the long term.

This is where there’s real space for creativity and care, not just in what we build, but in how we build it, and who we build it with. Not self-promoting conferences, not glossy decks, but compost piles and messy gardens, things that live, change, and root themselves in everyday needs.

The #OGB project is just one shovel. But there are others. Pick one up. The ground’s ready.

Telegram messaging app is dieing

Telegram partnering with Elon’s #AI to distribute #Grok inside chats is a clear line crossed. This matters because private data ≠ training fodder, bringing Grok (or any #LLM) into messaging apps opens the door to pervasive data harvesting and normalization of surveillance.

This is an example of platform drift: Telegram was always sketchy (proprietary, central control, opaque funding), but this is active betrayal of its user base, especially those in repressive regions who relied on it.

Any #LLM like Grok in chats = always-on observer: Even if “optional,” it becomes a trojan horse for ambient monitoring and a normalization vector for AI-injected communication.

“Would be better if we had not spent 20 years building our lives and societies around them first.”

That’s the #openweb lesson in a sentence, that the #dotcons will kill themselves. This is what we mean by “use and abuse” of these platforms which have been driven by centralization, adtech, and data extraction, that they inevitably destroy the trust that made them popular. It’s entropy baked into their #DNA. As Doctorow calls this #enshitification, the tragedy is how much time, emotion, and culture we invested in them – only to have to scramble for alternatives once they inevitably betray us.

What to do now, first step, remove data from your account then delete telegram app, not just for principle, but for your own safety. Move to alternatives – #Signal for encrypted, centralized messaging (trusted but closed server). There are other more #geekproblem options in the #FOSS world but like #XMPP, #RetroShare, or good old email+GPG can work too, but they can be isolating, so stick to #signal if you’re at all #mainstreaming.

Then the second step, build parallel #4opens paths by supporting and develop alt infrastructure like the #Fediverse (Mastodon, Lemmy, etc.), #OMN (Open Media Network – decentralized media), XMPP and #p2p-first protocols, #DAT/#Hypercore, #IPFS, or #Nostr etc.

Yeah, things will get worse before they get better, what we’re seeing now is the terminal phase of the #dotcons era. These companies are devouring themselves and will eventually collapse under the weight of their contradictions. The question is, will we have built anything to replace them?

If not, authoritarian tech (like Elon’s empire) fills the void. That’s why we rebuild the “native” #openweb, even if it’s slow, messy, and underground. That’s why projects like #OMN and #Fediverse matter. If you’re reading this, you’re early to the rebuild, welcome, let’s do better this time.

Bridging alt and mainstreaming: A note on the shape of resistance

There’s a nice post by Elena Rossini’s, “This is what resistance to the digital coup looks like.” she is commitment to the #Fediverse, #FOSS tools, and open publishing solutions, and her critique of #VC-funded platforms like #Substack and #Bluesky is needed. At the same time, it’s worth pausing to reflect on how we talk about these things, particularly when we’re speaking to an emerging audience, still navigating the gap between centralized tech and more native, grassroots tools. Because while we do need clarity, we also need care. Otherwise, we risk turning signal into noise.

Rossini’s article is a good example of how alternative infrastructure begins to reach broader consciousness. Many of the platforms she champions – Ghost, Beehiiv, and even certain curated Mastodon experiences – fall within or adjacent to the broad #4opens networks. They are a part of the solution. But they also carry baggage. Some are corporate-lite. Some depend on foundation funding. Some straddle a line between truly open and VC-sanitized.

This isn’t a problem per se, but it’s important to be transparent about it, many of us in the radical grassroots space, nurturing compost heaps of alternative media, peer publishing, and federated community infrastructure – have seen what happens when clarity is lost. The #NGO-ization of resistance. The capture of the #openweb by polite #PR. The story gets smoothed out, the risk disappears, and the power we need to shift change and challenge can simply be adapted and absorbed.

Let’s name the agendas, kindly. We’re not calling anyone out, quite the opposite, this is a call in. A reminder that it’s polite and politically grounded to acknowledge the agenda and position of the tools we use, even more so the ones we promote. Are they native to the grassroots? Are they part of a transitional bridge? Are they compromised in some ways?

Rossini’s argument – that using Substack and Bluesky while denouncing Big Tech sends a mixed message – is fair. But the same critique could be gently extended to Ghost and Beehiiv, too. These aren’t immune from #mainstreaming pressures. If we want to build a truly alternative infrastructure, we have to be honest about what’s native, what’s transitional, and what’s being branded as “alternative” without any roots in the alt.

The #4opens as compass, is a tool that helps us make these distinctions: open source, open data, open process, and open standards. It’s not a purity test, nothing ever should be, but it gives us a compass. A way to orient ourselves as we navigate the mess. A platform might look open because it feels different from Big Tech. But if it lacks open process, if its governance is closed or opaque, then it’s not truly part of the alt path. If it uses open source code but locks users into proprietary hosting or hidden metrics, that’s worth noteing too.

This doesn’t mean we throw out every tool that doesn’t tick all four boxes. It means we contextualize. At best, we practice a kind of digital literacy that includes politics, power, and history, not just #UX user experience. Clarity is compost, Rossini’s voice is part of a broader chorus rising in defence of a better “native” web. That’s good news, but let’s make sure that as more people join this space, we compost the confusion, not spread more of it. Some things we might use to balance this good practice:

Choosing native language when we can (use “open publishing” or “independent Fediverse platforms” rather than brand names as default). #openweb is a powerful statement in itself as it contrasts to #closedweb.
Naming the agendas behind the platforms we use or promote.
Valuing bridges, but not confusing them for destinations.
Practicing digital humility, so we can learn without defensiveness.

On the current path there’s little clarity to begin with, let’s help each other work through the compost, with bare feet and open minds, toward something truly rooted in the commons. And yes this will mean dirty feet and hands 🙂

#TED – A Community of Delusions

Scaling federated networks and codebases: A human-centred balance

To put this into a social path, scaling is a double-edged sword – it can be both good and bad, depending on how it’s done.

Good, because when things scale well, people don’t have to worry, systems run smoothly, communities thrive, and services become accessible.
Bad, because the strength of a healthy network lies in staying small-scale, transparent, and human. The moment something becomes too big, it starts to lose the relational dynamics that gave it value in the first place.

So, how do we balance this? The idea is that codebases and networks need to scale just enough, not infinitely, but to the point where they can support a human-scale community. After that point, it’s not only acceptable but preferable if they start to strain or fail under pressure. That friction is a feature, not a bug, it nudges people to move to federate rather than stay and centralize.

What does “enough” mean? “Enough” isn’t a fixed number, but a pattern, a community of a few hundred to a few thousand accounts. Of these, perhaps 15–25% are very active, contributing most of the content, moderation, and tagging. This scale is large enough for rich conversation and diverse activity, but still small enough for shared context and trust, low moderation overhead, organic relationships and accountability. Once a community grows beyond this range, organic moderation and social cohesion break down, leading to noise, exploitation, or the #mainstreaming call for reliance on impersonal algorithmic solutions, the very things OMN path wants to avoid.

Federation is the healthy scaling path we need to take. Rather than “scaling up” in a single, monolithic instance, the sustainable way is to scale, is out through federation. That is, build many interconnected human-scale communities, each managing itself. Using shared protocols, metadata flows, and trust tagging to connect communities meaningfully. Respect local autonomy, while allowing content, trust, and culture to flow between nodes. This model mirrors healthy ecosystems, small habitats working together rather than being swallowed by a single “concrete” system.

Why this matters for #FOSS codebases? Software should be designed to reflect and reinforce this human-scale path. Keeping systems lightweight and maintainable for small teams, to enable interoperability and modular design, so communities can fork, adapt, or remix code to suit local needs. It’s core to this path to accept that codebases don’t need to scale infinitely, they only need to scale enough to support the next healthy layer of federation.

The right question isn’t “Can this scale to millions?” but “Can this be easily cloned, modified, and federated by others?” By embracing “ENOUGH” as a limit and a guide, we ensure our networks stay rooted in trust, flexible in form, and resilient by design. Growth becomes a matter of spreading seeds, not building towers.

Don’t be a prat, please try and recognize the roots of issues

Horizontal people always get fucked over by vertical people. This is normal, why? Because horizontals give away power to build social fabric, while verticals hoard and concentrate power to extract and dominate. Every. Single. Time.

And the only thing that makes horizontals work, in the face of such mess making, is shared worldview, which we currently lack. Instead, we’ve got swarms of #stupidindividualism, where everyone thinks they’re the centre of the universe, interpreting everything as if their personal “common sense” whims are political strategy. And then, surprise! We keep getting steam rolled.

An example, let’s bring in the rot of #postmodernism, the #pomo guy proudly clams that “Ah, but classification requires a classifier!” This is what #postmodernism does to your brain. It unplugs you from reality while pretending it’s insight. It’s true that classifiers precede categories linguistically. But the material world precedes both. Rocks didn’t need a PhD to be granite.

This kind of derangement isn’t just stupid, it’s systemically useful to the #deathcult. Because if you believe that value only exists if humans assign it, then a tree has no value unless it can be turned into toilet paper. A whale has no value unless it can be monetized or aestheticized. Nature becomes valueless. And so it’s obliterated.

Meanwhile, people in the #fediverse are still pretending codebases matter more than people. No. The value of the Fediverse is in the humans running the instances and inhabiting them. Not the bloody Git repos. Without people, the code is just more maths.

On this #FOSS path, don’t be a prat. Recognize the root issue:

The #geekproblem
The collapse of shared worldview
The enshrinement of individual narcissism over collective meaning
The complete #deathcult worship of self pushed by our #nastyfew

Let’s compost this mess. #OMN #OGB #4opens #indymediaback

Can people engage with the #4opens process?

The #4opens is a completely obverse social restating of the #FOSS development model — but with a critical edition: The return of #openprocess, something we’ve lost over the last 10 years due to the shift from public email archives to our reliance on encrypted chat.

With this in mind, what is still #blocking the #openweb reboot? One thing I’ve learned from the last five years of this reboot is this: The #geekproblem is inadequate for the scale of change and challenge we face. Currently, the #geekproblem is HARD #blocking, obstructing both, funding, and tech direction. Think: #NLNet, #NGIZero, #SummerOfProtocols, #InvestInOpen — they say the right words, have potential, but are actually #blindly caught in a loop of the same limiting #blocking patterns.

This is why we need activism, this can be #spiky, sometimes all it takes Is a rock or a stick. Think of Greek shepherd dogs in the mountains — they come at you like wolves. But just bending down to pick up a rock or stick? They back off. No violence. Just clarity and intention. Think of the #4opens like this when facing #mainstreaming, suddenly, it starts to make sense.

Nuts and nutters, Yes — you’re right, this can sound like blinded ideology. But remember: Humans are meaning-creating creatures. One word for that is ideology — there are others: https://en.wikipedia.org/wiki/Synonym

If we can compost this mess, that’s a big if, will the #OMN Work? Simple answer: Yes.
Complex answer: No. My answer to that riddle? We find the complex by implementing the simple. That’s the #KISS principle in action. Walk the simple path, we discover our way through the complex path by implementing and walking the simple one #KISS.

#Mainstreaming = #Deathcult Worship

Most mainstream agendas are pointless. Why? Because they’re built on “common sense” — Which today often just means #deathcult worship. Something to keep in mind… whenever you’re doing anything that matters. Hope this slight poetry piece helps. One thing I keep saying, please don’t be a prat, thanks.

Rebooting the #openweb in a good way

The #Fediverse exists, and more than that, it’s alive and kicking. Sure, it might be a messy, chaotic, a bit fragmented, and yes, still niche. But let’s not underplay it, this is the healthiest corners of the internet we’ve got. Tens of million accounts, hundreds of thousands active people, and some are sometimes talking about how we build our digital spaces from the bottom up.

Yep, there are the cat videos, the #fluffys and the #spikys. But also an in-group debate is bubbling away about who speaks for the Fediverse? What defines it? Is it the standard #ActivityPub that binds us only technically? Or is the value in the community that’s formed it, the living web of relationships, servers, instances, and admins making this work day-in-day-out? Truth is, it’s both. #activitypub without community is just code. Community without #activitypub is just another silo waiting to collapse. They are not the same, but they are inseparable. To build something real, we need to nurture both the tech and the people.

What works in the #Fediverse is decentralisation with purpose, it works because it resists centralisation. It gives people choices, want a cat picture, instance? A political instance? A hyper-local or themed space? You install and build it, and people might come. This is #DIY grassroots digital culture in motion. Standards support this growth, #ActivityPub, like #RSS before, may not be perfect, but it’s open, extensible, and functional. It allows platforms and networks to talk to one another. This is a real #4opens foundation for collaboration, not control. That’s the kind of architecture we need in the #openweb reboot.

What doesn’t currently work is the over-reliance on hard blocking as a solution, with the common approach to problems is too often to block, users, instances, entire classes of servers like the #dotcons. While this kinda makes sense in the short term, it’s not a long-term strategy. It’s the digital equivalent of putting your head in the sand. You’re not solving the problem, you’re just not looking at it any more. This has the strong tendency to feed the “Cave Mentality” where some corners of the Fediverse are in defensive mode, retreating into smaller and smaller bubbles, avoiding engagement, trying to build perfection behind walls. But hiding from the mess doesn’t clean it up. If the #openweb becomes too closed, it dies from within. Openness is a value, not just a setting.

This is in part due to a lack of collective strategy, yes we’ve got the passion. We’ve got the tools. What we’re missing is a shared direction. The is currently too much reinventing the wheel, too many forks without purpose, not enough joining the dots. A thousand flowers bloom, but the garden needs tending.

#nothingnew is a basic tool about this, then there is the use of the #4opens, we need to make the #Fediverse and every layer of the #openweb, measurably open. That means: Open Data: accessible and remixable content. Open Source: transparent and forkable codebases. Open Standards: like #ActivityPub, that let different platforms interconnect. Open Process: decision-making in public, with participation and accountability.

The #4opens framework is a guide, not to perfection, but to direction. It’s a map toward trust, decentralisation, and sustainability. On this path, we need to build culture, not only code. Healthy communities don’t just appear, they’re built. Instead of building tech features, let’s also build social norms. Encourage, informative, welcome messages, transparent moderation, shared spaces for discussion. Moderation and admin is labour, support it, reward it and most importantly decentralise it.

To build community, don’t shy away from engagement. It’s tempting to block and move on. But sometimes, the hard work is worth it, call things out, talk things through, escalate when needed, but don’t disengage by default. We need active participation, not digital ghost towns. If we want the #Fediverse to grow, we need to build bridges, not walls. Let’s weave human trust networks to grow spaces that are porous, where new people can enter, learn, contribute, and stay. This is the work of social federation, which is just as important as technical federation.

There is a bigger picture if you are interested and are motivated to look, the #OMN, Open Media Network project is a vision and collective path for this kind of social architecture. It’s a federated network of media hubs, rooted in community, powered by open standards, and guided by human trust. It doesn’t seek control, it offers #KISS tools to build trust, add value, and create meaningful networks from the ground up. On this “native” path, rather than rejecting “bad actors” by exclusion, we build systems that surface good actors through collective tagging, trusted feeds, and editorial flows. Moderation becomes a feature, not a bug.

Final thought, let’s not repeat the mistakes of the past. The last 20 years of alt-tech is a graveyard of well-meaning platforms that failed because they forgot one thing, the humans. The #geekproblem has been building “perfect” systems with no one in them. That’s not the #openweb we want. We need less abstraction, more interaction. Less control, more cooperation. And above all, we need to recognise that openness requires work, but it also delivers freedom. So yes, the Fediverse exists. It’s healthy. But it can and needs to be more. Let’s stop hiding. Let’s start building. Together.

#Fediverse #OMN #4opens #OpenWeb #IndymediaBack #SocialTechnology #AltTech #Decentralisation #FOSS #MakeHistory #ActivityPub #OGB #SocialCoding

What software do social justice activists need?

First we need to look at the core problem for the last 20 years has been that most activists were locked into #dotcons (corporate social media silos) because open alternatives were either too difficult to use, lack network effects, or fail to meet their practical needs. With the current reboot of the #openweb with the #fedivers based on #ActivityPub we have already taken a step away from this mess.

From my experience, here’s what’s needed from a software development perspective to break out of this mess. Open & accessible publishing networks. Activists need easy ways to publish and share information outside corporate-controlled platforms. Right now, #Fediverse is a first step, tools like #Mastodon and #PeerTube exist, but they are still largely copies of centralized platforms rather than native alternatives that work for any working grassroots media.

To take the second step in alt tech we need a native decentralized, trust-based publishing network (#OMN is the example I am working on) Bridging tools to syndicate content between #dotcons and open platforms. Better “unbranded” discovery tools for surfacing trusted grassroots content (think of a federated search engine that’s not controlled by Google)

The third step of secure yet open communication, is already mostly in place. Activists do need to secure yet transparent communication tools that balance privacy with accessibility. Right now, many are stuck using encrypted corporate platforms like #WhatsApp and #Telegram, which create spy silos and exclude people who purposely don’t have the apps. Projects like #Signal and XMPP chat kinda work in this space, so this is not a strong social tech focus, but is a social issue to work on getting people to use the tools.

Finally, the type of project we do need #indymediaback, #makeinghistory, #OGB and the base #OMN coding. There is a continuing need for resilient infrastructure, hosting and sysadmin alongside sustainable funding tools for activists’ websites, blogs, and tools. Currently, these tools often get taken down due to coordinated attacks and lack of resources. On the more dev side of this path, hybrid peer-to-peer hosting solutions (so sites can stay online even under attack) could be useful to bridge current client server tools.

There’s a roadmap, but the problem is developer focus and funding. If you’re serious about helping, check out the stalled dev work on https://unite.openworlds.info and see how it can be set in motion, please. If you’re a dev who wants to make a real impact, this is a good place to look.

The issue, we need to work more on, with #FOSS tech development, the failure of many #FOSS projects, is a failure to move from theory to practice. The issue is that developers work in isolation, disconnected from grassroots needs, and get lost in perfectionism rather than delivering functional prototypes.

The #geekproblem dominates, with coders prioritize control, abstract debates, and self-contained experiments over practical, usable tools for real-world communities. This is why projects stall: they are not built with activists in mind. Meanwhile, centralized platforms continue to consolidate power, because they offer simple, accessible, and functional solutions, despite their deep and nasty flaws.

To break this cycle, we need:

Practical iteration, build rough, working solutions rather than endless theorizing.
#4opens culture, embrace open process, standards, and real collaboration.
Bridging solutions, tech that activists can actually use, not just developer-driven experiments.
Funding models beyond #NGO traps, so projects remain independent and sustainable.

The fight for the #openweb is not only about resisting #dotcons but creating alternatives people can and will use. Can we move beyond abstraction and actually make history?

Please.