402
submitted 11 months ago by minnix@lemux.minnix.dev to c/privacy@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] pixxelkick@lemmy.world 60 points 11 months ago

Do people seriously still think this is a thing?

Literally anyone can run the basic numbers on the bandwidth that would be involved, you have 2 options:

  1. They stream the audio out to their own servers which process is there. The bandwidth involved would be INSTANTLY obvious, as streaming audio out is non-trivial and anyone can pop open their phone to monitor their network usage. You'd hit your data limit in 1-2 days right away

  2. They have the app always on and listening for "wakewords", which then trigger the recording and only then does it stream audio out. WakewordS plural is doing a LOT of heavy lifting here. Just 1 single wakeword takes a tremendous amount of training and money, and if they wanted the countless amount of them that would be required for what people are claiming? We're talking a LOT of money. But thats not all, running that sort of program is extremely resource intensive and, once again, you can monitor your phones resource usage, you'd see the app at the top burning through your battery like no tomorrow. Android and iPhone both have notifications to inform you if a specific app is using a lot of battery power and will show you this sort of indicator. You'd once again instantly notice such an app running.

I think a big part of this misunderstanding comes from the fact that Alexa/Google devices seem so small and trivial for their wakewords.

What people dont know though is Alexa / Google Home have an entire dedicated board with its own dedicated processor JUST for detecting their ONE wake word, and not only that they explicitly chose a phrase that is easy to listen for

"Okay Google" and "Hey Alexa" have a non-trivial amount of engineering baked into making sure they are distinct and less likely to get mistaken for other words, and even despite that they have false positives constantly.

If thats the amount of resources involved for just one wake word/phrase, you have to understand that targeted marking would require hundreds times that, its not viable for your phone to do it 24/7 without also doubling as a hand warmer in your pocket all day long.

[-] GreatBlueHeron@lemmy.ca 4 points 11 months ago

What you're saying makes sense, but I can't believe nobody has bought up the fact that a lot of our phones are constantly listening for music and displaying the song details on our lock screen. That all happens without the little green microphone active light and minimal battery and bandwidth consumption.

I know next to nothing about the technology involved, but it doesn't seem like it's very far from listening for advertising keywords.

[-] liquidparasyte@pawb.social 2 points 11 months ago

That uses a similar approach to the wake word technology, but slightly differently applied.

I am not a computer or ML scientist but this is the gist of how it was explained to me:

Your smartphone will have a low-powered chip connect to your microphone when it is not in use/phone is idle to run a local AI model (this is how it works offline) that asks one thing: is this music or is it not music. Anyway, after that model decides it's music, it wakes up the main CPU which looks up a snippet of that audio against a database of other audio snippets that correspond to popular/likely songs, and then it displays a song match.

To answer your questions about how it's different:

  • the song id happens on a system level access, so it doesn't go through the normal audio permission system, and thus wouldn't trigger the microphone access notification.

  • because it is using a low-powered detection system rather than always having the microphone on, it can run with much less battery usage.

  • As I understand it, it's a lot easier to tell if audio seems like it's music than whether it's a specific intelligible word that you may or may not be looking for, which you then have to process into language that's linked to metadata, etc etc.

  • The initial size of the database is somewhat minor, as what is downloaded is a selection of audio patterns that the audio snippet is compared against. This database gets rotated over time, and the song id apps often also allow you to send your audio snippet to the online megadatabases (Apple's music library/Google's music library) for better protection, but overall the data transfer isn't very noticeable. Searching for arbitrary hot words cannot be nearly as optimized as assistant activations or music detection, especially if it's not built into the system.

And that's about it....for now.

All of this is built on current knowledge of researchers analysing data traffic, OS functions, ML audio detection, mobile computation capabilities, and traditional mobile assistants. It's possible that this may change radically in the near future, where arbitrary audio detection/collection somehow becomes much cheaper computationally, or generative AI makes it easy to extrapolate conversations from low quality audio snippets, or something else I don't know yet.

load more comments (10 replies)
this post was submitted on 15 Dec 2023
402 points (95.3% liked)

Privacy

32045 readers
1563 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS