Hey all, I haven’t been active in the discussions on this forum until now, but I wanted to join the conversation and introduce what I’m working on. Over the last few weeks, I’ve read through all of the past discussions in this Working Group to bring myself up to date.
Recently, I’ve been helping Chad Miller and the Atmosphere Team at Bluesky with work related to the spaces-based Groups that have been talked about here. My contributions are focused on a few key areas:
- Proposing a new design for the “promotional” website/docs, as well as the narrative, storytelling, and strategy for pitching Groups to key audiences.
- Working with builders, creators, and community organizers who are interested in using Groups.
- Refining the branding and formal name for Groups, which up until now has been referred to by several names, most recently “opensocial.group”.
In addition to all my Atmosphere and software work, I have over a decade of experience in branding, content, and storytelling, so I’m looking forward to leveraging that here to help Groups succeed.
After several weeks of exploration, research, and prototyping (plus numerous convos with Devin, Bryan, Daniel, and Chad), I’m feeling pretty certain that we should shift away from the “opensocial.group” name and pivot to “atmospheregroups.org” or “atmosphericgroups.org”. Both of these domains were graciously bought and held safe by Boris in case there was ever a need for them. There are several reasons why we should do this:
1. To avoid confusion and reduce the amount of explaining we need to do. As it stands, running with “opensocial.group” would likely require a lot of additional, recurring effort to pitch both Groups and the Atmosphere. The SEO and historical legacy of the term “opensocial” is another layer that complicates things further. Lastly, the domain itself doesn’t roll off the tongue, and in my opinion, it doesn’t look very credible.
2. To reinforce and stay narratively connected to the Atmosphere. If these Groups work as we hope, they’re going to become a major gateway into the Atmosphere and atproto, potentially one of the biggest entry points to date. We want to use this opportunity to ensure that everyone who engages with these Groups is seamlessly introduced to the Atmosphere by name, in a way that shows them how interconnected everything is. Having “Atmosphere” in the name makes this a lot easier.
3. To mirror and pair well with “atproto spaces”. We’d have “atproto spaces” at the protocol layer and “Atmosphere Groups” at the implementation layer.
One concern that has been raised about “Atmosphere Groups” or “Atmospheric Groups” is that the name might make this seem like the official or only way to implement groups in the Atmosphere. While I think this argument has merit, I don’t believe the cons outweigh the pros here. And, at the end of the day, using this name won’t actually prevent anyone else from doing their own thing.
I’m polishing up a preview of my proposed website design and narrative for “Atmosphere Groups” as we speak, and I’ll have that to share with everyone this week. I think it will further reinforce why this naming direction is more compelling and effective for our goals. Stay tuned for a link to that preview!
In the meantime, I’d love to hear everyone’s thoughts on running with “Atmosphere Groups” or “Atmospheric Groups”. With the Spaces beta rapidly approaching on December 1, it’s important that we continue to make progress here so people can start building with Groups as soon as possible!
Let me know what you think! 