The world is full of well shitty people… this is not surprising as we have lived in a sewage outlet for more than 40 years, to be covered in shit is human. What is not human is to go along with #stupidindividualism to play #fashionista agenders. Make judgments for social good, don’t go with the flow as it’s a sewer. You do need a shovel #OMN
The #OMN project is more important for what it does not do. The is a core/ perfiery outlook, more than 99% of peoples input from mainstream tech culture is clearly coming from the perfery for the human centred workflow of the #OMN Our mission is to shift through the tech pile and find the 1% that is core to the human project. Avoid getting lost in the stinky, shiny, fashions that the majority push.
A good project needs focus, without it you just have a diluted mess. In a world driven by #stupidindividualism we have problems with https://en.wikipedia.org/wiki/Bad_faith to constantly overcome. Generally people have no idea they are coursing a problem which makes it difficult to deal with.
For the January meeting am interested in looking in detail at #activertypub (and the new tech around it) as we should have a wider outline of the social #OMN project by then and have an urgent need to find technology that fits into it. Good focus for this meeting. Of course everyone is welcome.
This should lead to working on the next codebase of the #indymediaback project.
We are on a mission
The network is made of pipes and holding tanks with different end connectors. The idea is that every part, in abstract, is understandable by a normaliseish human being.
* link/subscribe to a flow – plumb a pipe in, on, the end/beginning of the pipe can be other functions
* trust/moderate flow – through flow or to the holding tank then though a sieve to shift the flow to different pipes.
* rollback – empty, remove that content to a point in the flow or remove objects from the flow.
* edit matadata – add to the trailing tail of the data object, this will change how data is sieved and is the main function in aggregation news.
* publish content – add an object to the flow (you can maybe edit this object or not)
The is then the storage tank which is a database.
That’s it the rest is UX and UI think of it as macaron for news publishing.
TAKENOTE: the is nothing original in this, its how our plumbing, our electrical grids and even the neurons in our brains work and fits into the #nothingnew that is a core of this project.
Report back on peertube/youtube video posting experiment. #XR video posted only to peertube got 18 views in 48 hours. Video posted only to youtube got 26 views in 24 hours so far. Both videos were nice fluffy #XR shared widely in meany #dotcons groups with 1-10k subscribers so in theory to 20-50k people based on “simple” subscription count.
Posted to peertube
Posted to youtube
Let’s look back for a moment. Last year posting similar video you #youtube would have received 100-250 views
10 years ago 2000-4000 views would be normal.
Thoughts on this the #dotcons algorithm affectively #BLOCK straight grassroots video reports – only by shaping your media to #SEO games can you get any views in the #dotcons. This behaviour has shifted popular radical messages/media makers to #deathcult agenders to have any hope of achieving personal “success” and will continue to malform our media if there is no working alternatives for them to use.
I think our “digital addictions” explains the failure of the videos to organically spread inside the #dotcons with views not being feed by the algorithms which prefers #clickbate and people have been trained to push #clickbate so no longer see the need to push straight content – “vanilla” radical grassroots content does not feed their digital addictions or the hole mainstream culture leaves inside us all.
On one hand, if we keep going down the #dotcons path our media will become more and more malformed to #deathcult agender simply to get views and attention. on the other “straight” grassroots coverage will be affectively BLOCKED.
A note here for the #fashionistas “Gaming” the algorithms is just SEO under a new path. Let’s worship the “cargo cult” mentality and not a helpful comment/reply please have a think on this point.
For the last 10 years I have been pushing anti-algorithm content to amplify the exclusion affect. Looking at these numbers I think we are starting to get peek exclusion as our visionontv youtube channel has 7k subscribers so to get only 26 views in 24 hours is notable bad, just on this subscribe base not to mention the #failbook groups embed postings etc.
Talking about the #deathcult is not advertising friendly no matter how fluffy some of your content is 🙂
To conclude. Two points for #openweb media we need to remove “advertising friendly” as criteria. Second we need to actively detox people from their digital addictions. We do the first one, but we have no real plan/implementation/ideas on the second.
Yes. Lots of #NGO’sh people will want to add “common sense” #dotcons ideas and process to #openweb projects as they take off. There will be a pile of shit shovelling need to get past this “common sense” issue. We need good shovels #OMN
The reason we are building out the wide #OMN network to provide a space for our messages and to make compost out of our current shit pile;)
UPDATE: the youtube video got to 42 views in 2 days the peertube stayed at 19 views both are very poor numbers but the #openweb one is growing and the #dotcons one visible declining which is positive.
Take a moment to think about basics: activism/campaigning is about building resistance to the mainstream to change its flow in progressive directions. Were #mainstreaming is about shifting activism to reduce these resistances to the mainstream flow. Thus, it’s good to understand that #mainstreming is a #NGO agender to build the jobs of the people involved and is in turn funded to this end. Good not to get the shit mixed up.
Lifestyle is a way of forming a tribe inside this mainstream flow. The problem for activism is that this old school tribalism is obviously a BLOCK on social change as looking and talking right are MORE important than being right. Being right would be “resistance” and lifestyle is about going with the counter flow.
On the other hand the are advantages to “modern” tribal and lifestyle activism – it functions as social glue to hold campaigns together and provides a “uniform” flag to rally round. You notice I do not use words like anarchist, socialist, liberalism here as these have a different role in social change thinking – they are the ideas – the clothing is what I am taking about #fashernista is the hashtag.
#Revolution is about blowing up the flow of the mainstream so it floods into a different path with much “calcollateral” damage in the process as we live inside a highly urban complex society. Both paths can be useful, both have costs.
Good not to mix this shit up
Let’s build something to compost this mess #OMN
In web application development there are 3 groups you can empower and it’s important to understand which group you are empowering.
1) the users
2) the producers
3) the geeks who develop/admin
Most #geekproblem coding is about the 3ed grouping taking all the power to decide. We, tiny, “elite” know what is good for you “passive” masses. This is why most #openweb codebases are unusable, because obviously they simply do not know, good UX in social tech is hard.
Most #dotcons empower capital who pay the geeks to “serve” the producers to enslave the users. In this they are an interesting evil hybrid.
I can’t actually think of an example where the users are actually empowered off the top of my head – ideas please?
Good #openweb projects try to empower the producers/user they are not meany of these. Can anyone think of examples, we need a list.
Obviously we can’t keep repeating the first two shit outcomes as they are already piles of stinking manure everywhere from the last 20 years of this tech mess. You have/need a shovel #OMN
Q. I’m not interested in doing that as I don’t know what it is you are actually proposing. Apart from using hashtags and talking about #deathcults I don’t actually understand your plan?
What I haven’t heard is a practical way of hosting and distributing alt media.
Visionontv turned into a mess just as Indymedia did. So what has changed?
A. What happened is a good question. The answer is simple the fedivers maybe start here https://en.m.wikipedia.org/wiki/Fediverse
Our own tech in activism was ripped apart by the open/closed war, indymedia dies because of this, visionontv never went anywhere because of this. Outside activism this war has also been fought, the closed/encryptionists have been dominant for the last 10 years.
Around 5 years ago a handful of people said fuck this crap we need a spade. They created #openweb tools and it has exploded from there to be a real UI friendly alternative. This is exactly the same outcome of the World Wide Web did to the silos of the early internet.
Am simply bring this explosion of affective DIY creativerty into the ossified and dead depression of activism tech. Obviously meany nay sayers are going to piss and shit all over this move. Activist tech died for very good ressions. This dose not have to be a block, as I say this makes good compost so get your shovel ready and lets plant some seeds. I hope that not to metaphorical
What is also clear is that is people are getting serusly unhappy on the #dotcons
BUT we do not have a choice to stay in the #dotcons its poison and our ecosystem and social syteams are dyeing.
A realistic time line a year of dev and small scale roll outs. Durining which the will be lots and lots of shit shovelling to stop it becoming a stinking mess that people will not go nowhere near.
The tech is “easy”ish its the shovelling shit that’s hard, non techs can help with this bit.
The project is to decisively shift power from the geeks and admins to the producers and consumers of media. In this its about good UI and simple empowering #KISS tools to move content by categorising it with a bootum up folksonermy. This simple approach is balanced by shared site level higher languages for the complex crew.
“This is the Internet”
People can get involved at a level they feel they can add to the project to reshape there world.
* simply on a portal/app (aggregation top site/app)
* on there own site as a sidebar or page.
* as a part of an admin team on a middle/bootem site
* from a feed from there own site or #dotcons account
* writing linking articals as a part of a top/middle/bootm site
* as a embed on there own site
* on a bootem/middle/top site
For the geeks the project is based on #4opens protocols
1) For bringing legacy content in – RSS
2) For talking to the fedivers – Activertypub
3) And for internal working – OData
Lets look at the last:
OData fundamentals (from https://blogs.sap.com/2018/08/20/monday-morning-thoughts-odata)
OData is a protocol and a set of formats. It is strongly resource oriented, as opposed to service oriented. There are a small fixed number of verbs (OData operations) and an infinite set of nouns (resources) upon which the verbs operate. These OData operations map quite cleanly onto the HTTP methods
|OData operation||HTTP method|
|C – Create||POST|
|R – Read||GET|
|U – Update||PUT|
|D – Delete||DELETE|
|Q – Query||GET|
If something is important enough it should be addressable in that elements should have addresses, not hidden behind opaque web services endpoint. In the case of an HTTP protocol like OData, these addresses are URLs. And the shape of the data can be seen in the way those URL addresses are made up.
OData goes back further than you might think, its a grassroots project.
TThe protohistory of OData
OData’s origins go back to 1995, with the advent of the Meta Content Framework (MCF). This was a format that was created by Ramanthan V Guha while working in Apple’s Advanced Technology Group, and its application was in providing structured metadata about websites and other web-based data, providing a machine-readable version of information that humans dealt with.
A few years later in 1999 Dan Libby worked with Guha at Netscape to produce the first version of a format that many of us still remember and perhaps a good portion of us still use, directly or indirectly – RSS. This first version of RSS built on the ideas of MCF and was specifically designed to be able to describe websites and in particular weblog style content – entries that were published over time, entries that had generally had a timestamp, a title, and some content. RSS was originally written to work with Netscape’s “My Netscape Network” – to allow the combination of content from different sources (see Spec: RSS 0.9 (Netscape) for some background). RSS stood then for RDF Site Summary, as it used the Resource Description Framework (RDF) to provide the metadata language itself.
Atom. Like RSS, the key to Atom was the structure with which weblog content was described, and actually the structure was very close indeed to what RSS.
An Atom feed, just like an RSS feed, was made up of some header information describing the weblog in general, and then a series of items representing the weblog posts themselves:
header item item ...
A few years later, in 2005, the Atom format became an Internet Engineering Task Force (IETF) standard, specifically RFC 4287, and became known as the Atom Syndication Format:
“Atom is an XML-based document format that describes lists of related information known as “feeds”. Feeds are composed of a number of items, known as “entries”, each with an extensible set of attached metadata. For example, each entry has a title.”
What was magic, though, was that in addition to this format, there was a fledgling protocol that was used to manipulate data described in this format. It was first created to enable remote authoring and maintenance of weblog posts – back in the day some people liked to draft and publish posts in dedicated weblog clients, which then needed to interact with the server that stored and served the weblogs themselves. This protocol was the Atom Publishing Protocol, “AtomPub” or APP for short, and a couple of years later in 2007 this also became an IETF standard, RFC 5023:
“The Atom Publishing Protocol is an application-level protocol for publishing and editing Web Resources using HTTP [RFC2616] and XML 1.0 [REC-xml]. The protocol supports the creation of Web Resources and provides facilities for:
- Collections: Sets of Resources, which can be retrieved in whole or
- Services: Discovery and description of Collections.
- Editing: Creating, editing, and deleting Resources.”
Is this starting to sound familiar – OData is exactly this – sets of resources, service discovery, and manipulation of individual entries.
AtomPub and the Atom Syndication Format was adopted by Google in its Google Data (GData) APIs Protocol while this IETF formalisation was going on and the publish/subscribe protocol known as PubSubHubbub (now called WebSub) originally used Atom as a basis. And as we know, Microsoft embraced AtomPub in the year it became an IETF standard and OData was born.
Microsoft released the first three major versions of OData under the Open Specification Promise, and then OData was transferred to the guardianship of the Organization for the Advancement of Structured Information Standards (OASIS) and the rest is history.
Something that humans could understand, as well as machines. The resource orientation approach has a combination of simplicity, power, utility and beauty that is reflected in (or by) the web as a whole. One could argue that the World Wide Web is the best example of a hugely distributed web service.
OData has constraints that make for consistent and predictable service designs – if you’ve seen one OData service you’ve seen them all. And it passes the tyre-kicking test, in that the tyres are there for you to kick – to explore an OData service using read and query operations all you need is your browser.
Excerpts from the service document and from the Products collection
Notice how rich and present Atom’s ancestry is in OData today. In the service document, entity sets are described as collections, and the Atom standard is referenced directly in the “atom” XML namespace prefix. In the Products entity set, notice that the root XML element is “feed”, an Atom construct (we refer to weblog Atom and RSS “feeds”) and the product entities are “entry” elements, also a direct Atom construct.
Today’s business API interoperability and open standards are built upon a long history of collaboration and invention.
Food for thought #OMN
Nourishment for action