Tag: Mastodon

Crisis of Governance in FOSS: Medieval Politics and Neoliberal Failures

Silicon Valley influence is significant and with the globe hegemony of the #dotcons every where, the concentration of power and resources among a few #dotcons raises issues about democracy, equity, and control. With this in mind, we need a strong push and for meany people a fundamental rethink and restructuring of how we approach technology, governance, and real community building.

The open-source and free software communities, despite their progressive foundations, are marred by outdated governance structures that are at base medieval aristocracy and monarchy. This, compounded by the problematic mediation attempts through #neoliberal individualism, results in a stagnation of innovation and collaboration that highlights the #geekproblem within these communities.

Medieval governance in modern tech, aristocratic hierarchies are the core in most open-source projects, decision-making power is concentrated in the hands of a few “maintainers” or “core developers.” These individuals hold their positions for long periods, leading to a de facto aristocracy, with the same people in control and influencing the paths of projects big and small. Monarchical leadership is core to meany, led by “charismatic” leaders whose word becomes law. This monarch-like leadership stifle dissent and discourage fresh contributors, as the projects revolves around the vision and whims of a single individual, in the #fediverse an example is the #Mastodon codebase.

Neoliberal Individualism and Its Failures

#StupidIndividualism is a part of #neoliberalism, which promotes a form of individualism emphasizesing self-interest and competition over collaboration and community. This mindset infiltrates open-source communities, leading to fragmented efforts and a lack of cohesive or even any vision. This “common sense” market-driven development infects open-source projects that are pushed by market demands rather than community needs. The results are software that prioritizes “control”over usability and any innovation.

The #techshit and #geekproblem

  • #techshit, a term that reflects the use of #dotcons and #FOSS which proliferates, poorly designed, unmaintained, and redundant software projects that clutter the open-source paths.
  • #geekproblem, refers to the insular and exclusionary culture within tech communities. It includes issues like poor communication, lack of diversity, and a focus on technical prowess over collaborative skills.

Moving Towards Modern Governance

Democratizing Decision-Making: Shifting from aristocratic and monarchical structures to more democratic governance can help. This includes implementing transparent decision-making processes, rotating leadership roles, and widerning voices that are heard.

Community-Centric Approaches: Prioritizing community needs over individual ambitions and market demands leads to more sustainable and impactful projects. This involves active engagement with users and contributors to understand their needs and incorporate their feedback.

Embracing Diversity: Cultivating an inclusive culture that values diverse perspectives address the #geekproblem. This means actively working to include wider groups in tech and fostering a collaborative rather than competitive environment.

Holistic thinking: Moving beyond the neoliberal framework requires a holistic approach to mediation that considers social, cultural, and economic factors. This includes spaces for dialogue, conflict resolution mechanisms, and support systems for contributors.

Conclusion, to move forward, we need to shed the medieval political structures and #neoliberal individualism to make space to embracing democratic governance, community-centric paths, diversity so that communities can mediate the #techshit and #geekproblem, paving the way for a more collaborative and native #openweb.

ActivityPub and Mastodon from a #closedweb prospective

A #closedweb Critique

  1. Design for Abuse: The #AP protocol is vulnerable to abuse, particularly in terms of Distributed Denial of Service (#DDOS) attacks.
  2. Push-Based Model: The push-based notification model leads to overloading servers, especially when a popular account generates a large amount of activity.
  3. Harassment Concerns: There is a perceived inadequacy in control issues to address the worry of harassment, with issues like the inability to disable replies not being implemented.
  4. Need for Defensive Model: A #geekproblem call for abandoning the working “native” #openweb path and push a “native” #closedweb path, with a complete overhaul of the protocol to incorporate defensive measures from the outset.

The Critique

From an #openweb and perspective, the critique highlights a different mindset that is clearly incompatible with the current path. But yes, there are questions about the balance between openness and security. Let’s not get lost in the #geekproblem and look at them:

Design for Abuse

Critique: The assertion that the protocol is designed for abuse is an overstatement, but it highlights genuine vulnerabilities. The open “trust” based nature of #ActivityPub and the #Fediverse, promotes decentralization and federation, but can indeed be exploited by malicious actors, people do brake “trust”. Transparency in code is crucial. Vulnerabilities should be openly discussed and addressed through community collaboration, most can be fixed by social norms rather than hardcoding. Data sharing is core, there should be as little as possible “private data” to abuse. Protocols should work with slow revisions to improved community feedback. Decision-making processes around security, should be based on social rather than coding, #openprocess is a core part of this.

Push-Based Model

Critique : The push-based model can indeed lead to server overloads. Popular accounts generating a lot of traffic can unintentionally cause DDOS-like situations. This is a normal lossy part of the “native” #openweb, we should work on this. Implementing caching strategies and lossy notification systems should be developed and tested within the community. Efficient data handling techniques should balance ease of hosting and speed of application, with ease of hosting first. Exploring hybrid models (push/pull) with RSS backup can lead to more resilient protocols use. Real time is less important than the app keeps working. Part of this is about ensuring that changes to the protocol are hard and slow, with debate and consensus.

Harassment Concerns

Critique : The constant talking about harassment tools and features such as disabling replies is a concern. Yes open networks are just that open, it’s the social norms of federation that make them a safe space, we need to build up our communes of trust. Developing robust moderation tools and anti-harassment features should balance with building strong social instances, who in the end do the work, be very careful of #closedweb paths in coding these features. Socialise data on harassment patterns helps to improve trust based moderation tools. The stories we tell and the way we work for moderation and anti-abuse measures should be developed collaboratively. Including diverse voices in the social decision-making process for instances is crucial.

Need for Defensive Model

Critique: Starting with a defensive model is the wrong path. Many security and abuse issues can be mitigated with a trust-first approach. A good culture should be built into the core from the beginning, with active community involvement. Developing norms of behaver through community consensus helps build a more resilient system.

Conclusion

The #closedweb path tries to raise points about vulnerabilities and shortcomings of the current #ActivityPub and #Mastodon implementations. From an #openweb and perspective, the solution lies not in suggesting we abandon the native path and implemented protocol but in addressing these issues through open, collaborative, and transparent social processes. By leveraging the strengths of the framework, the community can work to create resilient, and user-friendly networks that are already on the successful native #openweb path.

#mainstreaming counter-cultures

The #mainstreaming of counter-cultures, like the #openweb, #Fediverse, and #Mastodon, touch on issues in openweb culture and the needed community sustainability. It should come as no surprise that we need both action and community to hold together the culture, values and integrity of these digital spaces.

Normalization and Dilution of Values: As counter-cultures like the openweb and Fediverse gain #mainstreaming acceptance, the values and ethos that created these spaces and technology they are based on get diluted, this is the normal. The key community-driven, decentralized, and open-source principles are pushed over by commercial interests and mainstream norms.

Sustaining Cultural Integrity: The challenge lies in maintaining the native culture of these spaces while expanding their reach. The inclusion of diverse voices and broader participation is essential for growth, but it needs to be balanced with the preservation of foundational path for the value to have the maximum impact that we need.

Different Perspectives: The interpretation of #mainstreaming as good, bad, or indifferent varies depending on political and ideological perspectives. For some, mainstream acceptance represents success and broader impact. For others, it signals a loss of autonomy and a clear steeping away from the original path.

Critical Stance: it should be obvious that #mainstreaming without holding the original and #DIY ethos in place is a bad path. There is growing need for vigilance and action to safeguard these spaces from being co-opted and over commercialized.

Participation: Engaging “natively” in discussions on platforms like SocialHub is a path. This participation helps in shaping the future of these open’ish spaces and ensuring they remain relevant and on mission.

DIY : The #DIY (Do It Yourself) is fundamental to the #openweb and #Fediverse. Emphasizing community control, self-reliance, and collaborative development. Promoting and practising this ethos to resist “common sense” #mainstreaming pressures is needed.

Mobilization: Encouraging wide community involvement is essential. Whether it’s through developing new features, creating content, or moderating discussions, contributions sustain the “native” ecosystem, it is at best a “gift economy” path.

The #mainstreaming of counter-cultures of the #openweb, #Fediverse, and #Mastodon is filled with challenges as well as opportunities. With native participation, a strong commitment to #DIY principles, and a collective effort to preserve this native culture, it is possible to sustain and grow these spaces without losing their original path of cultural integrity.

You can find out much more about my thinking on http://hamishcampbell.com, and please try “not to be a prat” thanks.

What names to use?

The term #openweb refers to an internet ecosystem characterized by decentralized, interoperable, and community-driven platforms and protocols. It emphasizes principles of openness, inclusivity, and user control over data and online experiences. The “openweb” contrasts with the #dotcons centralized and proprietary nature, the mainstream internet platforms, thus offering an alternative vision for the future of the internet, and the society this shapes.

Meanwhile, #Fediverse refers to a specific decentralized social networking ecosystem built on interoperable protocols (#ActivityPub), allowing people on different platforms to interact and share content seamlessly. It encompasses a variety of codebases such as #Mastodon, #PeerTube, and #Pixelfed, offering alternatives to centralized social media giants like #Twitter, #YouTube, and #Instagram.

#web1.5 is a more technical term used in geeky conversations, this can be useful as a buffer to the #ecryptionist mess that talks about #web3

Talking about the fediverse can be hard, for broader, #mainstreaming audiences, simply using #mastodon can be sufficient, as Mastodon is one of the most well-known platforms within the Fediverse. This term may resonate more with individuals who are less familiar with the technical nuances of decentralized web architectures but are interested in exploring alternative social media platforms.

The choice of terminology depends on the context and audience. Whether you’re engaging in technical discussions with the “tribe” or introducing newcomers to decentralized internet paths, using the appropriate term can help facilitate understanding and communication.

Tribalism can make this harder than it needs to be, “don’t be a prat” comes to mind.

Cambridge Analytica, 5 years on

I think we face the usual problem of working on and implementing policy for yesterday’s issues.

* We are coming out of ten years of Blockchain mess

* Now we are into #AI mess, the is no intelligence in the current round, only artificial writing.

Let’s look at what actually matters

The original openweb had in this context #opendata is the issue we are talking about.

We then had 20 years of the #dotcons with #closeddata. Which you have talked about.

Coming out of this, we have an active openweb reboot happing with federation and opendata.

For example with #Mastodon, the #Fediverse, #bluesky and #Nosta which have grown from half a million to 10 to 15 million users over the last year. #WordPress building #ActivityPub support for a quarter of the internet and #Failbook‘s #threads.

You are seeing a different world back to #opendata, if you run a mastodon instance you will have a large part of the content of the Fediverse sitting in your database in plan text….

Take this into account with policy and regulation please

#Oxford

#OGB – what is the project

The purpose and vision for our #OGB project is to address challenges and conflicts that currently existwithin grassroots organizations and assist in the management of those that arise. By creating a tool set for’Do It Yourself’ (DIY) governance. We aim to develop a ‘Keep It Simple Stupid’ (#KISS) standard frameworkand process. This will become #OGB which can be used in future solutions, organically evolving throughtime.

Human organization and governance are inherently complex and messy. Standard approaches to solving such, tend to enforce rigid structure. Software built to facilitate this reflects such rigidity – attempting to force messy processesinto being ‘cleaner’, ‘neater’ and ‘tidier’ – and thus through such forced behaviour, inevitably fail their purpose. Existing means of decision making tend to lead to ill-fitting outcomes for the actual problems at hand. Too often led by the loudest voice rather than the most suitable solution. The #OGB serves a real need by addressing these problems. Problems identified through past projects and experiences. #OGB further draws on comprehensive experience gained from greater than five years of active involvement in hands-onorganization within #Mastodon instances and the wider #Fediverse. This experience provides valuable insight into the challenges and obstacles that arise in digital grassroots governance.The #OGB project aims to create a decentralized democratic system for grassroots governance, available for any collective or community, with a focus on producers and consumers. The #Fediverse is used as a test case.This project does not seek to create a single organization that dictates protocols or standards. Rather it enables the organiccreation of synthesis, where competing arguments are broached to formulate corrective procedure and proposals for implementation.The #OGB project emphasizes voluntary collaboration. It prioritizes sortition and ‘messy consensus’ to achieve decision-making and a more equitable power distribution.

The #OGB project is a set of software tools and processes that embody a grassroots activism-based governance model. We envision both an online and offline tool suite to fully embolden accessibility. Specifically, this project has the objective of preventing polarization within online communities whilst obtaining an understanding into how such effects amount. Polarization refers to the division and fragmentation of society into opposing groups with conflicting beliefsand values. Leading to breakdowns and disruptions in communication, increases in hostility, and an eventual lack of understanding between perspectives. The #OGB project aims to counteract polarization by promoting trust-based dialogue and governance within the #openweb.The project provides a framework for open and inclusive conversations, enabling people and groups to engage in meaningful dialogue within common ground and allowing the bridging of differences to be better understood. The project enables active body members to shape their own governance structures using tools that facilitate problem-solving and decision-making.

The #OGB project brings added value and innovation. Leveraging decades of first-hand experience fromgrassroot organizations. In identifying and addressing systemic failures that often hinder social change initiatives. We highlight and recognize valuable knowledge and experiences obtained. Years of endurance should not go to waste, nor be repeated in the field of online governance and trust-based conversations, there are existing initiatives and developments that aim through formal consensus to address similar challenges. However, these initiative shave never worked beyond small expert groups online. Adversely hindering offline activist groups throughloss of inertia and ossification.What sets the #OGB project apart is our focus point. By emphazing learning from past experiences and incorporating these into the development solution, all valuable insights gained are not lost or forgotten. Scaffolding upon this knowledge, #OGB will overcome the common pitfalls and challenges that dilute effective governance and trust-based conversations.The #OGB focusses on building active trust based groups – people who get involved, solve and initiate change to go out and get things done. When a community communicates effectively and efficiently,decisions and right actions come naturally.

The #OGB project also distinguishes itself by emphasizing the importance of recognizing power dynamics within online communities. It acknowledges that the #Fediverse as a decentralized network, operates differently from traditional institutions and mainstream platforms. Instead of trying to conform to mainstreaming paths. The project seeks to embrace the unique characteristics of itself and build with focus having these differences clear in mind. The #OGB brings the #Fediverse notion of technological decentralization, moderation and horizontal scaling into the world of action, organization and governance. Results from #OGB processes may then feed backinto the #Fediverse anew.

The #OGB project aims to achieve several concrete and measurable outcomes:

1. Implementation of natural, horizontal governance: The project intends to establish agovernance structure that promotes horizontal decision-making and empowers a diverserange of voices. This can be measured by the number of participants involved in decision-making processes and the level of inclusivity achieved.

2. Prevention of polarization within groups: The #OGB project seeks to preventpolarization by facilitating constructive conversations and ensuring that decision-makingtakes into account a wide range of perspectives and values. The success of this outcomecan be measured by assessing the level of polarization within groups using the #OGB,KISS framework.

3. Ethical decision-making and progressive development: The project aims to prioritizeethical considerations and focus on the primary needs of people within the community as awhole.

The measure of success here would be the extent to which ethical principles are integrated into decision-making processes and the impact of these decisions on progressive development. The success of this outcome can be measured by the number of people and communities that actively install instances of the #OGB. The success of all of these outcomes will be measured through quantitative indicators such as the number of participants, levels of inclusiveness and adoption rates.

The #OGB project is relevant to a diverse range of people and groups who are interested in alternative technology, open governance, with the vision of creating a more equitable and just society.

Here are some examples of the people and groups that the project is relevant to:

1. Fediverse Users: The project is directly relevant to people and groups who are already part of the #Fediverse, including users of platforms like Mastodon, Pleroma, Peertube and Pixelfed. These users are likely to be interested in the project’s goals of trust-based conversations and governance within the #openweb.

2. Tech Activists: The project is relevant to tech activists who are passionate about promoting decentralized, open-source, and user-controlled technologies. These people can contribute their technical expertise, provide feedback, and help spread awareness about the project within their networks.

3. Social Justice Advocates: The project aligns with the interests of social justice advocates who are committed to creating a more equitable and just society. By involving these people, the project can benefit from their insights, experiences, and knowledge in addressing wider social issues.

To involve people and groups in the realization of the project, the #OGB project will adopt the following approaches:

1. Open Collaboration
2. Community Engagement:
3. Co-creation and Co-design

To effectively reach the target audience, the project can utilize various #openweb native networks, media,and channels.

Fediverse Platforms: The #OGB project can leverage existing platforms within the #Fediverse such as Peertube, Mastodon, Pleroma and Pixelfed. These platforms provide adecentralized and open alternative to mainstream social media, aligning with #OGB values.

Social Media: Utilizing mainstreaming social media platforms like Twitter, Facebook, or LinkedIn can help reach a wider audience beyond the #Fediverse. Sharing updates,announcements, and engaging in discussions can help raise awareness and attract individuals interested in alternative tech and governance.

Development Blog: Maintaining a dedicated blog for the #OGB project serves as a centralhub for information, updates, and resources. Futhermore through publications such as articles, case studies, and success stories to additionally aide understanding and help educate the greater public with an aim to engage a further audience.Online

Communities and Forums: Participating in relevant online communities such as #SocialHub and other forums or activist networks, to help connect with like-minded peoplewho may be interested in the project’s goals and principles.

Mailing Lists and Newsletters: Creating a mailing list or newsletter specifically for the #OGB project can allow for direct communication with interested individuals. Regular updates, project highlights, and opportunities for involvement can be shared via email.

Online Events and Webinars: Organizing online events, webinars, or live streams can provide opportunities for the project team to present their work, share and collaborate insights and engage in discussions with the target audience.

The #OGB project will actively seek ongoing funding. However, once the project reaches a stable state, it envisions a cycle of funding through donations. This funding will be distributed among the project’s foundations and further research and development projects. The project is creating a multi-tier structure where the development stages of each tier will progress sequentially. This implies that as one tier completesits development stage, the next tier will begin. This approach aligns with competent program managementcycles and indicates a plan for the project’s continued development and sustainability beyond the periodcovered by the requested grant.

The #OGB is fundamentally rooted to the open sharing of knowledge and results, including all source codedeveloped as part of it.The #OGB intends to provide valuable outcomes including innovative approaches for governance, trust-based conversations, and democratic decision-making processes within the #openweb and the greaterworld.The code base is not specific to the #Fediverse but can be applied to any community with stakeholders,both on and offline.The project is committed to the principles, which advocate for openness, transparency, andaccessibility in technology.

1. Open data : refers to the availability of data to the public, free of charge and without anyrestriction on its use. This is considered a basic requirement for a project to be consideredopen.

2. Open source : software that is free to use, modify, and distribute. This promotes healthydevelopment and increases interconnectedness, allowing for serendipity. Open licensesare used to ensure the project remains open and free to use.

3. Open standards : technical standards that are open to the public and are not controlled byany one organization. This is essential for the open internet and the World Wide Web, andallows for interoperability between different systems.

4. Open process : transparency and openness of the project’s decision-making anddevelopment process. This can include the use of #Wiki’s and activity streams, and isconsidered a ‘glue’ that binds together the trust based networks that make up a project.

The #Fediverse has developed good technology and social norms around disability and minority groups.The intention is to incorporate these principles into our code base for #OGB project. The aim is to have strong documentation that focuses on consensus building and horizontal processes, which will promoteworking diversity among people with different abilities. The project plans to prioritize the development ofcomprehensive documentation for further use within instructional design as an aide for education and training. These principles are the core process of the project. This indicates a commitment to inclusiveness and accessibility within the #OGB project. The #OGB code and documentation is to be designed with accessibility as a first-class citizen, being compatible across everything we currently utilize with existing norms. Screen readers are a perfect goal toset our mind to.

Team Founder – Hamish Campbell: Hamish has 30 years of experience in building and running grassroots socialtech projects. He has been involved with projects such as Undercurrents, Visionontv, and the #OMN. Currently he is working on multiple projects within the SocialHub community, including outreach of ActivityPub to the European Union. Hamish has a strong understanding of what works and what doesn’t inboth social and technological contexts.

Founder/Lead Programmer – Saunders: Saunders is an experienced software engineer with expertise in C++, Python, and other programming languages. He has been responsible for managing the Linux-based #OMN servers for the past 5 years. Having a foundation in permaculture design and training, his programming skills have been utilized within grassroots social aid projects across several continents.

Project Manager – Nicholas Matheson: Nicholas has more than 20 years experience in project management, initially focusing within the hotel/tourism and hospitality sector in Australia/New Zealand. Hebegan consulting in China following the Beijing Olympics. Pursuing training and development workshopsacross the sector and the creation/assistance of importation logistics following client’s recommendations.

Privacy – As stated within the ‘Security’ section the project emphasizes a clear separation between personal and public communication. Being a project with an #openprocess at its core, we will not be handling private data outside of passwords. Additionally, the project plans to support pseudo-anonymous accounts via Tor usage. These accounts will operate on a trust-based system similar to any other account within the project. This approach highlights the project’s commitment to transparency and privacy while providing options for users to engage with the platform in a way that aligns with their chosen preferences.

The #OGB project will involve activities that contribute to the intended outcome of developing improved ways for trust-based dialogue, governance, and problem-solving within the #openweb. These activities include:

1. Developing a Framework: The project aims to create a framework that demonstrates improved ways for trust-based dialogue and governance within the #openweb. This framework will provide guidelines and principles for fostering open and inclusive conversations, decision-making processes, and governance structures.

2. Building Cooperative Alliances: The project seeks to establish a true cooperative andcollaborative alliance that is native to the #Fediverse and #openweb. These alliances will bring together people and groups who share a common vision of promoting trust,openness, and decentralization within online spaces.

3. Recognizing Power Dynamics: The project emphasizes the importance of recognizing where power originates in the context of the #Fediverse and #openweb. By understanding power dynamics, the project aims to challenge and change vertical power structures,promoting more equitable and democratic forms of governance.

4. Developing Technological Tools: The project aims to develop improved technologicaltools that address problems arising from social organization within the #openweb. These tools will enable problem-solving in a native grassroots activist manner, empowering people and groups to navigate and shape their online and offline experiences.

5. Removing Hard Coded Defaults: The project seeks to remove current hard-coded defaults by providing a standardized set of KISS (Keep It Simple, Stupid) tools. These tools will empower active body members to utilize them deeply and instruct others on their use,enabling more flexible governance structures.

6. Permission-less Structure: The project aims to create a permission-less structure allowing the active groups to decide who is a part of their group or groups, promoting inclusivity.

The signal to noise issue of our #geekproblem

#Mastodon and the wider #fedivers are native #openweb project based on the people who try to “harden” and “secure” these are completely missing where the value is at.

They are spreading #FUD and endangering real activists acting this way.

Media is “open” using #ActivertyPub.

Anything that is not media should use encrypted p2p chat, there are many mature #FOSS projects for this.

At the moment as the #Fediverse is a #OMN based on the you have very low barrier to running or even developing an instance, this is where the value is.

Adding security generally makes a HUGE barrier to Dev and #DIY running an instance.

The #geekproblem has no idea of the damage they do when pushing their “common sense”. This creates a signal-to-noise issue that has been blocking alt for 20 years.

 

A project outline for the OGB

Project description

The Open Governance Body (#OGB) project is a set of software tools that encode a governance model structured on traditional grassroots activism.
Further, the OGB – for which the code base is named – is a decentralized and democratic system for “governance” of any collective/community consisting of (generally speaking) – Producers and -Consumers.

The #Fediverse is used as the example herein.

To explore and develop better ways of having trust-based conversations and governance within the #openweb. To utilize comprehensive experience gained through greater than 5 years active, “on-the-ground” organization of instances within the #Fediverse as a technological toolkit for horizontal scaling of social
power.

The #OGB is a #Fediverse native process of working that emphasizes voluntary cooperation and collaboration with a standard #KISS approach.
The #OGB prioritizes focus on sortition and “messy consensus” in order to achieve decision-making and equitable power distribution.

The project is not about creating a single organization that dictates what protocols and standards to use within the #Fediverse. #OGB is about developing better processes for healthy, trust-based conversations and forging governance
accessible and equitable to all

Project results

Developing/creating a framework to demonstrate improved ways for “trust” based dialogue/conversation and “trust” based governance within the #openweb.
Building a true cooperative, a collaborative alliance that is native to the #Fediverse and #openweb.

Emphasizing the importance of recognizing where power originates in the context of the #Fediverse and #openweb.

Developing/creating improved technological tools as a solution to problems arising through social organization enabling problem-solving in a native #openweb manner.

Removing current hard coded defaults by providing an alternative standardized set of #KISS framework tools to empower active body members a space to utilise said tools deeply and to begin proficient instruction of their use.

Developing/creating a permission-less structure that is open to and for all. One which enables the active group through organic process, a framework of tools to decide who is a part of their group/groups.

Emphasizing that there is no exclusion and that there will always be diversity, making it an organic piece for the #Fediverse.

Building governance where the “way”, “rules”, “norms” and “actions” are structured, sustained, regulated, and held with accountability

Benefits to the Community

There are challenges and conflicts that arise within grassroots organisation or #DIY governance. In developing/creating a #KISS standard such as the #OGB framework to address said problems, we will enable a more true democratic and equitable process that benefits any and all involved.

Through empowering a more diverse scope of voices, decision-making is made more collectively. These tools utilize a greater range of voice, preventing polarization from smaller groups using perhaps limited perspectives and or values.

Additionally, through a strong ethical foundation, decision-making is ensured a more progressive development. With a focus on the primary needs of the community as a whole, rather than individuals or polarized groups.

As a social coding project, the #OGB is neither a traditional top down distribution of power or project derived of a normal #mainstreaming agenda. Rather, it is a bottom-up grassroots empowerment for sharing of knowledge and power. An example of what is found in many of the 20th century social movements,
movements responsible for the birth of what is said to be today’s best current progressive mainstream.

Through the #OGB project the “we” will facilitate the forming, communication and governance.

Timeline and important milestones

Upon securing foundation funding, negotiations for immediate ICT services will begin with respected clients for future partnership to cement project longevity and sustainability.
As described above within the KPI outline, the progression of timelines is a basic and #KISS standard
project operation where in all tasks/tiers are realistically achievable to ensure project success.
The following is an initial outline – it can be extended when possible:
9 months to Alpha testing with #Fediverse
12 months to Beta testing with #Fediverse
12 months to Beta testing with offline communities
24 months to public launch

Key Performance Indicators

Tier 1 – Source code development from base developers and progressive training through the scaling of
outreach servers through the use of MOOC LMS training platforms.
Beginner – Test Community… Local Distribution – Flea Market,Sunday Market – APP Progressive Code
9 months to Alpha testing within Fediverse
12 months to Beta testing within Fediverse
Tier 2 – Test Community… #Fediverse – Web Code
Page 4 of 8
Intermediate – Test Community… Local Distribution – Boating Community,Hiking Community – APP
Progressive Code
Tier 3 – Progressive Web App
12 months to Beta testing with offline communities
24 months to public launch
Tier 4 – The below distributions are escalations through our developed outreach scheme.
Advanced – Test Community… Local Distribution – Schools/classrooms

Project publicity

Utilizing the recent promotion of approximately 10 million people encompassing 1 million active Twitter migration users to #Mastodon to further bring awareness.

The continuance of our work within #SocialHub will continue to build on the origins of #OGB Promoting publicity through the building “governance” through #ActivityPub

Why you

We would like to reboot the #openweb and the way we communicate, interact and govern as a whole.
We know what works socially… grassroots movements
We know what works technologically… #Fediverse
We are the people developing the symbiosis for all to utilise for our futures

Activities that will benefit

FOSS and open-source frameworks are facing a continual social challenge of balancing their grassroots paradigm within corporate parameters. #OGB aims to develop/create a set of tools to encourage and aide balance.

The efforts of the #Fediverse community have been successful in shifting the EU closer through our outreach to promoting a more humane internet. #Mastodon and technologies like #ActivityPub have become important players in the EU’s initiatives for a more inclusive and equitable online environment.
The huge growth of Mastodon, one of the most popular social networking platforms in the #Fediverse, due to the #Twitter migration attracted a large and diverse, vibrant community of users from across the EU and
the world. This growth helped to validate the importance of decentralized internet and its potential to shape a more humane world by relieving the community of hosting burdens so we can focus on collective
governance and the formation of a collective governing body for decentralized efforts

  As the righwing is failing, the mess is growing in the left…

What #mastodon is doing now is going to lead to a lot of mess, duo to people squabbling. This might or might not be a level of mess that negates the vertical move to “simplicity” of a single codebase and a single instance. That would be a waste… and it was the king and his https://en.wikipedia.org/wiki/Favourite that are pushing this mess, good not to get confused about this part.

This is actually the same as the #NGO mess we see in #XR at the same time

As the righwing is failing, the mess is growing in the left…

Why is Mastodon so dominant in the fediverse?

Q. Why is Mastodon so dominant in the fediverse?

A. It had better #UX and @Gargron running it was an effective communicator at #KISS and built it out as a project alongside a healthy (white) lie about security and privacy.
The rest of the projects lacked these things – #Pleroma the obverse compaine was ripped apart by the #geekproblem then embraced by the right-wing. #Peertube was stuck in a good but closed development for years. #Pixelfed is a little brother project to #mastodon. Then there are a whole flood of #NGO funded projects that have no community.

Might be useful to see it as we’re having a “KING” problem, then the rest are #feudalism all the way down. This should be easy to fix as its and all #openweb, but it’s not. Just about everyone is hard #BLOCKING the obvuse need for “democracy” as a path out of the mess #OGB

How is the #NOSTR world doing on this?

Libertarian #Fediverse “cats”

This story is about a group of libertarian #Fediverse “cats” who convinced one of the largest and most bureaucratic institutions, the European Union, to embrace decentralized and #openweb technologies. Through outreach efforts, EU-sponsored events and advocating to policy-makers, they raised awareness of the benefits of decentralized models of the internet and the positive impact this has on creating a more equitable and sustainable online environment for European citizens.

As the #Fediverse, #Mastodon, and #ActivityPub continues to rapidly grow in popularity, the #openweb cultural values at the heart of this outreach have been validated. Through continued grassroots community building and outreach efforts, radical activist have the potential to empower users and promote an inclusive, equitable, and sustainable online environment for all of us.

Please help tell this real life story https://socialhub.activitypub.rocks/t/eu-outreach-if-we-dont-tell-our-story-am-not-sure-who-will/2950

 

A fresh look at #openweb history

For people who like buzzwords

The World Wide Web is a system of interlinked hypertext documents that is accessed through the Internet. #Web01, #Web02, and #Web03 are terms that are used to refer to different generations or phases of the World Wide Web (#WWW).

#Web01 refers to the early days of the World Wide Web, when it was first introduced in the late 1980s and early 1990s. During this time, the web was primarily used for academic scientific, #NGO’s hobbyists and activists purposes and less yet widely adopted by the public.

#Web02 refers to the growth and expansion of the World Wide Web during the late 1990s and early 2000s, as the web became more accessible and user-friendly, and was increasingly adopted for commercial purposes. This era saw the rise of #dotcons, characterized by the growth of social media, mobile devices, and cloud computing. The web had become increasingly interactive and interconnected, and has become a critical tool for communication, misinformation, social control and commerce.

#Web03 was a waste of space, focus and money by the #Encryptionists who in bed with the scammers produced meany still born tech children in the last 10 years.

#Web01.5 refer to an intermediate stage between Web01 and Web02, marking a transition between the early and more experimental phase of the web and its more widespread commercial adoption. Web01.5 refers to a time when the web was still growing and evolving, but had already become more accessible and user-friendly, and was being adopted for more diverse purposes. With #mastodon and the #fedivers over the last 5 years, we are rebooting this web01.5 stage.

The patriarchs of the early #openweb