I don’t know what it should be called…but anyway, I put up a page where I can try to organize my allegedly spiffy idea . After my little “Proof of concept” experiment with audio geomicroblogging during the holidays, I’ve decided that the concept is indeed at least fun to play with. Since I’m still too poor to buy myself any really expensive toys or take a long luxury vacation, I figure I can amuse myself by trying to turn my experiment into a “real” system that someone might actually want to use. I’ve posted my current idea and plans for the first release at the link up there. I figure getting to the first basic implementation will take a few days to a few weeks, mainly depending on whether anyone but me likes the idea (if it seems interesting to anyone else, there’s a lot more reason to focus on getting it done than if it’s just a crazy idea that everyone else hates…)
Between telemarketers annoying me into getting my upgrade to Asterisk 1.6 finished and the hasty long-overdue road-trip back to and from Idaho again, I’m reminded of an idea that has been fluttering around in the back of my head, not unlike a small bat in the top of a bell tower.
My vast hordes of cult-like fans always seem to want to know where I am. This is obviously an issue in a case where I’m going to be driving 1600 miles, then turning around and driving back, over the span of 4-6 days. It would be pretty easy to set up something on a web page somewhere with some kind of map. The real problem is – how do I update the map?
In some places, I could stop for a while, haul out Igor, boot up, find a public wireless network connection to the internet, and do the update that way. However, that’s time-consuming and awkward, and I want to get this trip successfully completed as quickly as I can. Plus, it’s not always easy to find public network access points, especially through the barren, windy, snowdrift-covered wastelands of Southern Wyoming where a chunk of my route will take me. I have a hypothetical solution, however…