Google Releases Chrome 25 With Voice Recognition Support
An anonymous reader writes "Google on Thursday released Chrome version 25 for Windows, Mac, and Linux. While Chrome 24 was largely a stability release, Chrome 25 is all about features, including voice recognition support via the newly added Web Speech API and the blocking of silent extension installation. You can update to the latest release now using the browser's built-in silent updater, or download it directly from google.com/chrome." But if you're more interested in the growing raft of Google-branded hardware than running Google OSes, some good news (via Liliputing) about the newly released Pixel: Bill Richardson of Google posted on Thursday that the Pixel can boot Linux Mint, and explained how users can follow his example, by taking advantage of new support for a user-provided bootloader.
I see what you did there, this is social engineering. Who is going to shout at their monitor "Natalie Portman grits petrified porn"?
Fappist: "Natalie Portman grits petrified porn"
Chrome: "Madly norman sits petrified corn"
Fappist: "NATALIE PORTMAN GRITS PETRIFIED PORN"
Chrome: "Actually foreman knits electrified morn"
FAPPIST: "GRRRRR! NATALIE PORTMAN GRITS PETRIFIED PORN!!!!"
One of these days, I'll have a supported version of Chrome which can address more than 4GB of memory in my !Linux boxen...
"In the end, there is simply no weapon more devastating than the truth, delivered in just the right way." - tnk1
It looks like they're making a marketing mistake: they make it sound as if they added recognition of arbitrary text.
There are only two things voice recognition is useful for:
* taking a small number of distinct commands
* producing nonsense poetry that keeps rhythm and rhyme with input voice
A small corpus of words can be distinguished between pretty easily -- as long as no two are similar to each other. In a real language, with many thousands of words, even a human has a hard time without understanding the subject matter and filling the gaps from context. In fact, what you hear is mostly gaps -- just try to transcribe a series of random words with any real speed. Or, for another example: in a written text, randomly permute all letters except the first and last in every word -- it will still be pretty understandable if you recognize its sense or not at all if you don't. And recognizing the sense is an AI-hard task.
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
Locally? Or on their servers?
Next time you go and search, will you start getting ads for sports illustrated's swimsuit edition and Quaker?
How do you pronounce "Goatse" anyhow?
Skip ------ See the latest from http://www.anArchyFortWorth.com
Not to sound like a rant but I've almost had it with their countless bugs with password saving.. I tried every trick on the net short of abandoning it for another browser.. it won't save my passwords anymore, it never updates my existing passwords, and the ones I delete won't ask me to add them anymore.. And googling around I see countless others who have the same problems since 2009.
No I don't want to use another plugin, I'd prefer to stick to google's own as much as possible and not replicate features.. I just would have thought Google would put more effort into this seeing as how large they are and how anal they were when it came to interviewing for a job there. I expected better...
Let's hope the message gets through..
What's with the releases every couple months? What's with the bloat? Why don't they address speed and stability bugs that have been open for two years?
Oh wait. This is a Chrome thread. Google gets a pass. Never mind.
Since this morning's update on Ubuntu I can't pull up Gmail. It's pretty darned annoying and now I've gone back to Firefox to wait for the next update to fix whatever is really busted.
No? Wake me if it ever does.
I'm 31 and I am the current generation of consumerists...I can type faster than I can talk (I am special because I was taught to type when I was 7). I was in high school before computers where common. kids now have been typing as long as they have been writing. I don't see speech recognition as being to terribly important, but it does have its use cases.
sorry for my comments, I'm drunk
One of my favourite spontaneous epithets being, "Bite me!"
I'm sure inventive Slashdotters can devise even more entertaining variations.
Il n'y a pas de Planet B.
"Display bookmark sidebar."
The difference between a Rolls Royce and a Volkswagen Beetle is in the 10% that costs 90% of the price/time. One of the reasons Apple did so well with its products is that it at least went for 5% at not to much extra. The "it just works" praise Apple often gets means a REALLY boring job for someone who doesn't get to build anything exciting and new but just has to fix small trivial bugs that only occur during a blue moon but are the difference between something working and NOT working.
Consider this: Java. No deb files just yum and rpm support.
Chrome has deb packages for ubuntu.
Opera has special deb packages for mint to.
Now which is the piece of software recommended to be removed and which is the browser that just resumes where it left off, has build in mouse support, multi-account password managment build in and works on the most number of environments?
Building so many packages is a boring task but it is the difference between a polished product and a cutting edge product.
There is a man at Rolls Royce whose only job is to hand paint a stripe on the car. Something tells me that from this you can conclude that the paint job on a rolls is better then that on an Brazilian build beetle. It takes a lot of people taking exceptional care in seemingly trivial detail to get a truly polished experience out the door.
It is one reason Americans make better entertainment movies. No European would think of putting fake scaffolding on top of a skyscraper to make it look taller. Americans do... it makes for better entertainment movies because some guy in props is spending time thinking how to make a sky scraper look even better.
Google releases a lot of stuff but they never ever really finish it because they all moved on to the next big thing. It "works". You won't see a cutting edge Rolls Royce long after other car makers have already implemented a new feature.
Make your choice, polish or cutting edge.
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
I have not had the opportunity, but is voice disabled by default and the user can selectively turn it on? I don't mean is the checkbox checked to turn it off ... is it actually off and not phoning home?
Winners tell stories while losers yell deal.
Google - the front runner of innovation :)
Btw I think this has something to do with Google Glass - those glasses will be just an aux display for the phone. Phone needs to have good voice recognition integration. To get there in time they are starting with pc browser (10 years too late).
Who logs in to gdm? Not I, said the duck.
I don't know whether this has been mentioned before, but the big problem with Google's approach is that it won't allow me to define a formal grammar as the "set of things the user might reasonably say". Dictionary recognition, as is employed here and on the Android phones, has the big disadvantage that I would need some kind of natural language understanding on the (already error-prone result) for anything but dictating text.
It is in essence a projection of voice to an N-Best list of recognition results. No if I could specify a grammar (e.g. per SRGS), I could have semantic annotation per SSML and use voice to actually control an application.
something clever to make me stand out!
From the press release: "We’ve also resolved a high severity security issue by disabling MathML in this release. The WebKit MathML implementation isn’t quite ready for prime time yet but we are excited to enable it again in a future release once the security issues have been addressed."
Let me know when the geniuses over at Google finally figure out how to release a version of Chrome that has a fucking menu bar. Until then, I'll stick to FireFox and Opera.
LK
"Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
AFAICT from reading the API spec and surrounding information is that's not a problem with "Google's approach", its a problem with the fact that the W3C Speech API Community Group couldn't come to a consensus on the grammar format(s) to support in the Web Speech API, so that while the API adopted in the group's final report specifies containers for grammars and how to attach them to recognition requests, it doesn't specify any actual formats for grammars.
Since the mission of the group was to come up with a consensus limited-subset specification as a step on the road to a specification that would meet the full set of use cases set out by the Final Report of the Speech Incubator Group's final report, it makes sense for an implementation of the Web Speech API not to adopt an approach on grammars that would fail to be forward-compatible with the anticipated future specification, since that would encourage building applications that would be broken under the expected follow-on full-featured speech API, which can be expected to retain compatibility with the limited-subset API in the areas covered by that API, but is less likely to do so in areas not covered by the limited-subset API.