It's a legitimate way to transfer data. I linked it here in a discussion about something more surreptitious but I doubt it'd actually be useful in that context.

It's a legitimate way to transfer data. I linked it here in a discussion about something more surreptitious but I doubt it'd actually be useful in that context. Think of it like an audio QR code -- anywhere a QR code might be useful, this could also be useful. And it already is pretty much fully cross-platform. Firefox downsamples in order to save CPU cycles on noise reduction and echo cancellation. Also yeah, I forgot about the div that gets added. Since that page is just a demo, I don't necessarily see any reason to display additional receiver info. The hope is that this is a workable library that won't put a lot of burden on the end-user in order to confirm it's working. Perhaps all that's missing here is looking at signal energy just to confirm that the mic isn't muted, and displaying something if it is. The lab only transmits to itself because of UI sync difficulties. It is on my road map to come back to this later, but essentially the issue is that the receiver has to have the same setup as the transmitter, which would require some out-of-band method to sync up. Running it on my laptop seems to be a perfectly workable way to test the config.