@SuperDicq Either way, both ATP and AP are flawed insofar as being dependent on servers representing single points of failure whereas Nostr is simply a network of relays with built-in fault tolerance and no single server dependency. @izzy
![👺 奇诺[流浪者]👹 👺 奇诺[流浪者]👹](https://mtl.jinxian.casa/media/2a017adbdb27e3d88b95060edde41b3005fa196d94784f60c9cdaf354b2b675a.gif)
adiz@mtl.jinxian.casa
@adiz@mtl.jinxian.casa
Posts
-
@SuperDicq There is an implementation of ATP written in Rust called Blacksky, which I think basically comprises all the bits and pieces necessary to operate a full ATP service. -
@SuperDicq There is an implementation of ATP written in Rust called Blacksky, which I think basically comprises all the bits and pieces necessary to operate a full ATP service.@SuperDicq There is an implementation of ATP written in Rust called Blacksky, which I think basically comprises all the bits and pieces necessary to operate a full ATP service. But I think DID resolution is still dependent on Bluesky. And, as it stands, due in part to the complexities of ATP and all the moving parts the barrier for entry for getting an ATP service setup is far more demanding vs. an AP server or Nostr relay. It's almost engineered by design to limit the capabilities of people to setup independent ATP services and limiting the component services in easy to deploy ways continues ensuring that a critical mass of users will always only ever exist on Bluesky. @izzy