Why isn’t Bluesky p2p?

Bluesky's AT Protocol moved away from the pure peer-to-peer designs its founders built earlier, keeping some of their properties while using servers instead of user devices. The article describes the early P2P projects (IPFS, Secure Scuttlebutt, Dat, WebTorrent) and their problems, including the introductions problem, unreliable DHTs, and resource limits on devices. Bluesky instead uses Personal Data Servers for hosting, a did:plc registry with a Certificate-Transparency-inspired log, and large AppViews for aggregation. The author calls the result "Internection," a term the article says is not yet settled and that the team is not fully behind.