Nurturing community’s – tech is not going to do this

On the #fediverse, we need to work/think about the need to cross-link the subject instance.

As, the idea of as instance as a community is lightly built into the code of mastodon. So individuals and groups need to push this into existence, then add issues to the #ygithub mastodon tracker to try and get this into the code (hard job due to #feudalism as governance in #FOSS).

As a first step, we need to build flows between subject instances by individually fallowing people cross subject instance, to leak the content into timelines. Then encourage people to look at the global and local timelines, not just their personal timeline, which is likely pretty empty.

Nurturing community’s – the tech is not going to do this for us, is my thinking. This is a problem as community’s have the power for social change/challenge we need to get out of this mess.

I am asking people to try working round the poor “community” side of the hard coded ideas of community in mastodon.

A conversation on trust and tech with #OMN projects

Remember the #fedivers is built like this, no geek in their right minds would do this, yet we use it every day

All our existing code is based on #feudalism master (admin) surf (user) this is why it is defenceless vs capitalism (#dotcons)

There have been attempts to build democratic code, early #wikis, think #indymedia

#geekproblem “common sense” shifted them back into feudalism.

We have a hard #BLOCK on democratic code, if you want to change/challenge then this blocking needs to be removed.

The #OMN is a project for this, it’s an uphill battle to bring democracy into our coding.

This is the media project (text needs a update” unite.openworlds.info/Open-MedOFFLINE

Governance for horizontals to talk to “vertical power” unite.openworlds.info/Open-MedOFFLINE

And a video for you visionon.tv/w/jqTdss1qrdk4yEZi OFFLINE

We get into the details, of the #OMN you would get Boleyn tag changes on import, so you can auto translate guardian issued tags and add your own tags with both rules and manually.

These tags would flow out of your instances and could flow back to the guardian if you trusted each other.

The idea is to turn news stories/videos into “commons” objects with rich flowing metadata… done in a #KISS way based on trust/moderated link/flows

RSS bring in the legacy objects #activitypub is the main transport protocol.

It’s the news part of the #fediverse, our first implementation of this would be #indmediaback

The idea is to decenter the server, the data is in a soup that flows… #activertypub is two-way this is need to build the horizontal network, so the soup does not ONLY flow one way.

Nobody is in charge, no slaves, no masters. Only trusted or moderated flows. It needs to be two-way, though you are right people being human meany will be one way. BUT we are not building it that way 🙂

RSS brings the legacy in, and it’s a simple display format for embeds and passive news feeds etc.

I think people find the “nobody is in charge” bit a very hard thing to understand, even though we have built meany networks/social groups on this idea, and still do.

In the realm of tech, I call this #blocking the #geekproblem and to get anywhere we need to take the “problem” outa “geek” or we are left with the mess (in a bad way)

#KISS