I think you have the right mindset about the most ideal approach, but how-to guides on how to do this *such that* it is only *a few days every few months* to ma

I think you have the right mindset about the most ideal approach, but how-to guides on how to do this *such that* it is only *a few days every few months* to maintain a setup like that are few and far between... as in there aren't any. Sure - same page, digital sovereignty isn't free, if you want it have to work for it. But, speaking as a technical securtiy user myself, and have worked with ghidra, I have zero context on how to take the approach you call for that cleanly strips out the bad stuff without buying me, what would feel to be likely, hours upon hours of troubleshooting dependencies for core functionality that I inadvertantly broke due to the surgery... such that I'm back to not carrying a smart device or being ok with a fliphone traingulating me. One approach I have thought through with effective (I think? still considering this) privacy outcomes is leveraging LLCs and related device plans as a "cloaking" mechanism. If my current phone stays at my house always, I travel locally with a fliphone, and travel with a network of smart phones under LLCs, that could be enough to throw off the tracking effectively while only (maybe?) exposing data that's already exposed in public records.