Step 1: Threads starts federating with mastodon
Step 2: mastodon users happily engage with threads, letting it become the biggest fediverse instance
Step 3: threads stops federating with mastodon
Step 4: mastodon users switch over to threads where all conversation is happening, leaving the fediverse deserted
More than 5 million people signed up within hours, let’s assume they will have 30 million users by the end of the month. I’m sure there are Mastodon users will consider switching to Threads.
https://www.marketing-interactive.com/meta-threads-garners-5-million-signups-in-first-few-hours
And not to mention the Threads app is a privacy nightmare. I’m sure they can figure out any fediverse user, If fediverse server remains federated with meta server.
One more thing, this mastodon server admin declined an invitation from meta
Plus knowing meta, they’ll problary select a handful of instances to federate with. Meaning this plan is stupid.
Mastodon.social is the biggest instance
There’s plenty of conversation already existing. Even my single user instance is barely keeping up.
Its not like this is how federation works, federation happens in 3 ways: a person follows a user, thus getting their posts, an instance follows a relay, which gets sent posts and spreads them back out like a vaccum, and 3rd boosting posts.
I don’t see threads changing all that much if people don’t follow those accounts, and or meta doesn’t follow relays and send their posts out through relays.
I can’t figure out what meta wants to actaully do.
I can’t decipher fully.
If your a big instance and don’t want to waste bandwidth, just block them.
If you want meta, block them from the federated timeline if you desire.
No one will guide you in what to do with your fedi instance.
