{"id":237,"date":"2008-11-03T10:43:48","date_gmt":"2008-11-03T14:43:48","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/digitalnatives\/?p=237"},"modified":"2008-11-03T10:43:48","modified_gmt":"2008-11-03T14:43:48","slug":"information-overwhelm-two-types-of-overload","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/2008\/11\/03\/information-overwhelm-two-types-of-overload\/","title":{"rendered":"Information Overwhelm: Two Types of Overload"},"content":{"rendered":"<p>This week&#8217;s theme here at the Digital Natives blog is Information Overload.  When my calendar reminded me of this, I squinted quizzically at the words.  Though an entire chapter of <a href=\"http:\/\/www.borndigitalbook.com\/\">Born Digital<\/a> is devoted to the question of Information Overload, I realized today that the term is only a vague gesture toward a whole constellation of concerns.  Before we talk about information overload, I wanted to draw a distinction between two facets of that constellation.  <\/p>\n<p>It is definitely possible to feel overloaded\u2014even overwhelmed\u2014by the amount of information that streams past on the internet.  This feeling of overload can derive, though, from two quite different experiences of information: rabbit-holes and spigots.  My friends and I often joke about the peril of <a href=\"http:\/\/www.wikipedia.org\">Wikipedia<\/a>\u2014you fact-check one tiny thing, and before you know it you&#8217;re down the rabbit-hole.  And there go the next few hours.  For some reason, I have trouble getting worked up about this kind of information overload.  It seems like a mostly-positive side effect of curiosity.  It&#8217;s not similar to reading an encyclopedia all afternoon: it <em>is<\/em> reading an encyclopedia all afternoon.  The hyperlinked nature of Wikipedia makes it a perfect environment for exploring the seemingly infinite array of knowledge available on the internet; the relatively stringent community policing at Wikipedia helps to raise the quality of the information contained within that environment.  <\/p>\n<p>That&#8217;s the rabbit-hole risk.  Though I&#8217;ve described a pretty limited scenario\u2014staying within the bounds of Wikipedia\u2014it&#8217;s a good illustration of a phenomenon that can happen anywhere on the internet.  Hyperlinks are a handy way to reveal the provenance of ideas and effortlessly suggest additional reading.  The feeling of &#8220;overload,&#8221; it seems, occurs when curiosity or the fearsome imperative of procrastination makes the rabbit-hole feel inescapable.  <\/p>\n<p>What about the spigot risk, then?  This is exemplified, I think, by the magnetic draw of RSS readers.  RSS readers\u2014&#8221;inboxes for the internet&#8221;\u2014pull blog posts and updates down from chosen websites in real time, and aggregate them into programs that operate much like email inboxes.  The programs (<a href=\"http:\/\/www.google.com\/reader\">Google Reader<\/a> is a popular one) display unread counts and often full-text copies of articles from each website.  Theoretically, they save their users from having to check preferred websites constantly to see what&#8217;s new.  Not all Digital Natives use RSS readers; in fact, probably few of them do.  However, many other services leverage the same principle: providing a river of information that never runs dry.  <a href=\"http:\/\/www.facebook.com\">Facebook<\/a>&#8216;s news feed is another good example: it pulls &#8220;news&#8221; from friends&#8217; profiles, providing a single destination for social procrastination.  Other sites, like the gadget blogs <a href=\"http:\/\/www.gizmodo.com\">Gizmodo<\/a> and <a href=\"http:\/\/www.engadget.com\">Engadget<\/a>, pride themselves on posting new reviews and rumors almost hourly.  And, of course, <a href=\"http:\/\/www.digg.com\">Digg<\/a>&#8216;s homepage aggregates the &#8220;most popular&#8221; posts on the internet at any given moment, as measured by the number of people who have &#8220;dugg&#8221; each one.  These sites serve as de facto information spigots.  The feeling of &#8220;overload&#8221; here, though, comes not from the time-suck of information exploration, but from the sense of obligation that accompanies an &#8220;unread&#8221; count.  When given such reliable streams of information, it&#8217;s all too common to feel constantly behind; constantly in need of catching up.  That sense of obligation, often, is misplaced.  An unread articles count should be a convenience\u2014not a wagging finger.<\/p>\n<p>The internet is a vast array of hyperlinked information.  Anybody could follow links for the rest of their life, and never reach the end.  Overload, then, seems inevitable: the system itself has become a conglomerate entity that would overload <\/em>any<em> mind with its sheer volume.  The question then becomes not how to stop overload, but how to manage and assuage the feeling of being overwhelmed by it. <\/p>\n<p>How do you deal with information overwhelm?  Are there there greater risks involved than the ones described here, and if so, what&#8217;s at stake?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This week&#8217;s theme here at the Digital Natives blog is Information Overload. When my calendar reminded me of this, I squinted quizzically at the words. Though an entire chapter of Born Digital is devoted to the question of Information Overload, I realized today that the term is only a vague gesture toward a whole constellation [&hellip;]<\/p>\n","protected":false},"author":1729,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1175],"tags":[],"class_list":["post-237","post","type-post","status-publish","format-standard","hentry","category-information-overload"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/posts\/237","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/users\/1729"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/comments?post=237"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/posts\/237\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/media?parent=237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/categories?post=237"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/digitalnatives\/wp-json\/wp\/v2\/tags?post=237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}