Should we use tech or social to verify a news source/flow.

Looking at the indymedia reboot

Its verified by the crowd/community as you will have text, photos etc from the event from different views with some of them by known actors. The event happend.

A single post from a unknown source needs verification. Its journalism 🙂 from a grassroots prospective based on communerty and trust in that community.

Of course what we lack in the contempery world is these very things. In this its the chicken/egg problem 😉

The indymedia reboot is the egg, we the affinity group are the chickens?

As in everything in this project we look for the solution in the social first. Then look for tech that helps to build this social.

Focus on the #4opens #PGA hallmarks and try and solve the issue with the 5 functions.

Ha! This is startling to sound like a religion. Were in reality its about #KISS and keeping focus on this.

Why move away from both the #dotcons and the #encryptionists now?

Lets look at trust/community building as this is what the OMN is about after 20 years of failed tech “solutions”.

 

* Link – am interested in there content flow for my community.

* Trust – i have a relationship with them, no questions.

* Moderate – we are building a relationship.

* Whoops – rollback

* Unlink – am annoyed, this is shit, waist of time.

* Bolyon logic hashtag flows – a conversation on what is important between the two groups to fine tune flows.

So for flows from a single source that dominate the instance flow. First stage moderation, more work for site crew. Second agree on a hashtag group based flow with the fast source and put them back on trust. Rinse and repeat

If it messes up rollback, if communication bracks down unlink.

An example of this would be the canary news site. Lots of low quality clickbate with acational good posts. Talk to them and get them to use a hashtag for quality post and subjects and only bring that in as flow. If they abuse this talk to them if you can’t come to an agreement then unlink or moderate. The is advantages for everyone to get an agreement and this will not affect the SEO games they play with the #dotcons

The outcome is the up quality of there SEO games getting grassroots content into the #dotcons And our communities we don’t have to see there SPAM. Grassroots news is spread wider, the communities that produce it are empowered. (And sadly likely co-opted, but that another problem for a different step)

 

Were is security?

Yes to security, people have to be who they say they are and content has to come from a place and its path has to be recorded.

Am going to joke and say we need a blockchain 😉

Trust has to have a foundation.

Stuff can’t just be made up at any level, this would brake trust.

Down the road the is a place for strong p2p identities and personal/group data stores. But not in the ” balancing” roll out of the OMN its good to plug in this stuff as the network grows. The growth stage is as #KISS as possible.

We are strongly refocusing on groups and flows and away from individuals and silos. We are not fundementism on this instead are balancing if that dose not sound to hippy… The #deathcult world is all #stupidindividualism and controlling #dotcons our mission is to rebalance this. Were the balence ends is up to the groups involved. I like the DIY anachronism of party and protest, some people like gardening, other are content with other things.. what ever rocks your boat the is space for meany paths – but the current #deathcult is not a nice one at all.

The is no securaty in tech, ecology or just about anywhere. Its very inhuman world we live in says the man sailing away in a lifeboat – as i keep saying that’s not a metaphor.

On the subject of people being who they say they are – this can be sudo anonymous if they feel like it but that “anonymous” person still has to fit into the trust web

Thus the sudo bit.

End thought

If data is the new currency, then opendata is the new communism, jumps to mind, lets see were #4opens leads.

Q&A what is a fashernista in the hashtag way.

Q. I’ve read a lot of your stuff but I’m hoping you’ll clarify something. What’s a “fashernista”?

A. A large part of society who do what’s fashionable. Not what’s right/wrong/best. In the era of the #deathcult of neo-liberalism this has always been the wrong path to take. Its a simple idea.

men-make-their-own-history-but…

#fashernista is a feedback loop of #stupidindividualism at mo.

The hashtags are designed to make the mainstream as dirty as possible so people see the need to pick up #openweb #4opens tools “spades” to clear the stinking shit and pools of piss #climatechaos is increasingly going to show we live in (consumerism/alienating work/greed is good) Make compost (decay of death) to plant seeds (fertile life) to grow flowers (lifecult). Its a convoluted metaphor 😉

Its a hard to understand simple thing. In the era of the #deathcult the fashernisas are almost always wrong and a part of the problem. In the era of the #lifecult fahernistas are mostly right and a part of the solution, dose that make it more simple?

What would a #lifecult look like in this era?

The encryptionsists – the last 10 years.


Security theater you should ask who we are hiding from. The sad and bad outcome of just about everything is only our friends – our enemies, the state and the #dotcons can almost always look behind the curtain. The rare exception of this is p2p encryption, never client server. Though the issue that makes most of security into a thin layer of cloth is the hardware and firmware our ”secure” apps run on. So many holes in these that it’s all academic, what we do next with social technology #4opens

4opens review of NHSX track and trace app

WHAT DO PEOPLE THINK ABOUT THIS?
The app is from NHSX with contributions from Apple and Google obvs and Pivotal Labs and Uni of Oxford. All source code for front and backend on Github and open source.
What is the actual polatics behind this?

#4opens review. Think it duse 2 opens as it clearly fails openprocess and likely opendata? Its opensource? And kinda open “industrial” standard. So its at best a bronze 4opens project, try harder?

On outreach of OMN and indymedia reboot

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

Were we are now https://the-federation.info/ or https://fediverse.network/

From an activist tech prospective. The real opening we have is this was built outside activism outside #encryptionist agenders and for the #openweb and is thus #4opens

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

A simple video on the tech https://www.youtube.com/watch?v=S57uhCQBEk0 from this its clear this #openweb tech works and scales and people like it

What is also clear is that is people are getting serusly unhappy on the #dotcons

YES its going to be a mess of shit and piss and fuckups, that’s activism, and the #encryptionsists pushed “closed” ideas deep into our #fashernistas so its a uphill battle.

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.

Help OMN indymedia reboot
* It easy to keep crossing wires with “media” vs. personal. Media should be open, with clear sources, except when protecting them. Whereas personal data should default to private
* #OMN is not about tech – all code is idolagy – the OMN its a social solution to a social problem
* teach people the #4opens and review tools/projects they use/wont to use by them.
* on the dev/organising site you can help by asking simple basic questions

#4opens reviews – Discord

https://discord.com
The #4opens:

Are a simple way to judge the value of a “alt/grassroots” tech project.

Open data – is the basic part of a project https://en.wikipedia.org/wiki/Open_data with out this open they cannot work.

* hard to say am assuming you can download your chats? but your contacts ect? Say ½ a open

Open source – as in “free software” https://en.wikipedia.org/wiki/Free_software this keeps development healthy by increasing interconnectedness and bringing in serendipity. The Open licences are the “lock” that keep the first two in place, what we have isn’t perfect but they do expand the area of “trust” that a project needs to work, creative commons is a start here.

* Discord is an American proprietary freeware instant messaging – No

Open “industrial” standards – this is a little understood but core open, it’s what the open internet and WWW are built from. Here is an outline https://en.wikipedia.org/wiki/Open_standard

* No its propritery

Open process – this is the most “nebulous” part, examples of the work flow would be wikis and activity streams. Projects are built on linking trust networks so open process is the “glue” that binds the links together. https://en.wikipedia.org/wiki/Process

* nop its a private .com

Note: Discord uses the metaphors of servers and channels similar to Internet Relay Chat even though these servers do not map to traditional hardware or virtual servers due to its distributed nature

So to be generous that’s 1/2 a opens so it is not a #4opens project

What is the #geekproblem

400 new securaty problems have just been announced for 40% of the devices in our pockets. This same story happens every month or so… these problems are at the chip level and can never be fixed in the device in your pocket.

Our “phones” are as complex as anything built by human beings. Think the British or Roman empire level of complexity siting in your pocket feeding you social media updates.

The geeks have been lieing to themselves and to us that there code can be “secure” on these devices. This has been going on for 20 years, the #encryptionists fantasy has been built on top of this lie, as well as our banking and governance.

Take a moment to think about this mess.

The is a way out #4opens networks move us to a different place, and likely set of problems 😉

What is the Open Media Network (OMN)

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”

GET

PUT

POST

DELETE

–MERGE–

This Odata is the #4opens #OMN project.

People can get involved at a level they feel they can add to the project to reshape there world.

Consuming content

* 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

*

Producing content

* from a feed from there own site or #dotcons account

* writing linking articals as a part of a top/middle/bootm site

*

Aggravating content

* 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
    in part.
  • 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.

Have a quick look at an OData service. The Northwind service maintained by OASIS will do nicely. Have a look at the service document and, say, the Products collection.

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

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.