Hilarious. Someone would have got a nice retirement out of that. It's amazing that some people have the power to sell a slice of the entire population's financial transactions for the next 25 years.
I'd run the numbers and AWS and Amazon's ad business together accounted for 100% of Amazon's market cap. The e-commerce division is essentially worthless as far as Wall Street is concerned, other than a loss-leader inventory source for the ad business.
France doesn't extradite its citizens, even absolute scumbags like Roman Polanski. Someone like Musk has lots of lawyers to gum up extradition proceedings, even if the US were inclined to go along. I doubt the US extradition treaty would cover this unless the French could prove deliberate sharing of CSAM by Musk personally, beyond reckless negligence. Then again, after the Epstein revelations, this is no longer so far-fetched.
I use a self-hosted healthchecks.io watchdog timer instance to monitor jobs like these and alert if they don’t complete. Of course TimeMachine doesn’t have a way to signal successful completion, unlike, say, Carbon Copy Cloner. Given Apple software quality’s accelerating downward trend, I’d suggest switching to rsync/rclone instead, or Borg/Kopia if you want GUI-driven restores for non-technical members of your family.
It’s long past time you flipped the bozo switch on Apple, the title of your blog notwithstanding.
I never trusted Time Machine, my primary line of defense is rsync to a server running ZFS with hourly snapshots, and weekly rotations of offsite drives. For bootable backups, Carbon Copy Cloner.
I am a long-time CCC user, but bootable backups haven't been supported for a while now, basically since Big Sur -- if you're counting on that, make sure you're testing it regularly.
+1 for TM to ZFS - although over samba. A ZFS snapshot at each successful disconnection means any occasional corruption is simple to rollback.
Also I’m using nightly Arc backup to B2 of critical files.
It is extremely flaky on GrapheneOS, at least on my Pixel 8 Pro. Just typing Ctrl-D to exit will corrupt it, requiring a full reinstallation of the Debian VM
The built-in terminal app seems to be similarly flaky on my Pixel 8. Also, the kernel it boots into is really stripped down, and it lacks a ton of essential features. I was not able to install VirtualHere client to pass through USB devices, and there's no built-in functionality. There's also no way to open it full-screen on the Pixel 8's DP-over-USB-C desktop mode. Hopefully it continues to improve, but it seems like Google is more into extracting value than they are improving their products at this point.
Oh wow. I did a very basic test this morning `ping google.com` and then ctrl+c and it seemed to work okay. Not done any more extensive testing than this though.
Could it be that it's just very flaky on all pixel devices? Or maybe something graphene is doing to harden the OS doesn't play nicely with how it's been implemented?
reply