As it says in the title, I’d like to learn about the most pressing points of confusion or connections people would like to tease out or agree on together:
What are you stuck on and would like some shared brainpower on?
What do you have some solution for, but are still unsure you have the right one?
Where would you most want to interoperate, or are most afraid implementations will drift?
What are you worried we won’t collectively think about until it’s too late?
I’d also like to learn about the less pressing (but still important) points, but it’d be nice to know where people’s priorities are at this will definitely help inform next steps—not to mention the bonding exercise over shared struggles or worries.
I haven’t had the chance to think about my answers yet, so I’ll be back later with some! I know I’m always worried about standards not thinking about my Astro sites, floating in the web as their own self-contained small islands disconnected from any specific platform.
I think the most pressing use-case from my perspective, where standardization feels important, is having a way for other apps to understand and contribute to a community from different applications.
Like I want you to be able to create an organization or community in one app, and then be able to log into another app that will also be able to recognize it and allow you to manage the community, as appropriate, in the new app too.
That’s pretty fuzzy, since it’s kind of like saying “having ATProto apps interop with each-other”, in which there is a whole spectrum of compatibility rather than a binary, “interoperable or not”.
But I guess the big thing I want to avoid is you having to create a new community in each of the different apps, even for the same community, because the different apps can’t coexist over the same community DID.
The community arbiter I’m working on, which will eventually act as a space host in the permissioned data proposal, and which we are hoping to have a working proof-of-concept of this week!
This POC will actually not focus on permissioned data at first and it will be immediately usable to provide “programmable” org accounts for the wider atmosphere similar to opensocial.community. We’re hoping to have an integration with Blento this week if possible.
More details on that soon. I’m hoping to make some stuff so it’s easier to learn about and get feedback on.
Ooh, yeah, I like that perspective, because I’m very interested ( vaguely ) in how these kinds of things might allow you to be as independent as much as you want.
For example, I want to be able to self-host my community, and have a domain where you can only interact with my community, while still being connected to the wider atmosphere if other people want to connect with other domains.
Honestly been kind of taking things one step at a time, so a lot of y’all might be a little further along on other issues or things we should think about that I just haven’t gotten to yet.
Hi! Excited to see these conversations getting going I wanted to chime in here as I’m getting back up to speed after getting into a new gig (at Bluesky!)
I originally created OpenSocial with the intention of trying to understand how interoperable/cross-app communities could work in ATProto, and also with the plan to move some of the community structures onto permissioned data once it was ready. I think this is a really exciting space that could lead to some very cool apps!
I’m in agreement with Zicklag here; this seems like a thing that’s worth coming up with a standard on just so that we can clearly understand from the app development side what is a community, when it should be rendered, and how different apps interoperate with a single community. I’m not personally on the Bluesky app team, but am gonna be spending some time with the Bluesky app crew to gather hard requirements from the Bluesky app side, and am also curious what this may end up looking like from the perspective of OpenSocial.
Would anyone be up to a call or stream some time next week to chat through it a bit more? It’d be great to get together and share each of our requirements so we can start to understand what this will end up looking like!
this will definitely help inform next steps—not to mention the bonding exercise over shared struggles or worries.
I wanted to chime in here as I’m getting back up to speed after getting into a new gig (at Bluesky!)