Spaces as Layers - Nick's Blog
Public anchor records paired with sidecar records in permissioned spaces give ATProtocol apps a composable pattern for blending open discoverability with controlled access.
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
New PDS! New PDS! Hear all about it!
The AT Protocol reference PDS implementation has just published a new release, version 0.4.5006 with a whole heap of awesome new features in it, we take a look at those features and the roadmap tha...
PDS Entryway | Bluesky
Bluesky runs many PDSs. Each PDS runs as a completely separate service in the network with its own identity. They federate with the rest of the network in the exact same manner that a non-Bluesky PDS does. These PDSs have hostnames such as morel.us-east.host.bsky.network.
Spaces | contrail
Auth-gated store for records that can’t live on public PDSes — private events, invite-only groups, members-only chat. Opt-in; zero cost if you don’t enable it.
Sharing this! Wish I'm not late for #IETF126 Tangled found PDS doesn't fit well for contributions even with upcoming permissioned space spec. So, we are planning to store record-like data outside of PDS, in Knot. This is a post explaining the reasons & upstream spec change we need. #atproto #atdev
tangled-cob.md · by boltless.me
tangled.orgYou 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.
So Streamplace has some personal-private data of yours in our PostgreSQL database, like your multistream targets (Twitch stream keys) and Discord webhook URLs. I'd love to move those into a personal-private space on your PDS, let's design what that looks like? We need six things: 🧵
daniel holmgren 🫠
here it is folks! lots of details to still nail down, but this is roughly where our heads are at for the design of a permissioned data protocol give it a read and let me know your thoughts!
@dholms.at thinking about permissiones data. What if: Permissioned data URI was at://<PDS did>/<record type>/<rkey> exactly the same as public data. The PDS would handle the space assignment opaquely and do a 4xx response with some space aturis. Client goes and grabs a space cred and retries
Hey @iame.li since video tracks are strongRefs to assets on a special Streamplace PDS, can they still be migrated to another PDS later? I think it would be quite important for creators to be able to move their videos to different providers over time.
Hey @dholms.at, do you have plans for blobs in spaces? We're chatting about it on @iame.li's stream. The proposal says blobs are uploaded to space host, right? That makes sense when the space host is a PDS because it has `com.atproto.repo.uploadBlob`, but not if the space host is something else.
