re: Discord post-mortem from a cloud engineer on the outside
You could say "That's just hobby stuff" but one of the events that comes to mind has five digit USD yearly take for charity so it matters to some degree.
re: Discord outage post-mortem, comms meta
@trysdyn @jonw as an activist, also yes.
Distressing is putting it mildly, the ramifications of this are...very troubling, professionally speaking.
Discord is a freely accessible communication platfor. If you have an OS that supports HTTPS, you can use it.
I've initiated a migration decision, but this will be weeks of collaborative effort, and there's not time this month, for certain.
The amount of organizational stuff that gets discussed, pinned, and then referenced for research and documentation is huge.
We have dozens of channels where pinning requires a pruning of the backlog, and the fact that none of that data is portable keeps me, a sysadmin, up at night.
This is my comms nightmare confirmed.
re: Discord outage post-mortem, comms meta
Here's the real problem:
Matrix is nowhere near being a solution.
IRC has no permanence.
XMPP has never *quite* worked on mac and windows, although Pigeon under Linux performs well.
Keybase is centralized and probably a honeypot.
SSB is...lacking in a method for realtime comms? (can someone who knows scuttlebutt confirm this?)
Email is a marginal and increasingly noisy spectrum.
RocketChat is a useability disaster.
Mumble authentication and web integration is convoluted and crufty.
I haven't yet attempted to deploy Mattermost, SSB, or Zulip.
Anyone have hands-on user or administrative/backend experience with those?
fuchsiaaaaaaaaaaaaaaaaa
re: Discord outage post-mortem, comms meta
@eryn @trysdyn @jonw@hackers.town would you mind elaborating on "Matrix is nowhere near being a solution"?
I use it as my primary communication platform (with my own server) and already much prefer it over IRC. Although the clients are lacking it's still been a *much* better experience than XMPP for me
