Slipstream, part 3.

One of my favorite literary genres at this point is what author Bruce Sterling once dubbed slipstream. Slipstream, which includes the work of authors like Steve Erickson and Haruki Murakami, occupies a middle ground between ‘straight’ fiction and science fiction or fantasy. Like fantasy, slipstream stories play fast and loose with the boundaries of what can be considered strict realism, incorporating elements that may appear outlandish or inexplicable (if not actually supernatural) within what is otherwise a realistic setting and tone.

A defining slipstream moment, in my mind, is a scene in Haruki Murakami’s novel Sputnik Sweetheart in which the character Miu describes being atop a Ferris wheel near her vacation hotel, seeing through opera glasses that two mysterious figures are having sex in her hotel room, and realizing to her astonishment that one of the figures is she herself. The novel offers no explanation for this unnerving moment, which leaves the character profoundly disturbed. Was it a bad dream, a hallucination, or something much stranger? The character doesn’t know, and Murakami leaves the interpretation to the reader.

What distinguishes slipstream from standard fantasy (and in this case, I use “fantasy” as a blanket term, encompassing science fiction, speculative fiction, horror, and magical fantasy of the Terry Pratchett variety) is that lack of explanation. When fantasy breaks the rules of what’s generally accepted as realism, it offers an alternative framework in their place. If a character vanishes into thin air in a fantasy story, the author will eventually present a demi-rational explanation. Perhaps the vanished character has been whisked by some form of magical or technological teleportation. Maybe a time traveler has altered history and caused her to cease to exist. Or maybe she wasn’t really there to begin with — maybe she was a hologram or a magical illusion. Whatever the reason, if the protagonist or POV character doesn’t understand it at the outset, he or she will figure it out during the course of the story. The unspoken contract between the author and the reader is that the author will eventually reveal what really happened. In that respect, fantasy is not about unreality so much as alternative reality.

By contrast, slipstream does not necessarily offer that reassurance. Even if the protagonist or another character does provide a coherent (if not rational) explanation of the story’s odd events, there’s no guarantee that it will be the truth. The protagonist is left to draw conclusions based on his or her own first-hand experience.

The effect of that subjectivity is to change the narrative’s center of gravity. A fantasy story’s focus tends to be, to one degree or another, on the characters’ interaction with the mechanics of the story’s alternative reality. (In a sense, it has to be, if the fantastical elements are to have any narrative purpose.) A slipstream story’s focus is on the characters’ experience of the unusual — how they perceive their experience (and sometimes how they reconcile not understanding it).

You might reasonably ask how slipstream differs from magical realism, which also inserts fantastical elements into otherwise realistic settings and stories. The distinction is a subtle one, and there are a lot of slipstream stories that could reasonably be classified as magical realism. For me, the distinction is primarily one of surety. The fantastical elements of a magical realist story may not have an explanation or rules (at least that are presented to the reader), but their reality within the context of the story is not in question. For example, at a climactic moment of Carlos Trillo and Domingo Mandrafina’s satirical graphic novel Cosecha Verde (a.k.a. La gran patraña, or The Big Hoax in English translation), the fictional nation of La Colonia is struck by a night that lasts for several days. The story offers no particular explanation of why this happens, but its reality within the story is not in doubt — all the characters experience and remark on it, even though they find it odd. Slipstream rarely leaves its oddities so cut and dried; they tend to focus more on “relativistic” effects, things that only one character sees, or are only seen by a few among the multitude.

Three things become clear about slipstream as a genre:

  • It’s usually somewhat unsettling.
  • Being unsettling or discomfiting is part of the point.
  • Making such a story dramatically satisfying is tricky, because it involves an inherent lack of closure.

When Bruce Sterling coined the term slipstream in 1989, he said that its central purpose and unifying theme was capturing the strangeness of living in the late 20th century (and now the early 21st). In that sense, it’s a form of speculative fiction. Rather than speculating about a specific sociopolitical trend or technological development, slipstream is principally concerned with the nature of change. It examines the psychological and emotional impact of living in a world whose technology, priorities, and rules can change significantly without notice. This is the reason why most slipstream stories are set in the modern era; the genre’s fundamental discomfiture only really works if the story takes place within a familiar setting.

Why do I like slipstream? As I said in my previous post, I’ve come to find fantasy narratives unsatisfying — they create a cognitive dissonance between my intellectual experience of the story and my emotional experience. Looking at a story intellectually isn’t necessarily bad, but it doesn’t provide the emotional experience that I’m looking for in fiction. I might find the ideas interesting or compelling, but if it’s only the ideas, I’d rather the author wrote an essay about them, rather than a story. Since slipstream is more concerned with experience than ideas, its strangeness can serve to draw me more fully into its emotional journey, rather than throwing me out of it.

The frequent drawback of slipstream is that it doesn’t necessarily provide a lot in the way of closure, and their plots don’t necessarily make a great deal of linear sense. When I was younger, I just thought stories like that were weird, if not infuriating. Coming to embrace them has required a substantial shift in my own outlook.

The world is a weird place. As even a casual reading of modern physics makes clear, the physical universe around us is deeply strange. We can’t routinely perceive a lot of the truly odd stuff because of our scale, but bizarre, deeply counter-intuitive things happen around us all the time. Add to that the potential for vast social and technological change in a remarkably short time, and discomfiture is the rule, not the exception. Contemplating that — which is something that can cause profound vertigo — has given me a new appreciation for the Weird.

# # #

2 thoughts on “Slipstream, part 3.”

  1. Aaron Severson

    Haruki Murakami's books frequently fall into this realm: <strong>Sputnik Sweetheart</strong>; <strong>A Wild Sheep Chase</strong> and its sequel, <strong>Dance, Dance, Dance</strong>; <strong>The Wind-Up Bird Chronicles</strong>; <strong>Kafka on the Shore</strong>. Steve Erickson's <strong>The Sea Came in at Midnight</strong> would qualify (his latest <strong>Our Ecstatic Days</strong>, which involves several of the same characters, is even stranger, but its oddities are more explicit: a giant lake that consumes Hollywood, a woman falling between dimensions), as would <strong>Zeroville</strong>. I'd put Jim Dodge's <strong>Not Fade Away</strong> in this category, because it has the same kind of emotional effect on me, although I'm sure some people would dispute that, saying it's more of a picaresque.

Leave a Comment

Your email address will not be published. Required fields are marked *

Commenting also signifies your acceptance of the Comment Policy — please read it first! Comments may be moderated.

Privacy Preference Center

Privacy and Cookie Preferences

These cookies manage your cookie and privacy preferences. There will typically be several such cookies, each beginning with "gdpr" (e.g., gdpr[allowed_cookies], gdpr&5Bprivacy_bar&5D, and gdpr[consent_types]). They normally expire after about one year. If you delete or disable these cookies, your existing preferences will be lost and you may not be able to save your privacy settings for this website. (These cookies may not be set at all for administrative users unless they access the publicly visible portions of the website.)

gdpr, gdpr[allowed_cookies], gdpr&5Bprivacy_bar&5D, gdpr[consent_types]

Accessibility Settings

If you change certain aspects of the site's appearance using the accessibility sidebar, it may set these cookies to manage and remember your settings. The wahFontColor and wahBgColor cookies, which are set if you alter the site's color scheme, normally expire after about 14 days, but you can remove them immediately by clicking the "Restore Defaults" button on the sidebar.

I may sometimes present an alternative version of the sidebar offering different options, which may set the a11y-desaturated, a11y-high-contrast, and/or a11y-larger-fontsize cookies if you change those settings. These a11y cookies normally expire after about seven days, but are removed immediately if you restore the applicable settings to their default values.

wahFontColor, wahBgColor, a11y-desaturated, a11y-high-contrast, a11y-larger-fontsize

Age Verification

Viewing certain site content may require you to first verify your age by entering your date of birth. If your birth date indicates that you are 18 or older, the website places the age_gate cookie (whose value is "1," meaning "yes, passed") to allow you to access age-restricted content. The cookie remains active for up to 14 days if you click the "Remember me" check box when you enter your birth date; otherwise, the cookie normally expires when you close your browser. If the birth date you entered indicates that you are NOT 18 or older, the website may place the age_gate_failed cookie (whose value is also "1") to prevent you from trying again to access age-restricted content. (The website does not retain your birth date or your age. See the "Age Verification" section of the Privacy Policy for more information about how the age verification system works.)

age_gate, age_gate_failed

Password-Protected Posts

Accessing certain posts or pages on this website may require you to enter a specific password. If you correctly enter the password, the site saves this cookie on your device to allow you access to the password-protected post or page. (For this cookie, "xx" will be a cryptographic hash.) The cookie normally expires in about 10 days and is not set at all if you do not access any password-protected content.

wp_postpass_xx

Commenting

When you submit a comment, you may have the option save your information for future comments, storing the info in these cookies. (For each of these cookies, "xx" will be a cryptographic hash.) The cookies are not set at all unless you select that option when submitting a comment. They normally expire in just under one year, but you can delete the cookies in your browser at any time. (These cookies are not usually set for administrative users, since comments they submit while logged in are associated with their user ID number and user profile information rather than a manually entered name and email address.)

comment_author_xx, comment_author_email_xx, comment_author_url_xx

YouTube Videos

These third-party cookies may be set by YouTube (which is now owned by Google, superseding the now-defunct Google Video hosting service) in connection with embedded videos, for purposes such as (without limitation) managing video settings (such as tailoring the playback to your connection speed), storing video preferences, providing certain functionality such as allowing you to stop and restart a video without losing your place, showing you advertisements, associating your video viewing and other activity with your Google account (if any), ensuring proper functioning of the service, and/or compiling user analytics data. The cookies may be set by various domains, including (but not necessarily limited to) youtube.com, youtube-nocookie.com, googlevideo.com, ytimg.com, google.com, accounts.google.com, and/or doubleclick.net (which is part of the DoubleClick advertising service). Some are session cookies that expire when you close your browser; others may remain on your device as long as your browser settings permit. Some cookies Google sets in connection with your Google account and/or advertising served through YouTube (which may include others not listed here) are persistent cookies that may remain in your browser for as long as your individual browser settings permit. See Google's "Types of Cookies Used by Google" page for more information about the functions of their various cookies. To learn more about how Google uses the information they collect, see the Google Privacy Policy. (YouTube, Google Videos, and DoubleClick are trademarks of Google LLC. Google is a registered trademark of Google LLC.)

yt.innertube::nextId, yt.innertube::requests, yt-remote-cast-installed, yt-remote-connected-devices, yt-remote-device-id, yt-remote-fast-check-period, yt-remote-session-app, yt-remote-session-name, recently_watched_video_id_list, use_hotbox, demographics, GPS, LOGIN_INFO, PREF, VISITOR_INFO1_LIVE, YSC, AID, ANID, APISID, CONSENT, DSID, FLC, GAPS, IDE, NID, HSID, OTZ, SID, SNID, SIDCC, TAID, exchange_uid, 1P_JAR

Vimeo Videos

These third-party cookies may be set by Vimeo in connection with embedded videos, for purposes such as (without limitation) managing video settings, storing video preferences, providing certain functionality (such as allowing you to pause a video at a particular point), associating your video viewing and other activity with your Vimeo account (if you have one), showing you advertising, and/or compiling user analytics data. The cookies whose names begin with "_ga" and "_ut" are associated with Google Analytics (which is subject to the Google Privacy Policy); the ones whose names begin with "_ceg" are associated with the Crazy Egg web analytics service (which is subject to the Crazy Egg Privacy Policy); the ones that begin with "optimizely" are associated with the Optimizely digital experience optimization service (which is subject to the Optimizely Privacy Policy); and the ones beginning with "adsense" or listed in all caps are associated with Google AdSense and/or other Google advertising services (which are also subject to the Google Privacy Policy). The Vimeo Cookie Policy does not currently disclose the normal durations of their cookies, but some are persistent cookies that may remain in your browser for as long as your individual browser settings permit; some Google Analytics cookies can persist for up to two years. For more information about how Vimeo uses the information they collect, see the Vimeo Privacy Policy. (Vimeo is a trademark of Vimeo, Inc. AdSense and Google Analytics are trademarks of Google LLC; Google is a registered trademark of Google LLC. Crazy Egg is a trademark of Crazy Egg, Inc. Optimizely is a trademark of Optimizely, Inc., registered in the United States, EU, and elsewhere.)

_abexps, aka_debug, clips, continuous_play_v3, embed_preferences, has_logged_in, is_logged_in, jsessionID, player, search_click_position, Searchtoken, stats_end_date, stats_start_date, sst_aid, uid, v6f, vimeo, vuid, _ga, _gads, _utma, _utmb, _utmc, _utmv, _utmz,_ceg.s, _ceg.u, optimizelyBuckets, optimizelyEndUserId, optimizelySegments, adsense, adsenseReferralSourceId, adsenseReferralSubId, adsenseReferralUrl, adsenseReferralUrlQuery, S_adsense, APISID, GAPS, HSID, NID, N_T, PREF, SAPISID, SID, SNID, SSID

PayPal® Buttons

The payment or donation buttons that may appear on portions of the administrative dashboard (which is not normally accessible except to logged-in administrative users) contain embedded content served by PayPal®. Those buttons may set the third-party cookies PYPF (via paypalobjects.com), which appears to check whether or not you are a logged-in PayPal user and is probably used to facilitate the PayPal user login process, and/or 01A1 (via abmr.net), which stores certain technical information about your device and browser, probably to facilitate the login and shopping cart functions. The PYPF cookie normally expires in approximately four weeks, the 01A1 cookie in approximately one year.

If you use the buttons to make a payment or donation, PayPal sets additional cookies (not listed here) to manage your PayPal login and transaction data (and potentially also for various other purposes, such as user analytics and/or advertising). For more information on what data PayPal collects and what they do with it, visit their Legal Agreements for PayPal Services page to review the PayPal Privacy Statement and Statement on Cookies and Tracking Technologies that apply in your location. (PayPal is a registered trademark of PayPal, Inc. All button icons, custom graphics, logos, page headers, and scripts related to the PayPal services are service marks, trademarks, and/or trade dress of PayPal or PayPal's licensors.)

PYPF, 01A1

Administrative and Login Cookies

These functionality cookies are used to manage user logins and other WordPress administrative functions, such as post editing. If you are not an administrative user, they shouldn't normally be placed on your device at all unless you somehow access the login area, which is off-limits to non-administrators.

Accessing the login page places the wordpress_test_cookie (a session cookie that tests whether your browser will allow the cookies needed to log in and expires when you close your browser) and the itsec-hb-login-xx cookie (which expires after about one hour and helps protect the site against "brute force" attempts to hack user passwords).

Logging in sets the wordpress_logged_in_xx, wordpress_sec_xx, and/or wordpress_xx cookies, which store your user login credentials to allow access to the administrative dashboard and other administrative functions; these cookies expire in about 15 days if you click "Remember Me" when logging in, but if you don't, they normally expire when you close your browser (or, failing that, within about two days). The wp-settings-UID cookies store a logged-in user's configuration settings, while the wp-settings-time-UID cookies store the time those configuration settings were set; these cookies normally expire after about one year. One or more wp-saving-post cookies may be placed while creating and/or editing posts or pages, to help manage version control and the autosave feature; these cookies normally expire after about 24 hours. The wp-donottrack_feed cookie, which controls a blog feed, may be set by accessing the dashboard menu for the WP DoNotTrack plugin (if I currently have that plugin enabled); this cookie normally expires in about one year.

For all of these administrative and login cookies, the "xx" will be a cryptographic hash while "UID" will be the administrative user's user ID number in this website's WordPress database. (WordPress is a registered trademark of the WordPress Foundation.)

wordpress_test_cookie, itsec-hb-login-xx, wordpress_sec_xx, wordpress_logged_in_xx, wordpress_xx, wp-settings-UID, wp-settings-time-UID, wp-saving-post, wp-donottrack_feed

Change Font Size
Contrast Mode (Note: This option sets cookies to save your settings)