We host Rocket.Chat ourselves (300+ people company), and when it's down (which is very rare), all it takes is to make a visit to the IT guy on the same floor. Also our infosec people are happy sensitive data is not stored on servers we don't control. There've been attempts to move to Slack or Google Chat without success. Is there something we're missing by not using Slack?

Did you intend to reply to the person you did?

My understanding of the parent post was poking fun at the fact that these chat spaces (Slack or otherwise) allegedly end up being a productivity loss as people spend more time finding the meme-of-the-week to post rather than working.

Nothing to do with the viability of Slack or whatever instant messenger you choose to use.

Yes, my bad.

Contrarily for me I can not add myself to company VPC, because the command works on Slack. What a bummer.

That's some terrible OPs and ridiculous single point of failure.

More proof that SlackOps/ChatOps is a failed methodology. I'm not quite sure what the fascination is with it. It's certainly neat for querying infrastructure but I certainly wouldn't rely on it for critical infra.

Maybe use this as an example that you guys shouldn't do that?

That feels like a leap too far. ChatOps should be a convenience, not the sole method of doing something. However conveniences are important.

I've had the luxury of building out an entire platform with ChatOps that built groups of people who had access to do deployments and mutate infrastructure.

It definitely was a neat project using chat flows, but I ultimately said "this is great until slack is down". Slack promptly went down the following week and we just threw our hands up and used the AWS console.

time to go home...

closes laptop. phew, short commute today.

the covid years sufficiently described

if i were a poet, i might have tried to put it in a meter. since i'm a coder, i made it a one-liner.

I'll do my next reboot at nine, I'll do my next commute with wine.