Atmospheric Group Terminology and NSID

The current proposal for interoperable groups is called “opensocial.community”. There have been a number of scattered discussions about changing the name, as well as related terminology questions like what product features built on it might be called, what should show up in OAuth consent screens, etc.

I think it is important to get this settled sooner than later, and am creating a dedicated thread for proposals/discussions.

Notable previous conversations:

2 Likes

Here is one proposal:

  • a “group account” is a dedicated network identity (DID+handle) that powers an “atmospheric group”
  • an “atmospheric group” is the pattern of organizing multiple individual participant accounts in an interoperable way that works across app modalities and software implementations. The core of this is data localization and consistent group access/visibility across apps of different types.
  • this WG is standardizing an interoperable way to manage atmospheric groups (membership, roles, moderation, etc). We expect this to be the most popular way to implement things, but there might end up being alternative/competing ways to go about it, and that is fine. The goal is to be the “default” and most broadly interoperable system, not a “universal for all time” system.
  • we use the intermodal.group domain (group.intermodal.* NSIDs) for this specific standard. Developers and protocol folks refer to it like “the intermodal implementation of atmospheric groups”
  • “atmospheric groups” is the terminology that comes up in application and OAuth surfaces, and is how folks talk about this functionality generally (“a cool benefit of SportsApp app is that it uses atmospheric groups, so you can use CalApp for calendar events and visibility just works”)
  • folks can use basically whatever terminology they want for product features: group, circle, organization, team, club, etc. “an OrangeApp Team is just an atmospheric group”

I think “group” should appear in the NSID we go with, but I’m not strongly opinionated about intermodal.group specifically. Something wonky/specific works well to signal that this is an implementation thing, not the broader concept. It could also be something like opensocial.group. “Standard Group” in analogy to “Standard Site” is sorta nice.

9 Likes

I’m for it as described. No strong feeling between intermodal.group and opensocial.group.

1 Like

Sounds good to me.

Re intermodal.group I do feel like it’d be good to not use “opensocial”.

I think personally that’s mostly driven by the way it didn’t feel good when the Social Web Foundation was formed and it felt like it was basically saying the “Social Web” is ActivityPub, without acknowledging the other equally “social web” protocols such as ATProto or Nostr.

I’m not saying that’s quite what we are doing with opensocial.group, it just feels like it’s a bit overloaded to be used as a way to refer to a very specific group standard on ATProto.

2 Likes

Tagging @erlend.sh @essentialrandom.bsky.social @brittanyellich.com for input.

1 Like

I agree with just about all of it.

I’m using my own domain for NSIDs as I experiment. I’d love to contribute to and point at a standard.

I like something in *.group. Leaning against OpenSocial because I’m confused by naming collisions.

1 Like

I’m not sure I have a super strong opinion here, intermodal.group is fine with me!

2 Likes

Intermodal group is a cool name, though i wonder why not use a word like atmospheric if the expectation is that the popular terminology will be “atmospheric groups”. Is the goal to disambiguate between the concept of atmosphere groups and the reference protocol?

2 Likes

Is the goal to disambiguate between the concept of atmosphere groups and the reference protocol?

Yup, I tried to address that in my post. I think “atmospheric group” is the concept and design pattern, and intermodal.group is a specific implementation of it.

2 Likes

+1 for intermodal.group.

As an update, the tangled repo and current version of the proposal use opensocial.group.

I’m now leaning towards that name personally. It is a bit friendlier, retains more of the history of this WG and Brittney’s original proposal, etc.

It would be good to settle on a final name soon. I don’t think this WG has a formal consensus process, so i’m not entirely sure what that will entail. But definitely if you would have a problem with that being the name, or have a counter-proposal, weigh in soon?

3 Likes

Yeah, as much as I some initial, light opposition to it, at this point it feels like we could just go with it.

Intermodal is a little starkly nerdy, which isn’t really a pro.

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! :slight_smile:

7 Likes

I agree with this (as part of the unfortunate politics of this work); I’m leaning towards intermodal.group or what the person above suggested, atmosphericgroups.org (although IIRC there’s a bit of a difficulty in registering .org addresses nowadays, don’t they check for 501(c)3 (or equivalent) status? Failing that, atmospheric.group could work in itself.

atgroups? ATGroups? Atmosphere too long IMO

Unfortunately after over a week of in-depth research on domain names, none of the more optimal ones are available.

We do have atmosphericgroups.org registered already!

I would lean away from intermodal.group for reasons number 1 and 2.

1 Like

Similar issue here, none of the domains are available. And tragically at.group is thousands of dollars a year, otherwise that would be my vote haha :slight_smile:

I personally balk at first at the term “intermodal” 9 times out of 10 even though I know what it means. It just isn’t a concept that sits in the lower, more rudimentary levels of my brain. It requires higher-level thought to conceptualize what it means, and requiring that for a fundamental word in the spec seems unwise.

I like the idea of atmosphericgroups.org as the NSID. “Atmospheric” makes a lot of sense in the name, and “groups” has a lot of inertia here and I can’t think of a term that fits better. Although, to be clear, how do Atmospheric Groups relate to spaces? I’m assuming an Atmospheric Group is just one implementation type of a space. What exactly do Atmospheric Groups afford you? Can you have a “type” of Atmospheric Group, with an inheritance kind of thing?

Basically what I’m getting at here is that if an Atmospheric Group is only one type, and it’s rigid, and it defines only one way to do moderation, roles, membership, etc., that doesn’t seem flexible enough to be the “default” way people do groups on the protocol, it just seems like the way one specific usecase does it. And I’d much rather just have some sort of template types for things like moderation, roles, membership, etc. that anyone can plug in if they want to use them than one “standard” way that’s super rigid.

I love atmosphericgroups and atmospheregroups. Personally I think that atmospheric sounds cooler but is also a bit weirder and not a term most people will know :joy: atmospheregroups leans on the word atmosphere which I think is good, that’s already something we will be putting effort behind branding more.

I agree with the branding arguments here in favor of using something like atmosphericgroups.org over opensocial.

I personally feel like “atmospheric groups” is probably better than just “atmosphere groups” because “atmosphere group” sounds like a group of atmospheres, when there is really just one Atmosphere.

I agree here. It’s pretty opaque feeling. I don’t know where I learned what a “modality” was, but it’s not a very common word.

Also the term “modal” even has an AI association at this point with multi-modal being the way they refer to Text+Image AIs, etc. and there will probably be people who draw an association and just dislike it for that reason, even if it doesn’t have an actual relationship to AI.

It is a rigid, specific type. And yeah, there will be other “atmospheric group” implementations that would be perfectly valid to call “atmospheric groups” I think. Really anything that implements groups on top of ATProto spaces should be considered an atmospheric group implementation.

That’s the biggest argument I see right now against using atmosphericgroups.org.

At the same time, I do think it makes sense that we should market this as the “default” implementation. The network will benefit from having a default right out-of-the-gate I think because interoperable groups are extremely valuable and consensus is hard to build. Getting this out to people as a capable first try for integrating groups will go a long way I think.

So from that perspective, maybe having org.atmosphericgroups, as the NSID is totally reasonable and not a strong enough argument against using the name. It’s not claiming that it’s the only standard, but it is making a claim to being the default standard.

The only real fear I still have at this point is that when talking about atmospheric group standards in the future, every time I say “atmospheric group” I’m going to have to clarify it by saying the “atmosphericgroups.org one” to differentiate it between the other implementations.

Again, just to take the perspective in the other direction, though, those other standards will have their own domains, and, we’ll probably just call them things like “the message garden group standard” or a “somebrand max group” or whatever name these other group standards use.

So in the end I feel like there is a little bit of conflation between atmosphericgroups.org as a specific implementation of “atmospheric groups” as a general concept, but I don’t know of an actually better name for this project at this point, so it’s the best option I see so far.

2 Likes