Open simosimi993 opened 1 year ago
Thank you @simosimi993
Actually this is a know defact caused by the fact that the Tor browser do not support the WebAudio API because it would enable browser fingeprinting: https://fingerprint.com/blog/audio-fingerprinting/
@msmannan00 @gianlucagilardi @ danielvaknine @rglauco @larrykind: what do you recommend to handle this incompatibility?
Maybe we could find a way to show a text area as alternative to the voice when users visit a questionnaire that includes voice questions?
There is not much that can be done. You could just have a warning that Tor Browser users cannot file voice reports. From a compliance standpoint it works anyway, since you just need to have a voice message system and Tor access is not a legal requirement. I guess it can be handled at a questionnaire level, e.g., in my template I have a second questionnaire step asking for the kind of submission (voice/writing) which then triggers conditionally the following step. I'd just add a disclaimer at the time of the choice, so that the whistleblower using Tor Browser can choose either to continue using that browser to file a written report or switch to another browser to file an oral report.
What version of GlobaLeaks are you using?
the issue persist from 412.3.0 until the last one (4.13.9)
What browser(s) are you seeing the problem on?
Tor Browser
What operating system(s) are you seeing the problem on?
Windows, macOS
Describe the issue
When i reach the voice question on the questionnaire i cannot rec my vocal message and i see:
{{seconds}}/{{fields.attrs.max_len.value}}
Proposed solution
No response