@hongminheeๆดช ๆฐๆ (Hong Minhee) 
@kopperkopper 
This thread, in particular the starting post, are direction to move towards. We know this for years. Somehow there's a deep inertia to correct course. This "somehow" is the area of applied research that Social experience design focuses on and intends to provide solutions for: the very particular social dynamics that exist in grassroots environment, such as the FOSS movement and fediverse.
@hongminheeๆดช ๆฐๆ (Hong Minhee) @kopperkopper
SX defines the concept of a Grassroots open standard, and a domain of Grassroots standardization.
These are direly needed to be able to healthily evolve #ActivityPub to where it can be the future of social networking, and support a peopleverse.
If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116147786851664068 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
@foxFox Ritch 
๐ฉ๐ช 
@silverpill 
@raphaelRaphael Lullis 
@julian 
@mariusormarius
Yes. I tooted about the need for Grassroots open standards and Grassroots standardization this morning..
https://social.coop/@smallcircles/116147786851664068
In a decentralized grassroots movement, somewhere there needs to an aggregation of the solution artifact. In this case a robust, comprehensible #ActivityPub standard that can be readily implemented in libraries, frameworks and SDK's upon which then subsequently #SocialNetworking solution design can take place.
This is not centralization, this artifact can be federated. But there must be a place of convergence where consensus on protocol design comes together.
There might be a crowdsourced ActivityPub 2.0 specs + documentation site, plus a process around it to make it work.
