Archive for the ‘Geekery’ Category

Contemplating the Open Source Auto

Monday, January 25th, 2010

Cast your imagination ahead 25 years.  It’ll be 2035 (and I’ll be 58; eek!), and my 2006 MINI will be 29 years old, or about as old as the first BMW E30s are today.  My 2000 SV650 will be 35 years old, my first car—a 1987 Pontiac Grand Am—will be 48.  Many car and motorcycle enthusiasts like myself will be scouring barns and fields for the cars of their youth, looking to reclaim a long-forgotten vehicle as a project, something from a “simpler time”, even though there’s nothing simple about a modern vehicle.

Forget for the moment whether these are “good” cars (or bikes), because that’s not really the point; who, in 1967, thought the 1957 Chevy Bel Air would be the much sought-after classic that it is today?  And what does “good” mean when you’re looking back a quarter of a century?  Instead, think about trying to get one of these electronics-laden, black-box-riddled, emissions-control-saddled, proprietary, indecipherable vehicles running and drivable on the roads of tomorrow.  Assuming you can still get 91 octane unleaded and roads are paved in the future (where we’re going, we don’t need roads!), how about passing emissions?  If the laws are similar to today, you’ll need the emissions equipment working the way it worked when the car came off the assembly line, assuming regulations haven’t tightened to the point that even “antique” cars need to comply with present-in-the-future-day requirements.  What about repairing or finding a replacement for the engine computer, or the climate control computer, or the ABS module?  The manufacturers sure aren’t providing schematics, programming references, or the source code,  even to their own factory-trained mechanics, opting instead to provide “if subsystem A exhibits fault B, then replace component C”.  Will you be able to find component C in a junkyard, or will there be a dealer network in place that has stock of component C?  What if you’ve got a rare car and the manufacturer went bankrupt?  Or even a mass-produced car and the manufacturer went bankrupt?  (I’m looking at you Chrysler; we’ll be lucky to see you in 3 years, let alone 25.)  Will a Ferrari F430 be anything more than a large decoration because the manettino no longer responds?

These kinds of problems present themselves today, even on cars that nobody would begin to think of as “rare”, actively supported by the manufacturer and their dealer network.  The early first-gen (BMW-owned) MINIs with the factory CD-based navigation basically have a pretty (although that’s open to interpretation) yet useless screen in the middle of the dash because the maps are out of date and won’t be upgraded because BMW is only updating the DVD-based systems.  How many modern cars are cast off because their owners can’t afford dealership rates to diagnose wonky wipers or a climate control system on the fritz?

Instead, what if there were a way to replace these closed systems and proprietary parts?  What if you could have a modular system that allowed you to replace the failing, antiquated, obsolete command and control systems in your old jalopy—either in whole or in part—with modern replacements, developed and supported openly, built on well-documented hardware with published schematics, and running open source software that could be easily updated on the road?

There’s a lot that goes on in a modern car: anti-theft systems, entertainment and navigation systems, remote start, keyless entry, traction control, passive restraints, emissions control, engine management, lighting, instrumentation, and the list goes on.  Replacing any one of these failed systems on a 2006 MINI Cooper S (my own car) would be a monumental task, but I have feeling without an open alternative, you won’t see this car or any others like it on the road in 25 years, and that seems like a real shame.

At The Car Wash

Saturday, March 24th, 2007

Just playing. :-)

(more…)

A Quick(Time) timelapse

Sunday, January 28th, 2007

I used my new suction cup mount on yesterday’s run to take some pictures while driving. When I got home and started sifting through them, I realized I (barely) had enough for a short QuickTime movie. I took the 146 still shots and created a new QuickTime movie, and then brought that into iMovie so I could add a soundtrack. It isn’t much (in fact, it’s so silly I’m wondering why I bothered…), but I’ll probably try to do more like this in the future.

(more…)

Updated Flickr Bookmarklets

Monday, January 8th, 2007

I’ve updated my Flickr Bookmarklets that I originally introduced in January ‘06. They’ve now got their own page, and I’ll make changes and updates there.

Associating with iSquint

Wednesday, November 29th, 2006

I’m loving iSquint for converting videos to formats that are QuickTime and/or iPod friendly, but was frustrated with the inability to open videos with it from the Finder (right-click, “Open With”). A little hacking of the Info.plist and a rebuild of LaunchServices and I’m in business.

First, make a backup of iSquint.app/Contents/Info.plist and then open the original with either Property List Editor or your favorite editor (TextMate, in my case). Now, modify the CFBundleTypeExtensions array (reference) so that it has the video extensions you wish to handle. Looking at VLC, I came up with the following (for the entire CFBundleTypeExtensions key):
    <key>CFBundleDocumentTypes</key>
    <array>
        <dict>
            <key>CFBundleTypeExtensions</key>
            <array>
                <string>3gp</string>
                <string>avi</string>
                <string>mov</string>
                <string>mp4</string>
                <string>mpeg</string>
                <string>mpg</string>
                <string>wmv</string>
            </array>
            <key>CFBundleTypeName</key>
            <string>DocumentType</string>
            <key>CFBundleTypeRole</key>
            <string>Editor</string>
        </dict>
    </array>

I’m not sure how long it would take for this to appear in the Finder normally, but I had to rebuild the LaunchServices database anyway. Once that was done, I was in business!

"Open With" with Pawnee

“Christian Web Developer”?

Tuesday, August 22nd, 2006

... “as a Christian Web Developer, I must say [bla bla bla, nothing related to religion at all].”

What, pray tell, is a “Christian Web Developer”?

Do you cry out “Jesus saves!” before saving your code?

“Praise the Lord” with every semicolon?

“Amen!” when compiling might be apt, however…

Zach suggests every variable begins with “WWJD_”.

FastMail.fm down again

Wednesday, May 3rd, 2006

These guys are starting to piss me off.

Both Web and IMAP services are failing to authenticate. Grrrr.

Aaaaaaand, we’re back

Saturday, February 25th, 2006

This site’s been down for, what, 2 weeks? 3? Something like that. Doubt anyone noticed, but that’s ok. I’ve moved, and the server’s moved, died, and the pieces are being picked up and reassembled on this trusty (borrowed) Mac. Time to do some backups, I think…

Flickr meets vBulletin

Sunday, January 22nd, 2006

Update: Something changed on Flickr, so I have updated them on their own page

I’ve been posting a lot of Flickr images to vBulletin sites (like NAM) and found the number of steps required to come up with the proper post code to be a royal pain in the ass (like most things with vBulletin). Here’s a little bookmarklet that will pop up a JavaScript prompt containing the requisite code to display a medium-sized image with a link back to that image on Flickr:

Flickr to vBulletin

(wow, that was way more work to post to this entry with Textile than it should have been…)

When on an image’s page in Flickr (such as this one), click the bookmarklet, and you’ll be given the code that will look something like this:

[url=http://www.flickr.com/photos/blalor/89537398/in/set-72057594051954910/][img]http://static.flickr.com/31/89537398_971b3013bc.jpg[/img][/url]

Flickr to vBcode bookmarklet

The world just stopped

Tuesday, January 10th, 2006

Acutal job posting: PowerPoint MultiMedia Specialist

Fast growing Indianapolis-based company is currently seeking a experienced and technical savvy PowerPoint/Multimedia Specialist for their CS Department. Duties of this position would include but not limited to media integration, animation, formatting, vendor communication, training, developing time lines, and quality control checks…just to name a few.

Salary between 35k and 50k, depending on experience. Seriously. I only wish I was making this up!