@sir user discord instead!
Is it ok to use slack for an internal chat for sysadmins?
Practically all internal communication is done with Facebook, because why not? It's the lowest common denominator. Messaging is done through Facebook messenger, teams are private groups, etc.
Except one group has resisted this: the sysadmins.
Sysadmins need to be able to communicate at all times, /especially/ if things aren't working. And it turns out that there's no way to make sure things like Facebook messenger always work—especially during outages. They're just too damn complicated.
So, they came to a compromise. The rest of the company will move to Facebook, and the sysadmins will stay on IRC, the communication platform they know they can rely on.
When Facebook's on fire and the company is panicking because they can't communicate, you can be sure of one thing: the sysadmins are chatting away on IRC about how to get it working again.
"Google has found IRC to be a huge boon in incident response. IRC is very reliable and can be used as a log of communications about this event, and such a record is invaluable in keeping detailed state changes in mind. We’ve also written bots that log incident-related traffic (which is helpful for postmortem analysis), and other bots that log events such as alerts to the channel. IRC is also a convenient medium over which geographically distributed teams can coordinate."
@pounce @sir @Wolf480pl this is not solely a problem of Facebook and the greatness of IRC. Any system will go down at times and if you are the one to bring it up again you better have another way than that system to communicate. Of course, IRC being a battle-proven and resource-friendly technology is a good choice for this. Yet, unless you are operating Slack, you can of course also use that. Just have a backup plan on what you do if your Internet, or Slack, goes down.
You'll notice that slack always goes down then you need it the most.
OTOH, IRC never goes down. Sometimes it has netsplits, but even then you can still communicate with some of the people in the channel, and you can hop servers to find everyone else.
IOW, IRC is more resilient.
@sir What alternatives could you suggest? IRC is text-only and primitive and Matrix is slow and I haven't yet seen a client with decent UX. I haven't used Zulip or Mattermost yet, I've only heard of them.
@phoe IRC is king, text-only is a feature not a bug
@sir @slp Of course it's a feature - unless you want to chat with someone who isn't a complete and total developer nerd like me or you and wants standard contemporary features like automatic image uploads, conversation threads, channel history, or if you want to build a community of non-technological people around your software. At that point, I observed that people prefer to leave rather than stay on IRC.
Or they start Discord servers of their own.
It's a pity, since it worked perfectly fine, was self-hosted and had features that Slack still lacks (for example, the ability to implement bots that push custom HTML in replies).
@slp @sir Yep - my case is perhaps a little bit more specific. I want a means of collaborating with people who are both deeply technical and deeply non-technical, and also includes most (or at least some) of the features I have listed above. When it comes to programming, I'm eager to nerd all over Freenode, but when it comes to collaborating with non-technerds, I'm looking for something more featureful, or the community will go set up a Discord server anyway.
yet: if everynerdy did that, nerds would be dead within a few decades entirely.
nobody's born a nerd. people don't learn in a vacuum. some people need people contact to learn, or pictures, or whatever.
if you're not volunteering to teach, that's understandable -- I refuse too -- but from someone with severe learning problems, I can tell you accessible isn't just cheap hardware
it's unicode, screenreaders, pictures, text-to-speech, and sometimes people contact
just saying ❤️
I cut my teeth on Doom, son. ;) I'm aware. And I flailed desperately for years and years, mostly due to my learning defects and low tolerance for frustration.
This is also arguably an example of the "well X was just fine why would we Y"? We didn't go to the moon for years and years, said people during the space race -- why bother now? It's a waste of money, yeesh.
Nobody knows what lies beyond their space if they refuse to innovate past what they are already comfortable with.
If you're using lynx right now to toot things, I will literally accept that you literally believe this.
Especially if you don't have a smartphone (which was decried as 'dumbed down' computing by some, IIRC).
Otherwise, I'm going to assume you believe it in some sense, in a "well I had to so they have to" sense. And I'm gonna tell you, as someone who thought that way a long time: It doesn't move forward. It is stationary.
It is, long-term, quite unhelpful. (IMO, obviously.)
And no, "Nerds" won't die. Your concept of them, though, could -- things that refuse to maintain or grow die, and fertilize the things that are willing to grow. The "old guard" of "real" techs, or whatever this concept is; yes, they'll function. But as a slim minority at best. It's endless meta-November forever, all the way down.
This is meant as food for thought, assuming people are looking for that.
Anyway: Be well. ^_^
(oh, and I forgot: I don't think I actually said that they'd die? I was saying they'd be excluding people that might be interested, and if they're doing it out of "well fuck you" issues, then it's probably illogical and unnecessary. since logic is more important than feelings under all circumstance, it'd probably be logical if the old guard passed on their stuff, however they can, to people who can use it after they're in the ground.)
cmpwn.com is a private Mastodon instance for friends of SirCmpwn.