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!

The #atproto AppView I've been working on needs to store more and more private data. However, I don't want to wait for Spaces to be ready. I'm gonna need to do some data migrations once Spaces land 😅

I agentically developed a Ghost-to- @offprint.app importer script and fell down the rabbit hole that is the future of networked code sharing @v-it.org

Bluesky picking up bots and spam accounts before I can even get into the app to check the notification, while probably over half our followers on X are fake, still. I just wish this app had the equivalent of Spaces cos I'd definitely move.

I hate to post from the other app but I have to agree with Zach. Add atproto and permissioned data and we’re onto something…

Permissioned spaces in HappyView didn't get much attention after the initial release because I've been focusing on service proxying, but I wanted to make sure to get caught up with the changes in @dholms.at github.com/bluesky-social/proposals/pull…. Permissioned Spaces in HappyView should be fully spec-aligned (for now).

I really worry that permissioned data is gonna kill a lot of stuff Take my recipe app: If i wanted no one to have access to the records but my app all i have to do is 1. create a space 2. use that space for all user content Bam, now no open data

We implemented the new permissioned spaces spec. This is a step in the direction for making Blacksky-only posts work for our users in any app It is also a strong signal to our Acorn customers that their access-control gated community feeds aren't proprietary to Blacksky and work even if they leave