As I thought experiment, I wondered what Bluesky on permissioned spaces would be like (…caveats/context my POC)
It would work the same as it does today, basically everything “public” and going into the users’ own repo, but… one could enforce “only logged in accounts can view”
Threadgating is more complicated, and an interesting use case in it’s own right, but would require that (i.e.) comments live with the post and clients understand this for threadgated posts so don’t look to other repos for comments, which could still exist.
While the example code here does not show it, it is possible to have more private spaces within the public Bluesky equivalent parent space. Generally speaking, there are a lot of interesting use cases sitting in the primary atproto app we all use already, that seem to me to stress the permission system we are trying to design at the opposite pole from fully locked down E2EE data (or even msgs, but excluding that effort in this discussion and WG)
