ActivityPub over ATProto
Summary
The article proposes a design provocation: running ActivityPub atop ATProto with minimal changes to either protocol. It explains ATProto’s PDS and signed data concepts, uses actor documents to illustrate how ActivityPub endpoints could be discovered, and outlines practical hurdles (inbox method support, identity/handle alignment). It argues that ActivityPub and ATProto address different problems and could be complementary if bridged thoughtfully.