Our old friend Knightwise is back with an interesting problem to be solved.
He reads his books electronically in the Kindle app in ePub format, and he likes to highlight as he reads. He uses these highlights in creation of talks he gives to other entrepreneurs. He outlines his talks using a Mind Mapping program called X-Mind from xmind.net.
He was hoping to get an iPad Pro and use split screen to view the book on one side and the mind map on the other side. The problem he found though was that he couldn’t use the Kindle app in split screen and wonders whether iOS 11 would fix the problem.
A while back on the show, I was talking to someone about Nightshift and how much I dislike it. It might have been Bart but I’ve had this argument with so many people I lose track. Anyway, Chris Eschweiler wrote in letting me know that I’m not alone. He gave me permission to read his commentary on the subject out loud:
Personally, I find removing the letter “F” from “Nightshift” is more accurate. I can’t stand the muddy, baby’s-first-diaper quality that the feature brings to the iPhone. I so want to grab Jony Ive by the collar and remind him that not everyone is looking for stylish, trendy, kitschy interfaces…some of us just want something that works well for *us*.
The closest thing the iPhone has to adding functionality in low light situations is the ability to invert the screen. The only problem is, it inverts the colors of everything…including icons and images.
Why would ANYONE want to invert images, Apple? Unless you’re in some underground command center trying to tease detail from a poor photo of a tire track from a suspect’s car, inverting images is…well, it’s dumb. Why doesn’t Apple modify this feature to be more useful? Light text on black background is a so much easier to read in low light. If we are truly going to embrace the “go paperless” mantra that computers were supposed to usher in, then why do we start with the paper analog and assume the background of everything we do must be white?
This week Steve and I attended, and I spoke at the CMD-D Conference, created by Sal Soghoian. Sal was responsible for all Automation at Apple for many years. His team managed AppleScript, Automaton, and Terminal. Pretty much all the coolest stuff at Apple.
This week’s guest is Patrick Beja, host of The Phileas Club, Le Rendévous Tech, and Pixel, all fine podcasts over at FrenchSpin.com. We talk about how France is marketing their technology worldwide, what the government is doing to encourage tech companies to bring business to France, and how education folds into the equation. We might also get a bit off topic discussing French food and sewing, but as are all conversations with Patrick, it’s a delightful show. You can find Patrick on Twitter @NotPatrick.
This is a bit of a different show – it’s primarily the four part story of my saga dealing with two catastrophic failures with Apple in a single week. It’s quite a tech story with a lot to interesting angles. After that Bart joins us with Security Bits.
It’s time for the final post about my MacBook Pro and iCloud woes from this week, because after four full days, both are finally working! The path there was fascinating.
To recap, my 2016 MacBook Pro went into Apple repair because it wouldn’t charge, and my 2013 MacBook Pro, which was restored from a backup of the 2016, couldn’t access any Apple cloud services. My little friend Erica from Executive Relations had escalated my repair, while my little friend Senior Advisor Specialist Joe was helping me crack the code on iCloud with engineering.
As the saga progressed on my 2013 MacBook Pro being unable to contact any Apple services (no apps would run, no Mail would come in, no access to my iCloud data), I decided to see if I could get a response out of the executives at Apple. I originally wrote to Tim Cook, CEO of Apple but then forwarded the email on to Craig Federighi, Senior Vice President of Software Engineering. He seems like a swell guy with that pretty hair and all.
In my most recent post I told you about how my 2016 MacBook Pro died and had to go back to Apple for repairs. I said at the end that it wasn’t the worst thing that happened. Things got far far worse.
This isn’t my first rodeo, so I had three backups of my Mac. A full clone backup from SuperDuper! on an external drive, plus Backblaze AND CrashPlan offsite backups. It’s a long story why I have both but I was fully covered. I also always keep my most recent Mac when I buy a new one, just in case I ever have a hardware failure like this.
I reversed the cloning process to send my image onto my 2013 MacBook Pro. It was a little bit more complicated than it would be for a normal person, because I had upgraded the 2013 Mac to High Sierra and allowed it to change over to Apple’s new file system, APFS. SuperDuper! is really easy to restore from; you just sort of run it backwards, but it didn’t recognize the internal drive on the 2013. I used Disk Utility to reformat it back to Mac OS Extended (Journaled) and then I was able to shove the backup onto the old machine.
I entitled this article “AppleCare Needs a Frequent Flyer Program” because if they had such a program, I’d be getting all kinds of free perks by now. If someone asked me if they should buy anything from Apple right now, there would be hesitation in my response. It’s that bad.