It still bothers me 30 years later that in the DC vs Marvel, Wolverine beat Lobo… Shouldn’t have happened to someone that beat up Superman because a guy at a bar said he couldn’t…

Just use Snapraid & MergerFS. No special Hardware required and you don’t need to change what is on your disks.

From a quick search: https://perfectmediaserver.com/02-tech-stack/snapraid/

This is how I do it. No striping, normal partitions, different hard drive sizes, pretty easy. This way makes upgrades super easy too. Currently running 76TB mergerfs with 2 14TB Snapraid parity drives.

I know that Pixel 7’s and above support it. There are Reddit posts showing they have the feature already. Satellite messaging is just using standard 4G/LTE from Starlink. I wouldn’t be surprised if this is only an OS update away for most newer phones.

Looks like it’s been available on some android devices for at least a month. I don’t know about free though, I think it depends on your carrier. I know T-Mobile has been talking about supporting it using Starlink satellites.

https://www.reddit.com/r/tmobile/comments/1ct1no1/satellite_messaging_option_appeared_on_my_pixel_7/ https://www.t-mobile.com/news/un-carrier/first-spacex-satellites-launch-for-breakthrough-direct-to-cell-service-with-t-mobile

This is the best answer I’ve seen in this whole thread. You’re right that the key is not needed. Microsoft identified your system components and did the original activation based on the hardware you’ve got on your computer. All you need to do to bring back a licensed copy of Windows is to reinstall it.

I get alerts on my Android for an Airtag I keep in my backpack all the time. My phone gives me the option to make the Airtag play a sound.

On Debian, you have to be root or a sudoer. Those commands are there, just not in the path of regular users.

Probably not that deep. I’ve heard there are definitely discounts. That doesn’t count for much though when it still increases your cost 6x.

This honestly sounds like the best solution to this particular problem.

Just make sure it’s RFC 2324 compliant. You don’t want it throwing any HTTP 418 error messages.

If you’re having power on issues, I would make sure you are using a standalone power brick. I’ve used a Surface Pro for work and I’ve found that sometimes when connected to the docking station, it wouldn’t power on. When connected to a standalone power brick it usually would. For a standalone power brick, I’ve used both the one that came with the Surface and also a 65W USB-C adapter with a USB-C to Surface per cable.