2 ms·
Beeper (before mini) was working with iMessage by relaying messages from VMs, probably one VM for x users. November 15 ( or a bit earlier, but communicated on
by bluesign 3y ago
Beeper (before mini) was working with iMessage by relaying messages from VMs, probably one VM for x users.
November 15 ( or a bit earlier, but communicated on that date) they switched to new iMessage bridge, where Beeper client directly communicated with Apple servers.
Beginning of December they launched Beeper Mini.
My theory is: their move to move from VM relay to new bridge caused problems, but VM relay was not sustainable with growth. Maybe Apple started to require re-validation, maybe it was like this to begin with.
So eventually they rolled the dice with Beeper Mini and in the end existing Beeper users have to provide a Mac for validation.
I think this will be good for Beeper, as I guess slowly they will retire iMessage totally. And focus on the on the other bridges. They are a bit more sustainable now.