We've found a solution to stabilize the iMessage situation for Beeper Cloud and Mini. It works well, and, in our testing, is very reliable. The only downside is that the solution requires you to have access to a Mac computer, or have a friend on Beeper with a Mac.

Here's the backstory. When you connect iMessage on Beeper, we need to send identification information called ‘registration data’ from a real Mac. We have, up until now, we been using our own fleet of Mac servers to provide this. Unfortunately, this has proven to be an easy target for Apple because thousands of Beeper users were using the same registration data.

Registration data is used only to indicate that a Mac is available during registration. The Mac in no way is given any access to your account, or your messages.

Tomorrow, we'll publish an update for Beeper Cloud (Mac version) that generates unique registration data just for you. This 1:1 mapping of registration data to individual user—in our testing—makes the connection very reliable. If you use Beeper Mini, you can use your Mac registration data with it as well, and Beeper Mini will start to work again. Beeper needs to periodically regenerate this data even after you've connected, roughly once per week or month, so the Mac needs to switched on regularly.

If you do not have access to a Mac computer, but have a friend on Beeper with a Mac, you can ask them if you can use their registration data. In our testing, 10-20 iMessage users can safely use the same registration data.

We'll also be open sourcing our full iMessage bridge, as well as the Mac code that generates registration data. If you prefer, you can choose to self-host or inspect our code.

•••

⚠️ Please note that this update restores chatting on iMessage with your AppleID email, if you do not currently have a iPhone number tied to your account.