191–200 of 225 posts
Slack has been a nightmare since the start of August - my assumption is they just can’t handle the increased level of data going through their servers with the increase in video they will now be handling
EDIT: problems == sustained issues. Yes, there are occasional blips.
Edit: Not just for slack, but 2020 in general
The current thread title "Users may be unable to connect or experiencing degraded performance" seems like it could be used to just sum up 2020. Edit: Not just for slack, but 2020 in general
Edit: Folks, I was kind of half joking and making fun of NDT. And we're discussing the definition of "Arbitary" and harvesting seasons. Lighten up people.
Earlier quoted context omitted.
> slacks operational transform or CRDT implementation or whatever they use to get edited messages to converge I'm pretty sure they have none of that, considering you can only edit your own messages. So what's likely happening is that two quick edits are reaching the server at the same time and overriding each other.
I could be wrong but i'm relatively sure that I reach message states that do not directly correspond to anything i typed into the editor -- which i wouldn't expect if the edited state was always sent in full rather than as a delta on a previous message state. I suppose it's possible that the corruption happens on the client side tho -- 1. initiate edit action and get editable view of snapshot of text 2. server acks s…
You'll get more downtime hosting your own chat server. But you can also fix it immediately when something breaks.
Assuming that a random company will pay to have engineering/ops staff on-call 24x7 who all have enough knowledge about their internal chat system.
Some interesting logs most people can understand:
[REDACTED] info: [OPPORTUNISTIC_RELOADS] User has been blurred for 1200000 ms, evaluating whether or not we should reload opportunistically
[REDACTED] info: [OPPORTUNISTIC_RELOADS] Client is still visible to the user even though it is not focused, will avoid updatingSlack has been a nightmare since the start of August - my assumption is they just can’t handle the increased level of data going through their servers with the increase in video they will now be handling
A heavy user for the last 2 years, and I have not noticed any problems until today. EDIT: problems == sustained issues. Yes, there are occasional blips.
The screen sharing one is so bad I have to send zoom links out if I think I’m going to screen share in a call
Earlier quoted context omitted.
If you're question is it a viable alternative to Slack for business purposes, the answer is no. And it's not bc of anything related to the application itself but because of the insane TOS. > By uploading, distributing, transmitting or otherwise using Your Content with the Service, you grant to us a perpetual, nonexclusive, transferable, royalty-free, sublicensable, and worldwide license to use, host, reproduce, modif…
Are these licenses actually enforceable? Those absolutely seem like overreach in terms of what someone would consider reasonable from a user perspective.
You'll get more downtime hosting your own chat server. But you can also fix it immediately when something breaks.
that includes deployments, updates, security audits, etc.