I'd like to give a heads-up to #SocialCoding movement where I'm involved and plan to revive the notion of #SX or Social experience design, esp. for the #SocialWeb.
So much chatter on #Fediverse is either deeply technical or app-specific. The field of SX may offer a more holistic and inclusive perspective, focus on methods, guidance and best-practices.
@ashleykolodziej in the thread with @dahukanna I mentioned "movement" vs. "community", spontaneous emergence and DoOcracy.
That sounds a bit overly casual, but just indicates it is up to anyone to give their twist to the SX field exploration. And ideally based on having the incentives to do so, and thus intrinsic motivation.
More concretely I'm thinking on having something akin to working groups (called Fellowships) with clear scope and focus, based on interest for particular themes within SX.
It's just a sketch in a different context (a Fediverse of fine-grained components & services instead of big siloed apps. #AppFreeComputing). It only depicts how a #Microblogging timeline might be richer.
One aspect of #SX may be to show what is possible in federated #UX, in order to inspire and envision a future #Peopleverse.
I’m interested in the work/discussion/decisions to address a specified challenge that happen before assets like RadiFedi storybook components and patterns are created expressed as solution atomic building blocks.
The Social Coding movement is explicitly a "movement", not directly a Community of Practice.
This because that scope is so large, and communities work less well then. So there's a DoOcracy, which just means "pick up any task or initiative and see it to completion".
And then organic emergence will see where this movement heads towards. There's less need for governance, risk for all kinds of power dynamics, etc. And expectations depends on what people put in.
..only to find that that was a bit too much work for me at that time. But fine #SX insights are waiting in that discussion, that can link rot at any moment.
Took a quick look (I restrict SoMe to mobile) & “reply guy” topic sits squarely in existing digital experience voice and tone, conversation design and linguistics theory+practices.
Would be interesting to apply those tools & research methods to identify+document “reply guy” interactions+expectations+actors. Interested in developing an informed understanding/model of why this digital human interaction happens. Then figure out appropriate, contextual solutions.
There's some ideas + wordplay around the term "social coding".
The word came about from witnessing disconnects between fedizens and FOSS devs. The notion that "coding is social" and involves ALL stakeholders including non-technical people, and that reversing to "coding social" refers to "Reimagining Social" (Social Media are about $$$ rather than social).
Note the "we are crowdsourced" on that website. This was a bit of a naive notion that that would happen.. i.e. that a process could be set up whereby people documented the pattern library involved with Social Coding / FSDL.
That is a typical community goal, and will not work, since people hate to document, esp. when it is not for their own initiative and in vast scope.
Ways in which the movement can mature are part of the discovery process on SX.
Add comment