Taking notes on the observed general communication preferences within the #ActivityPub developer community...
1. Microblog, microblog, microblog
2. Seek one-to-ones, mentions-only
3. Don't care about spread of the msg
4. Don't boost, don't use hashtags
5. Tooted today, gone tomorrow
Convenient? Pragmatic? Desirable? idk.
Anyone asked where the #ActivityPub dev community’s communication went to, can let a broad beaming smile come to their face, svivel their eyes skywards, then make a broad gesture with their arms, and exclaim solemnly “To the fediverse, my friend. To the fediverse”. And the dotted clouds high above in the steel blue sky will smile back at them, wave and gesture, and sing in a non-melodious cacophony “Here we are, come join us”.
And so we all do. It is a sight to behold. 🥹
Or with a tad less sarcasm, you might also say: Even though it is a medium that is not up to the task of holding a grassroots open-standards based ecosystem together, #Microblogging #SocialMedia has become the preferred channel for communication in the app-centric #fediverse. Majority of dev happens in the federated cloud and is driven by app owners.
Though luckily there is also a minority of ecosystem atmosphere custodians who help study the weather patterns of the future #SocialWeb.
If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116141469199837056 on your instance and quote it. (Note that quoting is not supported in Mastodon.)
@silverpill 
@raphaelRaphael Lullis 
@julian 
@mariusormarius
Btw, damn we should've caused this entire discussion thread to somehow flow to #SocialHub to have it in the archives. Instead of on "now you see me, now you don't" channel. Peekaboo. 🫣
https://social.coop/@smallcircles/116141469199837056
Here today, gone tomorrow, who made notes? The post-facto interoperability leaders did. Those who happened to be around at the right time to hear things being said on the grapevine.
We need a proper Grassroots standardization process, and a Grassroots open standard that is able to healthily evolve. The good organization of this is just as important as the technical robustness of the protocol, which is the solution artifact at the end of the open standards cocreation pipeline.
