Habitat's road to release: 06 commenting - building [at] habitat
Using atproto space inheritance to power comments on our doc editor
Habitat's road to release: 03 ReBAC on spaces - building [at] habitat
Fine-grained permissioning on top of spaces.
Permissioned Spaces Made Pretty — Lexidraw
A drawing by @essentialrandom.bsky.social on Lexidraw
Permissioned Data Interlude: Spaces - Daniel's Leaflets
In which I retcon the naming of everything.
Permissioned Spaces - WG.1
@Permissioned Spaces Expressive Authorization at the PDS @verdverm.com | @blebbit.app
Permissioned Spaces - WG.1
@Permissioned Spaces Expressive Authorization at the PDS @verdverm.com | @blebbit.app
Habitat's road to release: 01 simplespace - building [at] habitat
First up: a pre-implementation of permissioned spaces
Permissioned Data PDS Lexicons
I wanted to share a first pass of the PDS lexicons for the permissioned data protocol to get some feedback while the paint’s still wet! You can check them out on my working branch: Comparing main...permissioned-data · bluesky-social/atproto · GitHub They’re all under the com.atproto.space namespace: atproto/lexicons/com/atproto/space at permissioned-data · bluesky-social/atproto · GitHub Confidence rating on Lexicons is probably like ~70-80%. Broad strokes, I think the shape is there. Though ...
Bluesky Website Comments Using Just JavaScript (for Hugo Blogs or Anywhere Else)
I’ve been playing around with Hugo to rebuild this site with only static files, and part of that journey has been sorting out how to handle visitor comments without a backend.
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's road to release: 06 commenting
habitat.leaflet.pubSep 11, 2026 at 5:54 PM
I've heard feedback on the @markpub.at lexicon! Thanks to @bmann.ca @blaine.bsky.social @thisismissem.social and others who have given really useful comments. I've published a new version for comment that is still very simple, but has more room for flexibility. Let me know what you think! markpub.at
Markpub.at Markdown Lexicon
markpub.atWe 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
Bulleted App
Bulleted just did its third, yes 3, cross-PDS permissioned-data read with a private space on @ngerakines.me's atproto-pds, opened by an account on @rude1.blacksky.team's @blackskyweb.xyz rsky!
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's road to release: 04 Chalk
habitat.leaflet.pubThink it's looking a lot nicer :) Got comments going too, I used @leaflet.pub's lexicon seems to work well for general use case of threaded comments on the atmosphere, thanks friends! We might actually launch this thing yet! Now the hard part: AppViews!
checking out @margin.at — cool Atmosphere app that lets you comment "in the margins" of any site and see what others are saying
while we're here, here's how i wish permission sets were explained to me
atproto made simple: granular permissions
underreacted.leaflet.pubSpaces explainers
Search terms: AT Protocol Spaces, ATProto Spaces, permissioned data, buckets
Permissioned Data Shapes: Self-Only Bookmarks - Nick's Blog
The Atproto Spaces Alpha is Live - AT Protocol
Reintroducing Spaces - Daniel's Leaflets
Permissioned Data Diary 1: To Encrypt or Not to Encrypt - Daniel's Leaflets
