The article seems to forget about content addressable storage and signing key cryptography and how these tools might make their software more distributed.
my experience with most more-distributed internet-systems is: it's so distributed it's hard to get.
here you have Authenticated Transfer Protocol. you can get data very easily. via any of a huge range of means or sources! we have some examples ones today (direct from pds, relay, jetstream, appview, new protocols like Atom (atproto over MoQ), new systems like hubble). you can tell that it's from a certain account, no matter how you get the data (not all of these means actually preserve the crypto signatures, but there are more than one way to get the data with signature, and more are welcome).
I agree with you, I just think the bases are covered. I also think that it's a fascinating topic. And yes it matters. The Distributed Systems Engineers probably should know why atproto has such great addressable data (not hash based though), signed key crypto. I think it focuses some on the distributed side.
there's a lot of people who focus on distributed, on what that means. what seems a lot missing though is that atproto is already nicely a nicely authenticated (crypto) transfer protocol. and that it's probably the best actually distributed, in terms of data availability, in terms of people trying to get your data.
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.
The article seems to forget about content addressable storage and signing key cryptography and how these tools might make their software more distributed.
my experience with most more-distributed internet-systems is: it's so distributed it's hard to get.
here you have Authenticated Transfer Protocol. you can get data very easily. via any of a huge range of means or sources! we have some examples ones today (direct from pds, relay, jetstream, appview, new protocols like Atom (atproto over MoQ), new systems like hubble). you can tell that it's from a certain account, no matter how you get the data (not all of these means actually preserve the crypto signatures, but there are more than one way to get the data with signature, and more are welcome).
I agree with you, I just think the bases are covered. I also think that it's a fascinating topic. And yes it matters. The Distributed Systems Engineers probably should know why atproto has such great addressable data (not hash based though), signed key crypto. I think it focuses some on the distributed side.
there's a lot of people who focus on distributed, on what that means. what seems a lot missing though is that atproto is already nicely a nicely authenticated (crypto) transfer protocol. and that it's probably the best actually distributed, in terms of data availability, in terms of people trying to get your data.
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.