Thinking about how communities can manage shared data on and off ATProto
Evaluating permissioned spaces for community contexts - meri's missives
A look at Bluesky's proposed approach to private data on ATProto
Rashid Aziz: Extending ATproto for private data - ATProto Community
The Community Manager Pattern - Nick's Blog
This post looks more closely at Brittany Ellich's work on representing groups in ATProtocol. It builds on earlier conversations and explores how these ideas might work in practice.
Roomy and community organizing for system change
Roomy is a group messaging app that gives online communities tools for autonomous collaboration — designable spaces not just for chat, but for cultivating a web of shared understanding together. We show how cheap, user-controlled, interoperable data on ATProto can enable online communities to channel impassioned mobilizing into sustained organizing in the shadow of Big Tech's empire.
What ATProto Needs to Support Consentful Distributed Community Governance
[Proposal] WG for group/community standards and infrastructure in ATProto
Interested in contributing — specifically to Phase 1 (shared ontology and community archetypes). I’m a cognitive linguist and university researcher. My work on the AT Protocol side includes Mezzanine, an information networking system using opaque cashtag connectors as a routing layer, and two Leaflet pieces on community infrastructure as a gradient — from permissionless tag-based commons to credentialed spaces. The reason I’m flagging my disciplinary background: Phase 1 is where this WG will e...
Live Call: Communities & Permissioned Data for Roomy.space
Permissioned Data Diary 2: Buckets - Daniel's Leaflets
The second in a series of posts building up a solution to permissioned data on atproto. We introduce buckets: a new protocol primitive for creating a shared social context.
ATProtocol Community
A community space for coordinating, convening, and collaboration around ATProto
ATProtocol Community
A community space for coordinating, convening, and collaboration around ATProto
Representing groups in ATProto
I wanted to add book clubs to my GoodReads-like app (Collective), but ATProto doesn't have a standard way to handle shared group resources yet. So I'm building opensocial.community—a separate service that manages groups independently from any single app. This means the same book club could potentially work across multiple apps (imagine your book club having both a reading list in Collective AND a discussion forum in another app), and groups can migrate between providers if needed. It's probably over-engineered for my use case, but might help other ATProto developers building community features.
Representing groups in ATProto
I wanted to add book clubs to my GoodReads-like app (Collective), but ATProto doesn't have a standard way to handle shared group resources yet. So I'm building opensocial.community—a separate service that manages groups independently from any single app. This means the same book club could potentially work across multiple apps (imagine your book club having both a reading list in Collective AND a discussion forum in another app), and groups can migrate between providers if needed. It's probably over-engineered for my use case, but might help other ATProto developers building community features.
I wrote my first #atproto community discourse topic. Pretty simple idea, but can be a good groundwork for private data, group-owned data or off-protocol data.
[Proposal] AT-URI for cross-service records
discourse.atprotocol.community
