slate While looking through my referers, I noticed that I got mentioned in a Slate article. I really sound cheesy in the quote. I probably would have pulled that quote as well. I was caught up in the moment a little bit when I wrote it, but I don't regret writing it that way. That was a prertty horrible day. It started exactly the way 9/11 started. My wife gets up earlier than me, and she checks out the news. She runs into the bedroom and wakes me up, and tells me what happened. I parse the words, but the significance of the event doesn't sink in until about 15 minutes later, when I saw the events unfold on CNN.
It was freaky how similar the days were. |
getting closer The http://developer.danger.com site is getting closer. The host resolves, but the site is just a little "under construction" page.
I can't wait. |
ego surfing So now I'm the 7th David Brown in Google, after the Astronaut, the Aston Martin designer, and some guy who works for Textron.
Pretty cool. |
customers It's nice to see that there are people that are actively using the MailEdit tool. (Yes, Cameron, I know you're using it too, I just don't have the link for your weblog handy. I'll fix that when I get home.) (fixed.)
I love making tools, I love it when people use those tools. |
research pays off So, I squashed some bugs last night, added a feature, and figured out why Radio was copying my images. Of course, I don't know how I can keep Radio from copying my images, short of duplicating functionality. It turns out that the mere act of referencing an image using radio.macros.imageRef puts the image on a list of items to be copied to a location directly under /images/ in your WWW folder and therefore in the cloud. I don't like this -- it means I'm using 2x the space for any image not directly under /images/. It also means that there's the potential for filename collisions. I was going nuts last night, feeling as if I was never going to figure out why my images were being moved around. Finding the code that did it was satisfying. Oh, and the new feature? If I can figure what the name of the attachment is, that's the name that gets used as the filename. I know it's not that big of a deal, but you would be surpised at just how many different ways mail clients create attachments. Right now you still can't use Mail.app from OS X to send an image to MailEdit. I've heard rumors that a fix was in the works. Mozilla's mail client plays with tcp.getMail's mind, and causes a bogus attachment to be created. I end up doing a lot of work in MailEdit just to sanity check the attachments.
At any rate, we're getting closer. A lot closer. Just got to keep
digging. |