To real concerns that Meta might do to Acivitypub as Google & they did to XMPP, this seems helpful including this point via
@darius
"Regardless of bigco shenanigans around open protocols, Kazemi isn’t worried about what happens with ActivityPub. 'The nice thing for me is that if the big companies do jump in [to support ActivityPub] and then sort of walk it back,' he remarked, 'at worst, we’ll be back to where we are right now, which is still a pretty nice place.'”
https://thenewstack.io/why-developers-should-experiment-with-the-fediverse/
@tchambers @darius Seems like that kind of ignores the "extend" part of #EmbraceExtendExtinguish... When they start adding their own weird, undocumented stuff on top of #ActivityPub and then all of the real #FOSS activitypub clients don't/can't implement it, then most people are going to blame them for being broken, rather than GoogBook for not following the standard. Then people learn that only MegaCorps clients "work right" and stay there when the clients stop using activitypub all together.