What is the #OMN project for

The #OMN is about building #KISS bootem up trust based media networks for publishing and soughing content with enriched metadata flows. In the end you have a “stupidly simple semantic web of media object “cauldrons” and flows build up from a local level. What you/we do with this is up to the users/producers… this is held to radical politics by #PGA

Initial projects are media #indymediaback and archiving #makeinghistory with the resistances’ exhibition. There are likely lots of other things you can build as its just pipes and flows – the internet as a “open/trust” database of humane objects/people.

How this fits into traditional or Alt economics is not rarely up to us – but bounded by #4opens and #PGA so up for “connections” based on opendata flows – #RSS or #activertypub are good starts.

 

Lets build a real world example base on the OMN tools set- a indymeda instance/network.

Looking at this very simply they are two pools of data – trusted and moderated

– the trusted data is displayed on the site and flows out from the site as feeds.

– the moderated is displayed on a back end moderation/draft feed the mods of the site get to decide what to do with this content, to add it to trusted, to leave in draft/mod for consensus, to remove it.

The content that is trusted is unedited, though the long tail of metadata can be edited and updated by mods.

The site banner and side links are static.

The site display is based on two main flows that are both #activertypub and #RSS.

Newswire and features (and optional individual flows based on user accounts)

* The first main flow, newswire, is made up of a number of sources

– user accounts from this instance (if turned on) based on roles defined by the #5functions.

– boolean logic tag created #activertypub or RSS feed – there should be #5functions on both ends of this flow in the best implementation – we can live with one end. These feeds are added by the mods of the site to allow a local network of publishing sites to be created and nurtured

* The features is a feed for storeys created from the resources published to the newswire, linking back to them. The flow is original content published as a feature by the mod crew based on #5F if its in moderation it is treated as a draft not yet reach consensus if it is trusted it appears on the page and flow feed. This feed is a prime news resource to other newswires of indymedia sites that subscribe to it.

Rich compost in technology

Think of the fedivers as a flowerbed in a big (#openweb) garden surrounded by concrete. We are interested in the garden and bracking up the concrete (#dotcons) to make room for more flower beds and wild forest.


 

#Activertypub is a part of the flow, as is #RSS and maybe #Odata etc. The apps are the pipes. The human community produces and mediates the flow, in a metaphorical sense is the flow.

The fedivers is lovely healthy’ish flower bed, a small part of the #openweb garden that we are caring/nourishing in our work. When we are down and dirty working in tech it is important to remember this. In the end the garden is the human community’s living as part of a wider natural ecosystem.

The current priority is to get the flow working in a small and sustainable way – thus the hyperlocal test rollout and #epicyon.

This is why i use “mess” “shit” “compost” and “spades” as communication metaphors. The stinking mess we are in is a fertile time for change. For the last 10 years the #encryptionists agender and the #dotcons have been a sterile time, in this shit is a good thing, to live in stinking times 🙂

We have to keep focus on nurturing the seedlings with nutrition rich flows otherwise they wither and die. “Priority is to get the flow working in a small and sustainable way – thus the hyperlocal test rollout and epicyon.”

Looking at wordpress (WP) as a option, would like to try this out on my blog (http://hamishcampbell.com) thus the desire to get it working better. We have already mastodon and peertube. With out a bigger crew we should concentrate on creating a flow with epicyon as this is work anufe. If we can join WP to this flow a bonus.

Remember we are ONLY planting the seeds in the cracks and nurturing them. The roots of the plants (community) bracks the concrete. If we spend time trying to break the concrete we will soon be exorsted and achieve little.

So our mission is to find cracks and plant seeds. Of courses gathering the seeds (crews/code) is a first step – thus outreach and the messiness this brings – we do live in stinky times.

Then think of #searx (http://openworlds.info) as the map to the garden and as a way for people to find out of the concrete paths to the fresh #openweb grass fields. It can all grow up slowly if we keep a nourishing flow going. If we forget, it dries up and dies as it has done meany times in the last 20 years.

You would be surprised how fast nature reclaims concrete given a chance 🙂

A look at the internal mess of the uk indymedia project

The project i like to point to as an example. The indymedia project an early alt-media network that spread the use of open source software and #4opens organizing around the world at the turn of the century. In the UK the was a #geekproblem vs #openweb fight that became nasty over what we would now understand as “activertypub” the fedivers vs more centralized silo approach. In the UK you can see this stress point fought as a proxy war over #RSS

The #openweb aggregation side were sold a dud by the #fashernistas being swayed by the #geekproblem It was obvious that the project had to change and move away from central servers to a more aggregation model. BUT the movement was torpedoed by an obviously pointless opensource project instead of implementing a existing standerds based RSS they created there BETTER, BRIGHTER flavor which was of coures incomparable with everyone else.

This is an example of a “better” but obviously pointless open source project and also destructive behaver. The #indymedia project in the UK was ripped apart internally from this same devide in the end. A bad “open source” outcome. You can find similar behaver today in the fedvers if you look.

Its a intresting thing to look at. Actually you can see 3 active sides in the internal uk #indymedia mess and important to see the outcome that they ALL LOST in the end.

1) #encryptionists (being pushed by the #geekproblem)

2) #fashernistas (being influenced by the #geekoroblem)

3) #openweb being sidelined by the rest

1) The first resisted and blocked aggregation and #RSS from privacy and “securaty” issues.

2) The second is a obviously failed compromise by keeping control of “there” own better, non comparable RSS format.

3) The last, the one the whole project was based on were ignored and sidelined.

The #IMC project soon became irrelevant and died.

What is the OMN

The #OMN its a anything in and anything out – mediated by trust database/network.

It’s up to “commernerty” what they do with this and up to the individuals what commerty they choose or if a bit geeky can be an individual. it’s just soup (data soup) of course my project is to build a media/news network out of this other people can build other things #OMN

The data soup is fed by folsonmeny flows of tagged data objects mediated by trust. The consumption is based on the same. All with a nice UI

Lossy, redundancy, trust are features, the #geekproblem seeing these as problems needs to be overcome.

Being based on the #4opens am looking at Odata as the rest API core https://www.progress.com/blogs/odata-faqs-why-should-rest-api-developers-use-odata as this is an outgrouth of #atompub and #RSS and comes from a long process of open development #indymedia What do you think?

The exciting bits are the “flows of trust” bulding commertys, the tech and code are just tools.

* Nothing new

* All #4opens

* Good UI