This week saw the completion of one rite of spring: attending a Nats home opener. Another, doing our taxes, is in progress. I haven’t even started a third: mowing the lawn for the first time since last year.
I had some fun with the Federal Communications Commission’s proposed broadband labels by noting how they didn’t cover such broadband pain points as the amount of time you may have to spend talking a rep off the ledge before he’ll consent to your closing your account.
I was far along into a different topic when I realized that we hadn’t run anything about the impending shutdown of a once-promising smart-home hub–and that other stories on Nest’s move had glossed over how tech-news sites waited a good two months to cover it.
This was another case of my setting aside one topic to cover another. This may have been the only story on this issue to clarify that AT&T won’t charge you its “device upgrade fee” if you move your old phone’s SIM card into a new device purchased from anybody besides AT&T.
• I’m still seeing the spinning-beachball cursor way too often, and for steps that shouldn’t particularly tax either computer’s processor or flood its memory. Having it look different does not help.
• While Mail no longer randomly bounces me months back in a particular folder when I select it, it’s exhibiting a more annoying malfunction: When I move or delete messages in either of my Google Apps accounts, they pop back into their original inbox for a moment before being swept away a second or too later.
• Time Machine still can’t do math. On this iMac, it’s complaining that the backup volume is full–even after I’ve removed more than 150 gigabytes of data from its backup set. Dear Apple: I am not interested in buying a new hard drive because your backup utility doesn’t know how to subtract.
• Some random malfunction has caused every item in Address Book–both individual contacts and contacts groups–to get duplicated. I’m going to assume this is iCloud’s fault.
• Safari continues to randomly pop tabs into their own separate window. This bug has now persisted through different OS X releases, and I know I’m not the only one to complain about it. Alas, its cause and how to end it remain mysteries to me.
• Safari remains vulnerable to locking up the entire machine when Safari Web Content processes start to gobble memory; short of force-quitting Safari, my only remedy is to bring up Activity Monitor and force-quit the offenders, one at a time. But hey, at least I can finally silence the audio that started randomly playing in some other tab.