一位开发者在参加柏林Local First Conference后，深入分析了ATProto协议的架构设计，指出其在支持私有数据方面存在根本性问题。[1]
该开发者计划基于ATProto构建评论应用系统，但发现该协议目前仅设计为公开数据协议，其设计和存储系统都是为公开发布而构建的。[1]虽然社区正在设计"权限数据"功能来支持私有数据，但这要求开发者实际上编写两个独立的应用程序。[1]
开发者认为这种设计方案存在根本缺陷。[1]他表示，私有和公开数据本质相同，只是权限配置不同，不应该被设计成完全独立的系统。[1]此外，ATProto的Personal Data Server（PDS）是一个远程服务器，不像Git仓库那样支持离线本地操作，这使得用户必须始终与远程服务器交互。[1]因此，开发者认为ATProto违反了Local First的原则。[1]
尽管对该协议的设计理念持有异议，该开发者仍然对ATProto保持积极态度，但指出如果协议的设计理念不改变，基于其进行开发会面临很大困难。[1]
A developer who attended the Local First Conference in Berlin has shared a detailed analysis of the ATProto protocol, highlighting fundamental limitations in its current architecture. [1]
The developer aims to build a commenting application system on ATProto but discovered that the protocol currently supports only public data, with private data implementation designed in a way that forces developers to essentially construct two separate systems. [1] According to the developer's assessment, this approach contradicts the ideal protocol design, as private and public data should be treated as inherently the same with only permission-based differences rather than as fundamentally distinct systems requiring separate implementations. [1]
The critique extends to ATProto's underlying infrastructure. The protocol's Personal Data Server (PDS) operates as a remote server that does not function like a Git repository supporting offline local operations. [1] This design means users must continuously interact with remote servers, which the developer contends violates Local First principles. [1]
The community is currently working on designing "permissioned data" functionality, but the developer views this approach as burdensome for developers who would need to write two separate applications to fully leverage the protocol. [1]
Despite these concerns, the developer maintains a cautiously optimistic stance toward ATProto. [1] However, the developer cautions that without fundamental changes to the protocol's design philosophy, development on the platform would prove difficult. [1]