[redwall_hp]

If any company with a restricted service exposed to the internet found someone illegally gaining access by spoofing device IDs or API keys, the engineers who noticed would immediately shut down access and inform management, so they can run it up the chain to legal. There need be no other motivation beyond preventing illegal access to a computer system.

I doubt Beeper Mini is on the radar of anyone high up at Apple. Some engineering team responsible for the services that back iMessage is just spotting and dealing with one of probably many malicious actors.

RCS support has also already been announced by Apple for 2024.

[everforward]

This is simply not true. Frankly, my first instinct would be to let it go if they're not causing issues. I certainly wouldn't start swinging the ban hammer around without knowing that the hell the traffic is.

It could be a bug in our client code, and I could be cutting off paying customers. It could be some weird and/or poorly written software by a customer. It could be some bizarre WAN accelerator issue at some giant company with real devices.

I would presume that at least someone at Apple knows that the traffic is from Beeper, and what Beeper is. I would expect that it hit the desk of a mid-tier Director at least (would you or your manager be comfortable implementing heuristic blocking without telling a director?).

It still may not be a strategic decision, but I wouldn't assume that decision makers aren't aware of what's going on.