Talking About the #geekproblem in Funding

Funding the #openweb is a political act, yet most funding decisions today are framed in technical terms only, dominated by what we call the #geekproblem – a worldview where infrastructure is king, user needs are secondary, and social context is largely ignored.

Let’s unpack this with real-world examples and look at how we keep falling into this trap, and what we could do to climb out. The call-out for funding is phrased in social language, to build privacy-preserving tools, improve the commons, empower communities, decentralize infrastructure. But the funded projects rarely reach or empower actual communities. This is the disconnect, a cultural blind spot that stems from the #geekproblem.

We need to fund the social layer, as a strong backend is necessary, nobody is saying otherwise. But it’s not sufficient, the #openweb is not failing because of lack of backends. It’s failing because almost nobody knows they exist, cares, or knows how to use them. Take ActivityPub, the protocol behind Mastodon and the #fediverse. It had existed in various forms for years, but it only took off because:

Mastodon made it social.

It had good UX for regular people.

There was media buzz and community-building.

It offered emotional utility — a real alternative to Twitter at the moment people needed it.

Without this social glue, ActivityPub would have been another elegant-but-abandoned standard. A backend sitting on a shelf, this is the lesson:

To have an #openweb because we need to fund the people and projects who do social UX, onboarding, design, documentation, evangelism, and community organizing.

We currently keep building plumbing and call it a house, we then blame people for not living in it, feeding the #dotcons. Here’s a bitter irony:

Funding backend tools with no regard for adoption pathways just helps #dotcons.

The corporate world happily scoops up open source backend work (including ActivityPub) and wraps it in slick UX, marketing, and control. That’s how:

Meta is building Threads with ActivityPub.

Google funds protocol work to feed proprietary services.

Microsoft contributes to open source, then wraps it in Azure services.

They have the social layer, #PR, onboarding, monetization, network effects, and we hand them the backend work for free. We build the roads, they put up the toll booths.

The Fediverse is not a collection of protocols, it’s not a stack of servers, it’s a culture – or it was. And that culture is in crisis:

Burnout among developers.

Fractured community governance.

Rising influence of #NGOs and foundations pushing vertical, institutional models.

Selling out to mainstreaming partnerships (ex: EU outreach, Threads integration).

Social stagnation as microblogging dominates over creativity, curation, and real collaboration.

There is still potential, a web of relationships, tools, and practices built on trust rather than control, but we are not funding that potential. We are, instead, funding more tools, more protocols, more #techchurn.

What’s the pat out of this mess? We need to rebalance, right now funding overwhelmingly goes toward:

Code (especially backend)

Security and cryptography

Infrastructure-level "innovation"

We need to start funding:

Onboarding, documentation, UX

Social features, not just tech protocols

Network-building between grassroots media and communities

Outreach that isn’t just evangelism, but relationship-building

Public education, not just developer conferences

Human infrastructure — the people doing the messy, unglamorous work of care and connection

Think about projects like: The Open Media Network (OMN) – which builds out real linking between alt-media producers using existing standards like RSS and ActivityPub. It’s boring tech, but socially radical. This project aren’t shiny, but it matters.

We cannot build future paths by pretending the problem is just technical. The #geekproblem is a cultural blindness, the belief that the social will magically emerge once the tech is “good enough.” It won’t.

If you want a flourishing #openweb, you need to fund the people with shovels — the ones doing the care work, building bridges, and holding space for non-geek communities.

Until we do that, the #openweb will remain a ghost town of beautiful ruins – and a free R&D lab for the next generation of #dotcons.

#NGI #NLnet #NGIzero

Why most #geekproblem software fails: Trust vs. control

Almost all of our #geekproblem software fails because it’s built with a mindset of control.

Control over users.
Control over systems.
Control over outcomes.

But all good societies, and all durable communities, are based on trust. When we ignore this, we don’t just write bad code, we produce #techshit that nobody uses, that burns out developers, and that confuses users. Then we start over… and call it “innovation.” That’s #techchurn.

Control-driven projects: Examples of failure

Diaspora
Touted as a Facebook alternative, it focused too much on cryptographic control and data silos — and forgot the social UX that makes people actually want to use social media. It never recovered from this early design flaw.

GNOME Online Accounts
Supposed to be a bridge between the desktop and online services. Instead, it became a privacy puzzle with unclear consent and broken trust. Control was enforced without social understanding.

Secure Scuttlebutt (SSB)
A radical peer-to-peer network, very promising. But became increasingly unusable due to overcomplicated trust mechanics and lack of simple social pathways for onboarding new users. The community stalled.

Matrix / Element
Still pushing forward, but has constant friction because it replicates many centralised “control” models in the name of “choice.” Powerful, yes. But still struggles with real decentralised trust outside geek bubbles.

🌱 Trust-Based Systems: What Works?

Fediverse / Mastodon
It works because it’s socially familiar and based on human trust over algorithmic control. You choose who to follow, what server you trust. And it grew because of this — not in spite of it.

Signal (Early Days)
Before turning more into a consumer app, Signal succeeded by focusing on trusted networks — your phonebook — and making end-to-end encryption invisible. It was about trust, not just security.

The real problem is in part to do it money and the funding of the wrong side of tech, in that most funding goes to things that feel safe:

Protocol development

Core backend infrastructure

“Governance” initiatives run by “neutral” NGOs

These are important up to a point, but this “safe” money ONLY reproduces the #geekproblem:

Building tech without communities

Tools without culture

Features without stories

When we do try to fund the social side, the interfaces, user onboarding, documentation, actual relationships, it too often gets handed to parasite #NGOs with no grassroots accountability. Just look at the endless pilot projects by digital rights NGOs that are abandoned 18 months later. Or the “governance frameworks” that never go anywhere. It’s a cycle of buzzwords over boots-on-the-ground.

The people with shovels, in a messy world, the only thing that might work is messy people with shovels, people who compost the shit, clean the broken tools, and patch the networks to keep things going.

These people are rarely funded.
They’re not “scalable.”
They don’t write grant-friendly proposals.
But without them, none of the tools work.

Who funds them?

A call to action: If we want an #openweb that survives the coming waves of #climatechaos and #mainstreaming sellouts… We need to fund trust, not control, to support social infrastructure, not just servers and specs, to back messy doers, not polished whitepapers. We need to talk about this, fund this, and build on this, or we’re just making more compost for the next #dotcons to grow from.

A conversation about money and the #openweb

#NLnet #NGI #NGIzero #EU #funding

A conversation about money and the #openweb

Let’s talk about the tension at the heart of the modern #openweb, and why so many grassroots builders and radical technologists find themselves on the outside looking in. Scene: A typical “open internet” conference in Europe. Excited NGO-funded attendee toots:

“Just booked my place for ePIC in Lille! My first Eurostar trip! It’s where I started 10 years ago with Mozilla. Time flies. #OpenBadges #VerifiableCredentials”

Me (a social tech outsider):

“These things are hopelessly expensive. To attend you have to worship the #deathcult. Hard to know what to do with these two-track approaches. Kinda can’t be #openweb if they’re locked behind temple walls.”

PS. It’s a metaphor. But not an empty one.

Two economies, two Internets, the #mainstreaming of the #openweb means that most so-called “open” events are inaccessible unless you:

Work for a #NGO, startup, or university with a travel budget

Have a career track aligned with #neoliberal frameworks

Can spend hundreds of pounds on accommodation, tickets, and travel

That’s not grassroots, not radical, not open – it’s branded openness for the networking class. The Reply:

“I think that’s a complicated way of saying you can’t afford to go?”

No, it’s not, it’s a social critique, and a common one from those of us who have spent decades building grassroots tech infrastructures and activist media, unpaid or underpaid, mostly ignored. It’s about asking: Who is the #openweb for, really?

Why this matters, when we raise issues like this, we’re not “being reply guys.” We’re making a point about the structural divides that are silencing and marginalising the very voices we need most in these spaces, the people actually building and defending the #openweb on the ground. You can’t build democratic tech by replicating elitist spaces and calling them “inclusive” just because the code is on GitHub. The pushback:

“You can’t live outside the mainstream, throw rocks at it, and complain when it doesn’t accommodate you.”

“I’ve never had a positive interaction with you. You wear that like a badge of honour. I’m muting you.”

Pause here, is this really the attitude we want? If you’re part of the #NGO world, if you have stable income and access to conference budgets, then you are in a position of power. When someone critiques that system, not you personally, but the structures you inhabit, and your reaction is to mute, dismiss, or mock them… something has gone wrong. This is exactly how we lose the #openweb. Not to tech giants, but to social silos within our own communities.

A different approach? Imagine this instead:

“You're right, many of these events are structurally exclusionary. I’ll raise this at the conference. How do you think we can bridge this divide without compromising either side?”

That’s the kind of solidarity we need, that’s how we stop #mainstreaming the death spiral, how we build together. If we want an #openweb that isn’t just another branded ladder for careerists, we have to defend the messy, painful, and vital presence of the grassroots, even when they come knocking without a conference pass.

Muting critique is easy, building bridges? That’s harder, but it’s the only thing worth doing right now.

#NLnet #NGI #NGIzero #EU #funding

Why most #geekproblem software fails: Trust vs. control

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

The wall of funding silence

In the sprouting landscape of #openweb infrastructure, it’s not just code that gets ignored, it’s the possibility of change itself. Projects like #makeinghistory, part of the wider Open Media Network (#OMN), aren’t asking for much. They’re not flashy. They’re not political in the #mainstreaming sense. They just quietly build the back-end tools that allow people to document their histories, publish from the grassroots, and hold space for the memory of struggle that shape our progressive liberalism. But that seems to be too much.

The wall of funding silence – We’ve submitted funding proposals – dozens over the years, to every channel supposedly set up to fund the #openweb non-mainstream side of tech. From #NLnet to #NGI, from “open futures” to the latest EU moonshots. Most of the time, the response is a polite no, a vague shrug, or silence.

Sometimes, we get honesty – “This kind of effort is very hard to seek grants for” or “I don’t have an obvious candidate for you.” What they don’t say is what’s really going on: The system does fund this kind of work, look at the bonfire fresco as an example, but only when it’s a shadow of the status quo.

There’s a path through this, if we’re honest about the rules of the game. One such route is the #makeinghistory project, a non-threatening, archive-based approach that doesn’t scream radical, but quietly lays the groundwork for deeper change. What funders may not realize (or perhaps they do) is that by supporting it, they also enable development on #indymediaback and the metadata “soup” back-ends of the OMN, the very infrastructure needed to reboot truly grassroots media.

It’s a shadow funding path. And yes, that might feel cynical. But if you’re unwilling to fund change directly, maybe you’ll fund the shadows of change. Sometimes the only way to sneak truth past the gatekeepers is through the side door.

We do need to get past this broken balance, the hard part is that many of these funders do think they’re doing good. And to be fair, they are, a little. But the balance is broken. That imbalance is invisible to most, especially those inside the comfort of stable institutions. When we push back, it looks like we’re hitting “good” people with little sticks. It’s messy, and it’s easy for them to just turn away. We get told to be grateful. To celebrate, the seedling being planted in the foreground, while bulldozers level the rest of the forest behind it.

Stick or Carrot? So what do we do? We talk about sticks and carrots. The truth is, our sticks are tiny, dwarfed by corporate lobbying, government inertia, and internal conservatism. The peaceful, hippy route changes nothing long-term, but conflict isn’t working either. We’re stuck in between, too radical for the boardroom, too polite for the barricades.

But here’s a thought: maybe it’s not about the size of the stick, but where we aim it. We’re not here to fight good people. We’re here to point out that a little good is not enough, not when the stakes are this high. If we don’t build space for change, it won’t happen. And if funders like #NLnet want to be the change they speak of, then they need to fund the infrastructure that makes it possible, even if it’s uncomfortable. Even if it’s messy. Even if it’s indirect…

What Now? We’ll give it a month. Then maybe we nudge a bit harder. But no shame, no blame. Just a call for balance, for trust, for a shift in what “doing good” really means.

The pushing of doomed projects

#OMN #makeinghistory #indymediaback #NGI #NLnet #NGIzero #openweb #4opens #deathcult #mainstreaming #funding #changechallenge

Composting the reboot funding

Dear Michiel,

At this point, it’s hard not to notice a pattern. You’ve received clear, thoughtful proposals aligned with your calls – yet no real engagement, year after year. I’ve said this gently before: your call-out text needs to be composted. If you’re not funding alternative, open, activist infrastructure – just say that. Don’t lead people on.

Look forward to seeing what did get funded – I’ll be writing something on that soon https://hamishcampbell.com/?s=nlnet

A post on why this kind of institutional #geekproblem push needs compost: https://hamishcampbell.com/we-need-to-compost-the-current-culture-of-lying/

Hamish

Not surprised. This is probably the 10th time we’ve applied to the #NLnet / #NGI fund over the years. Just heard back: our proposals for #OGB (Open Governance Body), #indymediaback, and #MakeingHistory were not selected – again.

“We are very sorry that we cannot offer you support for your good efforts.”

Sure, I, appreciate the polite brush-off again. But after so many rejections for solid, urgently needed tech projects that actually fit the funding goals, it’s time to name what’s really going on.

That there’s no #mainstreaming support for grassroots alternative, activist-rooted #openweb infrastructure. These projects aren’t pointless and inoffensive enough, not wrapped in shiny #NGO-speak, and don’t fit the comfy (in)circles of #geekproblem “innovative” funding. But they are native, they are needed, and they work – if you actually want a humane, federated, public-interest net that the funding outreach text says you do.

Time and again, we’re told these projects are “not selected” – Meanwhile, funding continues to flow toward a few good minority projects, a few #mainstreaming #fashernista alt tech projects, but the most goes to, minority interest, academic paths or closed bureaucratic #geekproblem circles, recycling the same stale stack of status quo ideas in slick/pointless packaging.

On balance, this is VERY much not building the #openweb – it’s way too often pushing #NGO and geek hobby paths or building another layer of the #closedweb under a friendlier mask. Yes, the is some small good done with this tech funding, it supports the big #dotcons copying Fediverse projects, no bad thing. But on the question of balance, we can see the lies.

We’re not discouraged. We’re composting this – as ever – into the next push. And yes, we’ll keep applying in till they change the text of the invites, so our projects are not the perfect fit they are now. Not because we believe the system works, but because we need to document the process if it works, well more when it doesn’t work, sadly. Composting lies is a part of the #openweb reboot.

If you do want to support native, trust-based, grassroots tech building, outside the NGO bubble, chip in here: https://opencollective.com/open-media-network or help to make this institutional funding work as it says it does.

A look at this narrow #NGO and #geekproblem point of view

The essence of the #geekproblem is its narrow, self-referential logic. Here’s a #spiky, pointed, prody view of the narrow track of thinking that defines the #geekproblem in the context of an #openweb reboot:

“There is no Emperor, King, or Priest in the Fediverse’s feudalism.”

The illusion is that it’s all flat – no power structures, just pure meritocracy. If you’re already a priest or acolyte, there’s no need to ask. You just do:

Want a new app? Code it.
Want a new protocol? Spec and ship it.
Want a new UX? Design it and deploy.

And if you can’t do it yourself? Then you kneel before the alternative establishment and pray.
Or, as they prefer to say, advocate.

This is both a critique of the (hidden) hierarchies and a mirror held up to the myths of autonomy and openness in the current #Fediverse culture. There’s a real power structure – it just doesn’t wear a crown, but if you look it’s VERY visible, people choose not to look, this is the #techshit mess we make and need to balance with healthy grassroots composting.

What would a #fluffy view of this look like?

We need to shape native paths, not recreate #fashionista ones with shinier branding

We’ve got a new bunch of #mainstreaming tech devs flooding into the #Fediverse. Some from burned-out Big Tech, some from the academic funding circuits, some just looking for the next shiny project after the #AI hype wore thin.

Now, this could be good. IF even a few of them started working on native, grassroots tech – tools built for and by the communities who actually use them, not just more #dotcons platform clones.

Right now, we’re at a turning point. The first wave of the Fediverse was all about copying the #dotcons:

#Mastodon as “ethical Twitter”

#PeerTube mimicking YouTube

#Mobilizon as a Facebook Events replacement

#Lemmy doing Reddit but federated

All of this was necessary, it helped people jump ship and start imagining life beyond the dotcons. But that wave is peaking, and the second step is overdue. That next step? It’s about original, grassroots infrastructure. A federated trust graph instead of reinventing karma points or like-buttons. Protocols for local-first publishing, like the #p2p side of the #OMN or radical #4opens-inspired news and tools for community trust flows, moderation and accountability, rooted in values, not corporate TOS and PR management. Infrastructure for interoperability and redundancy, so projects don’t die when a maintainer burns out or a server goes down

But here’s the risk, if the new #devs only copy the #dotcons AGAIN, it’s a fail. Worse still, if they get sucked into the #NGO vampire nests, the slow, bureaucratic funding black holes of the worst paths of #nlnet and #NGI, we’ll just see more “safe” projects that burn grant money building tools nobody uses.

Let’s be clear, these institutions do some small good, on basic infrastructure, but their #NGO sides are hoovering up resources by pushing for risk-free deliverables, and ignore the actual needs of grassroots groups. This funding is way too often shaped by #mainstreaming politics and careerism, not lived practice. We’ve seen it before, and we’re seeing it again.

What we need now are tools that grow from compost, not code sprints. Tools built from social use, not tech fashion. We need radical simplicity, transparency, and flexibility, tech that can’t be easily co-opted by the forces we’re trying to move beyond.

So if you’re a dev stepping into this space, welcome. But please don’t make another Mastodon, but with more “privacy” or #AI features. Instead, work with those who’ve been composting here for years. Build with the messy, weird, and beautiful people who need to shape new paths, not, boringly, recreate the old ones with shinier branding.

A letter from the margins of the #openweb

All the #OMN projects I’ve worked on over the years, from #OGB to #indymediaback, are not directly about social change. They are about creating the possibility of social change. A subtle, but critical difference.

We don’t claim to have the answers. What we do offer are tools, networks, and processes that make it easier for people to imagine that the world can be different, and then help them to take the first step.

Yet still, here’s the mess that keeps being pushed over us. We are told this work is “too high up the stack,” “too fuzzy,” or “too political.” But in reality, the same topics and themes do receive #NGO funding, just safely sanitized within the logic of the #deathcult. In this, the “shadow” keeps getting funded, but the light source is ignored.

When we say “the world can be different,” we’re not talking about abstract theory. We mean literally:

Media that people control from the grassroots up
Governance that isn’t locked behind elitist gates
A web that grows through trust not platforms
Protocols that reflect values, not just efficiency

But the funding, even in the so-called ‘alternative’ spaces, is trapped in a conservative loop. People working in these orgs are either too captured by their own #geekproblem funding logic, or too afraid to support anything that might really challenge their place in the status quo, by threatening to end the funding flows they live in.

Some of the real replies to the over 20 funding applications I have put in for the last ten years: “This kind of effort is very hard to seek grants for…” “I don’t have an obvious candidate for you to go to, either.” What these polite deferrals mask is a structural failure of imagination. The fear of change is so strong that even funders tasked with enabling alternatives end up only supporting work that conforms to existing institutional logics and barely deviates in meaningful ways from the normal #mainstreaming paths.

So, where does that leave those of us pushing for a real #openweb reboot? We get silence or slow-walked rejections. We burn out or pivot to “safer” projects. Or worst of all, we get absorbed by the very forces we wanted to challenge. And look, maybe that’s the plan. Maybe co-option is the endgame for the #openweb: a slick, tamed version of rebellion, friendly enough for NGOs and palatable to #EU bureaucrats.

But that’s not our plan. Not the plan we’ve been composting all these years. The challenge:

Funders: If you want the future to be different, stop only funding imitation’s, fund the real thing, step outside the safety of compliance. Trust radical imaginations.
Builders: If you’re still holding the compost shovel, don’t drop it. The real garden will grow, but only if we stop watering the plastic plants.
Everyone else, demand more. Not just better bling, but better foundations.

We don’t need more advice, we do need courage. The #openweb is not dead, but it is at risk of becoming another façade unless we build the possibility of real change into its #rebooting core.

I am still digging #makinghistory #OMN #indymediaback #OGB

#RIPENCC #NGI #NLnet

The #blocking of #openweb funding

Funders, #NGOs, and the #mainstreaming crew are trapped in fixed truths, while real change comes from dynamic thinking. That’s why they keep failing us. So, how do we break this cycle and move forward? For meaningful #openweb funding, we need projects that are native and align with critical social needs for the evolution of the internet, balancing openness/trust based tech with funding for outreach and feedback mechanisms.

Shifting Funding From “Fear/Control” to “Open/Trust” The Problem, current funding paths for internet projects focus on security, control, and compliance, perpetuating systems of centralized authority. This approach stifles trust-based collaboration, which are essential for the #openweb path. Action: help to advocate for dedicated funding streams for projects explicitly focused on decentralization, trust-building, and open governance structures like the Open Media Network (#OMN) and #OGB. Incorporate trust-based metrics into funding criteria, rewarding projects that demonstrate sustainable, human-centered governance.
Bridging hard tech and soft use. The Problem: Hard tech (protocols, platforms) develop in isolation from people, leading to tools that fail to meet real-world social needs. Action: Allocate funds for programs to bridge developers and user communities, ensuring reciprocal feedback between tech builders and real life communities. Establish mechanisms to incorporate insights from “soft use” (how people interact with tools) into the iterative development of “hard tech.” Support user-led design initiatives for communities to directly shape the platforms they use.
Governance: The Problem: Existing tech networks prioritize technical over social design, exacerbating the #geekproblem of over-complexity and alienating the change we need. Action: Fund projects like the OMN that flip this dynamic, prioritizing human networks as the foundation for technical systems. This creates tools that reflect and support the needs of grassroots communities. Promote protocols like #ActivityPub to enhance interoperability and people/community autonomy across networks.
The OMN is a lightweight framework with five core functionalities aimed at building a trust-based semantic web:
* Publish: Share content as objects.
* Subscribe: Follow streams of interest (people, organizations, topics).
* Moderate: Manage trust by endorsing or rejecting content flows
* Rollback: Remove historical flows content from the point trust is broken.
* Edit Metadata: Improve the discoverability and context of content.
These tools enable people to control their digital spaces and data flows while horizontally growing collaboration and accountability

This native #openweb path requires systemic support with funding to promote tools and frameworks that build human agency and trust. By doing this, we create resilient and equitable paths in tech, moving away from the limitations of the #open and #closed web mess we keep repeating

On this subject, it’s worth looking at this https://en.wikipedia.org/wiki/Conway%27s_law

The funding crisis for the #openweb isn’t just about money—it’s about values. Right now, too much funding goes into coding copies of #dotcons, replicating the same social centralized, mess under a different name. This doesn’t fix anything—it just locks us into the same broken patterns.

We need to push for native #openweb approaches—ones rooted in decentralisation, trust, and open process. History is full of projects that did this right—#indymediaback being just one example. But the real challenge isn’t just building the tech; it’s getting people to value this diversity.

Funding bodies like #NGI, #nlnet, and #ngizero could play a key role if they prioritize projects that challenge, rather than copy, the status quo. But beyond grants, we need a cultural shift—one that recognises the importance of public digital infrastructure and collective ownership over our tools.

So what can we do?

Demand funding for actual #openweb projects, not more social silos.
Build bridges between funders and radical grassroots tech.
Create our own support networks outside traditional funding models.
Shift the conversation—value the diversity, not just the tech.

If we don’t push, the funding will keep flowing into the wrong places, and we’ll be stuck recycling the same failures. Let’s compost the mess and grow something real.

#4Opens #OMN #DIY

In part, the USA shift to the right is due to the #geekproblem in tech

The political power that Silicon Valley and Big Tech pushed over this election is a real #geekproblem threat, with the #dotcons leveraging technological and financial influence to shape society in ways that benefit the nasty few and undermine basic democratic paths we need to be fallowing to mediate #climatechaos

One path to balance this #mainstreaming mess making is the need for active and healthy critiques of the lack of institutional support for #openweb projects and paths that focus on humanistic alternatives to these Big Tech platforms. The problem we need to challange is that organizations theoretically supportive of democratic values, such as #NLNet and #NGI, sideline core “native” paths in tech as “too radical”, instead favouring safe narrow #geekproblem and #NGO tech paths which we know do not work. This is frustrating, and with the increasing authoritarianism spreading worldwide, it’s a part of the #deathcult we all worship.

The “geekproblem” in tech is about challenges arising from the culture and mindset within technical communities, particularly around developers and engineers. It is associated with an overemphasis on technical solutions, insularity, and a tendency to prioritize technological efficiency or novelty over broader social and ethical considerations.

Overemphasis on Technical Solutions: People involved in tech prioritize creating or improving technical features while overlooking social impacts or peoples needs. This leads to “solutionism,” where every problem is assumed to have a tech-based answer, neglecting simpler, social, or policy-based solutions.
Insularity and Group Think: The tech world is insular, with tight-knit subcultures that resist input from outside communities and dismiss perspectives that don’t align with technical paths. This leads to narrow solutions and a resistance to the needer wider perspectives, ultimately #blocking the social change and challenge we need.
Focus on Control over Collaboration: Tech communities are often defacto hierarchical, top-down in the paths of design and governance, leading to a “we know best” paths. This often alienates non-technical people and discourages cooperative and participatory input, making it hard to integrate open, community-based governance in to the narrow paths that are imposed.
Ignoring and Dismissing Social Issues: Focused on technical work overlook social issues the tech is supposed to be addressing and solving. By focusing only on engineering, they overlook who has access to the technology, who benefits from it, and what ethical implications it brings, perpetuating the disconnect between technology and the communities it made for.
Resistance to Broadening Perspective: Tech creators actively resist moving beyond their own narrow areas of expertise and interest, they block ideas and initiatives that don’t fit within their immediate understanding, inhibiting growth and the needed experimentation. This resistance limits meaningful progress, community needs, and alternative technologies.

In sum, the #geekproblem stems from a blend of narrow technical focus, resistance to diverse input, and lack of attention to social impact. Addressing it involves building more inclusive, collaborative, and socially aware tech paths that embrace #4opens broader perspectives beyond the purely technical.

We now need to compost these piles of #techshit

State Funding of #FOSS and Open Source: Is it a Good Idea or a Bad Idea?

The questioning over state funding of Free and Open Source Software (FOSS) and open-source initiatives revolves around invisible ideological debates about benefits and drawbacks. Let’s look at this from a few specific examples: #NLnet, #NGI, and the European Union (#EU), to understanding the implications and effectiveness of this funding path.

The #NLnet Foundation is a notable example of an organization that provides funding to open-source projects. Supported by private and public funds, including significant contributions from the #EU, NLnet focuses on promoting a free, open, and secure internet.

The #NGI initiative, funded by the #EU, aims to shape the development of the internet of tomorrow. By supporting a range of open-source projects, NGI tries to foster innovation, privacy, and security. It emphasizes human-concentric technology, ensuring that the future internet respects humanistic values and needs.
The #EU has been a significant proponent of FOSS, providing funding through programs such as Horizon 2020 and Horizon Europe. The EU’s supports digital sovereignty, reduce dependency on non-European technologies through promoting open standards.

The is some democratization as these state-funded FOSS projects ensure software is accessible to wider groups, thus reducing the digital divide. For instance, NGI-funded projects are supposed to focus on inclusivity and user empowerment. At best, this transparency brings public overview to these processes.

There are some economic benefits and cost savings in using and supporting FOSS instead of expensive proprietary software. Funding initiatives like NGI stimulate innovation by allowing developers to build upon existing open-source projects, fostering a collaborative environment. Though, there are unspoken issues of sustainability in a pure capitalist path, thus the question of balance in state funding.

Open-source software allows for independent security audits, reducing the risk of vulnerabilities. The EU’s investment in secure communication tools underlines this advantage. Reducing reliance on a few large proprietaries #dotcons software vendors enhances national security and control. The EU’s support for open-source projects aims to bolster humanistic digital sovereignty.

For example, #NLnet’s diverse (though #geekproblem) funding portfolio highlights this limited community-driven development. The collaboration between public institutions, the private sector, and community contributors helps #NGI projects bring together diverse stakeholders to work on common goals. #FOSS projects thrive on community contributions, leading to continuous improvement and support and thus in theory community needs, though due to the dogmatic #geekproblem this is currently failing.

Funding Continuity: Projects become dependent on government funding, which currently is not stable or continuous. For example, sudden policy shifts in the EU affect long-term project sustainability. Without a sustainable funding, FOSS projects struggle with long-term maintenance and support.

Most #FOSS projects are too idiosyncratic to meet quality #UX standards. Thus, the current #geekproblem dominated process means that state funding inadvertently support meany unusable and thus pointless, subpar projects. Effective diversity and oversight of these mechanisms are crucial to mitigate this failing path.

Government involvement leads to bureaucracy, slowing down and ossifying development cycles, currently we do not work though this path well, The balance between oversight, diversity and agility is critical. With the #EU path this is a huge problem leading to almost all the current funding bring poured down the drain.

For #mainstreaming capitalism the issue of “Market Distortion”, the idea of competition raises the issue of state funding distorting “market” dogmas to disadvantage private companies and startups that don’t receive government support. For instance, EU funding can overshadow smaller #dotcons, capitalist thinking sees this as a risk that government-backed projects might stifle innovation by shaping the market landscape.

Political and ideological biases influence which projects receive funding, this is currently pushing a #blocking of the needed “native” #openweb path. How to move past this to ensuring diversity and “impartiality” in funding decisions need real work. How can we shift this “common sense” focus that government priorities do not align with the wider needs of the #openweb community and end-users. Aligning funding priorities with community needs is needed to address this concern, how can we make this happen with funding like #NLnet and #NGI?

To sum up, #NLnet are doing some good work, but this is focused on feeding the #geekproblem and building #fashionista careers, evern then on balance they do a better job than most. Then the wider #NGI funding is going into the #dotcons and #NGO mess, thus being poured directly down the drain. Over all, it’s fantastic that the #EU is funding the #openweb even if it is doing it very badly by funding very little that is native or useful.

Conclusion, state funding for FOSS and open-source initiatives, in our examples #NLnet, #NGI, and the #EU, has potential for creating real change and challenge, but this path presents both opportunities and challenges. When implemented thoughtfully, it can foster “native” paths, innovation, reduce costs, and enhance community and security to challenge the current worshipping of the #deathcults by our widespread use of the #dotcons. The question is the will and understanding to balancing this path to ensures that state funding positively contributes to the #4opens FOSS ecosystem, driving forward a free, open digital future or just leads to the capitalistic criticism of waste and distortion? At best and at worst, we see some real change and a lot of poring funding down the drain to feed some #geekproblem and build the careers of a few #fashernistas

The is much to compost in the current mess, can we get funding for shovels please #OMN

Slogan for #openweb: “Technology’s job is to hold the trust in place”

Definitions can be loose; making things overly rigid is a #Geekproblem that fosters conflict.
This is why the #4opens is about interpretation and judgment. The #Fediverse is a vibrant and active #openweb project, currently one of the healthiest “native” parts of this path.

Some “native” examples we are working on:

Principles for #OGB (Open Governance Body) Consensus and Engagement: Decisions are valid only if a wide range of people are involved, ensuring that the collective is the consensus. This prevents any single individual from overpowering the group. Power resides in trust groups, which likely use their influence positively. This #KISS is needed to maintain trust that ensures better outcomes.

Solving technology problems with trust and #4opens: These principles provide a flexible and resilient approach to technological challenges. To repeat, the key role of technology is to maintain trust. To do this, let’s focus on the social path, an example of this would be #PGA (People’s Global Action), that keeping this as a checkpoint helps block #mainstreaming attempts and maintain polite engagement.

Building and maintaining projects needs strong social defaults and hardcoding #4opens. Consistency, keep the #4opens principles at the forefront to prevent dilution during outreach. Building tech from the grassroots level, horizontally, avoids #mainstreaming “common sense” which always leads to burnout and friction. While outreach is essential, the core principles should not be compromised. Focus on community and consensus to ensure broad engagement to maintain trust and effective governance.

These guidelines provide a structured approach to developing and maintaining technology projects that are open, transparent, and community-driven. By emphasizing trust and the #4opens principles, we create a resilient and sustainable path for technological and social change and challenge that is so needed in the era of #climatechaos.

#NGI #NLnet #EU