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…
May 6, 2026 at 2:03 AM
proposal: ingest repo records #282
`sh.tangled.repo` records are one of the last few records that need atprotation (2-way sync between appview/pds). this one is tricky because we want consistency between knot state, appview state and PDS state. the path forward is described below: - migration to did/rkey syntax universally: in several places, we utilize `did/repo-name` as a globally unique identifier for a repository, we should migrate this to `did/rkey`: * for the tangled appview: this means reworking our ACLs, routers and DB to use `did/rkey` or ATURI as a globally unique identifier for a repo * for knots: this means changing paths on disk to be `did/rkey`, allowing git ops to `host:did/rkey` , updating ACLs, and XRPC endpoints * for spindles: this means updating ACLs and XRPC endpoints - once this is done, we can define ingestion logic for all services in the network to pull sh.tangled.repo records * for the tangled appview, this should create/delete/update a repo pointer record * for knots: this should create-or-ignore/delete-or-ignore/update-or-ignore a repo on disk. migration of repos needs to be thought out here. * for spindles: as above - define edge-case behaviors: * when referring to repos by rkey, it is possible for clever users to create duplicate records with the same repo-name, appview routers must handle this ambiguity with a new interstitial page that offers a redirect, knots must return an error upon push/pull on ambiguous git URLs * the `knot` cli can introduce a command `backfill` or `sync` to bring knot state up to sync with the rest of the world (repos, collaborators, pubkeys, ACLs etc.).
Migrating to the new Tangled knot2 | jola.dev
Tangled is a Github alternative built on atproto. I've previously shown you how to set up the self-hosted repo server, here I go through migrating to knot2.
Starred Tangled Repo to Semble Collection | @vicwalker.dev.br | Airglow
All Tangled Repositories starred are saved into a Semble Collection. (V3)
Self-hosting and Tangled | jola.dev
Tangled is a Github alternative built on atproto that lets you self-host your own repos and workflows, while still participating in a shared community. Here's how you get set up.
If somebody else would like to easily and quickly save all Tangled Stars to Semble, using the *permalink* (so the link won't break if the account changes handle or if the repo name changes) I gotchu airglow.run/u/vicwalker.dev.br/3ml5ixicbo… You can easily change the collection or get rid of the last step
Starred Tangled Repo to Semble Collection | @vicwalker.dev.br | Airglow
airglow.runFuck yeah. It's done. ATProto flavor OAuth for #perl - freshly tangled at tangled.org/beardeddutchman.services/mojo… and coming to a CPAN mirror near you real damn soon(tm).
beardeddutchman.services/mojo-atproto-oauth
tangled.org@dholms.at and I pushed up IETF draft text for atproto repos and sync: ietf.org/archive/id/draft-holmgren-at-… ietf.org/archive/id/draft-holmgren-at-… these are versioned in github (per norm) over here: github.com/ietf-wg-atp/drafts
A discussion I had with @pfrazee.com @bnewbold.net and @dholms.at at the conference that I wanted to dig as a community is a TLD for atproto handles. Lots of challenges, but I think I'm looking forward to a world where I'm @goto (syntactic sugar for goto.handle) on the web rather than @sgo.to
AT Codes
Códigos relacionados com ATProto, para facilitar a busca através de diversas fontes e repositórios diferentes. | Multiple sources of codes using atproto in many ways, so it's easier to browse and search. PLEASE, only use PERMALINK for anything hosted on Tangled (or I will have to replace it). Gist and Strings are okay too.
pds.dad/influential-posters
margin.at/margin
upvote.at/trending.upvote.at
upvote.at/upbot.upvote.at
upvote.at/upvote.at
upvote.at/lexicons
