Tag: IMC

Talking about grassroots media as a step away from the current #techshit

Hamish Campbell, a veteran in radical media for the past 30 years, discusses the failure of current technology and mainstream culture. He highlights how the #dotcon boom commodified our data, resulting in closed technology silos like #Facebook and #Instagram that capture our attention and data for their own profit. Campbell argues that alternative technology built around an #encryptionist agenda has gone nowhere and that the world is dominated by these tech giants. He argues for the importance of the #openweb, which was born open but is dying closed over the last 20 years, and advocates for rebooting grassroots media as a solution. Campbell uses the Oxford #IMC as an example of how a simple federated network can work by sharing content, using trusted link flows, and allowing content to be moderated or rolled back. He believes that the beauty of the #openweb is based on free flowing links, unlike the #closedweb of our current dominating technology. Campbell concludes that the #OMN project is more important for what it does not do than for what it does, and highlights the need to take small steps towards a solution by rebooting grassroots media as a example project.

What you can do

In the last few years there have been events and gatherings in the US, Portugal, and Madrid, discussing the possibility of #rebooting #Indymedia. The current history of Indymedia has been primarily written by academics and is very Americanized, so there is a need to retell the stories and provide a wider perspective. To successfully reboot Indymedia, I think it needs to return to its open and serendipitous roots, rather than the bureaucratic and closed structure it became. Fortunately, most of the technical tools needed for a decentralized and federated system, such as ActivityPub and Scuttlebutt, already exist. To maintain its radical grassroots philosophy, the principles should be used to ensure openness and accessibility. To get involved, one can search for #indymediaback or “reboot Indymedia” and find useful links #OMN

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 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 #Fediverse 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 open-source project instead of implementing an existing standards based RSS they created their BETTER, BRIGHTER flavour which was of course 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 divide in the end. A bad “open source” outcome. You can find similar behaver today in the fediverse if you look.

It’s a interesting 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 #geekproblem)

3) #openweb being sidelined by the rest

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

2) The second is a obviously failed compromise by keeping control of “their” 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.

A look at how technology shapes progressive/radical media-looking forward-looking back

3 events at newspeak house this winter:
Session 1) Looking back – how technology shaped the production and distribution of radical/progressive media like #Undercurrents, #Indymedia etc.

Session 2) The current day – failure of radical media technology. The rise of the #dotcons and the new alt-media projects.

Session 3) Looking forward – The #activetypub meetup. This is an update on the state of current #openweb projects. A continuation of the very successful #Mastodon meetups that I set up last year, opening up to the wider projects like #Peertube, #Pleroma, #Pixalfeed etc.

What kind of format do you imagine?

First two would be presentation, with long Q&A sessions and feedback from other participants that arrive on the day. Following the successful meetups last year, the last session is a user group go round with a few lightening talks and Q&A.

Session 1) I’m planning to invite one of the founders of both Undercurrents and #IMC to speak. I was also involved in both, so we would have 3 perspectives. I would have to cover the expenses of these speakers.

Session 2) I’m currently looking for speakers. I can talk/guide on this subject to shape the agenda to the subject.

Session 3) We have a list of people to invite from our meetup group from last year, so it will be a continuity user group meetup with fresh outreach.

And who do you imagine as your target audience?

Session 1) People who were involved (a lot) in the production and distribution of radical/progressive media. Historians (a few), and people interested in the 3 workshops and the subject of tech and politics in general.

Session 2) The same people from the first session will come to the second one, plus next generation who built good things inside the #doctons (for example UK uncut, student protests, current radical media projects and their ordinances).

Session 3) The same people from the first two sessions, plus the people running the Mastodon instances. Both developers and users, as well as the new alt media producers to connect with the developers/sysadmins

For outreach, there will be two bites of the cherry, the publicity for the event and the publicity for each of the sessions.