Last month, Clay Shirky gave a presentation with the title “It’s Not Information Overload. It’s Filter Failure” at the Web 2.0 Expo. ¹ Shirky admits up front at the start of the talk that the topic is something new that he is exploring, and as a result the ideas are not fully formed. (I get lost in how the last of his three examples applies to the topic at hand, for instance.) But his viewpoint is a refreshing way to look at the issue of “information overload” from a new perspective, and it is worth looking at even in this raw stage. For starters, he says that we’ve been facing information overload for the past 500 years — since the introduction of the Gutenburg movable type press gave readers more books than they could possibly read. What has changed in the last decade has been how past information “filters” are no longer effective.

Shirky posits that the expense of printing a book made publishers both the creators of the object and filters for information printed in objects. The relatively high up-front costs of producing the book meant publishers in the position of selecting only the best information to print. Publishers were, in effect, a kind of filter of quality for the onslaught of information as a way of reducing their risks of printing content that no one would want to read. The internet has driven the cost of publishing to near zero, and as such the “pre-publication” filter that publishers provided is no longer in place. (He calls this “post-Gutenburg economics.) In Shirky’s words, “the filter for quality is way downstream from the site of production.”

Shirky points to some examples of filters and talks about their effectiveness. For inbound communication, the example is e-mail spam and how spam filters must be constantly tuned. This is a pretty clear example of what he is talking about — the cost of production is cheap and the assessment of quality is done by the reader, not the producer. The second example is one of outbound communication; Shirky tells the story of a colleague who attempted to use Facebook privacy settings to slowly disseminate the fact that she had broken up with her colleague. (That isn’t what happened. P.S.: Karen Schneider — your name pops up briefly in one of Clay’s screenshots!) The third example is that of a student that faced expulsion from a Canadian university because he started a Facebook homework group. Shirky’s point with this example seems to be that a filter-of-inconvenience was removed through the use of technology — that a study group of 147 students wouldn’t actually occur in real life but was replicated on Facebook.

Some other quotes that caught my ear:

• “Managing your privacy practices is an unnatural act… Privacy is a way of managing information flow… The big question we’re facing around privacy now is that were not moving from one engineered system to another engineered system with different characteristics. We’re moving from an evolved system to an engineered system.”
• “The inefficiency of information flow wasn’t a bug, it was a feature. That’s what privacy was.”
• “What the internet does is allows large systems that are free-rider tolerant rather than free-rider resistant.”
• “It really is about rethinking the [higher education] institutional model. You have to have group conversation. You have to have individual effort. You have to design a system that accommodates both.”
• “If you have the same problem for a long time, maybe it’s not a problem. Maybe it is a fact.” –Yitzhak Rabin

Footnotes

1. Web 2.0 Expo, co-produced by TechWeb and O’Reilly Media, “is a global annual gathering of technical, design, marketing, and business professionals who are building the next generation web. Web 2.0 Expo features the most innovative and successful Internet industry figures and companies providing attendees with examples of business models, development paradigms, and design strategies to enable mainstream businesses and new arrivals to the Web 2.0 world to take advantage of this new generation of services and opportunities.”

This one goes out to all of the MacOS X users out there. (For the rest of you, why aren’t you switching?) Perhaps you have seen PocketMod — the origami-like manipulation of an 8 1/2″ by 11″ piece of paper into an 8-page booklet.

Example PocketMod, courtesy of the Boston Globe.

Touted as a way to “get back to the basics” using analog media over digital media, it is a scheme by which you can transform pages of text into a pocket-sized form for carrying around. Many use it as a way to synchronize their digital to-do lists with the analog world, while others use it document shortcuts and cheat-sheets in a convenient form.

I’m migrating from Thinking Rock to iGTD as my Getting Things Done tool-of-choice. One of the things I’m missing about Thinking Rock is its built-in ability to create PocketMods for the actions in the GTD system. The only real easy way to create the PocketMod format was via a Flash applet or a Windows application. Some have set up shell scripts or worked with other programs, but I was looking for something as simple as the MacOS X print dialog box. And with a little bit of Automator, Java, and shell scripting, it is possible!

Step 1: Get the “Multivalent” PDF Manipulation Toolkit

Step 2: Create the Automator Action

In the ‘Run Shell Script’ action, change “Pass input” to “as arguments” then replace “cat” in the command box with this (ignoring any line breaks that may appear here — this text should be entered without line breaks):

cat "$1" > /tmp/temp$$.pdf && java -classpath [location]/Multivalent20060102.jar tool.pdf.Impose -dim 2x4 -layout "1l,2r,8l,3r,7l,4r,6l,5r" -paper letter -verbose /tmp/temp$$.pdf 2> /tmp/temp$$.err && open /tmp/temp$$-up.pdf

Replace [location] with the complete file path where you downloaded the Multivalent20060102.jar file. The final results should look something like this:

Now save this as “PocketModMac” in either the “/Library/PDF Services” directory (to make it available to all users of your machine) or to “Library/PDF Services” in your home directory for just you.

Step 3: Using PocketModMac

After a few seconds, the Preview application will open up with the PocketMod-ed document. Print this document as you would to any printer, then follow the directions for folding and cutting the page to create your booklet.

Troubleshooting and Known Issues

This isn’t necessarily a very nice solution because it leaves files laying around in the /private/tmp directory after it is done. The /etc/periodic/daily/500.daily maintenance script will clean them out automatically after three days, but still — it is somewhat sloppy to leave them around.