meilon
My feedback
2 results found
-
17 votesmeilon
supported this idea
·
An error occurred while saving the comment -
23 votes
This feature is in progress and planned to ship with Desktop App v4.0
meilon
supported this idea
·
An error occurred while saving the comment meilon
commented
I'd like such a feature as well.
My proposal for the easy way would be:
Check if config file under app.getPath('userData') + '/config.json' exists
if not, try reading config under app.getAppPath() + '/config.json' and copy it's content to the userData one.A better way would be to check on every start (if a admin config.json exists), if the user config.json contains at least the server(s) from the admin config.json. That way, if something changes the admin could make sure everyone has at least the company server, if someone needs an external mattermost server that wouldn't be a problem. And if the name stays the same, an URL change of an existing server wouldn't be a problem, too. An optional flag could tell the app that it should overwrite all servers and settings, should the need arise.
If there will be an acceptance of a pull request for this issue, I'd be happy to code this into the app.
I'd like this on a per message basis, too, especially for webhooks. We send notifications to the group channels, and they are just that. A user would delete it after reading, and if he's on vacation or something, the message just doesn't concern him. It would be nice if a bot could then set a time to when a message is considered "old news" and mattermost deletes them on the next deletion run.