Chrome is basically crippling Chromium's features

Re:Chrome is basically crippling Chromium's features by CommanderData on Thursday April 27, 2017 @07:21AM (#14210659)

Chromium's Web Speech API 'ServiceURI' attribute was removed recently allowing you to specify your own speech recognition service instead of the default Google's Speech service.

Last Wednesday, I tried searching for a work-around, it would seem I'd have to build something with WebRTC to achieve similar responsiveness. The attribute was available until 49.

I don't know the reason behind its removal. There isn't anything to suggest Google is forcing you into their speech service (which is expensive) but it would be nice to ASR on your own server and have the attribute back as per the specification or not be forced into using Cloud Speech or reinvent the wheel.

Spec: https://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.htm...

Others seem to have noticed: https://groups.google.com/a/chromium.org/forum/#!searchin/ch...

[ Parent | on HN ]

Re:Chrome is basically crippling Chromium's features by gsnedders on Thursday April 27, 2017 @08:07AM (#14210829)

The commit mesasaging dropping it: "Reverting serviceURI since it is not supported anymore."

That at least implies it was already unsupported, and the code diff doesn't seem to change anything notable. Looking through history I can't find any evidence of serviceURI ever being hooked up to anything? Are you sure setting serviceURI ever actually did anything?

[ Parent | on HN ]