Honestly I think it’s far more mundane than that. I suspect it’s engineers at meta re-using an existing open codebase to kickstart a new product, then leadership further up the chain liking it for efficiency plus hedging on future compliance challenges

It could even be that ActivityPub solves infrastructure issues that have been quietly internally plaguing Meta and that’s why they’re excitedly embracing ActivityPub for Threads