Slate

An arcades project

User Tools

Site Tools


Sidebar

contents

  • hypertext
  • note taking
  • convolutes
  • new media
  • modernism
  • situationism
  • literatureNow
  • procedural literature
  • modernism
the_hypertext_reader_explores

This is an old revision of the document!


The hypertext reader explores rather than consumes

An example from print: Bottom's Dream bottoms_dream_extracts_page_7.pdf

Link from Hegemony and Hypertext

What makes reading hypertext so difficult?

To read hypertext, to use its links to make meaning, readers must act and be able to act as explorers and constructors of text and meaning rather than consumers of givens. But the habit of sequential text over-rules the direction that hypertext can take and casts the reader as consumer as in Hegemony and Hypertext. Readers and writers must resist. Writers must write to enable and encourage constructing, and publishers permit such construction with their texts and outside their texts.

example from print: Bottom's Dream

We consume words. The design of Bottom's Dream pushes for construction and exploration rather than consumption. At the content level, it touts a lit=theory of etyms as construction elements. Stylistically, it ranges from vernacular to literary-formal. Narratively, it challenges focalization. At every turn, it keeps the active construction of meaning not encoded at the front. It also gives guidance to how to construct.

The page attached illustrates how B'sD works at the content level and the stylistic level to push the reader to construct, explore, rather than consume.

Even materially, B'sD is constructed to resist to consumer hegemony. It's too long (over 1300 pages). It's too big (folio). It's too heavy (13+ lbs). It looks “too difficult to read.” The lack of paragraphing, non-standard quotation marks, columns, images, drawings, scholarly-looking side notes. The sentences seem to be a challenge to parse, demanding too much attention. In its design, it even prohibits teaching the text.

I haven't found the book difficult. I find it easier to read at the sentence level than Ulysses and FW. Listen to it:
»Have’Y ever actually cunsiderd exactly : why it=is He had this=or=that fav’rite book?« / — : »Nope why should l?« (he said, gratuitously licking lips, then) »First I‘m not gettin' paid for it. And it‘d be pretty unpindownable too — wouldn‘t it?«

That's readable at first pass. Over a few pages, the use of = and moves such as « / — : » become, if not clear, then familiar: They are indicators of reactions of characters, used a little like emoticons.

As for teaching the book, it would be a medieval carnival: 15 students lugging 13 lb folios to class each week. The size would demand lecterns or full-sized desks. The classroom would resemble a monastery. We'd need to cover a mere 100 pages a week - a dawdle in a grad course.

By design, B'sD demands exploration rather than consumption.

and so hypertext

In design, materiality can | must | will limit.

the_hypertext_reader_explores.1576867473.txt.gz · Last modified: 2019/12/20 10:44 by morgan
https://slate.mcmorgan.org/doku.php?id=the_hypertext_reader_explores&rev=1576867473
slate.mcmorgan.org
crawl=CC-MAIN-2020-50
17616
application/http; msgtype=response
sha1:JAKZDNUDQYYEXBA5PNQDAMCERC5F4RCF
<urn:uuid:084542a8-babe-4b61-be35-6801c3b4c0ce>
2020-12-02T22:10:02Z
208.113.172.200
text/html
sha1:2CJ52IJ26VUNFTIPNXEEIYRAWNRAUKBH
<urn:uuid:fa38be31-d7c2-4999-91f8-b00ccb88cd7b>
https://slate.mcmorgan.org/doku.php?id=the_hypertext_reader_explores&rev=1576867473
response
<urn:uuid:fb372ee9-041d-45cf-8ba6-5fbaa5519fd1>
isPartOf: CC-MAIN-2020-50
publisher: Common Crawl
description: Wide crawl of the web for November/December 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-31.ec2.internal
software: Apache Nutch 1.17 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/