How should public community-controlled spaces be represented in atproto?
AT Namespaces for Community Spaces
How should public community-controlled spaces be represented in atproto?
Spatial Analysis - at:// pizza thoughts
Some dense protocol theorizing about atproto spaces
Spatial Analysis - at:// pizza thoughts
Some dense protocol theorizing about atproto spaces
Spatial Analysis - at:// pizza thoughts
Some dense protocol theorizing about atproto spaces
Community Spaces on AT Protocol - at:// pizza thoughts
Scaled-down design patterns
Atmosphere Community
A community space for coordinating, convening, and collaboration around ATProto
Where Does Community Live? - some responses - Connected Places
I agree that the architecture of a space matters, but I'm not sure the extent we agree as to how much a protocol really matters, versus what we build with them. Roundabout is built on atproto, and I'm quite happy with the decision. I think our architecture very strongly supports our communities.
ATProtocol Community
A community space for coordinating, convening, and collaboration around ATProto
ATProtocol Community
A community space for coordinating, convening, and collaboration around ATProto
WG Community Standards
A community space for coordinating, convening, and collaboration around ATProto
AT-Communities #1: the Concierge, the Vault, and the Fuck-ass Astro Website – Essential Randomness
In which I try to make sense of communities on ATproto.
Evaluating permissioned spaces for community contexts - meri's missives
A look at Bluesky's proposed approach to private data on ATProto
Reintroducing Spaces - Daniel's Leaflets
Zooming out and re-motivating the design of spaces, the new primitive for non-public data on atproto.