Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack is down for some users

status.slack.com

Post reply on HN
Print view View original

131–137 of 137 posts

Re: Slack is down for some users

#131

Post by stjohnswarts »

aftbit wrote: post #57
anderspitman wrote: post #36

The cool thing about Slack (and Discord for that matter) is that it's essentially federated on a technical level. SlackHQ controls all the instances, but the UX is very achievable by an open source alternative. I'm bullish on federated chat in the next few years. It would be awesome to have essentially the same experience as using Slack, but also a server running on our lab's hardware that we can reboot/debug ourselv…

Element/Matrix is getting pretty close, and is federated at the protocol level.

I think "first comer's advantage" will win over for the really big outfits like apple, ibm, intel, etc because they've gone through integration pains with other services and don't want to go through that pain organization wide. However, I think small to mid-size businesses could find some migration from slack to matrix pretty advantageous.

Re: Slack is down for some users

#132

Post by Mandatum »

zestyping wrote: post #110
epivosism wrote: post #72

Surprised no one is talking about how awesome slack is. Think about it in user stories: * I want to find someone by name => ctrl+K * I want to search with sane keywords => search, "from:me" "to: " work. * I want to remember someone I talked to recently => people you chat with show up in the list on the left * I want to keep com channels organized as the ground changes => easily rename channels, favorites UI works wel…

Significant regressions in Slack: * I used to be able to type a message containing "@channel" or "@here" and just hit Enter without looking, and 100% of the time it would be parsed correctly. Now it fails to detect the "@channel" or "@here" often enough that I have to look to see if it failed, then go back and retype that part of the message until it lights up. Once a week or so, I see a message posted by someone els…

> * Recently Slack pushed everyone to switch from usernames to full names with spaces, and eliminated the entire concept of unique usernames.

That's your Slack settings my dude, blame your admins.

Re: Slack is down for some users

#133

Post by bitexploder »

bun_at_work wrote: post #120
edgyquant wrote: post #103

Earlier quoted context omitted.

I don’t understand why zoom is so much more popular than Google meet. I never used zoom before my current company who uses Google meets for daily meetings and then zoom meeting for the biweekly review. No idea what advantages zoom is supposed to have.

It seems like the popularity of Zoom is related to the singularity of the product's purpose. Zoom is a video conferencing service. Google is everything and the kitchen sink. So when the pandemic started, that worked in Zoom's favor, sadly.

Thick clients perform better than Google Meet in the browser in my experience.

Re: Slack is down for some users

#134

Post by twistedpair »

alberth wrote: post #116
twistedpair wrote: post #69

Earlier quoted context omitted.

Reminds me why we intentionally avoided tying core biz/dev workflows to Slack. :)

Devils advocate... Do you tie core biz/dev workflows to Github (or any other service)?

Requiring GitHub to deploy your code to prod... goodness no.

Using, highly available, deterministic artifacts, that can be rapidly deployed or reverted from production is what we do.

Re: Slack is down for some users

#135

Post by Forbo »

legofr wrote: post #29
nate wrote: post #15

One fun thing we discovered an outage or two ago: Zoom, which is likely already on your computer too, has a very Slack-like Chat feature. Open up the Zoom app, then click the Chat icon in the top header. You probably missed it this entire time. You can make rooms, DMs, animated gifs, the works :)

That spyware thankfully isn't no mine, and if you're forced to use it (if you for whatever reason can't use Jitsi/Teams) then I strongly encourage you not to install the app and instead use the web version.

Why is Slack considered spyware but not Teams?

Re: Slack is down for some users

#136

Post by kawsper »

bmhin wrote: post #123
treesknees wrote: post #114

Earlier quoted context omitted.

On the contrary, I find Slack threads to be very annoying for discovering/stumbling upon conversations. Your whole team could be having a new discussion within a thread and you'd never know unless you participated in the thread previously or somebody @'s you. Compare that to more IRC-like discussion where each message is posted to the channel. Sure, you may end up with contextual issues reminiscent of the IRC days, b…

I've used Slack competitor Flowdock in the past which did the more "elevated" approach to threads. Rather than "hide" them from the main branch of a channel, the main branch had every message in the top level and you could collapse to a thread view if you wanted to read it in isolation. In my experience, the main problem here was that people regularly lost sight that a conversation even was in a thread. So they'd pos…

The issue you mention with Flowdock, in my experience, only happened for newcomers to the product, they added a button to add an unthreaded comment to a thread in later versions.

I prefer Flowdocks threading model, it's too bad what happened to the product after being bought/sold, but I think it was a superior product.

Re: Slack is down for some users

#137

Post by throwdbaaway »

https://status.slack.com/2022-02-22 has been updated with this:

> A configuration change inadvertently lead to a sudden increase in activity on our database infrastructure. Due to this increased activity, the affected databases failed to serve incoming requests to connect to Slack. We introduced tighter rate limits on connection requests to reduce the load on the system. This meant that some people could not access Slack at all, but also that Slack would continue working for those who were already connected.

> Once the system had stabilized, we began lifting these rate limits to enable more connections to Slack. However, we moved too quickly and the increased activity affected the system again. We reinstated the rate limits and redirected some traffic to the database replicas to relieve the demand on our primary databases.

I wonder if their bottleneck is at vitess vttablet or at mysql.

Post reply on HN