The Heroine’s Journey I (Remnant Population)

Remnant Population
Elizabeth Moon; Del Rey 2003


Courtesy of the Heroine’s Journey thread over at Tor.com, about which I’ll say more once I’ve dug myself out from underneath Bayesian analysis, counterfactual models, causality, directed acyclic graphs, fractional polynomials, splines, and simulation of datasets … I’ve been rereading Elizabeth Moon’s Remnant Population. There aren’t many protagonists in SF like Ofelia, whom the Scots (and we should know) would describe as a cussed auld besom. She’s nearly eighty, one of the oldest inhabitants of a human colony thwarted in its development by repeated disasters; of Ofelia’s several children, only one son, Barto, has survived into middle age. The colony has endured but not grown or progressed; education is purely vocational and individual talent and aspiration suppressed. The social order is narrow: Ofelia’s community impresses on her her dependency and diminishing worth as an old woman, and Ofelia in turn passes silent judgment on disruptive, sexually promiscuous women like her neighbour Linda and childless women like her daughter-in-law Rosara.

But within the first pages of the novel the colonists learn that their colony has been judged a failure and is to be abandoned by its corporate sponsor. Within a month, the colonists will depart for another planet, decades away, leaving the work of forty years behind them. As a further imposition, the sponsors are refusing to pay for Ofelia’s passage, charging it to her son and daughter-in-law.

Enough, Ofelia decides. When the time comes, she will walk into the forest with enough food for a few days, and wait until she is certain the last shuttle is gone. The company representatives will not trouble themselves to look for one woman too old to work. She will live the rest of her life alone, and for the first time in her life she’ll have nobody around to tell her what to do and who to be.

And she does. Once she has restored power to the deserted colony and established a routine of gardening and foraging, she has everything she needs. She gets up to mischief. She pokes into other women’s cupboards. She sleeps in other people’s beds. She sheds the drab clothing of elderly respectability and dresses in gaudy colours, walks naked in the streets, weaves herself a cape of netting and beads, daubs her body with paints. She annotates the colony’s official log with the stories of sexual strife and violence that lie behind single line entries of moves between households or ‘accidental’ deaths. The narrow inner voice of social censure is gradually silenced by a new voice. (These acts of throwing off social convention, that argument between the inner voice of social censure and the new voice of true experience turns up in other womens’ novels, too. Top of my mind is Joan Barfoot’s Abra, a mainstream novel of a woman who also chooses solitude and self-sufficiency, but on this earth.)

But she does not remain alone. Months later, the colonists’ successors arrive. Disdaining the site of her failed colony, the new settlers set down elsewhere on the planet—and Ofelia, silently listening over the radio, hears their unanswered pleas for help as they are slaughtered to the last man, woman and child by aliens that no one knew were there. Ofelia’s initial intense fear, loneliness and vulnerability are gradually easing with the familiarity of her surroundings and routine when, in the middle of one of the planet’s violent storms, she comes face to face with a small wandering band of the aliens. The recognition that one of them is injured, and exasperation at seeing anyone or anything too foolish to come out of the rain, pre-empts fear, and she throws open her door.

They spend an uncomfortable night huddled together in the dark, and each party (the aliens’ collective voices are represented in brief interpolated passages) emerges gratified to find themselves unharmed by the other. Ofelia would be quite happy to go back to her solitary life, but the aliens are social and curious, and Ofelia finds herself shooing them out of the kitchen and out of the colony control room and power-plant, convinced they’ll do themselves harm, and pushing towels and mops into their hands when they track mud and water across her floor. Children, she thinks, having reached the age where everyone looks like children, and exasperated all over again at losing her precious solitude. But she demonstrates how light-switches work, and how domestic appliances work, and struggles—despite her own truncated education—to explain how electricity is generated. She makes music with them. She dances with them. An elder, a nest-guardian, the People decide in their turn, and summon one of their senior singers, a diplomat, to treat with her as a representative of her people. And, half-understanding, she finds herself appointed as guardian to the newborn babies of one of the band.

One of the marvelous aspects of this novel is that the important events happen in Ofelia’s old age. Many novels with an old person as protagonist (eg, Margaret Lawrence’s The Stone Angel, itself a groundbreaking book) take place as much in the novel past as the novel present, and youth’s adventures and dramas pre-empt attention. Age seldom gets all the adventure all to itself, as it does here. Despite the arrival of a team of experts, all shiny, knowledgeable, and oblivious to their own human foibles (Children, thinks Ofelia), Ofelia—old, ill-educated, eccentrically clad, and cussed—and the alien diplomat whom she calls Bluecloak, succeed in making the human representatives recognize the outrage that provoked the massacre, and establish the terms for colonization of the planet in full partnership with the People.

Feeding Zotero

Zotero is where I keep an eclectic library of background to works in progress, works in incubation, and topics of interest. Zotero 2.0, which is still in beta, allows registered users to synchronize citations between computers and a page on the Zotero server itself. The citations are stored as a library with collections in subfolders, with feeds available at both levels, and can be made public. I liked the idea of pulling feeds from my collections into relevant pages, like my Women scientists in fiction page. It’s a work in progress, but figured I’d make notes before I forgot the convolutions and the useful links found along the way.

Currently there is no option to sync or make public just part of a library. That’s coming, but at the moment it is all or nothing. It is possible, using a Zotero-generated API key, to access a feed from an individual collection (folder) within a private library, but (naturally) click-through is not allowed so the full citation is not accessible. The Lifestream plugin gave a certificate error, when I attempted to add the Zotero feed as a generic blog, but the ZoteroFeedWidgit worked handily out of the box, installing a compact  Zotero feed in the sidebar. It’s not there now; in the sidebar was not where I wanted it, but it is an option for those wishing a sidebar feed. There’s an attached CSS file which grants the user some latitude in styling. The recommended syntax for calling the feed is:

http://feedaddress/top?key=APIkey

To get the feed address, bring up the page of the individual collection (ie, folder or subfolder). At the bottom of the page, there is a standard RSS symbol with a link to subscribe to this feed. Right click and copy the link; it will be different for each collection.

An offered workaround was to create a separate public collection with a separate registration. To enable me to use both my larger private collection and smaller public collection simultaneously, I have the first in Firefox and the second in Flock – otherwise I would have to relaunch Firefox to switch collections. The feed from the public collection (no https) works in Lifestream (in fact, it has taken over my Lifestream for the moment, with a great bolus of migrated articles). Still no in-page feeds, which will require use of a plugin that enables the execution of php in a page. So as I said, a work in progress. I might look at a more generic means of mashing together a Delicious feed and a Zotero feed – the first is very useful for links, the second obligatory for properly formed citations.

For more discussion on Zotero feeds and websites, there’s this thread on the forum.

TiddlyWiki: a demonstration

I expressed my enthusiasm for TiddlyWikis in general terms in a previous post, since I find them mindbogglingly useful (to borrow a phrase) for keeping running notes on just about any topic. As I set up a TiddlyWiki to capture notes for a course project, it occurred to me that I might contribute a step by step description of how I go about customizing a new Tiddlywiki.

First step is to download an empty TiddlyWiki from http://www.tiddlywiki.com, courtesy of a large, friendly, blue button. That places a file called empty.html on my Desktop, so the next step is to rename it to something appropriate.

Then I open the page in Firefox, remembering to permit Javascript. The default view shows a GettingStarted tiddler front and centre, which invites the user to set the SiteTitle and SiteSubtitle (which should be self-explanatory), and stipulate the tiddlers to appear on the MainMenu and DefaultTiddlers (which are opened when the site is launched). Click on the images to show at full size.

Before I modify any content, I select options in the sidebar, opening up the options submenu. I enter the name I wish to use to sign my edits, uncheck SaveBackups and check AutoSave. The browser will issue a warning if one attempts to navigate away from unsaved changes, but I prefer to have my changes saved automatically rather than risk a distracted click on the wrong button. SaveBackups tends to generate a confusing bunch of files, although there is the option to put these in a separate subdirectory from the main file, which might be useful, and is accessed through AdvancedOptions. Changes to options are saved in the form of a cookie, so will reset to default when cookies are deleted.

Back under GettingStarted, I click SiteTitle to open that tiddler, click edit (beside the title) and enter “Demo Tiddlywiki”. A similar edit to SiteSubtitle changes that to “making tiddlywiki show its stuff”. The other two I leave, since I have some more customization to do.

Modifying the appearance: adding a template

The style is a default, and I have a couple of styles I prefer, so in a separate tab in Firefox I browse over to to TiddlyThemes and call up the Haemoglobin template. Built in to default TiddlyWiki is the ImportTiddlers plugin, accessed either through the list of Shadowed Tiddlers under the More tab on the right sidebar, or under the Import menu in the backstage toolbar. The backstage toolbar is accessed by clicking on backstage, which either appears in the extreme upper right hand corner of the TiddlyWiki page, or which can be made to appear by moving the mouse over that spot. Enter the URL for the desired template in the box provided, select the desired tiddlers – in this case HaemoSideBarOptions, PageLayout, contentFooter, and StyleSheet.

If ImportTiddlers does not work, I cut and past the contents of these Tiddlers from source into my new TiddlyWiki. It may be important to do so in a certain order: for the Haemoglobin style, the side bar should be added before the page layout, or the link to create new tiddlers disappears. The new page layout places the contents of the MainMenu in the coloured strip across the top.

Adding functionality through plugins: addition of the tagCloud plugin

I find a tag cloud a compact and effective index, and use the tagCloud plugin, available from TiddlyTools, to generate a tag cloud. Using ImportTiddlers, or manually, I load or copy the plugin over to my new tiddlywiki. Manual loading involves copying and pasting the code from TiddlyTools into a new tiddler in my tiddlywiki named (exactly) tagCloud and tagged as (exactly) systemConfig. The tag systemConfig is required for Tiddlywiki to recognize the plugin.

I then create an tiddler for the tag cloud itself called Topics (Tag cloud) (or some variant of) and containing the call to the tagCloud plugin, <<tagCloud systemConfig>>. The error that appears disappears on page reload.

Then I add the tag cloud tiddler to the DefaultTiddlers and MainMenu, using [[Topics (Tag cloud)]], the double square bracket being needed to that the Tiddlywiki code will recognize the two words as a cross reference. Now the tag cloud appears front and centre on loading, and a link to it appears in the main menu, which in the restyled Tiddlywiki runs right to left.

Creating new content

To illustrate the creation of a tiddler, here is the open edit box for one called What’s this?, showing the markup required to create an external link, in this case to Wikipedia. Making a new entry involves clicking new tiddler, on the upper right sidebar and, presented with the editing panel, entering a unique entry title, the text and the tags to go with the text. In the body of the entry, anything that in the form of WikiWords or enclosed in [[double square brackets]] is treated as a link to a current or potential entry (current entries are bold, nonexistant entries are italic). The escape character, to avoid unwanted link creation, is ~, eg, ~TiddlyWiki will not create a link. In the tag box, any single word or phrase in double square brackets, is used as a tag. More information about Tiddlywiki markup, including links and images, is found at TiddlyWiki for the rest of us.

The styled Tiddlywiki, with default tiddlers What’s this? and Topics (Tag cloud), is here:

In recent versions of TiddlyWiki, the styling is controlled entirely from the StyleSheet, which is a great improvement on having it scattered over several tiddlers. The stylesheet itself is CSS, and can be edited for further customization.

Curating

Keeping a tidy TiddlyWiki requires some decisions about preferred terminology, best made prospectively or at least early, and attention to detail. It is case sensitive, so if the title of a tiddler starts with a capital, then all references to that tiddler need to start with a capital. Should nouns in tags be singular, plural, or mixed, eg, article(s)? Tag-variants and non-existant tiddlers tend to proliferate. A list of all tiddlers appears by date of last edit under Timeline on the lower right hand menu and alphabetically under All. Nonexistent tiddlers, ie, those referenced but not defined, appear under More > Missing; this list can be used to hunt down tiddlers spawned by a mis-spelling. Previously used tags appear under the Tags tab, or in the tag cloud. The tag cloud updates when the wiki is reloaded or the tiddler is closed and reopened. Size of the font indicates the frequency of use. Click on a tag, and a drop-down list shows which tiddlers it applies to; this, too, can be used to hunt down tag variants and bring them in line.

I keep a collection of definitions, reviews and useful sites on my Tiddlywiki Backpack page. For some elegant implementations, see: see the Tiddlyspot gallery, and Tiddlywiki in Action.

A few of my favourite tools: Wine

Wine (named in recursive fashion “Wine is not an emulator”) is used to run Windows applications on Linux; essentially, it interprets Windows commands for Linux and vice versa. I first met Wine in the form of Darwine (the “Dar” being for the underlying Darwin windowing technology in OSX), ported and maintained by Mike Kroneberg, and described at Low End Mac in an article by Alan Zisman. An alternative approach to installing wine, which I have not explored, is to install Wine via MacPorts.

The utility of Wine is that it does not require one to partition the hard drive, reboot, or to own and run any version of Windows. I have a full installation of Windows Vista Pro running on Parallels, but for certain lightweight, self-contained programs, I can launch Darwine and be running in a quarter of the time it takes for Parallels and then Vista to lumber into motion. WinBUGS, which I’ve been learning for Bayesian analysis, runs quite happily on Darwine, although I had to install by downloading and unpacking a zip file (per instructions for Vista or 64 bit systems), as the installer itself gave an error. After that, about the only tricky part was figuring out the file structure of the pseudo-C drive and how to access the files on the Mac, since they’re in an invisible folder. FirstBayes (Bayesian learning software) did not run, even after I figured out how to do the required registry hack, but then FirstBayes didn’t care much for Vista, either. Notepad++ runs without any trouble, as does Plant Studio (an old Windows program for building 3D plant models). Here is the official application database, rather games-heavy.

Darwine is no longer being developed, but its successor, now named Wine, is still in development. As my copy of Darwine survived beyond the Snow Leopard Event Horizon and still does what I need it to do, I will upgrade later.

A few of my favourite tools: Tiddlywiki

This started as part of my earlier post on DokuWiki and MAMP, and then grew to demand a separate entry. Tiddlywiki, a demonstration of über-Javascripting, goes places other wikis cannot. It is a completely self-contained, platform- and server-independent wiki, capable of being run from any rewritable media and on any system that supports a modern browser. Everything, script, entries and plug-ins, is included within a single .html file; installation consists of downloading the empty file, setting a couple of options (name and saving), and starting to edit.

Why? Because I as I said before, I like wikis, I work cross-platform, and I find I work best by separating out my projects. So, one Tiddlywiki per project. To date I have run Tiddlywikis on all three major operating systems, though using Firefox by preference as a browser.

A series of articles by Mark Gibbs at Network World (Jan – Feb 2009) covers the basics. Some of his readers express reservations about the quality of the documentation, but it occurs to me that that in part may be because much of the documentation appears in Tiddlywiki form (see, for example, tiddlywiki.com). A potential user coming to it without previous experience may need a few moments to decipher the conventions of the interface (in a traditional tiddlywiki, look to the right hand menu for actions and lists of previous entries), as well as come to terms with the jargon (although, in 2009, “tiddler” cannot seem any more whimsical than “tweet”).  Tiddlywiki for the rest of us provides a more conventional presentation of the basics, and tiddlywiki.org‘s documentation is built on a MediaWiki engine. Admittedly there are aspects, like the styling, that are intricate beyond simple documentation. I have reached the point that I can tinker with other peoples’ styles, but have not progressed beyond that; fortunately, there are a couple of styles I quite like.

My uses are admittedly rather bland: keeping ongoing research notes on emerging treatments in a disease area, keeping bibliographies, keeping a off-line, but still portable list of resources for my medical/regulatory writing activity, keeping a concordance for a loose series of short stories. Other people are much more adventurous, using tiddlywikis for home, education and commercial websites, presentations, weblogs, course notes, course materials, bibliographies, and developing and presenting scholarly papers – see the Tiddlyspot gallery, and Tiddlywiki in Action. As tiddlywiki is open source, developers have produced a number of variants, including a popular one one that incorporates the tasks-projects-place structure of Dave Allen’s Getting Things Done (GTD) strategy, complete with checkable to-do lists; I’ve flirted with this, but have always returned to Backpack.

My own collection of Tiddlywiki Resources page is here, on Backpack. I started it after I spent far too long hunting around for a site that contained a plug-in I knew I’d seen in passing and wanted to include. My page on Tiddlyspot (a service for hosting Tiddlywikis online, worth an entry in itself), on the German Imperial Navy, shows a number of my favourite modifications, including restyling to the Blueberry template (from Tiddlythemes) and the addition of a tag cloud.