3 ms·

Your speech data assertion looks to be inaccurate, the user does have to opt in. Nor does the response sound like a mea culpa. I wouldn't use it, but seems re

Your speech data assertion looks to be inaccurate, the user does have to opt in. Nor does the response sound like a mea culpa. I wouldn't use it, but seems reasonable for people who might want to.

bramhaag 8mo ago
Yes, sent*, not sends. Before they got called out, it was opt-out. No consent dialog, warning, or any other sort of confirmation before sending audio to OpenAI. The keyboard is auto-enabled. Almost half a year after the controversy started, they added a consent dialog (https://gitlab.e.foundation/e/os/murena-voice-to-text/-/commit/58d946b https://gitlab.e.foundation/e/os/murena-voice-to-text/-/comm...). A few months later, they actually made the consent dialog function as intended (https://gitlab.e.foundation/e/os/murena-voice-to-text/-/commit/562f813 https://gitlab.e.foundation/e/os/murena-voice-to-text/-/comm...). Mistakes happen, but initially Murena: 1. sent voice messages to OpenAI 2. did not anonymise said voice messages, only their origin 3. did not ask the user for consent 4. ignored the user's consent after they started asking for it That is not a good look for a privacy-focused OS. There is now a working consent dialog before using this feature, and audio is actually anonymised (random pitch shifting + filtering + noise), but it took them nearly 8 months to address all of this after getting called out.