To paraphrase Sartre’s famous comments about Che Guevara, the autonomous citizens of Rojava, or the Democratic Federation of Northern Syria — and especially those fighting in the ranks of its militia, the YPG/YPJ — are the most fully realized human beings of our time. Their understanding of kyriarchy and what it requires of those of us who would unwind it is direct, complete, unclouded.
Officially branded as terrorist sympathizers, alternately supported, disregarded and threatened by the US, in this era of incoherent strategic policy and smash-and-grab opportunism, the men and women of Rojava have been forced to do it all on their own. They’ve had to learn how to do anarchism, how to do feminism, how to do horizontalism and federation, in practice, in real time, in what certainly appears to be some of the least propitious soil imaginable, in the face of a world that seems to want nothing so much as for them to disappear.
I believe we ought to be doing everything possible to support them, and defend them against those who would destroy them.
The emergence of a vital resistance in Rojava is weirdly personal for me. For decades, nurtured on more-or-less annual rereadings of Homage to Catalonia, I harbored the fantasy that had I lived during the time of the Spanish Civil War, I would naturally have run off and enlisted in a militia like that of the POUM Orwell was affiliated with, and put my body on the line in the struggle against fascism.
And not just to fight against something, either, but for something as well — for the total vision of emancipated life that emerged during the years of struggle in Spain. The POUM, of course, was committed to a fiercely egalitarian politics, even under the pressures of the front line; in the militia that fought beneath their banner, “[t]here were no visible differences between ranks, no saluting and no differentials in pay,” while combat tactics and plans of action were often debated among the fighters expected to enact them. (And they weren’t even anarchists!) Meanwhile, behind the lines, in the cities and lands under revolutionary control, entirely new forms of collective life were emerging.
For most of my adult life, this was one of the precious few examples of actually-existing anarchism any of us could point to. We could celebrate the real improvements in status and condition won by revolutionary Spanish women, in the “double struggle” against gender and class oppression. We could emphasize, with almost equal pride, the fact that material production and even technology-intensive urban infrastructure like tramways or the telephone network prospered in the sectors under democratic management. And we could further argue, with a good deal of justice, that this experiment in popular control ended not because it collapsed beneath the weight of its own accumulated contradictions, but because it was destroyed from the outside — directly by the Nazi-armed and -supported Nationalists, and indirectly via the perfidy of the parties aligned with Moscow.
Nevertheless, destroyed it was. And curiously, that made the Spanish experience of revolution safe for those of us who took inspiration from it so many years down the line. For one thing, whatever difficult realities, compromises or oppressions emerged during the months of popular control, they were interred in glorious defeat along with the insurgents themselves. Neither those brave souls nor their overseas admirers ever had to reckon with the unresolved tensions of large-scale governance and self-management over the longer term. But also, however those tales of heroism on the barricades and in the trenches may have quickened our blood, with no real way to act on them, it became cheap and easy to imagine oneself into the narrative. You could puff out your chest and say, “Oh, yeah, I would have shipped out, signed on with the Abraham Lincoln Brigade, and killed me some Fascists,” with nobody and nothing to stand in the way of your self-righteous posturing.
With another experiment in popular control really unfolding in our time, though, Rojava has put such fantasies to the test, and me along with them. The question isn’t, what are “we” going to do for Rojava? It’s what am I going to do for Rojava, for this land that never was, where the people are somehow, miraculously, against every certainty of geopolitics, both putting Murray Bookchin’s beautiful thought into practice, and setting Daesh to flight at the same time?
Without hyperbole, there is literally no question in our lives more important, nor likely to be, at least for those of us moved by currents of the antiauthoritarian or horizontalist left. For us, especially, the way we answer it will determine whether we really mean our politics, and intend to see them through — with all the risks and pitfalls that entails — or prefer to see them safely, gloriously dead and in the ground, where we can haul them out a few times a year to mourn what could have been.
An article I was commissioned to write for the Touch issue of What’s Next magazine.
What does it mean for a text to be digital?
In principle, it can be replicated in perfect fidelity, and transmitted to an unlimited number of recipients worldwide, at close to zero cost. Powerful analytic tools can be brought to bear on it, and our reading of it. It can be compared against other texts, plumbed for clues as to its provenance and authorship. Each of our acts of engagement with it — whether of acquisition, reading, or annotation — can be shared with our social networks, mobilized as props in an ongoing performance of self. Above all, it becomes (to use the jargon practically unavoidable in any discussion of information technology) “platform-agnostic.” This is to say that it becomes independent, to a very great degree, of the physical medium in which it currently happens to be instantiated.
To varying degrees, these things have been true as long as words have been encoded in ones and zeroes — certainly since 1971, when Project Gutenberg was founded with the intention of digitizing as much of the world’s literature as possible, and making it all available for free. Why is it the case, then, that digital books only seem to have entered our lives in any major way in the last two or three years?
The apparently sudden arrival of the digital text likely owes something to the top-of-mind quality Amazon currently enjoys in its main markets, its name and value proposition as prominent in our awareness as those of the grocery chains, television networks or airlines we patronize — a presence it’s taken the company the better part of the last fifteen years to build up. And it surely has something to do with the widespread popular facility with the tropes and metaphors governing our engagement with digital content of all sorts that has developed over the same period of time, to the point that it’s increasingly hard to meet a grandparent inconversant with downloads, torrents and the virtues of cloud storage.
But the fundamental reason is probably that bit about platform-agnosticism. Anyone so inclined could have “engaged digital text” on a conventional computer at any point in the past forty years. But the act of reading didn’t — and maybe couldn’t — properly come into its own in the digital era until there was a platform for literature as present to the senses as paper itself, something as well-suited to the digital text as the road is to the automobile. I refer, of course, to the networked tablet.
It’s only with the widespread embrace of these devices that digital reading has become ubiquitous. Relatively inexpensive, lightweight and comfortable in the hand, capable of storing thousands of volumes, the merits of the tablet as reading environment may strike us as self-evident. But there’s another factor that underlies its general appeal, and that is the specific phenomenology of the way we manipulate reading material when using one.
We read text on a tablet as pixels, just as we would on any screen. But the ways in which we physically address and move through a body of such pixels have more in common with the behaviors we learned from books in earliest childhood than with anything we picked up in the course of later encounters with computers. This is why the post-PC tablet feels more “intuitive” to us, despite the frank novelty of the gestures we must learn in order to use it, and which no book in the world has ever afforded: the swipe, the drag, the pinch, the tap.
This is the new tactility of reading. But where there are comparatively few semantically-meaningful ways in which the reader’s hand can meet the pages of a material book, the experience of engaging a digital text with the finger is subject to a certain variability. It’s not a boundless freedom — it’s delimited on one side by technological limitations, and on the other by the choices of an interaction designer — but it does require explication.
The first order of variability is the screen medium itself. Each of the major touchscreen technologies available — resistive, capacitive, projective-capacitive, optical — imposes its own constraints on the latency and resolution with which a screen registers a touch, and therefore how long one must place one’s finger against it to turn a page or select a word for definition or a passage for annotation. Reading on a good screen feels effortless, even transparent — but particularly high latency or low resolution can easily disrupt the flow of experience, lifting the reader up and out of the text entirely.
The second is the treatment of type. As critical as it is to the legibility and emotional resonance of a text, and even at the higher resolutions now theroetically available, typography is all but invariably treated as though it had not been refined over five centuries. It still feels like we are many years and product versions away from type on the tablet rendered with the craft and care it deserves.
A third order of variability consists in the separation of content, style and interface elements inherent in contemporary application design. This means that both the meaning of gestural interactions and the treatment of the page itself can vary from environment to environment. Especially given the pressure developers are under to differentiate their products from one another, a tap in the Kindle for iPad application may not mean precisely what a tap in Readmill or Instapaper or Reeder does, or work in at all the same way.
In fact, something as simple and as basic to the act of reading as turning a page is handled differently in all of these contexts.
Originally, of course, the pagination of text was an artifact of necessity, something imposed by running a semantically continuous text across a physically discontinuous quantity of leaves. One might think, therefore, that pagination would be among the first things to go in making the leap to the digital reading environment, but contemporary applications tend to retain it as a skeuomorphism, larding down the interaction with animated page curls and sound effects.
On the Kindle proper, the reader presses a button — one for page forward, another for page back — and the entire screen blanks and refreshes as the new page loads, a transition imposed by the nature of electronic pigment. In the Kindle app, by contrast, the page slides right to left, slipping from future to present to past in a series of discrete taps.
The Instapaper application is, perhaps, truest to the nature of digital copy. It dispenses with all of this, and treats the document as one continuous environment: swipe upward when you’re ready for more. Instapaper is an acknowledgment of the text’s liberation from the constraints of crude matter. Handled this way, there’s no reason a digital text can’t return to something approximating the book’s earliest form, a scroll — in this case, one capable of unspooling without limit.
Finally, we also need to account for what it means to absorb text as a luminous projection. Marshall McLuhan drew a distinction between “light-on” media — that is, those in which content inscribed on a passive surface like paper is illuminated by an external light source — and “light-through” media, like our luminous tablets; per his insistence that medium is coextensive with message, we can assume that the selfsame text consumed in these two ways would be received differently, emotionally every bit as much as cognitively.
As it happens, I have both an actual, e-paper Kindle — digital, but nevertheless light-on — and Kindle applications for the eminently light-through iPhone and iPad. And purely anecdotally, it does seem to be the case that I have an easier time with thornier, weightier reading on the e-paper device. Novels are fine on the iPad, even on my phone…but if I want to wrestle with Graham Harman or Susan Sontag, I reach for the Kindle.
The McLuhanite in me frets that, in embracing the tablet, we inadvertently give up much of our engagement with the text. That beyond sentimentality, there is something about the act of turning a page to punctuate a thought, or the phenomenology of light reflecting off of paper saturated with ink, that conditions the act of reading and makes it what we recognize it to be, at some level beneath the threshold of conscious perception.
Which brings us back, at last, to the printed artifact. We can acknowldge that the networked tablet is a brilliant addition to any reader’s instrumentarium. I’m certain that it increases the number of times and places at which people read, and know from long, intimate and sorrowful personal experience the difference it makes where the portability of entire libraries is concerned. But it’s not quite the same thing as a book or a magazine, and cannot entirely replace them.
Curiously enough, the ambitions to which paper appears to remain best-suited are diametrically opposite:
On the one hand, deep, thoughtful engagement with a body of language, an engagement that fully leverages the craft of bookmaking. In this pursuit, the tablet cannot yet offer nearly the typographic nicety, conscious design for legibility or perceptual richness trivially available from ink on paper — all of the things, in other words, that permit the reader to immerse herself for longer, and with less strain.
But there are also occasions on which surface is all important, where the ostensible content is almost incidental to the qualities of its packaging. Here the texture or other phenomenological qualities of paperstock itself — even its smell — communicate performatively; I think of glossy lifestyle magazines. It’s hard to imagine any tablet or similar device affording these virtues in anything like the near term.
If we understand a book as a container, the precise shape that container takes ought to reflect the nature of its intended contents, and what one proposes to do with them. In acknowledging all the many virtues of networked, digital texts, the texture, tooth and heft of paper will ensure that for at least the contexts I’ve specified here, it remains irreplaceable among all the ways we contain thought as it flows from one human mind to another.
It’s been a big week hereabouts. In particular, two pieces of Do projects news to share with you:
– As you probably know, Nurri and I have been running Systems/Layers “walkshops” under the Do aegis for the last year or so, in cities from 65°N to 41°S.
As we define it, anyway, a walkshop is an activity in which anywhere up to about twenty people take a slow and considered walk through the city together, carefully examining the urban fabric and the things embedded in it, and then sharing their insights with one another and the wider world. (Obviously, you could do a walkshop on any particular urbanist topic that interested you, but we’ve focused ours on looking at the ways in which networked information-processing systems increasingly condition the mretropolitan experience.)
We’ve gotten a huge kick out of doing the Systems/Layers walks, but the simple truth is that there are so many competing claims on our time and energy that we can’t dedicate ourselves to running them full-time. We’ve also been encouraged by the result of our first experiment in open-sourcing the idea, the Systems/Layers event Mayo Nissen held in Copenhagen last June.
So when Giles Lane at Proboscis asked us if we’d consider contributing to his Transformations series, we knew right away just what we’d do. We decided to put together a quick guide to DIY walkshops, something to cover the basics of organizing, promoting and executing an event.
Last Monday, with Giles’s patient support, this idea came to fruition in the launch of Do 1101, Systems/Layers: How to run a walkshop on networked urbanism as a Diffusion eBook pamphlet. As with most things we offer, the pamphlet is released to you under the terms of a Creative Commons Attribution-Noncommercial-Sharealike license, so we expect that some of you will want to get in there and repurpose the content in other contexts.
We’ll most likely be rereleasing the Systems/Layers material our ownselves in the near future, in an extended dance mix that includes more detail, more structure, and more of Nurri’s pictures. In the meantime, we hope you enjoy the pamphlet, and let us know about the uses to which you put it.
Safety Maps is a free online tool that helps you plan for emergency situations. You can use it to choose a safe meeting place, print a customized map that specifies where it is, and share this map with your loved ones. (As it says on the site, the best way to understand how it works is simply to get started making a Safety Map of your own.)
It’s been a delicate thing to build. Given the entire framing of the site, it and the maps it produces absolutely have to work in their stated role: coordinating the action of couples, households and other small groups under the most trying of circumstances, when communications and other infrastructures may simply be unavailable. They have to do so without implying that a particular location is in fact safer than any other under a given set of conditions, or would remain accessible in the event of disaster. And they have to do so legibly, clearly, and straightforwardly.
These are utilitarian preparedness/resilience considerations, and they’re eminently appropriate. But in the end, the site springs from a different set of concerns: in Nurri’s original conception, the primary purpose of these artifacts is to prompt us to think about the people we love and the utter and harrowing contingency of the circumstances that allow us to be together. We obviously hope people find Safety Maps useful in challenging moments, but we imagine that we’d hear about this either way — whereas it’s difficult, if not impossible, for us to ever know if the site works in the way she intended it to.
Even though it was an accident of timing, Nurri also had some questions about releasing Safety Maps so soon on the heels of the Sendai earthquake/tsunami; she didn’t want us to appear to be opportunists reaping ghoulish benefit from the suffering of others. I think it was the right decision, though: sadly, there are in truth precious few windows between natural or manmade catastrophes of one sort or another. And there may be no more productive time for a tool like this than a moment in which disaster is in the news and fresh on a lot of people’s minds.
From my perspective, there’s been one other notable feature of the journey Safety Maps has taken from conception to release: but for an inversion of name, emphasis and colorway (from “Emergency Maps” in red to what you see at present), the site looks, feels and works almost identically to the vision Nurri described to me in Helsinki in October of 2009. In my experience, this almost never happens in the development of a website, and it’s a tribute both to the clarity and comprehensiveness of her original idea, and to Tom and Mike’s resourcefulness and craftsmanship.
I’m also quite fond of the thoughtful little details they’ve built into every layer of the experience, right down to the animated GIFs on the mail you get when you send someone a map. It’s just a lovely thing, and I’m terribly proud to have had even a tiny role in helping Nurri, Tom and Mike build it. Our thanks, also, to Cloudmade and the entire community of Open Street Map contributors, without whom Safety Maps would have remained nothing more than a notion.
Those of you who live in the British Isles may wish to run out and pick up a copy of this month’s Wired UK, featuring a special section on the “digital city.” As it happens, I have a piece in this section, but it’s not precisely the one I wrote.
Strictly for purposes of comparison, then, you’ll find what I intended for you to read below in its original form, bearing its original title. Enjoy.
When rumors of the project later revealed to the world as the Segway personal transporter first surfaced, back in 2001 – back in the days when the curious had little more to go on than inventor Dean Kamen’s reputation, and the cryptic codename “Ginger” – one of the more tantalizing of the few tidbits of information that did emerge was Steve Jobs’ reported reaction: “If enough people see the machine, you won’t have to convince them to architect cities around it. It will just happen.”
Architect cities around it: now that fired the imagination. What innovation could possibly be so fundamental that it would compel us to rethink something so deeply entrenched in culture, and so hard to alter, as the way we make cities? (At the very least, what might convince RDF-sporting Steve Jobs himself, of all people, that any such thing was likely?)
Speculation regarding the machine and its nature went on for months, online and off, anywhere technophiles, futurists and venture capitalists gathered. Had Kamen come up with an ultra-efficient power source? Some unexpected breakthrough in materials science? Something still further afield?
These were the obvious things to wonder about. Lying just underneath, though, were the questions that really settled into the mind and took up residence – or at least did so if that mind belonged to someone who’d grown up on Blade Runner, Judge Dredd and Angus McKie book jackets. If people really did come to devise cities around Kamen’s machine…what would those cities look like? And how would it feel to live in them?
Whatever heights the primed imagination may have scaled in these months, we know how the story ended. Already suffering from impossibly inflated expectations, the Segway launched into a world still reeling from the September 11th attacks, and in no mood for overscaled flourishes of dotcom-era technotriumphalism; to say it has not seen wide adoption in the years since would be generous. To date it’s had no appreciable effect on the cities of humanity at all, beyond the occasional column of tourists doing their best to sightsee while tilted forward at a ten-degree angle.
But the potent set of expectations that surrounded the Jobs pronouncement – that technological innovation would reshape the way we collectively make and understand cities, that we would see it happen in our historical moment, and maybe even play a role in shaping the outcomes ourselves – these were and are by no means unfounded. In fact, maybe they’re surer guides to the present than might have appeared to be the case in the immediate aftermath of the Segway’s anticlimactic launch.
It is by now clear that over the last decade a great number of people on Earth, in the developed and the developing world both – certainly the overwhelming majority of those reading these words – have embraced the digital mediation of everyday life, to such a ferocious extent that it can already be difficult to remember how we ever got through our days without the networked things around us.
Without necessarily considering the matter with any particular care, as individuals or societies, we have installed devices in our clothing, our buildings, our vehicles and our tools which register, collect and transmit extraordinary volumes of data, and which share this data with the global network in real time. If some of us once – and recently! – thought of this as the domain of “ubiquitous computing,” the words are already starting to sound obsolescent, as clunky as “horseless carriage.” This is simply the way we do things now.
And barring the usual panoply of potential catastrophes, it is only likely to be more so as time goes by, for an ever larger proportion of us. Under such circumstances, it’s only natural to expect that a great many of these systems will wind up speaking directly to the challenges cities were designed to resolve, as well as those with which they cannot help but confront us:
In the interest of managing traffic and – ostensibly – enhancing public safety, our streets are ringed with networked cameras, salted with embedded sensor grids. Where our parents might have owned one or more cars, we increasingly traverse urban space in networked vehicles that are GPS-tracked and leased to us as hourly services, or tap our way onto mass transit with RFID-enabled payment cards like London’s Oyster. (If you should happen to live in Hong Kong, Seoul, or Tokyo, that same card will serve to buy a magazine or a can of soda.) Above all, we ourselves declare the moment-by-moment choices we make to services like Twitter and Facebook.
The data sheeting off of these systems can show us where muggings and assaults happen, when and where the worst traffic arises…or simply whether there are any nearby Vietnamese restaurants open at this hour, and how highly they’re rated by their customers.
These things are fait accompli, well on their way to being unremarkable for many of us. Never mind that this kind of god’s-eye perspective on the city was impossible just a few years ago: cheap, ubiquitous, networked information processing has reshaped urban potential, every bit as dramatically as the automobile did the cities of the twentieth. And all of it in the absence of top-down guidance or orchestration: You won’t have to convince them to architect cities around it. It will just happen.
But as is so often the case, there’s a catch: the complex technologies the networked city relies upon to produce its effects remain distressingly opaque, even to those exposed to them on a daily basis.
In fact, it’s surpassingly hard to be appropriately critical and to make sound choices in a world where we don’t understand the objects around us. Understanding networked urbanism on its own terms, however wise it might be, requires an investment of time and effort beyond the reach of most. (“I learned to drive in order to read Los Angeles in the original,” said the great 20th Century architectural critic Reyner Banham, and the systems we’re talking about are orders of magnitude more complex than mere cars and freeways.)
In the networked city, therefore, the truly pressing need is for translators: people capable of opening these occult systems up, demystifying them, explaining their implications to the people whose neighborhoods and choices and very lives are increasingly conditioned by them. This will be a primary occupation for urbanists and technologists both, for the foreseeable future, as will ensuring that the public’s right to benefit from the data they themselves generate is recognized in law. If we’re reaching the point where it makes sense to consider the city as a fabric of addressable, queryable, even scriptable objects and surfaces – to reimagine its pavements, building façades and parking meters as network resources – this raises an order of questions never before confronted, ethical as much as practical: who has the right of access to these resources, or the ability to set their permissions?
All of this will be messy, and contentious, and never anything other than locally and/or partially successful. It certainly makes for a less satisfying narrative than the heroic genius all-but-singlehandedly reshaping human cities with his self-righting wondercart. But it’s the work we have cut out for us, it is profoundly worth doing, and the rewards will pay out in increments of better quality of life and a deeper, more resonant engagement with the places and people that surround us. We may as well roll our sleeves up and get started.
Sometimes I stand in awe at my friends’ talent and dedication. It happens pretty often, actually: every so often somebody I know will release a piece they’ve been working on that’s just so right it’s difficult to do anything but stand back and say: Yeah: that. That precisely. I find it both humbling and inspiring. I’m sure you know the feeling.
I never do get quite used to it, either. Today’s frisson is provided by Timo Arnall and Jack Schulze, who’ve between them put together this exquisite film illustrating near-field communication (NFC) interactions in the style of Weiss and Fischli’s The Way Things Go.
What really gets me about it is the fusion of technical insight, aesthetic sense, skill in execution and sheer patience it represents. If every made thing in the world were even one-twentieth as carefully thought out as the most offhanded gesture here, we’d all of us be in inestimably better shape. Maximum kudos.
Since the expiry, on June 30th, of the Knight Foundation grant that had been sustaining operations, I’d been more than a little concerned that the service and all the hard work that went into crafting it would disappear, so I couldn’t be happier that Everyblock has found a path to survival. You know, though, that I have questions about whether an organization like MSNBC will truly be able to keep its mitts off everything that makes Everyblock great, and I even wonder whether thinking of it as a discovery engine for “news” isn’t selling its potential a trifle short.
And that’s what the piece is about. I hope you enjoy it. (While you’re there, by the way, you should check out the other wonderful things UO is doing. In a lot of ways, it’s like a love letter to New York City, and I don’t hear its name on enough lips. Maybe you might could fix that.)