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.
@smallcircles@social.coop AP dev discussion is centred around microblogs not because it is the ideal form of communication... because it absolutely is not.
It's that way because the dominant implementor utilises the microblog format.
A more appropriate conclusion is that AP dev discussion is centred around the fediverse because dogfooding makes the most sense.
@julian dogfooding is always a good thing, but whether it makes most sense to use microblogging as primary communication medium in an open-standards based grassroots ecosystem is another question.
