Post

Maybe. Private spaces are supported. I think having this at an org level could be pretty interesting. Content, comments, components (?), users, auth, design system, CMS all in one place (?)

Adding a required field can make list() return no records until migration, per the docs. Could it expose a skipped-record count? Then an app could say '12 records need updating' instead of showing users an empty workspace.

Gotcha. I've wanted to dive into ATProto but I'm so used to Workers and the persistent socket connection aspect has been hard to reconcile. Hadn't considered fetching direct from the client. The personal site use case seems nice. May try that.

back in june I migrated my own site to use an 'atproto cms', and I've been thinking how to make this usable for everyone, without requiring special atproto knowledge πŸ‘‰ this hopefully fixes the rough edges + bugs it also adds support for private data + drafts via the experimental 'spaces' proposal

by this, I mean: I've been using a cms for a long time to store things like: βšͺ #ama questions people ask βšͺ talks I'm planning to give (or have given!) βšͺ my current location (which I track and expose publicly πŸ‘€) ...and so on πŸ‘‰ but atproto means your pds = your data so … why not use it as a cms?

a few more details: βšͺ airspace core is 9.2 kB in production βšͺ includes automatic validators + migration utils βšͺ no need for typegen βšͺ ships with a minimal read-only live client βšͺ runs on workers and deno ... and the name is credit to @mkrl.xyz, who made an amazing brainstorming partner πŸ™Œ

now we just need to figure out what the ecosystem wants to do for storing rich text (that wasn't drafted via pckt/leaflet) and we got a stew going

At a hackathon in 2011 we had no idea where to host a backend so we used twitter API in the browser to store and retrieve information because we didn't need to persist much. That didn't feel like pioneering something 🫣

Maybe I can use it for publishing music metadata Would be cool for syncing app data/settings once Spaces are stable

Records are also fairly "cheap" as far as things go, it's the events that are expensive to store forever (this is what changed in your repo for sync to work)

omg when i learned about atproto my first thoughts was "wait this is just pocketbase" thank you for making at pocketbase real