automerge-repo drop in replacement backed by Habitat "permissioned spaces" om your PDS
Atproto spaces alpha updates
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...
Creating a did:web identity in ATProto — Kamin's Corner
In the process of migrating my self-hosted PDS to a new server, I managed to accidentally lose my .env file and in the process lost by ro...
/atproto-crates/crates/atproto-pds at main · ngerakines.me/atproto-crates
A repository on Tangled
Habitat's road to release: 06 commenting - building [at] habitat
Using atproto space inheritance to power comments on our doc editor
Migrating PDS Account with `goat` | bryan newbold
Account migration is an important feature of atproto, and has been possible in the live network since February of this year, but is still a bit scary and developer-oriented. As part of documenting the migration process, I recently implemented basic account migration in the goat CLI tool for atproto...
ATProtocol-Community/ATStore
Contribute to ATProtocol-Community/ATStore development by creating an account on GitHub.
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.
com.atproto.repo.createRecord | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*
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.
TLDR in English Just did an automation using @airglow.run that will save me so much work from now on Every tangled repo I give a star will now be saved into my @semble.so collection for atproto-related repos, using the permanent URL
Victoria
Mal conheço o Airglow e já considero PACAS Acabei de fazer uma automação que vai me poupar um trabalhão Todo repositório do Tangled que eu dar uma estrela, vai ser automaticamente salvo numa coleção do Semble, E USANDO URL PERMANENTE (que usa DID e não handle)!!!!! airglow.run/u/vicwalker.dev.br/3ml5ixicbo…
ahhhh it works! I have an atproto PDS, knot, spindle, and hold, all driven by a repo hosted on the knot, running on container images created by the spindle and hosted on the hold. The accounts that tie it together all live on the PDS. tangled.org/cove.town/cove.town
cove.town/cove.town
tangled.org1/X I made an atproto proposal around PDS to PDS repo migration that gets around all of the pain points of account migration today and intentionally builds a migration flow for users to go to the PDS that they want to move to and commence the migration from there.
0014 repo migration pds by afbase · Pull Request #91 · bluesky-social/proposals
github.com
