Habitat now supports creating organizations and approving apps to them, backed by the opensocial community working group's proposal!
Habitat's road to release: 05 adopting opensocial
habitat.leaflet.pub
Habitat
@habitat.network
Habitat is building data agency for organizations. Learn more about us here: https://habitat.network Join us on Discord! https://discord.gg/PTgZER8S73
Habitat now supports creating organizations and approving apps to them, backed by the opensocial community working group's proposal!
Habitat's road to release: 05 adopting opensocial
habitat.leaflet.pub
It's that time of the week again! Today, we're sharing Chalk, a document editor that shows how apps that need fine-grained permissioning can be built on spaces. Chalk is built on our last three releases!
Habitat's road to release: 04 Chalk
The one where we don't release an API :)
habitat.leaflet.pub
At Habitat, we've been thinking about what apps might need to build rich permission-ed interactions and interoperate. Here's our take ⤵️
Habitat's road to release: 03 ReBAC on spaces
Fine-grained permissioning on top of spaces.
habitat.leaflet.pub
Week 2: introducing sap, a Go package for syncing permissioned spaces. We're testing this out with a couple teams now, @ us and give it a try!
Habitat's road to release: 02 sap for syncing permissioned spaces
A package to help apps keep permissioned data up-to-date.
habitat.leaflet.pub
Over the next few months, we'll be spotlighting parts of Habitat one at a time as we work through our roadmap to a stable release in ~6 months. Here's a little preamble to that!
Defining data agency
& more reflections from Habitat's summer in Berlin
habitat.leaflet.pub
We've spent the last couple weeks deep diving on the permissioned spaces proposal and what it means for Habitat's use case! We plan to release a formalized spec on what we're building soon, but in the mean time appreciate any thoughts on our design.
Habitat & permission spaces for organizations
Our plans for organizational permissions on spaces
habitat.leaflet.pub
hi #ATmosphereConf and in the spirit of ABL: we built a local-first p2p markdown editor on our private data implementation: habitat.network/habitat/docs/, it permissions p2p connections in addition to records find @offline.arushibandi.com @sashankg.bsky.social @eagraf.dev to ask us more!
docs
Web site created using Habitat
habitat.network
We'll of course be demoing at #ATmosphereConf, but I'm really excited to get into the *why* of what we're building with this talk. Much of the internet sucks right now. We all know it. So what is the vision for the future? We hope you watch this talk and dream on with us.
I am really looking forward to Arushi's @offline.arushibandi.com talk. As we were wrapping #AtmosphereConf 2025, she said thank you & a few other kind words on her way out the door. So I'm very pleased to see this talk, "in conversation with several of the talks from last year"
spaces, meet cliques! how we built a minimal calendar on pear (our permission-enforcing ATProto repo) and what we had to build to get there.
calendar pt. 2: buckets spaces, meet cliques!
permission-ed data without AppViews
habitat.leaflet.pub
@eagraf.dev with part 1 of how we're building a personal calendar on ATprotocol and what we're thinking about (differently!) for permissioned data
calendar pt. 1: ATProtocol beyond AppViews
our approach to permissioned data (part 1!)
habitat.leaflet.pub
happy friday folks! had to get this out, give it a go :)
greensky: what does permissioned data feel like?
habitat.leaflet.pub
@habitat.network, we are so excited about ATProtocol not so we can get new social networks, but because of the primitives it provides for a world with user data agency. let's build that world.
but should apps see our data?
thinking small on the protocol
habitat.leaflet.pub