Introducing MT::Import::*
I keep my email in a dated (YYYY/MM/DD) space. In a world where every other way of organizing email messages kind of sucks, this one doesn't necessarily suck any less but at least it's consistent.
The downside to doing things this way is that there aren't any email clients that are capable of doing multi-folder searches. When I need to find something I am reduced to using tools like grep which, despite having a certain charm, is pretty painful.
Movable Type, with its built-in search and trackback widget seemed like an interesting way to create a threaded read-only archive of my mail. I could have built something from scratch (and I have) but MT was most of the puzzle already completed.
The idea of using tags and comments for annotating an email was also intriguing. Using custom X-headers to tag an email from Ted as "asshole" is great until you need to reply to that message and forget to purge your personal notes.
Also I was curious to see if, and how, it could be done and I hadn't played with the MT source in a couple years.
In other 1.0 news, I've blessed Net::Blogger as 1.0 to celebrate Blogger's decision to deprecate version 1.0 of their API. I've also passed maintainership of the module on to Chistopher Laco. Similarly, Net::Google has been blessed 1.0 just because
and passed on to Bill Stilwell.
Oh, and that gaping hole you've been feeling in your life? It can be filled with change files written in RDF.
#mtsplatAaron's del.icio.us bookmarks, XBELjax-ified
#xbeljaxSome things that kind of suck trying to use XBEL and XSLT, in the browser, include :
“Getting the Interweb on a Yahoo Wi-Fi shuttle without the Wi-Fi”
But that doesn't help me, now, does it ? Here he is, browsing on the bus while all I have is an unfinished OmniGraffle network diagram in front of me. I was blue, and feeling no love.
John Allspaw, ladies and gentlemen. Feel the love.
#wifilovemap { pithy_comment($_) } @apis;
08:13:56 me: just flickr
08:14:03 me: but I like to keep an eye on the maps stuff
08:14:19 him: cool...
08:14:37 me: even I would have told them that SVG ain't ready for primetime yet
08:15:03 him: yeah, well, someone's gotta push the edge.. I mean 'w3c standards'
08:15:06 me: 6 months after firefox 1.5 I imagine people will wonder how they ever lived without it but, well, people are stupid that way
08:15:13 him:heh
08:15:14 me: w3c 2.0
08:15:29 him: ooooh, yeah... tell Tim O'Reilly
08:15:51 me: I imagine that's what the what wg imagines themselves to be
08:16:01 him: suppose so..
08:16:11 me: we need to write a microformat for BNF (BFN?) notations
08:16:37 him: BFN being?
08:17:15 me: it's that awful syntax used in formal specs to define properties of an object - just poke around any w3c spec
08:17:33 me: awful but concise and without much room for interpretation
08:17:35 him: no thanks, I like to keep what little sanity I have
08:17:49 me: says the perl hacker ;-)
08:17:54 him: what, the RSS 2.0 "spec" isn't good enough for you!
08:17:59 me: heh
08:18:34 me: I am going to write an RSS 2.0 geo module where everything is relative to wherever dave winer's car is at any moment
08:18:58 me: it will use enclosures to pull down his latest podcast as a reference point
Meanwhile, I wrote myself an OOP-y / XPath-y wrapper for the Yahoo! geocoder API. I probably won't put it in on the CPAN, but it is available online if anyone wants to play with it.
#maps