Summary #
New repositories created today (2026-07-30) via tg repo create on knot1.tangled.sh never appear on the tangled.org appview (HTTP 404), while older repos on the same account continue to work.
Evidence #
- Account:
nandi.uk(did:plc:ngokl2gnmpbvuvrfckja3g7p) - Repo:
nandi.uk/sleek→ https://tangled.org/nandi.uk/sleek → 404 - Control: https://tangled.org/nandi.uk/vidya → 200 (created 2026-07-29)
Backend is healthy #
- PDS record exists:
at://did:plc:ngokl2gnmpbvuvrfckja3g7p/sh.tangled.repo/sleek - Knot has git data:
git ls-remote git@tangled.org:nandi.uk/sleekshowsmainatf77d271c… tg repo view nandi.uk/sleekreturns the record (Bobbin/PDS path)
Repro steps #
tg auth login nandi.uktg repo create sleek --description "…"(or delete+recreate)git push/jj git pushtogit@tangled.org:nandi.uk/sleek- Wait 2+ minutes —
curl -I https://tangled.org/nandi.uk/sleekstays 404 - Canary
sleek-web-canarycreated the same way also stayed 404 (since deleted)
Also tried #
tg repo editre-put of the PDS recordtg repo set-default-branch main- Full
tg repo delete+tg repo create+ force-pushmain
Looks like appview firehose/index lag or post–knot1-migration gap: new sh.tangled.repo creates are not landing in the web index.
should be sorted now!