4 ms·
I'm guessing the binary they use from Apple (IMDAppleServices) to generate part of the registration information probably adds metadata to the "validation blob"
by nickorlow 3y ago
I'm guessing the binary they use from Apple (IMDAppleServices) to generate part of the registration information probably adds metadata to the "validation blob" that gets sent to apple when registering beeper mini as an iMessage device.
If the metadata includes the OS version, Apple probably blacklisted any new devices registered in the past few days with validation blobs generated from that binary.
(The binary was sourced from OS X 10.8 which is ~11 years old now)
- threeseed 3y agoMy suspicion is this is going to be a cat-mouse situation for a while. Apple would've found some easy way to identify these users and Beeper will likely release a patch to fix it.
- nickorlow 3y agoAgreed. I think Apple wins easily though. If they can break it once a month for a day or two, I think that makes it inconvenient for beeper mini users. Maybe not though, who knows
- winterqt 3y agoIt doesn't look like that binary is used for Beeper Mini, unlike pypush: https://blog.beeper.com/p/how-beeper-mini-works https://blog.beeper.com/p/how-beeper-mini-works
- nickorlow 3y agoI wouldn't be surprised if whatever they reverse engineered from the binary had similar behavior