ActivityPub of course uses the same cryptographic certification virtually all the web does, just TLS/HTTPS and relies on the host cert to be valid. But if you wanted to add further levels of verification like pubkeys and sigs, there's absolutely nothing stopping you.
I guess the race is on, then. Surely ActivityPub, with its much larger user and developer base, will grab the best ideas from AT Protocol and squash this redundant newcomer.
Seems based on that variable, ActivityPub has the benefit of being more widespread, but that tends to also make changes go through slower. ActivityPub being a specification maintained by W3C also make changes extra slow, but stable at least, while AT Protocol probably won't have any stability guarantees for a long time.
Sure you could implement BlueSky-over-activitypub, but would it be usefully compatibile with mastodon-over-activitypub? If not, why add the complexity.
Felt very much like in practice it just gives you tools to make mostly-insular federated apps, rather than letting different apps interact.
Have you seen the ecosystem study BlueSky published in 2020? https://gitlab.com/bluesky-community1/decentralized-ecosyste...
Bit more of a summary https://twitter.com/bluesky/status/1511811083954102273
BlueSky/AT Protocol seems to have pretty distinct design goals that are not possible with ActivityPub.