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
The people in our testing groups ("ChatOps for non-DevOps people") do not work in a typical T.I. environment, often use chat platforms that are different from corporate chats (i.e. Slack, HipChat, Glip, Gitter...), but maybe "more simple", but mainstram messengers: WhatsApp, Facebook Messager, then others, by this order or usage.
If slack/HipChat/Etc promote themselves as a replacement for e-mail, we could think that what we are trying here is to replace mainstream chat with some more intelligent version of itself. This could be done or 1) improving (example: adding chatbots used for chatops to mainstream messagers) or 2) replacing with new chat platforms. Both ways are in testing in this working grouo.
This specific issue discuss the second alternative, with usage of rocket.chat (a very very good hackeable platform) to be more friendly for Facebook/WhatsApp related to voice audio.
Perceived problem when uploading voice using rocket.chat: "it does not work" "it works for small length audio"
Server problem: audio files where blocked because of default server upload size (2mb); increasing upload to 10mb make it work
File size problem: files are encoded in .wav, with very low compression rate; even if server compress a file before share to others, would waste too much bandwish if encoding does not occour on client side, before upload
I'll still get more information about the problem in the next few days. I asked them to send files on different platforms to allow comparison.
The text was updated successfully, but these errors were encountered:
The people in our testing groups ("ChatOps for non-DevOps people") do not work in a typical T.I. environment, often use chat platforms that are different from corporate chats (i.e. Slack, HipChat, Glip, Gitter...), but maybe "more simple", but mainstram messengers: WhatsApp, Facebook Messager, then others, by this order or usage.
If slack/HipChat/Etc promote themselves as a replacement for e-mail, we could think that what we are trying here is to replace mainstream chat with some more intelligent version of itself. This could be done or 1) improving (example: adding chatbots used for chatops to mainstream messagers) or 2) replacing with new chat platforms. Both ways are in testing in this working grouo.
This specific issue discuss the second alternative, with usage of rocket.chat (a very very good hackeable platform) to be more friendly for Facebook/WhatsApp related to voice audio.
I'll still get more information about the problem in the next few days. I asked them to send files on different platforms to allow comparison.
The text was updated successfully, but these errors were encountered: