Adrian
My feedback
5 results found
-
10 votes
An error occurred while saving the comment -
18 votes
An error occurred while saving the comment Adrian
commented
No, it's not covered by the CLI tool:
- CLI hard-deletes instead of flagging as deleted
- CLI tool doesn't post websocket messages, so people will not notice the team being deleted if they are currently in it. -
275 votesAdrian
supported this idea
·
An error occurred while saving the comment Adrian
commented
Very good idea. Especially social channels are more useful if they are team-independent. While creating another team containing these channels would work, you'd always need to switch between teams to view these channels, which is not very user-friendly.
-
10 votes
An error occurred while saving the comment Adrian
commented
This would be beneficial in the team edition as well, since even in a team you might have some subcommunities where you don't want everyone to join immediately. For team edition the only way to join such a channel would be being approved by any member (since there are no channel admins), while enterprise would have all the options - channel member, channel admin, or LDAP group, and maybe even an external API call to determine whether someone can join or not.
Adrian
shared this idea
·
-
8 votesAdrian
shared this idea
·
Numeric IDs are not sensitive data, you cannot do anything useful with them. However, human-readable team/channel/user names or even message contents are a problem. Disabling them in the settings is not great, because e.g. on smartwatches this makes notifications basically useless.
Unfortunately Mattermost is not "privacy-first" in this regard, as their new "ID-loaded notifications" feature (which is exactly what you are asking for) is restricted to Enterprise Edition E20, even though this would be good for privacy even on a small Team Edition instance!