Comment by danielspace23
3 days ago
Just an fyi for everyone: while Tangled is built partly on top of ATProto, it differs from its component architecture widely, as the tasks that should be done by the AppView are offloaded to "knots", self-hostable servers specific to Tangled that do most of the Git heavy lifting. It violates the "user data stays on the PDS" principle, as repo data stay on knots, not in PDSes. As far as I know, no other ATProto application has a similiar architecture.
> It violates the "user data stays on the PDS" principle, as repo data stay on knots, not in PDSes.
I'm not familiar with ATProto; what does this mean in practice? Does it just change the failure modes if something breaks?