It's a dilemma -- you're quite right that there's a tradeoff between reach and privacy. Personally, I have multiple accounts; this one for example tries to reach as wide an audience as possible, so it's on an instance that federates with Meta (and most of my posts are public) ... and I've also got a personal account on an instance that doesn't federate which i use for stuff where the goal isn't to get wide visibility (and most of the posts are unlisted, local-only, or followers-only).are you saying that even with authorized fetch and an instance that blocks Threads, we need local- or followers-only to keep Meta's nose out of our businessEven with authorized fetch and an instance that blocks Threads, there are some potential paths of information flowing to Meta indirectly -- for example replies from an account on an instance that doesn't block Meta can reveal your account name (and perhaps some additional information depending on what they say in their reply). Local-only posts can reduce the risk of that, as well as scraping. As to how much it matters relative to other risks ... hard to know.@datum @fembot @Em0nM4stodon