Mattermost: Open-source, on-premises, Slack alternative

http://www.mattermost.org/

by aviv • 11 years ago

432 216 11 years ago

mattermost.org

mosselman• 11 years ago

Cool :). It would have been nice to see some more screenshots or product videos in order to get a feel for it.

DoubleMalt3• 11 years ago

Nice project but the documentation is a bit terse (yet). We like https://github.com/sdelements/lets-chat atm.

Things that would be essential for me to use it in a company are

- LDAP or OAUTH integration - Hubot integration

I'm not sure Zapier integration cuts it for use cases where I want a self hosted solution.

vishaldpatel• 11 years ago

Will there be plugin support so teams can share their add-ons?

mijoharas• 11 years ago

Agreed, without a list of the features, or something to show what useability is like (does it support markdown? code highlighting? e.t.c.) it's tough to evaluate it.

Kudos to them for open sourcing it. It does look nice in the small pictures they have of it.

volent• 11 years ago

I don't really get why there is so many Slack alternatives coming up these days.

On every post like this there is tons of comment linking to other Slack alternatives, it's not like this is gonna be _the_ Slack-alternative.

Here is a non exhaustive list :

RocketChat : https://news.ycombinator.com/item?id=9624737

Let's Chat : https://news.ycombinator.com/item?id=9040841

Friends : https://news.ycombinator.com/item?id=9461504

Gitter : https://news.ycombinator.com/item?id=6739074

jsmthrowaway4• 11 years ago

Slack's success inspires derivatives and, in this case, a direct copy. Review the screenshots.

Before you get excited about Mattermost as the hosted Slack you've been waiting for, think hard about the AGPL licensing.

nzseth• 11 years ago

Why would that be a problem?

robmccoll• 11 years ago

Does anyone know if these or any others have native desktop and/or mobile clients?

sneak• 11 years ago

Or, more importantly, GApps OAuth/SAML SSO?

DonHopkins• 11 years ago

As long as Gitter was copying Stewart Butterfield, they should have named it "Gittr".

grizzles• 11 years ago

Anyone know which of these has an easy integration component for chatting with web visitors?

kidsil• 11 years ago

For me, only Gitter makes perfect sense. Because it's based on GitHub repositories, I can see why this should be used instead of Slack.

lmm• 11 years ago

So many slack alternatives are coming up because slack is really good. It's that simple.

richmarr9• 11 years ago

...and because so few people apparently realise that's Slack's value is in the quality execution, which can be copied by a decent team (but takes a phenomenal team to beat).

javiercr3• 11 years ago

It's like back in 2010 when everyone was building free / open source Basecamp clones.

jdp23• 11 years ago

Yeah whatever happened to all of those?

StavrosK4• 11 years ago

Has anyone used a self-hosted one they were satisfied with? Which one?

DoubleMalt3• 11 years ago

We are pretty happy with let's chat.

mrmondo2• 11 years ago

Let's chat looked great but we were a little put off by mongodb and something else that escapes my mind right now so we ended up sticking with OpenFire for our XMPP server / chat rooms for the time being although it certainly has it's share of bugs.

tadfisher3• 11 years ago

IRC.

it336• 11 years ago

Mattermost team here,

We think choice is good, and open source reduces the cost of creating more choice.

pjc50• 11 years ago

Choice itself is also a cost, beyond a certain point. The more alternatives, the harder it is to evaluate them all properly.

orkoden3• 11 years ago

I actually prefer todays web video to having to install RealPlayer, Quicktime, Windows Media Player, Flash player, Shockwave player just play video on the web.

Choice is not always good.

akhilcacharya• 11 years ago

But this one is written in Go!

it336• 11 years ago

Go is awesome!!

jmkni• 11 years ago

I guess it's because it looks like a pretty easy application to build.

'Looks like' being key there.

gukov• 11 years ago

https://scotch.io/courses/building-a-slack-clone-in-meteor-j...

ara4n2• 11 years ago

There's no harm in having loads of options - you just get a Darwinian survival of the fittest for which app works best. Competition is healthy.

The thing that sucks is that as end users we end up having all our chats and identity fragmented over all these different silos - be they selfhosted ones or proprietary SaaS. There's no way I'll rely on MatterMost or any of the above unless I can access my existing communities (be they on IRC, XMPP, Slack, HipChat or whatever); adding yet more fragmentation into the mix helps nobody.

This is why it's vital to have an open standard for decentralising the conversations between all these different islands that kills fragmentation whenever a new one pops up. And it's actually beneficial to new contenders like MatterMost as it could help them onboard users into their UX and app without having to start new conversations and contacts.

[Disclaimer: Matrix.org is such a standard, providing an open HTTP API for decentralised chatrooms, and I work on it.]

bad_user2• 11 years ago

You mean XMPP federation?

Nobody wants to implement that because companies like Slack, Atlassian, Google, Facebook, Microsoft, Apple, etc are interested in lock-in primarily.

colordrops• 11 years ago

One of the reasons there are so many alternatives is that many of us have been begging Slack for a self-hosted version for over a year and they are completely ignoring our requests. We want to give them a lot of money but apparently they don't want it.

pbreit3• 11 years ago

I don't think it would make much/any sense for Slack to deliver a self-hosted version. First, it is growing like crazy right now. And second, that would be a totally different animal in terms of coding, maintaining, supporting, marketing, etc.

orkoden3• 11 years ago

A great RFC instead a dozen incompatible startups would be the best thing since IRC.

fixxer• 11 years ago

The best thing since IRC is IRC.

jerf• 11 years ago

I'm not aware of any particular feature that doesn't fit into XMPP with a couple new namespaces at most.

And before you get too down on XMPP, bear in mind that anything that standardizes half-a-dozen chat clients will end up pretty nasty on its own, too. It all looks simple when you're a user of the client, but under the hood chat systems get... "interesting". In the apocryphal Chinese curse sense.

dbecker• 11 years ago

I recently switched from a company using HipChat to a company using Slack, and the differences seem mostly cosmetic and immaterial. Are the differences between these various chat programs big enough to affect user experience or productivity? What distinguishes one from the next?

joesmo3• 11 years ago

You mean that slick, plaid UI with neutral, low key colors doesn't enhance your productivity? That's the whole reason I moved from HipChat to Slack.

davis_m• 11 years ago

One of the biggest differences for us was the option for a self hosted solution with HipChat. Both companies are fairly open about accessing user communications without any sort of permission or audit trail. Being able to self host it ensures that Atlassian or Slack employees aren't dropping into our chats.

segmondy• 11 years ago

10,000 message limit for free version.

You might have sensitive information you need contained in your network.

It get's expensive very fast.

JustSomeNobody• 11 years ago

Probably the same reason there's a new javascript framework every week. Some people think it's cool and want to build their own.

For better or worse.

jakejake• 11 years ago

I think when developers see a simple, successful product they say to themselves "hey, I could do that!" So we wind up with a thousand to-do apps. Slack is a step or two in complexity beyond a to-do app. Simply copying a product like slack is not that difficult. Building an "amazing" version of a product while re-inventing small details is the clever part.

Cymen• 11 years ago

Slack is non-optimal for open source projects because each project will require you to have yet another Slack account. It also isn't IRC-like. With Gitter, you can be on multiple projects at once in one client UI.

So different use cases mean a different product might be better. Particularly if business concerns limit how one can use existing products.

niutech• 11 years ago

That's because Slack is slow. There are even more lightweight open source Slack alternatives described here: http://browsingthenet.blogspot.com/2015/05/slack-is-so-slow-...

restya• 11 years ago

As you have mentioned many chat system... We thought about adding chat module to our open source trello clone called Restyaboard http://restya.com/board/

Do you think if this will not be useful addition? Or what chat system among above will be useful to integrate?

timdorr• 11 years ago

Here's the code: https://github.com/mattermost/platform

From the look of the screenshots ( http://www.mattermost.org/70-2/ ), I'd say there are some copyright concerns with the styles. This isn't a Slack alternative, it's a Slack clone. That's very problematic from a copyright stance. Why not create your own design style?

Gogs had (has?) this same issue: https://github.com/gogits/gogs/issues/1069

chii2• 11 years ago

That's very problematic from a copyright stance

why? they didn't copy slack (i assume) - it just looks similar. Slack doesn't (and shouldn't be allowed) own a look and feel, as long as the implementation of it is cleanroom.

nieve• 11 years ago

https://en.wikipedia.org/wiki/Trade_dress#United_States

I have no idea if Slack could actually win a case, but in the US (where both companies appear to be headquartered) they do have some rights to look and feel as part of trademark law.

joesmo3• 11 years ago

I think you misunderstand copyright. You can't copyright a style, only a specific implementation thereof. Unless you're accusing Mattermost of copying code directly from Slack (which you wouldn't be able to tell from a picture), there is no copyright violation.

TheHydroImpulse• 11 years ago

https://en.wikipedia.org/wiki/Trade_dress#United_States

jsmthrowaway4• 11 years ago

Teams who can’t use SaaS rely on cryptic, decades-old technologies. As an example, the US Army uses myIRC to order missile strikes

"myIRC" doesn't exist. The name of the protocol is IRC. The name of a popular Windows client is mIRC. WikiLeaks called their leak "mIRC logs," which is where this trope came from.

The United States military (not just the Army) uses Internet Relay Chat for a whole lot of C2. It runs on a network, both IRC and IP, dedicated to the purpose. Given how long IRC has been in existence, that they've been doing it since the early 90s, that the use case is the perfect ideal for IRC, and that the average modern Web app is less reliable than my last Datsun, I have a hard time finding incredulity at sticking with something that works.

Even beyond that, IRC is text-based. It is not cryptic. An IRC client is a common first software project. About twenty lines of Go gets you a bot. You can make IRC look exactly like Mattermost with a week of hacking in your favorite framework of choice, and then you're not reinventing fanout. Entire products have been built atop IRC.

Even beyond that, guess how many protocols are decades old in just the software development workflow for this product. Pretty tired of "that's old, let's do it better," even though I hate finding myself on this side of defending IRC.

KaiserPro• 11 years ago

IRC federates easily, requires minimal resources, and is vastly more efficient when it comes to bandwidth usage. (you'll notice this over satellite links)

plus it works in screen natively

Dowwie• 11 years ago

How many open source slack alternatives before someone writes one that actually utilizes the IRC protocol?

Is there a defensible argument against using IRC?

vidarh• 11 years ago

The IRC protocol isn't pretty, and there are plenty of incompatible server implementations, but if you're controlling both the server end and the client end it's certainly where I'd start. My first thought when I saw Slack was "someone did a pretty web irc client finally, cool" (I have no idea if they use irc internally? but it seemed such a direct match)

TeMPOraL2• 11 years ago

This is my biggest problem with Slack. It's a cool product that could have been built over IRC. But no, they had to create their own walled garden.

lorenzhs2• 11 years ago

There already are a number of IRC client web frontends. The one I'm working on is Glowing Bear -- https://github.com/glowing-bear/glowing-bear . It uses a proper IRC client running on a server (WeeChat in a terminal multiplexer) and connects to that via WebSockets. Minimal reinvention of the wheel, and you can continue using all those nice scripts, triggers, and filters that WeeChat offers. The frontend (Glowing Bear) is completely static and runs 100% in your browser, connecting to your server directly.

I really don't get those projects that consist of a designer frontend and a terrible half-baked IRC client in nodejs.

joesmo3• 11 years ago

Yes, but Slack is slick, plaid, and even gorgeous.

Seriously, these days it seems most software like this is judged purely on its external styling and aesthetic beauty. You're right, Slack has no new features over IRC or any other decent chat clients in the past. But read any article that praises slack and if the slick UI (or whatever adjective is in style these days) isn't mentioned up front and center, I'd be surprised.

Of course the UI's 'slickness' and 'modernity' would be top discussion points for people writing such articles as they're usually not technical enough to argue the merits of tabs vs. spaces or braces vs. non-braces which the creators of such software usually argue about to the detriment of real issues.

dodgedcactii• 11 years ago

Can you recommend your favorite protocol OR app for a small dev company where we share files and want to keep a centralized area where team members can chat, using various apps (or web interfaces)? The more robust the better, doesnt have to look amazing!

synchrone• 11 years ago

Also, there is http://getkaiwa.com/, with roughly the same features, open protocol and a built-in LDAP. Hubot integration is also possible.

hitlin37• 11 years ago

can i run it on Linux?

aidos• 11 years ago

Having a look around the code it's a web based front end (using react) with an api written in Go behind the scenes. From that it sounds like you should be able to run it in Linux (but I haven't installed it myself, just had a peak at the src).

icebraining4• 11 years ago

It's available as a Docker container, so yes, it can run on Linux (with or without Docker).

soasme• 11 years ago

Better to have slack-compatible APIs.

tracker12• 11 years ago

One thing I really like and appreciate is that there's a dockerfile right in the root of the project, which makes spinning up a container a relatively nice experience... haven't run it or looked into the code though... that just struck out at me...

Looking at the dockerfile, it seems pretty big, and it also strikes me slightly that they have dependencies on node, ruby and go, along with mysql and redis. The UI appears to be react based.. not sure what's running in ruby.

ctolsen• 11 years ago

I definitely appreciate projects having Dockerfiles included, but yeah, that's not a good one. They should simply include instructions about how to link it to MySQL/Redis, or use something like docker-compose.

The way it's done now makes it inherently unscalable. Also, there are so many steps that it makes pushing an image to a Docker repository a massive pain.

pibefision• 11 years ago

+1 for a Docker Compose file

sehr• 11 years ago

Looks like it's only being used for their scss files.

tracker12• 11 years ago

Slightly weird that they didn't use node's module for that (which uses the compiled sass), since the front end is a react application, and seems to use node for building.

sciurus• 11 years ago

I think it's nice that they support Docker, but I was disappointed that their entire installation instructions were "install docker then run our image". I had to read the dockerfile and the "start" script to find out what the actual dependencies and setup steps are.

https://github.com/mattermost/platform/blob/master/Dockerfil...

https://github.com/mattermost/platform/blob/master/docker/do...

Surely even docker users don't want to run this app, mysql, postfix, redis, react, and compass all in the same container?

ptman• 11 years ago

I agree that a dockerfile isn't perfect, but it's not that bad either as a machine readable install guide that doesn't fall out of date as easily as documentation written for human consumption.

tyrion• 11 years ago

I tried to spin up the docker container locally and it worked until it had to send me a mail for registration.

Looking at the README it says that it does not work if my ISP is blocking port 25, which I don't think it is.

But anyway I created a droplet on digitalocean and ran the container there, but "MySQL init process failed."

I would love to try this project, or at least try a demo deployment somewhere :)

aargh_aargh• 11 years ago

Me too, mail didn't arrive. Not possible to continue.

javiercr3• 11 years ago

We’re a YC-backed indie video game company releasing an open source alternative to Slack.

Don't want to troll you guys here, but if you're a video game company why are you spending so much time building a Slack clone?

I was expecting some short of explanation in your blog post like "we did this because this serves as a core piece of our company for X reason and Slack didn't fit our use case for Y reason".

a13xb• 11 years ago

They probably pivoted. ;)

sbank• 11 years ago

Very interested? Somewhat interested? Not interested? Which one? Which one? Which one?

tacone• 11 years ago

They probably had to build similar stuff for some of their games perhaps.

it336• 11 years ago

Mattermost team here,

You guessed it, Mattermost is the 3rd version of what started as a portal/community site for our players (first version was forum-like, the second was Facebook-like, Mattermost is now HipChat/Slack-like).

dasil0033• 11 years ago

I can't tell if you're aware of the coincidence, but did you know that Slack was a pivot from game development just like Stewart Butterfield's previous unicorn Flickr?

quesera2• 11 years ago

"Unicorn" is probably the silliest term of the year. But it degrades to meaninglessness if you include Flickr, which sold to Yahoo! in 2005, for $20MM.

agumonkey2• 11 years ago

Text editors become mail clients. Game editors need chat clients. I see a pattern. Things want to talk to other things.

agumonkey2• 11 years ago

Their game was called 'Game neverending', never launched, how apropos.

pornel• 11 years ago

It may be a perfect match, given that Slack has been created by a game dev team too:

https://en.wikipedia.org/wiki/Slack_Technologies#Initial_fun...

lucisferre• 11 years ago

I'm not sure why that would be all that relevant though.

evilduck• 11 years ago

With even the same argument of them building a HipChat or Flowdock clone.

atombender• 11 years ago

It's rather funny how Stewart Butterfield keeps trying to build games, and ending up with social apps.

His first company, Ludicorp, tried to build an MMORPG called Game Neverending, which never launched, and they pivoted to create Flickr, apparently based on the same platform (which is why ".gne" URLs proliferated Flickr originally).

With Tiny Speck, he created Glitch, another MMORPG, which closed a little more than a year after launch. Tiny Speck then pivoted to launch Slack, based on a chat app they had built internally while developing their game.

nadams• 11 years ago

Don't want to troll you guys here, but if you're a video game company why are you spending so much time building a Slack clone?

I think a better perspective is that this is a tool they needed/wanted and built it - it's really no different than a map editor. Also some companies like Google have a X% time to work on a "personal" project during work hours - and this could be the result of that.

jqueryin• 11 years ago

Sounds like a lot of burndown on your non-core competency IMO, but thanks for releasing.

AnonJ2• 11 years ago

What's wrong with that? Many great products started at companies which are not "supposed" to do that as their core business. Pivotal Tracker is one thing that immediately sprang to my mind. Why do you want to strictly limit what a company is working on, and potentially kill great ideas anyways. I believe as long as they're still functioning, their game development business is probably totally fine. The same applies to a person: I don't believe if you work on something as a full-time job you're then not allowed to have your hobbies, side projects(some of which are quite huge in scale) and personal interests. That would be horrible.

UserRights• 11 years ago

no ldap?

richmarr9• 11 years ago

  Unlike Slack, Mattermost is open source...

  Teams suffer when SaaS companies lose focus. Since it’s open source,
  Mattermost can endure through its community. If quality declines, 
  anyone can fork the code and take stewardship.

Open source and focus are the wrong arguments here.

(a) Mattermost is built by a video game company, so there is no focus to start with.

(b) Moving from a SaaS product to a self-hosted open source component runs against the process of commoditisation so is ultimately only ever going to be of niche value. After all, why spend scarce and expensive engineering time setting up, maintaining, and potentially having to fork a product, when you could just pay $however-much/month and not have to worry about it.

ville• 11 years ago

Funny you say that, given that the company that built Slack (originally named Tiny Speck) was also a video game company initially. :)

richmarr9• 11 years ago

Funny in what way? Not sure I see the point you're alluding to.

amandine3• 11 years ago

The problem of SaaS is having your company data stored by someone you have to trust... So I reckon it depends on your use case: if I'm a small company who doesn't want to bother running/maintaining the service then I'm more than happy to hand it over to someone else and trust them. If I don't want to trust anyone with my data I'd rather have something simple to deploy and run myself.

The same way that having a closed client prevents you from customising it to fit your needs but can be helpful if you had no intention to do so in the first place.

richmarr9• 11 years ago

Yeah, there'll always be companies like that but as more and more large orgs, government departments, etc. migrate all their email over to Gmail, I'm starting to consider that as a niche. Those orgs are also disproportionately likely to want to build their own thing because they have a hope of making the economics of scale add up.

richmarr9• 11 years ago

Anonymous downvoters: please build up some courage and actually contribute. I don't bite.

it336• 11 years ago

Mattermost team here. Thank you!! This feedback is awesome. Working on some replies...

flyosity• 11 years ago

Why don't you work on an interface that isn't a nearly exact copy of Slack's before you work on some replies. Copying their functionality is one thing but copying their look and feel is not only pathetic, but against U.S. intellectual property laws. You guys made the equivalent of a Chinese knock-off product. And why not focus on your startup instead of working on cloning other team's hard work?

ywecur2• 11 years ago

There are many slack alternatives out already, as volent has pointed out. What I'd like to see is one that is based on Tox technology.

Having a decentralised network would be much better as it would remove all costs of self-hosting.

mempko• 11 years ago

It is more oriented towards real time and spontaneous conversations, but my Firestr project is a p2p chat/app platform. I am working on the idea of more persistent conversations. Check it out, it is still alpha but works well. I am always open for help to make it more awesome too.

http://firestr.com https://github.com/mempko/firestr

ywecur2• 11 years ago

Hos does your network work? Is it compleatly distributed, like Tox or does it rely on nodes?

vijayrawatsan• 11 years ago

Are you planning to open source you android client as well?

uniclaude• 11 years ago

That's all good, but the differentiating factor of Slack over Hipchat & the like is how well it integrates with everything your team is likely to use. It works seamlessly with Github, Trello and IRC.

I don't mean to devalue this product at all, but This is not a viable Slack alternative, it's a generic (and good looking) communication tool. This said, I commend the open source approach, it could probably help the product evolve towards something much better and integrated.

pluc2• 11 years ago

You know what else is a great open-source on-premises Slack alternative? Most IRCds.

coldtea• 11 years ago

You know what is nothing like Slack in functionality and you'd knew if you have used Slack? Most IRCds.

pluc2• 11 years ago

I use Slack everyday, and I disagree.

LinuxBender• 11 years ago

I've run numerous IRCd's for decades. They are completely stable and scale to 10's of thousands of users per VM. I can't even remember the last time I had one crash. There are already tons of integrations for IRC. It is just difficult to get people to understand the simplistic beauty of IRC. People like "shiny", as mobile phone addictions have proven. There are not many great web front ends for IRC that are secure at the same time as being shiny.

ocdtrekkie• 11 years ago

Awesome to see more companies questioning Slack, and developing their own solutions!

andmarios• 11 years ago

Once a month an “insert something tech-related here” company releases an open source slack clone.

While I am grateful to all you guys, how much free time do you have to work on these clones instead of your main product?

I've tried so far let's chat and rocketchat and I liked them. I will give a spin to mattermost and I am sure I will like it too. I think the one that matures first, will be a big hit because we need a slack clone —as evidently shown. But also as with any other open source / free software project it will need commitment.

hhaidar3• 11 years ago

Let's Chat is actually three years old :P

solve• 11 years ago

Before you disparagingly call it a "clone" and "not their main project", consider that free products often go on to crush their expensive first-to-market predecessors.

The strategy of first seeking to monopolize the user-base, and then afterward heavily monetizing it is a very well proven long term strategy by now. The overnight success of Slack and some other SAAS companies may give some people the impression that this strategy is suddenly irrelevant. It may not be.

caustic• 11 years ago

shmerl2• 11 years ago

So, can it be used as an improvement over XMPP? A new IETF standard may be?

ryanSrich2• 11 years ago

What a horribly uncreative rip off. That may sound harsh but I'm a bit floored that this is getting so much attention...but YC right?

Reproducing functionality and growing an idea is fine. It's the blatant disregard to UX and UI where this company has literally pixel for pixel ripped off slack.

tadfisher3• 11 years ago

It's the blatant disregard to UX and UI where this company has literally pixel for pixel ripped off slack.

I'm finding it hard to parse this sentence. Are you saying ripping off Slack is the blatant disregard, or are you saying Slack pioneered a blatant disregard for UX and UI?

ryanSrich2• 11 years ago

Sorry about that.

What I meant was that Mattermost is blatantly disregarding their UI/UX by just ripping off Slack. If design was that easy we'd all have the same looking/feeling/functioning product.

pbreit3• 11 years ago

Mattermost looks to me like it departs from Slack UI more than some of the other clones I've seen (Rocket Chat, for example).

it336• 11 years ago

Mattermost team here,

There's been a number of questions of what's coming from Mattermost, and how we design things. I wanted to share some raw, unpolished work we have of what's coming up.

It's a feature called "App Center" that we're working on to support 3rd party applications.

It's just a Google Doc of our early design that we're sharing on Hacker News to get feedback: https://docs.google.com/document/d/1s6vrticxgz9PsxePQ-dFrsKp...

Would you find this interface interesting for building 3rd party apps?

What do you like about the design?

What do you wish we changed?

There's a couple 1st party Apps we'd start with, like an Admin Console and a Custom Web App. We're thinking there could be a marketplace for 3rd party workflow apps.

Example: create an "Expense Report" app where a user can upload the photo of a receipt from lunch from their phone and type "#expense #meals" and have a 3rd party app create a labeled expense report that would be viewable in App Center.

Would love to hear thoughts from the community. This is an early idea, it's just a Google Doc right now. Your input would help shape it.

bitsweet• 11 years ago

this is how you earn revenue as an OSS platform company (once you get it in the hands of everyone aka build a network)

eltondegeneres• 11 years ago

Does it have email notifications? That's a killer feature missing from most Slack replacements.

brazzledazzle• 11 years ago

Some of the comments here are... aggressive.

pbreit3• 11 years ago

Help: anyone able to get it going on Mac with Kitematic?

Does it set up mail server that can get email to my Gmail account? I signed up but didn't get an email. Are emails dumped somewhere or possible to lookup whatever I need to get started?

AnonJ2• 11 years ago

Such self-hosted services might help us a lot, as Slack is currently blocked in China already. I think the two main reasons are that the Chinese government is unable to inspect the data at will, and also they fear sensitive data being leaked to the US government easily, which is actually quite legit. No interest in politics nonsense and having full control over your own sensitive data is probably the best possible thing to do.

ChicagoDave• 11 years ago

Why is there no package? I have to use docker? Why? Why? Why?

Mattermost: Open-source, on-premises, Slack alternative

Related Stories