This rings true, especially this part:
"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. In other words, users should be punished for decisions they have no control over and may not even be aware of, made by the administrators of servers they don’t belong to. I am dead serious when I call this toxic."
https://tracks.ranea.org/post/722507935765397504/youre-so-vain-you-probably-think-this-app-is
One of the reasons some are considering doing this is that they do not want their users content "relayed" onto #Threads.
If an instance fully federates with Threads (we still don't know any specifics of "federation with Threads", but hypothetically...), and they do not enable auth_fetch, then it seems like posts that the instance users boost will be transmitted to Threads.
Some do not want any of their content on Threads where it might be exploited by #Meta.
@mastodonmigration @tchambers @chipotle wait, shouldn't it be users that have a say what happens to their content? Since when are admins the ones entitled to take this decision? Maybe there are some consulting mechanisms I'm missing, but I'd love to be enlightened about the workings of some parts of the fediverse I haven't experienced yet
