can the server-side be a watson like computer cluster ? just curious...
Cracking Siri
71–80 of 105 posts
Re: Cracking Siri
#72I wonder how Apple is taking all of this? Is Applidium risking their developer license?
I would doubt it - there's nothing illegal about reverse-engineering a protocol.
Re: Cracking Siri
#73I didn't see anything in this article that mentions that the natural language understanding is done in the cloud. May be I am missing something, but I don't understand why everyone is jumping to the conclusion that the NLU is also done in the cloud and downvoting other's comments that said so.
From what I've seen, Siri sends compressed audio to the cloud which translates that to text. What happens to the text and how does that translate to action? Where is this being handled? Is there any proof that this is done in the cloud?
Re: Cracking Siri
#74No one is at all concerned that this is a hack? I know it's interesting stuff, but I'm curious what "rights" Applidium have in publishing this information. With this information, (if I'm not wrong) it wouldn't take long to simply DDoS Siri... Or port Siri to Android (effectively stealing IP). (I have no bias either way, just pointing out, if someone figured out how to reverse engineer dropbox, so you could use their…
Hacks are admired here, not condemned. Reverse engineering should always be allowed. This information doesn't make it possible to DDoS Siri or port it to Android as each request requires a unique iPhone ID; Apple can easily filter out unauthorized requests.
Maybe You admire them. But I don't. Are we going to hack/crack each other's apache servers from now on? Or are we going to build businesses that will solve problems for everyone?
Re: Cracking Siri
#75The question that springs to my mind is not 'how can I play with this?' but 'Are Apple bringing Siri to the desktop?', seeing as it appears there's nothing specific to the 4S hardware in how this works. I'd quite like to be able to add calendar entries or tweet without moving to another application.
Apple has clearly had a difficult time keeping up with early demand for Siri services as it is. I think keeping it limited to the 4S looks a lot more like a operational necessity at this time. Given that, If Siri appears on the Mac between major OS releases, I imagine it might be only for new hardware (i.e. a Macbook Air with an exterior Siri button and purple LED) at first as well. Eventually (once they can scale Si…
What makes you think thy've had a tough time scaling with early demand? I'd think that this scales horizontally pretty well, given that each request is largely stateless and there's no interaction between users.
Re: Cracking Siri
#76I wonder how Apple is taking all of this? Is Applidium risking their developer license?
I would doubt it - there's nothing illegal about reverse-engineering a protocol.
Sure, but there's nothing illegal about Apple kicking someone out of the App Store on a whim either.
Doesn't matter if you are breaking the law or not, plenty of legal apps get rejected. Apple sets their own terms outside of US law.
Re: Cracking Siri
#77Earlier quoted context omitted.
"As a result, we are able to use Siri’s recognition engine from any device. Yes, that means anyone could now write an Android app that uses the real Siri!" Are they just lying then? There demo said they got siri to work with no iphone involved (in the end). Also... DDoS would still be effective, no? (the server still has to 'filter') > Hacks are admired here You sure about that? A lot of China-bashing happens here ba…
They're not lying. Anyone could write an Android app that uses Siri, but it would require the ID from an iPhone to work, so distributing it would be problematic.
Yeah, unless someone happened to have a huge cache of real device IDs...
http://www.readwriteweb.com/archives/dear_iphone_users_your_...
(I hope the app store magical-vetting-code is smart enough to ensure the new hit app "Somewhat Annoyed Birds" isn't capable of fishing around in the phone for the Siri ID and sending it back to the developers website along with the high score you just got...)
Re: Cracking Siri
#78Earlier quoted context omitted.
Since it's HTTPS, those proxies can't see the traffic anyway, so as long as they used SSL on port 443, they could use any protocol on top.
They potentially can; commercial firewalls can man-in-the-middle HTTPS traffic with a locally signed and organization-computer-trusted SSL certificate.
How does that work? I thought all verification of certificates was done in the browser...
Re: Cracking Siri
#79Earlier quoted context omitted.
I would doubt it - there's nothing illegal about reverse-engineering a protocol.
Sure, but there's nothing illegal about Apple kicking someone out of the App Store on a whim either. Doesn't matter if you are breaking the law or not, plenty of legal apps get rejected. Apple sets their own terms outside of US law.
Apple has to comply with its contract just as the developers do. I did just check the agreement and either party can terminate with 30 days' notice for any or no reason, so they could theoretically terminate.
Given this is completely out of the scope of the App Store or even the SDK (contrast with the security researcher who got unapproved code executing), however, I don't imagine Apple will feel the need to terminate. I guess we'll just have to wait and see.
Re: Cracking Siri
#80Earlier quoted context omitted.
They potentially can; commercial firewalls can man-in-the-middle HTTPS traffic with a locally signed and organization-computer-trusted SSL certificate.
How does that work? I thought all verification of certificates was done in the browser...
IT installs the corporate MITM certificate on all of their computers so the browsers accept them as valid.