Two weekends ago, Diet Coke was accidentally spilled onto my MacBook Pro Keyboard. The machine, a Core Duo 15" that was among the first of the Intel Macs rolled out, suddenly didn't work the way it used to. Luckily, damage was restricted only to the keyboard: caps lock, shift, b, h, and num lock didn't function. Not being able to type the word "butt" was a pain in the "utt." While I've since repaired the keyboard -- on my own, thanks to iFixit's instructions -- it made me question, again, the value of an extended warranty. Had the damage been worse, I may have had to get a new machine.

While AppleCare is certainly compelling for many (phone support and timely repairs of manufacturer defects by Apple-authorized technicians, among its values), its defect is that hardware repair coverage is restricted to manufacturer defects. And in my case, even if this had been a new machine still under AppleCare, it wouldn't have been covered. So, if you accidentally drop your iPhone in the toilet (it happens) or if, while looking up your Tiramisu recipe in MacGourmet, you happen to spill Kahlua all over your MacBook, you won't be covered by AppleCare.

While researching third party extended warranties, I stumbled upon Square Trade. In addition to covering manufacturers' defects, Square Trade's warranty covers accidental damage. In effect, it's a warranty with an additional safeguard for dings, drops and drenching.

Although the Square Trade warranty covers accidental damage, consider all your options before proceeding with a purchase -- Is it worth its cost? For example, claims for accidentally damaged items (as opposed to manufacturer defects) require a $50 deductible. In the case of the MacBook and MacBook Pro, this narrows the price gap between AppleCare and the SquareTrade price.

While I love the functionality of Apple's microphone-enabled headphones (both the Apple Earphones with Remote and Mic, which comes with the iPhone 3G S, and the iPhone Stereo Headset, which came with previous iPhones), I've found that the extra layers of functionality also bring extra layers of troubleshooting when they're not working right. For simplicity sake, I'll refer to said models as "iPhone headphones" in this post (non-volume control model pictured).

The most common issues I've come across pertain to the microphone. Unlike most non-microphone enabled headphones, which use a standard two-ring TRS connector (tip, ring, sleeve), the iPhone adds an extra ring to support microphone functionality. This is what the hardcore audiophile refers to as TRRS (tip, ring, ring, sleeve).

But if your pockets are consistently filled with lint and dust (or tater tots if you happen to store them there), that extra ring won't make full contact with the iPhone's headphone jack. Which means that you, unfortunately, will lose microphone functionality.

One way to fix this is to remove any dust or lint trappings in the phone's jack. I've found that wrapping a toothpick with a thin layer of toilet paper and brushing it lightly against the walls of the headphone jack helps out a great deal. It's also important to not dip said toothpick in water or moisture. There's a moisture sensor in the iPhone's headphone jack. When exposed to moisture, it changes color and could potentially void your warranty. Also, the usual disclaimer in do-it-yourself scenarios apply: you're doing this at your own risk, so proceed with caution.

The following is a re-enactment of the mysterious and sudden failure of Megan Lavey's MacBook.

It was the evening of Tuesday, July 14, 2009. Megan Lavey heads out to the movies to watch the eagerly anticipated Harry Potter and Half-Blood Prince. But the excitement of the night was short lived.

Upon her arrival home, Megan found her MacBook in an unconscious state. She tried several attempts to revive it: plugging it and unplugging it, removing and reinserting the battery, as well as performing an SMC reset. However, these attempts proved futile.

In a last ditch effort, Megan made an emergency visit to her local Apple store to meet with a genius. They had both good news and bad news. The good news was that they identified the problem with her MacBook (the logic board) and could save it, but -- and here comes the bad news -- could cost up $750 to repair. What's worse, Megan didn't have AppleCare coverage. In a state of shock and sadness, Megan leaned on the shoulders of her fellow TUAWers, each of whom offered words of encouragement her:

Chris Rawson: "My wife's mid-2007 MacBook is having the exact same issue right now. Luckily, it's covered by AppleCare, and going to the local repair place ASAP."

Erica Sadun: "":( :( :(""

Sang Tang: "Hey, this would make an interesting post. I'm going to write something on this."

There are many Megans in the world, and each is faced with the difficult task of deciding whether or not a repair is worth its cost. It's also times like these that one regrets not purchasing AppleCare, for often times repair costs outweigh the cost of AppleCare. And this raises the question. Should you purchase AppleCare? Several months back, TUAW's Robert Palmer penned a piece on why he believes AppleCare is worth it. This post expands upon that and provides examples of when AppleCare is and isn't justified.

ifoAppleStore is reporting that Apple has instituted a new policy that will let iPhone owners swap their liquid-damaged iPhones for replacements. For $199US, customers can swap their defunct phones for a refurb unit, provided that it succumbed to an out-of-warranty encounter with liquid. Here's the catch: Said swap renews your 2-year contract with AT&T -- so it's pretty much like buying a new phone, except if you were to do that out of contract it would cost you $499 for a 16GB unit.*

Of course, this could also be another way to clear current iPhone inventory in preparation for a new model.

We couldn't determine if sweat-induced failures are covered by this program, but we'll let you know if we find out.

*Update: Apple has told us that a replacement under out-of-warranty service would not renew a customer's contract. We apologize for the error.