More from Minnesota

Another day in Minneapolis. Gwen and I started off by walking around Lake Phelan, just down the road from our hosts. Very pleasant, with a pair of trails for running and bike riding, both of which were getting plenty of use. The powers that be trucked in some sand and created a beach at one spot on the lake that nobody was using–but there were buoys marking off a swimming area too tiny for anything beyond a little splashing around.

After that, we drove into Minneapolis again to visit the Walker Museum. The first thing that caught my eye was something outside that I had read about before, the Mobile Dwelling Unit by Lot Ek. This is a 40-foot shipping container that has been converted to a living space, with almost all of one wall, and much of the opposite, converted into slide-out units, each for a specific function–toilet, shower, kitchen, bed, storage, TV viewing, dining–so when deployed, the center area is empty. The concept is quite clever. The thing itself seems incomplete–most of the interior was unfinished plywood, with pencil marks showing cut-lines and the like; the soft surfaces were raw foam. Curiously, surveillance cameras were everywhere inside, even though there’s nothing to obstruct your view from one end to the other (and, well, who puts surveillance cameras in their home?). A museum staffer explained that the idea was that the cameras would be on the outside in a real MDU. Apart from the unfinished quality, I have more serious criticisms of the MDU: it has poor connections to the outdoors, with very limited window exposure, none of which open, and only one door to only connect to the outside. My guess is that it has no insulation to speak of, and only a window-unit air conditioner, so it could become intolerably hot in a hot climate. But it’s still a very nifty concept.

After taking in the MDU, we wandered around the nearby sculpture and botanical gardens (which were fodder for my camera–I will upload pictures when I get back). The weather was especially nice, and I think none of us were in hurry to go indoors. Eventually we did. The current exhibit–of which the MDU is a part–is of cutting-edge industrual and architectural design. Some of this was high-concept wankery, like the chair that responds to electromagnetic radiation to make you conscious of the high-tech world we live in. Some of it was self-mocking, like bottles that look broken. Some of it was mind-boggling, like a presentation for “pig city”–a self-contained pig-farming skyscraper that’s designed for maximum efficiency. One of Shigeru Ban’s cardboard-tube emergency shelters (used to house victims of the Kobe Earthquake) was on display, and I was glad to have a chance to walk around in that.

The permanent exhibit at the Walker pretty much left me cold–navel-gazing modern art. Everyday objects presented as art. When Marcel Duschamp did it, it was a clever gag, but you can only get away with that once–you can’t build an entire movement out of it.

After we finished with the Walker, we fortified ourselves with coffee and snacks, dropped in on an old friend of Gwen’s, and then went to the home of the parents of my friend Jen, who just happens to be visiting the ancestral abode at the same time we’re up here. We all had a chance to catch up, her mom overfed us and guilt-tripped us about not eating enough (you’d think she was Jewish, but she’s Chinese), and we generally had an excellent time talking about disturbing movies and feral Chihuahuas.

Modems suck

Just something that travelling has forced me to re-learn. I haven’t used a modem regularly since 1997. I’m accustomed to an Internet connection being like water. It’s not the same.

Greetings from Minnesota

Gwen and I have begun a trip to Chicago and Minnesota. Two days ago, we flew to Chicago, met my parents (who were setting up for an antique show), borrowed my dad’s truck, a ’91 Ford, and lit out on I-90 for St. Paul.

I think my father has a predilection for vehicles that have loose front ends. This truck was also loud and primitive–possibly one of the last pickups that was built primarily for hauling loads, rather than for personal transport. Also very loud, and hard on gas–a fill-up cost $47. Cheaper than flying, though. Getting onto the interstate was stymied by construction, and we wound up going quite a bit out of our way before we actually found an on-ramp. Driving through Illinois, we encountered a frustrating pattern where we’d be backed up with road construction, get to a toll booth, and for about one mile after, the road would be clear. Then it would be down to one lane, more construction, and another tollbooth. Repeat until the Wisconsin border. After that, it was pretty much smooth sailing.

We reached St. Paul while there was still light and navigated with little trouble to the home of an old friend of Gwen’s, where we are staying.

Yesterday morning, we were up at a relatively early (for a vacation) hour to go kayaking, which I’ve never done before. We were right on the Minnesota-Wisconsin border. An outfitter dropped us off at an upstream point, we paddled along for about 4 hours (with a few stops for snacks and sunblock on the way), and we got picked up near the outfitter’s storefront at the end. It was fun, though my enjoyment would have been greater if it weren’t for a comparatively mild migraine. We saw at least six bald eagles close-up–I’m pretty sure that was the first time I’ve seen them in the wild in the USA.

Today we drove into Minneapolis and wandered around Gwen’s old haunts. Her old neighborhood is an awful lot like my old neighborhood in Chicago–I felt right at home. We also spent some time downtown, looking at nifty old Art Deco buildings and walking through the human habitrail system. Tomorrow we’ll be getting together with a friend of mine, Jen, who lives in Philadelphia but was raised here–it just so happens that she’s visiting at the same time we are.

Revised firedancing equipment recipes

I got into the whole sideline of making firedancing equipment because of my How to make firedancing apparatus webpage. People found the page, and offered to pay me to make the stuff for them. Reversing the normal order of things, I started making the equipment quasi-commercially about six months before I actually started using it.

Anyhow, that page is pretty musty and ugly. I had it in my mind that this might be a good (though untraditional) application of Movable Type, and so I started hacking something together, photographing my production process, etc. Yesterday, I got something usable posted. So far I’ve only documented the recipe for wicks, but more will come. Once I flesh out those pages a little more, I’ll be taking down the old page.

Speedy service

I posted a lazyweb request concerning the creation of foaf files a couple days ago. One of the guys who appears to be the prime movers in the world of foaf, Jim Ley, whipped together a little converter that takes tabbed data and spits out the “knows” portion of a foaf file. You’ll probably want to use the foafamatic to create a shell foaf file with your own data and maybe one friend , then export your contact data from whatever dark cave you store it in into tabular form and run it through Jim’s widget, and finally merge the two. A little clunky, yes, but a big improvement over what we had before.

Once your done, check out your handiwork in the foaf explorer.

Just water

At Chango’s, if you want just water to drink, that’s just what you’ll get.

Lazyweb: a better foaf-file maker

Making good FOAF files is a pain. There’s the foaf-a-matic web page, that lets you type stuff in and formats it for you, but who wants to re-type all that data? There’s a Java-based successor, but that’s overkill, and still doesn’t have any way to import data, as far as I can tell.

Thanks to Address Book Exporter, it’s easy for me to extract data from my address book in a tabular form. I suspect that most people interested in using FOAF probably already have their data typed in somewhere, and would be able to extract it in this form if needed. From there, it would be pretty easy to use GREP to mark up the file into a usable FOAF file, except for the sha1 e-mail address encoding (which is not required, but is the responsible thing to do). And not everyone would be comfortable writing a GREP pattern, for that matter.

What we need is a little web utility that ingests tab-delimited text files and spits out FOAF files. I know it can be done–it’s just out of my reach.

Spam in my name and challenge-response

I recently discovered that some spam was being sent with my address as the return address–the bounces were coming to me.

Other than pissing me off, I wasn’t sure what those smegma-sucking spamming scumbags hoped to accomplish by doing this. Now I have an idea: it may be to undermine challenge-response spam-blocking systems.

These challenge-response systems are a klunky way of dealing with spam: if Alice sends Bob an e-mail, and she’s not on Bob’s whitelist, the system sends Alice an automated response asking her to visit a web page and prove that she’s a real human being worthy of Bob’s valuable attention. This usually involves looking at a graphic showing distorted text, and typing the text into a box.

Even if this all works according to plan (and there are plenty of reasons why it might not), it’s very annoying. But as soon as spammers start sending out e-mail purporting to come from real people, it really goes to hell:

  • If I am already whitelisted with a C/R service, the spam gets a free pass.
  • If I am not already whitelisted with a C/R service, the challenge comes to me. Maybe I’ll respond correctly, in which case the spam gets a free pass
  • Or maybe I won’t respond, or (acting mischievously or perversely) respond incorrectly, in which case the spam is blocked, but so is any e-mail I might want to send to any person using that system in the future.

Correct run-in headings

I’ve recently noticed a couple of blogs that use an awkward “span” kludge to create “run-in” headings. These are both by smart guys who should know better. Instead of using structurally correct headings and paragraphs, the heading text is part of the paragraph, and is just bracketed with SPAN tags so that it can be styled differently.

CSS-2 does include a “run-in” display style that achieves exactly what these guys want, but it is not universally supported. There are a couple of possible workarounds, both of which I’ve documented. One is to float the header; the other is to style the header and the paragraph immediately following as “inline.”

Scroll to Top