Did Google Fake Its Big A.I. Demo?
vanityfair.com
vanityfair.com
"As Axios[0] noted Thursday morning, there was something a little off in the conversations the A.I. had on the phone with businesses, suggesting that perhaps Google had faked, or at least edited, its demo. Unlike a typical business (Axios called more than two dozen hair salons and restaurants), the employees who answered the phone in Google’s demos don’t identify the name of the business, or themselves. Nor is there any ambient noise in Google’s recordings, as one would expect in a hair salon or a restaurant. At no point in Google’s conversations with the businesses did the employees who answered the phone ask for the phone number or other contact information from the A.I. Further, California is a two-party consent state, meaning that both parties need to consent in order for a phone conversation to be legally recorded. Did Google seek the permission of these businesses before calling them for the purposes of the demo? Was it staged in the simulated manner of reality TV?"
0. https://www.axios.com/google-ai-demo-questions-9a57afad-9854...
Google probably wants recordings of each call, so they'd have to include a preamble. Phone systems that say "Your call may be recorded for quality assurance purposes" usually:
1. Make you press a button before you speak to a human, thereby recording your consent.
2. Don't record before that point (since you're in the phone tree.)
Seems unlikely Duplex will pass as human, for legal reasons.
They're not testing it in California, is one option. Two party consent is not the standard in most states.
http://www.dmlp.org/legal-guide/recording-phone-calls-and-co...
Another hypo: What if my AI bot calls the restaurant and talks to their AI bot? Is that a call with zero parties? Can consent for recording be given at all?
My guess is that it depends on the definition of "party". Cue the lawyers.
I believe generally the US courts have decided that the person who triggers the action is the pertinent party.
Something similar has come up in the firearm fabrication community. There are companies that sell things that are legally paperweights, but are 80% of the way towards being a firearm (e.g. [1]). There are CNC mills that come with programming to take one of these "80% lowers" and finish it, making a fully functional firearm, or at least the part that is considered a firearm by the BATF; other parts can be ordered and shipped online (e.g. [2]).
In this case it's not the builder of the machine or the writer of the code that instructs it that is the "manufacturer" of the gun. It's not even the person who placed the unfinished lower in the enclosure and bolted it down. Instead it's the person who pushed that button.
I'm going to guess that this will be similar. The user who pushes the button (or asks assistant to make an appointment on their behalf) is likely to be the one giving consent.
But neither the laws nor the judges will be uniform. The laws use different words to say slightly different things, and will have different legislative histories (the record from the officials who voted them into law).
Some judges will look to the actual words to interpret the law, and others will look to the legislative history. Still others might desire a "living Constitution" approach — applying the laws in a way that they think makes sense in today's world.
Considering the dozens of laws and thousands of judges that could opine, there will likely be considerable uncertainty in this area for years to come.
I immediately visualised two physical robots attaching old-school landline handsets to acoustic couplers on their torso.
If that software were incorporated, or was acting as or for a corporation, could it?
Interesting question - would love to hear an opinion from a lawyer.
Side question: What makes recording voicemail legal? Is there just a presumption that people understand that voicemail is a recording? I don't think I've ever heard a two-party consent warning before leaving a message.
Presumptively no one forces you into making a recording at the beep. And the recording doesn't start until after the beep.
Would it be illegal to record voicemail without the beep?
Would be cool if the government created a "recording consent" sound, so you could play it in lieu of spending 5 seconds to explain that you'll be recording. I suspect a beep does not qualify in most situations, would need to be more distinctive.
Saying "leave your message after the beep" seems unambiguous, but are fake messages where someone pretends to answer the phone in a legal gray area?
(I'd guess voicemail is a legally-ambiguous loophole that was grandfathered in because so much of the population understands it, but curious)
I wondered how this worked with things like Google's earphones that (supposedly) translate from one language to another. Those translations all get recorded and all get sent to Google's cloud (and, likely, get stored there too).
Sure, there are going to be some ephemeral copies made in codecs, DSP's and such, but my cell phone does the same.
Google may want recordings so they can evaluate the system after a call, but they don't have to make them.
Consent after the call would be just fine to exempt someone from liability under California's privacy act.
…seems kind of unnecessary in this context.
If the calls were real, I wonder how many recordings did it take to get these perfect examples? How many times were the appointments scheduled correctly, and how many failed?
But this was just a flashy demonstration to drum up excitement over the Google brand. Until they write up a paper or release it as a product, we're unlikely to know how well it really works.
The question will be what is the net time savings? If it works 99 out of 100 times, maybe that's good enough for many mundane tasks. But if it's 75 out of 100, that's almost certainly not worth it.
Consider the new Apple keyboards, which attract hundreds of intense complaints every time they come up here on HN. Apple Insider [1] estimated the percentage of service tickets that were attributed to keyboards:
2014 - 5.6%
2015 - 6%
2016 - 11.8% (first year of new keyboard)
2017 so far - 8.1%
So, an approximate doubling of the prevalence of keyboard problems in the first year has been enough to convince a lot of people that the entire product is an unmitigated disaster.
One of the very interesting facts in that Apple Insider study is that the total number of tickets actually decreased from 2015 to 2016. If the keyboard was actually a design disaster, you would expect the total number of warranty service tickets to climb, but they didn't.
2014 - 2,120
2015 - 1,904
2016 - 1,402
2017 - (incomplete)
[1] https://appleinsider.com/articles/18/04/30/2016-macbook-pro-...
Also, I distinctly remember on multiple occasions having to ask "is this <XX restaurant>?" when making reservations in the past. Does this really never happen to people that it feels more likely that Google is faking high-profile demos in the keynote that it can't actually deliver on? And wouldn't they want to pick demos that didn't include or redacted the name of the restaurant anyway?
There's nothing entirely wrong with that, but not being open that such a thing occurred makes you look very dishonest...and if you can't answer basic questions about the event, you're probably hiding something. The tech isn't that different from what some telemarketing companies do, so it's not like people are saying this is impossible (some are very convincing.)
- (G) Hello, I want to make appointment for my client.
- Sure, what would you like and when?
- (G) Sorry, I don't understand
- What service would you like to set an appointment for and on which date?
- (G) I can't help you with this yet..
- ?? What the hell are you talking about?
- (G) Playing Katy Perry station on Spotify
Not really joking :(
Everyone who thinks that there are multiple distinct assistants worked on at Google (not the separate features powered by THE ONE) - Apple would like to have a word with you. Yes, it just like chat apps - another team just need to start thinking of promotions.
And since I've been caught talking nonsense let me explain how I (as an outsider) got these crazy ideas:
I overestimated complexity involved in creating smarts behind it, Siri and Bixby mislead me. Glad to know that google assistant and duplex are two absolutely different products and duplex is not a new feature on the same (often confused by the same words commands) foundation.
And I thought that due to all the complexity to create this original assistant/AI it would be high-level product where even in messed up corporation environments no duplicate efforts would slip through (we all know how dysfunctional big companies are, or maybe just because it's Google (they have multiple chat apps) that's the way how they approach all the initiatives). Of course I was wrong and they have multiple assistants being created. It's just a matter of having one more team tasked with it.
Those Apple and Samsung, looks like they're not even trying!
And about submission itself - it was an absolutely real call to suspecting nothing regular person, who just happened to talk in that particular way, similar to how I try to provide all the context when doing web searches (but funny thing is that it doesn't even matter - demo was not to make a call to real restaurant, it was just showing functionality being developed, they may have even put someone on scene to take a call, but decided to insist that demo call was absolutely regular one instead)
Anyway, I hope everybody is happy and not all worked up anymore, I was wrong on the internet, was put on my place and accepted that.
peace
Your post also was so definite instead of suggesting. Things do not know about usually you start with a little less direct, IMO.
They store billions of lines of code in a monorepo. If they don't have an organizational structure and automated testing tools to make sure they aren't having multiple teams of expensive engineers duplicate work, they might as well close up shop right now.
Is it some wierd Bay area thing that businesses don't identify themselves when they answer a call?
However, more likely I think they edited out the initial introduction to give the businesses privacy. They also probably told the businesses beforehand that there was a chance they would be calling in the future with bots to get around California 2 party laws on recording (or maybe they got approval afterwards although I'm not sure that's legal).
[1] https://www.theverge.com/2013/3/4/4063272/meet-starbucks-bar...
As long as the final product works as advertised, no one seems to much care.
https://www.theverge.com/2013/3/4/4063272/meet-starbucks-bar...
The truth is that they still make the majority of their profit from search, but need to look like they have something to back that up to keep the stock price up. Between that and Waymo it really felt like they don't. Android and the Chomebooks are promising as technologies, and I like they refinements they are offering, but the monetization strategy doesn't seem to be clear strong. It is definitely not as strong as Apple's ability to make profit from selling Macs and I-Phones...
One of the things I've decided to do these days when I find things that make no sense when I read them, is to figure out if the commenter had any pre-existing biases.
I guess it's nice to give great feedback when the work was great. I don't see why people sometimes want to obsessively find a problem that doesn't really change things.
But generally I totally agree with you. When the manager only makes positive comments and doesn't engage, the person is not being helpful at all.
Second recording at https://ai.googleblog.com/2018/05/duplex-ai-system-for-natur... has very clear background noise.
So probably the calls were faked, but so what? It is a glimpse into the future, it shows what this tech can do maybe not now but a couple of years in the future.
Is it dishonest? Yes, but then again Google is not the first company to put vaporware out. Microsoft did it first and that did not stop them to become a leader in the industry.
spoiler: FCC part was clever, but what fakery? Are you talking about the "golden path" or something else I missed after a quick read?
Internally, the criticism is brutal, because we want free-form, general, conversation abilities, and we don't consider the demo to be perfect.
But fake ? IMO, if the team wanted to fake a demo, they could had done that years ago when the project started.
But we are Google. We don't fake demos because we don't have to.
[edit: To add to what I said: If you think that a team at Google could fake something at this scale and have the face of the company back it at our most high-profile event of the year, just think of the aftermath internally. The code is available for all of us to study. The design docs are there for us to read. There were thousands of engineers that at least peeked at the codebase even on the same day of the demo.]
I tried to give a balanced viewpoint so that I don't project more than what has been accomplished, but I feel personally offended when I read we are faking demos, and I instinctively desire to defend to the best of my abilities and without revealing non-disclosed information.
I'm looking past your ``poor taste'' editorialism and I apologize if you feel that I offended you or singled you, or a part of the company, out.
I think part of this guideline applies, and following it should avoid disclosure, embarrassment, or being forced to speak on the defensive of an entire company (not a job that most developers are automatically good at).
> You probably know that our policy is to be extremely careful about disclosing confidential proprietary information. Consistent with that, you should also ensure your outside communications (including online and social media posts) do not disclose confidential proprietary information or represent (or otherwise give the impression) that you are speaking on behalf of Google unless you’re authorized to do so by the company. The same applies to communications with the press. Finally, check with your manager and Corporate Communications before accepting any public speaking engagement on behalf of the company. In general, before making any external communication or disclosure, you should consult our Employee Communications Policy and our Communications and Disclosure Policy.
While a compiler may block you from writing faulty code, the media will just take your faults, and then present them as truths coming from upper management.
Just take out of context or read the following with a different job role and see why these guidelines make sense:
> we are Google ... These kind of systems need 99% precision ... I feel it was full of tiny imperfections ... Internally, the criticism is brutal ... It seems that I am "attacked" primarily by fellow googlers ... There are a dozen variations of this question already for TGIF ... the team wanted to fake a demo, they could had done that years ago ... a team at Google could fake something at this scale and have the face of the company back it at our most high-profile event of the year ... Would volkswagen be able to do what they did ... I've been told that there were cases were the human would react by saying "no, you are not a robot, you are human!" when they were told that the caller was a bot
It seems that I am "attacked" primarily by fellow googlers, which speaks to my point: If this demo was fake, it would have been rightfully torn appart internally.
By the way, did you just copy-paste our internal policy on a public forum ?
I am not trying to imply you are against the policy, just that it isn't a good idea to make yourself an accessible target in a "witch hunt".
The media is clearly trying to kick up some shit. They know Duplex is hot, and so they try to find another angle/drama/controversy to continue the clicks-cycle. If they had anything of substance, then plenty of AI researchers would be lining up to be cited, warning against AI-hype and winters. The article would be called: "Google faked its Big A.I. Demo!". Now they are still on the prowl for anyone that will dignify them with a soundbite, be that on social media.
Notice how few Facebookers stepped up here on Hackernews, when Facebook was the target of a negative news cycle. There is just no winning, just a lesser of two evils: Take a temporary hit to your pride, or let the media and fellow Hackernews posters take everything you say as an official company statement, attacking you and your colleagues while you weren't even directly involved in the project and can do little to alleviate any concerns or lies.
My 2 cents: The demo was not faked. But of course the samples were cherry-picked to make for a good demo. Also, a large part of the negative coverage stems from irrational fear or misunderstanding of AI, futurism potential, and the first uncanny valley for natural conversation.
Irrational? No. At the heart of this demo is deception. After the deception comes "impressive tech" and all the rest.
Booking hair appointments is one thing, but we all know these systems will be babysitting our children, teaching them new things, and responding to their verbal prompts.
Emotional development in children is crucial for psychological health. FAKE synthetic emotion is not healthy, it's not cool.
Having "Googlers" at the top of the ethics pyramid for AI systems in our homes, is worth a healthy dose of fear and loathing. "We are Google. We don't need to fake demos [of our fake human voice]" is precisely why Google shouldn't be dictating the terms of AI standards around ethical concerns and communication disclosures.
This is about more than hair appointment bookings.
You seem to conflate this with another issue with the demo: It was so good that it seemed real, and you deem this to be deception/deceptive.
While I may share some of your concerns, I can't help but compare it to the rants against video games: unhealthy, fake social interaction. Often used by politicians without any scientific backing of their claims.
I do understand the current attraction from the general public to the unsurprising AI research going on at top labs. You don't need any relation to the field to muse about killer robot singularities and 2000 year old ethics philosophy, and no one will brand you a fool like they did to the people warning about earth-eating black holes at CERN.
You mention video games. In a video game, the interactions via voice chat, or text chat are person to person. I am not aware of any politicians calling that "fake". It's not related though, as online multiplayer gaming is a sub-set of a specific type of digital activity, whereas AI and bots and voice recognition is all-pervasive. It will be everywhere, and deserves scrutiny because you won't need to be a "gamer" to be exposed to this technology. IMHO it's vital we continuously examine the ethical concerns.
It’s not like there’s a conspiracy of silence between yourself and hundreds of other employees; more that hundreds of people all independently have over-inflated faith in the product and all independently cut corners and “cooked” the demo in various small ways. I can easily see that happening in an intense, secretive team, even if every individual’s intentions are basically good.
Anecdotally, I've been told that there were cases were the human would react by saying "no, you are not a robot, you are human!" when they were told that the caller was a bot, but I haven't been able to verify this.
The software might be good, better than what other teams would have produced, but I can't really tell that from a couple of carefully selected (and edited) recordings.
You mean pessimist? Or was that not a typo?
I suspect you'd be surprised what skeletons Google has in their closet.
Why do you think Google is so scared to answer journalists' questions, if you are confident in the veracity of the demo?
Again, if everything is above board here, why isn't Google answering questions? Perhaps pose the question at TGIF? If they have nothing to hide, why risk looking bad by not answering?
someone should reverse lookup this image[2], match it with bay area based restaurants and find the restaurant then
[1] https://ai.googleblog.com/2018/05/duplex-ai-system-for-natur... [2] https://3.bp.blogspot.com/-Arp_jhtS4F0/WvD7KzLvDRI/AAAAAAAAC...
Edit: It looks like Chinese/Korean restaurant from Image.
Unlike startups, it's not like Google's business depends on investors supporting lofty goals. There would seem to be no benefit to faking a demo like this.
Not revealing the business location is likely just because they consider their business partners to be business data that they don't want to give away to competitors. Clean auto could easily just be done via a simple noise filter, just for the sake of the demo. When you have a little noise in your ear, it's not bad. But when you need to broadcast sound to an entire stadium, you need to rebalance it. This story is a load of nonsense.
Thay supposedly made a call (won’t release proof) to a restaurant (that they won’t name) and talked to a receptionist (who didn’t mention the restaurant name) that didn’t ask what time the reservation was for. And you couldn’t hear the restaurant in the background.
The demo is really suspicious. They deserve to be called on it. For all we know that was a recording of a fake training/test call with a Google employee.
If they manipulated the audio in some way (cut out an intro, filtered out noise, etc) they just have to say so.
Google deserves this kind of scrutiny. They’re a MASSIVE company, they should be able to handle these kind of questions about new products.
Especially those that are supposed to be released in the next few months.
If they don't need to impress anybody, why would they even have a demo at all?
You could say the exact same thing about Microsoft and the Milo demo.
Reminder that Duplex explicitly uses Concatenative Text-to-Speech - i.e. they record humans saying phrases, and just play those soundbites back where appropriate. Sort of like a chess AI storing a dictionary of opening moves.
If they have to call, I suspect that it isn't 100% without human intervention. I am reminded of "Samantha West" the telemarketer "bot" that will robocall people and respond to people. It turns out it isn't a bot at all but someone pushing buttons on a soundboard to play the appropriate prerecorded response. http://newsfeed.time.com/2013/12/17/robot-telemarketer-saman...
It would be pretty easy for the small number of times that google can't make a reservation online for you to pay some people in a call center to do this.
It's probably just a proof of concept that doesn't work very well. They probably just played back one of the few attempts that it worked very well.
I even remember, when reading the article, a lot of caution in overestimating the state of the technology. So, given their disclaimer, I'm giving them the benefit of the doubt; and I'm thinking that everyone else overreacted because they don't understand software development.
I guess they could have the bot call Dan Primack at Axios and clear it up...
The minute someone else used it, the illusion was shot. It's really easy to make a chatbot work when you keep it on the rails - even when you're not intending too.
There's the rub, they did make that exact claim...
True - in fact the iPhone actually does transcription on-device, AFAIK the cloud loop is for validation and to get answers.
Dont believe me? Put your iphone in airplane mode and use the dictation button on your keyboard!
They clearly portrayed it as a real, unedited call. If they were dishonest, of course that matters. Arguably ethics don't matter as much as the underlying tech, I suppose. But it still says something about the individuals involved.
They seem incredibly dodgy for something they announced openly in front of thousands of people.
It doesn't hurt them to not answer these questions, and they definitely don't want to answer some of them, so why would they?
And that's likely why, weirdly, no business identifies itself in the audio. They don't want to admit to ANY editing because it would open up MORE questions.
> . “What you’re going to hear is the Google assistant actually calling a real salon to schedule an appointment for you,” Pichai told the audience. “Let’s listen.”
I think this would require that a grant of permission is transferable.
- Employee grants permission to employer to record as term of employment.
- Employer grants Google blanket permission to record calls.
Do you know if it works that way?
Also, any business that is recording its employees must notify customers. This would be another thing they would have had to edit out of the call.
> Also, any business that is recording its employees must notify customers.
Google did the recording, so that doesn't apply. Even if it did, it would make sense for Google to edit out the "Your call may be recorded for quality recording purposes," in the demo.
I believe if this demo were real, it was tested and cherry picked from a very particular environment
Tacotron (Mar. 2017): https://arxiv.org/abs/1703.10135
Parallel WaveNet (Nov. 2017): https://arxiv.org/abs/1711.10433
Tacotron again (Mar 2018): https://arxiv.org/abs/1803.09017
Tacotron 2 audio samples: https://google.github.io/tacotron/publications/global_style_...
BTW, I have no particular reason to trust (nor distrust) anything Google says or does.
Surely if they had that computing power they would just be breaking crypto and stealing money all day long?