Discussion space for the questions I brought up in this leaflet: Modeling communities on permissioned data - Daniel's Leaflets
Please let me know your thoughts/suggestions or if there are previous discussions around this that I might have mised
4 Likes
Hey Daniel! Sashank from Habitat here. We’ve slightly pivoted since we talked at AtmosphereConf away from the local-first stuff to focusing on data ownership for organizations (more detailed blog). Basically, we’re thinking that members of an organization (like a company or university) will get an identity on a PDS (or maybe an “organization data server”) managed by the organization. That way, the organization admin can apply policies on data access to approved apps and between org members. We’ve been playing around with our own implementation of spaces based on the existing proposal to prototype this.
This model actually answers both of the questions you posed in the blog post for our use case. Regarding scopes, admins grant approved apps access to all the spaces on behalf of the entire org. The app just needs to declare space types that they’re interested in. (side note: this also makes syncing easier for apps since they can use the admin granted credential to access all member spaces). Regarding who runs the arbiter, the org data server comes to the rescue again as the definitive source of truth for space membership policies.
We’ve been discussing with the Roomy folks on interoperable membership policies. Habitat intends to have fine grained permission models to support the wide variety of permissioned data use cases. However, we intend to track this state as records themselves (maybe within the spaces they control permissions for) so that they are migratable. Enforcing the semantics of the permission state will be the responsibility of the space host. The hope is that standardized lexicons will emerge around permission models that all space hosts can implement. We’re working on a proposal for one such permission model lexicon.
We’re excited to see the progress on spaces and can’t wait for it to be set in stone! Also very interested in continuing discussions so that our approach slots nicely into the atproto ecosystem.
1 Like