Tag: geekproblem

#Indymediaback Funding Application 2025-02-036 indymediaback received

The following submission was recorded by NLnet. Thanks for your application, we look forward to learning more about your proposed project.
Contact

name
hamish campbell
phone
email
hamish@visionon.tv
organisation name
OMN
country
UK
consent
You may keep my data on record

Project

code
2025-02-036
project name
indymediaback
fund
Commons_Fund
requested amount
€ 50000
website

    https://unite.openworlds.info/indymedia

synopsis

The #indymediaback is a Fediverse project about rebooting the radical grassroots media network, Indymedia, by anchoring it in trust-based (Open Data, Source, Process, and Standards). It prioritizes local, collective publishing as the foundation for global solidarity and counter-narratives. The project resists the co-option of #mainstreaming and #dotcons by decentralized, democratic governance and focusing on native, horizontal structures.

Expected outcomes include a revived independent media landscape that amplifies marginalized voices, balancing corporate and state narratives, and builds resilience against #posttruth misinformation. By composting the #geekproblem and embracing simplicity (#KISS), the project empower communities with sustainable, open tools for storytelling, activism, and solidarity. The goal is to seed a flourishing, cooperative #openweb native media as a part of the current activertypub based web reboot.

experience

I’ve been actively engaged in #FOSS and #openweb projects for over 20 years, focusing on building grassroots, community-driven alternatives to centralized and corporate-controlled platforms. My work emphasizes creating and sustaining open, democratic, and resilient digital paths.

In the early days of the Fediverse, I ran five instances for the first five years, helping to seed the decentralized ecosystem that has since grown into a viable and widely recognized alternative to the #dotcons. This hands-on involvement gave me a deep understanding of the technical, social, and governance challenges of decentralized networks.

Since the launch of the ActivityPub standard, I’ve contributed to shaping the underlying paths that enable decentralized social networking. My work has facilitated discussions, advocating for grassroots perspectives, to ensure that the voices of smaller, community-oriented projects are heard amid broader efforts to standardize and scale the Fediverse.

My involvement includes engaging in advocacy, community building, and technical implementation, ensuring that open standards remain open and accessible. By bridging technical expertise with grassroots activism, I work to mediate the #geekproblem and bring human-centered, trust-based solutions to the forefront.

These experiences directly feed into the #indymediaback project, where I bring not only technical skills but also a rich history of working within collaborative, open frameworks. By combining lessons from past successes and challenges, we plan on contributing to building a robust #openweb ecosystem that stands resilient in these fragile social, ecological and technical times.

usage

The budget for the #indymediaback project will be allocated to support the development, outreach, and sustainability of the initiative. Drawing on code from Ibis 0.2.0 https://ibis.wiki/article/Ibis_release_0.2.0_-_Federated_Wiki_with_Shiny_Redesign

  1. Platform Development: Core Infrastructure: Building a lightweight, federated publishing platform that aligns with #openweb principles, based on a federated wiki approach like Ibis. This includes robust ActivityPub integration for seamless interconnectivity with the Fediverse. UI/UX enhancements on top of this to show and shape the media flows.
  2. Community Support and Training: Workshops: Conducting training sessions to onboard activists, journalists, and developers onto the platform, focusing on decentralized publishing and governance. Documentation: Creating clear, multilingual resources to empower communities to use and extend the platform independently.
  3. Outreach and Advocacy: Network Building: Expanding the grassroots network by collaborating with existing projects in the Fediverse and the broader #FOSS ecosystem. Awareness Campaigns: Promoting the importance of independent media and the dangers of the #closedweb to engage both activists and potential contributors.
  4. Maintenance and Sustainability: Hosting Costs: Providing stable hosting for early adopters and community-managed hubs. Ongoing Development: Allocating resources for iterative updates, security improvements, and adapting/building code and UX from user feedback.

Past and Present Funding Sources: Historically, the #indymediaback project has operated with minimal funding, relying on volunteer efforts and community goodwill to sustain its activities. Some aspects, such as initial platform experimentation and hosting small-scale instances in the Fediverse, were supported by personal contributions and donations from allied groups.

While the project has not yet received large-scale institutional funding, it has benefited from the collaborative ethos of the #FOSS and #openweb communities. Moving forward, the project seeks to diversify funding sources by exploring grants, grassroots crowdfunding, and partnerships with aligned organizations. However, maintaining independence from corporate or agenda-driven funding remains a core principle to safeguard the radical and democratic essence of the initiative.

The requested budget will act as a seed, enabling the #indymediaback project to transition from concept to sustainable implementation.

comparison

Comparison with Historical Indymedia: #Indymediaback: builds on the original ethos of news publishing and grassroots participation but adapts to modern needs with more robust and user-friendly technology. The project focuses on federated systems and decentralized governance to avoid the bottlenecks and centralization that hindered the original Indymedia.

Technology: early Indymedia used custom-built CMS platforms like DadaIMC, which were groundbreaking at the time but eventually became outdated. The lack of resources for updates and scalability led to significant challenges as the internet evolved.

Indymediaback: Leverages ActivityPub and the Fediverse, building on existing protocols and infrastructure while maintaining an open and adaptable architecture. This ensures scalability, security, and relevance in the evolving landscape of decentralized web technologies.

Comparison with Existing Fediverse Media Projects

Mastodon and Pixelfed, Flagships of the Fediverse project focused on microblogging, popularized ActivityPub and brought decentralized platforms into mainstream conversations. However, this success has also led to “NGO-style” #mainstreaming tendencies, with decisions catering to wider audiences rather than grassroots paths. Pixelfed: A decentralized alternative to Instagram, Pixelfed focuses on visual storytelling but often lacks the “news” path that #indymediaback seeks to prioritizes.

Indymediaback, unlike Mastodon or Pixelfed, explicitly targets “news” communities and grassroots content. Its focus is on collective storytelling and action, ensuring that it serves as a platform for organizing, not just broadcasting.

Lemmy and Kbin: Are Reddit-style platforms for community-driven forums, Lemmy demonstrates the potential for federated discussion but lacks the tools for journalistic workflows or media dissemination.

Bonfire Networks, is a federated platform emphasizing modularity, Bonfire aims to provide tools for diverse community needs. However, its roots in the #NGO space mean it struggles to align with actually reverent to grassroots paths.

Expected Outcome: The #indymediaback project revitalize “native” media by combining the best aspects of the original Indymedia—open publishing, grassroots participation, and activist focus—with the technological and governance advancements of the Fediverse. The outcome is a resilient, federated news network that empowers communities to create, share, and amplify their stories, freed from the constraints of corporate platforms and institutional agendas. This reboot provides a necessary counterbalance to the #closedweb and an avenue for meaningful news in these trubaled “post truth” times.

challenges

The #indymediaback project faces some challenges:

Federated Open Publishing: Developing a robust, ActivityPub-compatible open-publishing system to handle collaborative content creation and moderation at scale.

Scalability and Usability: Ensuring the platform can support diverse communities while remaining accessible to non-technical users.

Trust and Governance: Implementing transparent moderation tools and decentralized governance to balance openness with accountability.

Interoperability: Seamlessly integrating with existing Fediverse platforms while providing unique activist-focused features.

ecosystem

The ecosystem focus on empowering local activists, citizen journalists, and independent media organizations, providing them with tools for collaborative storytelling, decentralized publishing, and grassroots governance.

Key Ecosystem Actors:

Fediverse Platforms: Like Mastodon, Pixelfed, Peertube form the foundation for connecting and amplifying diverse communities. #indymediaback interoperates with these platforms, enriching the Fediverse with news-focused capabilities while leveraging their existing user bases.

Citizen journalists: community reporters, and activists will be the core creaters of the platform. The project will provide tools for collaborative content creation, transparent moderation, and open publishing to ensure their voices are heard.

Developers and technologists: open-source developers and technologists in the Fediverse and ActivityPub communities will play a critical role in refining and scaling the platform. The project will actively engage with forums like SocialHub to share progress, seek feedback, and align with broader Fediverse standards.

Grassroots organizations: Non-profits, collectives, and activist networks will be key collaborators. By building a decentralized news outlet, the project amplifys their impact while fostering cross-community solidarity.

Engagement Strategies: Collaborative development, hosting regular open sprints, hackathons, and discussions within the Fediverse to build a strong, participatory development culture.

Community support: Dedicated onboarding and user support resources will ensure seamless adoption by non-technical people and communities. Tutorials, workshops, and community-led training will help bridge the digital divides.

Outreach and partnerships: The project will engage with existing Fediverse admins, moderators, and activists to build a coalition for shared goals, promoting the outcomes through federated content streams and cross-platform collaborations.

Blindness and Compost

Ideologies are frameworks for interpreting and navigating the world, the #mainstreaming “common sense” of rejecting them amounts to rejecting structured understanding. When people claim to eschew ideology, they default to the dominant paradigm, the #deathcult of #neoliberalism, without realizing it. This uncritical stance isn’t radical or alternative; it’s a by-product of mainstreaming and the disorienting effects of #postmodernism.

The act of composting this mess is acknowledging and breaking down these entrenched, harmful systems, for the needed, cultivating healthier, more grounded alternatives. Keeping it simple (#KISS) and reaching for that metaphorical shovel is the first step in transforming decayed ideas into fertile ground for the #OMN and other grassroots projects.

So yes, it’s time to dig deep, break it down, and build anew. Let’s shovel together. 🌱

What can you do? Some actions to reclaim the #openweb and refocus on its core principles of trust, humanity, and grassroots democracy is a good first step. The #posttruth era has eroded the integrity of our media, and tools like #Google—once a gateway to knowledge—have been reduced to serving the agendas of #dotcons and more recently the state, leaving us stranded in a desert of noise and distraction.

To take the different path, we need:

  1. Composting the #geekproblem: Our tech culture has long been trapped in deterministic, myopic paths that prioritize tools over people. This “#techshit” needs to be broken down and repurposed, with a focus on social and democratic values rather than isolated, insular designs.
  2. Pushing aside the #dotcons: These thrive on extraction, disconnection, and control. By putting them aside, we free ourselves to create paths and projects that genuinely serve communities, fostering collaboration rather than competition.
  3. Rebooting the #openweb: Grassroots democracy must be central to this effort, with social technologies incorporating human and social needs into their design, ensuring they empower rather than alienate. The #OGB and projects like it offer a tangible path by embedding democratic processes and open collaboration into the fabric of the web.

A simple path is the invitation to “click on the hashtags and think” which is a challenge to break out of default paths of disengagement and passivity. The #OMN isn’t only a tech project; it’s a rallying cry for those who want to see through the mess of the #mainstreaming culture and the #deathcult of neoliberalism.

If you’re reading this and feel the pull, its time to act. Visit Statements of Support, sign up, and let’s compost the mess to grow a flourishing, democratic #openweb together. Don’t be shy—this is our moment. 🌱

Critique the ideological blindness of the tech world

The story often revolves around the #geekproblem and deeper ideological and structural issues in the tech world. There are internal conflicts in open movements. An example i like to talk about is the UK Indymedia project as a case study of ideological and technical battles between groups with different visions for open media. #Encryptionists: Advocated for security and privacy at the expense of openness, blocking aggregation efforts like RSS. #Fashernistas, sought control over media flows through proprietary yet “better” alternatives to open standards, undermining compatibility. #Openweb advocates promoted aggregation and widely adopted standards like RSS but were sidelined by other factions. The result was a self-destructive cycle that caused the UK Indymedia project to become irrelevant, exemplifying a broader failure to embrace shared, open solutions.

The broader #geekproblem, refers to the cultural and ideological blind spots of the tech community. A fetishization of privacy, encryption, and individualism, which serve market-driven ideologies rather than societal good. A failure to address systemic social and environmental issues (e.g., #climatechaos, #deathcult worship) in favour of isolated, tech-first solutions. The division between “open” (sharing power) and “closed” (hoarding power) reflects fundamental tensions between altruistic and exploitative visions of technology.

Society and technology, the story draws parallels between historical ideologies (e.g., capitalism’s greed vs. socialism’s altruism) and the current state of tech. Examples: Closed systems reinforce inequality, greed, and control. Open systems, guided by principles, prioritize cooperation, connection, and societal benefit. The problem of dogmatism on both sides of progressive tech (spiky vs. fluffy) hinders collaboration and slows progress.

Working grassroots projects need to return to basics, embrace openness, foster flow rather than blocking, and reject the destructive patterns embedded in neoliberal tech culture. The framework is a shovel to compost the ideological and technical mess, enabling meaningful technological change. Social movements and tech must integrate this change and challenge to prevent centralization and co-option.

It’s good to critique the ideological blindness of the tech world and suggests that only by fostering trust and openness can we build a sustainable future #KISS

Shifting tech to collaboration, accountability, and sustainability

For a nuanced take on the #geekproblem, we need to highlight challenges and cultural dynamics in tech development. A starting point is the support for standards as foundations, everything in tech is built upon layers of “open industrial standards,” which provide value and interoperability. Ignoring these foundations to create isolated systems is akin to “building sandcastles”—fragile and ephemeral. The process of defining standards, however, is itself flawed and sometimes exclusionary, reflecting broader social issues like tribalism or nationalism.

Tribalism in tech can be seen as innovation and community-building but can also create fragmentation, gatekeeping, and resistance to collaboration. Comparisons to nationalism suggest that, like nations, large #dotcons (e.g., Facebook, Google) exert power rivalling traditional states, creating their own “tribes” with significant social influence. Tribalism in tech isn’t inherently bad; it can build strong, purpose-driven communities. However, when it turns exclusionary and disconnected from real-world issues, it becomes counterproductive.

Critique of dotcons and deathcult focues on the dominance of for-profit platforms (#dotcons) and the neoliberal ideology (#deathcult) underpin much of the dysfunction in society, including within the tech world. Life “inside the dotcons” involves uncritical participation in harmful systems, perpetuating cycles of #stupidindividualism and environmental degradation (#climatechaos). Platforms like Facebook and Google exemplify prioritizing profit over public good. Moving away from this requires alternatives rooted in the : Open data, Open source, Open standards, Open processes. Projects like the #OMN exemplify this shift.

Mediating harm in tech development with the broader social and environmental impacts of technology, pushing against #stupidindividualism and toward collective, sustainable solutions. Much of the “blocking energy” comes from entrenched systems and social inertia rather than active conspiracies, though intent exists in places like #traditionalmedia. Developers have a responsibility to build systems that mediate harm and foster collective well-being. This means rejecting solutions that exacerbate individualism and embracing technologies that empower communities and address systemic issues like climatechaos.

The #geekproblem as dysfunction, the geekproblem reflects a 20th-century tribalism that fails to embrace the ethical, collaborative potential of the #openweb. Examples include failed projects like #Diaspora, which had technical merit but struggled due to cultural and governance issues. The dysfunction stems from a narrow focus on technical solutions without considering social or ethical dimensions. Bridging this gap requires integrating diverse perspectives into tech development, emphasizing simplicity and human-centric design.

We do need a call for change to address these challenges head-on, we need ethical interventions rather than drawn-out or overly complex common sense “solutions”. The geekproblem highlights the limitations of tech communities to balance technical expertise with broader social responsibility. Ultimately, the solution lies in rekindling the spirit of the openweb while actively composting the “shit heap” of the dotcons. One path is addressing the geekproblem, to shift tech culture toward collaboration, accountability, and sustainability, to create tools that serve people rather than profit #KISS

Application 2025-02-032 Open Governance Body #OGB

Application 2025-02-032 Open Governance Body #OGB received

The following submission was recorded by NLnet. Thanks for your application, we look forward to learning more about your proposed project.
Contact

name
hamish campbell
phone
email
hamish@visionon.tv
organisation name
OMN
country
UK
consent
You may keep my data on record

Project

code
2025-02-032
project name
Open Governance Body #OGB
fund
Commons_Fund
requested amount
€ 50000
website

    https://unite.openworlds.info/Open-Media-Network/openwebgovernancebody

synopsis

A project designed to create a trust-based, decentralized framework for governance within grassroots networks and communities. Rooted in the principles—open data, open source, open processes, and open standards—the #OGB seeks to mediate human-to-human collaboration by fostering trust, transparency, and simplicity (#KISS).

Its primary focus is addressing the #geekproblem by bridging technical and social flows, creating tools that empower people to organize effectively without falling into hierarchical or centralized traps. The #OGB builds on trust to sift through noise, allowing genuine contributions to rise, moving from complexity to simplicity and back to complexity organically.

The expected outcomes include:

Strengthened grassroots governance: Tools for decision-making and collaboration that are inclusive and scalable.
A thriving #openweb ecosystem: Platforms and networks that prioritize trust and social value over profit.
Mediation of mainstreaming and NGO influence: Keeping progressive activism focused on spiky, meaningful change rather than fluffy distractions.

The #OGB aims to create sustainable digital commons that nurture resilience, diversity, and real-world impact.

experience

Yes, I’ve been involved in projects and communities aligned with the ethos and goals of the #OGB. My contributions span technical development, advocacy, and fostering open governance frameworks, all rooted in the principles of trust, transparency, and collaboration.

  1. Indymedia, I was an active contributor to the global Indymedia movement, which played a pivotal role in grassroots media and decentralized collaboration. My contributions focused on: Open publishing workflows to empower communities to share their stories. Advocating for the “trust at the edges” model to ensure decision-making remained grassroots-driven. Bridging technical and social challenges by helping develop and maintain tools that aligned with the movement’s values.
  2. OMN (Open Media Network), As one of the key proponents of the #OMN, I’ve worked to reboot grassroots media using trust-based networks and federated tools. My contributions include: Developing the concept of (open data, open source, open processes, open standards) to serve as a foundational framework. Advocating for federated tools like #ActivityPub and #RSS to enable media flows across decentralized networks. Organizing collaborative spaces to design tools that prioritize human-to-human trust rather than algorithms or centralized control.
  3. Fediverse Advocacy, Within the Fediverse, I’ve championed the importance of grassroots governance and resisting the co-option of these spaces by corporate or NGO interests. Contributions include: Participating in discussions to shape decentralized protocols like #ActivityPub. Pushing for #KISS (Keep It Simple, Stupid) principles to ensure accessibility and scalability. Highlighting the dangers of #mainstreaming and proposing strategies to mediate its impact on the #openweb.
  4. Open Governance Experiments, I’ve collaborated on smaller experimental governance projects aimed at exploring new ways of mediating human collaboration. For example: Designing trust-based moderation systems to reduce #geekproblem domination in decision-making processes. Implementing open-process methodologies to ensure transparency in workflows. Mediating conflicts between technical and social contributors, fostering productive collaboration.

Core Contributions Across Projects, across all these initiatives, my primary focus has been on bridging the technical and human aspects of governance. This involves: Developing frameworks that enable decentralized decision-making while maintaining trust. Advocating for simplicity to combat the paralysis caused by unnecessary complexity. Building alliances and mediating the challenges posed by #dotcons, #NGO dominance, and #geekproblem tendencies.

Through these efforts, I’ve gained insights into the challenges of building sustainable governance models in decentralized spaces, and the #OGB embodies the culmination of this work. It’s a step forward in creating robust, trust-based networks that empower communities to take control of their digital and social spaces.

usage

Budget Allocation for #OGB Project

The requested budget will be allocated strategically to ensure the project’s foundational development and long-term sustainability. An outline of key areas:

  1. Technical Development and Infrastructure (40%) Development of Core Tools: Funding will support developers to build the initial version of the #OGB code, focusing on simplicity, accessibility, and scalability. Server Infrastructure: Setting up and maintaining federated servers for testing, development, and early adoption. Integration with Existing Standards: Work to align with protocols like #ActivityPub, #Nostr and #RSS, ensuring seamless interoperability with the broader #openweb ecosystem.
  2. Community Building and Outreach (25%) Workshops and Training: Organizing sessions to train communities on the #OGB framework, focusing on trust-based governance and open-process workflows. Content Creation: Developing accessible documentation, tutorials, and guides to demystify the #OGB model for diverse audiences. Engagement Campaigns: Reaching out to grassroots organizations, activists, and communities to onboard early adopters.
  3. Research and Iterative Design (20%) User Feedback Loops: Conducting trials with early adopters to gather insights and refine the tools and processes. Governance Framework Refinement: Exploring different trust-based models to ensure inclusivity and adaptability to various contexts. Conflict Mediation Strategies: Testing and integrating mechanisms for conflict resolution and power balance within the #OGB framework.
  4. Administrative and Miscellaneous Costs (15%) Project Coordination: Funding part-time coordinators to manage timelines, resources, and community engagement. Operational Expenses: Covering software donations, events, domain hosting, and other minor but essential operational costs.

Past and Present Funding Sources. The #OGB project is currently unfunded in a formal sense, operating entirely through volunteer contributions. However, it is rooted in a history of collaborative efforts from related initiatives, which have benefited from in-kind support rather than direct funding.

Past Sources: #OMN and #Indymedia Communities: Provided foundational concepts and voluntary contributions of time, skills, and infrastructure. Fediverse and #Activertypub Advocates: Offered insights and testing environments for early experimentation with governance ideas.

challenges

Present Sources: Volunteer Contributions: Core contributors are donating their time and resources to push the project forward. Allied Projects: Informal support from related decentralized tech communities, sharing knowledge, feedback, and occasional resources.

Future Vision, while external funding is vital to accelerate the project’s development, we aim to maintain independence and adhere to the principles. By minimizing reliance on corporate or NGO funding, we ensure that the #OGB remains a grassroots-driven initiative. Our long-term goal is to establish a self-sustaining model through community contributions and shared ownership, embodying the trust-based governance the project seeks to promote.

Detailed budget breakdown can be attached if required.

comparison

The #OGB (Open Governance Body) project stands on the shoulders of both historical and contemporary efforts, drawing lessons from their successes and failures to craft a novel path to decentralized governance.

A comparative analysis: Historical Projects and Their Influence

Indymedia (Independent Media Centers) Overview: Indymedia was a global network of grassroots media collectives that emerged in the late 1990s to provide a platform for independent journalism. It embodied principles of openness, decentralization, and non-hierarchical governance. Comparison: Like Indymedia, #OGB aims to empower communities through open and decentralized structures. However, Indymedia struggled with governance conflicts and centralization of power in some regions. The #OGB addresses these issues through trust-based networks, conflict mediation mechanisms, and scalable governance tools. Key Takeaway: The #OGB builds on the ethos of Indymedia while implementing technological solutions to mitigate governance bottlenecks.

Occupy Movement’s General Assemblies. Overview: Occupy’s assemblies were experiments in direct democracy, emphasizing inclusivity and consensus-based decision-making. However, the lack of structured governance led to inefficiency and internal conflicts. Comparison: The #OGB shares Occupy’s commitment to participatory governance but incorporates trust-based models to build the decision-making. Instead of full consensus, the #OGB employs trust networks to delegate decisions while retaining accountability and inclusivity. Key Takeaway: The #OGB leverages structured trust-based governance to overcome the decision-making paralysis often seen in consensus-driven movements.

Contemporary Projects and Their Relationship to #OGB. Fediverse and #ActivityPub. Overview: The Fediverse is a decentralized network of federated platforms like Mastodon, powered by the ActivityPub protocol it is pushing user autonomy and grassroots control but has faced challenges around governance and moderation.
Comparison: The #OGB complements the Fediverse by providing governance structures for federated projects, addressing the ongoing issues of moderation and decision-making. The #OGB’s trust networks align with the decentralized ethos of the Fediverse, offering a scalable solution for community self-governance. Key Takeaway: The #OGB enhances the governance layer missing in many Fediverse projects, fostering resilience and collaboration across federated networks.

NGO-Led Open Source Initiatives. Overview: Many open-source projects are managed by NGOs, which often prioritize stability and funding over grassroots participation. This has led to criticism of centralized decision-making and “corporate capture.” Comparison: The #OGB resists NGO-style top-down management, instead prioritizing the principles: open data, open source, open process, and open standards. Unlike NGO-driven projects, the #OGB is inherently community-first, ensuring power remains with the users and contributors. Key Takeaway: The #OGB rejects the NGO-centric model, emphasizing trust-based grassroots governance to avoid co-option by external actors.

Lessons from Historical Failures. CouchSurfing’s Decline. Overview: CouchSurfing transitioned from a grassroots volunteer-driven project to a for-profit company, alienating its core community and undermining trust. Comparison: The #OGB guards against such shifts by embedding trust and open governance at its core, ensuring the project remains community-owned and operated. Key Takeaway: Trust-based governance prevents mission drift and maintains alignment with the community’s original values.

P2P Projects and Overengineering. Overview: Many P2P initiatives have failed due to technical complexity and a lack of user-friendly interfaces, alienating non-technical users. Comparison: The #OGB adheres to the #KISS principle (Keep It Simple, Stupid), ensuring accessibility and ease of adoption without sacrificing functionality. Key Takeaway: Simplicity is essential for widespread adoption and long-term viability.

Key Differentiators of the #OGB Trust-Based Networks. Unlike purely consensus-driven or hierarchical models, the #OGB employs trust-based networks to enable efficient and inclusive decision-making at scale. The Framework. The #OGB is grounded in the principles, ensuring transparency, accountability, and openness across all aspects of the project. Focus on Digital Commons. The #OGB is designed to nurture digital commons, creating a space for grassroots innovation, collaboration, and governance that resists corporate capture. Composting the #TechShit, creating fertile ground for genuine social innovation.

Expected Outcomes. The #OGB aims to fill the governance gap left by historical and contemporary efforts, fostering a resilient, open, and trust-based framework for digital collaboration. By learning from the past and building on existing technologies, we seek to empower communities to reclaim the #openweb, bridging the gap between technology and grassroots activism.

The #OGB project faces significant challenges in implementing scalable trust-based governance systems. Key technical hurdles include:

Interoperability: Ensuring seamless integration with existing open protocols like #ActivityPub and the widening #openweb reboot.
Usability: Creating user-friendly interfaces to make complex governance processes accessible to non-technical people.
Resilience: Building systems resistant to malicious actors and spam within decentralized networks.

Are a few issues.

ecosystem

The #OGB project is rooted in a diverse ecosystem of grassroots organizations, decentralized communities, and open-source initiatives.

Ecosystem Description

  1. Grassroots Communities: Activist groups, independent media collectives, and community-driven initiatives seeking alternatives to hierarchical decision-making.
  2. FOSS Developers: Open-source software developers invested in decentralized tools, such as #ActivityPub, #Mastodon, and related protocols.
  3. NGOs and Advocacy Groups: Organizations interested in participatory governance and transparency tools for improving their operations.
  4. Tech Enthusiasts: People exploring ethical and sustainable technology beyond the centralized #dotcons paradigm.
  5. Academic and Research Institutions: Scholars studying governance, social movements, and decentralized technologies.

Engagement Strategies

  1. Collaborative Development: Open, participatory development processes underpinned by the philosophy (open data, source, process, and standards).
  2. Workshops and Webinars: Educating target audiences about trust-based governance and the project’s tools.
  3. Partnerships: Building alliances with aligned organizations, including community networks and FOSS projects.
  4. Documentation and Guides: Creating accessible materials to help communities adopt #OGB principles and tools.
  5. Pilot Projects: Collaborating with grassroots organizations to implement and refine governance systems, ensuring practical impact.

Promotion of Outcomes

  • Demonstration Projects: Showcasing successful case studies of #OGB governance in action.
  • Fediverse Integration: Leveraging federated platforms for dissemination and collaboration.
  • Open Events: Participating in conferences, hackathons, and public forums to share insights and foster adoption
GOVERNANCE-BODY_REV-March-2022.pdf
OGB-dev.png

What we need to do

There is a direct line between the challenges of the #mainstreaming of the #openweb and the critical need for tools like the to address these challenges. The #mainstreaming of the openweb brings visibility and new energy but also risks flooding it with shallow “common sense” that undermines its foundational values. The 4opens is your shovel, a tool for mediating this balance and preserving the integrity of the native ecosystem.

Tools to Shift the Balance: as a Guiding Principle: Ensure every project or platform respects:
Open data
Open source
Open standards
Open processes

Using this framework to evaluate and pressure projects co-opted by corporate or NGO agendas, will “naturally” lead to community-led governance to keep control in the hands of people and communities, avoiding capture by #dotcons and other hierarchical paths and structures.

Then we have the urgency of the #geekproblem which is aptly named—it is a paradox where geeks often already “have all the solutions” but lack the social frameworks to implement them. This disconnect exacerbates issues and entrenched systemic failures.

Next we have the shifting from individualism to collectivism to balance “stupid individualism” which fills tech culture, to grow collaboration and shared responsibility. Rooting the work in #nothingnew helps to focus on proven solutions and resist the allure of constant innovation for its own sake. Embed ecological awareness to tie technological development directly to ecological paths we need, making sustainability a core design principle. Shovel Work, encourages collective efforts to “compost the #techshit” and build sustainable alternatives. This promotes the slow and messy work of growing robust, community-driven ecosystems rather than relying on quick-fix solutions.

The call to action – Use or Lose – The healthy #openweb development community needs active engagement. Whether through contributing to existing projects, advocating for the 4opens, or simply resisting the co-option of open spaces, it’s time to pick up the shovel and start digging. The message is clear: there’s no magic, just work. The #OMN and provide the framework and the tools—we need to use them before they’re buried under the weight of the mainstream flow of “common sense”.

The Evolution of SocialHub

“the crew gathered around #SocialHub worked remarkably well for a while, organising good gathering, conferences and very useful outreach of #ActivityPub to the #EU that seeded much of the current #mainstreaming. But yes, it was always small and under utilised due to the strong forces of #stupidindividalisam that we need to balance. Ideas?“

From grassroots origins, #SocialHub emerged as a community-driven platform, rooted in the #openweb principles, focusing on the interplay of technology and “native” social paths. Its initial success lay in its collaborative ethos, free from mainstream interference. This promising start has since failed, due to lack of core consensuses and the active #blocking of any process to mediate this mess making.

Current challenges are from the influx of non-native perspectives, The twitter migrants and rapid #Fediverse expansion has diluted what was left of the original focus. Then in reaction to this the has been a retreat to tech paths over the social paths. This shift toward technical priorities has marginalized the social aspects that initially defined the community, this is a mirroring broader #geekproblem struggles that are core to the original failing.

What actually works is always grassroots messiness and constructive processes, that is messy in a good way, authentic, grassroots movements are inherently untidy, this ordered/chaos is where real social value is born. Attempts to overly structure or mainstream these paths risks losing their soul. Lifestyleism, and fragmented tribalism, distract from meaningful change. These behaviours breed from #stupidindividualism, a core product of the #deathcult culture that undermines collective action. There is a role for activism, based on learning from history to avoid repeating mistakes. This can lead to wider social engagement, and an embrace of messiness to counteract the stifling tendencies of rigid mainstreaming and isolated tech focus.

The metaphor of “shovels” is useful to turn the current pile of social and technical “shit” into compost is apt. Grassroots communities nurture a healthier ecosystem that balances tech and social. The imbalance favouring tech over social must be addressed. Reinvigorating the core social crew with a focus on community-oriented discussions and actions can restore equilibrium.

For this, it can be useful to challenge neoliberal narratives, use the #openweb/#closedweb framework to critique and dismantle neoliberal “common sense”. Highlight how these ideologies breed the individualistic and exploitative tendencies that undermine collective progress. The need for vigilance against co-option and the importance of nurturing the messy authenticity of grassroots movements. The path forward requires not just shovelling but planting seeds of collaboration, transparency, and collective action. By embracing the chaos and keeping the focus on social value, the #openweb can flourish as a genuine alternative to the #closedweb.

#KISS

What is the “problem” with our geeks

The #geekproblem highlights a recurring issue within tech-driven movements, the overemphasis on control and complexity at the expense of accessibility, community, and collective goals. This “problem” arises from the intersection of tendencies toward hierarchy, a blind reverence for technology as inherently powerful (#deathcult worship), and the unchecked growth of technical complexity over the last few decades. This diverges from the principles of #KISS (Keep It Simple, Stupid).

Control as an Obsession is the invisible insecurity that blinds this path. The desire for control has deep roots, where order, precision, and predictability are prioritized above all else. In tech communities, this translates into over-engineering, with complex solutions that are difficult for non-technical people to engage with. Leading to exclusion and often to gatekeeping through jargon, obscure processes, and rigid technical hierarchies. This is tech #Fetishism, and leads to a belief in technology’s ability to solve any problem, with almost no understanding of the side lining social or political paths this come with.

This fixation, and resulting intolerance, leads to systems that might be technically impressive but fail to serve any broader community, producing another wave of #techshit that then needs work to compost
In this path, the #deathcult represents the blind worship of systems and ideologies that lead to direct harm to us.

The #KISS principal advocates for simplicity and accessibility, ensuring systems are intuitive and usable by the wider community groups that need them. The #geekproblem runs counter to this, by alienating the very communities tech projects are meant to serve and widening the gap between technical experts and everyday people, perpetuating inequality in access and understanding.

Taking the “problem” out of geek, we must rebalance priorities by shifting dev focus on people over technology. Build systems and networks that empower and include rather than control and exclude.
Embrace simplicity, with , prioritizing usability, transparency, and community feedback to make tools accessible. Actively challenge tech fetishism by pushing of technology as a tool, not an end in itself.

Solutions must address social and political dimensions by decentralize, this can be hard as all the code is in the end is about centralize authority in the hands of a few technical “elites”. But, the #geekproblem is not insurmountable, solving it simply requires a shift in mindset. By rejecting control-driven hierarchies and embracing collaborative simplicity, we build systems and networks that serve the people they’re meant to empower.

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.

#OMN #DIY

This ends very badly

It’s easy to see now that the world is a mess, and we have made this mess, we have collectively ripped apart our common humanist path. On part of this I talk about is that we have spent 20 years squandering the #openweb tools of liberation and connection. In our hyper-connected era, attention has become the currency of capitalism The #dotcons tools we were pushed in to believing were empowering—apps, platforms, systems—were always instruments of control. They’re not just tools for us, they’re manipulative mechanisms engineered to shape focus and erode our autonomy, they are tools of social control.

Your attention, once an inherent to you, is now a resource being siphoned without your consent or in most people’s understanding any attention. In the #mainstreaming path, it’s as if you’re holding an account you never opened, and every time you try to tap into your own focus, you find it already spent. The result? A hollowed-out version of yourself: overwhelmed, perpetually distracted, unknowingly complicit in your own digital and social exploitation. Welcome to the ‘obsession economy,’ where the most valuable product is you.

This isn’t some unintended consequence; it’s by design. Every endless scroll, every notification, every “you might like” pop-up is a calculated move designed to map your behaviour, desires, and unconscious tendencies. The current #mainstreaming path is clear: make you a predictable machine that clicks, buys, and reacts—repeatedly. And these #dotcons systems have perfected their craft of control.

The science is well known: our dopamine pathways are hijacked and held hostage. Each surrender refines the technique, locking us into feedback loops that make each swipe feel both essential and unsatisfying. The distraction is by design; the purpose is to keep you from noticing who is profiting from this economy of fractured attention.

We still cling to the illusion of control, this is a core definition of the #geekproblem, believing ourselves to be savvy navigators of our own choices. But put your phone down for a day, and you’ll feel the “phantom itch” of notifications that never came. Try to watch a show without scrolling through social media, and you’ll feel the discomfort of a single, unshared thought. The system is built to make us fear boredom and flee from stillness because those rare moments are where self-awareness could break through. And self-awareness? That’s bad for our worship of this #deathcult.

The #deathcult is not hard to understand

So, how do we start to reclaim what has been taken? You don’t need to start big, but you do need to start relentless. Think of it as a focus detox. Eliminate all non-essential notifications. Reclaim your mornings—don’t let them be dictated by a screen. Cultivate moments of true presence, where attention isn’t an asset being exploited but a gift to be savoured. Then bring this fresh focus to create a community around the change and challenge that we so obviously need.

Lift your heads from worshipping this deathcult. In a world obsessed with monetizing every moment of focus, remember: your attention is yours to guard. Without it, the real ‘you’ is another asset on someone else’s balance sheet. This ends very badly #climatechaos is a small part of the mess we have made and are making.

The #fashernistas and #geekproblem interact to work in unintentional tandem

In part, the current challenges faced by the #openweb and grassroots reboot movements can be traced back to two cultural and structural problems: the influence of #fashernistas and the deeply ingrained #geekproblem. Both of these contribute to active blocking of meaningful change, hindering the progress needed for an openweb reboot. To walk this “native” landscape effectively, it’s needed to understand these barriers and how they block change and challenge.

The fashernistas and their echo chambers, the term refers to a subset of people who are highly engaged in performative discussions, centred on trending topics and social posturing without substantive engagement in grassroots real world problem-solving. While they are adept at identifying and amplifying transient issues, their conversations stay within insular bubbles. This creates a cycle where attention and focus are pulled toward repetitive discourse that never leads to any outcomes.

This taking up space with little and most often no follow-through is detrimental. Fashernistas thrive in spaces where the appearance of awareness is valued over the hard, real, messy action that is needed. In this #manstraming bubble, dialogue is focused on social capital—who knows what, who said what—rather than collaborative problem-solving. The result? The conversation around the openweb becomes cluttered, attention splinters, and meaningful action is overshadowed by a constant churn of noise.

The role of #fahernistas in blocking change is their ability to dominate platforms and narratives. This domination becomes active blocking when their presence leaves little room for discussions rooted in genuine collaboration and open progress. They inadvertently (or sometimes deliberately) creates environments where the needed ideas and radical challenges to the status quo struggle to gain traction, let along attention. If the openweb is to flourish, this culture of self-referential chatter needs to be mediated.

What can we do with our fashernistas?

The #geekproblem is a different barrier, which is the cultural divide within tech communities that leans heavily toward deterministic, technical solutions at the expense of accessible, inclusive approaches. The geekproblem manifests when developers and technologists become gatekeepers, framing issues in ways that reinforce their control, preserving existing narrow structures rather than opening them up for collective problem-solving.

For example, in the #openweb and #fediverse projects, the drive for good #UX runs parallel to an implicit exclusivity of bad UX dressed in “privacy”, “security”, “safety” etc. Technical jargon, complex onboarding processes, and a lack of user-friendly interfaces are a barrier to entry and community building. This exclusivity prevents the broader range of participants from engaging meaningfully, turning potentially revolutionary spaces into “specialized” silos, that reinforce this very #blindness.

#fashernistas and #geekproblem interact and often work in unintentional tandem. While the former distracts and fractures attention with endless (pointless, narrow and repeating) discourse, the latter locks down practical pathways for change through gatekeeping and technological insularity. The result is a failing “native” path, where critical mass, and the needed community, fails to grow—one part is too busy talking, and the other is too busy coding in isolation. The broader culture of the #openweb suffers as a consequence, making the needed change far more difficult to achieve than it needs to be.

The solution lies in finding a balance that mediates between the superficiality of fashernistas and the closed nature of the geekproblem. This involves, promoting diverse voices, so that the #openweb aren’t monopolized by any tiny group. Building bridges between projects and communities, to facilitate communication between technical experts and those involved in creating actionable steps that align with paths we need to take. Developing a culture that values tangible outcomes and collaborative input over performative dialogue and gatekeeping. Amplifying onboarding, by making entry points into #opentech accessible, so people outside traditional tech ghettoes can contribute meaningfully.

The #geekproblem might kill meany of us, mediating it matters

The path we need for the openweb, is more than only technological solutions; it needs a culture shift. Both fashernistas and those contributing to the geekproblem need to recognize their roles and adjust their approaches, for the #openweb to thrive. The has been to meany years of pratish behaver in the paths we need, it’s pastime for #KISS focus. The current moment presents a fresh opportunity for change. With the fediverse and platforms like mastodon growing exponentially, there is a path to free the native spirit of the internet as a collaborative, #openspace with trust, transparency, and action as core motivators. Let’s try and make this work, and not squandered it by letting the voices of the few block the work we need to do.

Ideas please?

Shifting the #mainstreaming to the #openweb

We need to try and make the #mainstreaming agenda more functional in the #openweb reboot, how do we do this? One way is to strengthen community governance with native decentralized decision-making frameworks that involve more voices from the grassroots, like the #OGB project. This is self empowering as tools based on federated models (like those used in the #Fediverse) empower people to participation in decision-making processes rather than top-down dictates.

Develop a supportive ecosystem for builders with funding beyond the #fashernistas. To make this happen we need to shift funding mechanisms toward projects that align with the values of the (open data, open standards, open source, and open process). This means supporting those who build with the public good in mind, not just flashy, trendy ideas, and tech fashions. Empower developers with a community focus by highlighting projects that prioritize #UX and community needs rather than only tech novelty. Encourage #FOSS governance practices that are transparent and inclusive. Foster this inclusivity by bridging silos with cross-community dialogues, this facilitates discussions that bring together different sectors of alt-tech, civic tech, and grassroots movements to cross-pollinate ideas and useful paths to take.

Ensure that platforms being built do not only cater to niche tech communities but are accessible and usable by the public, thus focus on practical relevance. This helps to empower people to understand the importance of decentralized tech and how it benefits them directly. Thus helping to break down the barriers posed by the #geekproblem and demystifies participation in the openweb paths. A strong part of this is organizing hands-on workshops that engage people in contributing to and shaping the projects.

Accept that failures are part of the process. Instead of discarding what doesn’t work, use these experiences as compost—breaking down what failed and learning from it to build stronger initiatives. This plays a role in shifting cultural narratives to challenge and change the stores around the #openweb and wider #openculture to include cooperative problem-solving and mutual respect. Shifting the focus from tech utopianism to realistic, impactful change.

Build tech paths that are adaptable and capable of evolving with peoples needs and global conditions, including #climatechaos and socio-political shifts that are accelerating. A part of this is support for meany small tech paths that link and flow information and communities.

To reboot the #openweb to become a part of a shifting mainstreaming, we need to promote messy participatory governance, redirect funding to genuine, community-oriented projects, and champion inclusive, sustainable paths. The composting analogy emphasizes learning from past mistakes and continuously building resilient, inclusive solutions #KISS

What can we do with our fashernistas?
How can we mediate the #NGO blocking?

A test is to look at people and projects to see if they link, a basic part is the act of linking, which goes far beyond a simple convenience; it forms the backbone of an interconnected, accessible, and transparent internet. Yet, many people overlook its importance or misunderstand its role, especially when transitioning from #dotcons (corporate-controlled platforms) to #openweb environments. To sustain the promise of an open, people-driven internet, we need to recognize and actively engage with the practice of sharing non-mainstream links #KISS

But yes we do need to mediate the current mess, don’t feed the trolls, keeps coming to mind, when looking at the influx, this is like waves washing on the shore, be the shore not the wave.