Finally, I do NOT have to miss out on the cat filter fun “in real life”:
Twice as 25 as those other dot-com founders
Finally, I do NOT have to miss out on the cat filter fun “in real life”:
If you plan to break your iphone twice a year, AppleCare might makes sense.
But historically you’ve had at most one catastrophic damage event over a 2 year period, forget it… you pay $79 for 2 years, PLUS the $29 (for screen), which is MORE than just paying for a screen out of warranty. (iPhone SE)
The British elevate understatement to a genuine art form, don’t they?
For example the UK PM using “bumpy period” today to describe recent USA events in our capitol.
Orwell be proud.
TL;DR Formerly unusably-slow for backups a few years ago, the built-in Target Disk Mode in Macs has improved in latter-day Intel models (using a Thunderbolt 3 cable), now nearly 1/2 as fast as an external USB-3 drive dock.
My test: use Carbon Copy Cloner v5.1.22 to clone an internal SSD with 690GB of data. “Find & replace corrupted files” is OFF*.
Source: Macbook Pro 16″, Catalina 10.15.7
Targets: external SSD (usb 3) vs. 2020 13″ MBP (TDM, thunderbolt 3)
Result: Direct-connect two MBP using a high-speed Thunderbolt-3 cable was 5.9 GB/minute, about half as fast as backing up via USB 3 to an SSD in an external drive dock (12 GB/minute).
Keep in mind that two “trips” are required if the goal is to move the data to a new Mac via an external SSD (first from source -> external SSD, then from external SSD -> target)… so when you add the time it also takes to restore the external SSD to the target Mac (which I did not measure), the net time difference between the two approaches is less.
For my purpose, simply cloning Mac#1 to Mac #2, the direct-connect using Target Disk Mode was simpler and adequately-fast. YMMV.
Target | Connection | Time (690GB) |
External SSD, cheap Insignia Dual Dock | USB 3 | 56:32 |
Internal SSD of a 2020 MBP 13″ Intel (updated to Catalina 10.15.7) in Target Disk Mode, writing to a new APFS volume** | Thunderbolt 3, direct connect, using 40G Pluggable cable plugged into Left*** ports | 1:56:23 |
** Because APFS makes it so easy, I now keep the “out of box” OSX in the original APFS volume when I get a new Mac (as a backup bootable volume, updated to the lastest version of Catalina), use Disk Utility to add an empty APFS volume for work, then clone my old drive to that new work volume.
*** I didn’t test it myself to quantify any different, but have seen claims that the right ports have lower data transfer speeds.
When it was time to pay, my surf instructor today asked if I use Venmo.
Venmo has IMO ridiculously high default transaction limits (thousands of dollars) and does not (according to their support rep), give users ANY way to lower them.
Which seems like some evil bullshit to me, given they offer zero recourse in the case of a transaction that goes awry.
They advertise themselves (in big letters) as “Fast, safe, social payments”.
Who in the hell makes “social payments” transactions of $2,000, and weekly total “social transactions” of $4,999?
Okay, maybe some of you do.
But I’d guess most of us wouldn’t.
If they’d let users set their own lower limits (if desired, for example transaction limit size to say $100 or $150), I would use Venmo from time to time to make the occasional payment for coffee, splitting a lunchtab, or pay my surf instructor.
But, they are IMO too-clever, too-greedy asshats.
“No way,” I replied to to my Surfing instructor. He then pulled out his little Square reader, where I have far greater protection against transaction mistakes than Venmo’s lame policy: “Venmo Support can only reverse a payment if the recipient gives their explicit permission”
Transaction limit safeguard options are always Good.
Companies that won’t let you set them, and also provide no recourse in case of mistakes, are Bad.
If more people would “just say no to Venmo” (and tell them why) maybe they’d listen.
If I’m being honest, at first I might have been a little flattered when the Amazon chat support rep suggested I “bare” with him/her. It’s not my thing, so I declined, but still… nice to be asked. (Once we hit 60, those offers are few and far between.)
Then I realized, wait, maybe it’s just a new form of multi-factor authentication. After all it’s creepy how much info big-web collects about us, and webcams get hacked everyday, so maybe they just want to take a good look to ensure it’s really me, not some other geek in a button-down shirt posing as me, before they answer my question.
Problem: Apple 27″ Thunderbolt Display not working when connected to 16″ Macbook Pro (2019) via the Apple Usb-C to Thunderbolt 2 adapter. The display remained dark, despite have just been disconnected from an older Macbook running Mojave.
First (simplest) solution: Connecting a stand-alone Thunderbolt 2 cable from the Macbook adapter to the BACK of the Display worked fine, the Display works fine.
But since I was pretty sure the display’s T2 cable is fine (even if it did not work connected directly to the Macbook) I then tried putting a Thunderbolt peripheral between the Macbook and the Display (using the Display’s built-in T2 cable). And that worked too, freeing up the T2 port on the back of the Display!
Second (better) solution: Display’s built-in T2 cble connected to a T2 peripheral (and OWC thunderbolt dual drive dock in this case) and then the peripheral’s other T2 port connected to the Macbook’s adapter.
If you use other T2 peripherals, solution 2 is superior since it frees up the extra T2 port on the back of the Display.