Marco
Marco
Hi @alexxcons , Thanks for the report. There is a "delivery receipt" feature in one to one chats, that will tell you if any device of the receiver ever received...
Hi @DrAxelbauer , thanks for reporting this issue. We are currently working on fixing a number of issues with assets - you can track our progress in this branch: https://github.com/wireapp/wire-android/tree/assets_refactoring
Hi @2048-Bit , sorry for late reply and thanks for opening the issue. This sounds like an issue in AVS indeed. We are in the process of adding more AVS...
Hi @PacoBell , thanks for the suggestion. We will look into this when time allows.
Hi @TubaOrNotTuba , Thanks for writing this up. I believe the issue is not with the message per se, but with the fact that dropping the websocket too often (which...
Hi @MSavoritias , thanks for starting the conversation. At the moment we keep the text for attribution (giving credit to the giphy service). The current solution was the less engineering-demanding...
Hi @kirillt , no changes have been made to Giphy since then.
Hi everyone, thanks for contributing to the conversation. The SMS code is not generated by the Android application but by the wire server application. Moving this issue there.
Hi all and thanks for the feedback, we are planning to completely overhaul the calling system to make it more reliable, in particular with regards to network conditions. This will...
Hi @JohnyM01 , I believe this is not an issue with calling per se, but with notifications not reaching your phone (including calling). There are a number of things to...