@matigo There was still a SuperDuper! app backup available, not needed. It turns out the backup clone that I restored from using Carbon Copy Cloner had actually been cloned using SuperDuper! app.
I reckon shirt-pocket.com could do us all a big favout by dropping the exclamation point from the end of therir app’s name.
@variablepulserate Snapshots came along with High Sierra and are taken every hour by time Machine, they are generally no more than 2 GB maximum. Prior to APFS, only laptops saved local backups (as they were previously known) but all Macs using APFS create snapshots. Snapshots are also saved very quickly.
More info here: https://www.lifewire.com/roll-back-apfs-snapshots-4154969
The Mac had been super-sluggish, my G3 Pismo PowerBook from 2000 was faster! It wasn’t connecting to the internet, no matter which process I tried.
With Carbon Copy Cloner being so quick & successful, I resolved to make those backups more frequent.
Update: three hours after the restoration attempt: success. Mac restored & working fine. Time Machine failed me for the first time since 2007. Restorations from both a system snapshot & a 4-day-old Time Machine backup failed to have any beneficial effect.
But I make clones, too, using both Carbon Copy Cloner & SuperDuper! apps. I chose to use CCC for the restoration, its clone was on an external SSD.
Booted from that, made sure all apps were updated & restored it. Took under 15 minutes, transferred 6.6 GB data.
Mac is fine now.
Frustrating. Closed the MacBook Pro’s lid last night with a YouTube video running. Today the bloody thing was too sluggish to work effectively. Worked fine when booted from an external SSD. Tried restoring from an earlier system snapshot, no improvement. Now restoring from a four day-old Time Machine backup.
Cat experiment. Place cat on table beside computer desk. Place various items on said table. Watch surreptitiously as cat plays with item and sends it to the floor.
In September I deactivated two licences for iMazing app on my iMac & MacBook Pro because I had taken up a Setapp subscription which included that app.
Yesterday an email from Setapp informed me that iMazinf was being disassociated from Setapp by its developers on Dec 27th & that Setapp was in the process of enabling a similar replacement app.
Any version of iMazing currently rersiding in the Setapp folder would keep working but not receive updates. If uninstalled from Setapp, andy instances of iMazing would need to be licenced versions.
Just finished deleting iMazing from Setapp on the iMac & MacBook Pro & reinstating the licenced versions from the iMazing website.
I also had to perform new backups of the iPad, iPhone & iPod Touch but as they were only incremental backups, little time was needed for the operation.
@hybotics There is the Counter.social example as a different way. It started as a Federarted Mastodon Instance but became a more isolated aspect when, for “security” reasons Federation was turned off. Also, the founder of Mastodon isn’t so keen on that non-Federated part, but it’s an option.
You would certainly be able to set up an instance then isolate it from outside by shutting down Federation. It will work with existing & new Mastodon app, too.
// @matigo
25,500 km driven in the last twelve months in the car I bought exactly a year ago.