News for hackers. Stuff that matters.
Re:Google Duplex: An AI System for Accomplishing Real World ... by smadge on Wednesday May 09, 2018 @01:03AM (#17027505)
In a sense you are correct, but remember that Duplex only works because it is limited to a very strict well specified domain: scheduling for restaraunts and hair salons. That is, Duplex only works because there already is a de facto specification for these transactions. It requires a lot less effort overall to just formally specify this de facto standard and deploy it once and for all, but of course a top down approach rarely works. This actually reminds me of the failure of the industry to adopt semantic web technologies. Many organizations are providing the same services and could easily adopt a common “API.”
Re:Google Duplex: An AI System for Accomplishing Real World ... by TeMPOraL on Wednesday May 09, 2018 @08:39AM (#17029316)
> Many organizations are providing the same services and could easily adopt a common “API.”

It's not in the interest of those organizations to adopt a common API. Everyone wants to suck in data and be the platform; nobody wants to give data away.

Re:Google Duplex: An AI System for Accomplishing Real World ... by freyir on Thursday May 10, 2018 @08:54PM (#17044200)
But that's the reason why Duplex is interesting, and why there's a grain of truth in what ZainRiz is saying:

Humans have settled on a de facto API for scheduling appointments. It uses the telephone as its interface, speech as its medium, and Duplex is exploiting it.

Re:Google Duplex: An AI System for Accomplishing Real World ... by Piskvorrr on Thursday May 10, 2018 @07:01AM (#17037813)
...but Google is one of the giants that could pull that off and become The Platform.
Re:Google Duplex: An AI System for Accomplishing Real World ... by ZainRiz on Wednesday May 09, 2018 @03:31PM (#17033096)
You first need "ye old barber shop" and "big corp barber shop" to all agree on what this common API should be. That's the old standards proliferation problem https://xkcd.com/927/

Which is what makes it very hard to define a new common API

However, they all already agree on the standard for natural language communication (in the context of a strict, well defined domain). That's the pre-existing common API which Duplex is using