Slack was down
status.slack.com
status.slack.com
If you do bring your work phone. Log yourself out of everything as well.
More friction, less problems :)
There are to many damn chat apps, someone make a memey ffs.
> A modern emergency response center housed on a reliable digital platform ensures teams are ready for emergency response at a moment’s notice.
...
Seems like you just googled some reliability article to make this comment? Lol
You can become burned-out using any tool, and even without using any tool.
Far easier to abuse by bad actors than email.
Patch out the phone-home Segment spyware and selfhost a Mattermost, or a Zulip, or a Discourse (for non-real-time) for your team.
Selfhost a Gitea and a Drone.
It's more simple than you think, and you can backup and restore it onto a new hosted VM in minutes.
For some companies self-hosting might make sense. For others, the overhead isn’t worth it.
[0]: Fork of Gitea, discussed here previously. Recall that Gitea is itself a fork of Gogs!
I really hate the: For support with CompanyA make account to use service provided by CompanyB to contact A.
Every time I have to use a Slack/Discord to reach a company I'm spam/alert bombed all over again - triple annoying.
Just to clarify, by patching out, all you need is to disable a config setting: https://docs.mattermost.com/manage/telemetry.html. It's not like you have to modify the code or anything more intrusive.
Still not 100% sure why I pay for Slack, when even Skype has better IM
Might cancel our sub and go to discord
#quakenet
On IRC you had netsplits where half of the people could still talk to each other and the rest were disconnected. I would guess it was equally rare (back when I used irc more, 8 years ago?) as outages of "centralized" services today.
On slack the only indication that anything was wrong for the past 2 hours was that my co-workers weren't responding.
So it's possible that slack has as many faults as IRC or more but we don't know because the interface is so dishonest/corrupt.
Because aside from the capability to send a message, their respective features and use cases are totally different?
So we will switch tomorrow?
Not so fast: it is such an upheaval changing chat system company wide - thats how they get the retention!
I will also say, teams may actually be better aligned for business use given two reasons, threads promote conversation focus, and threads also make me not want to post idle thoughts. A lot of slacks devolve into chatter, making a thread for a minor thought doesn't feel right. Upside, less idle chit chat, downside lots of things probably go unsaid and it's a less communal feeling.
We dont really use the Teams part for Chats. Only for incidents or company wide stuff.
- It doesn't allow viewing both the (text) list of people and chat at the same time
- The vast majority of the time, people don't include a dial-in. This, alone, kills it for me
- Every time I want to mute myself, I wind up needing to search for the mute button (I know it's in the same place every time, but the fact that I need to "find" it every time tells me there's something poor about it's placement; I couldn't say what, though)
- It's an extra step opening it in the browser, because it tries (twice) to get you to open the application.
It's a death by 1,000 cuts. Just tons of little things that make it annoying (and the one big "no dialin" thing)
I reluctantly let the company switch to Slack. But 100% driven by employee demand/satisfaction. If as an IT person I recommend anything other than Slack, it will immediately get shot down if I do a poll of employees. Employees like slack for whatever bizarre reasons, even when comparing it to basically identical chat apps.
It’s almost like making a Mac person switch to Windows (or vice versa). People have a strange emotional connection with Slack making it hard to use anything else.
> People have a strange emotional connection with Slack
Seems to contradict: people don't have a strange emotional connection, they value the integrations, apps and familiarity.
As for running the server, I cannot recall any bigger problem I had, Zulip runs in our org for more than 5 years.
Backups are also pretty easy to setup.
If you committed to changing the services you paid for every time one went down, you’d
A) spend a ton of time migrating your workflows instead of being productive B) eventually run out of options because everything goes down at some point