@mhoye
There's also a philosophical dimension to it, which is dubbed 'forward-looking collective responsibility'.
https://plato.stanford.edu/entries/collective-responsibility/#ForwLookCollResp
@mhoye
There's also a philosophical dimension to it, which is dubbed 'forward-looking collective responsibility'.
https://plato.stanford.edu/entries/collective-responsibility/#ForwLookCollResp
@futurebird
When this last circulated, the image to the right was debunked a Blender rendering.
@cwebber
@mattl
Do you know the Rotate, Repave, Repair pattern?
Many times its easier to migrate the services to a new system, instead of upgrading the old one.
@Codeberg
When GitLab starts to show federating with Forgejo, a new time begins.
@nick_vh @n0toose @Gusted
@GossiTheDog
I get a different dog.
I would be interested to hear the thoughts of @johncarlosbaez to the points stated in the thread above, including the question in the OP.
@mcc
Due to the way how Fedilab pulls in other messages up to the OP when I've entered the thread further down.
@johncarlosbaez @futurebird
@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/
@postmarketOS I was very surprised recently that Alpine's musl resolves DNS differently than glibc.
- https://biriukov.dev/docs/resolver-dual-stack-application/5-getaddrinfo-from-musl-libc/
- https://jvns.ca/blog/2022/02/23/getaddrinfo-is-kind-of-weird/
- https://wiki.musl-libc.org/functional-differences-from-glibc.html#Name-Resolver/DNS
- https://martinheinz.dev/blog/92
- https://purplecarrot.co.uk/post/2021-09-04-does_alpine-resolve_dns_properly/
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.
@tomw I don't feel a generic rejection needs any justification. As a first, I just don't like the term.
My reasons for that can be debatable, but not the sentiment.
@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.
@aral As an @ecobytes member, we could always fire up a few containers for the small-web.org.
@aral I was thinking of running an instance for the computational common allmende.io, alongside the existing lab.allmende.io GitLab.
We don't always need all of its features and sometimes I just need a git and that's it
The application is simple and we still have enough compute left at @ecobytes
Also I wanted to offer you our self-managed PowerDNS at some point, which is now closer to being available for API use, if you wanted to test that.
Should we roll a git.allmende.io Forgejo instance?
@evan
Yes, what happened to C2S anyways?
@erincandescent @Seirdy @starshine
@ntnsndr @GuerillaOntologist @skyfaller @shauna @Matt_Noyes Thanks for mirroring the arguments. As I might feel tempted to answer to the second example later, I'm inclined to offer a slight variation of the prior:
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."
@GuerillaOntologist @ntnsndr @skyfaller @shauna @Matt_Noyes Josh, can we name three specific critiques that are missing a response in this thread?
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.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.