Hacker News Reader

Comment by scrollaway | Hacker News Reader

So after playing around with the page, I just started saying random things to see how the speech API would fare with my atrocious accent. That was interesting, until I said "the quick fox", and it interpreted ... bleeped speech?

    2015-06-20 03:02:49.109 say_restyle.js:7 Speech recognized: the quick f****
    2015-06-20 03:02:49.110 say_restyle.js:7 Speech recognized: the quick Fox
    2015-06-20 03:02:49.110 say_restyle.js:7 Speech recognized: quick f****

What the fox?

View on HN

I noticed that while I was developing the script. I'm using annyang -- https://github.com/TalAter/annyang -- to interact with the web speech API, and it doesn't look like annyang is the one censoring the results, so it must be ... the API itself?

That is unbelievably messed up. The fear of swear words in american culture actually messing with APIs. I really hope this isn't what it looks like and someone is playing a prank somewhere.

Yes - in particular, it's done server-side by Google. It seems that there is a config option to turn it off. http://src.chromium.org/viewvc/chrome/trunk/src/content/brow...

Am I really the only one freaked out by this?

No. The idea that your voice is being recorded and sent to Google is something that a lot of people might not want.

I think you missed the point.

Interesting that they're using FLAC as the encoder... Seems like it would be very memory intensive.

Can you say specifically where for the stupid people like me? I looked through and did not see anything.

Reply on news.ycombinator.com