Face it: your address book and your contacts, they're personal. They reveal a lot about you: your friends, your business partners, your cake buying proclivities, and more. The address book you see at the top of this post appears to be for someone in the Denver area. I know that because of the REI Denver listing and Le Bakery Sensual on 6th, which I drive by whenever I head East from Broadway.

These contacts, along with their notes, their phone numbers, dates of birth, and other information say a lot about the person whose address book this is, and also about the people who appear in that contact list, with all their personal and professional info.

There's one big problem. The screen shot you see wasn't made by the person who owns this me.com account. Under certain very specific conditions, Apple is inadvertently sharing data from other people's accounts. Ouch.

A TUAW reader sent us a video made as he renewed his me.com account from the UK. The address book data he accessed during that time included this Denver-based set shown here, as well as data from an Ireland-based user of Polish descent (all his contacts were back in Poland although his business was based in Ireland).

This all went down during the period when his MobileMe account was renewing. Each time he logged off and back on, he was presented with yet another set of contacts--none of them his. He writes, "Each time I logged off and on I got a different address book. All the other options were disabled (because my renewal was being processed) but clicking the Contacts icon showed me *an* address book," just not his address book.

With a little Internet-fu, he checked out some of the numbers and found that they were valid and operational. This leads him to believe that this is real data. My inspection of the local Denver data from his screen shots convinces me of the same. Further inspection of work addresses and personal family names makes us believe we know whose Denver-based address book this is. We've attempted to contact this person but as yet have not heard back.

The address book glitch ended once the registration process finished, leaving our TUAW reader with a series of screen shots and videos and a deep concern about Apple's ability to safeguard personal data. He's already contacted Apple about the bug. "I contacted them by two means: their web-chat thing where they told me that they 'had no reports of such an issue'. They suggested closing and reopening Safari (helpful eh?) and a generic autoresponse saying they'd reply within 5 days when i sent an email." He adds, "I don't think the people manning the help desk appreciated the seriousness of the situation."

TUAW has sent a heads-up to Apple and will keep monitoring the situation to see how it develops.

Looks like it. You can't access the main MobileMe page. Apple says this on their MobileMe support page:" MobileMe members are intermittently unable to access MobileMe services. Mail is available via a desktop email application, or Mail on iPhone or iPod touch. Normal service will be restored ASAP. We apologize for any inconvenience."

Well, at least that page is up. Seems like MobileMe has had a rough couple of weeks with issues concerning mail, Back to my Mac, and syncing.

The MobileMe service had a rocky start and has had a variety of issues over the last year or so. Let's hope Apple gets things back on an even keel soon. So far this morning, MobileMe is MobileGone.

UPDATE: Some of us are able to log in, but it has been up or down for various people throughout the morning. The status page still says the issue is intermittent as of 3:15pm ET.

UPDATE #2: Looks like everything is back to normal. Thanks to everyone who sent this in!

We reported on the abundance of Time Capsule failure-to-boot after 18 months in September. A new site has emerged from the mist to help Time Capsule owners who are struggling to get Apple to acknowledge the issue. TimeCapsuleDead.org exists as a register for the owners of dead Time Capsules and has links to self-help discussions as well as the Apple Feedback page. Of the devices that have been registered thus far, the average time until ports-up is 17 months and 29 days -- eerily close to the estimated 18 month mark.

We'd like to give you a friendly reminder that our own Lauren explored the AppleCare agreements, and found that any computer-centric AppleCare agreement that's in force should cover this Time Capsule failure (as it's considered a peripheral used with the Mac). That does not mean that our readers who don't have a current agreement should be left begging on the streets by Apple. This is something that needs to be addressed. Hopefully this new site will be a good resource for all of our readers.

Thanks, Pim and KB!

UPDATE 2: Be sure to read Engadget's analysis of what appears to be a non-event here.

Apple is apparently getting hot and bothered over Australian/New Zealand supermarket chain Woolworths' new logo. Woolworths insists the logo is merely a stylized "W," but Apple's copyright lawyers aren't buying it. They're trying to knock down Woolworths' copyright application for the logo by claiming it violates Apple's intellectual property.

Apparently, according to trademark lawyer Trevor Choy, Apple does this fairly often, trying to make sure that some other company's branding can't be mistaken for its iconic logo.

I'll admit that at first glance the logos look similar (to me, anyway – my ex-graphic designer wife doesn't agree). Even so, it seems kind of a stretch to assume anyone is going to confuse Woolworths, a supermarket chain based only in Australia and New Zealand that mostly sells, you know, food, with Apple, a worldwide company that sells computers. Trust me, I shop at the Woolworths here in Palmerston North every week; it's a decent grocer, but nobody's going to wander in there looking for a MacBook Pro.

What do you think? Does Apple have a case here? Or is it sort of ridiculous for Apple to claim that anything roundish with a leaf on top endangers its trademark? Sound off in the comments.

UPDATE: A couple of points we should clear up on this post. First, Apple is not, in fact, the aggressor in this case. No one is, really. It is a trademark action, and as far as we know it has NOT become a lawsuit. It appears to be a part of the trademark process as it happens down under. Apple is free to object, and since Woolworths is attempting to register their mark across a huge range of products (like computers), they are practically obligated to do so. We'll keep an eye out for any interesting developments, however. - Ed.

Something new, unexpected, and possibly worrying has popped up in iTunes. iTunes now "calls home" to the Apple mothership whenever you restore an iPhone or iPod touch. It tells you that it's "Verifying restore with Apple...", checking your device identifier and the firmware with Apple's new signature server.

Today, TUAW has the pleasure of talking with Jay Freeman, otherwise known as "Saurik", the developer of Cydia. Saurik has constructed a server that duplicates Apple's functionality, ensuring that you'll be able to downgrade your iPhone or iPod in the future, even if you have not jailbroken your device. This topic is for all iPhone users, regardless of whether they use jailbreaking. Please join us with your questions and comments as we hear from Freeman about why this move matters to you. Read on to see the full live chat transcript.

Please join us this afternoon at 4:15 Eastern for a live chat with Jay "Saurik" Freeman. Jay is going to talk to us about Apple's new signature server and what that means to you as an iPod or iPhone owner.

Have you noticed a new message in iTunes when you restore an iPhone or iPod touch? "Verifying restore with Apple..."? iTunes is now checking your unit against a registered database and deciding whether to allow you to install your firmware or not. Potentially, Apple could disallow downgrades to previous firmware versions. According to Freeman, this move allows Apple to "recall existing firmwares by keeping people from restoring to them in the future. To do this they simply would refuse to ever sign, for example, iPhone OS 3.0 again."

Freeman will explain why this is a real problem to both the standard App Store community and to the jailbreak community. Join us with your questions.

Something seems rotten, at least for some Mac users, with the Apple Mail program. Apple support boards are lighting up with reports of email messages being downloaded multiple times. This problem seems to be mostly with POP mail accounts, but even IMAP users are seeing it. There is another Apple support thread here with 10 pages of comments from unhappy Mail users.

I've noticed it myself twice. In the morning I bring up Mail and read what's come in overnight. Then a little later I re-open Apple Mail and the same messages download again. Of course my POP account is set to delete everything from the server, and my settings have not changed.

This is the first really bad behavior I've seen from Apple Mail since OS X came out in 2001. This most recent glitch seems to have popped up in the 10.6.1 update. There are enough people reporting it that it seems like there is an issue for some users, but obviously not everyone is seeing it.

There have been some suggestions posted, but while they worked for some they did not work for all. Are you seeing this strange behavior? Did it start with 10.6.1? Let us know, and hopefully Apple will kick the code for the next update and put this bad boy to rest.

Thanks to Mark for the tip.

The latest festival of issues with Snow Leopard alongside a round of people unhappy with the latest iPhone update both suggest that Apple might need to work a little harder on pre-release testing.

One thing Microsoft does rather well is gets a lot of people testing software releases in extended public betas. Of course that didn't go so well for Vista, which was a mess for many people, but it seems to have gone better for Windows 7.

Apple, secretive as always, doesn't get really wide testing of new software builds, and when those updates finally get released there seems to be an ever increasing, ever louder response from customers that things aren't going swimmingly.

Snow Leopard was supposed to be a cleanup of Leopard, but it appears that some people are having lots of issues. In my own case, some fonts were pretty messed up, and Keychain was jumbled pretty badly. The fixes in both cases weren't onerous, but they were nasty enough that it made me wonder how thoroughly the release had been tested. I still don't hear new mail sounds from MobileMe, a problem that has been going on at least since Leopard was released. I'm not alone in this, but not everyone has the problem.

Most of the people I know had flawless upgrades, and of course here at TUAW we are more likely to hear about problems, which is also true of the Apple forums where people are able to report the smallest or the largest bugs.

Therefore, from my perspective it's hard to say for certain if things are slipping away from Apple quality control, but it's starting to look that way. Apple was quick to release 10.6.1, which was a good effort, but it is not quieting down the roar of users who don't think that this latest release of Snow Leopard 'just works.' What's your perception? Does Apple have some work to do?

In the last week, we have had a constant barrage of iPhone issues break through the lines... so much so that we feel it is our duty to inform the two of you who haven't updated what you could experience by updating to version 3.1 of the iPhone OS. This is no small problem, as you can read from the discussions on Apple's website here, here, here, and here.

The first two links are where we're getting the majority of our tips -- random shutdowns and very poor battery life. The second two, bricked phones and general slowness are still worth a mention -- even prompting our own Erica Sadun to do a live walk-through for debrickifying iPhones. We received a lot of praise for her help in that session and we'd encourage you to go back and read through the chat if you're experiencing trouble with a bricked iPhone.

I've spent quite some time reading the hundreds of posts about the "mysterious random shutdowns" and have determined that it really is what it is. As of this writing, there have been 409 posts and 28 pages in that discussion -- I've seen very little repeats and no real solutions. Some people have said that they've gone to Apple and received replacement phones because of this issue but for those of us who have out-of-warranty phones, Apple has merely said "It's $199 for a replacement." I have to agree with our tipsters -- this needs to be addressed. These people simply did not break their phones, it's a well-documented issue which we, as consumers, shouldn't have to pay to fix.

Battery life is a completely different debacle. I cannot seem to find a trend in the discussions at all. Some people claim to have removed certain apps, some claim that MobileMe sync is the culprit -- all of them agree that there is an issue with 3.1 and that battery life shouldn't dramatically decrease overnight. I'd really love to get into one of these phones and replace the battery to see what happens because the hardware guy in me says that it's not impossible. However, deductive reasoning says that there's something in the software. Whether there's a memory leak in 3.1 itself, or some apps that we're running aren't as "compatible" as they should be... we need to see another update soon to help alleviate the issues with version 3.1 of the iPhone OS.

Please feel free to use our comment system to express your concern, anger, resentment... whatever. Try to be helpful if you've come across a solution and be nice if you're not having these problems. Until Apple issues a fix or acknowledges the problem at all, just hope that you're still in-warranty.

There are quite a few unhappy Time Capsule owners over at the Apple support boards. It appears that some Time Capsules are going belly-up at roughly the 18 month mark, simply refusing to power on.

As Brian from Texas wrote:

"My TC did the exact same thing two days ago. It is 18 months old. After doing some research, I have found others with the same problem. At 17-18 months, the power supply goes out. I went to the Apple store today and they said too bad, out of warranty."

There are 6 pages of TC owners with similar issues, most of them happening after about a year and a half, so it looks like something is going on with the units.

This seems eerily similar to the 'dead airport express' syndrome of a couple of years ago where the products would simply fail to work and all the data and power lights went off. Sometimes there was an audible popping sound. Other times, the APX just died.

If you are having this issue it might be a good idea to report it to Apple and see if the weight of complaints gets them to look into this. Let us know too.

Thanks to Mike for the tip.

Update: As it's being discussed in the comments here, Lauren went ahead and investigated whether AppleCare for your Mac will cover an out-of-warranty Time Capsule. The answer may surprise (and please) you.

Buyer beware: one of the features that has silently disappeared from iTunes 9 is the Shopping Cart, where you used to be able to place songs, albums, videos, and apps for future purchase. It has been replaced with a new feature called "Wish List" that functions similarly to the old shopping cart, storing your potential purchases on iTunes's servers.

What's slightly sneaky about this is there's nothing apparently different from an end-user's perspective at first glance. Clicking "purchase" or "buy now" used to automatically place items in your shopping cart if you had that preference enabled, but now the behavior has been completely altered – now all purchases on the iTunes store are 1-click if you click the "Buy Now" button, and there's no way to cancel them once they start. So whether it's a $1.29 song or a $129 iPhone app, if you click that "Buy Now" button, you're getting charged.

If you want to emulate the old "shopping cart" purchase behavior, you have to instead click the arrow to the right of "Buy Now" and select "Add to Wish List."

A big thanks to the many readers who sent this tip in.

Update: If you had items in your shopping cart before updating to iTunes 9, they won't have disappeared. All of the items that used to be in your shopping cart in iTunes 8 or older should have migrated to the new Wish List in iTunes 9.

It's not that we have anything against the Flash plugin for Mac browsers. Well, other than the fact that it's crashy, and slow, and makes our laptop fans spin up like we're doing wind tunnel testing for the Air Force. But other than that, we have nothing against it -- and it's lovely that the new 64-bit version of Safari in Snow Leopard can isolate Flash-related stalls and hiccups from the main browser process for enhanced crash protection. Very nice.

Unfortunately, as pointed out initially by Graham Cluley over at the security and anti-virus vendor Sophos, the version of the Flash plugin that Apple bundles with Snow Leopard is old. It's the 10.0.23.1 version, old enough that it has some notable vulnerabilities versus the currently shipping 10.0.32.18 version. You can check which version of the plugin you have by visiting this Adobe check page. Even if you had the current build on your machine before upgrading to Snow Leopard, the upgrade process replaces your Flash with the vintage Flash instead -- poor form! Cluley recommends, and Adobe concurs, that the best thing to do is head over to Adobe's download site and get the most up-to-date version instead.

It's understandable that Apple had to lock down a version of the Flash plugin for inclusion in the OS golden master, but if you're gonna do that then you've got to provide an integrated method for users to update to the current build when the time comes (like, say, via an OS-wide Software Update utility). Downgrading user security while upgrading OS versions is a rotten way to run a railroad.

[Side note, does Cluley's narration in the video above make you wonder if, just maybe, he's moonlighting as Ben 'Yahtzee' Croshaw over at The Escapist? NSFW!]

Thanks to everyone who sent this in.

The world was looking bleak and dreary after Snow Leopard arrived last week, for my little menu bar friend, iStat Menus for Mac, was incompatible with the new version of Mac OS X.

This morning, however, the sun is shining, the birds are singing, fluffy kittens are playing again (see image at right for proof), and all is right with the world! iStat Menus 2.0 has arrived, and now my CPU monitor, calendar, and clock are back in the menu bar where they're supposed to be. The new Mac OS X 10.6 Snow Leopard compatible version is running just fine, and less than a week of darkness filled the hearts of all of those who love iStat Menus. You can download it for free, although a donation is requested.

While iStat's developer, iSlayer, has resolved this disturbance in The Force, there's still a dark and evil presence in the universe. Apple, taking on the role of Emperor Palpatine with gusto, recently forced all iPhone developers to remove or retool apps that use a Free Memory function to display memory usage and/or clear out wired or inactive memory. As a result, iStat for iPhone [App Store] version 1.1 was released with the Free Memory function removed. Bjango (the iPhone arm of iSlayer) has kindly posted instructions for how to use version 1.0 to keep the function intact, but we're all wondering why Apple decided to axe all apps that performed this useful function.

Since this latest kerfuffle has forced Bjango to release a feature-limited version of iStat for iPhone, the company has reduced the price to US$1.99. There's no word from Apple on why they chose to kill all of the Free Memory apps. When you're the Emperor, you don't have to give any reasons for stomping on kittens.

So, how's everybody enjoying Snow Leopard? Good stuff, isn't it? Gotta love those new Exposé options in the Dock, and all that saved hard drive space, and the faster if slightly quirkier performance... isn't it, um... great?

Argh. I can't keep up the charade anymore. I know nothing about the Snow Leopard experience other than what other people have told me, because it's not available in New Zealand yet (at least not outside of Auckland). And I'm not happy about it. And I'm going to rant... now.

In July of 2008, the Apple-loving (and Apple-hating) world's eyes locked onto a small, isolated nation in the South Pacific: New Zealand, home to 40 million sheep and a few hundred otherwise perfectly normal human beings dressed as hobbits. Why so much attention on New Zealand? Because of all the countries getting the iPhone 3G, New Zealand was getting it first thanks to its location just west of the International Date Line.

The logistics involved in a rolling launch across most of the world must have been staggeringly complex, but with a few bumps here and there, Apple pulled it off. The launch of the iPhone 3G was a success not just in New Zealand, but worldwide.

That led me to believe that something similar would happen for the launch of Snow Leopard. After all, if Apple could pull off launching the iPhone 3G in so many countries on the same day, it ought to be a simple matter to do the same thing with a much smaller and simpler product. I mean, it's got to be harder to coordinate the launch of a big ol' phone compared to what's essentially just a plastic disk in a box, right? Right...?

Well, not so much. Apple has fumbled the NZ launch of Snow Leopard like a wide receiver wearing butter-coated gloves. Plus the receiver is blind. Also, he doesn't know how to play football.

TUAW has covered the fine iPhone apps from Tapbots more than once. ConvertBot is a beautifully-designed and functional app to do a myriad of unit conversion calculations, while WeightBot is my personal favorite app for keeping track of my incredible ballooning body.

Tapbots posted an entry on their blog today stating that the most recent version of ConvertBot (1.4) had been rejected by Apple. What was Apple's reason for the rejection? As you can see in the graphic at the top of the page, the ConvertBot icon for time conversions looks very similar to the Phone app icon for recent calls. This is the same icon that has passed Apple's scrutiny in previous versions, so it is ridiculous for the company's eagle-eyed app inspectors to suddenly decide that the icon is unfit for iPhone consumption.

Mark Jardine of Tapbots noted "So what's the plan? I need to redo the icon, I suppose. But Convertbot icons were meant to use as little lines/shapes as possible to identify the category. I feel that our current icon represents time as simply as possible. So how can we make Time different? What if it's set at 9 o'clock instead of 3? Is that acceptable? The big problem here is the only way I can get that answer is by making the change, resubmitting the app, and waiting another week or 2 for Apple's verdict."

What gives, Apple? You release a couple of amazing apps to the world this week (Facebook, Spotify, TUAW, and Yelp), but you hold up the next release of an established app over an icon. I'm giving the App Store approval people the "idiots" tag on this post.