Zooming out and re-motivating the design of spaces, the new primitive for non-public data on atproto.
In which I admit I'm wrong, on the internet
Our plans for organizational permissions on spaces
I believe having good abstractions is key to writing good code. But as a coder, I often write code in an effort to find those abstractions…
The permissioned data proposal has the concept of membership, but leaves it to the app to orchestrate it. The arbiter is our idea for a general-purpose, interoperable ATProto group membership service.
At @habitat.network, we're working hard to launch something at ATmosphereConf. We're building a platform for user data agency: giving users full and transparent control of where their data flows on the internet. Naturally, building a privacy-first platform, we're thinking about permissioned data.