OK, seen about a dozen posts today that start with:
"When #Threads federates with the fediverse..."
They go on to imagine some wonderful or awful scenario where the floodgates are open and #Threads becomes another #ActivityPub app like #CalcKey or #Plemora.
Maybe.... but what you are envisioning is really very unlikely. Threads is entirely algorithm driven. How's that going to work? Plus they have no interest in letting their captured users escape.
Be careful with these assumptions.
Realize that there is absolutely nothing contradictory about algorithms in #Fediverse platforms. Effectively that just comes down to a UI tweak, and any client or interface is perfectly free to implement whatever algorithm it wants.
Heck, keep in mind that newest first is itself an algorithm, although a quite simple one.
Further, one of the huge criticisms I have of #ActivityPub is exactly that it is so instance-focused instead of user-focused so that it does not really help people escape. #Threads would really be a good fit for that philosophy.
So #Meta would use federation to bring a bunch of content from us to its users, while offering to its users the chance to be heard by all of us, at least in theory. That's good for the company. That's good marketing for them.
I think you overestimate the downsides of Meta turning on federation.
@volkris Not trying to estimate the upside or downside. Just urging caution in assuming you know what they will implement. Plus, #Threads pawing through content across the #Fediverse and applying their algorithms to it does not seem like a simple matter either technically or #DataPrivacy wise at all. These are the kinds of details where it is best not to make assumptions.