Can anyone help me understand what any Mastodon instance can possibly stand to gain by federating with Threads? The size disparity is absolutely massive. Anything going to Threads will be lost like a drop in the ocean and anything coming from Threads will be a deluge that drowns anything on Mastodon. You can limit your instance to only one of these but it's still bad.

Following Threads posters from a Mastodon client sounds ok at first, your users can get lots of Threads content, they get accustomed to it, and one day Meta changes the protocol and now you have to decide if you're a Mastodon or a Threads client. Or your users start wondering why they're using a subpar Threads client when most of their content is on there.

There's a false dichotomy about about storing #DogShit in your refrigerator: don't do it, or just smear it all over the entire interior.

I can't speak to other appliances, but refrigerators offer a third option: partitioning the dog shit. This can be for anyone with a refrigerator.

• You can select a dedicated area for the dog shit, like the vegetable drawer; users will know it's full of dog shit because of the warning provided by the smell.
• People who don't open the vegetable drawer won't have to see the dog shit.
• You'll have to manually open the vegetable drawer to access the dog shit.

Basically, it puts the dog shit in quarantine, without taking up all the interior space for your food.

I like that option for our refrigerator, social.poop, and it's the one we voted to implement earlier this year.

We know that dog shit already hosts biohazards (e.g., Giardia). We know that some reasonable folks have already stepped in it while attempting to dodge some other kind of shit.

This option makes it clear that dog shit isn't safe to store in your fridge, while allowing coprophiles to do exactly that.

Every household will implement the option that makes sense to them, of course.

This doesn't solve the problem of sending Threads a copy of absolutely every bit of activity that happens on the instance. If I'm on an instance that federates with Threads, even if I put them out of sight/out of mind, they still get a copy of everything I do. A lot of people are on the fediverse for privacy reasons, yet here we are with people begging to hand Facebook this data on a silver platter.

"But why hide information that's public? They could just scrape it."

Yes, they could. But a real-time feed of activity is more complete, easier to manage, and doesn't require them to go and build a scraping tool just for this.

If I don't want Threads to have any of my data sent to them, I should be able to choose without needing to leave an instance I've been on for potentially years.

people are so naive, agin and again. if anyone thinks this is anything other than facebook trying to kill the alternatives, they should look at the history of gtalk/xmpp.

mastodon is a viable alternative to twitter, and this means that anyone can go: "there can be other alternatives". like reddit/lemmy, instagram/pixelfed, youtube/peertube, twitch/owncast, etc. and this is not good for business.

but i want my knee jerk reaction to a static world! quit makin' sense!

I don't get it, I know the posts of these apps look similar, but these are two very different apps. One has verified users with phone numbers, with names and surnames, posting about their lives and selling products.

Well, actually mastodon would have more of those of it were bigger. But the content is different.

If mastodon users would just see the threads content, but not be able to interact normally, then I think it's obvious this is bad for mastodon and instances should defederate. But Facebook doesn't care about a few mastodon users either way. Maybe they just want an option to be a part of it when twitter goes down, try and get a piece of it.