A repository on Tangled
Hosting websites on Tangled
You can serve static websites directly from your git repositories on Tangled. If you’ve used GitHub Pages or Codeberg Pages, this should feel familiar.
Hosting websites on Tangled
You can serve static websites directly from your git repositories on Tangled. If you’ve used GitHub Pages or Codeberg Pages, this should feel familiar.
worm-blossom
The website of worm-blossom, the creative partnership of Aljoscha Meyer and Sammy Gwilym. (We are sorry.)
Erin Kissane, Writer/Researcher - XOXO Festival (2024)
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.).
Muse, in its own files
A citation-checked review of Meta's Muse agent, built from its own leaked virtual machine. Each finding links to the files and lines it comes from.
Reclaiming my digital identity — Open Indie
This post is the preamble of a 5-part series called The Great Untangling. The following four posts have already been published and are li...
The code is here: tangled.org/tyler.fun/chalky.town/tree/ma… I rushed through the sync bits a bit to get a thing working, but those two methods are in the branch I have to clean it up 😅
