Open Thinkering

Menu

Tag: governance

Defederation and governance processes

I’ve noticed this week some Mastodon instances ‘defederating’ not only from those that are generally thought of to be toxic, but also of large, general-purpose instances such as mastodon.social. This post is about governance processes and trying to steer a way between populism and oligarchy.

The first thing I should say in all of this, is that I’m a middle-aged, straight, white guy playing life on pretty much the easiest difficulty level. So I’m not commenting in this post about any specific situation but rather zooming out to think about this on a wider scale.

What I’ve seen, mainly via screenshots as I rarely visit Twitter now except to keep the @WeAreOpenCoop account up-to-date, is that Elon Musk has run some polls. As others have commented, this is how a Roman Emperor would make decisions: through easy-to-rig polls that suggest that an outcome is “the will of the people”.

Tweet from Elon Musk: "Should Twitter offer a general amnesty to suspended accounts, provided that they have not broken the law or engaged in egregious spam?"

Yes 72.4%
No 27.6%

This is obviously an extremely bad, childish, and dangerous way to run a platform that, until recently, was almost seen as infrastructure.

On the other side of the spectrum is the kind of decision making that I’m used to as a member of a co-op that is part of a wider co-operative network. These daily decisions around matters large and small requires not necessarily consensus, but rather processes that allow for alignment around a variety of issues. As I mentioned in my previous post, one good way to do this is through consent-based decision making.

Screenshot of the Loomio for social.coop with multiple discussion threads

Using Loomio, the social.coop instance that I currently call home on the Fediverse, makes decisions in a way that is open for everyone to view — and also for members of the instance to help decide. It’s not a bad process at all, but a difficult one to scale — especially when rather verbose people with time on their hands decide to have An Opinion. It also happens in a place (Loomio) other than that which the discussion concerns (Mastodon).

So when I had one of my regular discussions with Ivan, one of the Bonfire team, I was keen to bring it up. He, of course, had already been thinking about this and pointed me towards Ukuvota, an approach which uses score voting to help with decision making:

To “keep things the way they are” is always an option, never the default. Framing this option as a default position introduces a significant conservative bias — listing it as an option removes this bias and keeps a collective evolutionary.

To “look for other options” is always an option. If none of the other current options are good enough, people are able to choose to look for better ones — this ensures that there is always an acceptable option for everyone.

Every participant can express how much they support or oppose each option. Limiting people to choose their favorite or list their preference prevents them from fully expressing their opinions — scoring clarifies opinions and makes it much more likely to identify the best decision.

Acceptance (non-opposition) is the main determinant for the best decision. A decision with little opposition reduces the likelihood of conflict, monitoring or sanctioning — it is also important that some people actively support the decision to ensure it actually happens.

The examples given on the website are powerful but quite complicated, which is why I think there’s immense power in the default. To my mind, democratic decision making is the kind of thing that you need to practise, but which shouldn’t become a burden.

I’m hoping that after the v1.0 release of Bonfire, that one of the extensions that can emerge is a powerful way of democratic governance processes being available right there in the social networking tool. If this were the case, I can imagine decisions around instance-blocking to be able to be made in a positive, timely, and democratic manner.

Watch this space! If you’re reading this and are involved in thinking about these kinds of things for projects you’re involved with, I’d love to have a chat.

Enjoy things while they last (or hope for the best, prepare for the worst)

Note: it’s hot, this post might be be more ramble-y than usual…


Next to my bed I have one of these:

Glass paperweight with image of waves within it

It’s a glass paperweight that serves as a memento mori, a reminder that one day I will die. That might seem a bit morbid, but it reminds me to carpe diem (“seize the day”, to use another Latin phrase) and that things won’t be this way forever.

My kids will grow up and leave home.

My current state of calm will dissipate.

My possessions will stop working, get lost, or be stolen.

The list is long, for good and bad.


But my reason for writing this post is not a personal one, but a professional one. Right now, I’m more interested in talking about projects and initiatives ‘dying’ than me kicking the bucket. There have been multiple reasons over the past week where I’ve noticed that people expect things that start off great to continue to be so.

An OER repository was sold off to a company whose website is blacklisted by many educational institutions. A popular Android launcher was sold to an analytics company that’s often blacklisted by network blocking software. A project I’ve been involved with looks like it could be in danger of betraying its radical roots.

This is all very predictable, and is the reason for the popular phrase “hope for the best, prepare for the worst”. Especially in the kind of work I do at the intersection of learning, technology, and community, there are some amazing people collaborating on some fantastic things. It just takes a few bad actors (or people with ‘misaligned incentives’ shall we say) to spoil things.

That’s why setting up projects the right way from the beginning is so important. With MoodleNet, for example, we used the AGPL license, which meant that after I and the team resigned due to some internal drama, the Open Source code could form the basis of the project which has turned into Bonfire.

Even without specific licensing, just working openly can have the same effect. For example, there’s an archive of the work I did with a community that I helped grow at Mozilla around the Web Literacy Map. There’s no reference to it any more on the Mozilla site, but I can still reference it myself.

I’m not bitter about these things. (Well, not any more.) My point is rather than you should set up projects and initiatives in open ways, providing ways for awesome, talented people to get involved. But don’t be naive while doing so. Use defensive licenses, like the AGPL, and the wonderful Creative Commons Attribution-Sharealike (CC BY-SA) license which forces derivative works to be shared under the same license.

The same is true of legal structure and governance. WAO is set up as a co-operative with a flat structure and Sociocratic decision-making. It’s not possible for one person to sell out our company from underneath us because of the legal structure we created, after taking advice from more senior members of the co-operative community. And we’ve learned that consent-based decision making allows us to make decisions in line with our values.

Processes (especially around decision-making) work… until they don’t. You have to be intentional about these things. Remember that contracts are for when things go wrong, so cover your back. Imagine the worst thing that could happen, and put in place safeguards. Come up with ways to make decisions in productive ways with other people. Share your work far and wide, but protect it using an appropriate license.

Remember that our time on this planet is short, so let’s be awesome to each other.


In case you’re wondering, I bought my memento mori from The School of Life, and while you can’t get this particular one any more, there are others which are great — if not quite as awesome.

css.php