@ntnsndr It's interesting. Because we are a globally distributed group, the organisational infrastructure is a chat and Google Docs, therefore inherently online. But we have 50 % join rate from registration to the org to joining the chat, which is not a lot. I was rather asking about how to raise awareness about this inherent online-ness, when everybody is already fed up and tired out from getting lost in platforms and logins. An emphasis on synchronous collab is making things even harder.
@ntnsndr Nathan, how would you describe online community building to a group of people who consider themselves a community, but not primarily an online one, but using platforms and social media "as is" in a "ubiquituous/ambient computing" situation? For whom ICT are just a tool to communicate internally and externally, which leave technicial decisions to "the techies"?
Thinking about how to untangle the knot at the @IDN.
@jwildeboer The name C4 seems to be clashing with the other C4 systems architecture modelling language. Can we add or remove a word to end up with C3 or C5? If this is Pieter Hintjens, we're in for a treat. I was always intrigued by the good writing around the #0mq community process and also the work on calling out psychopaths. https://hintjens.gitbooks.io/psychopathcode/content/
In our case it breaks the search domain for Docker containers which would like to discover each other via DNS. This limitation of the search domain might also apply to mobile devices on postmarketOS in networks that set one.
@FediverseSymbol Nice symbol. Do you also have a proposal to replace the term Fediverse? I know many people, me included, who don't want to or cannot use it as a term in political debates, myself included.
Social Web was once one proposal, Open Socials is another. Maybe you've heard of other alternative naming that is more accessible in its name does not put the effort into a niche?
@zak GitLab CE just works (TM). Email service desks with custom email matures up. Adding external participants to confidential issues is useful, too. There is the work items migration, which unifies issues, incidents and tasks, offering new ways of interlinking. No epics, which is a label for us. What have I missed? Ah ja, the Kanban board and separate incident timelines. Also integrates well with external services and the rest they have to offer. The API and SSO integrate it in return.
Nobody accused anyone of lying above, if I'm not mistaken, which might leave us with the following, instead:
"The techno-social architecture of distributed ledgers is not sufficient to redistribute wealth equally to all, why we must choose to abandon this and persue other prospects."
I'm with you about scrutiny in empirical argumentation of the subject.
From the above discussion, I'd pick:
1. Distributed ledgers are not decentralised in terms of protocol design and P2P bootstrap. 2. Philosophical arguments about novel governance and renumeration schemes ignore the fundamental critique of immutable, ungovernable protocol design.
3. The identification and naming of quantification as institutional governance model, which is used to enscribe and reproduce monetary power hierarchies within a private property narrative that encloses common resources, limits the discourse within groups and the public plus assumes and presents social stratigraphy as an ontological fact.
"discrimination is justified by the difficulty of updates to the legal system and the cost of updating IT systems"
It means legal and informational systems are bound by material constraints, such as availability of labour, coordination costs, modular and standardised architectures, plus regulatory procedures.
Which all in all makes a strong argument for using FLOSS collaboration patterns to decrease auxiliary costs for all participants in the distributed system.