General
Please search for existing ideas before posting a new idea.
- or
No existing idea results
- ~ No ideas found ~
1200 results found
-
Transifex Web Hooks
Transifex Web Hooks
4 votes -
Enable setup as a Tor hidden service (like XMPP servers)
Many people use XMPP servers for instant messaging due to it's decentralisation. And many of these providers also have hidden service servers (.onion addresses)
If Mattermost wants to be competitive with other popular instant messaging programs like XMPP (Jabber) then it needs to allow easy setup of hidden service servers, ideally with a wizard setup installer.
3 votes -
give one click option to fully delete a message
give option to delete all trace of the message deleted, or replace with "this message was deleted" text. Right now, if you want to delete your last message, you have to his up arrow, cmd-a, delete, enter, enter (to delete), then click on the X
5 votes -
include a Trace option in the logging modes.
We were having an issue that was causing Mattermost to continually crash for no apparently reason. Nothing was consistent in the log files, debug didn't give enough information, heck I even did an strace on the PID and wasn't able to get anything useful. A Trace option should include DB calls, perhaps a transaction ID to link the API call to the DB call...
1 vote -
improve profile images by offering arbitrary size with cropping/centering
from https://github.com/mattermost/platform/issues/1981, Currently you have to click a button in order to select and image, and it has to be a rectangular image already. Instead, it makes sense to do things more like twitter or flickr, where you can either click-to-browse or just drag-and-drop an image onto the UI, and then the UI gives you the option to crop and scale, so you can pick any image and then just select the rectangular subsection you want to have act as your profile picture.
13 votes -
make administrators get a notification when new channels were created
When users create new channels, there currently seems to be no notification emails send to administrators neither when a new channel is added nor who this channel added. This prevents administrators from being informed proactively about misbehaviours of users (i.e. if users create non corporate/private information exchanges on the system). A moderator feature would be very appreciated to help the IT securing itself and not having to explain the CEO why there is a public channel for exchanging illegal content, for example.
9 votes -
Secure direct messages using TextSecure/Axolotl algorithms
Secure direct messages (and may be messages in private groups) using TextSecure/Axolotl algorithms. Unlike OTR protocol this will enable sending secure offline messages. I think TextSecure library could be used https://github.com/janimo/textsecure
17 votes -
make private chats able to authorize users based on ldap groups
In corporate Environments often closed discussions take place between persons whose users already exist within predefined ldap groups. For Mattermost it would make sense to authorize users for private channels using such existing ldap groups.
2 votes -
Ability to export all of a specific user's content when required for compliance
From: https://github.com/mattermost/platform/issues/2291
In corporate environments it is sometimes necessary on legal grounds to check an employees communication. Usually the management asks the IT therefor to deliver ones communication. Currently an administrator is neither able to view the existing private chats from any user nor is there an export function to extract all users content from the database
5 votes -
email notifications for new messages and for channel joins look alike and have a similar email notification subject
This behaviour leads to that one could not see at first sight which type of message the notification was for, because the email subject is always "New Mention on...".
It would be more informating and appropriate to choose a email subject that makes clear at first sight which kind of mention the notification is about. (channel join, user disabling, mention, etc)
In my opinion a channel join is no mention in sense of a new message. There is a difference between a new message and other System activities and this should be clear withing the notification email.
Maybe ist reasonable to differ the email design a bit by choosing different colours for different notification types, so a user can see what the notification is about just based on the colours in the notification email.
see: https://github.com/mattermost/platform/issues/2312#issuecomment-196896155This behaviour leads to that one could not see at first sight which type of message the notification was for, because the email subject is always "New Mention on...".
It would be more informating and appropriate to choose a email subject that makes clear at first sight which kind of mention the notification is about. (channel join, user disabling, mention, etc)
In my opinion a channel join is no mention in sense of a new message. There is a difference between a new message and other System activities and this should be clear withing the notification email.
Maybe ist reasonable…1 vote -
add support for syslog output
It's a pain to deal with many scattered logfiles, so syslog support would be a welcome alternative.
The only extra configuration despite enabling, and the loglevel should be the syslog facility.
https://github.com/mattermost/platform/issues/18204 votes -
make an admin be able to differ between inactive and disabled users
The problem of the current situation is, that an administrator yet is only able to set an user account status to "inactive". This means more a disabling of the user, because the user is in no longer able to log in. In fact, he is locked out.
It would be more appropriate to rename the status "inactive" to "disabled".A new status "inactive" should be introduced where a user is in fact using the featureset of a "team edition". No license is acuired for this user and he doesn't get any push notifications anymore until he logs in again. By loggin in he could reactivate his Enterprise license and get back again all Enterprise features. This would extremly help saving licenses for Enterprise Customers if companies got a lot of users that do either not often use Mattermost or particular users of a Enterprise licensed server do not need the Enterprise features.
This feature would be rounded down by adding a batch job to the console that sets users to inactive automatically when they do not re-login to Mattermost within a to be specified time period.
The problem of the current situation is, that an administrator yet is only able to set an user account status to "inactive". This means more a disabling of the user, because the user is in no longer able to log in. In fact, he is locked out.
It would be more appropriate to rename the status "inactive" to "disabled".A new status "inactive" should be introduced where a user is in fact using the featureset of a "team edition". No license is acuired for this user and he doesn't get any push notifications anymore until he logs in again. By…
2 votes -
Sync between redundant servers
In 2015, GitHub user titanous proposed adding support for more than one instance of the API server. (https://github.com/mattermost/platform/issues/402) It was suggested that it would be added before the 1.0 release, but the issue has since been closed without any changes. Since I didn't see this feature requested in this forum, I thought I would post it so that the community can vote on it.
I work with a team of five, all of whom have personal servers, one of which hosts our Mattermost instance. It would be useful for us if we could host as many as five redundant instances of Mattermost, so that if one of our servers were to go down, we could seamlessly switch to another one without losing messages.In 2015, GitHub user titanous proposed adding support for more than one instance of the API server. (https://github.com/mattermost/platform/issues/402) It was suggested that it would be added before the 1.0 release, but the issue has since been closed without any changes. Since I didn't see this feature requested in this forum, I thought I would post it so that the community can vote on it.
I work with a team of five, all of whom have personal servers, one of which hosts our Mattermost instance. It would be useful for us if we could host as many as five…7 votes -
Don't show 'More' channels if none are available
Currently, the channel list will show 'More...' as the last item in the list.
If there are no further channels created in the team, then this item performs no function other than to confuse users. New channels are obviously created by using the '+' icon at the top of the channel list.
5 votes -
Adding the posting user to the post markup, to enable filtering
posted in http://forum.mattermost.org/t/marking-posts-with-the-user-who-posted-it/912, was told to post it here instead:
I've been playing with mattermost a bit and noticed that posts are not currently marked as having been posted by a specific user - the only element inside a post that identifies the poster is the UserProfile component deep inside the post component tree, so it would be very nice if a component tagged its top with a class like "post__wrapper " for easy chat log filtering: some things that this would unlock:
- hard/soft ignore lists
- hard/soft 'never miss...' lists
- hiding everyone-but-X posts to find information in the backlog
- probably more things that I don't need on a daily basis and so haven't thought of yet =)
posted in http://forum.mattermost.org/t/marking-posts-with-the-user-who-posted-it/912, was told to post it here instead:
I've been playing with mattermost a bit and noticed that posts are not currently marked as having been posted by a specific user - the only element inside a post that identifies the poster is the UserProfile component deep inside the post component tree, so it would be very nice if a component tagged its top with a class like "post__wrapper " for easy chat log filtering: some things that this would unlock:
- hard/soft ignore lists
- hard/soft 'never miss...' lists
- hiding everyone-but-X posts to find information in the backlog
- …
1 vote -
allow per-user settings for showing links inline or not, ideally per content type
from https://github.com/mattermost/platform/issues/1983, While it can be nice to have links to images, youtube videos, etc. that display inline autoexpand to the media that they link to, it would be extremely useful to have a way to turn that off, so that you just get a link instead of losing a massive amount of chat because of the inline media block.
1 vote -
Channel modes
We tend to use the channels in two different ways. Some channels are for chat; a stream of short messages. Other channels have more in-depth messages (like explanations, articles, meeting notes, etc.). In those latter channels, to communication focuses less on a single stream, and more on the replies.
Currently Mattermost solely focuses on chat streams (chat mode), having replies as an option (literally on the side).
I want to suggest an extra mode: topic mode. It differs from the chat mode in the sense that:
- The main might only show the topics (first level messages), not the replies.
- The reply sidebar should be more wider, making it possible to focus better on the replies.
- The input fields for topics might be larger by default, since it will be used for larger texts.We tend to use the channels in two different ways. Some channels are for chat; a stream of short messages. Other channels have more in-depth messages (like explanations, articles, meeting notes, etc.). In those latter channels, to communication focuses less on a single stream, and more on the replies.
Currently Mattermost solely focuses on chat streams (chat mode), having replies as an option (literally on the side).
I want to suggest an extra mode: topic mode. It differs from the chat mode in the sense that:
- The main might only show the topics (first level messages), not the replies.…18 votes -
Add Lita Integration
It would be awesome to have a way to integrate easily with Lita on Mattermost.
18 votes -
nano editor
Some of us prefer nano over vi. It can't be that big of a deal to include nano in the container, can it?
1 vote -
Add per-channel email notification controls
Similar to per-channel desktop notification controls, I'd like the option to disable email notifications on a per channel basis. A good use case for this is our Git repo web hook: I don't need an email telling me I pushed commits to the repository (currently the author name generates a mention notification).
My original forum post might provide additional context.
9 votes
- Don't see your idea?