iiinova — where your digital self keeps evolving

Habitat @habitat.network · 11/09/2026

This week we built comments into our document editor to show off what can be done with fine-grained permissioning on spaces! Check it out here: chalk.habitat.network

habitat.leaflet.pub

Habitat's road to release: 06 commenting

Using atproto space inheritance to power comments on our doc editor

1155

Habitat @habitat.network · 04/09/2026

Habitat now supports creating organizations and approving apps to them, backed by the opensocial community working group's proposal!

habitat.leaflet.pub

Habitat's road to release: 05 adopting opensocial

0217

Habitat @habitat.network · 28/08/2026

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.leaflet.pub

Habitat's road to release: 04 Chalk

The one where we don't release an API :)

1296

Habitat @habitat.network · 27/08/2026

Happening tomorrow morning!

091

Habitat @habitat.network · 21/08/2026

At Habitat, we've been thinking about what apps might need to build rich permission-ed interactions and interoperate. Here's our take ⤵️

habitat.leaflet.pub

Habitat's road to release: 03 ReBAC on spaces

Fine-grained permissioning on top of spaces.

0203

Habitat @habitat.network · 14/08/2026

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.leaflet.pub

Habitat's road to release: 02 sap for syncing permissioned spaces

A package to help apps keep permissioned data up-to-date.

0415

Habitat @habitat.network · 06/08/2026

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!

habitat.leaflet.pub

Defining data agency

& more reflections from Habitat's summer in Berlin

051

Habitat @habitat.network · 12/06/2026

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.leaflet.pub

Habitat & permission spaces for organizations

Our plans for organizational permissions on spaces

1315

Habitat @habitat.network · 27/03/2026

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!

habitat.network

docs

Web site created using Habitat

1355

Habitat @habitat.network · 20/03/2026

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.

0212

Habitat @habitat.network · 19/03/2026

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.

habitat.leaflet.pub

calendar pt. 2: buckets spaces, meet cliques!

permission-ed data without AppViews

2266

Habitat @habitat.network · 11/03/2026

@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

habitat.leaflet.pub

calendar pt. 1: ATProtocol beyond AppViews

our approach to permissioned data (part 1!)

4335

Habitat @habitat.network · 20/02/2026

@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.

habitat.leaflet.pub

but should apps see our data?

thinking small on the protocol

1299