Minor thing that bugs the heck out of me: I can't login to Slack, it's a total outage for me, but on their status page [0] their copy says, "Something's not quite right."<p>In reality, there are probably folks freaking out internally at Slack with their hair on fire, and probably tens of thousands of people are locked out of their business comms. Saying "something is not quite right" trivializes and downplays the severity.<p>No! Something like, "We have a real problem" would be much more appropriate and not pretending like "oh it's no biggie, we'll take a look later."<p>[0] <a href="https://slack-status.com" rel="nofollow">https://slack-status.com</a>
Our company of >100 people is all remote and all our internal comms are through Slack.<p>The silence is deafening, surprisingly so, when Slack goes down like this. It happens so rarely (to the Slack team's credit), but when it does, it feels just like when the power unexpectedly goes out.<p>We totally forget how much we rely on it until it disappears.
Purely coincidence but we just posted about emdash, our Slack/Zoom alternative on Shown HN:
<a href="https://news.ycombinator.com/item?id=43184362">https://news.ycombinator.com/item?id=43184362</a><p>Check it out @ <a href="https://emdash.io" rel="nofollow">https://emdash.io</a>
Four hours and still broken for me. Not sure if we will get a postmortem but very curious what went wrong.<p>Good luck to SREs over there! (I know, they would say luck is not a strategy)
> Our investigation is still in progress with regard to deprecated functionality for Slack features such as workflows, threads, sending messages and API-related features.<p>I'm not sure what their status page is talking about, is sending messages a deprecated slack feature?
Everything seemed fine at around 9:00 AM PST (UTC-8). A few minutes later, I made the mistake of reloading Slack after a few messages began failing to send. Haven't been able to access my company's Slack workspace since. At the time of writing this post, it's now 11:00 AM PST.<p>Emailed my manager explaining the situation. Hopefully they can understand. Also plan to ask others about Slack alternative for situations like this. For now, we are relaying things through e-mail.
Based on the status report, it seems like it was related to a database disaster and mention recovering shards. Publicly they say they are using vitess[0] so I wonder if there was some issues there.<p>I wonder if there will be a more detailed post-mortem, would be super interesting to learn more!<p>[0] <a href="https://slack.engineering/scaling-datastores-at-slack-with-vitess/" rel="nofollow">https://slack.engineering/scaling-datastores-at-slack-with-v...</a>
This is another remainder that crucial business communication should be based on self-hosted solutions to be independent on third-parties and for privacy reasons. There are good and even more lightweight open source Slack alternatives: Nextcloud Talk, Mattermost, Zulip, Element.io, Jami, to name a few. Relying on a third-party provider is asking for trouble. Plus giving away your private business conversations to feed AI and NSA is another thing.
Came to post the same. The mobile client still seems to work for me though but the electron client is down.<p>Edit: the mobile client loaded messages but also fails to send.
All my apps are returning an auth:test fatal error:<p><pre><code> AuthorizeError: Failed to call auth.test API due to Failed to call auth.test due to fatal_error
</code></pre>
The slack app management page also seems down