AliExpress runs silent WebAudio fingerprinting that breaks Bluetooth multipoint

The discussion landed on two conclusions. First, this is as much a browser platform failure as a site abuse story. Users usually get clear prompts for camera and microphone, but not for audio output or for API use that can wake hardware, steal audio focus, or create new fingerprinting entropy. People want better visibility at minimum, like tab indicators for any live audio context, and many want autoplay-style blocking or explicit permission for audio output. Second, fully detecting or banning fingerprinting at the browser layer is harder than it sounds because the same APIs also support legitimate features and nearly every measurable property can become part of a fingerprint. That pushed the conversation toward mitigation, not magic detection: reduce API surface, normalize outputs, add better user controls, and block known bad scripts. The practical fix today is narrow and manual. The article’s custom uBlock Origin filters stop the AliExpress scripts, while Firefox users also noted per-site autoplay blocking can blunt some cases. A Mozilla engineer added that WebAudio fingerprinting is already partly mitigated in Firefox, which suggests the vendor response is moving toward output normalization rather than trying to guess intent.