#grassrootsstandards — Public Fediverse posts

@ex_06

Yes, 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.

@abeorch @gary

There are certainly issues. I wrote a long thought piece on social experience and travels in #ActivityPub space and with a call-for-reflection to anyone to ponder #fediverse's Future of #SocialNetworking..

The blog post (which is an hour-long read) also stipulates re-centralization risks, and how a #fedi-native protocol implementation of #GrassrootsStandards and #GrassrootsStandardization processes like the #FEP and #SocialCG can help mitigate the #centralization risks.

https://social.coop/@smallcircles/116379158584600016

PS. See also my call-to-participate as #CommonsCustodian in the #standardization of our networking protocols..

https://social.coop/@smallcircles/116402592862958767

Together we can :boosts_appreciated: #BoostFediForwards and #cocreate a better #future.

#SX #SocialCoding #SocialWeb

@toddsundsted

Btw. #GrassrootsStandards and standardization processes (such as the #FEP process) are a topic of Social coding commons and Social experience design, and we have a multi-author blog at https://coding.social ..

If you wish you might publish these results there as a report to spread about.

#SX #SocialCoding #SocialWeb #ActivityPub

@bob

I'm happy with this #MLS #e2ee development.

Just not with the way in which the #ActivityPub #fediverse now evolves, i.e. on the basis of protocol decay, tech debt, and whack-a-mole development. Which have been my #sighs and frustration in the past years of #SocialHub facilitation and #SocialWeb advocacy.

Where I have use cases is in Personal #SocialNetworking, to enable #DelightfulCommons participation, and subsequently work collectively on #GrassrootsStandards

https://coding.social/introduction/#personal-social-networking