ATProto for Distributed Systems Engineers

The article seems to forget about content addressable storage and signing key cryptography and how these tools might make their software more distributed.

I feel like it's the best ATProto architecture explanation on the web.

I hope it will make people who argue that "there are no instances in ATProto" is wrong, understand that it is actually true and not just a naming debate.