Categories
Just Shelley

The long way home

Recovered from the Wayback Machine.

Before weblogging and RSS—long before Facebook, Twitter, or the next poor bastard service, doomed to be worshiped and then sacrificed on some given Friday—I used to write long essays I’d publish online by hand editing the HTML and posting the static files. Having to manually create the HTML template and design, incorporate navigation, and craft the links and images, took a considerable amount of time.

To justify the time, I wanted to make sure that what I published was worth the effort. I would research a story and edit and re-edit it, and look for additional resources, and then re-edit the story again. My one essay on the giant squid actually took two months to research, and days, not minutes, to edit. Even after publication, I would tweak the pages as old links died, or to refine a section of the writing.

Now, we have wonderful tools to make it easy to put writing or other content online. We can think of a topic, create a writing about it, and publish it—all in five or less minutes. We’ve also come to expect that whatever is published is read as quickly. We’ve moved from multi-page writings, to a single page, to a few paragraphs, to 140 characters or less. Though there is something to be said for brevity, and it takes a true master to create a mental image that can stand alone in 140 characters or less, there still is a place for longer writings. We don’t have to be in a continuous state of noise; a race to create and to consume.

Other than a few posts, such as this, all writings at Just Shelley will be spread across pages, not paragraphs, or characters. Such length will, naturally, require a commitment of your time in addition to your interest. However, I can’t guarantee that your time will be well spent, or even that your interest will be held (though the former will, naturally, be dependent on the latter). All I can guarantee is that I probably took longer to create the writing than you will in reading it.

I am using a tool to publish, true, and even providing an Atom feed. There are no categories, tags, or taxonomies, though, because everything here fits under one bucket: it is something that interests me. Taxonomies would just clutter the site’s zen-like structure, as well as set expectations I’m almost certainly not going to fulfill.

To further add to my state of web regression, I’ve not enabled comments, though I’d love to hear from you through some other means. As anachronistic as it may seem nowadays, this is not a site that’s community built. It’s not that I don’t care about you or community, or that I’m asking you to be a passive observer. My hope is that if I don’t inspire you—to talk, to write, to howl at the moon— I make you think; if I don’t make you think, I provide comfort; if I don’t comfort, I entertain; if I don’t entertain, at a minimum, I hope I’ve kept you in the house long enough not to be hit on one of those rare occasions when a meteorite falls from space and lands in front of your home just as you were leaving.

Just Shelley is my place to be still, and my invitation for you to be still with me.

Categories
Just Shelley

The stories this week: Levee fails, Anheuser-Busch says no, Burke is gone

Recovered from the Wayback Machine.

second update Unfortunately the Hesco barrier erected by the National Guard failed. Though I admire the tenacity of the Guard, I’m not surprised the barriers failed.

Winfield is now, more or less, cut off, and many homes will, unfortunately, be damaged. How many, no one knows for sure at this time. The town gave it their all, but the Mississippi is one big river.


update This NECN in Boston shows how fast the water flows through a levee break, and how widespread the flooding is now. The National Guard is disheartened by the break, as they worked on the levee for nine days. This levee was also the destination for the sand bags I helped fill.

The flood crest has been raised at St. Louis, and there’s a possibility of flooding south of Lemay Ferry Road from River Des Peres. This is the drainage river that runs through St. Louis, and is also the waterway that puts us most at risk during a flood. However, the Mississippi would have to crest about 13 feet higher to put us at risk.

We will have to rethink how we manage our waterways in the future. We can’t keep putting our fingers in the dike, and hoping for the best.


The last levee in Lincoln County still holding back the water breached this morning. I don’t think anyone was surprised when a sand boil, a mix of water and sand, appeared in the side, signaling that water was undercutting the foundation of the levee. The folks in Winfield and surrounding areas made a mighty effort to save the levee, but it was not enough.

The waters should be cresting this weekend, though we have more rain in both the Mississippi’s upper river basin, and along the Missouri river basin. Whether this means the flooding will continue hasn’t yet been determined.

Another major event impacting on St. Louis is the InBev offer for our local, beloved Anheuser-Busch. A-B, the largest beer company in the US, has remained in control by family members to this day, and has been an important St. Louis and Missouri business. A-B is very generous to the community; many members of the family are very active environmentalists; from all accounts the company is a good employer— well, needless to say, no one wants InBev to buy the company but greedy, rapacious stock holders.

We’ve already had warnings from employees in other countries where InBev has made acquisitions, and left a swath of destruction in its path. By all accounts, InBev is only interested in profits and power, not a legacy.

This week, A-B turned down the offer, and InBev has already made the opening move of a hostile take over. Hopefully the A-B people can hold their own, but this war will leave this community scarred. The only way that A-B might be able to hold off the bid is by decreasing costs and increasing profits, both of which could mean the end of our gentle neighbor, regardless of who owns the company. I would wish InBev in Missouri…right in the middle of the Mississippi river.

Lastly, St. Louis’ Archbishop Burke is leaving for a position in Rome. Burke’s four year tenure here has been marked by disruption and antagonism, as Burke trounced Catholic presidential candidate Kerry for supporting choice with abortion, excommunicated the members of the St. Stanislaus Kostka, just because the church members wanted to control their own property, and condemned one of the local rabbis for opening her arms to women wanting to be ordained as Catholic priests. Burke has also skirted perilously close to crossing the line in allowable political activity, going just far enough to try to influence local and national elections, but without endangering the church tax exempt status.

I am not surprised at Burke’s appointment to Rome, and wrote not long ago that he had ambitions beyond St. Louis. I am, also, not disappointed at Burke’s leaving, though whether the man appointed in his place will be any better for the community is hard to say.

Categories
Semantics Writing

RDF too

Congratulations to the RDFa folks for rolling out a release candidate of RDFa for XHTML. Now that I’ve finished tweaking site designs, my next step is to see about incorporating smarts into my pages, including the use of RDFa. In addition, I also want to incorporate the RDF Drupal modules more closely into the overall functionality. The SPARQL module still seems broken, but the underlying RDF modules seem to be working now.

The RDFa release candidate is timely, as I gather the BBC has decided to forgo microformats in favor of RDFa. This has re-awakened the “microformats vs. RDFa” beast, which we thought we had lulled to sleep. I guess we need to switch lullabies.

Speaking of lullabies, I had hoped to start work on the second edition of Practical RDF later this year, but it is not to be. The powers-that-be at O’Reilly aren’t comfortable with a second edition and have accepted another book proposal that covers some of what I would have covered in order to make the book livelier. There just isn’t the room for both.

I am disappointed. The first version of “Practical RDF” was difficult because the specification was undergoing change, the semantic web wasn’t generating a lot of interest, and there weren’t that many RDF-based applications available. Now, the specs are mature, we have new additions such as RDFa, increased interest in semantics, and too many applications to fit into one book. I feel as if I started a job, and now won’t be able to finish it.

One issue in the book decision is the “cool” factor. RDF and associated specifications and technologies aren’t “cool”, in that people don’t sit around at one camp or another getting hot and bothered talking about how “RDF is going to change the world!” However, the topic doesn’t necessarily have to be “cool” if the author is “cool”, and I’m not. I don’t Twit-Face-Space-Friend-Camp-Chat-Speak-Shmooze. What I do is sit here quietly in my little corner of waterlogged Missouri, try out new things, and write about them. That’s not really cool, and two not-cools do not make a hot book.

I don’t regret my choice of lifestyle, and not being “cool”. I do regret, though, leaving the “Practical RDF” job undone. Perhaps I’ll do something online with PDFs or Kindle or some such thing.

Categories
Burningbird

Editing with ecto

My last few posts at my various sites have been created using the ecto Mac-based web publishing tool. I’m still working out the kinks, not the least of which I do my own HTML, when most of the world seems to be WYSIWYG by default.

What I like about ecto is that I can create accounts for all of my Drupal installation, and control all aspects of the publication. The only type of post that seems to be a problem is creating a new image, using the images module. The ecto application persists in telling me that I have to add an image before publication, and this after adding an image.

The other popular Mac-based editing tool, MarsEdit, seemed to have problems just connecting with Drupal and doesn’t, as far as I’ve seen, seem to be able to handle multiple Drupal accounts. Besides, ecto was cheaper.

Categories
Burningbird

Still living, still breathing

Though I detailed my move from WordPress to Drupal in Live, on Drupal, I wanted to provide a short summary of the changes made at all of my sites.

I’ve implemented the three phase 1 sites, Painting the Web, RealTech, and my personal site, Just Shelley using Drupal. The main Burningbird feed will list entries from all of the sites, while the Tech Only feed is for the tech-only sites (if you don’t want to deal with all that oogie personal stuff). You can, of course, just subscribe to the individual sites, or even individual categories.

The main main Burningbird page is now a portal, maintained by the aggregator software Venus, listing all of the entries from all of my sites. It’s the only page that’s using SVG as part of the theme, though I probably will end up changing the design, eventually. I also need to add links for my books, especially the newest, Painting the Web which was released to the streets in May.

I’ve only enabled comments here at RealTech, and only within the newly created Burningbird forum. All of the sites, except for Just Shelley, have their own forum category, and several forum topics. Using this approach, I can aggregate all discussions in one spot, while preventing some of the problems I had with XHTML and comments in WordPress.

You don’t have to register to comment. If you do register, and you’re someone I know, I’ll assign you “trusted” user status and you’ll be able to create your own forum topics, in addition to the ones I create. You can also use OpenID to register for the forums.

My RealTech site design is pretty conservative, and is based on the Drupal Garland theme. Painting the Web and Just Shelley are quite different in that neither site has sidebars, both use vertical images placed to the left, fixed in the case of Just Shelley. I just got tired of header images and multiple columns, and wanted to try something new.

I’ve given my Browser Shots membership a real work out, and all of my sites should show up in all of my tested browsers: Firefox 2.x/3/x, Opera 9.x, Safari 3.x, IE 6 and up, as well as several others. Do provide feedback, especially if you run into browser specific problems. At a minimum, I provide print only pages, which strip out all markup, if you run into problems.

Enjoy.