Okay as promised, we just cut another spaces alpha releast today! This includes the credential & sync changes that I listed above plus a small API field rename in listSpaces and simplespace.createSpace. There are several breaking changes, and I expect this to be a more disruptive rollout than the last one. The rollout will update the hosted psaces alpha PDS, the Docker image at ghcr.io/bluesky-social/atproto:pds-spaces-alpha and the relevant npm packages. For folks running their own PDS, this r...
Atproto spaces alpha updates
Hey folks, we just launched the atproto spaces alpha. Check out the blog post for more details! Over the following weeks, we’ll be iterating on the specification and the implementation. In all likelihood, this will involve breaking changes to the PDS distribution, the Bluesky-hosted alpha PDS, and the alpha SDKs. To minimize disruption, we’ll plan to do releases on Thursdays (barring something critical that requires more immediate attention). When we do a release, We’ll make a post to this thr...
The Atproto Spaces Alpha is Live - AT Protocol
Atproto Spaces, formerly known as “the permissioned data protocol,” is a new extension to atproto that enables non-public data. The alpha is now officially open. Here’s how to develop with it and what to expect as we work towards the full release.
The Atproto Spaces Alpha is Live - AT Protocol
Atproto Spaces, formerly known as “the permissioned data protocol,” is a new extension to atproto that enables non-public data. The alpha is now officially open. Here’s how to develop with it and what to expect as we work towards the full release.
The Atproto Spaces Alpha is Live - AT Protocol
Atproto Spaces, formerly known as “the permissioned data protocol,” is a new extension to atproto that enables non-public data. The alpha is now officially open. Here’s how to develop with it and what to expect as we work towards the full release.
atproto pds self-hosting: some issues and antipatterns | friendmeat
The Bluesky personal data server (pds) repository is weirdly opinionated about stuff that's easy, and unhelpful with the stuff that's hard. They also insist on using a script that installs a whole HTTP server and Docker stack. But if you're gonna use Docker why assume that people don't already have their own stack? It's just weird and annoying. But here's how I did it.
Embracing ATProto, part 1: Setting up a PDS
In this series of posts, I'll explore my journey into setting up my workflows and services for atproto. The first step is setting up my PDS. Let's start with a bit of explanation for all this lingo.
just wrapped up deploying a spaces alpha release! nothing too bad, but some applications that make use of simplespaces will likely break take a look at the breaking changes here: discourse.atmosphere.community/t/atproto-spaces-alpha-update…
Atproto spaces alpha updates
discourse.atmosphere.communityAtproto Spaces (buckets, we hardly knew ye) have moved from a proposal to real live working — AND VERY MUCH ALPHA DO NOT USE THIS IN PRODUCTION — code. We even set up a working PDS for y'all to use, head over to bsky.network/account to get going
AT Protocol Developers
The most significant extension to the protocol since launch—atproto spaces—is now officially alpha software you can start testing with. Here's more about the goals and how to start testing. atproto.com/blog/atproto-spaces-alpha
You 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.
The most significant extension to the protocol since launch—atproto spaces—is now officially alpha software you can start testing with. Here's more about the goals and how to start testing. atproto.com/blog/atproto-spaces-alpha
The Atproto Spaces Alpha is Live
atproto.comJust 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.com_very_ alpha, but I've been messing with an atproto backfill/sync solution built on @cloudflare.social — currently has a couple caveats, and needs some work and docs, but the bones are there
GitHub - estrattonbailey/slipstream: Slipstream is a syncing and ingestion pipeline for atproto, built on Cloudflare.
github.comI've just finished the first, barely-working prototype of our new arbiter server! It's not ready for use just yet, but we're going to start experimenting with it in @roomy.space as a way to make every space a fully-fledged ATProto account that can be seamlessly managed by the Roomy space's admins.
Arbiter Progress Report 3
zicklag.leaflet.pubThe week-end is over so I'm pressing ⏸️ on my custom PDS project for now. Here's part 2 of my dev journal. I've learned a lot already and so far I feel like it might actually be worth finishing. It's really cool to get a more intimate understanding of ATProtocol and it's implementation.
How to Make a PDS - Part 2 - Zicklag's Leaflets
zicklag.leaflet.pub
