4 ms·
If you take a look at their How it Works post [1] this is not an entirety client side implementation, so there would presumably be a small number of IPs that wo
by pxeboot 3y ago
If you take a look at their How it Works post [1] this is not an entirety client side implementation, so there would presumably be a small number of IPs that would need to be blocked.
[1] https://blog.beeper.com/p/how-beeper-mini-works https://blog.beeper.com/p/how-beeper-mini-works
- zxt_tzx 3y agoAre you referring to the step where Beeper's servers make a persistent connection with Apple's APN service to listen to new messages ? So your point is Apple can presumably distinguish between an actual iOS connection and Beeper's connection by looking at "how many connections per IP"? Still seems prone to false positives to me, unless there is something else I missed. (Upon re-reading the post, I realized that the phone number registration is actually done by Apple. Wonder if this might provide another basis to block Beeper, i.e. all this SMS infrastructure is not cheap to maintain and Beeper's integration is arguably using it in an "unauthorized" way.)
- pxeboot 3y agoYes. An Apple sysadmin could just install Beeper, watch what IP their APN requests are coming from and block it. Then repeat the process occasionally. They don't need to break it completely. If Beeper is unreliable, nobody is going to pay for it.
- rezonant 3y agoIn that very article they mention you can turn BPNs off, it is just used to listen to APNs when the app is not running. If that's what they blocked, Beeper Mini would still work while the app is running, or at least when that setting is turned off.