Mark replied to a comment along these exact lines. Quote below;
Mark Zuckerberg: That's the thing about AI. It's sort of like magic. We only call things AI that we don't understand yet. Once we understand something, it's just math.
But if you'd asked someone 30 years if a computer system that you could talk to, that could see your friends and let them in, that could learn your listening habits and figure out when to make you toast, if that was intelligent, then most people would have said that would be AI. Now that we know how to do it, it's just math.
Writers, at least, understood that there were different "flavors" of artificial intelligence. I have a funny feeling that at least science fiction enthusiasts also knew that AI would be separated in this way if it ever came to fruition.
One thing I was always wondering is why it took as long as ST:VOY to see transporters being used as a way to deliver armed torpedoes directly into the target.
In later seasons of Stargate SG-1 they sidestepped this problem cleverly - when humans received transporter technology from a more advanced species, they had non-overridable safeguards[0] (and an inspector on-board) preventing them from being used as a weapons delivery platform.
[0] - which, in the best fashion of this series, were overridden several times anyway. A lesson for those who think that if something is banned, it won't be used.
The Culture novels managed to convince me that a story about true AI needs to not only look a little different, but fundamentally different. Not least, answering "Why still humans around?"
It's a very long read, but it will give you a much better overview of AI and the different "calibres" than I could possibly try to in a HN comment.
What Mark has used here is "Artificial Narrow Intelligence (ANI)", the first of three levels/calibres of AI. Level 2 is "Artificial General Intelligence (AGI)", otherwise known as "Human Level AI". And level 3 is "Artificial Superintelligence (ASI)" which is "“an intellect that is much smarter than the best human brains in practically every field, including scientific creativity, general wisdom and social skills.” [Quote: Nick Bostrom].
Final word: I follow this stuff closely and read the research articles, and what we currently have is really great, but it's still just pulling the wool over your eyes. These techniques and algorithms trick you into thinking they are intelligent when in fact they are anything but. What we have now is a parlour trick in comparison to what the brain is doing. When true AI actually comes along, no one will doubt it.
If we can build systems that can fool us into thinking their intelligent (which I will agree that outside of limited scopes we have not), then we built intelligence.
What I see we have now is lots of bricks - often overly problem-specific (and it's important to stress this; a lot of things that get called "AI" in the news is really lots of compute thrown at super specific heuristics). To call it AI, we still need to connect them together into a system that can use those components to learn and solve problems it didn't see before, without bricking itself in the process.
That's a good turn of phrase, because it speaks to the real rub between algorithmic insufficiency and hardware insufficiency. From my reading, it seems fair to say that "strong general AI" will require some product of both to be realized and that our current hardware capabilities likely fall short of the minimum requirement (even with optimal algorithms).
Were they imagining exascale computing when Quicksort was dreamed up in 1959? No. But does that make it any less important?
As someone who was into programming and electronics in the eighties, I also feel a need to object whenever people say things like “we thought it was AI until we could make a computer do it, and now it’s just math” (paraphrasing).
We (those of us interested in the subject back then) had a pretty good idea about what would be possible in the future (because of faster machines and more storage) and what would not be possible in the future (unless a breakthrough was made in understanding intelligence).
Now, I do think we underestimated how fast things have developed, and especially the resources people have access today via the internet, but none of what I have seen today would have been classified as AI by myself back in the eighties.
[1] https://en.wikipedia.org/wiki/Facial_recognition_system#Hist...
>[mass noun] The theory and development of computer systems able to perform tasks normally requiring human intelligence, such as visual perception, speech recognition, decision-making, and translation between languages.
So obviously by that speech and Zucks type of face recognition are AI. I note the '68 system was hybrid and required humans to measure the faces and enter data for where the features are so it was more analysing numbers.
There was actually speech recognition software in the 80s but it used a neural network approach rather than if statements and didn't work terribly well https://www.wired.com/2013/11/tech-time-warp-of-the-week-ibm...
Human level thinking type AI is obviously still to come.
Source: around 2006 I made a Star Trek-like music control system with Microsoft Speech API and an electret microphone hand-soldered to a long cable and an audio jack. With ~30 minutes of training on my voice it worked as reliably in noisy environment as Google works for me now.
An AI doesn't need to do something it wasn't programmed for or understand what it's doing to count as one.
The construction metaphor is full of great wisdom to be gleaned as software developers. And I'm not just saying that in hopes I didn't waste all those hours watching History Channel documentaries. :-D
For me a well designed house is actually, you know, about the design. And whilst the construction is important due to standards it is largely irrelevant.
The analogy to software is apt. Well designed, well architected software is so important. Anyone can write syntactically proper code. Far harder to design a system that has just the right amount of extensibility, performance, elegance etc to meet the requirements without going over the top.
Engineering isn't really a place for more than very limited creativity. That place is R&D.
(i miss "free time to hack")
> I'd learn a lot about the state of AI this year, but I didn't realize I would also learn so much about what it's like to be an engineer at Facebook. And it's impressive.
> My experience of ramping up in the Facebook codebase is probably pretty similar to what most new engineers here go through. I was consistently impressed by how well organized our code is, and how easy it was to find what you're looking for -- whether it's related to face recognition, speech recognition, the Messenger Bot Framework [messenger.com/platform] or iOS development...
The rest of that paragraph goes through all the other developer tools you can sign up for in the facebook ecosystem, including convenient links. Then it continues:
> One of our values is "move fast". That means you should be able to come here and build an app faster than you can anywhere else, including on your own. You should be able to come here and use our infra and AI tools to build things it would take you a long time to build on your own.
It was a neat project, not denying that, but there is no free lunch. The CEO of a Fortune 500 does not write up a 5-10 min read without plugging his interests.
You can enjoy what he's doing, but also recognize what it is.
If a Google exec wrote this post, it would be about how amazing a Google product was as a solution to the problem, and that would be the end of it. But here's Mark saying "you know what, Messenger is great but I needed more". And maybe that could turn into some pretty big advice for his Messenger team on what to add next, but he seemed to be pointing out where the industry (including his own company) could do better.
I see it more as R&D than marketing, personally. His personal experiments may likely hint at new directions in which he wants to take his company. Depending on how you view Facebook, this could be terrifying or exciting.
One way I see it is: Facebook knows a lot about your (online) social interactions. Home-based AI would need to know a lot about your private behaviors and preferences. If they marry those two worlds, that's a heck of a lot of behavioral information to have. Google has a big lead in this area already, so if Facebook goes this direction too, it would be an interesting to see how it plays out.
It's not creating. It's just copy+pasting and glueing.
The actual creation of these systems took decades of research.
Jarvis in my house uses sensors, actuators, lights, switches, etc - but mine is not AI. It only does what I tell it how to do. I'm pretty happy with the results, but it can't learn a thing.
The latest thing I "taught" my Jarvis to do is stream the security camera to the TV with a voice command. Now if I only had time to look into how to tell it to stop...
[1]: http://webdocs.cs.ualberta.ca/~sutton/book/11/node3.html
The same can't really be said of AI in most other contexts, where the goalposts continually seem to move to whatever is currently just beyond our reach.
I wonder if you could open his door with an A4 printout of his face. That's the sort of thing I'd worry about creating this system.
Edit: Forgive me HN, it looks like a lot of people have wondered this. I only commented so high up because I commented before reading all the comments! Go upvote the more creative/indepth versions of this question rather than this one :)
Now, do facial recognition with the depth component. "Oh look, paper. How quaint... NOPE!"
You could also log all people coming by with a known-unknown axis. You could train the system so that all they need do is look at the door, and they have the appropriate access they need. And it could also, instead, default in a "pass through to app for user to decide".
Don't think of this as a huge monolithic system... But instead of dozens of component parts that can work together. Then, the problem is certainly tractable. And then adding things like Google-Now, Alexa, Siri, and similar is no longer damn near impossible.
I particularly like Node-Red for this very project. It is javasript, however the big positive side effect is easy implementation with all sorts of nodejs APIs.
I already wrote a system that can take new facial inputs, classify you as "new user", and put your data in a database. All you need do is go up to the door. I can easily view the timecode and enter your details (name, phone#, email) at a later date.
source: https://github.com/jwcrawley/uWho
news article about it: http://hackaday.com/2015/03/04/face-recognition-for-your-nex...
"Print picture" to
"Compute Sfm 3d object from thousands of photos, and have access to a 3d printer that large that can print human-sized heads, and paint it appropriately in the correct color-space as to trigger the right facial recognition"
It's then trivial to add a feature of 'Blink' and 'Smile'. We have public, free haar and lbp cascades for those. It would be a few lines to add in a check that requests those 2 actions.
"Then you have to print an articulated skull and musculature that activate the appropriate smile/blink responses, with the correct coloring across the face."
And then hope that the video feed of the disjoined head trying to pass as human isn't just sent to the butler or a family member for "quality control"....
Also, even in US suburbia, smashing the window is likely going to trigger a burglar alarm and get the police called to the location, whereas bypassing the face recognition system will not.
[1] For a non billionaire house: thinner concrete walls ending in broken glass or decorative-yet-functional metal barbs, outer wall shared by a 10-20 homes neighborhood.
The building blocks, though, very much fit classic definitions of AI: face recognition, speech recognition, natural language parsing.
But no, its not Jarvis. Yet.
The bar for "AI" (as distinct from "Jarvis-level AI") isn't high. Heck, video games have had "AIs" since the 1950s: https://en.wikipedia.org/wiki/Artificial_intelligence_(video... Not sure if everyone agrees with that definition, but's it the one in common use.
If so, then Machine Learning is just predicting the next possible result using the statistical probability of previously studied data, and could not qualify as AI either.
AI is being broken down in to so many parts, some that are invisible to us, that: either we abuse it to the point of over simplification, reclassify it as common sense, and redraw the finish line of where AI starts; OR we start calling everything we do a version of AI from computers turning off the lights to balancing the controls in the first Apollo missions.
(And world domination. The next step for the AI, obviously)
If you're in a position to. It sounds like he plugged into Facebook's face recognition, for example, and I don't think that's available as an API request ('is this one of my friends')?
Add enough complicated if statements and you've got a rough definition of a human!
1. Connect his home devices (lights, thermostat, doors, music player, TV, CCTV etc) to his computer, so he can turn them on and off from it and in general automate his house from his PC.
2. Add an NLP component to his computer, so he could text instructions to it and it would apply the correct automation task. This can learn preferences too and be told about mistakes so it does better in the future.
3. Add face recognition, so it can recognise people at his door and automatically open it if they are expected.
4. Add speech recognition, by creating an app for the phone that is constantly on and listening for his voice. This is then converted to automation tasks again.
All in all, an interesting way to spend 100 hours. Calling it AI is a bit of a stretch though; this is basically linking up a bunch of in-accurate sensory parsers, coupled with some limited machine learning, connected to a bunch of if statements. Still a long way off of Jarvis, who is basically a genius by human standards!