@trezy.codes shared how HappyView detects PDS spaces support — checking community.lexicon.service.describe first, with a fallback for PDSes without it yet. The question: what would a better detection standard look like? discourse.atmosphere.community/t/detecting-spaces-support/12…
Sep 18, 2026 at 5:07 PM
HappyView v2.16 | HappyView
HappyView becomes the authority for its own spaces, credentials get signed requests, and space sync goes both ways.
HappyView v2.10 | HappyView
Service identity, permissioned spaces, and new blob utilities.
Overview | HappyView
Spaces are containers for permissioned data in atproto. Unlike regular public records that live in a user's repo, space records are gated by membership — only members can read or write data within a space.
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 ...
Make the PDS Your Own: Customization and Metrics - AT Protocol
Branding, observability, and a session-list fix in the newest reference PDS
Make the PDS Your Own: Customization and Metrics - AT Protocol
Branding, observability, and a session-list fix in the newest reference PDS
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
Am I Building the Torment Nexus? - What happens when an AppView gets an easy window into atproto spaces.
I built a tool that lets HappyView operators browse the contents of atproto spaces, and the moment I saw it working I got a pit in my stomach. Here's what the community had to say about whether it should exist, and what it needs to look like if it does.
Just published a repo that's doing nightly builds for several spaces-enabled PDSes. It's mostly for @happyview.dev testing, but I figured some others may get some use out of it as well. Lemme know if there are any other PDS implementation I should add! #atproto
GitHub - happyproto/pds-test
github.comNew project I built last week: a kind of "isblueskydownforeveryoneorjustme.com" dashboard, so I can stop wondering "is it my PDS or is it the AppView" when the app isn't loading - bookmark it for the next time something doesn't work but you're not sure what 🙂 status.feeds.blue
Atmosphere Status
status.feeds.bluePermissioned 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).
Permissioned data by dholms · Pull Request #94 · bluesky-social/proposals
github.comYou know what I want: a "headless" PDS. @roomy.space needs a way to create an ATProto account for every space that is created. That means we need a legit PDS repo. We don't want to implement a PDS ourselves, so we'd rather use Tranquil or the reference PDS.
Now watching on @stream.place: @trezy.codes talking about HappyView
chicago.at's video on Streamplace
stream.placeIt's time to talk about the next version of HappyView. 😎 #atproto
Looking Ahead with HappyView
happyview.devGreat question. My biggest takeaway: we need to come to an agreement on how to advertise PDS/service capabilities. MOST of the PDS implementations I'm testing support community.lexicon.service.describe, which works v well. #atproto
Scooter
So what were your major takeaways?
