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.

we back on leaflet 🍃

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!

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.

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.

no, it doesn't! 🌱

@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

happy friday folks! had to get this out, give it a go :)

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