<?xml version="1.0" encoding="utf-8"?>
<feed xmlns='http://www.w3.org/2005/Atom'
      xmlns:thr='http://purl.org/syndication/thread/1.0'
      xml:base='http://craigmod.com/rss/'
      xml:lang='en-us'>

    <id>http://craigmod.com/</id>
    <title type="text">Craig Mod - Considering the future of books, publishing and storytelling</title>
    <subtitle type="text">Books are systems.</subtitle>
    <link rel="alternate" type="text/html" href="http://craigmod.com/" />
    <rights>Copyright 2001-2013 Craig Mod</rights>
    <updated>2013-06-05T06:06:58+00:00</updated>
    <generator>Expression Engine</generator>
    
    <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://craigmod.com/rss/" />
    

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2013-06-05T06:06:58+00:00</published>
      <updated>2013-06-05T06:06:58+00:00</updated>

             <title>Facebook is just fine &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/facebook" />
        <id>http://craigmod.com/satellite/facebook</id>

        <content type="html" xml:base="http://craigmod.com/satellite/facebook">
        <![CDATA[
          <a href="http://craigmod.com/satellite/facebook/"><h3>Facebook is just fine</h3></a>
                    <img src="/images/satellite/fb.jpg" width="400" />
                    
          <p><em>Note: This was also <a href="https://medium.com/how-to-use-the-internet/fb9f44469f92">posted over at Medium</a>. In part because I wanted to see how it felt to use Medium for editing (I invited a few friends to read this beforehand), and also to test the efficacy of margin commenting.</em></p>

<p>I love Facebook. </p>

<p>There, I’ve said it. </p>

<p>It’s one of the very few “social” places I’d be genuinely sad to see gone from the internet. </p>

<p>That’s crazy, right? I mean, Facebook is just a personal data farm, isn’t it? It’s just a not-too-coy set of dopamine-optimized actions to trick you into dumping information about yourself into the magic Zucker Woodchipper? And do you know what comes out of the Zucker Woodchipper? Gold nuggets. Made of advertising. And then leprechauns dump those gold nuggets into political lobbying — ha ha!</p>

<p>I’m not denying any of this. It is an ad machine, in part. But that doesn’t mean Facebook can’t also provide value. <em>(We’re partially to blame for these ad machines — we’ve given them permission to exist by not wanting to pay for things … but that’s another post.)</em></p>

<p>Ad issues aside, there is the possibility that nobody else derives the same value from Facebook that I do. Fair enough. But let me tell you why I like Facebook so much. It’s very simple.</p>

<p><strong>Facebook keeps me connected to folks I care deeply about. And more specifically: folks I care deeply about who aren’t nearby.</strong></p>

<p>That’s it. That’s the core value Facebook provides me. It’s one of my very few “emotive” online experiences. And it provides that experience daily and tangibly. </p>

<p>My newsfeed is almost all signal. This is, in part, because I am ruthless. If you are overtly negative <em>(which is different than having opinions differing from my own)</em>, you get hidden. If I don’t find value in your postings, you get hidden. If you’re a high school friend I friended just to be nice, I hide. </p>

<p>I hide unhesitatingly.</p>

<p>I hide remorselessly. </p>

<p>Hiding is your super power. Hiding is one of those few pure joys of the internet through which — amidst the near endless entropy of online content — you can take a stand, push back in a way that meaningfully affects the data you see. </p>

<p><em>(Hiding from newsfeed, it should be noted, is different from unfriending — they’ll never know.)</em></p>

<p>So, my feed is signal. Lots of signal. Lots of friends becoming parents. Getting engaged. Couples falling in love. Babies. Oh, god, the babies. (But I do like them <em>so</em>. If <em>you</em> don’t like babies — hide!) Friends and acquaintances off on adventures. Beautiful mountain photos taken during weekend trail runs. Family outings. I keep track of the orphanage a good friend of mine runs in Nepal. I am able to see what my quirky Japanese “parents” are up to. I get updates on the dog back home on the east coast of the US. She is still cute, I can report. </p>

<p>Yes, my Facebook feed is like a Facebook commercial. </p>

<p>And, no. No other internet product, service, or platform provides anything near this experience. </p>

<p>Perhaps most importantly, these folks I love get to keep tabs on me. </p>

<p>There is a qualitative difference in meeting up with someone after six months to whom you’re connected on Facebook (and actively watch) verses meeting up with someone to whom you’re not connected. Call it creepy or what you will. But there’s a lessening of perceived distance from that connection. Those six months don’t feel quite as long. And you have a shared déjà vu of general knowledge of what’s happened between you both. Artificial? I don’t think so. It’s part and parcel of the promise that social media brings to the table but rarely fulfills. </p>

<p>The more I use Facebook, the better it gets. And I find the quality of experience increases as I bring friends and family dear to my heart onto it. This is mostly because Facebook allows you to quietly prune as you go along. </p>

<p>So if you find your Facebook newsfeed full of inanity, start hiding. It’s easy. If you’re friends with a loudmouth, shut ‘em up. Simple. This isn’t magic. Facebook made it easy to hide for a reason — they know they won’t always get it right. One person can only read so many status updates in a single day. Make ‘em good. </p>

<p>Facebook algorithms are far from perfect — but they’re spectacular creatures when you consider the amount of raw data flowing through the system everyday. It takes a little effort to help them along, but if you ruthlessly prune, the signal-to-noise ratio shifts in your favor very quickly. </p>

<p>I love Facebook. Or, more accurately, I love the experiences it provides me. </p>

<p>Complaining about its doom and demise won’t make it — or the thing that follows it — better. The reality is we need algorithms to do a majority of heavy data lifting. But we also need to augment those algorithms with a little hand curation. </p>

<p>There’s no complicated trick to making Facebook better: Just hide the noise. </p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2013-04-05T22:29:25+00:00</published>
      <updated>2013-04-05T22:29:25+00:00</updated>

             <title>Wind Up Kidd Chronicle &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/kidd" />
        <id>http://craigmod.com/satellite/kidd</id>

        <content type="html" xml:base="http://craigmod.com/satellite/kidd">
        <![CDATA[
          <a href="http://craigmod.com/satellite/kidd/"><h3>Wind Up Kidd Chronicle</h3></a>
                    <img src="/images/satellite/kidd_1.jpg" width="400" />
                    
          <p><span style="font-size: .8em;">(This essay originally appeared in <a href="http://www.vqronline.org/articles/2013/spring/five-designers-books/">Virginia Quarterly Review's Spring 2013 issue</a>.)</span></p>

<p>I take them all off, the covers. As soon as I’ve paid — <em>swoosh!</em> Gone! I don’t have the heart to throw them in the garbage, but I certainly don’t let them muddle my beautiful hardcover books.</p>

<p>Contemporary covers can be rancid things. Littered with sales copy and discount stickers. They crumple, they tear, they smudge, they catch when you dump them in your bag. Once you embrace the serenity of coverless books you can never go back. Without covers, hardcover books become confident blocks of wood — they don’t shimmy or slide in your hands or atop tables. Try it. You’ll love it. You’ll never go back.</p>

<p>So it’s a rare and wonderful thing to find a contemporary book wrapped in something I just can’t remove. Or, rather, wrapped in something I love to keep on, to remove and replace, again and again. This is the case with <a href="http://www.amazon.com/gp/product/0679446699/ref=as_li_ss_tl?ie=UTF8&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0679446699&amp;linkCode=as2&amp;tag=cramod-20"><em>The Wind-Up Bird Chronicle</em></a>, my favorite book from Haruki Murakami. Designed by Chip Kidd, the cover contains only the barest of text: title and author’s name. No blurbs or quotes or synopsis. The surface of the entire cover, front to back, is a full-bleed photograph of an orange wind-up bird toy against a baby-blue background gradient. Geoff Spear photographed the toy so that most of it looms just out of focus. Only the bird’s eye — smack in the middle of the front cover — is sharp.</p>

<p><figure>
<a href="/images/satellite/kidd02.jpg"><img src="/images/satellite/kidd02.jpg" /></a>
<figcaption>Chip Kidd for Murakami Haruki</figcaption>
</figure></p>

<p>Despite such minimalism, the cover is alive. The circular path of the text, the positioning of the eye, and the sweeping patterns in the bird’s design pull your attention first to the center, then along the edge to the spine, inviting you to flip the book over and try to parse just what it is you’re looking at.</p>

<p>Now <em>tilt</em> the book: A translucent pattern shimmers across the surface. Look closer still and you’ll notice that it is, in fact, a mechanical schematic of the bird. Curious. Unwrap the cover and beneath it — printed in white ink on royal-blue chipboard — is a blueprint drawn by Chris Ware revealing the hidden complexities behind wind-up-bird mechanics.</p>

<p>Had they stopped here, Kidd and Ware and Spear could have claimed abject book-cover domination. But Ware goes one subtle step further to render the mechanics of the eye as a water well — an outer rim and an inner rim, abstracting the pupil into a perfect circle. The figure–ground relationship in this well illustration can be read in both directions: Either you’re at the bottom looking up and someone’s head is peeking over the top, or you’re at the top looking down, a small figure huddled against the well wall. Both are poignant to the story.</p>

<p>What a joy this cover is — its layers and materiality and physicality, made for print and print alone. In my library, it’s one of the very few hardcover books that has survived my rule — take them all off! Well, all except this one. Take it off and then put it back on.</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-12-06T21:39:35+00:00</published>
      <updated>2012-12-06T21:39:35+00:00</updated>

             <title>Subcompact round up and The Daily &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/subcompact_round_up" />
        <id>http://craigmod.com/satellite/subcompact_round_up</id>

        <content type="html" xml:base="http://craigmod.com/satellite/subcompact_round_up">
        <![CDATA[
          <a href="http://craigmod.com/satellite/subcompact_round_up/"><h3>Subcompact round up and The Daily</h3></a>
                    <img src="/images/satellite/subcompact_1.jpg" width="400" />
                    
          <p>A little over a week ago I published <a href="/journal/subcompact_publishing/">'Subcompact Publishing'</a>. </p>

<p>The essay is a consolidation of thoughts and prescriptions for tablet publishing. There is a <a href="/journal/subcompact_publishing/#sub_manifesto">manifesto</a> bit, too. Which is something of an update to <em>another</em> manifesto I posted nearly three years ago: <a href="/journal/ipad_and_books/">'Books in the Age of the iPad'</a>. </p>

<h3>Follow on</h3>

<p>Responses to 'Subcompact Publishing' began appearing immediately. </p>

<p>First up was Ryan on 37Signals' <em>Signal Vs. Noise</em> blog with <a href="http://37signals.com/svn/posts/3334-tablets-are-waiting-for-their-movable-type">'Tablets are waiting for their movable type'</a>:</p>

<blockquote>
  <p>Writers would love a way to push serialized content straight to tablets, and the experience would be a boon to readers. Tablets are the best way to read, and Newsstand is the equivalent of RSS for non-geeks. Hopefully apps like The Magazine inspire somebody to make this happen.</p>
</blockquote>

<p>Elliot Jay Stocks quickly responded on Medium with the <a href="https://medium.com/the-future-of-publishing/44e778827320">subcompact ethos</a> as applied to music: </p>

<blockquote>
  <p>Craig is talking about magazines here, but actually I think this can be extended to all forms of digital publishing, and it sparked off a very specific thought in my mind: that the enjoyment of consuming digital media is increased when we only have a small amount to consume.</p>
</blockquote>

<p>Then the prolific <em>GigaOm</em> writer, Matthew Ingram, up and slapped subcompact on everything in his <a href="http://gigaom.com/2012/11/30/sub-compact-media-rethinking-the-way-we-publish-online/">'Sub-compact Media'</a> piece:</p>

<blockquote>
  <p>Why aren’t more traditional publishers experimenting with features or services that are similar to Arment’s magazine, or Tapestry’s mobile approach, or a stripped-down experience like that offered by TL;DR or Circa? It’s not because they can’t — obviously they could if they wanted to. But as Craig Mod suggests in his essay, with reference to disruptive economics guru Clay Christensen, they don’t do this for the same reason North American auto-makers didn’t compete with Honda: they simply didn’t see it as a competitor until it was almost too late, because they had defined their business in the wrong way.</p>
</blockquote>

<p>A few days following that post I noticed a strange referrer in my logs: <a href="http://theperiodical.co/">The Periodical Co.</a> It appeared to be a newly minted, suspiciously subcompact service. Hamish Mckenzie did a little sleuthing and <a href="http://pandodaily.com/2012/12/03/get-ready-for-the-age-of-premium-micropublishing/">covered this mysterious company</a> in a post on Pando Daily: </p>

<blockquote>
  <p>It took Shahruz Shaukat (21), David Mancherje (28), and Cyrus Ghahremani (25) just 26 hours during the Los Angeles event of the AngelHack Hackathon to build a working demo of The Periodical Co, a product the men are calling “Digital Magazines as a Service.”</p>
</blockquote>

<p>And then:</p>

<blockquote>
  <p>To Shaukat, Mod’s argument made total sense. “When I read the Craig Mod article where he defines subcompact publishing, every line I was reading I was nodding my head,” he says. “I don’t think my opinions on it were fully formed until I read that article.” And so, they set to work on a publishing tool that, in their words, “would not offend readers with graphics or interactive elements that are just distractions.” It’s all about the reading, baby.</p>
</blockquote>

<p>Which is — really — the whole point of posting these things: To inspire, clarify, and solidify ideas for other to take and run. I'm firmly of the belief that you can <em>give away</em> a lot and the peripheral benefits will fall into place. Seeing The Periodical Co., even in its nascent shell, made me smile something wide. </p>

<p>Jason Kottke — <em>whose site I have been reading for nearly 13 years</em> — responded with, <a href="http://kottke.org/12/12/trend-alert-small-internet-publications">'Trend alert: small internet publications'</a>: </p>

<blockquote>
  <p>For the longest time, the web was all like "blog blog blog blog" and we were like "fave fave fave like like like" but a bunch of recent publications and publishing systems seem to be breaking out of that mode. Craig Mod calls it Subcompact Publishing. Not sure I like the name, but I dig his gist. </p>
</blockquote>

<p>Bill Mickey over at <em>Folio</em> posted a <a href="http://www.foliomag.com/2012/response-subcompact-publishing#.UMET28pU7jL">'Response to Subcompact Publishing'</a>, raising questions about the future landscape of tablet publishing:</p>

<blockquote>
  <p>I understand that with digital comes an expectation of disruption and re-invention. And not just an expectation, but actual disruption. But it's also a world where all sorts of business models live and play.</p>
</blockquote>

<p><a href="http://om.co">Om</a> very kindly added 'Subcompact Publishing' to his list of <a href="http://gigaom.com/2012/12/01/7-stories-to-read-this-weekend-46/">'7 stories to read this weekend'</a>. It was also picked up by <em>The Association of Magazine Media</em> in their piece, <a href="http://www.magazine.org/disruption-through-simplicity-digital-magazines">'Disruption Through Simplicity in Digital Magazines'</a>. </p>

<p><strong>AND THEN:</strong> <em>The Daily</em> folded. </p>

<h3>Daily responses</h3>

<p>Murdoch's <em>The Daily</em> was — in nearly <em>every</em> respect — the polar opposite of a subcompact publishing tool, platform, or publisher. It didn't take long for others to notice that, either. </p>

<p>MG Siegler was first out the gate with, <a href="http://techcrunch.com/2012/12/04/the-dakly-died-of-suckage/">'Why Magazine Apps Suck'</a>:</p>

<blockquote>
  <p>But the magazines and newspapers are stuck in the old way of doing things. They need to evolve &hellip; What if instead of pushing out all your content on a monthly basis, you released a weekly “mini” version with new content and live updates as needed? Instead of getting one giant dump of content one time a month (most of which people probably won’t have time and/or desire to read), you’d get four manageable deliveries a month.</p>
</blockquote>

<p>John Pavlus at MIT's <em>Technology Review</em> posted <a href="http://www.technologyreview.com/view/508166/how-to-publish-a-minimum-viable-magazine-online/">'How To Publish a Minimum Viable Magazine Online'</a>: </p>

<blockquote>
  <p>Shocking no one, News Corporation’s iPad-only publication “The Daily” kicked the bucket today. While future-of-journalism sites ponder the why’s and wherefores, technologists like Marco Arment and Craig Mod may have already identified a working alternative. Their connections to the journalism or publishing “industry” as we’ve understood it for the past century are tenuous at best–Arment is a programmer who built Tumblr and Instapaper, while Mod was a product designer at Flipboard. And that outsider status is precisely why they’re onto something.</p>
</blockquote>

<p>Joshua Benton absolutely nails it in his <em>The Daily</em> post-mortem over at Nieman Labs — <a href="http://www.niemanlab.org/2012/12/some-lessons-from-the-demise-of-the-daily-was-it-the-platform-the-content-the-structure-or-the-business-model/">'Some lessons from the demise of The Daily'</a>: </p>

<blockquote>
  <p>Here’s the thing: The Daily had over 100,000 paying subscribers. That ain’t nothing! With most subscribers paying $39.99 a year (others paid 99 cents a week), minus Apple’s cut, that’s around $3 million in annual revenue — and that’s before you add in advertising revenue. At various points, it was the highest-grossing app in the App Store in 13 different countries. In the United States, it’s been in the top 5 of news apps by gross since launch and, until this summer, consistently in the top 20 of all apps — even including Angry Birds and the rest.</p>
</blockquote>

<p>In the end, <em>The Daily</em> chose the wrong slice from the tablet publishing distribution dichotomy. Right now (and certainly two years ago!) you get to choose one, and only one: </p>

<ul>
<li><strong>Large → Many:</strong> A huge publication with massive overhead that's distributed <em>everywhere</em></li>
<li><strong>Small → Few:</strong> A lean publication with small overhead that's laser focused on a single platform</li>
</ul>

<p>They went for the most ridiculous non-option: a huge publication with massive overhead, laser focused on a single platform. </p>

<p>An odd choice for a group that had the resources to pull off <strong>Large → Many</strong>. If <em>The Daily</em> had created a real open-web presence, and had considered — at the very least — an iPhone app, maybe things wouldn't have looked so bleak. </p>

<p>Regarding the other non-option — <strong>Small → Many</strong> — you <em>could</em> try to start a lean publication with small overhead distributed on every platform. Unfortunately the lack of cross platform tools means it's not trivially easy to do well (especially if you want subscriptions / payment options).</p>

<p><em>This</em> right here: the difficulty in one-button, cross-tablet, cross-platform publishing, is a gaping hole in our digital publishing ecosystems, ready to be filled by a smart startup. The only real Small → Many option right now is the open web. </p>

<h3>More!</h3>

<p>It <em>also</em> just so happened that <em>The Awl</em> launched their new <em>Weekend Companion</em> days before <em>The Daily</em> folded. </p>

<p><a href="http://www.29.io/">29th Street Publishing</a> is the company that makes the software that powers <em>The Awl</em>. And low and behold — it's pretty darn subcompact. Nieman Labs covers them and <em>The Awl</em> in <a href="http://www.niemanlab.org/2012/12/29th-street-publishing-wants-to-make-selling-magazines-for-ipads-as-easy-as-blogging/">'29th Street Publishing wants to make selling magazines for iPads as easy as blogging'</a>:</p>

<blockquote>
  <p>“Very much like Movable Type and WordPress, we want to be a tool people can use to have their work go further and make deeper relationships with their readers,” he said. That approach is something Jacobs and one of his 29th Street cofounders, Natalie Podrazik, understand, since both came from Six Apart, the company responsible for blogging software like Movable Type and TypePad. (29th Street’s team also includes, among others, former NewYorker.com editor Blake Eskin and blogger-since-the-early-days Greg Knauss.)</p>
</blockquote>

<p>Which is great, because this feels like the universe responding to Ryan over at <em>SvN</em>: <em>ex-Movable Type folks making the next Movable Type for tablets</em>. </p>

<p>Even the death of <em>The Daily</em> — though easy to label 'failure' — is anything, in my opinion, <em>but</em> a failure. What it's done is shown us you can't build a print island in the middle of our digital ocean. Yes: many of us knew that. But, still, to <em>see</em> an old-school structured publishing institution thrust upon this new space, have it willfully ignore many of the rules-of-engagement obvious to us, and then fail means we are, indeed, somewhere new. It's nice to be able to say that with reinforced confidence. </p>

<p>There's a lovely Jung-ian collective unconscious chaos-made-visible feeling when you map out thought streams like this. When I wrote Subcompact Publishing I had a hazy inkling that there was a growing interest in this kind of publishing tool, now it's much clearer. </p>

<p>Please <a href="mailto:me@craigmod.com">let me know</a> if I missed anything. </p>

<hr />

<h3>All the links</h3>

<p>Here's a roundup (ordered, vaguely, in decreasing order by traffic) of subcompact related links:</p>

<ul>
<li>John Gruber, <a href="http://daringfireball.net/linked/2012/11/27/subcompact-publishing">'Subcompact Publishing'</a>, <em>Daring Fireball</em>, November 2012</li>
<li>Marco Arment, <a href="http://www.marco.org/2012/11/26/subcompact-publishing">'Subcompact Publishing'</a>, <em>marco.org</em>, November 2012</li>
<li>MG Siegler, <a href="http://techcrunch.com/2012/12/04/the-dakly-died-of-suckage/">'Why Magazine Apps Suck'</a>, <em>TechCrunch</em>, December 2012</li>
<li>Jason Kottke, <a href="http://kottke.org/12/12/trend-alert-small-internet-publications">'Trend alert: small internet publications'</a>, <em>kottke.org</em>, December 2012</li>
<li>Hamish McKenzie, <a href="http://pandodaily.com/2012/12/03/get-ready-for-the-age-of-premium-micropublishing/">'Get ready for the age of premium micropublishing'</a>, <em>PandoDaily</em>, December 2012</li>
<li>Ryan, <a href="http://37signals.com/svn/posts/3334-tablets-are-waiting-for-their-movable-type">'Tablets are Waiting for their Movable Type'</a>, <em>Signal Vs. Noise</em>, November 2012</li>
<li>Om Malik, <a href="http://gigaom.com/2012/12/01/7-stories-to-read-this-weekend-46/">'7 stories to read this weekend'</a>, <em>GigaOm</em>, November 2012</li>
<li>Dante D'Orazio, <a href="http://www.theverge.com/2012/11/27/3697702/rethinking-publishing-for-digital-consumption">'Rethinking Publishing for the Age of Digital Consumption'</a>, <em>The Verge</em>, November 2012</li>
<li>John Pavlus, <a href="http://www.technologyreview.com/view/508166/how-to-publish-a-minimum-viable-magazine-online/">'How To Publish a "Minimum Viable Magazine" Online'</a>, <em>MIT Technology Review</em>, December 2012</li>
<li>Justin Ellis, <a href="http://www.niemanlab.org/2012/12/29th-street-publishing-wants-to-make-selling-magazines-for-ipads-as-easy-as-blogging/?fromfloater">'29th Street Publishing wants to make selling magazines for iPads as easy as blogging'</a>, <em>Nieman Journalism Lab</em>, December 2012</li>
<li>Rob Beschizza, <a href="http://boingboing.net/2012/11/28/subcompact-publishing.html">'Subcompact Publishing'</a>, <em>BoingBoing</em>, November 2012</li>
<li>Bill Mickey, <a href="http://www.foliomag.com/2012/response-subcompact-publishing#.UL43S6FU7jL">'A Response to 'Subcompact Publishing'</a>, Folio, November 2012
<!--* <a href="http://waxy.org/links/archive/2012/12/index.shtml">sp</a>--></li>
<li>Ben Brooks, <a href="http://brooksreview.net/2012/11/newsstand-publishing/">'Newsstand, Publishing, Apps, and Developers'</a>, <em>Brooks Review</em>, November 2012</li>
<li>Shawn Blanc, <a href="http://shawnblanc.net/2012/11/mod-publishing/">'Subcompact Publishing'</a>, <em>Shawn Blanc</em>, November 2012
<!--* <a href="http://nextberlin.eu/2012/12/coming-next-cameras-rewriting-your-brain-and-disruption-dissected/">Next Berlin</a>--></li>
<li>Jean Snow,<a href="http://themagaziner.com/2012/11/subcompact-publishing/">'Subcompact Publishing'</a>, <em>The Magaziner</em>, November 2012</li>
<li>Ethan Grey, <a href="http://www.magazine.org/disruption-through-simplicity-digital-magazines">'Disruption Through Simplicity in Digital Magazines'</a>, <em>The Association of Magazine Media</em>, November 2012</li>
<li>John Del Signore, <a href="http://gothamist.com/2012/12/03/the_daily_is_now_the_never_news_cor.php">'The Daily Is Now The Never: News Corp. Shuts Down iPad Publication'</a>, <em>Gothamist</em>, December 2012</li>
<li>Jay Nelson, <a href="http://www.planetquark.com/2012/12/03/does-our-future-require-subcompact-publishing/">'Does Our Future Require “Subcompact Publishing”?'</a>, <em>Planet Quark</em>, December 2012</li>
</ul>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-11-30T08:26:18+00:00</published>
      <updated>2012-11-30T08:26:18+00:00</updated>

             <title>An invitation — Roden Explorers &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/invitation" />
        <id>http://craigmod.com/satellite/invitation</id>

        <content type="html" xml:base="http://craigmod.com/satellite/invitation">
        <![CDATA[
          <a href="http://craigmod.com/satellite/invitation/"><h3>An invitation — Roden Explorers</h3></a>
                    <img src="/images/satellite/james_1.jpg" width="400" />
                    
          <p>My first exposure to James Turrell came sometime in winter 2003, after a harrowing drive through the Japanese night. I was in a van with two Americans, a Japanese, an older — supposedly famous — French illustrator, a Belgian artist, a Swedish photographer, and another Frenchman, drunk — quite obviously so — and driving. </p>

<p>That configuration didn’t last very long. </p>

<p>Despite the fact that many of us had never met before, the consensus shifted quickly. The drunk Frenchman — against his vocal pleading that <em>He was fine! He can drive just fine!</em>  — would be replaced as driver. I was the only other passenger with an international license.</p>

<p>So it came to be that I drove this group of rag-tag bohemians and artists and drunkards through the night — my first time driving such a large vehicle, and also my first time driving in Japan. We hurtled down freeways draped in countryside darkness, past rice fields, music blaring, joyful, multi-accented English bouncing all over the interior, the Frenchman snoring in a heap in the back. </p>

<p>We were bound for the newly opened 21st Century Museum in Kanazawa,<sup id="fn-ref-86-1"><a href="#fn-86-1">1</a></sup> butted against the harsh Sea of Japan on the northern coast. James Turrell had a room there.</p>

<p>I had never before heard of this Turrell fellow. Everyone spoke well of his work so I was excited — naturally. </p>

<h3>Skyspace</h3>

<p>His room at the 21st Century Museum is like many of his rooms — a tomb with a rectangular hole cut in the center of the ceiling. One of his 'Skyspaces.' </p>

<p>I arrived at dusk. I sat. I looked up at the hole. I watched the sky darken. I felt the freezing air pour in through the open roof. I pulled my scarf up around my face. Then I left. </p>

<p><figure><img src="/images/satellite/turrell/skyspace_21.jpg" /><figcaption>Skyspace at 21st Century Museum, Kanazawa, Japan — &copy; <a href="http://www.flickr.com/photos/kalevkevad/1935585520/in/photostream/">kalevkevad</a></figcaption></figure></p>

<p>Still curious, I returned the next morning and sat again. The hole framed a crisp, deep blue Japanese winter sky. Suddenly a cloud floated past. Then some birds flew over. The construction was such that the material forming the hole in the roof was tapered to almost nothing. </p>

<p>This tapering produced the optical illusion — as you continued to stare — that the sky was pulled down to the very ceiling of the room. You could touch it. And when something moved past, it felt compressed and unreal.</p>

<p><figure><img src="/images/satellite/turrell/house_of_light.jpg" /><figcaption>Turrell's collaboration with architect, Daigo Ishii</figcaption></figure></p>

<p>And so began my minor obsession with James’ work. I’ve spent the night in his house in Niigata<sup id="fn-ref-86-2"><a href="#fn-86-2">2</a></sup> — a stunning collaboration with Japanese architect Daigo Ishii<sup id="fn-ref-86-3"><a href="#fn-86-3">3</a></sup> in which you sleep in a twelve mat tatatmi room. At the touch of a button, the roof slides off the house and a sky viewing timed perfectly to sunrise and sunset begins. You lie there, dazed, witness to the majesty of a darkness <em>(as the sun sets)</em> and color gradation <em>(as the sun rises)</em> you’ve never before seen. </p>

<p>This past summer I traveled to Naoshima on pilgrimage to James’ installations in the Tadao Ando designed, Chichu Art Museum.<sup id="fn-ref-86-4"><a href="#fn-86-4">4</a></sup> And I’ve hunted down small collections of his less consuming light installations at various museums and galleries around the world. </p>

<p><figure><img src="/images/satellite/turrell/crater.jpg" /><figcaption>Roden Crater</figcaption></figure></p>

<h3>Roden</h3>

<p>It was within this <em>lighthearted</em> decade long investigation of James’ work that I discovered his Roden project.<sup id="fn-ref-86-5"><a href="#fn-86-5">5</a></sup> Roden is the name of a crater in Arizona James bought in the 70s. It’s become an icon not just for his Life Work but for the ideal to which — I believe — many of us strive as creators. It is a myth — far larger than life in both ideological scope and physicality. </p>

<p>Here's James' description of the project: </p>

<blockquote>
  <p>At Roden Crater I was interested in taking the cultural artifice of art out into the natural surround. I did not want the work to be a mark upon nature, but I wanted the work to be enfolded in nature in such a way that light from the sun, moon and stars empowered the spaces … I wanted an area where you had a sense of standing on the planet. I wanted an area of exposed geology like the Grand Canyon or the Painted Desert, where you could feel geologic time. Then in this stage set of geologic time, I wanted to make spaces that engaged celestial events in light so that the spaces performed a “music of the spheres” in light. The sequence of spaces, leading up to the final large space at the top of the crater, magnifies events. The work I do intensifies the experience of light by isolating it and occluding light from events not looked at. I have selected different portions of the sky and a limited number of events for each of the spaces. This is a reason for the large number of spaces.</p>
</blockquote>

<p>Did you read that? <em>Then in this stage set of geologic time</em> &hellip; </p>

<h3>Explorers</h3>

<p>It’s with this work in mind I’d like to start a mailing list: <a href="/explorers/"><em>The Roden Explorers Club</em></a>. </p>

<p>It'll be a little more private than posting on this site. A little more ephemeral, perhaps. Like a crater in the desert: there if you look on Google Maps, but usually out of sight.</p>

<p>I'd like for it to be a place for me to announce small projects built with a <em>pinch</em> of James’ ethos in mind. Somewhere to ask folks for feedback. Somewhere to share off-the-cuff thinking about the future of books and publishing. A place for you to hit 'reply' outside of the public spectacle of comments and tweets.</p>

<p>The mailing list will have almost nothing to do <em>explicitly</em> with Roden, of course. Roden is just a guiding star, far off in our desert sky. </p>

<p>If any of this interests you, then please consider joining me and becoming an <em>Explorer</em>. The messages will be infrequent, and you can unsubscribe at anytime. </p>

<p>Together we'll hurtle out under the darkness of the interwebs towards whispers of who knows what. Hopefully joyful, joyfully hopeful, and, perhaps, a bit drunk.</p>

<p>So, see you out there?</p>

<h3>Subscribe</h3>

<div style="display: none;" id="thanks">
  <p>Subscribed — thanks!</p>
</div>

<form action="http://bookswemake.createsend.com/t/r/s/jyjudyh/" method="post" id="subForm">
  <div>
    <input type="text" placeholder="email address" name="cm-jyjudyh-jyjudyh" id="jyjudyh-jyjudyh" />
    <button type="submit" class="btn btn-primary" onClick="_gaq.push(['_trackPageview', '/goal/mailing-list-via-roden']);">Subscribe</button>
  </div>
</form>

<!-- 2. Add some JavaScript -->

<script type="text/javascript">
    $(function () {
        $('#subForm').submit(function (e) {
            e.preventDefault();
            $.getJSON(
            this.action + "?callback=?",
            $(this).serialize(),
            function (data) {
                if (data.Status === 400) {
                    alert("Error: " + data.Message);
                } else { // 200
                    $("#subForm").fadeOut('slow', function() {
                                  $("#thanks").fadeIn("slow");
                                }); 
                }
            });
        });
    });
</script>

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-86-1"><a href="http://www.kanazawa21.jp/en/">Kanazawa, 21st Century Museum</a> <a href="#fn-ref-86-1">&#8617;</a></li>
	<li id="fn-86-2"><a href="http://www11.ocn.ne.jp/~jthikari/">House of Light (光の館), Niigata, Japan <a href="#fn-ref-86-2">&#8617;</a></li>
	<li id="fn-86-3"><a href="http://www.future-scape.co.jp/">Future Scape — Daigo Ishii, Architects <a href="#fn-ref-86-3">&#8617;</a></li>
	<li id="fn-86-4"><a href="http://en.wikipedia.org/wiki/Chichu_Art_Museum">Chichu Art Museum</a> <a href="#fn-ref-86-4">&#8617;</a></li>
	<li id="fn-86-5"><a href="http://rodencrater.com/">Roden Crater</a> <a href="#fn-ref-86-5">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-11-26T01:10:45+00:00</published>
      <updated>2012-11-26T01:10:45+00:00</updated>

             <title>Subcompact Publishing &#45; Craig Mod &#45; Journal</title>
        
        <link href="http://craigmod.com/journal/subcompact_publishing" />
        <id>http://craigmod.com/journal/subcompact_publishing</id>

        <content type="html" xml:base="http://craigmod.com/journal/subcompact_publishing">
        <![CDATA[
          <a href="http://craigmod.com/journal/subcompact_publishing/"><h3>Subcompact Publishing</h3>
          <img src="http://craigmod.com/" />
          </a>
          <p>&hellip; Zip drives ate floppies. <br />
<span class="sc">CD</span>s ate Zips. <br />
<span class="sc">DVD</span>s ate <span class="sc">CD</span>s. <br />
<span class="sc">SD</span> cards ate film. <br />
<span class="sc">LCD</span>s ate <span class="sc">CRT</span>s. <br />
Telephony ate telegraphy. <br />
Text messaging ate talking. <br />
Tablets are eating our paper &hellip;</p>

        ]]>
        </content>

          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-10-31T15:54:01+00:00</published>
      <updated>2012-10-31T15:54:01+00:00</updated>

             <title>Unbindings and edges &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/unbinding" />
        <id>http://craigmod.com/satellite/unbinding</id>

        <content type="html" xml:base="http://craigmod.com/satellite/unbinding">
        <![CDATA[
          <a href="http://craigmod.com/satellite/unbinding/"><h3>Unbindings and edges</h3></a>
                    <img src="/images/satellite/unbinding-title_1.jpg" width="400" />
                    
          <p>On January 1, 2013, Newsweek goes unbound, but perhaps more interestingly, it becomes unbounded: Diffuse &hellip; Etherial &hellip; <em>Digital!</em><sup id="fn-ref-85-1"><a href="#fn-85-1">1</a></sup></p>

<p>It's worth taking a moment to meditate on this — the unbinding. It's a phenomenon particular to our liminal stage in digital publishing. One in which we move from physical to digital. It hasn't really happened before — there was no digital to move to.<sup id="fn-ref-85-2"><a href="#fn-85-2">2</a></sup> And, in a few years, it probably won't happen very often, if ever — all publications will start with digital. </p>

<p>I wrote an op-ed over on CNN last week called, <a href="http://www.cnn.com/2012/10/21/opinion/mod-digital-magazines/index.html"><em>How magazines will be changed forever</em></a>.<sup id="fn-ref-85-3"><a href="#fn-85-3">3</a></sup> </p>

<p>The intent wasn't to wax overly nostalgic,<sup id="fn-ref-85-4"><a href="#fn-85-4">4</a></sup> but instead to focus our attention on the one quality inherent to physical that I believe is underrepresented in digital: <em>edges.</em> </p>

<h3>Outer limits</h3>

<p>The CNN piece begins:</p>

<blockquote>
  <p>Forget everything we know and love about physical magazines. Forget their length. Forget their size. Forget their weekly or monthly publishing schedule. Forget all these qualities except for one: What it's like to come to an end, and to take a deep breath.</p>
</blockquote>

<p>What does a bookend — an edge — mean for narrative arc? Broadly, it helps define the <em>shape</em> of the arc. The <em>experience</em> of a bundle of content changes depending on how it's packaged. </p>

<p><a href="http://storify.com">Storify</a> exemplifies this: By bookending a cohort of tweets, you remove them from the firehose and create a coherent, consumable narrative. </p>

<p>In other words: It's difficult to shape a narrative without a pause, just as it's hard to craft a beautiful page without whitespace. Possible, but unlikely. </p>

<p>Related: Is Gangnam Style <a href="http://static.echonest.com/InfiniteGangnamStyle/">as potent</a> if it never resolves itself?</p>

<h3>Rigorous form</h3>

<p>Nicholas Carr (<em>The Shallows</em>) <a href="http://www.roughtype.com/?p=2019">posted a followup to my CNN piece on his blog</a>. It begins:</p>

<blockquote>
  <p>One of the advantages of embedding culture in nature, of requiring that works of reason and imagination be given physical shape, is that it imposes on artists and thinkers the rigor of form, particularly the iron constraints of a beginning and an ending, and it gives to the rest of us the aesthetic, intellectual, and psychological satisfactions of having a rounded experience, of seeing the finish line in the distance, approaching it, arriving at it.</p>
</blockquote>

<p>The 'rigor of form' is part and parcel of physical output, but it is something we have to work harder for in digital. </p>

<h3>Data</h3>

<p>You can apply <em>rigor of form</em> beyond creative output — to all data. </p>

<p>Facebook, for example, works <em>really</em> hard to shave down your ~10,000+ daily newsfeed items to a high-signal:low-noise ratio stream. It tells an eminently consumable version of the story of your friends' lives over the past day. And if you don't like how the algorithm is working, Facebook offers users a host of manual levers to further increase signal. All of these levers and tunnels in the algorithm manifest as edges. And those edges make the unconsumable, consumable. </p>

<h3>Apps</h3>

<p>In 2010, the <em>New York Times</em> showcased an app during the iPad launch event. It was called "Editors Choice" and was available when iPad went on sale. Editors Choice was simple. Delightful, even. It contained just a few dozen articles. Selected daily by — one would assume — a cadre of <em>Times</em> editors. This limited selection made it feel handpicked. Filtered by a higher power that said, <em>"This! This is all you need today!"</em> </p>

<p>As you read each article, it turned grey. Once they were all grey, you were done. You could breathe. </p>

<p><figure><img src="/images/satellite/editorschoice.jpg" alt="Editors Choice"/><figcaption>Editor's Choice — a nytimes you could 'finish'</figcaption></figure></p>

<h3>More</h3>

<p>Ask us if we want more and we often say yes. More timeline. More newsfeed. More articles. </p>

<p>iOS star developer Loren Brichter (creator of the original OS X and iOS Twitter clients) is credited with inventing the now ubiquitous <a href="http://www.macstories.net/news/loren-brichter-talks-about-pull-to-refresh-patent-and-design-process/">pull-to-refresh</a>. In some ways it's a near perfect gesture — attuned to our endless appetite. </p>

<p>We pull a lever. We get more [insert delicious content]. <em>Pull pull pull. More more more.</em></p>

<p><em>The New York Times</em> app has long since been replaced with its current version containing all of the newspaper. And while I understand the need for a completely inclusive reading space — especially across a news machine as big as <em>The Times</em> — I still admire the short lived — if, possibly, accidental — philosophical stand taken in Editor's Choice. </p>

<p>There's a reason <em>Most Emailed</em> and <em>Top Ten</em> article lists are so very popular: They're one of the few bounded datasets on a newspaper home page. They're high-signal lists, infrequently updated, that you know you can complete.</p>

<p>In the CNN piece I continue: </p>

<blockquote>
  <p>Linda Stone created the term "e-mail apnea" to describe holding your breath as you traverse the horrors of your inbox. I find myself experiencing digital apnea of all sorts. Google News apnea. Twitter apnea. Facebook newsfeed apnea. RSS reader apnea. In the face of endless content streams, it's hard to stop and take a breath.</p>
</blockquote>

<p>*<em>pause</em>*</p>

<blockquote>
  <p>There is no print apnea. Perhaps, at worst, one may experience library apnea -- standing before the vast greatness of the reading room in the British Museum, for example. But even then, it's different. There's the cozy smell of old books and the softness of the aged pages. It's more akin to basking in grandeur than to suffocating under information overload. It's hard to feel the same reverence for our 24/7 Twitter feeds.</p>
</blockquote>

<p>It's easy for conversations around these topics to devolve into diatribes against information overload, self control, 32oz sodas, etc. Ignoring lurking moral quagmires, there's certainly a time and place for the endless slurping of tweets. But, generally, I also think most of us would be grateful for less noise and more signal. For clearer narratives around amorphous data blobs. </p>

<p>Bringing the ethos of physical edges to digital spaces is all about increasing that signal.</p>

<p>Newsweek may soon be unbound, but just because it's digital doesn't mean it has to be unbounded.</p>

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-85-1"><a href="http://www.thedailybeast.com/articles/2012/10/18/a-turn-of-the-page-for-newsweek.html">A turn of the page for Newsweek</a>, <em>The Daily Beast</em> <a href="#fn-ref-85-1">&#8617;</a></li>
	<li id="fn-85-2">There were variants of physical to physical, and arguably, intangible to tangible (spoken histories to written histories), but not tangible to intangible like this. <a href="#fn-ref-85-2">&#8617;</a></li>
	<li id="fn-85-3">I've also written extensively about <a href="/journal/digital_physical">jumping between digital and physical</a> states on this website. It's a long piece but approaches the subject from a more media agnostic place.  <a href="#fn-ref-85-3">&#8617;</a></li>
	<li id="fn-85-4">If you read me regularly you know that I'm pro-digital with a strong humanist slant. Any implied nostalgia isn't for a bygone era of things printed, but a rally to take a few moments, step back and make sure we cultivate an awareness of where we are. Sometimes slowing down means faster progress, and I'm all for progress. <a href="#fn-ref-85-4">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-10-11T18:05:06+00:00</published>
      <updated>2012-10-11T18:05:06+00:00</updated>

             <title>Our bit heavens &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/fitbit" />
        <id>http://craigmod.com/satellite/fitbit</id>

        <content type="html" xml:base="http://craigmod.com/satellite/fitbit">
        <![CDATA[
          <a href="http://craigmod.com/satellite/fitbit/"><h3>Our bit heavens</h3></a>
                    <img src="/images/satellite/paris_datamind.jpg" width="400" />
                    
          <p>When I was a child I believed in a heaven. </p>

<p>One of the best features in my little heaven was a magic <span class="sc">VCR</span> <em>(I'm a child of the 80s)</em>. This <span class="sc">VCR</span> had <em>every moment</em> of your life in it. You could go back and relive any of them. You could also get inside the heads of <em>other people</em> at any moment, and you could change perspective. You could jump inside of <em>their</em> <span class="sc">VCR</span>s and play their lives.</p>

<h3>Paris, walking, data minds and towers</h3>

<p><a href="http://www.themorningnews.org/article/paris-and-the-data-mind"><em>Paris and the data mind</em></a> is about a little slice of that heaven <em>(or hell, for some)</em>. Andrew Womack at <em>The Morning News</em> took it on as editor and we threw it back and forth for a month. <a href="http://www.themorningnews.org/article/paris-and-the-data-mind">Check it out</a> — it was a blast to work on. </p>

<p><a href="http://www.amazon.com/gp/product/B005PUONKS/ref=as_li_ss_tl?ie=UTF8&amp;camp=1789&amp;creative=390957&amp;creativeASIN=B005PUONKS&amp;linkCode=as2&amp;tag=cramod-20"><img src="/images/satellite/fitbit/fitbit_full.jpg" alt="Fitbit Ultra" /></a></p>

<p>Buying a <a href="http://www.amazon.com/gp/product/B005PUONKS/ref=as_li_ss_tl?ie=UTF8&amp;camp=1789&amp;creative=390957&amp;creativeASIN=B005PUONKS&amp;linkCode=as2&amp;tag=cramod-20">Fitbit</a> inspired much of the thinking that led to the essay. Even now, months after my experience in Paris, I continue to dutifully clip it on. Which is to say: I wholeheartedly <a href="http://www.amazon.com/gp/product/B005PUONKS/ref=as_li_ss_tl?ie=UTF8&amp;camp=1789&amp;creative=390957&amp;creativeASIN=B005PUONKS&amp;linkCode=as2&amp;tag=cramod-20">recommend the product</a>, strange little thing it may be.</p>

<h3>Awareness</h3>

<p>More generally though, <a href="http://www.themorningnews.org/article/paris-and-the-data-mind"><em>Paris and the data mind</em></a> is an essay about our digital squirreling. About that heaven I dreamt of as a child. </p>

<p>It's about awareness — both taken and given — by digital devices. It's about the Church of the Data Mind; a church we're all subscribing to, whether or not we acknowledge it. It's about making sense of this <em>digital-self</em> detritus we're amassing. </p>

<p>From the essay:</p>

<blockquote>
  <p>I think of our checkins, our food photos, our tagged friends. I think of our steps, our Fuel Points. I think of the myriad and nearly endless stream of data — data now actively collected but becoming increasingly passive. I think of all of this and I can't help but see a hologram projected somewhere off in the distance. A reconstitution of something, some<em>one</em>, miles away, years out. </p>
  
  <p>Who <em>is</em> that hologram?</p>
</blockquote>

<p>It's us, right? I mean, it's not a 1:1 precise reconstitution, but it's something. We're currently in the  'self-selection' phase of personal data collection. Meaning, we have a bit of control over <em>what</em> goes into our collection. But this phase is transitory and fleeting, dovetailing into the totally passive, collect-it-all phase. Which raises the question: what does 1:1 look like? </p>

<p>In recent speaking engagements I've mentioned a 'corpus' — a corpus of data as created by publishers, and the corpus of data as collected by us. And I've spoken about how we are slowly habituating the collection of events — 'real' events in meat space. And how, psychically, I've felt an unexpected twist amidst all this collecting. I've felt that things <em>not</em> recorded in the ether, not <em>tagged</em> or <em>checked in</em> don't feel quite as real. They're fleeting. Given to the whim of my ever degrading memory. </p>

<p>And <em>that</em> — that feeling of 'real' events added to digital space becoming, somehow, <em>more</em> real, more existent, is a very strange thing indeed. A reverse <a href="http://www.robinsloan.com/note/flip-flop/">flip-flop</a> from that which I wrote about in <a href="/journal/digital_physical/">The Digital⇄Physical</a>. </p>

<h3>Everything</h3>

<p>The more I collect — the larger my corpus becomes — the more I think back to that data heaven I had seen as a child. The cyber punk'd, fluffy, bright, cloud filled expanse of endless VCRs and dusty CRT screens. </p>

<p>In imagining this heaven I would make lists of all the <em>amazing</em> lives into which I'd hop. Not just hop into, of course, but also scrub through. How I'd get lost down the sub-lives of other people who would appear in main streams. How those sub-lives would become main-lives and the sequence would continue on down an infinite recursion. </p>

<p>To me, it was a no brainer: exploring these fractals could easily fill up an eternity, however long that was. And man, oh man, did that sound like some fun magic. </p>

<p>So how close are we to this? This kind of scrubbing. Once gone, in what format do we leave our lives? And what is the value of a life spent exploring other lives? </p>

<p>All of this weirdness is wrapped up somewhere in <a href="http://www.themorningnews.org/article/paris-and-the-data-mind">Paris and the data mind</a>. Tugging at strange corners of our hearts. All starting with a simple number, on a <a href="http://www.amazon.com/gp/product/B005PUONKS/ref=as_li_ss_tl?ie=UTF8&amp;camp=1789&amp;creative=390957&amp;creativeASIN=B005PUONKS&amp;linkCode=as2&amp;tag=cramod-20">simple device</a>. </p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-09-16T23:15:02+00:00</published>
      <updated>2012-09-16T23:15:02+00:00</updated>

             <title>Publishing startups and the great fuzziness &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/publishing_startups" />
        <id>http://craigmod.com/satellite/publishing_startups</id>

        <content type="html" xml:base="http://craigmod.com/satellite/publishing_startups">
        <![CDATA[
          <a href="http://craigmod.com/satellite/publishing_startups/"><h3>Publishing startups and the great fuzziness</h3></a>
                    <img src="/images/satellite/startups-title.png" width="400" />
                    
          <p><em>Content Magazine</em> recently published an essay of mine, &ldquo;<a href="http://contentsmagazine.com/articles/our-new-shrines/">Our New Shrines</a>.&rdquo; Take a peek. It's a fun little thing &hellip; </p>

<p>Back? Weird, right? It's unusual. But the circumstances that led me to think about Facebook from a publisher's perspective have been unusual. So I thought I'd go into that a bit here ...</p>

<h3>TechFellows</h3>

<p>In February of this year I found out I was one of twenty individuals chosen as a <a href="http://techfellows.com/">TechFellow</a>. The TechFellow awards is a grant that you're asked to use to invest in startups. No strings attached.</p>

<p>I've always tried to live lean, and so outside of slowly building my small portfolio of publicly traded tech stocks,<sup id="fn-ref-80-1"><a href="#fn-80-1">1</a></sup> the idea of investing in early stage companies never crossed my mind; I simply never had latent capital sitting around to do such a thing.</p>

<p>Money dropping out of the sky — earmarked for investing — changes that pretty quickly. So, grant in hand, I decided to embrace this as an unexpected chance to learn to think more critically about startups from the outside. </p>

<h3>Books, of course</h3>

<p>Over the last decade I've engaged books and publishing on almost every level — from physical production and distribution, to working with printers and coaching authors, to international and domestic <span class="sc">(US)</span> sales. I've been involved as an author, a producer, a designer, a technologist, a cheerleader. I've organized events and helped build online communities. And all of that was just for &lsquo;classic&rsquo; books.</p>

<p>I've spent the last four years digging into the digital side of books and publishing. From <a href="/journal/ipad_and_books/">essays</a>, to Kickstarter <a href="http://www.kickstarter.com/projects/craigmod/art-space-tokyo-ipad-edition-hardcover-reprint">projects</a> <em>(to <a href="/journal/kickstartup/">essays</a> about Kickstarter projects)</em>, to <a href="http://flipboard.com">product design</a> on a startup team. I've tried to make a point of <em>doing</em>.</p>

<h3>Startups</h3>

<p>Naturally, when I began to look for startup investments, my focus was squarely on books and publishing <em>(and, tangentially, education)</em> related companies.</p>

<p>In the searches and meetings that have emerged over these past few months, I find myself drawing on all of the above — from a holistic theory of physical book production, to an empathy born from authorship, to the understanding of digital product design. </p>

<p>Startups — books and publishing startups inclusive — are mostly small groups of motivated people trying to give shape and form to ideas yet actualized. <sup id="fn-ref-80-2"><a href="#fn-80-2">2</a></sup></p>

<p><em>What if everyone in the world had access to every book in the world? <br />
How does that access change engagement? <br />
How does it change business models? <br />
What does it mean to read 'socially'? <br />
How do publishers and authors modify their behavior when distance to readers is zero?</em> </p>

<p>Lurking behind all of these questions are even more atomic questions about <em>tools</em>. It's necessary to question <em>all</em> of our tools. Almost every publishing focused writing, editing or design tool we use today was born in an age of unnetworked physicality. <em>Will Adobe have a place in the future of digital publishing?</em> Probably. <em>Will InDesign be the end-all-be-all of digital publishing?</em> Probably not. </p>

<p><em>How much of the old do we throw out to find the new?</em></p>

<p>All of the above are the sorts of questions publishing startups ask themselves. We don't know the full answers because the platforms upon which answers may lie have yet to be built. <em>And</em> it's hard to tell what <em>other</em> more interesting questions will emerge by tackling some of these more obvious questions. Sometimes seemingly boring questions lead to utterly fascinating ones. </p>

<h3>Fuzzy logic</h3>

<p>In my head, I call all of this <em>the great fuzziness</em>. </p>

<p>The process of assessing or mentoring a publishing startup feels like looking at a pool of abstraction through the lens of a decade of <em>doing</em>. <em>Book doing</em>, in my case. There's a balance you need to strike between total open-mindedness (because sometimes your experience blocks your ability to see) and framing the questions within the context of all of your experience (because sometimes your experiences helps skip unnecessarily circuitous routes). </p>

<p>The end goal in all of this being: help the great fuzziness coalesce into useful, sustainable, cogent <em>things</em>. Hopefully things that make books and publishing more pleasureful, engaging, sustainable, and, generally, socially better (which is, admittedly, a difficult thing to quantify). </p>

<p>Finally, one hopes books are <em>more</em> accessible — not less — because of technology. </p>

<h3>Mountain views</h3>

<p>The shift from an engaged <em>making</em> and <em>doing</em> into a more meditative, high-level space has been — so far — a deeply fun and satisfying adventure. Thinking about startups from a macro-level is, unsurprisingly, unlike working on a single product. It's given me an entirely <em>different kind of</em> empathy for companies raising money and investors contributing money. And I count anything that increases empathy as something valuable.</p>

<p>So it is I came to write, &ldquo;<a href="http://contentsmagazine.com/articles/our-new-shrines/">Our New Shrines</a>.&rdquo; Already — even from just a few months of conversations around this domain — I find myself questioning the <em>how</em> and <em>why</em> we publish as we do, as we have. A year ago I wouldn't have pegged Facebook as a viable platform to start a publishing enterprise. Now, I recognize there's a subset of content creators that are crazy <em>not</em> to start with Facebook. </p>

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-80-1">I was a stock market geek back when I was 15. I used to give myself budgets and track fantasy investments. Let's just say I was a weird kid. The end result is that I've cultivated the habit of buying small chunks of stock of companies I love, incrementally, over the past decade and a half. <a href="#fn-ref-80-1">&#8617;</a></li>
	<li id="fn-80-2">For more lengthy thoughts on what a startup is, exactly, see: Steve Blank's <a href="http://steveblank.com/2010/01/25/whats-a-startup-first-principles/">"What's a Startup?"</a> or Paul Graham's <a href="http://www.paulgraham.com/hubs.html">"Why Startup Hubs Work"</a> <a href="#fn-ref-80-2">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-09-13T18:47:32+00:00</published>
      <updated>2012-09-13T18:47:32+00:00</updated>

             <title>Twitter for minimalists &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/twitter_for_minimalists" />
        <id>http://craigmod.com/satellite/twitter_for_minimalists</id>

        <content type="html" xml:base="http://craigmod.com/satellite/twitter_for_minimalists">
        <![CDATA[
          <a href="http://craigmod.com/satellite/twitter_for_minimalists/"><h3>Twitter for minimalists</h3></a>
                    <img src="/images/satellite/twitter_for_minimalists-title1.jpg" width="400" />
                    
          <p>I love Twitter.app <em>(Tweetie for Mac)</em>. With the exception of a few posts from my phone, I'd bet 95% of all of my interactions with Twitter over the past few years have been through that application. It's fast. Supports multiple accounts effortlessly. And is, perhaps most importantly, streamlined and clean. </p>

<p>Suffice to say: I grew to love Twitter <em>because</em> of Tweetie, somewhat in spite of twitter.com. </p>

<p>Try as I might, I don't enjoy using twitter.com. There are parts of it I adore, but to speak in generalities, it's too busy. Too complex. Too far away. Twitter for me is useful only when it's close and quick. So when Twitter.app's death-knell was rung recently,<sup id="fn-ref-83-1"><a href="#fn-83-1">1</a></sup>  I began to try and figure out how to love twitter.com.</p>

<h3>Fluid</h3>

<p>For years, my go-to solution for daily-use web applications has been <a href="http://fluidapp.com">Fluid</a>. I have Fluid instances of gmail, Google Calendar, <a href="http://workflowy.com">Workflowy</a> and a host of other web-only applications. Generally, it works really well. The webapps load quickly via Spotlight like any other application, and you can quickly <code>CMD-TAB</code> into them without hunting through browser tabs. </p>

<p>Of course you can dump twitter.com into a Fluid instance but it feels pretty kludgy. Twitter buddy <a href="http://twitter.com/maxfenton">Max Fenton</a> whipped together a set of simple CSS rules removing a lot of the kludge. We went back and forth a couple times and the end result is pleasing. Twitter.com in a Fluid instance, with this set of user styles applied is actually usable. And I dare say it's almost worthy of replacing Twitter.app, were we forced to abandon it. </p>

<p>Here's the gist of the CSS: </p>

<script src="https://gist.github.com/cmod/3716608.js"></script>

<p>To use it: </p>

<ul>
<li>download Fluid</li>
<li>make a twitter.com instance</li>
<li>go to <code>window &gt; user styles</code></li>
<li>add a new style, pattern: <code>*twitter.com*</code></li>
<li>paste in the <code>CSS</code> from above</li>
</ul>

<h3>Icon</h3>

<p>To give your Fluid instance an 'official' Twitter icon, simply do the following:</p>

<ul>
<li>grab Twitter's <a href="https://twitter.com/images/resources/twitter-bird-light-bgs.png">logo</a></li>
<li>open it in Preview</li>
<li><code>CMD-A</code> to select all, <code>CMD-C</code> to copy it</li>
<li>highlight your Twitter instance in Finder</li>
<li><code>CMD-I</code> to see the application's info panel</li>
<li>click the top-left icon in the info panel, <code>CMD-V</code> to paste the logo</li>
</ul>

<h3>Issues</h3>

<p>Unfortunately, the biggest failure of this solution is that multiple accounts are still woefully difficult to handle; the sign-out/sign-in dance is the only solution. But as Twitter moves to further consolidate their experience to optimize around revenue maximization, twitter.com will be the only guaranteed way to get access to the service's latest features. </p>

<p>The biggest benefit of minimal twitter.com in a Fluid instance over Twitter.app is that you get the updated and far-superior @connect tab showing all interactions, not just mentions. Twitter's @connect work has been just fantastic. I hope they continue to polish and optimize the data flowing into that space. </p>

<h3>Fork</h3>

<p>This is hardly a perfect solution, but for those of us Twitter.app lovers wondering what we'll have to use next,<sup id="fn-ref-83-2"><a href="#fn-83-2">2</a></sup> this simple hack might be a bridge worth testing. </p>

<p>And, if you don't like the styling, <a href="https://gist.github.com/3716608">fork it</a> and make your own! </p>

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-83-1"><a href="http://daringfireball.net/linked/2012/09/08/mg-twitter-mac">Twitter Reportedly Discontinuing Development of Its Mac Client</a> <a href="#fn-ref-83-1">&#8617;</a></li>
	<li id="fn-83-2">Tweetbot's new client might work for some people — but I suspect its days are numbered at best. Jumping one sinking ship to another slightly less sinking ship isn't a very attractive option. <a href="#fn-ref-83-2">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-08-21T07:11:57+00:00</published>
      <updated>2012-08-21T07:11:57+00:00</updated>

             <title>Platforming Books &#45; Craig Mod &#45; Journal</title>
        
        <link href="http://craigmod.com/journal/platforming_books" />
        <id>http://craigmod.com/journal/platforming_books</id>

        <content type="html" xml:base="http://craigmod.com/journal/platforming_books">
        <![CDATA[
          <a href="http://craigmod.com/journal/platforming_books/"><h3>Platforming Books</h3>
          <img src="http://craigmod.com/" />
          </a>
          <p>In the last two years a simple, strong truth has emerged: The future of books is built upon networked platforms, not islands.</p>

<p>An essay about what a contemporary digital book looks like — scattered and disjointed, spread across multiple platforms in various states of open and closed. </p>
        ]]>
        </content>

          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-05-29T09:00:36+00:00</published>
      <updated>2012-05-29T09:00:36+00:00</updated>

             <title>Ahab! &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/ahab" />
        <id>http://craigmod.com/satellite/ahab</id>

        <content type="html" xml:base="http://craigmod.com/satellite/ahab">
        <![CDATA[
          <a href="http://craigmod.com/satellite/ahab/"><h3>Ahab!</h3></a>
                    <img src="/images/satellite/ahab-title.jpg" width="400" />
                    
          <p><h4>So you wanna publish a Kindle book on Amazon?</h4></p>

<p>Ahab! is a simple template for producing Kindle specific .mobi files.<br /> Available on <a href="https://github.com/cmod/ahab">github.com/cmod/ahab/</a>.</p>

<h3>Ahab!?</h3>

<p>I spent a few weeks reformatting and publishing four of my longer essays on the Kindle Direct Publishing platform. The process was a hodge-podge of snippets and trial and error. I wish I had this template from the start. Now I do. So I hope it helps you. <em>(Disclaimer: I am by no means a .mobi wizard, which is why it's on github — hack away and please suggest changes!)</em> </p>

<p>This is all — clearly — a bit geeky. It's for those of us who like to hand-code websites. Who want to know what's going on under the hood. Who are obsessive about CSS class names and indent technique and derive pleasure from knowing that the innards of the machines they produce are as beautiful and effecient as possible. <sup id="fn-ref-79-1"><a href="#fn-79-1">1</a></sup> </p>

<h3>.Mobi?</h3>

<p>Mobi is Kindle's ebook format. It's sort of like <a href="http://en.wikipedia.org/wiki/EPUB">epub's</a> step-brother. With a properly formatted <code>.mobi</code> file you can publish on the <a href="http://kdp.amazon.com">Kindle Direct Publishing</a> platform. </p>

<h3>Why .mobi?</h3>

<p><a href="http://en.wikipedia.org/wiki/Pareto_principle">Pareto pricinple</a> (80/20 rule). I want to leverage existing marketplaces for digital publishing, and Amazon covers 80%+ of the market I'm interested in reaching. iBooks just doesn't have the audience, nor is the platform presently inviting (IMO) from a systems and ubiquity perspective. Kindle hits iPad, iPhone, Android, web, desktop ... EVERYWHERE. And it does seamless syncing. I like all that. <em>Readers</em> like all that. </p>

<p>There's other engaged and energized communities emerging around products like <a href="http://readmill.com/">Readmill</a> but I don't want to have to deal with selling stuff on my own. And I do want to sell stuff. That's part of the experiment. And, I think it behooves anyone interested in the future of publishing to know the biggest guy in the room really well, even if you don't like them. (I've got nothing against Amazon but it seems like a lot of other folks do.) </p>

<h3>This template</h3>

<p>This template is meant to get you from <em>thinking</em> about publishing a piece of text you have to <em>actually publishing</em> it on Kindle Direct Publishing. If you have a long-form blog post composed mainly of text, I suspect you could convert it to a proper <code>.mobi</code> file using this template in fifteen minutes. Obviously, more complex texts (and cover production, etc) take more time. </p>

<p>So, this template is mainly about minimizing friction.</p>

<h3>Resources</h3>

<ul>
<li>Kindle Format 8 <a href="http://www.amazon.com/gp/feature.html?docId=1000729511">Guidelines</a> are a good place to start</li>
<li><a href="http://www.amazon.com/gp/feature.html?ie=UTF8&docId=1000765261">Kindle Previewer</a></li>
<li><a href="http://www.amazon.com/gp/feature.html?ie=UTF8&docId=1000765211">Kindlegen</a></li>
</ul>

<p>Yes — you're correct! You have to use a <code>COMMAND LINE PROGRAM</code> to make <code>.mobi</code> files for Kindle Previewer to preview them. </p>

<p>At the risk of this file turning into a horribly complex tutorial, after you
install Kindlegen, open your <code>Terminal</code> program (assuming OS X), type 
"<code>kindlegen content.opf</code>" from inside the <code>ahab</code> directory and Kindle Previewer should be able to open the <code>content.mobi</code> file it spits out. </p>

<p>Kindle Previewer is pretty kludgy, but it gets the job done. It saves you from 
trying to send <code>.mobi</code> files to seven different devices. And speeds up development / 
testing / iteration time. </p>

<p>You will, at some point, want to send something to a bunch of Kindles. This 
utility is useful for that:</p>

<ul>
<li><a href="http://www.amazon.com/gp/feature.html/?docId=1000778781">Send to Kindle</a></o>
</ul>

<h3>Covers</h3>

<p>So Amazon revised their cover guidelines in early 2012. Here's the latest:</p>

<ul>
<li><a href="https://kdp.amazon.com/self-publishing/help?topicId=A2J0TRG6OPX0VM">Creating a catalog/cover image</a></li>
</ul>

<p>Here are the base requirements:</p>

<blockquote>
<p>Requirements for the size of your cover art: </p>
<ul>
<li>Minimum of 1000 pixels on the longest side </li>
<li>Ideal height/width ratio of 1.6 </li>
</ul>

<p>For better quality, we recommend that images be 2500 pixels on the longest side. </p>
</blockquote>

<p>The 1.6 ratio bit is weird. It's the dimensions for the Kindle Fire. It is doubly awkward because hardware eink Kindles have a screen ratio closer to 1.3.</p>

<p>Amazon currently doesn't offer the ability to include multiple, device specific covers.
I feel most comfortable designing for hardware Kindles since I'm still not convinced anyone actually uses/reads on Kindle Fires. <sup id="fn-ref-79-2"><a href="#fn-79-2">2</a></sup> </p>

<p>For some reason, <code>.png</code> is not allowed for cover images. So make sure you stick with 
<code>.jpg</code> or <code>.tiff</code>. </p>

<p>Though <code>.pngs</code> are allowed elsewhere in a <code>.mobi</code> file. </p>

<h3>CSS</h3>

<p>Kindle Format 8 supports CSS media queries. It seems a little bit out of the
scope of a baseline template, but if you're interested, <a href="http://www.pigsgourdsandwikis.com/2012/01/media-queries-for-formatting-poetry-on.html">Liz Castro</a> explains all. </p>

<p>@font-face rules only work on Kindle Fire.</p>

<p>Actually, a lot of css rules only work on Fire. Floats, for example. The simpler
you keep your CSS, the saner you'll be. </p>

<p>Here's the full list of KF8 HTML and CSS support:</p>

<ul><li><a href="http://www.amazon.com/gp/feature.html?ie=UTF8&docId=1000729901">List of support HTML and CSS tags</a></li></ul>

<h3>What are these other files?</h3>

<p><code>toc.ncx</code> and <code>content.opf</code> are the two slightly alien files of this collection.</p>

<p><p>OPF means "Open Page Format". From <a href="http://en.wikipedia.org/wiki/EPUB#Open_Packaging_Format_2.0.1">Wikipedia</a>:</p>

<blockquote>
<p>The OPF file, traditionally named content.opf houses the EPUB book's 
metadata, file manifest, and linear reading order. This file has a 
root element package and four child elements: metadata, manifest, 
spine, and guide. All of these except guide are required. Furthermore, 
the package node must have the unique-identifier attribute. The .opf 
file's mimetype is application/oebps-package+xml.</p>
</blockquote>

<p>The .ncx file is explained thusly: </p>

<blockquote>
<p>The NCX file (Navigation Control file for XML), traditionally named toc.ncx, 
contains the hierarchical table of contents for the EPUB file. The specification 
for NCX was developed for Digital Talking Book (DTB), is maintained by the DAISY 
Consortium, and is not a part of the EPUB specification. The NCX file has a 
mimetype of application/x-dtbncx+xml.</p>
</blockquote>

<p>Exciting stuff! *zzzzzz*</p>

<p>I've done my best to obviate thinking too much about those files.</p>

<h3>Publish!</h3>

<p>So you have your cover. You have your properly formated <code>.mobi</code>. You've tested it
in Kindle Previewer and it looks pretty good on all devices. Now, how do you
publish?</p>

<p>You can just mail the <code>.mobi</code> file to friends, put it up on a server, upload it 
to a forum — distribute any way — and any Kindle will be able to open the file. </p>

<p>But if you want to "publish" it on Amazon — set prices and get it properly listed — 
then <a href="http://kdp.amazon.com">Kindle Direct Publishing</a> is what you want. It should
be pretty self explainatory. </p>

<h3>Extend</h3>

<p>This is by no means exhaustive. It's meant to give anyone interested in <code>.mobi</code> a
little boost. I've tried to strip away all the unnecessary gunk. What's remaining
should be relatively self explanatory. </p>

<h3>Similar projects</h3>

<ul>
<li><a href="http://javierarce.github.com/epub-boilerplate/">epub boilerplate</a></li>
</ul>

<h3>Contact</h3>

<p>If you do end up publishing something with this, please let me know. 
Post about it in the github project or shoot <a href="mailto:me@craigmod.com">me@craigmod.com</a> an email.</p>

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-79-1">Apparently, rumor has it, you can just upload a Word document and Kindle Direct Publishing will magically make it into a .mobi file. I haven't dared try that. I can't imagine what chaos might emerge. So, this sort of template is for those of us who are grossed out — who feel it in their gut — by the idea of auto-converting word documents. Heck, it's for those of us who are grossed out by Word documents in general.  <a href="#fn-ref-79-1">&#8617;</a></li></p>

<p>	<li id="fn-79-2">I'm sure there's tons of happy Kindle Fire owners, but — like the original Kindle — Amazon usually ships a very rough, nearly beta version one. So I still consider this first Fire iteration a public beta. I'm sure it's going to get a lot better. The current hardware eink Kindles are dreams compared to the first retro-inspired Kindle. (Which is pretty awesome in it's own special way, but not nearly as portable, simple as the current crop.) <a href="#fn-ref-79-2">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-05-23T20:39:18+00:00</published>
      <updated>2012-05-23T20:39:18+00:00</updated>

             <title>Hack the Cover &#45; Craig Mod &#45; Journal</title>
        
        <link href="http://craigmod.com/journal/hack_the_cover" />
        <id>http://craigmod.com/journal/hack_the_cover</id>

        <content type="html" xml:base="http://craigmod.com/journal/hack_the_cover">
        <![CDATA[
          <a href="http://craigmod.com/journal/hack_the_cover/"><h3>Hack the Cover</h3>
          <img src="http://craigmod.com//images/journal/hack_the_cover/index_image_3-300x300.jpg" />
          </a>
          <p>If digital covers as we know them are so 'dead,' why do we hold them so gingerly? Treat them like print covers? We can't hurt them. They're dead. So let's start hacking. Pull them apart, cut them into bits and see what we come up with.</p>
        ]]>
        </content>

          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-04-25T03:38:43+00:00</published>
      <updated>2012-04-25T03:38:43+00:00</updated>

             <title>A pointable we [3/3] &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/pointable_03" />
        <id>http://craigmod.com/satellite/pointable_03</id>

        <content type="html" xml:base="http://craigmod.com/satellite/pointable_03">
        <![CDATA[
          <a href="http://craigmod.com/satellite/pointable_03/"><h3>A pointable we [3/3]</h3></a>
                    <img src="/images/satellite/pointable-title.png" width="400" />
                    
          <p><p></p>

<h5>Other entries in this series:</h5>

<ul>
<li><a href="/satellite/pointable_01/">A pointable we [1/3]</a></li>
<li><a href="/satellite/pointable_02/">A pointable we [2/3]</a></li>
</ul>

<p></p></p>

<hr />

<h3>Land Locked</h3>

<p><em>Monkey Business</em> is here in my hands, printed. Solid. A brick. <a href="/journal/digital_physical/">I understand it.</a> It's real. <em>But</em> from our corpus perspective, it's deflated. It doesn't have legs. The author's words start and end on the page. I can't point. It's not "close" like digital text. It isn't adjacent to anything. All I can do is create a simulacrum here, on my website. And legally I'm only allowed to simulacrumize a few things. </p>

<p>So this — <em>those blockquotes floating <a href="/satellite/pointable_01/">over in part one</a></em> — is me adding Murakami's conversation to the corpus. Our corpus. Putting it in a public space. Making it searchable. Pointable. Taking it out of my underlined, dog-eared pages, dumping it into Simple Note / Notational Velocity,<sup id="fn-ref-76-1"><a href="#fn-76-1">1</a></sup> and embedding a slice of that here on my public home. </p>

<h3>Platforming</h3>

<p>Which brings us to The Really Controversial Question a lot of print focused publishers grapple with: <em>how much should be put online for free? And when?</em> But I don't think those are the right questions. It's not about content being free or not, it's about content <em>existing</em> or not. Can I point? No? Then it's kinda not <em>really</em> there. At least not in the way we now expect. Undeniably, it's certainly not doing the work it could be doing.</p>

<p>All this ties back into the importance of platforms in digital publishing. The web, of course, is the largest, most open, device agnostic, and most pervasive (and thereby a great place to start). But this doesn't preclude others from emerging.<sup id="fn-ref-76-2"><a href="#fn-76-2">2</a></sup> </p>

<p>This lack of platforminess is what makes many iPad magazine apps impotent. They end up in no better a position than a printed magazine. There are no routes by which you can directly get to their content. You can't point <em>in</em>. You're forced to go through the "front door" to get anywhere. And it's a door usually weighing several hundred megabytes and infuriatingly difficult to unlock. </p>

<p>The reality is — because of the way in which we share content — we almost never even <em>see</em> the "front door" anymore. (Which indicates that the long-term value of an 'issue' drops precipitously with time.) If you find a piece of great content inside one of these apps, at most you can say: <em>Hey! There's something interesting in there! Just download the app, swipe right ten times, up three, then tap to remove the text, rotate to landscape mode and I swear there's a great article in there! You gotta trust me.</em> Which, of course, almost no one follows all the way to the interesting thing. </p>

<p>In a best case scenario the article you want to point at also exists on a website somewhere. But there's often no obvious connection between the closed (unpointable) article in the app, and the open (pointable) article on the web.</p>

<h3>Close Your Loops!</h3>

<p>Which is to say: <em>the loops are left open.</em> The reading-enjoying-sharing-engaging-reading loop can't be closed when your platform doesn't have universally, publicly accessible points.<sup id="fn-ref-76-3"><a href="#fn-76-3">3</a></sup> And right now, those points — to be truly universally accessible and pointable — need to be web based. It's our lowest common denominator of pointability.</p>

<p>So that feeling: <em>if a text isn't online, then it doesn't exist.</em> This needs a little amendment: <em>If a text isn't online and publicly pointable, then it doesn't exist.</em></p> 

<p>Commercially, it gets sticky. But Amazon and their Kindle-as-platform solves a bit of that.<sup id="fn-ref-76-4"><a href="#fn-76-4">4</a></sup> The New York Time's pay-fence is another alternative.</p>

<p>Just as I was about to publish this satellite entry, apropos this discussion, Harvard announced their massive meta-data injection into the corpus:</p>

<blockquote><p>Harvard is making public the information on more than 12 million books, videos, audio recordings, images, manuscripts, maps, and more things inside its 73 libraries ... “This is Big Data for books,” said David Weinberger, co-director of Harvard’s Library Lab. “There might be 100 different attributes for a single object.” At a one-day test run with 15 hackers working with information on 600,000 items, he said, people created things like visual timelines of when ideas became broadly published, maps showing locations of different items, and a “virtual stack” of related volumes garnered from various locations.<sup id="fn-ref-76-5"><a href="#fn-76-5">5</a></sup></p></blockquote>

<p>It seemed remiss of me not to point at that.</p>

<p>All I know is the more I read digitally, the more this feeling — the strange joy of adding to the corpus<sup id="fn-ref-76-6"><a href="#fn-76-6">6</a></sup> and seeing where it takes us — grows inside me, and I can't be the only one to feel this. Adding to the corpus — making things pointable — has become habitual, and aspects of it are becoming more and more passive. These habits and expectations aren't going anywhere.</p> 

<p>As a publisher your text is either in the corpus or it's not. And so there is no better time for great, print-locked publications like <em>Monkey Business</em> or countless other app-locked publications to show others what happens when their texts "exist," when they're made open and pointable.</p>

<p>
<h5>Other entries in this series:</h5>
<ul>
<li><a href="/satellite/pointable_01/">A pointable we [1/3]</a></li>
<li><a href="/satellite/pointable_02/">A pointable we [2/3]</a></li>
</ul>
</p>

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-76-1">Simplenote/Notational Velocity has become my <em>de facto</em> external brain. <em>Everything</em> gets dumped into it. If we're having dinner together and I take out my iPhone, I'm not checking my mail, I'm dumping part of our conversation into my external corpus to reference later. <a href="#fn-ref-76-1">&#8617;</a></li>
	<li id="fn-76-2">Although it seems like it would be very difficult to build a platform that doesn't touch the open web in one way or another. This is perhaps <em>the</em> fundamental difference between Kindle and iBooks — Kindle has thus far achieved much more platforminess than iBooks. That achievement has come largely due to (among many other things) Amazon's embracing of the open web as a public anchor for book highlights and notes. When you "share" a highlight, that highlight receives its own landing page on the web. Combine this with web based Kindle reading software and you'll begin to see Amazon's holistic understanding of balancing a closed, 'sale' (which can be an Amazon Prime checkout) oriented platform within the context of social media sharing. With links to purchase the books on all the landing pages, they fully understand how to close their loops. <a href="#fn-ref-76-2">&#8617;</a></li>
	<li id="fn-76-3">When's the last time you saw someone link to or talk about <em>The Daily</em>? <a href="#fn-ref-76-3">&#8617;</a></li>
	<li id="fn-76-4">The books live within the walled, paid Kindle garden but pieces can sneak out through public links to notes / highlights / samples — Amazon doesn't make people go in through the front door. <a href="#fn-ref-76-4">&#8617;</a></li>
	<li id="fn-76-5"><a href="http://bits.blogs.nytimes.com/2012/04/24/harvard-releases-big-data-for-books/?pagewanted=all">Harvard Released Big Data for Books</a>, The New York Times, April 24, 2012 <a href="#fn-ref-76-5">&#8617;</a></li>
	<li id="fn-76-6">And as I mention in <a href="/satellite/pointable_01/">part one</a>, this also goes for location checkins, photos, hangouts and any other physical action with a digital hook upon which it can be hung. I've gone from abhorring checkins to feeling like they ground activities. Regardless — it's now our duty to feed the anonymous algorithms invariably watching over all of this. You don't want them to get hungry. You wouldn't like them when they're hungry. <a href="#fn-ref-76-6">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-04-23T18:25:15+00:00</published>
      <updated>2012-04-23T18:25:15+00:00</updated>

             <title>A pointable we [2/3] &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/pointable_02" />
        <id>http://craigmod.com/satellite/pointable_02</id>

        <content type="html" xml:base="http://craigmod.com/satellite/pointable_02">
        <![CDATA[
          <a href="http://craigmod.com/satellite/pointable_02/"><h3>A pointable we [2/3]</h3></a>
                    <img src="/images/satellite/pointable-title.png" width="400" />
                    
          <p><p></p>

<h5>Other entries in this series:</h5>

<ul>
<li><a href="/satellite/pointable_01/">A pointable we [1/3]</a></li>
<li><a href="/satellite/pointable_03/">A pointable we [3/3]</a></li>
</ul>

<p></p></p>

<hr />

<h3>Links</h3>

<p>We've built up a habit of pointing — effortlessly — through links, tweets, reblogs, and likes. And this is <em>really</em> efficient. Super easy. We all do it all the time. Pointing is embedded all over our digital surfaces. It's an incredible vector for spreading ideas and pushing or pulling attention towards or away from things. </p> 

<p>Most importantly though, is that digital pointing is nearly frictionless. Not only is the energy between seeing a pointer and clicking it almost zero, but so too is the energy required to create that pointer.<sup id="fn-ref-75-1"><a href="#fn-75-1">1</a></sup> The less friction, the easier it is to form a habit.</p>

<h3>Public Highlights</h3>

<p>Connected to this, and more explicitly to do with reading, is the now exhaustively discussed idea of the digital public commonplace book.<sup id="fn-ref-75-2"><a href="#fn-75-2">2</a></sup></p> 

<p><a href="http://findings.com/" target="_blank">Findings</a> provides tools for commonplace capturing across all of the web. Amazon has created an actual <a href="http://kindle.amazon.com" target="_blank">commonplace-book-social-network</a> (although still a minimum viable product). They both give <em>public addresses</em> to our little nut collections.<sup id="fn-ref-75-3"><a href="#fn-75-3">3</a></sup> </p>

<p>Traditional links allow us to point <em>at</em> whole documents or collections of documents. 
<br />These services let us point <em>into</em> documents.</p>

<p>Our notes and highlights get special powers as data in the public corpus. Search, of course. And increased accessibility. But also, they're <a href="http://kindle.amazon.com/most_popular/books_by_popular_highlights_recently" target="_blank">votes</a>. You're voting on interestingness within a particular text. There's a feeling that this is valuable data.<sup id="fn-ref-75-4"><a href="#fn-75-4">4</a></sup></p>  

<p>Because of this, as you're highlighting your book, there's an unmistakable and growing sense of social <em>usefulness</em> to the act. The highlight is doing some work <em>(or will be doing some work)</em>, not just sitting there to <em>(hopefully)</em> help you remember something later.<sup id="fn-ref-75-5"><a href="#fn-75-5">5</a></sup></p>

<p>In a recent interview, Clive Thompson, writer for <em>Wired</em>, mentions one tangible digital→physical example of leveraging his corpus of digital annotations:</p>

<blockquote>
<p>I annotate aggressively. If I’m reading a piece of really long fiction, I often find that there are these fabulous things I want to remember. I want to take notes on it, so I highlight it, and if I have a thought about it, I’ll type it out quickly. Then I dump all these clippings into a format that I can look at later. In the case of War and Peace, I actually had 16,000 words worth of notes and clippings at the end of it. So I printed it out as a print-on-demand book. In short, I have a physical copy of all of my favorite parts of War and Peace that I can flip through, with my notes, but I don’t actually own a physical copy of War and Peace. <sup id="fn-ref-75-6"><a href="#fn-75-6">6</a></sup></p>
</blockquote>

<p>The generalized takeaway is that we're evolving a set of habits and language (once active and now increasingly ambient and passive)<sup id="fn-ref-75-7"><a href="#fn-75-7">7</a></sup> around capturing "real world" stuff — not just book or reading related — in digital space.</p> 

<p>Some core differences between a captured or uncaptured — networked (in the context of open platforms) or unnetworked — action is:</p> 

<ul>
<li>A networked action is sticky <em>(Google never forgets)</em></li> 
<li>Being networked undoes the Galapagos nature of an unnetworked something <em>(everyone can see and search)</em></li> 
<li>The action is codified and aligned with similar data <em>(in a database)</em></li> 
</ul>

<p>The culmination of these qualities is a networked action ("I read", "I visited", "I saw", etc) on an open platform is persistent in a way totally different from its physical or closed or unnetworked counterpart. Each time we add an action to our public corpus, we perform a little act of faith ...</p> 

<p>In part 3, we'll tie this back into <em>Monkey Business</em> and publishing platforms.</p>

<p>
<h5>Other entries in this series:</h5>
<ul>
<li><a href="/satellite/pointable_01/">A pointable we [1/3]</a></li>
<li><a href="/satellite/pointable_03/">A pointable we [3/3]</a></li>
</ul>
</p>

<hr />

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-75-1">Google constructed a business and illuminated a zeitgeist around our excessive pointing. We've entered an age of terminal information velocity (baring perfect search) — where the discovery > production > sharing loops are the tightest they've ever been in human history. If you want perspective on how these sharing loops have evolved — how information transmission and consumption has sped from a trickle to the current torrential fire hose of today — check out James Gelik's <a href="http://www.amazon.com/gp/product/0375423729/ref=as_li_ss_tl?ie=UTF8&amp;tag=cramod-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0375423729"><em>The Information</em></a> (or at least the first half of it). And to get a sense of how that firehose is affecting the very topology of our minds, push on through Nicholas Carr's <a href="http://www.amazon.com/gp/product/0393072223/ref=as_li_ss_tl?ie=UTF8&amp;tag=cramod-20&amp;linkCode=as2&amp;camp=1789&amp;creative=390957&amp;creativeASIN=0393072223"><em>The Shallows</em></a>. <a href="#fn-ref-75-1">&#8617;</a></li>
	<li id="fn-75-2"><a href="http://en.wikipedia.org/wiki/Commonplace_book">Wikipedia on Commonplace books</a> <a href="#fn-ref-75-2">&#8617;</a></li>
	<li id="fn-75-3">Here's my Kindle collection: <a href="http://kindle.amazon.com/profile/Craig-Mod/52461">kindle.amazon.com/profile/Craig-Mod/</a>, and here's my Findings collection: <a href="http://findings.com/craigmod">findings.com/craigmod</a> <a href="#fn-ref-75-3">&#8617;</a></li>
	<li id="fn-75-4">This applies not only to text but with all the data we're adding to the corpus. The checkins, food photos, tweets — we're assembling a granular, meta-data filled set of human mundanity (and by extension, extraordinarity). <a href="#fn-ref-75-4">&#8617;</a></li>
	<li id="fn-75-5">What, precisely, that "work" is is still to be seen. Like much of the varied data we add to the public corpus, the value of this information has yet to be fully realized. Our collective acts of creation have embedded within them a certain faith in a future usefulness. Perhaps it's naieve to believe our checkins at Starbucks will have any future value to us (... they most certainly will and already do have value to advertisers). But consciously or not, there's over a billion of us wholeheartedly subscribed to the church of data capture.  <a href="#fn-ref-75-5">&#8617;</a></li>
	<li id="fn-75-6"><a href="http://blog.findings.com/post/20117251507/how-we-will-read-clive-thompson">How We Will Read: Clive Thompson</a> <a href="#fn-ref-75-6">&#8617;</a></li>
	<li id="fn-75-7"><strong>Active:</strong> linking, liking, checking in; <strong>Passive:</strong> auto-checkins, who I passed nearby during the day (<a href="http://highlig.ht/about.html">Highlight</a>), % of book read, number of pages read, amount of time spent on an article, and so on. <a href="#fn-ref-75-7">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-04-22T22:16:30+00:00</published>
      <updated>2012-04-22T22:16:30+00:00</updated>

             <title>A pointable we [1/3] &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/pointable_01" />
        <id>http://craigmod.com/satellite/pointable_01</id>

        <content type="html" xml:base="http://craigmod.com/satellite/pointable_01">
        <![CDATA[
          <a href="http://craigmod.com/satellite/pointable_01/"><h3>A pointable we [1/3]</h3></a>
                    <img src="/images/satellite/pointable-title.png" width="400" />
                    
          <p><p></p>

<h5>Other entries in this series:</h5>

<ul>
<li><a href="/satellite/pointable_02/">A pointable we [2/3]</a></li>
<li><a href="/satellite/pointable_03/">A pointable we [3/3]</a></li>
</ul>

<p></p></p>

<hr />

<p>
<em>
Where we've been.<br /> 
What we're thinking about.<br /> 
What we're reading.</em></p> 

<p>We're networking, digitizing, and indexing all of this. Building a corpus. And the growing bizarro emotional quandary is: <em>if an act — a checkin, a highlight, a note, a meal — isn't in the corpus, then is it real?</em> If a tree falls in the forest … </p>

<h3>Adjacency and Publishing</h3>

<p>I'm sitting here in a little cafe reading the first issue of <em>Monkey Business</em>.<sup id="fn-ref-74-1"><a href="#fn-74-1">1</a></sup> Edited by Motoyuki Shibata and Ted Goossen, and published by A Public Space,<sup id="fn-ref-74-2"><a href="#fn-74-2">2</a></sup> <em>Monkey Business</em> "is a newly founded journal of new writing from Japan and abroad with a few not-so-new works strategically slipped in."</p> 

<p>In this inaugural English issue there's a conversation between Hideko Furukawa and Murakami Haruki. It's long. It's intimate. In fact, I can't ever remember reading such a raw conversation with Murakami in English. Here's some of my favorite passages.</p>

<p>On <a href="http://www.amazon.com/gp/product/0375713271/ref=as_li_ss_tl?ie=UTF8&tag=cramod-20&linkCode=as2&camp=1789&creative=390957&creativeASIN=0375713271"><em>after the quake</em></a> and Murakami's systematic easing into third-person narrative:</p>

<blockquote><p>Before I began I decided I'd write one story every one or two weeks, that each would feature characters that would be named, that I would write in the third person, and that the earthquake would link them all together.</p> </blockquote>

<p>On discipline and pace:</p>

<blockquote><p>The lady who used to work at the club was amazed by how hard I worked — no other writer could match me, she said. For me, though, it was par for the course.</p> </blockquote>

<p>And then Furukawa on that pace:</p>

<blockquote><p>I can see the athlete in you at work. It's as if the act of running and writing had merged together.</p> </blockquote>

<p>When Murakami finished work on his book, <em>Sydney!</em> about the Sydney Olympics, he had a writing epiphany: </p>

<blockquote><p>I came away from that process finally convinced I really knew how to write: in concrete terms, I no longer had to stop and question whether I was capable of handling a particular scene — I could go on and write whatever came into my head, even if I had no familiarity with the subject matter.</p> </blockquote>

<p>And the interview goes on and on. They discuss the alternate Muakami-esque un-real reality of post-9/11 America, and Murakami's sense of looming mortality:</p>

<blockquote><p>… at sixty, I pretty much know how many [novels] are left. All I have to do is count backwards.</p> </blockquote>

<p>And on and on and on some more. It's a wonderful text that was part of a print publication released last year. And I want to point point <em>point</em> at it for you. But I can't. At least not in the way we've become accustomed — digitally; <em>into</em> the publication. And I realize how entitled this may sound — but not being able to point means it feels like the text is not really out <em>there</em>. Like it doesn't exist.</p>

<p>To not exist means in part to be offline. Which is why it's so easy to understand this by using a print publication as an example. But the offline metaphor also extends into the digital world.</p> 

<p>To not exist digitally means to be walled off.  Silo'd. Unpointable. It means a text feels flat or lifeless or limp. Unnetworked (even if it's on the network). It's means to not be part of that growing <em>corpus</em>.  Which, today, feels more damning than ever.</p>

<p>More in <a href="/satellite/pointable_02/">part [2/3]</a> ...</p>

<p>
<h5>Other entries in this series:</h5>
<ul>
<li><a href="/satellite/pointable_02/">A pointable we [2/3]</a></li>
<li><a href="/satellite/pointable_03/">A pointable we [3/3]</a></li>
</ul>
</p>

<hr />

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-74-1"><a href="http://www.apublicspace.org/pre-order_monkey_business.html">Monkey Business</a> <a href="#fn-ref-74-1">&#8617;</a></li>
	<li id="fn-74-2"><a href="http://www.apublicspace.org/">A Public Space</a> <a href="#fn-ref-74-2">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2012-03-29T04:55:40+00:00</published>
      <updated>2012-03-29T04:55:40+00:00</updated>

             <title>The Digital↔Physical &#45; Craig Mod &#45; Journal</title>
        
        <link href="http://craigmod.com/journal/digital_physical" />
        <id>http://craigmod.com/journal/digital_physical</id>

        <content type="html" xml:base="http://craigmod.com/journal/digital_physical">
        <![CDATA[
          <a href="http://craigmod.com/journal/digital_physical/"><h3>The Digital↔Physical</h3>
          <img src="http://craigmod.com//images/journal/digital_physical/index_image-300x300.jpg" />
          </a>
          <p>On Building Flipboard for iPhone and Finding the Edges of Our Digital Narratives.</p>
        ]]>
        </content>

          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2011-12-25T05:04:49+00:00</published>
      <updated>2011-12-25T05:04:49+00:00</updated>

             <title>The momentum of Steve Jobs &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/steve_jobs_momentum" />
        <id>http://craigmod.com/satellite/steve_jobs_momentum</id>

        <content type="html" xml:base="http://craigmod.com/satellite/steve_jobs_momentum">
        <![CDATA[
          <a href="http://craigmod.com/satellite/steve_jobs_momentum/"><h3>The momentum of Steve Jobs</h3></a>
                    <img src="/images/satellite/steve-title.png" width="400" />
                    
          <p><p style="font-size: 1.2em; margin-bottom: 20px;"><em>Note: I wrote this a few days after Steve’s death, but due to an intense work schedule, and being generally overwhelmed and wanting respectful distance from his death, I’ve finally now, as a cap to this long, winding year, properly edited and published this. </em></p></p>

<p><span style="text-transform: uppercase; font-size: .9em; letter-spacing: 1px;">The sound is always explosive.</span></p>

<p>Shortly after one a.m. each night, the last southbound Caltrain passes between the Palo Alto and California Ave stations. Sometimes it whistles, but more often than not, it simply rushes down the tracks. Its clacking cacophonous. A signal to finally end my day. </p>

<p>I’m usually in my room when the violent clacking floods our house, filling the otherwise silent night of Old Palo Alto. And each time that train passes, I find myself wondering if Steve, too, is still awake. If he also heard that train. </p>

<p>Through matters of coincidence, when I moved to California last year, I landed just two blocks from Steve Jobs. </p>

<p>Despite being so close, I never met the man. Occasionally I saw him walk through the neighborhood, or eat at local restaurants, but we never interacted. I always assumed that at some point there’d be a natural, professional introduction. There was no need to invade or disrupt his privacy in public. </p>

<p>And so this train was, in my mind, our one constant connection. Every night it would pass. And if he was awake, surely, he too could hear the clacking or whistling, the rush of energy down the tracks. </p>

<p>I found myself wondering what he thought as it passed. If he even noticed it anymore, having lived here for so many years. Regardless, this shared train sound — however tenuous and grasping might such a connection be — helped humanize for me a man who was often painted nothing of the sort. </p>

<p>As I’ve written previously, Silicon Valley is where the gods very much eat yogurt with mortals.<sup id="fn-ref-71-1"><a href="#fn-71-1">1</a></sup> And Steve was no exception. His house has no visible security, no gate. It is modest. Nestled in a very tony neighborhood. But not so tony as to exclude three enterprising rag-tag entrepreneurs from also living here. The blinds are almost always open (as most tend to be in Old Palo Alto). TVs flicker at night. Lights go on and off. There is no mystery. Humans live there, certainly. </p>

<p>Time and time again, I found myself biking past Steve’s house — simply by the nature of it being on my path home. And time and time again I found myself drawing tremendous inspiration from the hyper-reality of his presence. </p>

<p>I’ve always felt — the quicker you can kill a dream by making it real, the quicker you see bigger, more important dreams once blocked by the first. The same goes for celebrity: the deconstruction of celebrity removes excuses. With mystery, and thereby celebrity gone, so also goes the pedestal. Their achievements can be more easily assessed at human scale.</p>

<p>The hagiographic accounts after the passing of Steve this year understandably cast his accomplishments in an otherworldly light. But in my mind, he will be, as he became to me in this past year, that guy over there also eating brunch at Calafia. The neighbor in a comfortable neighborhood who happened to posses a beautiful, driven mind. Not a saint or a god but simply a someone who had a vision and executed, methodically and consistently and unrelentingly. </p>

<p>After his cancer diagnosis, I can’t help but wonder if the sound of that train took on a new meaning for Steve. The gravity of his work yet done — and now with so little time in which to do it — must have washed over him. A set of visions to be made real, for which he had only to build a clear, unwavering path before his passing. I wonder if he heard that train rushing, its steel and iron hurtling through the dead of night, and felt a kinship. Knew that that was what he had to be. Focused, moving forward as fast as he possibly could. On the edge of a certain chaos. Alone in his journey. Pulling those ideas forward. Crassly devoid of nostalgia. </p>

<p>Now, for the first time since moving here, I am certain he doesn’t hear it. </p>

<p>Steve may no longer be here, but that train is. And each night it passes I’ll remember how much he accomplished in so little time, carrying so much weight. I’ll remember how he chose to pursue ideas that inspired a man staring down death. A man who absolutely would not and did not give up. Driven by vision, exploding ever forward down his path. </p>

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-71-1"><a href="http://www.nytimes.com/roomfordebate/2011/08/03/can-new-york-rival-silicon-valley-for-start-ups/nurture-the-difference-between-new-york-and-silicon-valley?pagewanted=all">Nurture the Difference</a> — <em>New York Times</em>, August 2011 <a href="#fn-ref-71-1">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2011-09-06T05:02:28+00:00</published>
      <updated>2011-09-06T05:02:28+00:00</updated>

             <title>The shape of our future book &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/our_future_book" />
        <id>http://craigmod.com/satellite/our_future_book</id>

        <content type="html" xml:base="http://craigmod.com/satellite/our_future_book">
        <![CDATA[
          <a href="http://craigmod.com/satellite/our_future_book/"><h3>The shape of our future book</h3></a>
                    
          <p><blockquote><p>“... the more one was lost in unfamiliar quarters of distant cities, the more one understood the other cities he had crossed to arrive there.”
<br /><cite><strong>Marco Polo, talking to Genghis Khan</strong></cite> 
<br /><cite>Italo Calvino’s <em>Invisible Cities</em></cite></p></blockquote></p>

<p><em>Note: This essay is the extended version of the talk I gave at the dConstruct conference in Brighton, UK, September 2011.</em></p>

<p>Over the last ten months of working at a startup, I’ve noticed that it’s very easy to lose perspective. That is, it's easy to forget to stick your head up and get context for the work at which your're cranking away. This is especially true while working on front-line digital content design problems.</p> 

<p>The notion of a “new,” digital kind of book scares a lot of folks because there is such a rich fabric of romanticism, nostalgia and myth built up around the physical book. These qualities — <em>romantic, nostalgic, mythical</em> — are really indicative of emotion. And we don't want to lose that emotion. It's easy to forget this; I know I do. I forget how the weight of those myths <em>(some real, some imagined)</em> can and should be informing the work I’m doing now.</p>

<p>As designers working with ebooks, we are at a point of special convergence: many of the promises of digital books <em>(promises that have been spoken for decades)</em> are coming to fruition. Not the least of which being almost everyone carries with them a digital device capable of smartly displaying ebooks. But even more powerful is that all books in the world are being smooshed into a <em>single point</em>, and we finally have enough of a semblance of standards and distribution of devices to seriously consider interesting things to do with that <em>point</em>.</p>

<p>So I asked myself — how does one view the emotional weight of books in the context of our current excitement? And in asking myself this I found an image growing in my mind over the last few months. As I was doing the work of “now,” this image of the “past” grew stronger. That image manifested as a story — an imagined myth of the history of the book, converging with reality around the turn of the 20th century. </p>

<p>I'll be the first to admit that this is odd. But I found it to be tremendously useful as a framing device for the work I’m doing now. And my intent is to share this story as a model for creatively thinking about our kind of work — work that is so new, as to be shaping unseen experiences, but simultaneously connected directly with a weighty past.</p>

<p>Before the story, however, there are some ideas to keep in mind.</p>

<h3>OUR NOW</h3>

<p>Our basic truths:</p>

<ol>
<li>Many people (beyond just a tech / first-adopter subset) are regularly touching digital books via iPads, iPhones, Kindles, Nooks, etc. <em>(Clap, as it were, if you have one of those devices. *clap*)</em></li>
<li>From a user interface and experience perspective, the generalized notion of “content” and our older notion of “books” is merging. <sup id="fn-ref-70-1"><a href="#fn-70-1">1</a></sup></li>
</ol>

<p>The current surface forms for digital books are far from perfect, but they work and are getting better with each device and software iteration. So, in my opinion, many of the critical future questions digital books designers will have to address don’t directly involve pure content layout. Future-book design is not merely about font sizes and leading. Instead, our hardest (and possibly most rewarding) problems will involve the intermingling of content and data.</p>

<p>Over the past ten months of working on digital content containers, I find myself keeping in mind — from a design perspective — three overlapping precepts:</p>

<ol>
<li>Tame unfiltered data streams</li>
<li>Produce quiet data</li>
<li>Corral data</li>
</ol>

<p>There are already any number of startups working to <strong>tame unfiltered data streams</strong>.<sup id="fn-ref-70-2"><a href="#fn-70-2">2</a></sup> The easiest way to think about this is to consider the current Twitter timeline view — if you follow even a reasonably small number of people, it’s nearly impossible to regularly consume the entire stream. The net result is obvious: information overload. We are left with a constant sense of <em>maybe</em> having missed something. Hence, one of the primary roles for an iPad application like Flipboard becomes to evoke a feeling of having made tame, the unfiltered. In concrete terms: <em>we must smartly curate raw streams.</em> And raw streams of data are starting to grow wider and deeper just beneath the surface of almost all digital reading experiences. </p>

<p>Tom Armitage wrote a great post while he was working at BERG in London about the “quiet confidence” of the Kindle compared to the iPad.<sup id="fn-ref-70-3"><a href="#fn-70-3">3</a></sup></p>

<blockquote><p>Attention-seeking is something we often do when we’re uncomfortable, though – when we need to remind the world we’re still there. And the strongest feeling I get from my recently-acquired Kindle is that it’s comfortable in the world.</p></blockquote>

<p>And then:</p>

<blockquote><p>If this device is to replace, for many people, a book, it needs to manifest some of those qualities: safe, nonthreatening, no more distracting than a few hundred of pages of text intend to be. It needs a quiet confidence to make you trust it more.</p></blockquote>

<p>I think the same concept of “quiet confidence” can be applied to data. Namely — in designing user experiences we need to <strong>produce data that doesn’t draw attention to itself</strong> explicitly as data. </p>

<p>These first two precepts are wrapped in the third — <strong>to corral data</strong>. Which is to say, the results of taming unfiltered streams and quiet data shouldn’t detract with the content experience. </p>

<p>As an example, Kindle public highlights straddle the edge of quiet — they’re there but can be turned off. And they’re also corralled — unlike hyperlinks leading away from the text, they don’t really lead you anywhere; they’re just a “Hey! Lotsa folks find this interesting.” sorta reminder. </p>

<p>The obvious followup question to all of this is: <em>what do these data precepts have to do with digital books?</em> Well, as it turns out, our reading applications are growing more data sophisticated with each release. They are collecting more information about what we do inside of a book. How long we read. What we read. Put simply: large, passive sets of metrics around our reading activities are being produced.</p>

<p>Peter Collingridge gave a wonderful talk<sup id="fn-ref-70-4"><a href="#fn-70-4">4</a></sup> at the O’Reilly Tools of Change conference in early 2010 about how his company collects and uses metrics around reading experience:</p>

<blockquote><p>From the moment the very first printed book was sold, there has always been a relationship between publishers, readers, and marketing activity. It’s just been invisible. Short of breaking into people’s houses there is very little a publisher knows about a book after it is sold.</p></blockquote>

<p>Now they <em>(publishers, digital reading devices)</em> know significantly more. </p>

<p>One result of the collection or sharing of reading metrics (both passive and active data) is the development of communities. <a href="http://kindle.amazon.com">Amazon's Kindle site</a> is evidence that Amazon is clearly moving in this direction. Readmill is another startup looking to capture and surface the same sorts of community reading data.<sup id="fn-ref-70-5"><a href="#fn-70-5">5</a></sup> There are many others, of course.</p>

<h3>Data aware</h3>

<p>Designers working on the future form of the book need to be aware of these emerging datasets. It’s only through an awareness that we can surface them without harming the reading experience. And data, in my opinion, “harms” the reading experience whenever it pulls the reader away from the text, or forces them to concentrate harder than they would with a physical book. </p>

<p>But, still, with all of this in mind, it's critical not to forget we’re working at the tip of the edge of a field with a tremendously rich past. Working on these startup-like problems can lead to lack of perspective. And lack of perspective makes us forget about the evocative experiences the physicality of printed books brought to reading. Matt Might has a wonderful illustration of what it means to get a Ph.D.<sup id="fn-ref-70-6"><a href="#fn-70-6">6</a></sup></p> 

<p>Working in a startup context is pretty similar to working on a Ph.D. Startups are startups because they're pushing on the edge of some field. And if you're working with digital books, by default you're doing startup work. We have to make sure we don’t get stuck in that “knowledge nipple” in Matt's illustration — we need <em>tools</em> to zoom back out and remember the greater whole.</p>

<p><a href="/images/satellite/phd-01.jpeg" title="Where we're working."><img src="/images/satellite/phd-01.jpeg"  width="290" style="float: left; margin-right: 20px; margin-bottom: 20px; border: 1px solid #ddd;" /></a>
<a href="/images/satellite/phd-02.jpeg" title="Where we shouldn't get stuck."><img src="/images/satellite/phd-02.jpeg" width="290" style="float: left; margin-right: 20px; margin-bottom: 20px; border: 1px solid #ddd;" /></a>
<a href="/images/satellite/phd-03.jpeg" title="What we need to keep in mind."><img src="/images/satellite/phd-03.jpeg" width="610" style="margin-bottom: 20px; border: 1px solid #ddd;" /></a></p>

<h3>Distance</h3>

<p>And so — the story. The myth. A framing, imagined, yes, but still a framing. There are many myths around books, but this is mine. And for me, this sort of exercise becomes a <em>tool</em> for grounding; stepping back; and if not seeing, hopefully feeling the whole.</p> 

<p>In the opening quote — <em>"... the more one was lost in unfamiliar quarters of distant cities, the more one understood the other cities he had crossed to arrive there."</em> — Marco Polo was responding to Khan's question of “Why do you travel?” Khan criticized Polo of failing to bring back riches, just stories. And Polo's response is about perspective. Perspective was riches enough for him. As it turns out, Polo was never traveling anyway — his stories, too, were imagined.</p>

<p>Really, in presenting this, I’m asking you to consider <em>your</em> myth around the book. What emotion does the book of the past evoke for you? What does it mean for you as a designer? Is there a way to carry some of that feeling forward into the work we're doing today? There's a plethora of wonderful things digital brings to books, but they shouldn't come at the expense of the confident experiences already embedded within the idea of books.</p> 

<p><br />
<hr />
<br /></p>

<div id="myth">
<h4>AN ETHEREALITY</h4>
<p>Thousands of years ago and thousands of miles outside of the port village of Shanghai, in the strange hot cold deserts of the Gobi — the endless sea — deep in the heart of Mongolia, it was discovered. </p>

<p>At first, nobody knew what it was. It was too large to be immediately understood. The precise dimensions, while at the time unknown, ended up measuring roughly five kilometers long (north-south) by two kilometers wide (east-west), with a depth into the sands of nearly half a kilometer. The speculation is that it had been buried much, much deeper but with time the sand had shifted and the world had, slowly, lifted the object up from the desert floor. </p>

<h4>SEED OF MYTH</h4>
<p>Nobody knows who, exactly, was the first person to stumble upon a piece of it. But each village has their own theories and their own mythologies have evolved around the discovery. For some it was a child, others an old woman. There are tales of wanderers with visions and conquerors with nightmares. </p>

<p>Regardless, who found it or how it was found is of no concern. There is only now, the result of the finding, and how we arrived here into which we need to look. </p>

<h4>THE PROMISE OF FORM</h4>
<p>From the point of first discovery to understanding the enormity of the object took nearly two hundred years. </p>

<p>Word spread slowly through sub-mythologies about this object — coarse and dark, sometimes poking through the sands of the valleys of the desert. Unnaturally straight, level. Over time, it became the focus of countless speculations. </p>

<p>For many generations it simply loomed in the contradictions of evolving mythology — a thing, a nothing, an everything. Something worth investigating or ignoring. Dismissed, considered. </p>

<p>Still, slowly the people found the edges. Mapping technology improved and information was shared. Lines triangulated. Expeditions sent to measure. To look for other instances. It was large enough to confuse generations but not large enough to be entirely impenetrable. </p>

<p>Once a general sense of the size was achieved, primitive technologies — but technologies none the less — were invented to move sand and earth more efficiently for the purpose of excavation. Thousands worked in concert over generations to displace what was covering this thing.</p>

<h4>MYTH MADE TANGIBLE</h4>
<p>Finally, the earth alongside and above the thing was moved. The totality of the size of the object could be fully understood. From the crest of the Alashan Plateau on the outer edges of the Gobi, it was visible — stark, the contrast of its deep brown surface beautiful against the golden and light brown sands. Something demanding absolute consideration. </p>

<p>It was tremendous in volume, and looked to be covered entirely in a seamless layer of animal skin. The scientists of the time worked out that there was a hinge along the western long edge. And that maybe, just maybe if they could work out a system by which to apply force, the top layer could be moved about that hinge. </p>

<p>Again — calculations. A generation. It had now been hundreds of years since the first discovery of this thing. Its existence had embedded itself into the very fabric of the desert societies living near and around it. Stories of the object had spread as travelers moved along the silk road. Traders described the rough surface, it’s impossibility of form to family back home. You could find it in the ghost stories of children. In the bedtime chatter between parents. In the whimsical remembrances of the elderly. Songs were sung about it, to it and for it. </p>

<h4>EMBEDDED CULTURE</h4>
<p>The great push to move about the hinge began. Consider the mere size of the object! How could this ever be moved?, many said. But still, the scientists understood the simple mechanics of a simple machine to multiply force. They understood leverage and pulley systems. Certainly, they thought, through mechanical advantage this could be done. </p>

<p>The calculation was that it would take 20,000 men of peak physical strength<sup id="fn-ref-70-7"><a href="#fn-70-7">7</a></sup> to move the top layer. It would take them a coordinated effort over a period of years. But these villages, these societies were now accustomed to these efforts, these sacrifices. They remembered the years of mapping. The expeditions to understand the breath of the thing. The generations of digging and displacement. Their cities were surrounded by the walls of excavated sand and earth that had once encased the object. </p>

<p>They had heard from their parents, and parent’s parents. From great gandparents and beggars of the desert. From mystics and scientists alike. From all of these people they had heard of the object. It had been a part of their lives, always present, always demanding attention, evoking questions. Providing no answers. Nourishing only a mythology of speculation. Else, nothing. And so this had become a society comforted by and habituated into sacrifice.  With this in mind, the training began.</p>

<h4>MYTH DISSEMINATION</h4>
<p>Boys were taken from families and sent to camps. These desert nations were building armies of pushers and pullers. A massive human can opener. At these camps, technologies of leverage were iterated on, tested. Systems by which to announce the PUSH and PULL across kilometers and kilometers of desert were devised. Everything had to move in perfect synchronicity. </p>

<p>Finally, they were ready.</p>

<p>Thousands of camps were setup around the object. Food supply chains established. Endless streams of water diverted to fuel the efforts. It was determined that the pushing and pulling would take weeks, if not months, to get the lid of the object to a state of total verticality. Because of the volatility of the desert — the hot and cold, the night frost, the unbearable afternoon heat — the movements would take place only at dusk and dawn, timed precisely to intervals of the moon rising or setting, during the hour in which the sky cycles into or out of nothingness. </p>

<p>Thousands of ropes were attached to the outer lip of the top of the object, ropes kilometers and kilometers in length. Each the diameter of a man’s thigh. They were draped across the burning animals skins, now beginning to fade from a dark to light brown as they had been exposed to the harsh desert sun for nearly a hundred years. Skins that screamed and screeched to the undulating temperatures of the Gobi. </p>

<p>Ten thousand men lined up on one side of the object. Two kilometers away, another ten thousand other men lined up with ropes. Wedges ground out from the bones of massive animals, now extinct — had been made extinct in the process of tool production — were in hand. Scholars draped in saffron robes waited anxiously, notepads held closely. Everyone was ready. </p>

<p>The signals were sent — combinations of fugue-like iterations of song, with specially understood points of phase overlap on which the pushing and pulling would happen. Under the first full-moon of the 6th month of this year — the year of the opening — beneath billions of bits of cosmic information, the song rippled out across the deep blue of the night that is so characteristic of an open, endless desert. </p>

<p>The men on the side of the hinge pulled, the men on the side of the flap, pushed. Wedges were inserted, a creaking that was said to be heard as far as the plateaus of Tibet was released from the object. A painful groan.</p>

<p>That first night they managed to move the top of the object almost a meter into the air before men were passing out, hands bleeding. They rested for a day and then again, the songs rippled out. Children remember those nights — the haunting music coming from far off in the desert. For months they moved the object centimeter by centimeter higher. A few times they lost their grip, men were crushed under the weight. Limbs were severed as the song would sometimes fall off rhythm and the efforts become uncoordinated. But they had trained precisely for this pain. For this exertion. For the sacrifice of opening this thing that had haunted them for generations. </p>

<p>After months the top of the object reached peak verticality and with one last heave, one last ho, the hinge let out of massive sigh — this time, of total relief — as the lid, the cover, if you can imagine, this vertical tower two kilometers high and five kilometers long, teetered for a moment as the first morning light exploded from the east, casting a shadow hundreds of kilometers long, as this object then came crashing down the other side of the desert. </p>

<p>Nobody had anticipated the force with which that object would attack the desert floor. Millions of pounds of animal skin, dried and smoothed smashed the sands with such impact, that all of the men on the side of the hinge who didn’t make it into shelter were killed. The sand ripped through the air like a trillion needles — evaporating nearly everything in its path. </p>

<p>Still — it was open. And this wasn't the first sacrifice to have been made. </p>

<h4>CULTURE OF TANGIBLE MYTH</h4>
<p>Once opened, once the dust had settled, as it were — the scholars poured in en mass. Revealed beneath that top skin were perfectly smooth sheets of pulp with huge, thick marks of deep, black ink. The marks were multitudinous — billions upon billions of them. It wasn’t until months later, when someone looked upon the object from the Altai Mountains, that they realized just what had been unearthed — a fractal of information. The billions of tiny marks on each page, when viewed from afar, formed larger, individual marks. Stories embedded within stories. Each layer of pulp a page in a greater story, and each character on each page composed of a thousand sub-stories. </p>

<p>It took hundreds more years to get through the first few layers. Despite the best attempts at protecting the object, there were countless problems. Theft was rampant — large swarths of pulp were cut off in the dead of the night. Some folks revered the object, other loathed it. There were any number of attempts to destroy the entire thing with fire. </p>

<p>It wasn’t long before the nearby governments realized the pulp was useful for a number of things and so they began to harvest it. The excess of pages, once categorized and filed away to the best of the ability of the scholars were sliced into millions of pieces. </p>

<h4>TOTAL DEMYSTIFICATION</h4>
<p>The stories became currencies, peopled used it for barter, you could buy a basket of rice for a pound of story. The more black ink the more valuable. At first it was trade through nostalgia — the value of simply owning a piece of the core of now nearly a thousand years of their own culture. The ethereality of their myth made tangible. Culture folding into culture. As uses for it grew, so did the value. </p>

<p>Clothes were fashioned from the stories. They wore the promise of the myths of their great-grandparents to the market, the temples. Ground in water and boiled, the stories made a fine, earthy stew. Little children slept between sheets of the stories. Above and below a piece of a piece of a story. Their new dreams mixed with the old dreams, sleeping between both the myth of the object — something about which now dozens of generations had dreamt — and atop the myths contained within the object, still unknown, still under scrutiny.</p>

<p>New traditions sprung up. New romanticisms. When babies were born they were given a piece of the story. As the children grew older they would carry the piece with them, and upon making a new friend, a new lover, an enemy they would compare pieces, see if they were adjacent. An infinitesimally small chance of rebuilding an impossible puzzle. </p>

<p>Time passed. Large pieces of the object were lost in wars. It took hundreds more years to understand the languages. The symbols in artists’ renditions of the larger pages — the macro story — were used to decipher the micro languages. Slowly the mythologies of the stories were united with the actual stories themselves. </p>


<h4>ZEROED OUT</h4>
<p>They were reproduced. Commoditized. Through the age of mechanical reproduction all nostalgic quality of the stories was lost. The myths of the myths were produced alongside the actual myths. People forgot which were the originals, which were invented. </p>

<p>They became further atomized. The objects were called books. The age of mechanical reproduction gave way to the age of photographic reproduction and the books were reproduced once more. Made small, nearly invisible. Such so that almost all of them would fit atop a reasonably sized desk. </p>

<p>They were getting closer to nothing.</p>

<p>At first glance these microscopic books photographed and atop a table were more similar than ever to their idea of that object embedded in the desert so long ago. But the atomization process, while making them untouchable — the physicality of the content directly inaccessible to human senses — had compressed them into a single dimensional point in the eyes of our tools. </p>

<blockquote><p>In this the book is no longer a package<br /> — it’s information service.</p></blockquote>

<p>Said of course in 1967, by, of course, Marshall McLuhan.<sup id="fn-ref-70-8"><a href="#fn-70-8">8</a></sup> </p>


<h4>ETHEREAL AGAIN</h4>
<p>What happened in the forty years following has been a mere formalization of this atomization. An attempt to agree upon and codify that single point into which all books — and content — have been compressed. </p>

<p>It seems as if we are now, once again, on the edge of something buried in a desert. There is the myth of what that object might be. There is a dissemination within our culture through devices and distribution channels of varying iterations on that myth. We see it everyday, all around us. And are presently building tools to excavate that object, but we’ve yet to find the right ones.</p>

<p>While similar in idea to that imagined desert book, the difference now is that the object or objects we’re pulling out are no longer just the stories themselves — they’re also our interactions with the stories. Each time we turn the page, a machine knows. Records. Triangulates. </p>

<p>New mappings are being constructed — for an object of which we don’t yet know the size. Of which doesn’t have a determinate size.</p>

<p>For these mappings, as designers and engineers, we’re building a container. We’re looking for a new form. And it’s frustrating and scary at times, but I think for everyone working in this space, there is an overwhelming sense of gratitude to be here now, at this particular moment in time, working on this problem. Searching out the future book. </p>
</div>

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-70-1">"Content" is such a horrid word, but it's what we've got. Regarding the convergence of generalized content and digital books — from an interface / user experience point of view — consider Instapaper, which looks and feels in many ways like the Kindle app or iBooks. <a href="#fn-ref-70-1">&#8617;</a></li>
	<li id="fn-70-2">Perhaps the most obvious yet also most overlooked is Facebook. Not a startup anymore, but a tremendous amount of energy in that company goes into making your Top News newsfeed a consumable number of interesting items, changing based on your Facebook browsing habits. The raw newsfeed for an average user has something like 2,500 daily items in it. <a href="#fn-ref-70-2">&#8617;</a></li>
	<li id="fn-70-3">Asleep and Awake, Jan 2011 — <a href="http://berglondon.com/blog/2011/01/14/asleep-and-awake/">http://berglondon.com/blog/2011/01/14/asleep-and-awake/</a> <a href="#fn-ref-70-3">&#8617;</a></li>
	<li id="fn-70-4">Tools of Change: Analytics Wake Up Call, Jan 2010 — <a href="http://www.enhanced-editions.com/blog/2010/02/tools-of-change-analytics-wake-up-call/">http://www.enhanced-editions.com/blog/2010/02/tools-of-change-analytics-wake-up-call/</a> <a href="#fn-ref-70-4">&#8617;</a></li>
	<li id="fn-70-5">Readmill: <a href="http://readmill.com/">http://readmill.com/</a> (Email me if you want an invite!) <a href="#fn-ref-70-5">&#8617;</a></li>
	<li id="fn-70-6">The Illustrated Guide to a Ph.D: <a href="http://matt.might.net/articles/phd-school-in-pictures/">http://matt.might.net/articles/phd-school-in-pictures/</a> <a href="#fn-ref-70-6">&#8617;</a></li>
	<li id="fn-70-7">Louis CK Show, Season 1, Ep: "God" <a href="#fn-ref-70-7">&#8617;</a></li>
	<li id="fn-70-8">Marshall McLuhan Interview, 1967 — <a href="http://www.youtube.com/watch?v=OMEC_HqWlBY">http://www.youtube.com/watch?v=OMEC_HqWlBY</a> <a href="#fn-ref-70-8">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2011-06-14T06:28:33+00:00</published>
      <updated>2011-06-14T06:28:33+00:00</updated>

             <title>Post&#45;Artifact Books and Publishing &#45; Craig Mod &#45; Journal</title>
        
        <link href="http://craigmod.com/journal/post_artifact" />
        <id>http://craigmod.com/journal/post_artifact</id>

        <content type="html" xml:base="http://craigmod.com/journal/post_artifact">
        <![CDATA[
          <a href="http://craigmod.com/journal/post_artifact/"><h3>Post-Artifact Books and Publishing</h3>
          <img src="http://craigmod.com//images/journal/post_artifact/post_artifact_cover-300x300.png" />
          </a>
          <p>Thinking about books after Books. Publishing after Publishers.</p>

<p>There is the making of content. The content container. Then, our playful dance around the container.</p>

<p>How does digital affect these spaces? How do we talk about these spaces?</p>
        ]]>
        </content>

          </entry>

    <entry>
    
      <author>
        <name>Craig Mod</name>
        <uri>http://craigmod.com</uri>
      </author>
      <published>2011-06-02T06:44:36+00:00</published>
      <updated>2011-06-02T06:44:36+00:00</updated>

             <title>Twitter archives and the sendai quake &#45; Satellite &#45; Craig Mod</title>
        
        <link href="http://craigmod.com/satellite/twitter_archives" />
        <id>http://craigmod.com/satellite/twitter_archives</id>

        <content type="html" xml:base="http://craigmod.com/satellite/twitter_archives">
        <![CDATA[
          <a href="http://craigmod.com/satellite/twitter_archives/"><h3>Twitter archives and the sendai quake</h3></a>
                    <img src="/images/satellite/sendai-title.jpg" width="400" />
                    
          <p><p>In April of this year, I had the privilege of speaking at CreativeMornings’ San Francisco<sup id="fn-ref-68-1"><a href="#fn-68-1">1</a></sup> chapter. This was a honor for me on a number of levels, not the least of which being I had attended the very first Creative Mornings in New York City some three years prior. It was there I first met Swiss Miss.<sup id="fn-ref-68-2"><a href="#fn-68-2">2</a></sup> I have a lifelong hobby of closing loops, and so being able to speak at the San Francisco Typekit office, looking out over the city on that bright and sunny April morning, allowed me to close yet another.</p></p>

<p>The talk was called <em>A Strange Flight</em>. And it grew from a recent trip I had taken to Japan. A trip in which I arrived in Tokyo just hours after the 9.0 Sendai Quake. You can watch the talk here:</p>

<p><iframe src="http://player.vimeo.com/video/24547083?title=0&amp;byline=0&amp;portrait=0" width="560" height="400" frameborder="0"></iframe><p style="font-size: .9em; font-style: italic;"><a href="http://vimeo.com/24547083">2011/04 Craig Mod | A Strange Flight</a> from <a href="http://vimeo.com/sanfranciscocm">SanFrancisco/CreativeMornings</a> on <a href="http://vimeo.com">Vimeo</a>.</p></p>

<p>The more we’re involved with the creation of systems — be them iOS, HTML, EPUB, literary or photographic based — and the greater the reach of these systems, the stronger I feel shift the definition of our role as “designers.” There’s a growing obviousness that a designer must be holistic. That a designer must be someone who understands the output from the perspective of user, engineer and audience within the context of entertainment or business or social change. As someone who attempts to empathize fully with all perspectives <em>(or at least those currently perceivable)</em> and desires with an eye towards the functionality of the system. And synthesizes those desires organically, quietly and genuinely into the interface and user experience. </p>

<p>So, considering this, I’ve begun to operate under the ethos of:<br /> 
<strong>Great design is born from nourishing habits</strong></p>

<p>And, perhaps, as an addendum:<br /> <strong>Great design is born from constant application of nourishing habits across all life experience.</strong> </p>

<p>While my intent for 2011 was one of placidity and predictability, it’s been anything but. Arriving in Tokyo on the day of the earthquake has been one of several aberrations this year. And it has been because of these aberrations that I’ve started to recognize this underlying philosophy in my work. </p>

<p>The three core habits informing the ethos are:</p>

<ol>
<li>A constant effort towards empathy</li>
<li>A non dismissive stance</li>
<li>A shifting between micro (local) and macro (global) perspectives</li>
</ol>

<p>By constantly working towards empathy in any situation, you are inherently being non-dismissive. And if the goal is to achieve a holistic empathetic stance, then you need to understand a problem on both micro and macro levels. How does this problem affect components closely tied to the system? And how does it affect the greater macro ecosystems of which it’s a part?</p>

<p>Arriving in Tokyo on the day of the quake placed Twitter and Facebook into interesting and well defined use cases. Twitter was overwhelmingly the go-to service for first-person reportage on what was happening during the quake. In fact, I used Twitter to <em>go back in time</em> and “relive” the moment the quake hit for a number of my friends. I was able to <strong>experience the quake through their eyes</strong> and immediately perceive — <em>on a tremendously intimate micro-scale</em> — the gravity of the events. </p>

<p>The more I used Twitter to understand and check on the safety of friends, the more I realized there was — dare I say — a moral obligation on the part of Twitter to provide easier access to this archival data. In fact, weeks later, when I was first gathering data for my talk, I found it nearly impossible to scrobble back in time and capture — with granularity — these first-person narratives that so uniquely and spectacularly defined the experience of being in Tokyo during the quake. That I had to <strong>work hard</strong> for this data seemed to be a sad shortcoming of the Twitter interface. And it made me wonder how many other folks would benefit (emotionally, psychically, educationally) from access to well mapped contingencies of Twitter data. </p>

<p>Being there on the ground during this event, and having that hyper-local perspective allowed me to see precise changes in the way social media was used. After the intense initial reportage period passed <em>(by Saturday)</em>, Twitter devolved into a sort of Kaczynskian-esque chamber of conspiracy. The government was lying! <em>(Turns out, they were.)</em> and we were all on the verge of death! and acid rain was coming! and take your iodine tablets! now! to save yourself before it’s too late! and! and! and! Which did nothing to quell or calm fears. And none of which were based on verifiable facts. (“A friend in the government told me ... !”)</p>

<p>On the flipside, Facebook, largely ignored during the first-person reportage period of the quake, shined as the place for communicating with family. I witnessed friends in Japan posting constant updates and photos as to their whereabouts. And saw family members from around the world react with happiness and relief. </p>

<p>This clear bifurcation<sup id="fn-ref-68-3"><a href="#fn-68-3">3</a></sup> of use made me wonder why we turned to these services in these ways. It’s hard to see it boil down to anything but design choices.</p>

<p>There are four design reasons why I think we all run to Twitter to perform first-person reportage: </p>

<ol>
<li>It’s focused. You can only do one thing (really) in Twitter: say what’s in front of you.
<li>It’s lightweight. Both in terms of data (mainly just text packets) but also in terms of interface. (Although the growing interface complexity of recent releases worries me.) 
<li>It’s efficient. You open it, you post, you leave. Quick. 
<li>It has a near perfect delivery mechanism. The open model of one to many and the publicly linkable nature of most tweets combine to form a very strong platform for quickly disseminating front-line reports. 
</ol>

<p>It’s also interesting to note that there are now effectively two Twitters:</p>

<ol>
<li>Twitter as micro-curation tool
<li>Twitter as reportage tool
</ol>

<p>Application such as Flipboard leverage Twitter’s micro-curatorial tendencies and output beautifully formatted consolidations. </p>

<p>Hashtags help consolidate reportage happening within Twitter. But we’re still lacking a more efficient interface. </p>

<p>In both cases, the notion of an archive plays different but important roles. Particularly, in the case of reportage, Twitter could provide smart meta-data groupings <em>(geo, for example)</em> to aid in surfacing and consolidating historically resonant narratives from the muck. </p>

<p>Facebook, on the other hand, has been guided by a very different set of design decisions. In contrast to Twitter: </p>

<ol>
<li>It’s not particularly focused. There are countless activities from posting updates to commenting on photos to creating groups to playing games. 
<li>It’s heavy. It pulls a lot of data every time you open it. 
<li>It’s inefficient. To jump in and just post an update is to ignore a plethora of multimedia and notifications vying for your attention. (But it's hyper efficient at other sub-activities such as tagging photos.)
<li>The closed system of reciprocity in followship limits its mass broadcast capabilities. 
</ol>

<p>I don't mean to imply one is better than the other, simply that the differences in use cases stem from core design decisions. The fact that the mobile Twitter app is so simple, and its purpose so well defined means most people thoughtlessly and immediately turn to it in times of crisis reporting. The same simplicity comes back to bite it when the reportage ends and the conspiracy begins — echoing sentiment through retweeting is a totally effortless, mindless task. Sound-bite like comments, without any basis in reality, spread like wildfire.</p> 

<p>That said, once the <strong>dramatic</strong> first-person reportage ends, the <strong>mundane</strong> reportage <em>(all clear over here, no dead animals from radiation poisoning, ramen shops still open!)</em> becomes eminently useful. For the first time ever I <em>want</em> to know you're eating a sandwich. And certain folks become powerful resources as news curators — filtering the chaos to provide a stream of links to rational articles and sources.</p> 

<p>It’s through building the habits of a constant effort towards empathy, non-dismissal and perspective shifting that we designers become more aware of motivations behind use cases in products we create or use. Without understanding the psychology and motivations of use, it’s nearly impossible to create genuine interfaces. And without real empathy, you’re often left with surface design and no substance. </p>

<p>This video speaks mainly my experience during the events in Tokyo. But each piece of the talk is meant to emphasize embracing the three tenets of the above ethos — even in the most stressful situations. Of making them a habit that is defining and informative not just for ones work as a designer, but also in ones life as a creator. </p>

<p>As for Twitter archives — it's a hard problem. And I can see how it might not be a top priority within the company. But I hope that there is a sense of how important the right interface to those archives can be. And how surfacing the stories captured within Twitter's efficient reportage ecosystem could be one of the company's strongest, most beautiful assets.</p>

<p><h5>Noted:</h5><ol class="footnotes">
	<li id="fn-68-1"><a href="http://www.creativemornings.com/">http://www.creativemornings.com/</a> <a href="#fn-ref-68-1">&#8617;</a></li>
	<li id="fn-68-2">She approached me and commented on my Mondaine watch — the things designers remember! <a href="#fn-ref-68-2">&#8617;</a></li>
	<li id="fn-68-3">To be fair, it isn't entirely clear cut. Facebook was used to rally up volunteer supporters through Facebook group functionality, and certain Twitter users became the go-to place for calm, metered curation of emerging news on the nuclear situation. <a href="#fn-ref-68-3">&#8617;</a></li>
</ol>
</p>

          
        ]]>
        </content>
          </entry>

    
</feed>