We have several teams at work and each channel in the team has a specific purpose. It would be ideal if we could set a time at which a recurring message of the day would be posted. We would include links to resources for the team as well as recent news for people who have been out of the office and are returning.

It would be like an extension to the header and purpose sections. Ideally tagging people would work such that some of the messages can act as daily reminders to everyone of the schedule.

Notifications are challenging, and a common source of friction seems to be "hey, you triggered a notification I didn't want by saying @all".

Slack handles this nicely: they intercept the message before send, and advise the user of the outcome.

> By using @all, you are about to notify 123 people in 12 timezones. Are you sure? [edit message] [send now]

Bots are only able to post text messages to rooms, however, it would be convenient if bots were able to attach photos as a message to the room.

We would prefer if our bot didn't have to upload images to an accessible URL and then post that url to the room (and then only get a preview of an image), as this adds a few extra steps to viewing the image and requires our bot to be aware of when it is done uploading the image to the host and then finally post the link to the room.

Right now you can only navigate through images posted at the same time, whereas slack will let you navigate through the entire history of images

Mattermost fetches images from a URL to that image, however it ignores the exif data. This results in the preview often being in the wrong orientation.

It would be nice to have an option, that enables the user to hide contacts that are currently offline.
This would mainly apply to the "direct messages".
It is really annoying to search through a long list (~50) of contacts you often need to chat with, when about 50% are currently offline and are therefore of no interest at the moment.

Currently, we have users that work in close proximity to one another, and sometimes take on each other's identities, it would be nice if we had a way for a user to delete their direct message history. Reopening a direct message with a user should start fresh. If the logs remained unchanged that would be great too.

Would it be possible to add custom selection of username, nickname and full name to teammate name display? This would make it possible to use combinations like John Doe (Johnny-boy) or John Doe (johnd).

Some Mattermost instances have many channels and a crazy number of posts, leading to searches on terms returning too many results. It would be good to be able to search by date range. For example, gmail uses after:yyyy-mm-dd before:yyyy-mm-dd and probably other date formats to enable searching by date.

I got asked by a colleague if it is possible to sort the Users because he had about 60+ Users in the Direct Messages section.

It would be nice if you can sort it by a specified department (or Position) or that you can create User groups (with specific permissions for example) and that they get sorted in categories like this.

An other way could be that everyone can create custom folders with users in it and can expand it if needed.

On Slack, Bots can interact with users by adding UX elements within the message as you can see there : https://api.slack.com/docs/message-buttons

This would be an awesome feature to have in Mattermost.

Currently the web interface has no option to increase the font size. This is plainly silly. Please fix this ASAP.

This pull request introduced a security measure to protect against clicjacking attacks: https://github.com/mattermost/platform/pull/253

But it also prevents some legitimate uses of iframes. For example, Nextcloud has a "external sites" function to run any app as if it was a Nextcloud app, by putting it in an iframe inside Nextcloud (https://docs.nextcloud.com/server/9/admin_manual/configuration_server/external_sites.html).

My proposal is to add some settings to allow an authorized domain, and then change X-Frame-Options, instead of DENY put ALLOW-FROM this domain. And to check the domain also in the javascript check in head.html.

This way it would allow legitimate uses, while still protecting against clickjacking attacks.

While Mattermost's image expansion works as expected when the URL ends in .gif, .jpg, etc, image-based links that Slack would expand automatically are not expanded by Mattermost.

For example, post links like the following to a Mattermost channel or DM:
http://media.riffsy.com/images/41a79faf658c913d77bfe36b8a231244/raw
http://gph.is/2lQfDuj
http://imgur.com/gallery/83mmP

etc, and note that they do not expand, requiring a user to click on them to view in a new browser tab. It would be nice to have the images auto-expand in-line.

Show a member list on the side of the chat window listing all the users that are in the current room, sorted by status and then name (so that logged out users are at the bottom).

This seems critical to communication .. who's in the room, who's online, who am I talking to, am I in the right room before typing @everyone, etc. At a glance. The little member button with drop down is insufficient especially in rooms with hundreds of people.

Screenshot from Slack: http://take.ms/YhtK8

This is one of my concerns when upgrading to a newer version

Hi,

it would be nice if incoming webhooks could support some kind of actions or buttons.

Ie: you use mattermost to recive alerts from a monitoriring system and you want to take action on this. Create a ticket, close the alert etc (linking to external systems/source)

There are similar functionality in Microsoft Teams and Slack.

https://dev.outlook.com/connectors/reference
https://api.slack.com/docs/message-attachments

I would like Mattermost to be able to consume any Slack-compatible webhook. It is very frustrating that I have to build a tool to proxy webhooks from GitHub for example.

For accepting new users on a Mattermost system, there is no middle ground between "open system" and "invite only".

We were opening our Mattermost Team edition to interested people, and are now weeding out fake accounts manually. This could be prevented if we had an "approve new user" button for system admins.

Bonus: a configurable login page with custom text would give potential visitors a better idea about wether they should want to join this server. "You are about to sign up for the full-contact deep-sea chess entousiasts chat. Are you sure?"