Post

atproto spaces is shaping up! we're getting pretty close to what I expect will be the beta spec. ("beta" meaning in-production on bsky PDSes with real users) however, there's still room to maneuver. if something in the alpha isn't working for you, this is a good time to bring it up!

The more we've been discussing this and putting into production, the less you're going to want to hear our feedback. 😂 (Don't worry, it'll work, but a healthy dose of yagni would make it better, I think)

The one thing that's already super annoying that we've already discussed is the fact that now we have multiple synchronization mechanisms for data that is possibly otherwise the same. Strengthens my theory that everything will just move to spaces, rip the firehose.

I think it'll just come down to the simple fact that all of our indexers now have two code-paths and two separate sets of semantics to track for data that's arguably "the same."

Without some sort of abstraction that elegantly handles that, I think whatever the motivations, folks will gravitate towards one or the other (and the one will be spaces, because most use cases require spaces at some level).

My other hot take is that the community stuff would benefit from active outreach before working to finalize it. We've thought a lot about what sub-groups look like for Roundabout, but haven't had the resources to engage – I don't think subgroups-in-spaces will factor into our implementation at all.