Why isn't Bluesky a peer-to-peer network?

Bluesky's engineers explain why the AT Protocol is not a pure peer-to-peer network, though it carries many of its ideas forward. Their earlier peer-to-peer projects, including Dat-based Beaker and CTZN, ran into problems with introductions, multi-device sync, unreliable DHTs, and resource limits on user devices. Bluesky instead adopted a hybrid design: data is stored in Merkle Search Tree repositories hosted on Personal Data Servers (PDS), addressed by cryptographic identifiers, with the did:plc registry handling host lookup. Aggregation is done by large services called AppViews, and the authors call the model "federated" for lack of a better term while proposing "Internection" as an informal name.