notes from @habitat.network
Habitat's road to release: 07 bridging traditional SaaS apps
building bridges to the (organizational) atmosphere
Habitat's road to release: 06 commenting
Using atproto space inheritance to power comments on our doc editor
Habitat's road to release: 05 adopting opensocial
This week, Habitat as a platform for organizational data is finally beginning to take shape. We've been working with other great atproto devs in the Community Standards working group and are excited about the current proposal for opensocial.community (still proponents for a more generic rename to groups or something similar though). In classic fashion, we were so excited about it that we went ahead and implemented (parts of) it.
Habitat's road to release: 04 Chalk
The one where we don't release an API :)
Habitat's road to release: 03 ReBAC on spaces
Fine-grained permissioning on top of spaces.
Habitat's road to release: 02 sap for syncing permissioned spaces
A package to help apps keep permissioned data up-to-date.
Habitat's road to release: 01 simplespace
First up: a pre-implementation of permissioned spaces
Defining data agency
& more reflections from Habitat's summer in Berlin
Habitat & permission spaces for organizations
Our plans for organizational permissions on spaces
Habitat: a data home for organizations
an update from us!
calendar pt. 2: spaces, meet cliques!
permission-ed data without AppViews
calendar pt. 1: ATProtocol beyond AppViews
our approach to permissioned data (part 1!)
greensky: what does permissioned data feel like?
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.
but should apps see our data?
thinking small on the protocol
hello, network!
introducing habitat.