Tag: FOSS

Talking about #hashtags

We need to think of a serendipity view of how #hashtags work and how our coder kings implement them (#feudalism). Not saying this is a good aproch… i don’t know… but spelling hashtags “wrong” makes their use in categorization and sorting work differently. Might be worth thinking if this could add value or is purely negative? This depends on different views on federation and ideas of a universal truth or messy “truths”. Composting thought on this.

In the #OMN coding project, currently offline (unite.openworlds.info) we add word grouping flows, so you can say one hashtag is the same as another, ie. you can group different “meanings” to build category flows. This makes misspelled hashtags functional, and our current coding broken from the #OMN point of view.

It’s not implemented, is a speck projects so can’t test this. Over the last year I have put 5 #FOSS funding applications in to try and get this built, 3 turned down so far 2 more to be turned down (cross fingers and toes not) soon. Our #AP #openweb reboot is being destroyed by our #fahernistas and #geekproblem nothing new here, but we do need to do better.

That’s what we set out to fix 20 years ago, with the #OMN still digging, but my shovel has no handeal nor a head… says the man on his knees hands covered in shit… composting worthwhile however you do it, I could not make this shit up… but we keep making more #techshit

The signal to noise issue of our #geekproblem

#Mastodon and the wider #fedivers are native #openweb project based on the #4opens 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 #4opens 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.

 

Signal to noise on the #FBI seazing a database of a fediverse instance

https://kolektiva.social/@admin/110637031574056150

The #Fediverse is all #4opens so should not be used for anything that should be P2P encrypted. It’s important to keep this clear to users by not focused on the fig leaf of “hardening” security as the is non. It’s a very successful #OMN open media network, and it’s value lies in this.

Peoples pushing this are often not seeing the point that it’s designed #4opens this is why it works.

Both paths have value, but they are different.

And the push a different project (#closedweb) which is fine. But not a #OMN maybe they would be better off working on bridges as companion projects.

Good to think about this mess they talk about as it is not solved by more tech, we already have most of what we need.

* Open media is #4opens based on trust, the current ActivityPub is a relatively #KISS good example of this.

* Privacy is encrypted p2p chat, which there are meany good #UX mature #FOSS projects you can find

The change we need is social, getting people to use the different approaches for different needs, this is surprisingly difficult.

Bridges while dangerous are needed here, it’s good to talk about this in the sense of “security”.

https://newdesigncongress.org/en/pub/this-is-fine

This text reads like a vanguards path, based on #mainstreaming reading and narrow #geekproblem thinking. It’s missing the paths that hold value in #4opens horizontal activist paths we are building. But yes, we are getting lost in the growing #fediverse and the wider spread of #openweb  reboot diversity projects.

What it does highlight is the need for social and political thinking is needed, the is value there.

It’s hard to stress how “nave” meany devs on the #fediverse

#openweb #4opens is about building human trust, hard security is a very slightly overlapping but easy to see different path for building non “trust” based connections.

Some surprisingly hard to build bridges might help with this ongoing mess.

Can you see any of this feedback?

What is visionontv

#Visionontv is a grassroots media project that aims to provide an alternative to mainstream media by creating and distributing independent video content. The project has been running for over ten years and is based on the principles of openness, collaboration, and decentralization. It uses #FOSS open-source software and decentralized platforms to create and distribute activist video content. One of the key features of the project is its participation in the Open Media Network (#OMN), a decentralized network of media sites that share content and promote independent media that is not controlled by any single entity. The project emphasizes the importance of grassroots community-driven media, where people and groups can create and share their own content.

Building a better world, one link, one line of code at a time

Once upon a time, in a world dominated by the #dotcons, closed-source technology and centralized decision-making, a small group of passionate activists and developers came together to reboot an old way of building technology. They believed that technology should serve the needs of people, not only the profit of big corporations and governments. They called themselves the #4opens community.

The #4opens community believed that openness and trust were the path we need to take to creating technology that served the needs of people. They rallied round the codified existing #FOSS, open-source working practices as a process called the #4opens, which consisted of four #KISS principles: open data, open source, open “industrial” standards, and open process. They understand and valued that by embracing these principles, they could create technology that was more transparent, collaborative, and decentralized.

The first principle of the #4opens is #opendata. The community believed that data should be freely available to everyone, so that anyone could use it to build new tools and uses. They created a platform: #OMN where people could share data openly and collaborate on projects together.

The second principle of the #4opens is the #mainstreaming idea of #opensource. The #4opens community believed that software should be free and open for anyone to use, modify, and distribute. They created a library of #FOSS software that people and communities use to build grassroots tools and services.

The third principle of the #4opens is open “industrial” standards. This principle was a little more complex, but it basically meant that technology should be built using open, standardized protocols that anyone could use. This would ensure that technology was interoperable and that people could easily switch between different tools and services to push the projects that grow in the most healthy way.

The fourth and final principle of the #4opens is open process. This was perhaps the most important of all. The #4opens community believed that technology should be developed using transparent, collaborative processes that anyone could participate in. They organized on a platform https://unite.openworlds.info/ where people could share ideas, collaborate on projects, and make decisions together.

Over time, the #4opens community grew and expanded. They built new tools and services that were based on openness and trust. They created a vibrant ecosystem of developers, designers, and users who worked together to create technology that served the needs of people, and pushed back the profit greed of big corporations and governments and the people who server them.

And so the #4opens community continued to grow and evolve, creating a more healthy vision for technology. They knew that their work was just the start, they were determined to keep pushing, to keep building a better world, one link, one line of code at a time.

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.