This blog post is a part of Mattermost’s public disclosure of three serious vulnerabilities in Go’s encoding/xml related to tokenization round-trips. The public disclosure comes as a result of several months of work, including collaborating with the Go security team since August 2020 and with affected downstream project maintainers since earlier this month.

Optimizing SQL queries is always fun—except when it isn’t. If you’re a MySQL veteran and have read the title, you already know where this is heading 😉. In that case, allow me to regale the uninitiated reader. This is the story of an (apparently) smart optimization to a SQL query that backfired spectacularly—and how we finally fixed it. It started off with a customer noticing that a SQL query was running slowly in their environment.

We’ve heard your feedback and are happy to announce that Mattermost will be introducing Collapsed Reply Threads in beta early next year! This feature is a top priority for our team and is the most voted feature request on our idea forum. Threads are core to the messaging experience in Mattermost. They allow users to organize conversations about various topics within a channel.

The internet is changing all aspects of business communication, and with more of us than ever working remotely, it’s a change that is accelerating. Messaging—the ability to synchronously communicate with teams, coordinating work and workflows—is at the center of this new mode of day-to-day business life. The importance of messaging tools—like Slack, Microsoft Teams, and Mattermost—is well-known to those who have already made this shift.