We all know that people need to concentrate to work efficiently. This is why macOS and then all the operating systems have introduced the "Do not Disturb" mode, which allows to focus on your work.
And I think we can do even better while integrating it to Mattermost.
What is in the "Do not disturb" functionality ? It stops alls notification except the ones which doesn't disturb you.
But the question is : why is it interesting to add it to Mattermost ?
In a Mattermost server (for me), there are lots of different channels. Even the basics channels of Mattermost show us this : a "Town Square" which is the reception of your server, and an "Off Topic", which is the channel for entertainment. But in some server (as mine), there are lots of different "Off Topic" channels, for lots of different entertaining things.
Here is why a do not disturb could be good.
When you press this button, you won't receive any notification from all the channel that are not work channels, but in addition to that you will not have access to those disturbing channels.
For example, if I have to work hard to finish a mission, I will enable the "Do not Disturb" mode in Mattermost, and I won't be able to see my notification for the disturbing channels, but I won't be able to access to those. Or maybe if I click on one of those channels, I will get an alert which will say me "Hey, you are on "Do Not Disturb" mode, you have to work (or something like that)
What do you think about that ?
BCPG.

There are several options now provided for changing the grouping and ordering of channels, but one is conspicuously missing IMO: the ability to change the ordering of the groupings.

In my use of MM, I have a small handful of favorite channels, and then a bunch of other channels, and then a small handful of direct messages. Most of my communication is in the favorite channels and the direct messages, but the former is at the very top and the latter is at the very bottom. It is annoying to have to scroll through the wasteland of all of my non-favorite channels every time I need to switch between the two groupings I actually use.

Currently i'm reading 2 books the one is about American tradition like their dressing ways their food or like famous food of American people and majorly about their ascent like what is the difference between American ascent and England and some other staff and the second book which named as the "Animal Horn"[1] many early hornbooks were made by printing letters onto paper or vellum (animal skin) – both expensive materials at the time. To protect them, the letters were covered with a layer of animal horn like cow horns, sheep, goat etc so thin that it was see-through. This horn was fixed to a wooden or leather base, which was known as a hornbook. Sometimes the ‘books’ were made from metal, ivory, or bone like this one, but they still kept the same name. Some were even baked out of gingerbread to tempt children to ‘swallow what they read'
[1] https://hornsavvy.com/
what are you upto guys?

At the moment, you can configure users to be allowed to send direct messages either to other members of the team or to anyone on the server.

I'd like to make it so that normal users cannot start direct messages at all.

My particular usecase may be a little out of the sweet spot - I have created a mattermost for my children (quite young) who I want to be able to chat with while they are doing their home learning, but don't want them using public chat systems. I am happy for them to interact with each other in the public channels I have created, but I don't want them distracting each other with lots of messages that are difficult for me to see.

My favourite scenario would be just for non admin users simply not be able to create new direct messages.

While this is specifically for a home learning situation, I believe it could be useful in a corporate world too, although there it would have to be per user - it might be the kind of restriction you'd want on external users from outside of your organisation.

Custom attributes should optionally support having both a name and a value at the point of definition by the system admin.
They would be as currently assigned to users/teams/group as
appropriate. The value of the attribute could then be set at this time or by the user, team/group owner in a custom attribute extension to the user profile or similarly for for teams and group. Support for attributes of type simple
(no value, current behavior), required (must be set), overridable (can be changed or not from value set by system) could also be added.
An extension to markdown to return the value (could also contain markdown) of an custom attribute would also be useful e.g. "I have the following hobbies : %Hobbies%"