ATProto Permissioned Data Proposal Draft
Summary
Bluesky has published a draft proposal for permissioned data on the AT Protocol, alongside other proposals for user lists, moderation, OAuth, and more, as part of their ongoing development efforts.
View Cached Full Text
Cached at: 06/23/26, 10:46 PM
bluesky-social/proposals
Source: https://github.com/bluesky-social/proposals
Bluesky Proposals
This repository is an informal collection of proposals which we have published for feedback. It’s used as-needed and has no official process. External proposals are not requested yet.
Please open issues and PRs to discuss the content.
0001 User Lists, Reply-Gating, and Thread Moderation
0002 Labeling and Moderation Controls
0003 Hashtags
0004 OAuth
0005 Ozone Moderation History
0006 AT Protocol Sync v1.1
0007 Moderation Report Routing
0008 User Intents for Data Reuse
0009: Moderation Report Granularity
0010: Client assertion backend
0011: Auth Scopes
0012: Infrastructure Abuse Notices
0013: Consistent References to DID Services
0014: Service Auth Audience Revised
0015: JSON Event Stream Encoding
Similar Articles
Private data in ATProto: Permissioned Data Proposal
This is a Bluesky proposal for adding permissioned (private) data support to the AT Protocol, enabling access control over user data in decentralized social networks.
Building on ATProto
Luke Kanies discusses his plans to build a suite of decentralized review applications on ATProto, sharing feedback from the Local First Conference and critiquing the protocol's current trajectory.
ActivityPub over ATProto
This article proposes running ActivityPub on top of the AT Protocol's PDS, arguing that combining the two architectures could offer better user agency and credible exit while maintaining compatibility with existing federated social media.
ATProto for Distributed Systems Engineers
Explains the AT Protocol architecture through the lens of distributed systems engineering, covering the shift from SQL to NoSQL to stream processing, and how AT Protocol externalizes these services for a decentralized backend.
There are no instances in ATProto
Explains why the concept of 'instances' from Mastodon/ActivityPub does not apply to ATProto (Bluesky's protocol), clarifying that hosting and aggregation are separate in ATProto's architecture.