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

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 github mastodon tracker to try and get this into the code (hard job due to feudalism).

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.

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

A coversation 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-Med

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

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

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 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

 

 

The fediverse is an “accidental” openweb reboot

The #fediverse is an “accidental” #openweb reboot by the #fashernistas, so it’s herding cats to get anything done, not a bad thing, not a good thing It’s what it is.

One way to move away from this mess is #OGB grassroots #DIY producer governance.

Otherwise, live (and die) with the mess, and try to stop people bowing down and praying to the #deathcult is a step to keep the #openweb in place.

Talking about the #geekproblem in funding

Q. #nlnet – The problem we face with funding http://hamishcampbell.com/2022/06/06/the-problem-we-face-with-funding/

A. KiCAD, some warrant canary and Armbian aren’t “open internet” projects by any stretch of imagination, but the ones relating to routers and mesh networks are. They’re “open internet” at the infrastructure level – like Guifinet or Freifunk.

Q. yep and are useful for a tiny number of people so worth supporting. BUT the call-out for the funding is for a much wider social affect in the #openweb, so the is an obvious #geekproblem can you see this?

A. Whatever funding they put into the applications layer will be cautious because they probably don’t want to be dealing with Twitter-like problems. Infrastructure is more narrowly technical, and so it’s hard for that to blow up into a scandal, which could happen if they were more directly funding social networks.

Q.  yep… but the #openweb needs better USER-FACING code not more backend, the backend is not helping to address the social problems we face where it is being digested by the #dotcons and then adding more mess to compost. How to communicate this problem to the geeks?

A. Really it’s the backend – the plumbing – which needs more funding, because when you peel off the layer of ultra-trendy ActivityPub apps underneath you will find tools and systems which have been neglected for years if not decades. The application layer is currently a house built on sand. Or quicksand if you include Javascript.

Q. We do see the #geekproblem here you are right, and at the same time the view is irrelevant when you step back to look at the problem.

An example, #activertypub would have been still born without the outreach social UX of #mastodon. We have the #fediverse due to the social side of the mastodon project.

Adding more backend is feeding the #dotcons not the #openweb because we need BOTH, and we need to fund both. Yes, we can play “safe” and build tools to feed the future #dotcons, or we can do both and live life with the possibility of social change challenge…

UPDATE

Talking about the problem:

Q. Am thinking the #fedivers is in a bad way, so being angry and annoyed is understandable. The #openweb momentum we had is stumbling, the people sellingout growing as funding shifts… the problems grow, am interested in ideas to mediate these? The fedivers is a CULTURE first and a standard second… ideas?

A. I agree with your observation on the state of the fediverse. And on the cultural aspect too. I envision a Peopleverse (social) that is enabled / supported by the Fediverse (technical). And much more diverse social activity taking place here, that goes well beyond microblogging. And the funding should shift accordingly. You can fund as many innovation projects as you wish, but if the adoption of the technology grinds to a halt, then there’s a high risk this money is wasted.

 

Talking about the #geekproblem in relation to #peertube

Q. Says I need to log into an account to view the video.
A. that’s not good, was just impressed with the custom views in the updated #peertube, so maybe you need to be logged in to see them that’s bad #geekproblem maybe?
I don’t know how visionOntv works. Could be somebody’s choice given sets of options,, or could be default, or could be accidental combo of selections.
A. it’s a well moderated #peertube we updated our server so now have new filtering functions, but it looks like you have to be logged in to share links based on this, i tested in tor browser and cant see the links, likely they have resion for this or might just be #geekproblem – security first?
Q. Do not attribute to malice that which can be explained by incompetence…
A. to see malice is to miss the point github.com/Chocobozzz/PeerTube the #geekproblem is simple a critic of a modernist point of view, the persute of control/certainty that diminishes our ability to flourish.
You can call this incompetence if you like, I call it a problem that our “engineering” minded people need to work beyond. The #geekproblem is a good descriptive hashtag.
Can’t share custom filtered video lists URL’s without login being presented. · Issue #4611 · Chocobozzz/PeerTubeGitHub
And the people who created the feature may not have tested all the use cases either…

Or they might have done it on purpose to keep the new feature private…

Technically #peertube is good softwear, but as a social tool it’s not good and few people use it.
Q. Some programmers do not collaborate with real people who want to use their creations while they are creating them.

Did you know they intended to implement the feature you requested, and did you ask to work with them as they did so?

(P.S. if you keep calling them geeks all the time they might not feel like you would be warm and fuzzy to work with…)

A. I was talking to them from before the project was launched… though they have become more distant since they got funding – a different problem, though connected problem

Good codeing, bad social – kinda the #geekproblem

On the subject hamishcampbell.com/tag/geekpro of funding, I cover it more widely on the blog.

Basically funding alowes the geeks to be geeks when the funding comes from geeks.

If you think that’s bad, though, it’s even worst when it comes from academics 😉

Lived and worked through 30 years of this tech shit. Composting, we need some composting 🙂

End thought

The #geekprolem all ready has all the “solutions” It’s why it is has “problem” on the end of the hashtag. A problem that is going to kill millions of people and displace billions over the next hundred years #climatechaos we do need to step away and compost this shit #OMN

Note, I generally only use the “stick” after offering carrots quite a few times. Then alternate between carrot and stick with no plan for a good personal outcome.

Doing this for 20 years, in the medium/long term social change is generally visible. Yes you are right it’s a thankless task but somebody needs to do it and I live on a boat and can sail away, I half joke with the last bit.

This approach has only mediate the problems in my expirence though.