Luke Kanies critiques ATProto private data architecture
Puppet founder Luke Kanies critiques Bluesky's ATProto for treating private data as a separate, overcomplicated subsystem rather than a core permission layer for local-first applications. He argues that public and private data share identical schemas, warning that splitting them forces developers to maintain redundant sync engines and parallel data flows.
Hot Take: ATProto risks repeating Web2's mistake of treating user privacy as an afterthought, creating architectural fragmentation that undermines its promise as a universal application protocol.
- –Artificial Data Split: Kanies highlights that private and public user data (e.g., restaurant or book reviews) share identical schemas, meaning access control should be a permission parameter rather than a distinct protocol subsystem.
- –High Developer Overhead: The proposed "permissioned data" design obligates developers to maintain dual application logic, storage mechanisms, and sync pipelines for public vs. private states within the same app.
- –Lack of True Local-First Capabilities: Unlike Git, ATProto relies on client-server protocols with remote Personal Data Servers (PDS), requiring developers to build custom offline storage engines rather than enjoying native offline-first sync.
DISCOVERED
3h ago
2026-07-23
PUBLISHED
5h ago
2026-07-23
RELEVANCE
AUTHOR
speckx