News for hackers. Stuff that matters.
Re:A terrible, horrible, no-good, very bad day at Slack by k__ on Tuesday July 07, 2020 @09:12AM (#23758833)
After I used Discord in different contexts for months now (and Slack for years), I can't understand why someone willingly chooses Slack.

It's the Atlassian of chat tools. Horrible performance and bad usabillity.

Re:A terrible, horrible, no-good, very bad day at Slack by jrockway on Tuesday July 07, 2020 @09:19AM (#23758904)
As someone who uses Discord, I can tell you it goes down too. My favorite part is looking at their status page, seeing that API response time is exceedingly high, and getting no updates from the team about whether or not they're fixing it.
Re:A terrible, horrible, no-good, very bad day at Slack by k__ on Tuesday July 07, 2020 @09:39AM (#23759122)
I'm not saying Discord is perfect or "always up", it's just that their client UI is better structured and more responsive in most cases.

I am on multiple OSS Discord servers with thousands of users, and it works just fine most of the time.

I am on multiple Slack servers with just 10-20 users and it is unbearably slow.

Re:A terrible, horrible, no-good, very bad day at Slack by rpdillon on Tuesday July 07, 2020 @10:04AM (#23759384)
I admined a multi-hundred user Slack org and now am part of a multi-thousand user slack org and I've never experienced (or heard about) the slowness that you're describing. Do you have a feel for whether it was client-side or server-side?
Re:A terrible, horrible, no-good, very bad day at Slack by k__ on Tuesday July 07, 2020 @11:10AM (#23760049)
More client-side.

Server-side scaling was only an issue with OSS communities and for hackathons, where >50k people were online.

Re:A terrible, horrible, no-good, very bad day at Slack by carterklein13 on Tuesday July 07, 2020 @01:24PM (#23761577)
I think Discord's Achilles' heel for enterprise is its UI unfortunately.

There's no way that my company would adopt a platform so "fun" in the way Discord tries to be. Animated characters, a logo which looks like a gamepad, etc...

It sucks, because I use Slack for work and mostly Discord for personal use (mostly dev communities for different companies), and Discord is far and away a better experience. If Discord provided a "cleaned-up" offering for orgs like mine (finance), I think it would be an instant hit.

Re:A terrible, horrible, no-good, very bad day at Slack by buzzert on Tuesday July 07, 2020 @02:16PM (#23762284)
I log on to Slack at work and see pages of emoji, animated gifs, and animated reactions. What’s the difference?
Re:A terrible, horrible, no-good, very bad day at Slack by bhahn on Tuesday July 07, 2020 @02:51PM (#23762696)
Discord is actually actively trying to become less gamer-focused, but it's unclear if this will make them as enterprise as Slack or Teams is.

https://techcrunch.com/2020/06/30/discord-now-has-a-3-5b-val...

Re:A terrible, horrible, no-good, very bad day at Slack by pier25 on Tuesday July 07, 2020 @10:55AM (#23759883)
Yeah the performance of Discord is much better but it looks and feels like a product for gamers.

Slack has a more mainstream look and feel which is probably one of the reasons it's preferred by companies.

Re:A terrible, horrible, no-good, very bad day at Slack by bobobob420 on Tuesday July 07, 2020 @11:17AM (#23760118)
What are some open source discord servers you are a part of? I would like to know about some open source communities if you do not mind.
Re:A terrible, horrible, no-good, very bad day at Slack by k__ on Tuesday July 07, 2020 @12:13PM (#23760674)
I'm on the React and Rust servers.
Re:A terrible, horrible, no-good, very bad day at Slack by StavrosK on Tuesday July 07, 2020 @09:16AM (#23758872)
I use Zulip for the day to day (it's amazing, I can't recommend it enough), but sometimes use Slack because some open source communities use it, and I'm always amazed at how damn slow it is. I can consistently out-type it, it's terrible.

I guess it was great when it started out, but they're slowly boiling the frog, who is us.

Re:A terrible, horrible, no-good, very bad day at Slack by mikecoles on Wednesday July 08, 2020 @12:55PM (#23771742)
Zulip won my last bake-off for chat systems. Integration was easy and the topic method of providing threads was amazing. The only feature it was missing was federation. In the XMPP world, you could communicate with users on other XMPP instances. With Zulip, you can only communicate with local users. Do you know if this is still the case?
Re:A terrible, horrible, no-good, very bad day at Slack by tabbott on Wednesday July 08, 2020 @02:47PM (#23773001)
As other folks have mentioned, Zulip has a number of cross-server integrations with both the Zulip protocol and other protocols like XMPP. There's a few we document here as well as Matterbridge:

* https://zulipchat.com/integrations/communication * https://github.com/42wim/matterbridge

We'll eventually add a more native way of connecting a stream between two Zulip servers; we just want to be sure we do that right; federation done sloppily is asking for a lot of spam/abuse problems down the line.

(I'm the Zulip lead developer)

Re:A terrible, horrible, no-good, very bad day at Slack by twizzerlora on Wednesday July 08, 2020 @01:24PM (#23771997)
Zulip has a cross server bridge using a bot that you might be interested in:

https://github.com/zulip/python-zulip-api/tree/f47559e68dfcc...

Re:A terrible, horrible, no-good, very bad day at Slack by StavrosK on Wednesday July 08, 2020 @01:01PM (#23771809)
Yes, I doubt federation will ever be added.
Re:A terrible, horrible, no-good, very bad day at Slack by scaryclam on Tuesday July 07, 2020 @01:44PM (#23761876)
That's one thing that makes me quite sad, to see open source communities adopt a closed chat tool. I know that it's easy and zero-maintenance for them, but I can't help but feel there are better options.
Re:A terrible, horrible, no-good, very bad day at Slack by StavrosK on Tuesday July 07, 2020 @01:54PM (#23762025)
There certainly are, Zulip is OSS and so is Matrix.
Re:A terrible, horrible, no-good, very bad day at Slack by taormina on Tuesday July 07, 2020 @09:39AM (#23759110)
Well, Hipchat would be the literal Atlassian of chat tools.
Re:A terrible, horrible, no-good, very bad day at Slack by k__ on Tuesday July 07, 2020 @09:40AM (#23759123)
Ah yes, they have their own thing now :D
Re:A terrible, horrible, no-good, very bad day at Slack by miloignis on Tuesday July 07, 2020 @10:17AM (#23759509)
They've actually been shutting it down for a while after Slack bought it from them to do just that.
Re:A terrible, horrible, no-good, very bad day at Slack by orbz on Tuesday July 07, 2020 @10:00AM (#23759355)
HipChat was sold from Atlassian to Slack.
Re:A terrible, horrible, no-good, very bad day at Slack by k__ on Tuesday July 07, 2020 @10:17AM (#23759507)
Oh .... okay?
Re:A terrible, horrible, no-good, very bad day at Slack by whatsmyusername on Tuesday July 07, 2020 @10:32AM (#23759660)
Because it's the Atlassian of chat tools. It's the lowest common denominator.

Discord also doesn't let you set message retention that I'm aware of which is an immediate nonstarter.

End up in one lawsuit where the other party demands a fishing expedition and you'll be real happy that you've got retention limited to 90 days by policy and in practice.

Re:A terrible, horrible, no-good, very bad day at Slack by jessaustin on Tuesday July 07, 2020 @12:53PM (#23761130)
If it's legal to set this to 90 days, why can't a firm set it to one or zero days?
Re:A terrible, horrible, no-good, very bad day at Slack by whatsmyusername on Tuesday July 07, 2020 @02:13PM (#23762266)
You could, and I'm sure some places have a business case for this.

Most need stuff going back at least a little bit. If I was talking to you about something on Friday and wanted to reference the conversation Monday I'd be real mad if the convo was already deleted.

Re:A terrible, horrible, no-good, very bad day at Slack by jessaustin on Tuesday July 07, 2020 @03:56PM (#23763320)
I think I'm confused... there are complaints above that Discord doesn't save transcripts. That seems equivalent to zero-day retention? I haven't used Discord so I'm probably misunderstanding something.
Re:A terrible, horrible, no-good, very bad day at Slack by whatsmyusername on Tuesday July 07, 2020 @10:52PM (#23766471)
If I scroll back in discord I can go back to the first message I ever sent to the servers I hang out on.

In slack you can configure a retention period for files, messages, or both. Anything older than that gets wiped.

Re:A terrible, horrible, no-good, very bad day at Slack by qppo on Tuesday July 07, 2020 @11:30AM (#23760236)
Saved chat history is the big one. Discord is not suitable for business comms without it.

Other than that:

- shared channels between workspaces

- threads

- private messages within a workspace, instead of globally

- decoupled accounts from workspaces, so I can use my personal email and work email associated slack workspaces at the same time

- much tighter integration with third party tools eg zoom, webex, etc

Discord is great for casual chats with friends or open source communities. Insufficient for business.

Re:A terrible, horrible, no-good, very bad day at Slack by k__ on Tuesday July 07, 2020 @12:14PM (#23760690)
How come? Me phoning or talking with a customer/co-worker directly is also "suitable for business".
Re:A terrible, horrible, no-good, very bad day at Slack by jessaustin on Tuesday July 07, 2020 @12:52PM (#23761110)
I think this is why we often get that "this call may be recorded for training purposes" message while waiting in the call center queue? Even if they're not actually keeping all those recordings, they can pass the legal test by saying that they do.
Re:A terrible, horrible, no-good, very bad day at Slack by qppo on Tuesday July 07, 2020 @12:21PM (#23760759)
Chat history is pretty important for your HR and general counsel if there's instances of misconduct or abuse. Discord doesn't support the same level of chat history/logging that businesses (of all sizes) care about.
Re:A terrible, horrible, no-good, very bad day at Slack by k__ on Tuesday July 07, 2020 @02:29PM (#23762425)
I know.

I just don't understand why it's important for text based communication, but not voice.

Re:A terrible, horrible, no-good, very bad day at Slack by xtracto on Tuesday July 07, 2020 @09:47AM (#23759186)
Threaded comments. I tried using Discord with a group of 4 people for real job and we missed threaded comments.

Also the ability to draw on screen while screen sharing. So simple yet so useful.

Re:A terrible, horrible, no-good, very bad day at Slack by k__ on Tuesday July 07, 2020 @09:52AM (#23759253)
Interesting.

I personally didn't like threads and this is the first time someone mentions them favorably.

Re:A terrible, horrible, no-good, very bad day at Slack by xtracto on Thursday July 09, 2020 @04:33PM (#23784830)
Funny that I found it easy to see your comment in HackerNews because it was separated in ... a thread!

Imagine how HackerNews, Reddit or any other discussion board would be without threading. Now, if you see a #general Slack room of a 100 person company, you'll quickly see that it would be a mess without threading. That's what happens in Discord.

Re:A terrible, horrible, no-good, very bad day at Slack by snazz on Tuesday July 07, 2020 @10:36AM (#23759693)
Now that even iMessage supports threaded discussions (in iOS 14), I think it would be great if Discord added this too. They’re very nice when there are multiple overlapping conversations and you don’t want to break off into two separate channels.
Re:A terrible, horrible, no-good, very bad day at Slack by phumbe on Tuesday July 07, 2020 @01:44PM (#23761873)
Since you’re a skeptic, I’d love to hear your thoughts on my reply to xtracto!
Re:A terrible, horrible, no-good, very bad day at Slack by anderspitman on Tuesday July 07, 2020 @09:57AM (#23759309)
I missed them in discord just yesterday
Re:A terrible, horrible, no-good, very bad day at Slack by phumbe on Tuesday July 07, 2020 @01:41PM (#23761840)
Shameless plug for my side project: XpanXn.com

The central value proposition is its reimagined UI, making threaded replies more visible and more interactive by separating conversation topics (threads) into different columns.

It’s currently just an MVP, but I expect to at least improve the UI and maybe rearchitect the system in the near future.

Any feedback is greatly appreciated!

Re:A terrible, horrible, no-good, very bad day at Slack by rkrzr on Tuesday July 07, 2020 @09:43AM (#23759153)
We have been using self-hosted Mattermost for years and I can highly recommend it. It never crashes, performance is great, and upgrading it is very easy to do.
Re:A terrible, horrible, no-good, very bad day at Slack by ponker on Tuesday July 07, 2020 @04:29PM (#23763657)
The big requirements for enterprise use are: single-sign on, compliance with regulations (e.g. a multinational company needs to know that you are in compliance with the laws around data retention, data locale, etc. for their own data, in every country that it operates in), and API support for eDiscovery.
Re:A terrible, horrible, no-good, very bad day at Slack by luisehk on Tuesday July 07, 2020 @09:47AM (#23759198)
Because Discord is very gaming oriented. But yes, Discord is great.
Re:A terrible, horrible, no-good, very bad day at Slack by applecrazy on Tuesday July 07, 2020 @10:38AM (#23759717)
Actually, they’re pivoting to be a social platform for non-gamers, too. Just yesterday I got a notification that they’re pushing for more non-gamers to create their communities on Discord.
Re:A terrible, horrible, no-good, very bad day at Slack by Tyr42 on Tuesday July 07, 2020 @09:38AM (#23759103)
Oh no poor HipChat. (Atlassian's chat tool)