![]() ![]() Apple’s iMessage infrastructure handles billions of messages per day - trillions per year - with unlimited full-resolution image and video attachments. It requires servers (both for delivering messages and for the exchange of encryption keys), bandwidth, content moderation for spammers, and more. iMessage is much more than a protocol - it’s a service. It’s being talked about as though iMessage is merely a format or protocol, and that Beeper reverse-engineering the protocol is akin to, say, reverse engineering a document file format. I think the fundamental misunderstanding is over just what iMessage is. The iMessage LoungeĪny take on this entire saga that treats Apple’s stance or actions as controversial, in the least, (see below for more on that), is deeply misguided. These hoops will relegate Beeper Mini to relative obscurity, even if Apple takes no further action to counter it. Beeper needs to periodically regenerate this data evenĪfter you’ve connected, roughly once per week or month, so the Mac Registration data with it as well, and Beeper Mini will start to If you use Beeper Mini, you can use your Mac This 1:1 mapping of registrationĭata to individual user, in our testing, makes the connection very Users were using the same registration data.īeeper Cloud (Mac version) and old iPhones can now generate unique Proven to be an easy target for Apple because thousands of Beeper We have, up until now, used our ownįleet of Mac servers to provide this. Need to send identification information called “registration data”įrom a real Mac computer. ![]() When you sign in to iMessage on Beeper, we Beeper’s own explanation for this rigmarole: Only with a jailbroken iPhone can you register your Android device’s phone number as an iMessage ID if you’re using or borrowing a Mac to generate a registration key, Beeper Mini will only work using an Apple ID account, with an email address as your ID. Their current “solution” requires Beeper Mini users to either (a) own - or, I swear, rent - an old iPhone (6, 6S, 7, 8, or X), jailbreak that phone, install Beeper’s software on the old jailbroken iPhone, and then leave that old jailbroken phone powered on and connected to Wi-Fi continuously (b) have Beeper Cloud - their desktop app - installed and running on a Mac or (c) run a command-line tool to, on a weekly basis, regenerate a new iMessage registration code. We do not have anyĬurrent plans to respond if this solution is knocked offline. Something that Apple can tolerate existing. ![]() With our latest software release, we believe we’ve created Is that we can’t win a cat-and-mouse game with the largest company As much as we want to fight for what weīelieve is a fantastic product that really should exist, the truth ![]() Or maybe better put, half threw in the towel on their half-working app:Įach time that Beeper Mini goes “down” or is made to be unreliableĭue to interference by Apple, Beeper’s credibility takes a hit. So Beeper effectively threw in the towel. Regardless of details, half-working interop for a messaging service might as well be not working at all. I’m guessing that behind the scenes, after that initial message from an actual Apple device to a Beeper client would go through, Apple would determine that the Beeper device was illegitimate and blacklist the device ID. After that, messages sent from an iMessage user on an Apple device to a user running Beeper Mini would silently fail. What I had been seeing during the week before Christmas is that Beeper Mini half-worked: messages from Beeper Mini on Android would go through to Messages on an Apple device, but from any Apple device, you could get one message through to an Android device running Beeper, but only one. Long story short, they’ve been playing - and no surprise, losing - the cat-and-mouse game with Apple. There’s a lot to catch up on since last I wrote about Beeper. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |