Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yeah, I am not expecting this to be a protracted game of cat and mouse. Apple will just sue them in the end; that'll put a REAL quick stop to this.

I wish things had more interoperability, but Apple is under no obligation to implement it or be okay with it. And honestly, I believe them when they say that this is a security/privacy risk; even if it does serve their anticompetitive tendencies.



Tech journalists have noted that this kind of reverse engineering for the purpose of interoperability is specifically covered (allowed) by applicable laws. I’m not well versed in the related laws, but it at least seems on the surface that lawsuits may not be the end here.

If it’s a security issue, that’s on Apple’s architecture. They can cat and mouse this, but the more times they catch the mouse, the worse this looks for Apple because it effectively means that iMessage was never secure to begin with. Only time will tell how effectively they can address this.


And what if Beeper open sources their client? How is Apple going to stop that?


Sue them on what grounds?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: