Hacker News new | past | comments | ask | show | jobs | submit login

I didn’t mind — ^W is not hard to type — but it does strike me as slightly odd that this seems to have been a conscious choice: “It is based on BitListen by Maximillian Laumeister”, which requests you click anywhere to unmute (https://www.bitlisten.com/).



If I remember correctly, back at the time they adapted BitListen into Listen to Wikipedia, Chrome's policy permitted autoplaying sound.

The "click anywhere to unmute" notification was something I added some time later, after the new autoplay policy, so that people wouldn't think the website was soundless or that sound was broken.


On Firefox, it just starts playing as soon as the tab opens. That's what I was complaining about.


Google Chrome has changed its autoplay policy in the past few years [0] -- sites now require typically user interaction before they're allowed to start the audio context.

You can see this in the page's code [1] -- line 157 and further.

I was surprised to hear the page start playing right away though. Maybe Chrome's "whitelisting" has become more permissive..? See this [2] as well.

[0] https://developers.google.com/web/updates/2017/09/autoplay-p...

[1] http://listen.hatnote.com/

[2] https://developer.mozilla.org/en-US/docs/Web/Media/Autoplay_...




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: