1,077 karma · joined September 17, 2010
1. To have an ImageNet moment, we should have an ImageNet. LibriSpeech doesn't cut it. We should have an equivalent SpeechNet. Problem is visual language is one, while speech languages are many. So we should have an ImageNet for every language? And train for every language?
2. What is an ImageNet moment? Personally, though ImageNet has contributed a lot, similar to speech and NLP, even vision applications have promised more and delivered less in real world scenarios. And just like speech and NLP, only the big boys actually provide solutions in vision which shows in vision also they have access to better data which they don't share.
- Manually scan through a couple of hours of data and setup a human baseline.
- Run standard algorithms and find their accuracy.
- Find errors in the model and analyze why the errors are happening. Is the model classifying some other object as a supervisor? Is the model not classifying the supervisor in certain lighting conditions or scenarios.
- Retrain the model with the failure scenarios so that it learns.
That said, I have a small problem with the examples presented to say that already machines understand us :)
The article says 'For example, when I tell Siri “Call Carol” and it dials the correct number, you will have a hard time convincing me that Siri did not understand my request"
Let me try to take a shot at trying to explain that Siri did not "understand" your request.
Siri was waiting for a command and executed the best command that matched. Which is, make a phone call.
It did not understand what you meant because it did not take the whole environment into consideration. What if Carol was just in the other room. A human would maybe just shout "hey Carol, Thomas is asking you to come", instead of making a phone call.
If listening to a request and executing a command is understanding, then computers have been understanding us for a long time. Even without the latest advances in AI.
The death of the phone call has been heralded for many years now. I am guessing it's gonna stick on for some more time, at least for business use cases.
1. Surprisingly, the Calljoy website does not have a call in number or a demo number. This is supposed to be a disruptive technology, put a demo number that people can call in and test.
2. The Google brand is not there anywhere on the Calljoy website(except at the very bottom).
3. Rather than release a free beta product, which is the norm, Google has launched a paid commercial product.
4. Haven't tested the call quality yet. I think they maybe launching this on the Google voice platform.
5. Not sure why it should be a separate product, would have made more sense as a Gsuite add on.
6. Businesses need support. The success of this product will depend on the 24/7 support that Google can provide to business owners.
Note:I am a co founder of KOOKOO.
[1]https://medium.com/@nutanc/the-final-and-exhaustive-proof-of...
See you all at Signal Conference :)
But how would I present that on the website? Any ideas? Thanks!
So yeah, pricing is just one very small factor. It is a factor, but only after all other factors have been taken care of :)
This was built using KooKoo, the Twilio for India and is more of an IVR rather than SMS as India is a voice friendly country, and who does not like to hear the invite in the groom's own voice :)
Its got options for directions etc too, people always seem to call to know the directions to marriage hall :)
[1] http://getkookoo.com/getting-saas-pricing-right-pricing-clou...
Intercom for chat
And we dogfood getkookoo for phone support