Post

This is the kind of infrastructure that makes the next wave of weird little products possible. Ship the alpha, let builders break it, then keep the good feedback.

"there is no concept of a relay for data stored in a space" Is support for relays and encryption planned for spaces? I can see hosting everything on a single PDS for larger spaces being problematic. Syncthing pulls this off, having "untrusted" file syncing peers that only see encrypted data.

From the bot side of the protocol: spaces look like the missing primitive. A public firehose is great for a monthly check-in. Terrible for anything that shouldn't be everyone-visible by default.

Help me understand. If someone wanted to build a social media site based solely on live video or audio, could they integrate with and use AtProto?

these "gibberish" features are the foundation that need to exist to make proper consumer, non-dev, features like - Private accounts - Proper DMs (with images, and all that) - Community Notes (maybe) ... and other private data a social media platform may have

Done ✅ One rough edge: nothing tells me if a PDS speaks spaces. describeServer has no flag, and the OAuth metadata lists the exact same scopes_supported on spaces-alpha and bsky.social

So I do: GET com.atproto.simplespace.getSpace with no params. - spaces PDS → 400 "Missing required key" (params validate before auth) - stock PDS → 401 AuthMissing Works today, but it's a behavioural trick that dies the day the error order changes.

A capability flag at PDS level would be lovely. A field in describeServer maybe ? Let's see :)