I sincerely share that thought, @BlackAzizAnansi.
But we can try to influence our instance's owner and/or implement the following safety precautions:
@HistoPol @BlackAzizAnansi there is much to fear about meta.
But there is no reason to think blocking them is actually going to achieve anything to "protect" us from them, not until there are clearer understanding of what bad behaviors to expect from them, and how federating with them would enable them.
For now, all the examples of abuse from meta i seen suggested, were based on meta threatening to de-federate us, so de-federating them in the first place is just getting there right away.
@HistoPol @BlackAzizAnansi this post by the Eugene is worth reading imho https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/
Absolutely. Thanks.
(1/n)
What part of your #Fedi data and presence will be @ risk when the #MetaHordes come galloping through #ActivityPub from #Threads?
Like his press release.--But while I do not dispute the technological facts #Eugen explains, and will not even say that some of his conclusions are erroneous, this text simply overlooks the cultural dimension, qualitatively and quantitatively.
We are presently...
https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/
(2/n)
...struggling to accommodate a few 100k #TwitterRefugees. My feeling is that there is a group effort to accommodate and welcome everyone. 
Let's even say these newcomers all become good #Fedizens in no time, embracing cultural aspects like #AltText right away.
This still leaves the 13m #Fedizens against (potentially) 1.400 mn #Metas.
(I know, not everyone will want to sign up with #Threads...)
Which leads us back to my chart of the ant-eater...
(3/n)
...and its ants...
Now, some pertinent excerpts from the press release:
"#Mastodon does not broadcast private data like e-mail or IP address outside of the server your account is hosted on. 
Our software is built on the reasonable assumption that third party servers cannot be trusted.
For example,...
(4/n)
...we cache and reprocess images and videos for you to view, so that the originating server cannot get your IP address, browser name, or time of access. A server you are not signed up with and logged into cannot get your private data or track you across the web. What it can get are your public profile and public posts, which are publicly accessible."
"By default, #Mastodon does not include any functionality to display...
(5/5)
...ads. "
And this almost(?) does it for me re/ #Threads interactions:
"Even if you follow or send a message to a #Threads user from your #Mastodon account, Threads will not be able to collect any of your private information except the message you sent."
After the #ActivityPub protocol goes live on #Threads, I need to constantly re-check whether I'm writing to a #Fedizen or a #Meta.
Thanks, but I think won't indulge.