cross-posted from: https://kbin.social/m/fediverse/t/173527

Shared by @tchambers and originally written by @chipotle

With kbin’s microblogging integration I think this is particularly relevant for our community as well! It’s a great read please take the time to read the full post.

Relevant Paragraph:
“Look. At the end of the day, I’m a Mastodon partisan. But I don’t love its collective tendency toward self-important dogmatism. […]
[…]
The truth is, #Threads is not about Mastodon. It’s about Meta and only about Meta, and Mastodon isn’t important enough to them to spend the considerable effort that would be necessary to destroy it. It’d be awfully damn ironic if the Fediverse decides it’s become necessary to destroy itself to stop them.”

Also worth noting is that this post is not disregarding/dismissing precautions concerning Threads, as the author notes they would be inclined to silence Threads so that posts from there won’t appear in public feeds, but only in the home feeds of folks that choose to follow people on Threads.

And my personal relevant portions of this post are:

So if Threads isn’t trying to overwhelm and destroy Mastodon, why have ActivityPub support at all? Two answers. First, “Look, see? We’re open!” is not only perceived as a great talking point these days, it’s perceived as a regulatory relief valve. Look, see? ActivityPub! We’re open!

Second, remember that the business model for Threads is keeping you on Threads. If 95% of your friends are on Threads but 5% are over on that weird Mastodon thing, now you don’t have to use Mastodon to follow them! Just follow them from Threads! Woo! Will Threads be a good Mastodon client? No, but it just has to hit “good enough.”
[…]
The truly toxic idea, though, is that Mastodon instances should not only refuse to federate with Threads, but they should refuse to federate with other servers that do federate with Threads.