#Tag
Being "commons based" means being able to sustain responsible, healthy evolution and natural growth.
I posted on this notion of #SOSS before, with a meme attached..
https://social.coop/@smallcircles/115399465970544831
There's nothing wrong with #FOSS, but it only provides part of the solution as long as the #Sustainability angle is not given due attention to.
Esp. with disruptive inhumanely introduced #AI #LLM technologies, new major threats to the #FreeSoftware community are surfacing, and giving attention to this subject matter is more important than ever.
Being "commons based" means being able to sustain responsible, healthy evolution and natural growth.
I posted on this notion of #SOSS before, with a meme attached..
https://social.coop/@smallcircles/115399465970544831
There's nothing wrong with #FOSS, but it only provides part of the solution as long as the #Sustainability angle is not given due attention to.
Esp. with disruptive inhumanely introduced #AI #LLM technologies, new major threats to the #FreeSoftware community are surfacing, and giving attention to this subject matter is more important than ever.
FOSS == ✅️ software artifact
FOSS != ❌️ software project
SOSS == 🌱 sustainable software project
There are a number of architecture patterns that fit like a glove together. I might summarize them to offer "Functional-reactive DDD" which allows distributed communication systems and direct focus on solution development.
As for my own interest in these technologies.. they form the underpinning to the work method that steers both my life and career. I divide my activities in a concrete and pragmatic 'work track', where I earn my living, and a long-term background 'hobby track'.
On this latter track I defined a "Grand dream" I pursue: the philosophical quest as well as the elaboration of holistic solutions for some of the wickedest problems of our time. In particular the question how we not only design an alternative to hypercapitalism, but actually introduce it into global society, such that it becomes the prevailing system.
Crazy, but fun 😅
Let's zoom in on a particular area of the commons: the #FreeSoftware movement and their #FOSS deliverables, where a strong #WorkingInPublic credo dominates. The noble focus is on offering open technologies, software and systems. But in their quest to uphold #SoftwareFreedom the overlooked aspect is #sustainability. The ability to not only sustain oneself, but also by extension the creative #commons one is part of. The commons is an entirely chaotic grassroots environment with very specific social dynamics that are not properly accounted for. Instead top-down "herding of cats" governance models that work in regular business environments, are attempted. These may work, but only in small organizational settings, and NOT at scale where they break down.
FOSS in this definition is NOT commons-based. For that we need #ChaordicCommons where FOSS is the deliverable and #SOSS initiatives the engines of delivery, #FSDL (Free software development lifecycle) supply chains.
https://coding.social/blog/reimagine-social/#sustainable-open-social-systems
I posted on this notion of #SOSS before, with a meme attached..
https://social.coop/@smallcircles/115399465970544831
There's nothing wrong with #FOSS, but it only provides part of the solution as long as the #Sustainability angle is not given due attention to.
Esp. with disruptive inhumanely introduced #AI #LLM technologies, new major threats to the #FreeSoftware community are surfacing, and giving attention to this subject matter is more important than ever.
FOSS == ✅️ software artifact
FOSS != ❌️ software project
SOSS == 🌱 sustainable software project
🙏 Thank you for your attention to this matter.
https://www.w3.org/community/SocialCG
https://socialhub.activitypub.rocks
Commons based: You have opportunity to introduce a post-capitalist society
Default public: Sorry, it is #hypercapitalism for you. You lose.
I've been a long-time advocate for #HumaneTechnology. Social coding commons adds something to that to become "humane and harmonious technology". Humane by default. #Humanity is an intrinsic value of the movement. And harmonious by #SocialCoding. Coding is social, and first of all deals with people coordinating to find solutions that align with and satisfy stakeholder needs. Coding happens somewhere in the process, an impl detail.
A core principle of Social experience design is Sustainability, which is holistic in nature via the (adapted) Circles of Sustainability model. https://coding.social/blog/reimagine-social/#circles-of-sustainability
With this in place a #SX software solution will cycle through its Free software development lifecycle i.e. #FSDL, which drives a tailored development based on needs and lifecycle phase. https://coding.social/blog/reimagine-social/#free-software-development-lifecycle
Together this completely avoids a pure technology-driven development, ensuring Needs-driven development, and a natural NIMBY of inhumane technology and practices.
@smallcircles "grassroots social dynamics" may be actually digital NIMBY movement against targeted advertising and AI... :-)
@thisismissem
I've been a long-time advocate for #HumaneTechnology. Social coding commons adds something to that to become "humane and harmonious technology". Humane by default. #Humanity is an intrinsic value of the movement. And harmonious by #SocialCoding. Coding is social, and first of all deals with people coordinating to find solutions that align with and satisfy stakeholder needs. Coding happens somewhere in the process, an impl detail.
A core principle of Social experience design is Sustainability, which is holistic in nature via the (adapted) Circles of Sustainability model. https://coding.social/blog/reimagine-social/#circles-of-sustainability
With this in place a #SX software solution will cycle through its Free software development lifecycle i.e. #FSDL, which drives a tailored development based on needs and lifecycle phase. https://coding.social/blog/reimagine-social/#free-software-development-lifecycle
Together this completely avoids a pure technology-driven development, ensuring Needs-driven development, and a natural NIMBY of inhumane technology and practices.
I recreated an old diagram in Excalidraw that I spread about a couple years ago, and made it a bit more informative. Explanation can be found in the #AltText
See also and for discussion: https://discuss.coding.social/t/diagram-interoperability-in-practice/828
Or join the Social experience design chatroom at: https://matrix.to/#/#socialcoding-foundations:matrix.org
Also posted to #SocialHub at: https://socialhub.activitypub.rocks/t/activitypub-versus-fediverse-interoperability-in-practice/8498
#SX #SocialCoding #SocialWeb #ActivityPub #SolidProject #fediverse
Attention Media ≠ Social Networks by @susam
https://susam.net/attention-media-vs-social-networks.html
@toddsundsted very nice work! This is valuable information. #ActivityPub #FEP
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.
To chain things together a bit on this fleety medium of ours, create a hyperweb 😜 I'll quote this toot to follow-up to
https://social.coop/@smallcircles/116110545919004233
I remember about 2018 or so, when I joined my first #SocialCG meetup. It was when the CG was still strongly tied to #SocialHub community.
There were mundane items on the agenda, interesting to any #ActivityPub dev, and also the call to action was "whether you are technical or not at all, join the meetup, we are open and inclusive to all fedizens". Very friendly, good vibes.
However during the session the talk was not only CS expert level, but dealing with subject matter nowhere near the spec. It was 'wire reality' slang, and to learn it the guidance was either nowhere, or everywhere, dispersed. And this is still as it is today. To expertised AP developers their domain language sounds all natural, but it likely seems Martian to a dev newcomer.
Stark contrast to the W3C specs that leave folks with refreshing "Let's implement this" vibe.
I recreated an old diagram in Excalidraw that I spread about a couple years ago, and made it a bit more informative. Explanation can be found in the #AltText
See also and for discussion: https://discuss.coding.social/t/diagram-interoperability-in-practice/828
Or join the Social experience design chatroom at: https://matrix.to/#/#socialcoding-foundations:matrix.org
Also posted to #SocialHub at: https://socialhub.activitypub.rocks/t/activitypub-versus-fediverse-interoperability-in-practice/8498
#SX #SocialCoding #SocialWeb #ActivityPub #SolidProject #fediverse
@ben wrote a good article "Growing the open social web" for FediForum.
It poses this *essential* question: Why do we want to grow the open social web and for whom?
While the question is crucial when considering the future of social networking and the role of online technologies in society, it is not a question that is being addressed in any significant way. Our social web and fediverse "just happens", emerging from this chaotic cauldron of mostly technical discussions about which features to put in apps, how to connect one app to the next, and which social web technology or app is better than others.
Ben makes an appeal for creating good protocols, where the real value is, but only if we can share ownership of them. I 100% agree with the points in the article.
But how do we get there? What is this ownership? How do we achieve it, and subsequently retain it? I wrote down some some thoughts in a blog post.
@ben wrote a good article "Growing the open social web" for FediForum.
It poses this *essential* question: Why do we want to grow the open social web and for whom?
While the question is crucial when considering the future of social networking and the role of online technologies in society, it is not a question that is being addressed in any significant way. Our social web and fediverse "just happens", emerging from this chaotic cauldron of mostly technical discussions about which features to put in apps, how to connect one app to the next, and which social web technology or app is better than others.
Ben makes an appeal for creating good protocols, where the real value is, but only if we can share ownership of them. I 100% agree with the points in the article.
But how do we get there? What is this ownership? How do we achieve it, and subsequently retain it? I wrote down some some thoughts in a blog post.
What more?
Social coding commons is dedicated to the #future of the #fediverse that supports a thriving and delightful #commons for people to connect, cocreate and collaborate, and do all things that make life worth living.
#Humanetech #Socialcoding #ActivityPub #fediverse
