Artair Geal

If it worked, more power to you, but I make it a habit not to forcibly mount and poke around in Time Machine backups outside of the supported OS methods. The amount of risk varies, but there’s always the chance you could do something to corrupt the backup set, and then you lose the whole enchilada. That’s usually more risk than I’m willing to assume.

This is why I leverage iCloud storage heavily. If my M1 MacBook Air died tomorrow and something horrible happened to my Time Machine drive, I could still pull things down from the cloud regardless of OS version. Couple that with ADP (Apple Data Protection), and it’s a pretty safe and secure way to share files between systems.

Unfortunately, size DOES matter. Is this card over 32GBs in capacity?

https://support.apple.com/guide/disk-utility/file-system-formats-dsku19ed921c/mac

No, Apple Silicon-based Linux is why VMware Fusion exists. 😉 You can currently virtualize ARM-based distros, but if this new release leverages Apple’s implementation of ARM for M-series chips better, I’ll probably create a new VM and migrate what I need from the old one.

You have the situation in reverse. Ventura is the latest edition of the operating system, which is where the backup was made. High Sierra is a few versions back. So he’s trying to restore a backup that contains some OS-specific elements to a far older operating system. The progression is High Sierra->Mojave->Catalina->Big Sur->Monterey->Ventura. So this is an OS that’s five or so releases back, dating to 2017.

Clarification: I know he’s just trying to look at it in Finder, but Apple’s got plenty of “baby rails” to keep people from corrupting their operating systems. This is, for example, why SIP (System Integrity Protection) exists. Thou shalt not touch the kernel.

deleted by creator

deleted by creator

deleted by creator

Time Machine doesn’t just do simple documents and such. It does pick up some OS-related elements. For example, Mail and Photos often get updates that make them less than fully compatible with older versions, ergo restoring data files for them could break them. For this reason (and likely others), I would imagine Apple has blocked this backup restoration path.

I’m guessing you can’t even see the files because the OS can’t “adopt” the backup set, and is trying to protect you from manually deploying anything from it that could corrupt your OS and apps. Additionally, Apple may be trying to protect the backup data’s integrity for the system that made it.

You would need to bring the High Sierra machine up to Ventura (if the system will take the upgrade) and then have the upgraded system “adopt” the backup.

Absolutely no surprise there. When you keep the barrier to entry low and throw in an algorithm to increase “engagement” via outrage, the soup turns to poison quickly.

This is why every time someone says the Fediverse is “too confusing,” I just smile and nod. That attitude of petulant, lazy, self-imposed gatekeeping is what’s keeping the Fediverse a much nicer place to be.

I use masto.host for my instance. They even give you a web GUI for all the settings. Makes hosting so much easier!

This is why I use a paid host for Mastodon. Six bucks a month gets me my own instance with a custom domain and full admin rights.

There are three of us on said instance, and only two of us are active. It’s easier to build a consensus that way. Absolutely none of us want to federate with anything Meta/Facebook. I preemptively blocked threads.net yesterday. To quote Khan Noonien-Singh:

“Let them eat static.”

This is the problem with modern social media in general. It’s no longer about being “social,” and all about trying to make a buck. Every time someone complains on Mastodon about their “engagement,” my eyes roll.

Fortunately, corporate social media seems eager to cut its own throat: https://www.nbcnews.com/tech/social-media/elon-musk-twitter-mark-zuckerberg-changes-facebook-social-media-tech-rcna89766