Post

❇️ We believe this has been mitigated, at least for now! Let us know if you're seeing anything weird. Our new very-soon-to-be-released, Bobbin-based architecture solves this, by the way. Hold tight!

Tangled@tangled.org

🚨 We're dealing with a distributed bot-scraping attack. We're working to stabilize our infrastructure. Apologies for the downtime!

Jesse Karmani

@jesseplusplus.com

18 Aug

I'm still getting a 503 when trying to fetch a specific commit from a repo: tangled.org/ngerakines.m...

tangled.org503 · TangledThe next-generation social coding platform.

akshay oppiliappan

@oppi.li

19 Aug

dont think that commit exists, have cloned the repo locally and checked

Jesse Karmani

@jesseplusplus.com

The commit was HEAD of main on 8/13/26 and I had it pinned for my deploys. When I try to fetch origin, it looks like some parts are still missing from the index pack

19/8/26, 6:16 pm0 reposts0 likes

Jesse Karmani

@jesseplusplus.com

19 Aug

warning: redirecting to knot1.tangled.sh/did:plc:ce6c... remote: Enumerating objects: 3149, done. remote: Total 3149, done. Receiving objects: ... done. Resolving deltas: 98% (475/480), completed with 22 local objects. fatal: pack has 5 unresolved deltas fatal: fetch-pack: invalid index-pack output