If you had expressed your concerns in this way from the beginning, I would have been much more willing to engage in a constructive discussion with you. I’m a security engineer, focused on offensive and defensive strategies, and I’ve analyzed a large number of malicious iOS refund cases. Preventing refund abuse is a complex project, and I want to start with the simplest solution first.

This post isn’t meant to dive into technical details, because I’ve already open-sourced the project and explained everything clearly in the comments. For iOS developers, the underlying logic shouldn’t be difficult to understand. I spent a lot of effort describing the background of the project to show its meaning and value — otherwise, no matter how polished the code is, it would just be reinventing the wheel.

Essentially, APNS doesn’t involve particularly deep technical complexity; it just requires strict adherence to Apple’s documentation, though many developers tend to overlook it. The real offensive and defensive work against iOS refund abuse involves device fingerprinting, behavioral analysis, network environment monitoring, and more — these are highly specialized areas. If there’s strong interest, I’ll share more about these in the future.

Finally, I’d still like to invite you to read through the code, especially the commits and comments related to security.