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

Going from what the author says, Apple have asked that they try to settle it through the third-party developer first before getting Apple involved. But:

> Unfortunately since the developer is acting maliciously and mostly likely without any intention of ever responding to us, we have no way of settling this matter through that channel.

Basically, it sounds like they just decided -- without even trying -- that it wouldn't work and that they want Apple to do all the hard work for them.

I mean, I kind of understand if you're giving Apple a 30% cut of all your revenue that you'd expect something in return, but this sounds like a bit of an overreaction from the developer to me.



A 30% cut is a rip-off and the least they can do is to solve issues such as these.

If I were in this developer's shoes, I would send Apple a DMCA request. After which, if Apple fails to solve the issue, I'd sue Apple.


Yeah, I agree this does indeed look like exactly the sort of situation the DMCA was designed for and that's certainly the route I'd be looking at taking.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: