Currently it is not possible to have notifications triggered based on keywords, for example if there are any emergency keywords, a certain ringtone or vibration (or both) will be triggered.

This would be important in the event of any emergency that requires immediate action.

Add an server wide option to forbid renaming user names. It might be a security problem, if someone claims abandoned user name (/account name).

This would require major architectural changes for the Mattermost server, but adding some use cases to gather feedback from the community.

Server admins wouldn't be able to read the content of conversations because they don't hold the keys to decrypt, which means users wouldn't have to worry about
- Server admins spying on their private conversations
- Governments subpoening server admins into handing over conversations
- Hackers taking control of the server being able to read the conversations

The use case is to provide information to users, for example, release notes, status updates, etc. In order to keep the channel relevant and to avoid clutter, non-admin users have read-only access.

This feature allows a team to create "reference" channels.

1. team admins: create, read, update, delete
2. non-admin users: read-only

This idea is similar to, and currently under review for Enterprise Edition:

https://mattermost.uservoice.com/forums/306457-general/suggestions/12874797-add-write-policy-for-channels-and-private-groups#comments

This idea is related to:

https://mattermost.uservoice.com/forums/306457-general/suggestions/11205615-different-user-roles-to-configure

This has already been requested here:

https://mattermost.uservoice.com/forums/306457-general/suggestions/18607111-confirm-with-ping-warning-before-sending-all-eve

But for some reason, the confirmation has been implemented only for (at)all and (at)channel, which still allows people to use (at)here mindlessly (without realizing they're about to ping sixty or more people, for example).

So, I kindly request (at)here to be added to this list.

Support Gitea's OAuth2 provider as an authentication source.

Currently, the team edition only supports GitLab as an OAuth2 source. GitLab is pretty heavyweight and many people prefer other software for a variety of reasons.

Gitea (https://gitea.io/en-us/) is a really nice open source, community supported Git server. They recently added support for acting as an OAuth2 provider (see https://docs.gitea.io/en-us/oauth2-provider/ for documentation). It would be great if Mattermost would support Gitea as an OAuth2 provider.

Image Preview: Add a site blacklist to prevent image previews from selected sites.

Example: Someone can set up private repositories on github that aren't visible to users that aren't logged in and aren't members of the organization. Link preview currently creates a preview of the root github page. This is pretty annoying when you're sharing links to pull requests with coworkers.

Have a button in the code block to copy it on clipboard

A lot of AD forests have Profile Photos in them. Mattermost provides no administrative capability to set profile photos. Therefore, just yank them out of AD? Would prevent complex UI from being necessary and give us AD admins a more fancy way :)

In the iOS application, you need to be able to choose the degree of video compression at startup. This is necessary so that you can compress videos and upload them. Now, when you try to upload a video clip, the video is primarily compressed, but since the compression algorithms are not good enough, the video still weighs too much and cannot be uploaded. Please fix it.

Slack recently increased their character limitation on channel names. We would like Mattermost to increase the limit as well, as this has been a helpful feature since it was rolled out.

Allow emojis to be used in a channel name.

The same way we can send messages, we should be able to send voice messages.

It should be as simple as click "add voice", record what you want, press send and it's made available on the server for others to listen.

It should be supported by browser and mobile client apps.

for the default search backend (sql), search results are capped at 100!

you can verify this by loading jquery and doing:

$('.search-item__container').length;

you can see that paging isn't supported:

https://github.com/mattermost/mattermost-server/blob/master/app/post.go#L821

and the sql uses `LIMIT 100`:

https://github.com/mattermost/mattermost-server/blob/master/store/sqlstore/post_store.go#L834

i know this isn't an issue in enterprise because you're using elasticsearch, but please either bring elasticsearch to team edition or fix the default search backend. 100 results is sad :(

The Mattermost desktop client should automatically check for updates and prompt the user to update. This feature is mandatory in today's security landscape, even for an Electron app.

Most of our users don't realize their desktop is many version out of date, with pending security fixes.

Bonus points for shipping builds via the Windows Store, macOS App Store, snapcraft, etc.

For threading purposes it'd be great if consecutive messages from the same person (maybe within some time window like 10 minutes) would be counted as a single message.

We use mattermost for an internal support chat and very often we get stuff like

"Hi!"
"I have this issue with the fronk, for customer Acme"
<screenshot>
"Could someone take a look?"

You can't reply to any of those messages without losing crucial information in the thread.