A couple of months ago, my mother was diagnosed with breast cancer. She had a lumpectomy, followed quickly by mastectomy, and is now undergoing chemotherapy. When she first told us, i started preparing myself for the worst. Mom was already in poor health, and I figured if the cancer didn’t kill her, the treatment would.

Since then, I’ve become a little more hopeful. The doctor gives her good odds for surviving five years. The chemo’s been hard on her, landing her in the hospital with pneumonia recently. But, she’s responding well to the treatment.

I have to be optimistic, because anything else will drive me insane.

Because of this, my wife and I are running in the Komen Race for the Cure this Saturday. We started a team, so a few of our friends are joining us for the run. I hate running, but I hate being unable to help someone I love more, so there ya go.

This is the part where I hit you up for money.

I suck at this sort of thing, so I’m just going to say it: If you can afford to donate a buck or two, I’d love for you to sponsor our team. Or it’d be good if you could tweet, reblog, etc. the hell out of this to get the word out.

And if you have any extra bandwidth for your good thoughts, please send some to my mom. But don’t send them too hard — if she figures out where they’re coming from, I’ll have to explain Twitter/Tumblr to her. And nobody wants that.

Update: Looks like Twitshirt is changing their policy. Great to see a company respond so quickly to the community.

So, yeah, Twitshirt. I want to be clear that my objection is not for me personally. Do whatever you want with my words — once I’ve said them, I’m done with them. In fact, once they switch from the password anti-pattern to oAuth I’ll likely sign up and dutifully wait the 20 years it will take for me to earn enough to get a check. But that’s me, and you should never assume you can use someone else’s work without permission.

Because that’s really the problem here: permission. While royalties and opt-out forms are improvements over past attempts to sell tweets on shirts, it’s still not right. That’s not how copyright works. I can’t stand on a street corner and sell copies of Wall-E with a simple disclaimer that I’ll stop if I’m asked to. And Disney’s certainly not going to be interested in my offer of a 2.5% royalty.

It’s made worse by the fact that Airbag Industries, the company behind Twitshirt, is one I really admire. I expect better than this from them. My guess is they didn’t think it through. If they had, they would’ve seen that opt-out is wrong. They also might have realized all the other problems they were setting themselves up for.

So you wanna sell Tweet Shirts

This is the first problem that occurred to me. It’s also the first opportunity that occurred to me: What’s stopping me from retweeting everything that @hotdogsladies (who is opting-out) posts and making a killing on royalties? As far as I can tell, only morals.

Now, how ‘bout we print this shirt:

Think anybody will have a problem with that? Or maybe something like this:

Our little tweetshop has been in business five minutes and we’ve already committed copyright infringement, trademark infringement, and libel. Feels like a Monday, doesn’t it?

It’s a good idea. A really good idea. But from a practical standpoint, it just doesn’t work. I can only think of two ways to do it right: Create a CafePress style site, where individual Twitterers set up their own shops and you take a cut. Or, find individual tweets you like, negotiate a price with the writers, and sell limited runs of the shirts. Offering any tweet is so tempting, but it’s a world of hurt.

I hope Airbag realizes they’ve made a mistake and, at the very least, switch from opt-out to opt-in. It matters because words matter, regardless of whether you can sell them on a t-shirt.

I don’t understand — how can a cobbler even have children? And why would any dessert need shoes?

A few months back, I listed the places where I regularly publish online. I’ve added a few places since then, so I thought I should update the list. Here’s the list, in its entirety and formatted to fit your screen:

• What I’m doing and attempts to be funny go on Twitter.
• Links that I’m saving for my own reference get saved at del.icio.us.
• Links that I don’t necessarily need to save, but that I want to others to read — and thoughts that are longer than 140 characters — are shared via Google Reader.
• Movable Type tutorials go on Devlounge.
• MT news is posted every Monday on Blog Herald.
• Mac and iPhone software news and reviews on MacApper
• Blogging tips on… wait for it… Blogging Tips

The irony is, the more of these sites I write for, the more traffic gets directed here, where I don’t have time to write because I’m writing for these other sites (That is irony, right?). Hence my recent thinking about cobblers and shoes. My hope is that all this blogging I’m doing elsewhere — where I get paid and have real deadlines — will make me a better, more productive writer. And that, in turn, will lead to more posting here… which will lead to more blogging jobs… which will lead to my finally getting one of those drinking problems all the good writers have. Here’s hoping.

This past weekend, we went geocaching for the first time in a few years. We assumed, with each of us having an iPhone 3G, that we had everything we needed to find some caches.

Yeah… No.

We tried two different methods. First, we browsed to a cache page in Safari and clicked the Google Maps link to see the location in the Maps app. This all worked as it should — eventually. We were on a very slow Edge connection, so it took minutes to load the page, and more minutes whenever the map needed more tiles. The iPhone would find the location just fine. The problem was, the map app doesn’t have a high enough resolution to lead you to a specific set of coordinates.

We next tried MotionX GPS Lite. Downloading a 7MB app over Edge is a special experience I wouldn’t wish on anyone. MotionX works pretty well — put in your coordinates and the on-screen compass leads you to the location. This would work for geocaching, but the app depends on the iPhone being in motion for it to calculate a heading. In motion at a speed of at least 3 MPH, in fact. So to use this app I had to run back and forth in the woods, trying not to step on a cactus or slam into a tree. Ultimately, I gave up, as each heading update just made me more lost.

This was all very dissappointing. One of the reasons I bought an iPhone 3G was for geocaching and other GPS-related activities. But since it failed to achieve in the modest task that was its charge, I’m left wondering if I need to buy a separate GPS device.

Some people claim the iPhone GPS chip isn’t accurate enough for geocaching or turn-by-turn directions. I don’t buy that. The first commercial GPS devices were accurate to within 3-5 meters, same as most new devices. No reason the iPhone would be any different. A GPS receiver picks up signals from a minimum number of satellites then tringulates its location. The device itself has very little influence over the accuracy that comes from that process. It may be that the iPhone uses a small receiver that has more trouble detecting satellites. But the GPS-A chip is supposed to help compensate for that.

My gut tells me the real problem here is Core Location, the API apps use to access the GPS data. I know it provides speed, heading, and coordinates, but what an application really needs for geocaching is a continuous stream of updated coordinates. I’d be willing to bet Core Location can not provide those updates fast enough. If someone more familiar with the API could shed some light on that, I’d love to hear about it.

So am I giving up on my iPhone as a GPS device? Not necessarily. It’s possible that a future update to the OS will improve the situation. In fact, that may be what GPS software companies like TomTom are waiting for before they release their apps — a better API. Or perhaps there’s a better GPS app in the iTunes store that I haven’t tried yet. If anybody’s had success with a particular app, let me know in the comments.

In the mean time, though, I probably won’t be doing much geocaching.

…It’s a boy.

(What, you didn’t know we were expecting? You really should try Twitter)

Two points about ultrasounds: First, the work involved in performing an ultrasound makes Photoshop look like MS Paint. Second, many people have asked if we’re going to have a 4D ultrasound. Unless we change our minds, the answer is no. Maybe it’s just me—and it could be, since most people that have seen them, love them—but the photos and videos look to me like they’re from deep in the heart of the Uncanny Valley. Again, just a personal thing.

It’s become clear to me why women get pregnant and not men. Angela is handling the discomfort and inconvenience far better than I would. She’s amazing, she is. Of course, I’ve always said if I could be pregnant with our child, I totally would. Just the same as I will promise, here & now, to fight any dragon that attacks the U.S. That’s just the kind of man I am.

So, anyway, parenthood. I don’t have anything profound to say about it yet. So far, it’s a constant theme park Viking boat ride between overwhelming fear and immeasurable joy. I go into it totally unprepared and completely committed. I can’t even imagine what it will be like. I try, but what I imagine ends up being things I’ve seen in sitcoms. I only know one thing for sure: I’m grateful to have such a wonderful partner.

And, despite all the uncertainty, I’m sure looking forward to meeting that little guy.