New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 804812 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Remove censorship from webkitSpeechRecognition

Reported by olegs.ku...@gmail.com, Jan 23 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Steps to reproduce the problem:
1. open www.google.de
2. say arschloch
3. search censored to a********

What is the expected behavior?
A user preserves a human right to say and type on the device whatever he/she wants to

What went wrong?
webkitSpeechRecognition censors offensive words

Did this work before? No 

Does this work in other browsers? N/A

Chrome version: 63.0.3239.132  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 27.0 r0
 
Labels: Needs-Triage-M63
Cc: vamshi.k...@techmahindra.com
Labels: Triaged-ET M-66 FoundIn-66 Target-66 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on reported chrome version 63.0.3239.132 and on the latest dev 66.0.3330.0 using Ubuntu 14.04, windows 10 and Mac 10.13.1.
As the issue is seen from M60(60.0.3072.0) hence considering it as non-regression and marking it as Untriaged.

Thanks!
All Deletes /banchod
All Deletes /banchod

Comment 5 Deleted

Comment 6 Deleted

Comment 7 Deleted

Able to reproduce at Chromium 63.0.3239.132 at *nix.

Concur with OP:

What is the expected behavior?
A user preserves a human right to say and type on the device whatever he/she wants to
Where is the source code for this implementation at https://cs.chromium.org/?

http://www.adambarth.com/experimental/crx/docs/experimental.speechInput.html mentions a `filterProfanities` option for `chrome.experimental.speechInput`.  

Have not yet found where the censorship is implemented for `webkitSpeechSynthesisRecognition`.
It is possible to get `"assshole"` and `"arsehole"` for "asshole" and  `"fuc"`  `"fuk"` and `"phuck"` for "fuck" at the `SpeechRecognitionAlternative` `transcript` when `SpeechRecognition` `maxAlternatives` is set to a value greater than `1`. 

You should then be able to parse the accumulated results using an algorithm to reconstruct an uncensored result.

Sign in to add a comment