You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for developing this plugin. This is the main reason mattermost is useful for me and my international team.
Being opensource and based on AWS is important for privacy and security issues, in that area slack+untangle (its auto translation bot) cannot match. However the slack combo has an important feature that is lacking in the mattermost counterpart, that is to translate an entire channel, so that the user do not need to click the "translate" button for every message.
We are in the creative industries and being able to exchange ideas seamlessly and freely is important, the conversation needs to have a flow, the translate button can break this flow. This is the only reason we cannot adopt mattermost right now.
Please consider adding the feature to translate every new message for the entire channel without further user input.
Cheers
DS
The text was updated successfully, but these errors were encountered:
Thank you for developing this plugin. This is the main reason mattermost is useful for me and my international team.
Being opensource and based on AWS is important for privacy and security issues, in that area slack+untangle (its auto translation bot) cannot match. However the slack combo has an important feature that is lacking in the mattermost counterpart, that is to translate an entire channel, so that the user do not need to click the "translate" button for every message.
We are in the creative industries and being able to exchange ideas seamlessly and freely is important, the conversation needs to have a flow, the translate button can break this flow. This is the only reason we cannot adopt mattermost right now.
Please consider adding the feature to translate every new message for the entire channel without further user input.
Cheers
DS
The text was updated successfully, but these errors were encountered: