I’m a longterm member of fandom, which is something that brings many people online and historically found new applications of internet tools that the creators never could have envisioned themselves. It’s a powerful force, and is something that is near to my heart, and I was thinking about how the Atmosphere could be used for it. I wrote this Leaflet to describe an MVP form that could potentially be run on top of existing ATproto stuff today and business models to make it sustainable. My expertise is in design, so I’d love to know what other people think about this.
4 Likes
Also heyyyyyyyy design friend!
Welcome @brightperegrine.bsky.social !
Yes, the Permissioned Data Spaces / Community Groups that are coming are likely building blocks for what you’d like.
It should be possible to create more organized posting spaces within the Atmosphere, which sync up with fanart from Bluesky, meta essays from Leaflet, rambles from Pckt, and more. To this end, I am proposing a software infrastructure that allows non-technical people to easily create three pieces needed to operate a semi-open space: a feed that displays posts submitted to it, a roster of members, and a labeler that names community members with responsibilities within the space.
The Community Standards working group Working Groups > WG Community Standards is currently diving pretty deep into protocol bits sort of around this space.
But this is a custom app / group sort of thing.
We sort of have pieces of this at https://atmosphere.community - not currently listing rosters or inside group posts and not yet on permissioned data infra.
We’ll see what suggestions other people have!
Good of you to think of this, but I actually came up with this talking to Ms. Boba, so she got to see this early. 
She’s been really good at encouraging people like me to try contributing to this!
My impression is that the community standards working group is more for private content that doesn’t leave the community, is that correct? My idea with the community feed builder that people submit to is that it’s not necessarily private, just an organized space for it. The content would exist in people’s individual accounts, in public, and also be collected together in the community feed. For example, if someone makes fanart for the video game Baldur’s Gate 3, they upload it in the Bluesky client, then get an option to submit the post to the Baldur’s Gate 3 Art Community.
Edit to avoid doubleposting: I’m reading dholms.xyz’s “opensocial communities proposal” and it definitely has some stuff that seems relevant for this. I guess what I am proposing is a custom mini-app builder that creates something like the 2026 Atmosphereconf’s feed of all posts related to the 2026 conference, but instead of detecting and including posts that match the criteria automatically, it only takes deliberate submissions by the creators of the post.
Membership is defined bidirectionally. The community creates a membership record in the members space and the member in turn creates an acceptance record in the same space.
Two actions - assigning a role to a member and ejecting a member - are parameterized by the roles that they apply to.
Roles may entail certain conventions. For instance, the Bluesky app will likely special case the roles admin and moderator and give special UI affordances/badges to accounts with those roles in a community. Other roles may be treated as flair or metadata. A community is free to ignore the convention.
Each space in the community (both modality-specific spaces & opensocial.community spaces) has an open social access record. This record specifies which roles are able to view the space. Read access is enforced by the space host.