3 ms·
This. There's a nice paradox. Until the AI is good enough to understand the voice data, it can't know that it isn't privacy-violating -- up to and including ext
by dash2 7y ago
This. There's a nice paradox. Until the AI is good enough to understand the voice data, it can't know that it isn't privacy-violating -- up to and including extremes like somebody telling their most intimate secrets. Exposing this data to any other human, whether a subcontractor or internal employee, is a potential privacy violation, full stop.
- laumars 7y agoI would rather the voice processing happened locally on your device. We must be getting to the stage where that's becoming viable? If not entirely in software then via a custom chip. Even if that transcript then still needs to be sent to the cloud for processing (eg for translating human sentences into logical actions might still be out of the grasp of home devices), developers can at least then send the data tokenised (which wouldn't be possible if it was a compressed audio stream) and then get a server response referencing those tokenised place holders. A simplistic example of my point might be Message: I need to book a doctors appointment for erectile dysfunction. Sent: I need to book a $ARG[0] appointment for $ARG[1]. Received: { "action": "ring"; "subject": "$ARG[0]"; "message": "appointment for $ARG[1]" } I appreciate something like that wouldn't be infallible but it would still go a long way to redacting sensitive or identifiable information and thus a huge step forward for privacy.