Regarding the realtime communication note, I am assuming you're talking about realtime communication for anyone and not just SSWG core members. If that's the case, I would humbly suggest the idea of a SSS Discord channel. With Slack we may possibly run into the same problem that the Vapor community faced over a year ago with content being eaten up by the paywall. Discord is great when it comes to this and I've found it to be much nicer to work with regarding roles and members.
So out of the back of some discussions we had at the conference (and on the podcast!) I'd like to propose an alternative - using the ServerSide.swift conference Slack.
there's already an established community of Swift server developers on there
there's already a number of people who maintain the workspace (and no single point of failure)
it fits well with the aims of ethos of the conference - to become the single point for everything server-side Swift.
growing one helps grow the other
noise between mixing conference and general SSWG chatter
an implicit bias to the conference. Yes we're non-profit and (currently) the only conference focused on SSS but by choosing the conference as the home then it could provide an unfair advantage to the conference (one for the workgroup to discuss). This could of course work out for both by growing both, making both more 'official' etc but probably not a conversation I can take part in
Happy to discuss further and see what people say. As for the Slack vs Discord discussion, I'm easy either way. Discord has some better code support and we can have full history, on the other hand it's easier to get Slack into companies and installed on machines and Slack is more focused on messaging and less on gaming
Those are good points. I like the idea of helping grow one to grow the other. That being said, I would still say that anything other than Discord would be a poor solution for a large community-based network. Sure, the group may not have the size of audience at first that would require unlimited storage and better role management/permissions but I'd rather start in one place than have to go through the process of moving everything over once that possibility becomes reality.
There are actually quite a few very large code communities that already exist on Discord. Off the top of my head:
Mozilla is going through a similar journey in trying to replace IRC for their chatting needs. Last I heard they, among others, rejected Discord:
Discord’s terms of service, particularly with respect to the rights they assert over participants’ data, are expansive and very grabby, effectively giving them unlimited rights to do anything they want with anything we put into their service. Coupling that with their active hostility towards interoperability and alternative clients has disqualified them as a community platform.
Expanding on the last sentence, their love of open source seems to be restricted to publishing small components and expanding their user base with open-source communities. Any kind of open-source client at least seems to be out of the question, even if it were just a heavily modded official client.
Sadly I don't really have a better alternative to recommend (except the one a few friends and me are surely going to write any day now ), but I don't like the idea of moving to yet another closed-source, vc-funded startup's ecosystem.
Maybe "the next big thing" in free software chat-/voice-communication could be a good proving ground for server-side Swift (plus a wasm client?) :D Not very relevant for now, but one can dream
Why being so negative, focus on the possibilities! ;-) This stuff was hacked up in about two weeks' sparetime or so.
Not that I was serious about this, but there is something called IRC bouncers since forever. And it would be easy to add persistence, e.g. by storing messages in Redi/S.