Zulip me permite gerenciar várias conversas em múltiplos contextos e organizações com incrível clareza e eficiência graças à forma como gerencia os tópicos. Tem controle completo pelo teclado e marcar tópicos como concluídos é um prazer e ajuda a manter o foco. Enquetes e tradução de fusos horários internacionais são um ótimo bônus, assim como a formatação automática e (se você gostar) o editor expansível super confortável (não apenas uma janelinha arrumada). :) Eu também adoro absolutamente que podemos hospedar o servidor nós mesmos, quão estável ele é e quão fácil é atualizá-lo. Além disso, organizações extremamente zelosas vão adorar que você pode exportar todas as suas informações para mantê-las seguras em outro lugar. É um ótimo exemplo do que o Software Livre/Libre de Código Aberto pode criar. Mencionei que também tem ótima acessibilidade? O que mais podemos pedir? :)

Sem frescuras, sem lixo de IA, apenas comunicação rápida e confiável com nossas equipes ao redor do mundo.

First of all, Zulip has basically all the default features you expect from a messenger: * There is a desktop app to install, but it also works in the browser. * There are mobile apps too (some extra words on these later). * You need to create an account to get it. It can be free to join, or invite only. Login is possible with username & password or single sign on providers like Google, Github etc. * There are private areas with restricted access as well as public areas. And of course there is private messaging between a single user and multiple users. Of course there are also Webhook integrations for receiving messages from the outside world (e.g. Github notifications) and bots you can integrate. * You can bookmark messages for later. * Begun messages are sent as drafts (as many as you want) * You can directly ping people and jump to your reactions/mentions. That is our everyday use. There are fancy features like commands with bots, statistics, integrations, but I really need them much so I don't know the latest state. So far I didn't notice anything "missing" compared to other tools. Now here comes what is different and special about it: Zulip has a unique approach on how discussions are organized. Well actually it's not that unique, as it works more similar to the structure of bulletin boards. But it is unique compared to other chat tools. Every message is sent to a dedicated channel. Just like in IRC, Slack, or Discord. Then each message ends up in a certain topic that only exists inside the channel. You can pick existing topics (or it is auto-selected if you respond to an existing message), you can create a new topic or if you don't care at all you just use the default (no topic). While other solutions like Teams, Slack or Mattermost offer "Threads" based on a single message, these threads tend to vanish as the original message and they are not "core" to the user interface. So why is this such an improvement? First of all: You cannot manage thousands of channels. Because people first of all need to find it and then join and eventually leave it all the time. But channels are a much broader topic. Let me give you an example on what we use channels for: a channel for the production servers, a channel for the test server, one for moderation purposes and one for each software component we provide. So people who are interested or responsible for a certain thing subscribe to this channel. Now inside the channels there are new questions or topics opened: A certain downtime, a certain bug or feature, consistently sent push notifications from an uptime monitor or Github. Obviously not everybody is interested in every topic. I would like to know what is going on with our desktop client, but I am not interested in every Github issue or pull request opened - but the maintainer is. So I just mute just the topics I am not interested in. But all new topics I get a chance to look at and decide whether to approach them Topics can also be marked as resolved. A feature most commonly used in "support"-alike discussions. And I can search for topics by name. Helping me find older cases or some special topics where we stored some knowledge. Our production server channel has a "how-to" topic where there are many commands stored that we occasionally need. Doesn't that belong into a better knowledge management tool? Well maybe, but only if you have one… In the ui you can watch the combined feed of all channels, or all the messages of a topic. There used to be a way to see the combined feed of a channel, but it seems to have been removed. I assume because it used to be a problem to answer to the wrong topic based on which message was currently selected. Speaking of which: Posting in wrong channels is a thing - especially for new joiners. But it is possible to move messages to other topics and/or channels (just a single one, or all starting from that one). There is a permission model around this, but to me it seems crucial that everybody can do this and actively tries to keep these things because…