[deleted]
Mattermost: Open-source, on-premises, Slack alternative
191–200 of 222 posts
Re: Mattermost: Open-source, on-premises, Slack alternative
#192Earlier quoted context omitted.
Whatever happened to Basecamp itself? I used to hear about it all the time...
Last I heard they had 6 million active users (vs 1 million in 2012).
... by what definition of active, and what definition of users? Surely you would define such a SaaS by revenue or number of customers rather than users, which allows you to fluff up your number by claiming every individual at every client organization is a user ... even if those accounts are automatically generated by some onboarding process then ignored.
Re: Mattermost: Open-source, on-premises, Slack alternative
#193I 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=94…
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?
Re: Mattermost: Open-source, on-premises, Slack alternative
#194Earlier quoted context omitted.
Wow, I got reamed out pretty hard for absent-minded use of a trendy term without thinking about it too much. In my mind Flickr is up there with the Instagrams and the Ubers of the world because it was a fucking amazing experience at the time. I never even considered the valuation, but Flickr was definitely unique in the UX it brought to the table. I think people forget what the landscape looked like then. Or maybe th…
Sorry, my comment wasn't meant to be snarky, but I can see how that's not clear. I was just musing on the fact that (yes, I don't like the term, but also) "unicorn" was originally a label for startups with huge valuations, generally > $1B. It has mutated since then, but the idea that it would apply to Flickr seemed funny.
I wasn't bothered by your comment actually, it was more that I was at -4 for what I believed to be at least a mildly interesting observation at its core.
Re: Mattermost: Open-source, on-premises, Slack alternative
#195Earlier quoted context omitted.
There are standards for E-Mail though. So you can move your mail around different providers. With your chat system it's a lot harder. You can't move your yammer content into slack easily.
Is XMPP a standard? I know that everyone just ignores it.
Yep, and Slack supports it, along with IRC.
Re: Mattermost: Open-source, on-premises, Slack alternative
#196Earlier quoted context omitted.
Lots of people -- in that list, even -- started with XMPP based systems. They all move away. At first, I also thought this was an open and shut case of interest in lock-in. Now, I'm not going to say that isn't true, but it's also worth considering that XMPP... just isn't that good. Having recently started working on a chat client that was intended to speak first-and-foremost XMPP, I have to admit: XMPP is... it's dec…
One thing I'm curious about regarding matrix.org: As a federated protocol, is there anything at all in the spec that would discourage someone from piggy-backing on the federation to acquire initial users, goodwill and a head-start on features, and then locking users in once they've gained enough momentum by making proprietary modifications? You know, the same tactic countless companies have pulled with XMPP? I've bee…
The example 'Matrix Console' iOS & Android apps are aesthetically very ugly, but still very functional and usable from a geek perspective. Meanwhile we're currently replacing the example Matrix Angular webapp with a Matrix React webapp which will improve the performance enormously.
In terms of polished UI/UX, we were hoping the community would fork the example apps and put the necessary polish and usability on them. Features should (almost) all be there, and we're doing our best on platform ubiquity.
However, as ex3ndr's comment below shows, there are people still creating their own per-app proprietary protocols rather than building on something like Matrix.
So in order to help bootstrap Matrix, am sure we'll end up building a killer client app sooner or later if nobody else does :)
Re: Mattermost: Open-source, on-premises, Slack alternative
#197Earlier quoted context omitted.
Lots of people -- in that list, even -- started with XMPP based systems. They all move away. At first, I also thought this was an open and shut case of interest in lock-in. Now, I'm not going to say that isn't true, but it's also worth considering that XMPP... just isn't that good. Having recently started working on a chat client that was intended to speak first-and-foremost XMPP, I have to admit: XMPP is... it's dec…
One thing I'm curious about regarding matrix.org: As a federated protocol, is there anything at all in the spec that would discourage someone from piggy-backing on the federation to acquire initial users, goodwill and a head-start on features, and then locking users in once they've gained enough momentum by making proprietary modifications? You know, the same tactic countless companies have pulled with XMPP? I've bee…
Oh, in terms of the risk of federation causing lock-in: it's inevitable that folks will add domain-specific extensions to try to force people to use their platform. This is no different to me sending you an attachment over email in some proprietary vendor-specific format (e.g. .ppt) which obliges you to install PowerPoint to read it.
This can be used for both good and evil. The evil scenario is above - rather than using an open standard like ODF, it provides a route to promote vendor lock-in. The good scenario is that it provides extensibility for technology that simply isn't standardised yet, and gives vendors a way to differentiate their product. For instance, if Oculus jumped on Matrix and started using it to negotiate VR collaboration spaces, it almost certainly wouldn't work with any other vendor at first... but it's good news for end-users who get a cool feature which some day may be standardised across all of Matrix.
The bottom line is that as long as everyone implements the common base line use cases in an interoperable fashion (i.e. IM and VoIP), then vendors having freedom to put proprietary/experimental stuff on top is just a necessary evil... as long as they don't break the baseline. It's up to us as consumers to then encourage vendors to make their extensions standards rather than exploit them for vendor-lockin. It really is an identical situation to email and MIME.
Re: Mattermost: Open-source, on-premises, Slack alternative
#198Earlier quoted context omitted.
Lots of people -- in that list, even -- started with XMPP based systems. They all move away. At first, I also thought this was an open and shut case of interest in lock-in. Now, I'm not going to say that isn't true, but it's also worth considering that XMPP... just isn't that good. Having recently started working on a chat client that was intended to speak first-and-foremost XMPP, I have to admit: XMPP is... it's dec…
Can't agree more. That's why we started our project with fresh and new protocol for messaging with implementing all required stuff in it's core, not extensions.
I'm not sure that creating a new vendor-specific protocol without federation or cross-vendor interoperability really helps anyone but you ;)
Re: Mattermost: Open-source, on-premises, Slack alternative
#199Earlier quoted context omitted.
No it won't... It will at most trigger the AGPL for the integration off that system... which is it's proprietary no one will ever want... hence no one will ever sue you to release it. Are Tinfoil hats on sale or something?
No, just folks with a little more legal experience than "potentially and willfully violate the terms and spirit of a license because we assume nobody will ever sue us," which also doesn't scale beyond a team of two. Not enough people take license compliance seriously. (Your comment an example.) Just to communicate the impact here, getting compliance wrong can result in significant legal liability. You and I are both…
... Okay if it isn't tinfoil hatery... show me the case law which proves me wrong?
Saying "I know a cautious lawyer" is just tautological BS.
Re: Mattermost: Open-source, on-premises, Slack alternative
#200I 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 :)
Me too, mail didn't arrive. Not possible to continue.