8/23/2023 0 Comments Rocket.chat vs slackI know this is a topic with strong opinions but at the end of the day it’s just a chat app and the project has other priorities other than spending time fighting with difficult solutions. Large companies self-host it without problems and it seems fairly polished. But considering the 1k-users limit in Rocket.chat, Mattermost seems like a better option. If we can’t get a sponsorship, I think the natural choices would be Rocket.chat or Mattermost. If we’re happy with Slack and its features, the pragmatic approach would be to contact Slack and ask for a sponsorship. So much that are end users and business people returned to using email for most communication. I would advise against choosing either options because 1) IRC is dated and doesn’t support most modern features end users want and 2) Matrix and its apps are fairly technical and unpolished at the moment. I work on a project with a fairly diverse user base (sysadmins, programmers, designers, end users and business people) and we recently transitioned from IRC to Matrix. Over 95% of the message history for the Slack is gone, and IRC even on a modern package like inspircd only stores 50 lines of scrollback per channel.īasically, we need to be able to rely on message history, pins, and DMs being there, we need the ability to restrict posting of e.g., announcements to certain users and roles, we need to integrate with git and other services nicely, and it would be nice if it could integrate with other chat networks. IRC fails the same basic test that Slack is failing at this point, we are losing message history. I have (and currently do) run IRCd networks and unless it’s a niche use case as I have, it’s worth sticking with major networks. It’s where all the people are, and there’s plenty of oper staff to help if needed. If others really endorse it and think it’s the way to do it I’ll dig deeper on its we already make use of Freenode’s IRC and we would almost certainly stay there. I simply don’t have enough experience with Matrix to be comfortable endorsing it, I know roughly what it is but that’s about the extent of it. I was never able to find a satisfactory iOS client. I don’t mean that as a judgement - I just mean that it’s not very accessible and it’s encryption paradigm very easily leads to lost messages/attachments. It’s history and original use case definitely shines through. Before I tried Mattermost I tried Matrix. It also provides features we’ll probably ultimately want if ChatOps becomes important or we decide that conversations need to be kept and searchable, such as message logging and the potential for integrations with business apps like issue trackers. I run a small Mattermost server for a group of my friends/home life and it’s one of the least maintenance intense applications I’ve ever run, very easy to setup and care for, and it is completely self contained. Mattermost is also far more user friendly, especially to non-technical users. For example if we wanted to setup our own IRCd, we’d also need to setup a services server such as Anope. IRC is infinitely flexible with very little work, it’s rock solid, has been around forever, and these days can support basic best practices like TLS.īut for me Mattermost takes the cake because it doesn’t require the same level of setup and maintenance as IRC. I am a huge fan of Mattermost or IRC, but I favor Mattermost.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |