Rise and Fall of Grassroots #OpenWeb

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 #fashionistas are coming https://yewtu.be/embed/u_Lxkt50xOg? It’s time to become more real before this inflow swamp our “native” reboot, consume it and shit it out as more mess. It’s time to act, please, feel free to report these web posts, thanks.

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?

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 for grassroots 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 is 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 and increasingly gate kept #NGO commercial interests are then 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 anymore – 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)

NGIFORUM2025 is timidly touching sense

It’s good to see events like #NGIFORUM2025 as it’s trying to be on the path of the #Fediverse and the wider #openweb reboot which are real forces for social good, messy, hopeful, and grounded in decades of grassroots digital culture, which we do need to support. BUT we also need to speak honestly, as these spaces are not healthy by default.

Too often, they are co-opted by #NGO and institutional actors who bring with them a dangerous kind of “common sense”, what I’ve long described as the parasite class. We see this clearly at #NGIFORUM and similar #NGO events. Despite the energy and good intentions, the dominant framing is stuck in a narrow, #neoliberal logic:

More funding for shiny #techfixes.
Token gestures to social issues.
Endless discussion about scalability, compliance, branding, and “the market.”
Panels where “on-topic” needs reality-checking and “off-topic” is often the path to sense.

This is not the #openweb native path, and what we need is more shovels and composting, to grow the real grassroots native paths, with open projects from the messy soil of lived social experience. Not more polished “innovation theatre.” And crucially: we need to bring activism back into these spaces – not as token #fashernista crap, but as lived, rooted practice. We need to embed activist tech into the core of these events, not leave it in the hallway as is the current norm.

Because let’s be honest, too much of what’s being showcased is just more #techshit to compost. Take the role of NGI funding (Next Generation Internet): It could be a powerful tool to fund the future of a people-powered web. But right now? It’s structured to reward isolated hard tech with narrow deliverables, and punish anything messy, social, or disruptive. That’s upside-down.

The development side of open-source should be anti-commercial – in its process, not necessarily in its usage. That means public funding should support the huge social layer that keeps FOSS and #openweb projects alive:

Community organising.
UX design from lived needs, not compliance charts.
Onboarding and trust-building.
Accessibility work.
Documenting process for reuse and remix.

But currently these parts are entirely unfunded, and that is pushing us into the arms of the parasite class’s of all types. We are walking backward into the future, again, projects without people, users, and support are dead projects. No matter how elegant the codebase is.

One thing that the event brings up is that we need to shift policy, national governments and #EU to actively intervene in the monopolies running the current internet. Both mobile and fixed-line networks need to be opened up to allow for grassroots, peer-to-peer, and local hosting paths to flourish. The current centralised infrastructure is a block to the native #openweb, and we can’t “build better” on broken foundations.

The also needs to be a cultural shift, to unblock the #geekproblem. This is not a call-out – it’s a call-in. The feedback is there, i’ve personally been working on this issue for over a decade, what we’ve seen is a cycle: Working in a small way… failing in a big way… repeating.

It’s not personal, it is structural. And we can do better, if we compost the fear of doing things differently. A practical example, we need more points that are currently deemed “off-topic.”
Because what’s “on-topic” in these spaces is just branding and polite theatre. And that’s exactly how the #dotcons rose to dominance in the first place.

We are at risk of simply recreating their culture in softer tones. Let’s not do that. Let’s take a breath and reflect on what we’re actually building, it’s not a rhetorical question. This is not abstract.

Because if we keep defaulting to #neoliberal “common sense,” if we ignore the reality of climate collapse, digital authoritarianism, and infrastructure lock-in, then we’re just dancing around the edges of a very real #deathcult.

Let’s do the real work, let’s dig, plant, compost, and build trust. Let’s reclaim the tools and shape the #openweb around care, not control. Because anything less? It is just another empty panel on a sinking ship.

“All authority is quite degrading. It degrades those who exercise it, and degrades those over whom it is exercised.”
— Oscar Wilde

#Fediverse #OMN #4opens #commonsnotplatforms #mutualaid #socialroots #trustnotcontrol #KISS #NGIFORUM2025 #NGIforum #nlnet

It’s becoming a problem

It’s becoming a problem. When people start asking, “Is @_elena the first genuine superstar of the Fediverse?” – we should all pause. This isn’t idle praise, it’s the reproduction of celebrity culture, liberal imperialism, and vertical hierarchy in a space that explicitly set out to reject those structures.

Have you ever thought – just for a moment – that this might be the completely WRONG path for a horizontal network like the #Fediverse? Yes, we need mess. Yes, we need experimentation. But this? This is #mainstreaming in its most seductive form, a soft power grab, hiding behind friendly faces and growing marketing gloss.

Both #pubconf2025 and #fediforum, and the people who attend them, are becoming a showroom for this liberal capture, promoting star-making and platforming over community process and open governance. It’s a mirror of the conference-industrial complex, repackaged for the #dotcons-weary.

We’ve seen this before: #NGOs turned movements into funding funnels. Influencers replaced organizers. Polite panels replaced fourm-level solidarity. It’s been happening here the last few years. But we do need to remember, the Fediverse isn’t a playground for fame, it’s a commons, to distribute power – not concentrate it. We don’t need to unthinkingly push people down the superstars’ path. We need peers, comrades, care, conflict resolution, and actual shared infrastructure.

So let’s be honest, if you’re pushing “the first superstar of the Fediverse,” you’re not pushing decentralization, you’re pushing brand culture, mainstreaming logic, and attention economies repackaged for liberal feels.

That’s not radical. That’s not native, it’s not what we came here to build. Let’s compost this celebrity logic before it roots too deep. Let’s stay messy, collaborative, and resist the temptation to crown anyone. Because if we don’t? We’re just rebuilding the same old pyramids – with slightly alt avatars.

Let’s look at the more #mainstreaming #dotcons path. The not-so-subtle message we need to remember on social media: Dictators hate to be ignored. Especially on their “special days” – birthdays, elections, court appearances, or orchestrated spectacles. These moments are designed to dominate the media cycle and, by extension, the social media algorithms.

They thrive on attention, and whether that attention is praise or outrage, it fuels their visibility and power. Here’s the social tech they exploit:

When you doomscroll their face, the algorithm sees interest.
When you post disgust, the algorithm sees engagement.
When you argue with trolls, you’re boosting the signal of the original post.
When you call them names, it still centres them.

That’s the #dotcons feedback loop, engagement is king, and dictators know how to play that game. Let’s break this circle, on these days, do something different:

Share stories of local mutual aid.
Link to historical context that exposes the long game of these power grabs.
Boost voices that decentralize attention, not concentrate it.
Post about books, direct action, food sovereignty, climate organizing, and tools for collective autonomy.
Highlight grassroots projects like #OMN, which are building sustainable, decentralized alternatives.

This is how we take the air out of #mainstreaming fires. Starve the algorithm and feed the resistance. Focus on things that actually matter, remember: not engaging is a strategy. Ignore the circus. Build the commons.

#KISS

Why does any of this matter?

Because power matters, and power is never given – it’s taken, built, and at its best, shared. That’s why we care. That’s why the #Fediverse matters.

Let’s rewind: Private property wasn’t born from reason or consensus. It came from someone with a club drawing a line in the sand and saying:

“Cross this, and I’ll kill you.”

That’s the origin of power in the current #mainstreaming paths – violence, enclosure, and exclusion. This is not the foundation of the #Fediverse.

The Fediverse flows from a different source, built in open, social webs, where the lines we draw are “blowing in the wind.” Yes, a lot of people don’t get this. That’s why they try to jam it back into old models: branding, control, platforms, “governance,” and “best practices.” They want order. They want power they can hold.

But here’s the thing, There is such a thing as society, and we need to build tools that reflect this, not deny it. The beauty, and challenge, of the #Fediverse is that there is no central governance.
And that’s a good thing. Because it means we aren’t trapped by legacy systems of control. We don’t have to fit into the broken economies and top-down paths that dominate the “real” outside world.

The Fediverse was born from the “cats” of libertarianism and anarchism (without the [O]). And in this space, we have the radical opportunity to build different, native paths, based in trust, mutual aid, and the #4opens. But to keep building this, we have to compost the mess pushing: People pushing “common sense” corporate-style governance are part of the problem, they want to tame the wild, they want hierarchy where there should be networks, they want control where we need flow.

To be native to the Fediverse, we have to stop importing “common sense” control systems. Instead, we must use code – and culture – to build native #openweb society. Tools that empower. Processes that are messy, open, federated, and yes, hard to define. Organizing for community empowerment need to embed anti “common sense” in the same way the Fediverse is anti-enclosure. Because if we forget this… We don’t build a better web, we just recreate the old one with new colours. Let’s not just repeat history, let’s not draw new hard lines in the sand with the same threat of old clubs. A step away from this is to build bridges, not borders.

It would be helpful to talk about the industrial-scale air freshener being sprayed to mask the stench of collapse. An example, while Gaza burns and genocide unfolds in real time, too many on the soft left are busy sniffing their own ideological mess.

“Oh, but they used a plane once…”

“Oh, that project isn’t perfect, so let’s not support it at all…”

“Oh, their anti-Nazi message is just a header image. That’s clearly useless propaganda…”

This is troll logic. This is #psyop brainrot, it’s weaponized idealism used to undermine action.

“Sure, they’re doing good - but not perfect. So discredit, disengage, demoralize.”

It’s the tactic troll farms use on the #dotcons to feed manipulative, because it appeals to insecure egos and a culture soaked in #stupidindividualism, where the look of moral “purity” is more important than building power, solidarity, or impact.

And too many fall for it, because they don’t see it for what it is: A feedback loop that leads nowhere. A stalling tactic. A demobilizer. It’s not accidental, it’s designed to stop us acting.
It’s strategic passivity masquerading as moral high ground.

“Don’t link to that, it’s not flawless.”
“Don’t share that resource, the font is ugly.”
“Don’t support that campaign, they once took a selfie on a plane.”

Are you serious? While people are being murdered by states, you’re sniffing out aesthetic imperfections? Here’s #KISS:

Nobody wins by demanding perfection.

Nobody builds movements by tearing down every action.

Nobody helps anyone by blocking solidarity and smearing efforts.

We need to focus attention, not fragment it. We need to act in coalitions, not purity circles, we need to smell the rot, not cover it with ideological air freshener. Because this isn’t a game, it is about #powerpolatics, and how it’s wielded or lost. And while you troll your own side for imaginary infractions, the fascists are laughing – and organizing.

Please, please try and STOP being a prat, thanks.

When we block thinking, it’s pratish #dotcons behaviour

We’re living through a cultural shift. The #Fediverse, the #openweb, and grassroots tech projects like #OMN were born to challenge the values of the corporate web, not to reproduce them.
But what are we doing instead? We’re seeing people attacked simply for linking to context and history. Linking is native to the open web. Attacking people for linking? That’s native to #dotcons. Take this example: When we post links to hamishcampbell.com, a site with over 20 years of radical media history, no tracking, no ads, no monetization, some people respond with hostility. Instead of engaging, they block, slur, and accuse.

Why? Because the link was shared on a #dotcons platform? Because it challenges their gatekeeping norms? It’s absurd. The truth is simple: #KISS – Keep It Simple, Stupid.
This site is part of a long history of grassroots movements. No one is selling anything. No one is farming clicks. Yet bitter, shrinking cliques still push to block it. That kind of behaviour? It’s at best compost – something to shovel through as we grow better soil.

If you don’t get why this matters, start here: Why linking on the open web matters. Not linking is a dangerous cultural regression. The act of linking is a kind of mutual aid: it’s memory, solidarity, and a way to keep the commons visible. When you attack people for linking, you’re actively damaging the infrastructure we need to resist the #deathcult of #neoliberal capitalism.

Here’s another angle worth reading: CrimethInc on mutual aid vs. charity. Mutual aid is not charity. Linking is not self-promotion. These are fundamental ideas. The #Fediverse is built on these values, it thrives when people share freely. But when we import #blocking behaviour and #dotcons paranoia, we replace trust with fear. We end up with closed circles, bad vibes, and petty gatekeeping.

This is not how we build shared infrastructure. This is not how we win. So please: Let’s stop slurring people for sharing knowledge. Let’s stop policing links with fear. Let’s link more, think more, and rebuild grassroots, networked culture rooted in trust, not control. Because without this? We’re just another branded platform, with nicer avatars and the same old decay underneath.