This is a general view on the topic. I think open-source isn’t enough, we need also governance for the software we use, and create small pockets of freedom.

All feedback is welcome.

  • Kissaki@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    1 day ago

    I’m not sure the Fediverse examples are instances of “co-op governance”?

    Lemmy is a protocol where you can make suggestions and join discussions, but ultimately, it’s a project under the project governance. People then create their instances, and make their own rules with who they connect with and which they don’t. This is cooperation, but not governance of the network as a whole. You can scope and draw some lines and say “this collective/collection is governed by cooperating people”, but in my eyes, that’s not the “coop” and “workers/users own the project” kind of thing.

    It’s more of a dynamic, cooperative, collaborative system of localized governance and spanning cooperation. There is some governance on protocols etc, and you can fork it and give your opinion, but you don’t own it.

    • Shin@piefed.socialOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      Because make no mistake, federated software is not automatically a co-op either. Mastodon solves the protocol and the code. It doesn’t solve the governanceof each instance

      And I agree with you.

      This is the starting point, not the final destination.

      I’ll ask, did you read the post?