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 #4opens 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 #4opens 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?

The #hashtags embody a story and world-view

My use of #hashtags is confusing a lot of people, good to have some signal in the noise on this subject https://en.wikipedia.org/wiki/Hypertext am using them in the way the #WWW was designed to use them #KISS

The #hashtags embody a story and world-view that are rooted in a progressive and critical perspective on technology and society. They highlight the negative impact of neoliberalism (#deathcult) and consumer capitalism (#fashernista) on society, and promote the original ideals of the World Wide Web and internet culture (#openweb). The #closedweb hashtag critiques the for-profit internet and its social consequences, while the #4opens promote the principles of transparency, collaboration, and sharing in open-source development.

The #geekproblem hashtag draws attention to the cultural movement of geeks, who can become blinded by their own technical knowledge and fail to consider the broader social implications of their work (#techshit). The #encryptionists hashtag critiques the dominant belief among some geeks that all solutions need more encryption, which can lead to a desire for total control and artificial scarcity.

Overall, these hashtags are interlocking and tell a wide-ranging story and world-view that advocates for a more humane, collaborative, and transparent approach to technology and society. The #nothingnew hashtag raises the question of whether new technological projects are needed, or whether we should focus on improving existing ones. The #techchurn hashtag refers to the technological outcome of the #geekproblem, which can lead to a constant cycle of new projects that do not address underlying social issues. Finally, the #OMN and #indymediaback hashtags promote the idea of an open media network and the rebooting of the altmedia project that was once the size of traditional media on the #openweb. The #OGB hashtag represents the need for open governance and the power of community to make decisions collectively.

#SSB splintering a “commons”

Another link that is pure #geekproblem but interesting for #OMN in that #SSB is splintering https://www.manyver.se/blog/2023-04-05

@rabble is involved in another splinter #nosta

How protocols die… #SSB was a protocol that they all reallyed round, a “commons”, we now have 3 “commons” on the table. The rabble one which has hidden #VC money behind it, then this individualist one https://www.manyver.se/blog/2023-04-05 which will maybe rally the grassroots, and the original #SSB which might or might not carry on.

We don’t have a cross culture “common” any more. A clean separation of the #mainstreaming and the #grassroots. To make this relevant, the same is likely going to happen to #ActivertyPub when the #W3C “formal consensuses” is captured by the #dotcons

The enclosure of commons is always a bad path. And yes not saying #SSB was a good protocol it was not, it came from the encryptionsists, but it was a rare “commons”.

#AP is a good/bad protocol, we don’t need to do the same path. Thus, the message to #socialhub, 95% chance they will ignore it or more likely see it as weakness and attack harder, cats…

“The is currently an undeclared battle going on between the rebooted #WC3 and the grassroots (#fashernista dominated) #socialhub for power. If the libertarian cats can’t herd themselves to do something useful, like we managed with the #EU outreach – currently they cannot do this, have a feeling socialhub will lose.

Not a big problem, but a dangerous outcome for #ActivityPub as #WC3 is formal consensus which is easy to capture and control for the #dotcons – where socialhub libertarian cats have failed messy consensuses so less open to capture.

But from my view the libertarian cats are being prats as cats are… so WC3 is stepping back in to CONTROL… how to herd cats – should I try? Or keep focus on #OMN codeing is a question am asking my self?

@xxx @xxx@xxx, have tried building bridges, but no foundation stones laid on this building work. Honest question are we helping or hindering in this grassroots space?”

There is a small chance they act, we did herd cats on #socialhub for the #EU outreach. This is why I bring it up, though, think people can only see the power politics and not what am saying when doing this. Agen 5% chance of a good outcome…

Maybe this helps to make the “mess” metaphor clearer. For the #geekproblem they likely have no idea about the damage they do. Because in their terms they are mostly right. Step back to look at the wider picture, and it’s obviously adding to the mess to be composed.

The #geekproblem

Storeys of our tech http://hamishcampbell.com/2023/04/05/ssb-splintering-a-commons/ a post that give background on #SSB and its splintering as an example.

Why this matters, the #openweb is the most powerful tool for change/challenge. The mess we are in The moral depravity of virtue signalling solidarity at this time of mass murder – Roger Hallam The moral depravity of virtue signalling solidarity at this time of mass murder

 

A native path out of the mess people make on the #openweb

The Open Governance Body (#OGB) describes a permissionless process/structure that is open and allows the group that forms using the tools to decide who is a part of the group or not. This process can divide into a web of connecting instances of governance as a natural human process of group formation. The #OGB emphasizes that there is no exclusion and always diversity, making it a natural fit for the #fediverse.

The #OGB also shows that if people are stupid and focused on individualism, each governance instance will have one member and no power. To gain power, people have to work together, which is built into the code. The #OGB emphasizes that hoarding power is limited, and it flows through the community, energizing and solidifying the community and building horizontal power to challenge/change vertical power.

The #OGB focus is on the importance of keeping things simple (#KISS) and that some people will try to push for existing power structures before democracy. However, as the process is permissionless, it is not possible to stop them from doing this. The #OGB emphasizes the need to do better, and that being native to the #fediverse is a big help in this regard.

The #OGB emphasizes the importance of recognizing where power comes from in the context of the #fediverse. The fediverse operates differently from corporations, governments, courts, and police, and it is important to think and build with this difference rather than trying to drag the fediverse back to the #mainstreaming path.

The #OGB builds from the #fediverse works because it is different, and it is easy to forget this important thing when #mainstreaming agendas grab and hold. The #OGB suggests that the missing question in almost all conversations is “who are we empowering,” and emphasizes the need to do better in alt-tech.

The #OGB notes that there are problems in alt-tech and suggests that starting with the #4opens would remove 90% of the mess, revealing the real potential for good outcomes. The #OGB highlights that doing better in alt-tech would involve using shovels to make compost and planting seeds of the world we want to see.

The #OGB describes the process scaffolding for the governance body as a default effect, where the decisions on how things work will be up to the members of the body. The power of the governance body is only the power of default, and the #OGB is about removing all hard default choices and building in a small number of KISS tools, then letting the body members work out themselves how to use them.

The #OGB uses the example of #Couchsurfing, where the website redesign removed the #DIY tools active Couchsurfers had used to self-organize, leading to disappointment among members. The #OGB argues that letting members make their own process, open vs. closed, is necessary to overcome the #geekproblem and have hope for alt-tech.

The #OGB builds governance with the way, rules, norms, and actions are structured, sustained, regulated, and held accountable. this is to mediate that the #Fediverse currently has a “herding cats” governance, denoting a futile attempt to control or organize a class of entities that are inherently uncontrollable.

The #OGB codebase is not just a tool for the #Fediverse, but it can be used to democratically run any structures that have stakeholders.

The #OGB provides an example of how the codebase can be used to run a local street market, with each stallholder as a stakeholder, people who shop at the market as users, and the local council, events company, and shop owner’s association as affiliate groups. The #OGB approach and codebase will scale sideways, with street markets governed city-wide, and each of the markets becoming a stakeholder, users as users, and city-wide orgs and groups as affiliate groups.

The #OGB shaping of the “body” comes from a long history/experience of horizontal activism, where “those who do the work have more say.” noisebridge.net/wiki/Do-ocracy

The #OGB pushes that the bulk of the voice comes from those who run the #Fediverse, the people who run/support the instances. The people who build the tools also get a say, as do support orgs and events, and the users who will be spread widely get a say, but their power is diluted by the much larger numbers involved.

This working practice comes from 30 years of building from The Tyranny of Structureless tick box list https://unite.openworlds.info/Open-Media-Network/openwebgovernancebody/wiki/03.-The-Tyranny-of-Stucturelessness That code being quite “anti-human” is an interesting challenge, and it’s important to figure out how to get the humane “mess” in a coding process that is based on being “exact” and in control #OGB

The #OGB project is grounded in lived experience, and it’s a way out of this mess. We cannot keep using traditional institutions. We have to stop the #techcurn if we are going to use #openweb tech for social/ecological change/challenge, and we need to think about this now.

The #OGB project is about developing better ways of having “trust” based conversations and “trust” based “governance” in the #openweb. The project is built from hundreds of years of on the ground organizing that has shaped every “freedom” we enjoy and is done in a #KISS approach. The #OGB is a #fedivers native way of working, NOT a #mainstreaming way, and it comes from directly working, setting up, and solving recurring problems at hundreds of direct action protest camps.

The #OGB focus on what we know works, as at the moment, almost nothing works for social good. The #OGB project is what is needed, a voluntary cooperative and collaborative alliance that is native to the #fediverse.

The thinking is that we need to put a stop to the #techchurn as we have piles of #techshit already to compost, that #nothingnew is a hashtag for this.

It’s not the goal of the #OGB project to create an organization that tells everyone what protocols and standards to use in the #fediverse. The #OGB project is about developing better ways of having good “trust” based conversations and “trust” based “governance” in the #openweb

To sum up, the current working models of “governance” in open-source projects are monarchy, aristocracy and oligarchy. This is the rock star developer, the coders and the funders. It should be obverse to anyone that 99.99% of people are missing from this feudalistic ideal of “governance”.

Democracy is the basic foundation of our shared modernity.

WHY DO WE PUT UP WITH THIS MESS IN TECH?

Let’s take a different path, please #OGB

Q. that is an optimistic projection

A. I have no illusion that the normal shitty behaver of fucking people over and being a prat will happen, but the codebase is designed to mediate this crap behaver for better outcomes 🙂

#OGB “permissionless” is an important word that needs some thought. The body is made up of three different, balanced groups: stakeholders, users, and affiliate stakeholders. Anybody can become a stakeholder by setting up and running an active instance, and users are self-explanatory. That affiliate stakeholders are a little more complex and are treated differently, and it’s up to the body itself to decide if they play an active and useful role.

That nothing in this is top-down, elitist, discriminatory, or undemocratic, and it’s #KISS and looks safe to the “normal world” while being native to the #fediverse and its roots. All the coding is #4opens, based on #activertypub.

With #OGB, it’s important not to get lost in the #processgeeks and their dogmatic love of #formalconsensus, as that’s a dead end and has been for the 30 years of activism and coding tech. It’s important to keep the #OGB both #KISS and human, understandable. The #OGB is native “governance” and federates in the same way as the projects it “governs”. That this approach is counterintuitive to mainstream ideas and “common sense,” but that’s not necessarily a bad thing.

This approach has worked to some extent, as seen in the “#Fediverse” as a living example, working to scale small to bigger. There will be lots of “smoke,” and help is needed to keep the project clear of this mess. We have to overcome our #stupidindividualism to have a hope of a better world.

#OGB To remind you that the need for “governance” came out of a practical problem where the #activitypub community is made up of “cats” who were doing seminars outreach to powerful #EU Eurocrats on why they should be interested in #activertypub. #OGB is designed to be messy and not tidy, and it’s a “governance” of a disorganization, not a traditional power structure. “governance” can cooperate with more formal models of governance like traditional cooperatives.

My indymedia story

This is a DRAFT

Indymedia was a decentralized, grassroots media network that emerged in the late 1990s and early 2000s. It was founded on the principles of open publishing, direct democracy, and anti-authoritarianism. The project eventually experienced a split in the UK, with one side, the #fashernitas building an aggregating site and the other #geekproblem building a centralized silo. The split was supericaly over technical disagreements, but was driven by doctrinal and tribal disputes. The decision-making process, which relied on #formalconsensus, had become ossified and unfixable, so no decisions could be make any more to mediate this.

The split was ultimately driven by a focus on control on both sides. The two sides were more interested in their own tribal agendas than in working together to build a diverse and #4opens #OMN. The silo eventually built an aggregating site, with RSS feeds, but in a very controlling way. The stress was always on control, and this ultimately led to the decline of the #Indymedia project. The #dotcons took over the space, and the project became irrelevant.

I was working on the project, the person working in the middle saying “don’t be a prat” as each side tore and tore and tore I continued in the grassroots, saying that the culture is the key and that the value is in open media network, not control. The split in Indymedia was a shit show, but we can learn from it in the reboot.

The plan now is to reboot the project before the split happened, around 2008 with a focus on the #fashernitas path of the splinter groups. This path emphasizes openmedia and decentralized structures, rather than control and centralization. However, with the reboot there is still a very real risk that some members of the community will push for a control/encryptionist path, which could lead to another split in focus. The challenge is to find a way to walk this path without succumbing to the same tribalism and and power politics that led to the decline of the original project.

The use of hashtags and semantic web technologies did not exist at the time. Tags and metadata were not core to the start original Indymedia project, but they were later being added as a way to help organize and categorize content, the idea of building a structure with #RSS feeds was being discussed and enacted.

At the time, Interestingly, the silo path recognized that their approach was wrong and came back to aggregation, with moderated control of RSS flows. This is reflected in the #OMN’s choice of “trusted flow” and “moderated flow.” We are building both sides of the split of the original project and yes, criticizing the fashernista path a little, which only had trust, which would not likely work at all in today’s world. It’s important we do not make this decision for people. We let them decide and build both. The key is to avoid building pointless messes and to resist the #mainstreaming urge to make a mess. We are not mainstreaming, and we must not be prats about this.

Looking at what happened to the web after this time, the last ten years of tech history, the grassroots silo path went on to build #Diaspora, while the grassroots #fashernista path went on to build the #Fediverse. However, despite these developments, there was still no news based open media network being built yet. This led to the creation of the #OMN and the current #indymediaback reboot.

Unfortunately, in today’s world of liberation “cats” due to the last 20 years of the #deathcult, nobody sees any value in the “open” part of the #OMN. Everyone is still fixated on the silo path of control, we have to work against this #mainstreaming blindness. Over the last 20 years, the #mainstreaming as a whole took the silo/encryptionst path of the Indymedia split. Contemporary social media took #fahernista side of the #open path, the #dotcons, took the ideas and sold us back a facsimile of this that they could control, such as Facebook and other algorithms base #dotcons

To make the reboot work best, we have to tiptoe around the legacy of #Indymedia, focus on rebooting the project ain its 2008 state, where the social process were still working. The silos’ path control the old domains as they took as a part of the ripping. We are building something that looks like the fashernista path they fought against, so we need to build two projects in one: control and trust. We need to get the domains back in use, which would be a huge boost to the #reboot project. At the same time, we need to build trust with everyone else, as this is the power of open. It’s complicated, but everyone wants it back. However, the history is challenging, and the two sides are still fighting: fedivers vs. silos as we see this old mess today.

Were do fads come from on the #openweb

Thinking about the current fad for static sites,

A static site is a handwritten book, it’s a feudalistic form of technology.

A dynamic site is a printed book, a modernist form of technology.

The #geekproblem is based on feudalistic governance, kings, princes, nobals and pesents. This is why they like static sites, it’s native.

I like hand made https://en.wikipedia.org/wiki/William_Morris am not agenst static sites, rather am thinking of why.

The #geekproblem mess we make of #openweb funding

#NGIzero #NGI #EU It’s important to remember in #openweb tech that most funding is poured directly down the drain, all value comes from #DIY culture which is always underfunded. Would be a good idea to try to rebalance this mess. And yes, we are not talking about the #dotcons mess, that’s another subject 😉

The value we are all talking about, the #openweb #fediverse based on #activertypub is a very good example of this issue. The group that pushed through the speck only goes through the formal consensuses process because the #dotcons were not interested in owning the outcome as it had no “value” to them. The speck was done as unpaid, unfunded #DIY labour, this is where almost all value actually comes from when you lift the lid on the current mess.

The importance of #DIY culture and the underfunding of #openweb technologies. It is true that much of the value in openweb technologies comes from the grassroots efforts of individuals and communities who are passionate about creating and maintaining these tools. This can be seen in the case of the #fediverse, which was developed by a group of volunteers who were committed to creating a decentralized and open social networking platform.

At the same time, it is also important to recognize the role that funding can play in supporting the development of openweb technologies. While it is true that much of the value comes from DIY culture, funding can help to support and sustain this culture, providing resources and support to help communities. One initiative that is working to address this issue is #NGIZero, which is a program funded by the European Commission to support the development of #openweb technologies. Through this program, funding is provided to support projects that are focused on creating often #NGO focused decentralized and #geekproblem projects.

Overall, it is important to recognize the importance of DIY culture and grassroots efforts in the development of openweb culture and technologies. At the same time, we should also work to support these efforts through funding and other forms of support, in order to help ensure that these grassroots cultures and the technologies they build continue to thrive and evolve in the years to come.

Talking about trust and power in networks

A. on the subject of “security” we have a #open policy of not trusting ANY client server security at all, so this should only be done #4opens as far as possible and having limited trust in #p2p security, even though we use this, because of the insecurity of the underlighting syteams it runs on, mostly old outdated phones, built as blobs by #dotcons this simple approach gets round much of the current thinking of technical “security” ie. the is almost non at a normal use level and little real security at the paranoid level as you will be talking to the normal level so there security will fail even if yours is solid. good to keep this in mind 🙂

The #OMN is all about people messing around with each others data 😉 but yes we need good basic security, (sudo anomumus) accounts, public audit trails (openprocess) everywhere. we will need digital hashes/cigs for media items etc. but the data it self just sloshes around and gets hacked at and added to. its a commons, the rules are social based on trust flows, they are not mostly hard coded or encrypted. but we add a smidgen of hardcoding and decryption ONLY were its needed. So 90% trust flows, 5% social norms, 4% hardcoded, 1% encryption is my thinking.

A. Data has the value the instance itself is transitory, and yes the instance is needed and stores the data but if it vanishes it has little impact on the value (the data), we build this into the network.

Q. am talking about the machines

A. We won’t the instance to stay up and be secure, BUT we build the network, so it keeps working when they are hacked and poisend by bad actors.

Q. Yes, but that doesn’t mean we make things easy for bad actors

A. Yes, the code and instances have to be secure, but the network flows, and the data soup have to keep working when the individual instances are hacked and poised, no security is fool prof and the #OMN is focused on building trust so is inherently more open to fools, we build with this in mind. We are building a #KISS semantic internet of data/flows. For example the idea of rollback as a core security model rather than more traditional hard (control) security is a good fit, due to the #4opens approach, the missing few days of data will (mostly) rollback into the instance so the cost of being hacked/trust failed is less of a block to being open and (social) trusting to bring in actors/sysadmins/moderates etc. On the tin, we are clear that our network is a trust based “lossy” network.

Where you can still run the #OMN as a hard control based secure network if you wont BUT it will not scale to the social change/challenge if this second option is the only one, this is the current #geekproblem we need to work our way out of. The first path of trust based “lossy” is where the real horizontal “power” comes from.

Q. We sometimes need to think/talk about “security”.

A. I can only repeat I don’t have a solution to this, but I have a path to one, make the user facing “trust” based then from this, “trust” them to fix the next “problem” the #geekproblem of the hardcoded #feudalism of all our networks and code. Or in other words head in sand and pray someone else will fix it, am bussey 😉

On the #OMN projects maybe we need to list what needs to be secure: the account, the activity feed, the data credit might be more but can’t think of much else off the top of my head. And yes to secure the account the instance has to be secure, to secure the activity feed the flows need to be secure, to secure the credit the likely needs to be some hashing done on the media objects.
We likely end up back close to the place we started, but we come to this from a very different place, if that makes sense. This path we take matters.

The solution to the #geekproblem

One of the ways the world of technology is in a mess is due to the problem with institution’s limited funding of the social side of #openweb. Unfortunately, much of the funding that is given ends up feeding parasitic NGOs, which does little to nothing to solve the problems. The existing funding for functional coding also contributes to the #geekproblem by not pushing anything outside the basics. It’s up to people with shovels to clean up this mess, but the question remains – who funds them?

Technology has become an important part of our daily lives. We rely on the internet for everything from communication and entertainment to work and education. However, despite the many benefits that technology offers, there is a growing problem in the industry. Many of the software programs that we rely on are failing because they are built on the wrong foundation.

The #geekproblem software that dominates the tech industry today is built on a foundation of “control”. Developers focus on creating systems that regulate the user’s experience, from how they access information to how they interact with others. However, what many fail to realize is that good societies are built on a foundation of “trust”. When we trust the people and institutions around us, we are more likely to cooperate and work together on common goals.

Unfortunately, the current commercial approach to technology development is leading to piles of #techshit. People don’t trust these #dotcons programs, and they don’t trust the people who create them. This lack of trust can lead to a breakdown in society, that is accelerating the break-down of our environment

The problem is compounded by the fact that the tech industry struggles to communicate this simple understanding to the wider public. Developers are so focused on narrow #geekproblem agenda, technical jargon and complex systems that they often struggle to explain their ideas to others.

One way to address this problem is to fund the social side of tech. By focusing on the human aspects of technology, we can create programs that are not only technically sound, but also easy to use and trustworthy. We need to bridge the gap between the technical and social aspects of tech and create a more holistic approach to technology development.

However, there are very few institutions that fund the social side of #openweb tech. Many of these institutions focus support on parasitic #NGOs that don’t understand the technical side of things and are not interested in building trust. If we continue down this path, we will only feed the #techshit pile.

To make a difference, we need to fund the social side of tech in a way that supports both technical expertise and social understanding. We need to create programs that are not only technically sound but also easy to use and trustworthy. We need to invest in initiatives like the #OMN and #4opens that promote communication, cooperation, and trust within the tech industry.

Ultimately, the solution to the #geekproblem is to realize that good societies are built on trust, not control. We need to build technology that reflects this reality and invest in the social side of tech. By doing so, we can ensure that technology continues to serve us and not the other way around.

The problem with institutions funding the social side of #openweb tech

Almost all our #geekproblem software fails because they are building “control”, where all good societies are built on “trust”. We keep making piles of #techshit because we can’t communicate about this simple understanding #techchurn one way to address this is to fund the social side of tech.

The problem which we need to solve is the institutions funding of the social side of #openweb tech, if we do this now most of this funding will feed parasite #NGO’s rather than anything useful. This is also a problem of the existing funding for coding, it pushes the #geekproblem when it funds anything outside the basics.

We have a mess because our world is messy, current funding plays little role in composting this mess.

That’s the job of people with shovels – who funds them.

Most of our software fails because it is built with a focus on “control”, rather than “trust”, which is the foundation of a good society. This leads to an endless cycle of creating useless technology that we can’t communicate about. To address this problem, we need to invest in the social side of technology.

The challenge lies in funding the social aspect of #openweb technology. Currently, most funding goes to non-governmental organizations (#NGOs) that are not always effective. Additionally, the existing funding for coding primarily focuses on the basics, which perpetuates the problem of the #geekproblem.

Our world is messy, and the current funding plays little role in cleaning up this mess. People with shovels – those who do the work – need funding to make a difference.