Eliza Ludd the Fog and the Shade

Eliza Ludd the Fog and the Shade
Name	Eliza Ludd the Fog and the Shade
Location	NDSM
Date	2019/07/17
Time	9:30-16:30
PeopleOrganisations	Ollie George, Char Stiles
Type	HDSA2019
Web	Yes
Print	No

1. A Luddite is a person who dislikes or is critical of technology, especially technological devices that threaten existing jobs or interfere with personal privacy.

2. Fog Computing is like Cloud Computing, but more local and ubiquitous.

3. Shaders are a way to produce real-time computer graphics. Shaders are written in GLSL which is the OpenGL Shading Language, a C-like programming language that allows you to code powerful graphics programs (aka shaders) directly on your computer’s graphics card.

In this workshop you were introduced to shader programming through a semi-fictional/SciFi narrative. In this journey we were set in the far future meeting as a new breed of Luddites in a post-Fog-Computing world.

We learnt about our roots as Luddites, our relationship with technology in the current situation where Fog Computing has already risen and fallen, and finally we will draft a manifesto, which will establish our take over of the deprecated Fog Network. We will explain Fog Computing as it is “analogous” to shader programming, with the goal of sending our manifesto across the Fog Network, with the help of Eliza Ludd. Who is Eliza Ludd you ask? Well, come to the workshop to find out!

A laptop was needed. No coding experience required Note that this workshop was happening in parallel to another one, you had to sign up!

Kodelife intro by Char

Greetings Luddites…

Thank you for coming..

Here is the code from Eliza Ludd:

1. version 150

// All of the uniform variables are declared in the side control panel
uniform float time;
uniform vec2 resolution;

uniform sampler2D texture0;
uniform sampler2D prevFrame;

// this is part of the pipeline, it doenst really concern us.
in VertexData
{
vec4 v_position;
vec3 v_normal;
vec2 v_texcoord;
} inData;

out vec4 nodeStatus; // this is what the output of the node will be

void main(void)
{
vec2 nodeID = inData.v_texcoord;
// this ^^^^ is all the information we have about our fog node.
//JUST the ID which correlates to a pixel position on screen
// so the node given the ID (0,0) is in the bottom left screen and
// the node with the ID (1,1) is represented by the pixel in the top right

vec4 prevNodeStatus = texture(prevFrame, nodeID); // if this line isnt working, you have
//a different version of kodelife change the function texture to be texture2D

vec2 i = nodeID*8.0- vec2(20.0); // these are magic numbers that scale it to fit the screen

float intensity = .2;

float t = time;

//these next two lines are where the magic happens! feel free to noodle around with the numbers
i += vec2(cos(t - i.x) + sin(t + i.y), sin(t - i.y) + cos(t + i.x));
float fog = 2.0+ (8/length(vec2(i.x / (sin(i.x+t)/intensity),i.y / (cos(i.y+t)/intensity))));

//normalizes the (intensity)colors so theyre between 0 and 1
fog = 1.0-sqrt(fog);
fog = fog*fog*fog*fog;

// if the fog is too bright, copy what it was the previous moment(frame)
if (fog > 0.3){
fog = prevNodeStatus.x * 0.99;
}

vec4 final = vec4(vec3(fog), 1.0); // casting to a vec4
//ignore the last number it doesnt matter in this context

nodeStatus = final;
}

You can also see the raw code here

How this works is that you paste this entirely into Kodelife.

• If you’d like a different starter code to mess with: https://gist.github.com/CharStiles/69e7fa8d16dcbd4c02f7b8947706a559

NOW its time to remix the fog code!

• Here you can find the glsl sticker sheet: https://gist.github.com/CharStiles/e6fec016967c6c8fd648aa4b6c0055cc

Next Steps for if you want to use GLSL for live coding visuals and not just Fog Nodes!!!

These are some specific suggestions from me if you want to continue learning but don’t know how to start.

1. Learn the maths from The Book of Shaders

• If you haven’t looked at this already, look through it! Its wonderfully paced and has a lot of versatile useful information. [1]

2. Get into 3D!

• This tutorial here: https://github.com/ajweeks/RaymarchingWorkshop is super thorough and really useful!
• I wrote a really basic ray marcher that will work in kodelife: https://gist.github.com/CharStiles/0308b7c0cd4807e871f08250d57d0ec8

4. Get involved Online

• Toplap.org is the hub for livecode community. You can join lurk channel (its like slack) and join the visual channel https://talk.lurk.org/channel/visualists

Thanks a lot to all the folks at Hackers and Designers Summer Academy 2019 to make this workshop: Eliza Ludd, the Fog and the Shade come to life.

http://charstiles.com/shade/

Eliza Ludd & The Shades by Ollie George

In the wake of dark patchworks, networked clumsiness and technological dulling, an opening appears between the cracks of lost fiction and the merging of two narratives.

Two centuries ago, at the turn of the 19th century, the Industrial Revolution had grown strong in England. In a period that brought with it great technological advance and the idea of moral and economic progress, the drive to ‘become modern’ had put the livelihoods of many at risk.

New machinery was being introduced into textile and woollen mills across the Midlands, Yorkshire and north-west England. Highly-skilled workers had used artisan manufacturing techniques up until this point, but due to the development of technology, new stocking frames could produce cloth quicker and more cheaply than the trained workers could have themselves. Factory owners were now able to employ non-skilled, low-wage labourers to operate these new machines.

In the decades previous, the government had passed the Protection of Stocking Frames Act after a handful of irregular protests. Now, several groups of textile and woollen-mill workers had begun to more formally organise themselves, and an influx of riots began in 1811 onward. These workers soon became known as the Luddites.

The Luddites would write to factory owners and members of Parliament, calling for them to remove the new labour-saving machines in a bid to protect their working rights. When those addressed did not comply, the Luddites would attack the mills nocturnally and smash the machines in dispute. The revolts culminated in the introduction of the Frame Breaking Act, making their well historicised intervention with technology a capital offence.The leader of the Luddites, Ned Ludd, may or may not have been real. Some have authored that a Ned Ludlam was an apprentice frame knitter who destroyed two machines in 1779, though this story remains apocryphal.

The mythology of Ned Ludd, General Ludd, King Ludd, and the Machine Breaker in his many guises, created a fiction that could be actioned and assumed en masse. His name was authored across ballads, declarations, manifestos, and ubiquitous threatening letters.

Theorist Marco Deseriis defines Ned Ludd as an ‘improper name’, or “the adoption of the same pseudonym by organized collectives, affinity groups, and individual authors”.1 Nuance appears where the name Ned Ludd detached itself from its originating context. He writes:

“The name Ned Ludd designates two asymmetrical forms of struggle. On one hand, Ludd expresses the resistance of the last guild masters and apprentices against industrial capitalism. On the other hand, as it enters the Northwest, it comes to designate the emergence—albeit still in embryonic form—of a modern form of class struggle all internal to the capitalist mode of production.”2

Whether real or unreal, Ned Ludd’s collective identity became actionable in the political circumstance its users found themselves in. Ned Ludd was malleable, performative and constructed when and where was necessary:a fiction as literary weapon.

Along came Eliza

Many of the Luddite’s letters are stored at the UK’s National Archives. One of these is of particular interest to our story today. Marked ‘A’ and dated April 30th, 1812, its words were authored by an ‘Eliza Ludd’: the only non-male pseudonym deployed by a Luddite within a letter. Eliza’s words offered unique awareness and a literacy of politics that its counterparts did not share in, the vast majority of Luddite letters were violent threats. However, in the absence of knowing Eliza Ludd and anything beyond the words written inside ‘A’, their fiction remains in the shadow of another.

Today, machine breaking and technophobia have reduced the Luddite narrative to a colloquial stigma, though it is no longer machines that need breaking but the metaphors that obfuscate our literacies of them. What might a reclaimed and re-narrated Luddism—fit for the 21st century User—look like?

“Let me persuade you to quit your present post, lay by your sword, and become a friend to the oppressed, for cursed is the man that even lifts a straw against the sacred cause of Liberty.” Eliza LuddApril 30th, 1812

James Bridle has described our current condition as a ‘New Dark Age’, evidenced by a century-long history of ‘computational thinking’ that has reduced our realities to data and framed everything quantifiable as fact. He details the failure of technological acceleration to equally transform our understanding, making a call not for new technologies, but new metaphors and “a metalanguage for describing the world that complex systems have wrought.”3

Metaphors are powerful tools that help us understand and relieve the unknown. The metaphor can be productive: it allows information to be accessed and understood by an audience who before might have not. But, at the hands of some, the metaphor has become a means to directly abstract and obscure.

The Cloud, our omnipresent figurehead, is the corporation-made mediator between human and machine. What was once a fuzzy circle, puffball or thought bubble, soon became visual shorthand for electrical engineers during the 1950s. The Cloud’s shape and iconography alleviated the need to explain the complex infrastructure it alluded to.

Today, the Cloud looks hugely different, incumbent as the data centre within a new breed of non-human space. However, we should know by now that no technology is ever safe from the rush of time, greed of money, and ‘progress’ as we’ve come to call it. The Cloud is not exempt from this and is soon to become obsolete, made redundant by something newer and more insidious.

After the Cloud,came the Fog

Fog computing is to be technology’s evolution of the Cloud, the Fog its next metaphor. In what can be understood as the Cloud coming down and surrounding us is, in reality, decentralised and ‘mini’ data centres known as fog nodes. However, the Fog’s metaphor might risk dulling our understanding of technology completely.

The fog consumes, engulfs and abstracts, obscuring our orientation to the space of mental and physical capacities. The ‘fog of war’ describes a situational uncertainty caused by the chaos of battle, and when we talk of developing ‘brainfog’ we describe a cognitive dysfunction that produces problems with memory and mental clarity.

The Fog (proper)

To divide the fog in two brings forth a useful partition to navigate its problematic. The Fog (proper) we can conceive of as the computational system and network architecture known as fog computing. The Fog will bring Cloud computing closer to the user as an additional ‘layer’ within the Cloud’s ecosystem. Described as a critical and exciting opportunity, the Fog will help further enable the Internet of Things across smart devices and industrial infrastructure. At present, the Fog is caught within a storm of R&D, funded by a techno-guild of Cisco, Dell, Microsoft and Intel, among many others.

The fog (abstract)

The fog (abstract)—differentiated by lowercase f, but no less signficant—is symptomatic of our New Dark Age. The fog renders us in a state of perpetual confusion, at loss from a clarity to the technologies we live by and use everyday. That said, James Bridle makes clear that a New Dark Age is not a time in which nothing happens, nor an age in which things are not possible. Instead, he maps out the darkness as a space to think things through we’ve not been able to before. Could the fog be productive?

#acceleratethefog

If we can conceive of the metaphor as a technological system, it is one that might implicate as much as its computed counterpart. If we are to think of the metaphor as machine, then we must know how to pull the plug. Shall we go fogging?

We’ll DDoS the fog in one attempt, and censor it in another. Should that fail, in spite of a code that won’t compute so mathematically, we’ll brand it. We’ll saturate the fog and flood it with popular culture. We’ll script the fog in acts of three and roleplay it start-to-finish. We’ll confine the fog to download speed and corner its bandwidth allowance. We’ll forge, tamper with and spam its metaphor, disguise ourselves as Eliza and jam the fog with colluded data. We’ll invoke the fog into other metaphors to contradict itself and mediate a non-computed tussle. We may even try to mask the fog, though its potent source will dare to remain.In the face of its mounting corporeality, we must accelerate the fog, exercising it visually and textually to the point of overdrive. The fog in overdrive might lead to override, and overriding its unknown might help us to disarm it.

To break the machine then was to condemn its assault on working livelihood. To break the machine now is to demystify its metaphor by accelerating and disarming it.

Eliza Ludd & the Fog is a story already written, but yet to be told.

1. Marco Deseriis, Improper Names: CollectivePseudonyms from the Luddites to Anonymous(Minneapolis: University of Minnesota Press, 2015), p. 3

2. Ibid., p. 32

3. James Bridle, New Dark Age (London: Verso, 2018), p. 4

Poem Note by Juliette

remix culture
did ned ludd ever exist?
eliza eliza eliza
how do we resist progress today?
are hackers the new luddites?
it’s very unforgiving
can you redo what you just did but slow
the following are from the book of shaders
If I’m a pixel and I want to know what my color is from the previous frame
that’s how we realise that computers are basically toothpicks 
It’s so loud I wanted to turn down volume, but it’s visual!
FAT glitchhhhhhh
but I don’t want to fat shame glitches though
I just LOVE computers
plug stuff into other stuff
Try values until they work
let’s think about the body of code as the body of Eliza
the same way that Ned Ludd was a collective body
technology replaced religion

Load video

YouTube

YouTube might collect personal data. Privacy Policy

ContinueDismiss