Conversation

Notices

1. bhaugen (bhaugen@social.coop)'s status on Thursday, 08-Nov-2018 11:06:45 EST bhaugen

   @Matt_Noyes

   Not sure any protocol cooperatives exist yet. But (for example) implementing a co-op on ActivityPub would probly qualify.

   I think that is what Matthew Slater has in mind, last time I heard.

   @dajbelshaw how close will #moodlenet be to a protocol co-op? Or would it be more like a platform? Or a hybrid? Or not a co-op?

   1. Mayel (mayel@pub.mayel.space)'s status on Thursday, 08-Nov-2018 11:35:51 EST Mayel

      in reply to
      @bhaugen @dajbelshaw @Matt_Noyes
      
      I'd say something like MoodleNet is difficult to define (and I think the word platform is too restrictive, network is better), as it will involve several things:
      
      1. Software
      - #FLOSS #ActivityPub federation server (interoperable with other fediverse apps): https://gitlab.com/OpenCoop/CommonsPub/Server
      - #FLOSS MoodleNet back-end API, as an extension of the federation server
      - #FLOSS MoodleNet client app: https://gitlab.com/moodlenet/clients/react/tree/ui-milestone-1
      
      2. Infrastructure
      - An initial MoodleNet instance run by Moodle HQ
      - MoodleNet instances run by other/people orgs
      - HQ API run by Moodle HQ (the org) as a central service, mostly a search index
      - Fediverse instances running different software
      
      3. Community/Communities
      - Proximity: People on the same MoodleNet instance
      - Groups: People in the same 'Community' or 'Collection' on MoodleNet (across instances)
      - Graph: A user and the People/Communities/Collections they follow
      - Fediverse: People interacting between MoodleNet and other federated apps, and vice versa