🫧 Social coding commonsYes, the blog is written entirely with perspective and focus on evolution of the #ActivityPub fediverse.
#ATProto has the advantage of its prudent protocol development approach, and that it could 'stand on the shoulders of giants' to apply lessons-learned from the past. The luxury position of a tight team of protocol developers unbound by a formal design-by-consensus process in a greenfield environment, and with due attention paid to protocol robustness and quality of specifications makes ATProto an attractive choice. Most importantly the protocol does not leave gaping misconceptions unaddressed.
ATProto is not the opposite of working at standard level, but rather an exemplar of it. But that depends how you look at it. As a solution developer you do not have to care about the protocol intrinsics, and just get exposed to solid API's and intuitive #design concepts the protocol already specified and dictated to #protocol implementers.
#GrassrootsStandards do the same for fedi.
