Yeah that makes sense. Since habitat is hosting a private repo right now, I need to think a bit on what scopes we need from the PDS (might be expansive) and also how to communicate that for each of our apps, which actually auth with habitat and not PDS! Definitely thinking about this.
That is totally fair and same! These are definitely prototypes we are releasing, and will be polishing stuff like this in the coming weeks.
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
👀 exactly! what! we're! thinking about! it's interesting that if you build for data ownership from first principles, ignoring social media entirely, you still get something that looks like ATProtocol. but we need better privacy guardrails than the protocol offers today.
bsky.app/profile/habi...
