5 ms·

Wow, this is pretty intriguing and may actually be a solid differentiator in the browser space since it probably requires a considerable stored database of spee

by zmmmmm 16y ago

Wow, this is pretty intriguing and may actually be a solid differentiator in the browser space since it probably requires a considerable stored database of speech samples coupled with a decent back end server farm to do it effectively. Hard for the other players to replicate. Clever move Google! I wonder if they will add this as a standard feature for any text field at some point? It's probably not going to get much sunlight if it requires a chrome-specific attribute on the field.

alextgordon 16y ago
Couldn't the other browsers yank the code from Chrome and use Google's servers too?
- TomOfTTB 16y ago
  Not really. I mean, if Google chose to let them than sure. Otherwise it wouldn't be that hard to have Chrome (which is based on an open source project but is not itself open source) send an encrypted key in each packet ensuring it came from a Chrome browser. That said both Microsoft and Apple have voice recognition engines built into their client OS which seems like a much better option latency wise.
  - aaronsw 16y ago
    And other browsers could just extract the key and ship it as well.
    - TomOfTTB 16y ago
      I'm assuming there would be some kind of algorithm to generate the encrypted key.
      - rryan 16y ago
        The algorithm has to be seeded with a secret (Stream ciphers work this way). You can't get around having to have Chome own a secret, and it's really hard to protect a secret when you're in a hostile environment (e.g. the user's PC). This is part of what makes DRM really hard.
    - ryanpetrich 16y ago
      And get sued for doing so.
  - Sephr 16y ago
    If they're going to support it in Chromium, they'd have to support it for all browsers, else they'd get bad PR, as Chromium is open source.
    - TomOfTTB 16y ago
      I was speaking in the theoretical. Honestly I think Google would be overjoyed if other browsers decided to make themselves reliant on Google's server farm to function. I think that's why the issue isn't really addressed in the proposed standard... https://docs.google.com/View?id=dcfg79pz_5dhnp23f5 https://docs.google.com/View?id=dcfg79pz_5dhnp23f5
ra 16y ago
It might not actually be that difficult to build some level of speech recognition into the browser. See http://cmusphinx.sourceforge.net/ http://cmusphinx.sourceforge.net/

by zmmmmm 16y ago

alextgordon 16y ago

Couldn't the other browsers yank the code from Chrome and use Google's servers too?

TomOfTTB 16y ago
Not really. I mean, if Google chose to let them than sure. Otherwise it wouldn't be that hard to have Chrome (which is based on an open source project but is not itself open source) send an encrypted key in each packet ensuring it came from a Chrome browser. That said both Microsoft and Apple have voice recognition engines built into their client OS which seems like a much better option latency wise.
- aaronsw 16y ago
  And other browsers could just extract the key and ship it as well.
  - TomOfTTB 16y ago
    I'm assuming there would be some kind of algorithm to generate the encrypted key.
    - rryan 16y ago
      The algorithm has to be seeded with a secret (Stream ciphers work this way). You can't get around having to have Chome own a secret, and it's really hard to protect a secret when you're in a hostile environment (e.g. the user's PC). This is part of what makes DRM really hard.
  - ryanpetrich 16y ago
    And get sued for doing so.
- Sephr 16y ago
  If they're going to support it in Chromium, they'd have to support it for all browsers, else they'd get bad PR, as Chromium is open source.
  - TomOfTTB 16y ago
    I was speaking in the theoretical. Honestly I think Google would be overjoyed if other browsers decided to make themselves reliant on Google's server farm to function. I think that's why the issue isn't really addressed in the proposed standard... https://docs.google.com/View?id=dcfg79pz_5dhnp23f5 https://docs.google.com/View?id=dcfg79pz_5dhnp23f5

ra 16y ago

It might not actually be that difficult to build some level of speech recognition into the browser. See http://cmusphinx.sourceforge.net/ http://cmusphinx.sourceforge.net/