Skip to content

3,641 miles on 0.0 gallons of gas – Part Two

In the first part of this two-part series, I covered the planning and car prep required for our trip; today I'll cover the driving (briefly) and the charging (in lots of detail).

Driving the route

For a trip of 3,600+ miles, it's amazing how little trouble we had—or even saw—on the roads. We had no near miss-accidents, no flat tires, and no mechanical issues with the car. We didn't spot any drivers that looked like they were having trouble staying on the road, and we didn't even drive past any recent accidents. There was some road construction, but only on 50 or so of the 3,600+ miles we covered.

Aside: Bugs
So if we had no mechanical or tire issues or accidents, what was the most annoying car-related issue? Probably bugs. Not in Tesla's software, but the real kind…so…many…bugs!*To really see the splatter, click the image, then click the icon at the top right of the window that opens for the full-size version

Splatter zone

I did my best to ignore the bugs on the front (though I did scrub them off once, in Colorado), but the windshield was another matter—it's hard to drive when looking through a layer of bug detritus.

For that problem, we packed a can of foaming window cleaner and paper towels, because there aren't typically squeegees and water at Tesla Supercharger stations. This stuff works great, and is so much neater than the squeegee/water solution that we've switched to it in our other (gas powered) car as well.

[continue reading…]



3,641 miles on 0.0 gallons of gas – Part One

In August, my eldest daughter (Kylie) and I completed a long tour of the western states, visiting college campuses. The linked post discusses the steps we took to try and keep ourselves and others safe from COVID during the journey…these next two posts*Due to the length of the topic, I'm presenting it in two parts. are all about the practicalities of doing really long distance tours in a fully electric vehicle.

Today's post covers the trip planning and preparing the car for the journey; tomorrow's post will cover the actual drive, the charging experience on the road, and summarize the good and the bad of undertaking such a journey in an electric car.

Our electric car is a 2016 Tesla Model S, which we purchased in early 2019. This is our second 2016 Model S; with the first car, I took a trip to Las Vegas and back, a round trip of about 1,700 miles. (You can read about that journey in Part Four of my series about the Model S.)

At 3,641 miles, though, this trip was over twice as long, and ventured further away from civilization—driving through Nevada, Utah, and Wyoming, there's a whole lot of nothing between the small towns along the interstates. This definitely led to some anxiety on my part as we planned the trip. As a reminder, this was our route:

So what was it like driving an average of 300ish miles a day (plus campus visits), 12 days in a row, in our electric car? Overall, it was a non-event, which is about the most positive outcome I could have hoped for. But that doesn't mean the trip was as simple as it would've been in a gasoline powered car.

[continue reading…]



Give your iMac a lift

I have a 2019 27" iMac, which replaced a Late 2014 27" iMac. Both of these are/were placed directly on their stands on my desk. I've always felt that the screen was just a bit too low to be ideal, but I was too lazy to deal with solving it—especially as I knew it meant I'd also have to deal with the mess of cables on the desk behind the iMac.

Then last week, I saw MacRumor's review of the Twelve South Curve Riser iMac Stand, and thought it might solve my problem. But at over four inches (10cm) in height, I thought it would be too high for me—with the height of my desk and chair, I'd wind up looking up at the screen. And, at $80 for just a bent piece of metal, it seemed expensive for what it delivers.

However, MacRumors also linked to their review of the Satechi Type-C Stand for iMac (view on Amazon), which rises a more-reasonable 1.63" (4.1cm) from the desk. But what really intrigued me was that for $90—just $10 more than the Twelve South riser—the Type-C Stand includes two card reader ports (at up to 104MB/s), three USB-A ports (5GB/s), a USB-C port (5GB/s), and a headphone jack.

The ports on the front were the deal sealer for me: My Logitech keyboard and mouse both charge over USB-C, and I'd been using my MacBook Pro to do that as I only have a USB-C to USB-C cable. I also do a fair bit with memory cards—my drone uses microSD and my camera uses a regular SD card. I'd been using a regular card reader that requires the fiddly task of putting the microSD card into a SD-sized card holder; the Satechi stand has two separate slots, so that fiddly work is gone.

As for the brand, I have a Satechi Wireless Smart Keypad that's been working flawlessly for five years, so I felt pretty safe making the purchase decision. It arrived on Sunday, and after getting everything set up, I wish I would have done this years ago.

[continue reading…]



Simplify updates to oft-updated text documents

Here on my blog, I've been tracking macOS release dates and rates for nearly 15 years—if I'm doing my math right, I've edited and republished the post 115 times since then. Until the most recent update, all 115 of those updates were pretty much done like this:

  1. Update a Keynote document that calculates the release rate data and contains the two charts in the blog post.
  2. Edit the text of the blog post in a text editor, with Keynote visible, replacing all instances of variable data—dates, numbers, size, rates, etc.—wherever they appear.
  3. Upload the graphs and publish the updated post.

While this isn't an overly complex task by any measure, the second step in particular has gotten more time consuming over the years, because of the length of the post: It now contains over 50,000 characters. That's lots of scrolling and looking for the few bits that change—and I'd often miss a date or a number in some portion of the post.

I thought there had to be a better way, and there is…and of course, the better way uses BBEdit. In particular, BBEdit's support for including one file in another—and using variables in the included file—makes my update task much simpler. If you have text files that receive regular updates, you may find this method of interest, as it can be a big timesaver.

[continue reading…]



Resolving ‘A problem repeatedly occurred…’ error in Safari

Update: Apparently this has happened again with Safari 14.1 on non-current MacOS releases. As of today (Apr 29), MacRumors has the package downloaders available for Catalina and Mojave:

https://www.macupdate.com/app/mac/15675/apple-safari

I can't test this for myself yet as I'm away from my Mojave iMac for a while, but hopefully it'll solve the issue as it did before.

Yesterday, after updating to Safari 14 on my Mojave-running iMac, I noticed a big problem: I couldn't load many sites that contained either a login dialog or a shopping cart. For example, I could load Target's main site, but when I tried to open the shopping cart, it wouldn't work.

I'd briefly see the page, then it would clear and reload once or twice more, and then I'd be left with an error message:

A problem repeatedly occurred with "https://www.target.com/co-cart"

This was happening on many, but not all, sites—I could login on Amazon and my bank, but not on most of our credit card sites or typical retail shopping pages. Given this happened just after installing Safari 14, I assumed it was somehow related to the new browser version—the same pages that didn't load in Safari loaded fine in every other browser I tried. But they loaded fine on Safari 14 on my Catalina MacBook Pro, so then I knew I had a Mac-specific issue…the worst kind of issue to troubleshoot.

While troubleshooting, I found that I wasn't alone, nor was this a Safari 14 issue—there are lots of reports of the same problem over many years.

After tweeting about my troubles and what I'd done to try to troubleshoot the problem, Jeff Johnson of Lapcat Software got me on the right track by suggesting that my Safari install was broken. He suggested I check the date on this Safari framework...

/System/Library/StagedFrameworks/Safari/libwebrtc.dylib

When I did, I found that the version on my iMac was much older (Jul 13, 2020) than the version on my MacBook Pro (Sep 15 2020), where Safari 14 worked as expected.

It seemed that the fix might be as simple as reinstalling Safari 14…but Apple doesn't make it easy to do that, as you can't reinstall an installed update, and they don't include recent Safari versions on their download page.

After some searching, I found MacUpdate's Apple Safari page, which contains direct links to many versions of Safari—scroll down to the section titled "What's New in Apple Safari," expand it, and you'll see download links for Safari versions back to 13.0.3.

I downloaded the Safari 14 installer1And kept a copy, just in case!, let it do its thing, and the problem is solved. The date on the framework I checked now reflects a mid-September date, which matches the same file on the MacBook Pro.

I'm annoyed that Apple's installer didn't report any issues, and I wonder what a "typical" user might have done to resolve this issue—I only got it fixed thanks to Jeff's tip and the installer links on the MacUpdate page. I can't imagine how long I would have had to talk to Apple Support before they figured out that it was a bad Safari install, and not some app or utility or other "you caused this" issue on my Mac.

So thanks, Jeff and MacUpdate, for helping me find and fix this very annoying problem with my Safari install!



Road tripping through a pandemic

In late August, my eldest daughter Kylie and I set off on a nine-state, 12-day, 3,500 mile road trip…no, really…

Why, during the heart of the COVID pandemic would we choose to do this? Because Kylie is a senior in high school this year, and after looking at the calendar and her schedule, we sort of figured this was her only real opportunity to check out some campuses before it was too late. The timing, obviously, wasn't ideal, but it was what it was. We had to figure out how to make it work as safely as possible.

We used our Tesla for this journey, which will be the subject of a near-future post: It was, by far, the longest trip I've ever taken in an electric vehicle.

[continue reading…]



Download and track Amazon purchases over time

Dec 18 2020 update: The Amazon export URL appears to be functional again, which is great news. However, the data is in a completely different format than what's provided by the Chrome extension, so it needs to be massaged to work with my spreadsheet. For now, if you want to use my workbooks, keep using the Chrome extension. I'll see about modifying the spreadsheet to work directly with Amazon's data.

Recently I was trying to enter our Amazon purchase details into Quicken—the transactions download automatically, but they're generically assigned to "Shopping." I was using Amazon's order history page to match transactions and assign categories, but it was slow and painful going given the layout of the orders page.

I thought there must be a simple way to download your Amazon purchase history—once downloaded, I could use a spreadsheet to search my transactions. As it turns out, there is a way, but it's far from simple. Nonetheless, after way too much work, I now have an Excel workbook that makes it very easy to find any of our historical transactions. I enter a year and amount on my Search sheet, and any matches appear immediately:

Getting from "this should be possible" to "it works!" was (as usual) more of a challenge than I anticipated, but it is now working as I wished.

[continue reading…]



A cleaner method for debugging windshields

Unlike gasoline-powered cars, my Tesla is rarely at a gas station. The chargers in Tesla's Supercharger network are occasionally located on or near gas stations, but they're more likely to be at a hotel or in an industrial area, meaning you're not going to find a squeegee and water bin for cleaning your windshield.

To solve this problem, I keep a roll of paper towels and a can of Zep Foaming Glass Cleaner in the back of my car. While the car is charging, I spray and wipe the front and side windows. I've found that bug residue easily wipes off; only the largest of bug stains require a bit of elbow grease.

A recent 3,500 mile road trip (more on that in a future post) really put this system to the test, and it worked quite well—each time we charged the car, we left with a nice clear view…which lasted for all of a few miles, of course.

The other advantage to this method is that it's way less messy than water and a squeegee; it's easy to keep the spray exactly where you need it. This works so much better than the old method that we've put another can in the back of our gasoline-powered car—no more squeegees and water (of questionable cleanliness) for us!

This won't work well if you've got a large SUV, though, as you need to be able to reach across at least half the width and the full height of the windshield…another reason to stick with sedans!



Two silly solutions for creating numeric passcodes

This morning, I was reading about Henrique Prange's friend's stolen iPhone, and the financial damage the thieves inflicted in only a few hours time—yikes! I've got six-digit codes on all my iOS devices, which suddenly felt like not nearly enough.

I also deleted all my iCloud info from the saved website passwords, as explained in Kirk McElhearn's article for Intego. There are some good recommendations there.

Then I set out to change my iOS passcodes…and me being me, I made it way more complicated than it needed to be. But first, a bit about passcodes on iOS…

[continue reading…]



Review: Logitech MX Keys for Mac

In April of 2019, I reviewed the Logitech MX master 2S mouse, which I really liked. Earlier this year, Logitech came out with the Logitech MX Keys for Mac keyboard, so I thought I'd give it a try. (I also upgraded to the MX Master 3 mouse at the same time.)

Executive summary: I love this keyboard. I was on a road trip recently, gone for 12 days straight with nothing but a MacBook Air (of the 'broken butterfly' generation). As soon as I got home and switched back to my iMac, I was reminded of just how much better this keyboard is than the one built into my Air…and the one that came with my iMac.

(Note: The "Mac" in the name simply means that you're getting a keyboard with Mac-specific symbols on the Command and Option keys; I'm pretty sure the Windows version would work just as well, but without the Mac-specific look.)

This review won't be quite as thorough as that of my mouse, mainly because there aren't as many nifty features—it is "just" a keyboard, after all.

[continue reading…]