- FLEE IMMEDIATELY! THE CONCEPT -
A PDF-web is a PDF-print. Today, anyone can publish online with social media tools... But as an artist considers the pigment in every paint mixture, why don't we consider the code in every display? Moving away from PDF's and print screens, Flee Immediately! looks to explore content in line with structure (code) and to think critically about design standards, website templates, codes, datas, possibilities....What can we envisage a website or digital publishing to be?
Flee Immediately! is about publishing question-provoking content around technology and society within new designs and ways of using the web. Instead of just putting PDF's online, each issue will be unique in the form it takes - its own web platform. The way this platform will look depends on the the theme of the issue and the content generated, and will combine and play with both. The platforms will help to create new web experiences, expose the codes that are running behind and take a critical approach to the design and technical standards of the web today. What other possibilities are there and how we can use forms that help us to learn? Flee Immediately! furthers this by creating discussions around similar themes through workshops, 'blog' dialogues and events.
Flee Immediately! is more than just a digital publication - it is an experiment that generates new ideas, experiments, uses and understandings, and helps us to learn and think critically about the technology we use everyday - on and off the screen.
- FLEE IMMEDIATELY! THE PAST -
Before specifics of funding are discussed, let's Flee Immediately briefly into the past...
Flee Immediately! is already on issue 02. In the past, the concept of Flee Immediately! was the same but the materials were offline.
The first issue 00 was a complete experiment. It was and done, from concept to print, in only a month. I started the whole project in London in 2011 out of pure frustration. I had finished my Masters degree in Interactive Media, and yet (and perhaps also quite happily), I did not fit any checkboxes and nor did my understanding of technology. I saw technology culturally, extending beyond the screen and into every day life. So why not do something with this frustration in connection with my love of writing and codes? Issue 00 is printed double sided on A1 and folded down to A5. To make it a technology in its own right - off screen, I incorporated this idea of folding into its structure.
...and then Issue 01 was born April 2012. I found a collection of old computer manuals from the early 90's. Quite surprisingly they did not take themselves too seriously. Taking inspiration from them, I gave Issue 01 the theme of manual. It is again printed double sided on A1 and folded down to A5, but this time on transparent paper.
As much as I love print, however, I now think it is important, to start to think critically about the digital. Flee Immediately!'s roots allow it to become a venue for such experiments and discussions and to further my interest in code and design through publishing. This Kickstarter funding of Flee Immediately! will help to bring about these new experiments and collaborations.
To see information about Flee Immediately! in the past have a look at the newly made website: www.fleeimmediately.com
- FLEE IMMEDIATELY! THE FUTURE AND THE FUNDING -
Your amazing support of Flee Immediately! issue 02 will help to get this experimental publication back up and running - and digital.
It is with every little help from you, that this is possible, and we can all be a part of the process and add our voices to the discussion!
Specifically, the funding from this campaign will help to support the following:
* Admin Fees to pay for the hosting and longer term development and sustainability of the Flee Immediately! website and platforms
* Fees for the Programmers who build the platform
* Fees for the contributors/writers/artists of the issue
* A series of unique workshops in Berlin, Germany. In collaboration with the Open Systems Association
- FLEE IMMEDIATELY! ISSUE 02 - THE THEME -
Why dance and code, you may ask? Its a good question and I don't have the answers either. But it is through this issue of Flee Immediately! that we can start to explore the relationship between the body, rhythm and technology. Let's generate some answers - and more questions!
Here is an excerpt from the open call (and of course, feel free to participate in that as well!):
Imagine yourself on a dance floor - scratch that - a rave. You see faces, people, each moving separately but each to the same music — the same code. You start to dance with one face, you inter-face. You meet, you connect, you communicate, if only for a second, and then the face disappears. One meaning out of many, but its all produced from the social structure of a dance. Now imagine yourself in front of your computer, you are probably already there, perhaps cue more procrastination more curiosity - more clicking. You are looking for something, that long lost face from the dance the night before. You type, you click, you communicate, if only for a second, and your search disappears into a world of stalking. Do you dare click on the link? One meaning out of many appears, and its produced from the structure of the database itself. But, sigh of relief, the face may never know you are searching for them even if you found their long lost high school photo, you are in protected mode.
We could create a database of dancing and a database of a databases and put them side by side. Music is the code of the dance. Software the code of the database. They both guide how the the dance/database is to function when it is run, when it moves, when it is a process. But most importantly, both dance and databases have rhythm. They have a time and space. They have a context in which they run - and repeat. After all, rhythm is the repeated pattern itself - the code and the looping. And we all dance to that. We dance to a choreography that is pre-programmed into the interface. This choreography has power: it is the planned moves of control. And yet we see it as user friendly, we can use it, we can search the database, we can grasp what it is about. But really we are just making the same old moves that everyone else on the dance floor is pushing out of their (seemingly) free flowing limbs. We dance, and we are part of the choreograph of control.
So why Dance at all?
Flee Immediately! is opening a call to explore just that. Or in other words, themes around dance/rhythm/movement and code/technology/database and how it all comes together culturally, visually, in design, in motion, in control… You interpret it - dance at your own rhythm and to your own beat….
Read more here
Risks and challenges
The Flee Immediately! approach to 'Error':
We see error as a tool for growth, and just as important, as success. Anyway, we couldn't measure one or the other as they both help to raise the kinds of questions we want - and are beautiful in their own right.
However, as in any programming language, there are limits to the positivity of error. With this in mind, I can prepare for possible risks and challenges that may arise.
-How to make Flee Immediately! sustainable and to remain ethnical in its approach?
*I will need to generate a stable income that extends beyond this kickstarter campaign. I plan to apply for additional funding to help support the project in the long term. I am also thinking of ways in which the project in itself can generate funds without sacrificing its experimental nature. Some possibilities include: workshops, events, the selling of merchandise, and the adaption of codes specifically for other open source projects.
-Websites crash, Hackers Hack, codes do not work, problems cannot be solved, ideas fail, timelines cannot be met because coding is taking longer than we thought. What can we do about it?
*As most of you have probably experienced with your own devices, technology doesn't always behave as you want it and when you want it. Thankfully, due to my Masters degree, I have gained a logic in systems that helps me to ensure that I can problem solve and be creative about solutions quickly and efficiently. And if not, I at least know where to look and when to ask for help. I have engrained the motto of backup, backup, backup into everything I do.
-What about the contributors and the codes?
*The codes/softwares created will all be licensed under an open source license. They will also be well documented. Each contribution, in terms of rights and collaboration, can be arranged and discussed individually in advance. I am confident that through an open model of communication we can create a solution to these problems that works for everyone involved in the project.
-Sometimes relationships do not click. How can Flee Immediately! ensure that everyone is represented fairly?
*Based on experience working with various groups, from liked-minded people to support groups for people with Obsessive Compulsive Disorder, I can ensure that any collaboration is well noted, compensated and that all information is open and clear - for all parties involved. I am open to collaboration in all its forms, and I am happy when people want to interpret or change things in different ways.Learn about accountability on Kickstarter
- (30 days)