Hey all, as it's come up several times before, and was again discussed in the last call, why not add services other than Mastodon on social.coop? We could occasionally install an interesting FLOSS service, and all have the chance to try it out, to see how usable / user-friendly / useful it is. If the software is mature / useful enough for us, we can keep it running and try to provide the developers with contributions (code + financial), otherwise we can just give them some feedback, scrap it, and try another option. Criteria for social.coop member servicesIMO our criteria would be (in order of importance):FLOSSUser friendlyBased on open standards / protocolsFederated / DecentralisedSocial / Collaborative / Co-operativeProposed next stepsComment with your opinion on this whole initiative. If there doesn't appear to be consensus on moving forward with this, we can first discuss the premise further. Comment with your thoughts / ideas about the criteria. Once there appears to be consensus, I can post a proposal to formalise this.Discuss the financial aspects: some more lightweight services could run on our existing infrastructure (esp. with the upcoming upgrade), but others would require more resources (notably storage costs would go up with things like file hosting). how to compensate the members who would install and maintain the services, and contribute to developing the softwareComment with any services you need (or software that may be worth trying) and I'll update the list below. Once we have a semi-comprehensive list of options, we can discuss them more in depth, and then decide where to start!Possible servicesIdentity and single sign-on optionsCustom social.coop member database & web app, using OpenID/OAuth, and maybe integrate IndieAuthLook into projects like Portier, Auth0, and OSIAMLook into building on top of Hubzilla, which has a federated system featuring nomadic identity (a user can migrate from one instance to another, unlike with Mastodon). It also has social networking functionality that can federate with Mastodon (though doesn't seem to support ActivityPub). May be be a good option if we want all our services to be tightly integrated, with federation at their core, but would require more hacking on any software we want to add (which could arguably benefit the whole FLOSS community and push it from the current app/platform silos towards more federation & integration).FLOSS, federated servicesMatrix / Riot - federated communications platform, incl. group chat and end-to-end encryption, integrates with Jitsi for audio/videoFederated WikiCollaborative workspaces: Apache Wave, Kune Socialhome (also federates with Mastodon)Movim (XMPP based)Blogging (Ghost / WordPress)Cool things like Known, Quill & BridgyEmailCalendarFLOSS, not-yet-federated servicesDecision making with our own instance of Loomio and explore others like VoteIt, Orgbook, ukuvota, etcGitLab to help developers avoid centralising everything on Github. Git is already distributed in nature, but certain functionality could still do with more federation (being discussed among GitLab devs).Map creation (umap based on OpenStreetMap)Collaborative document editing (Etherpad / ethercalc / Jetpad / HackMD / onlyoffice)Reddit-like site for sharing & discussing links (Raddit for eg)Bookmarks / links sharing (examples)Feed reader (examples)Scheduling (eg Rallly, others)Video chat (eg Jitsi or Hublin)Secure password & notes saving/sharing (eg turtl)Kanban/Scrum project management (eg Taiga)LaTeX document editing (eg ShareLaTeX)Meta-platformsSandstorm (incl. some federation)Nextcloud (incl. some federation)CloudronFLOSS utilitiesThese would be handy for members to have on a platform we control, but don't necessarily meet the Federated / Decentralised nor the Social / Collaborative / Co-operative criteria.URL shortener (examples)Image hosting (eg mediagoblin or lutim)Photo sharing (eg Lychee)Audio/Podcast hosting (eg mediagoblin)Video hosting (eg mediagoblin, plumi, mediadrop, or clipbucket, and restreamer for live broadcast)Save stuff for later (eg wallabag, tiddlywiki, keeper or turtl)Static website hosting (eg using jekyll, grav or hugo)Pastebin (eg)