Conversation

Notices

1. Embed this notice
   Evan Prodromou 🇨🇦🇺🇸🇬🇷🇵🇸 (evan@cosocial.ca)'s status on Friday, 26-Jun-2026 20:42:16 JST Evan Prodromou 🇨🇦🇺🇸🇬🇷🇵🇸

   • Emelia 👸🏻
   • Jörg 🇩🇪🇬🇧🇪🇺

   @thisismissem @AlienJay @julian exactly! This is that outreach. Em, it looks like Bryan is on sabbatical; who else do you think we should tag into the discussion?

   • Embed this notice
     Evan Prodromou 🇨🇦🇺🇸🇬🇷🇵🇸 (evan@cosocial.ca)'s status on Saturday, 27-Jun-2026 03:56:39 JST Evan Prodromou 🇨🇦🇺🇸🇬🇷🇵🇸

     in reply to

     • Emelia 👸🏻
     • bryan newbold

     @bnewbold @thisismissem awesome, ty! I think we're looking for something similarly flexible. It would be neat to make the pieces fit across the bridge.

   • Embed this notice
     bryan newbold (bnewbold@social.coop)'s status on Saturday, 27-Jun-2026 03:56:41 JST bryan newbold

     in reply to

     • Emelia 👸🏻

     @evan @thisismissem
     I am mostly on sabbatical this summer, but can give some more context.
     There are several active projects in the atproto ecosystem building features with non-public data, including https://habitat.network/, Blacksky, Northsky, and Roomy. We've been talking about adding protocol functionality for that since last fall or so. This overlaps with the concept of "groups", but folks could also do all-public groups. We had in-person conversations with all these projects in Vancouver this past spring (at AtmosphereConf), and have been working towards a "spaces" proposal. The current direction is to not bake much "group" functionality in to the protocol itself, but be flexible about how membership/invites/etc work, allowing multiple approaches. So there might not be a single system or set of schemas that would or would not align with something like AP groups.