3 ms·
In a lot of corporate environments, "self-hosted" is not an advantage if you're the one trying to set up something new. In order to self-host, you have to go th
by quicklime 6y ago
In a lot of corporate environments, "self-hosted" is not an advantage if you're the one trying to set up something new. In order to self-host, you have to go through your corporate IT department to provision servers. This alone can take 6 or 12 months, and you still have to find someone to maintain the service.
And the kind of companies that value self-hosting will usually want this to be set up inside the company's internal network. So you'll have a bunch of firewall issues to get through, otherwise good luck getting your users to connect to some non-publicly-accessible server from their phones.
Other comments talk about how Slack nailed the UX for users to join a Slack workspace. But they also nailed the UX for getting a workspace set up in the first place.
(Well ok the whole idea of separate accounts per workspace thing is a bit of a mess, but they nailed everything else)
- JoBrad 6y agoIt took _forever_ to get a self-hosted Jabber-based chat client going at a mid-sized corporation, about 10 years ago. Someone went “rogue” and set a server up anyway. Our security staff began blocking ports, so it eventually died anyway... in favor of Skype and Yammer. All because no one wanted to host chat history and a server.