Apple partly halts Beeper's iMessage app again, suggesting a long fight ahead

Re:Apple partly halts Beeper's iMessage app again, suggestin... by saintfire on Thursday December 14, 2023 @11:37PM (#38651035)

AFAIK, and I could be wrong, beeper mini registers a new HWID with apple for each phone. Which is why they thought it was unpatchable, at first, as they would need to determine which phone is in fact an iPhone.

[ Parent | on HN ]

Re:Apple partly halts Beeper's iMessage app again, suggestin... by nneonneo on Thursday December 14, 2023 @11:51PM (#38651103)

There's much more to the validation protocol than just HWID/serial. See https://github.com/JJTech0130/pypush/blob/main/emulated/data... for a list of the data that is pulled from the platform and used for validation. I would assume that Beeper registrations either use data from a pool of real devices, or made-up data that Apple might "permit" (because hackintoshes) but can definitely detect and block at any time.

[ Parent | on HN ]

Re:Apple partly halts Beeper's iMessage app again, suggestin... by MuffinFlavored on Friday December 15, 2023 @12:44PM (#38656535)

> use data from a pool of real devices

This feels super against terms of services. Taking a paying Apple user's hardware ID and using it for a non-paying user?

Also, I thought you had to tie/pair hardware ID to Apple ID.

[ Parent | on HN ]