You're frankly uninformed on many levels, and while I'd normally refrain from replying to someone so obviously delusional, let's give a tiny peek at the problems:
AP is completely broken for anything but publicly-scoped content, relying on a lot of trust for every party involved. This gets broken frequently, and has had consequences so far on networks implementing it.
The specification itself is far too ambiguous. If you've got a lick of sense, you'd know this. But here's a post by a maintainer of Diaspora explaining this part further: https://schub.io/blog/2018/02/01/activitypub-one-protocol-to...
So let's assume you can get Twitter to implement ActivityPub perfectly to-spec. Great! It doesn't work with literally any pre-existing ActivityPub software, and users' DMs and are more or less public, with users' private accounts literally being public.