These Beeper folk sound a bit entitled. As was repeatedly mentioned in the other thread [1], building production applications on top of an undocumented and unsupported (in terms of backwards compatability, etc) API is a nightmare that should be avoided. Apple has every right to change their API, if they do Beeper will go down, and Beeper will blame Apple. I understand Apple's incentives to not want to be in this situ…
If the only thing Beeper does is continue to make Apple look anti-competitive, they've succeeded as far as I'm concerned. I'm deep into the Apple ecosystem and don't see myself getting out anytime soon. But I think their stance on iMessage sucks, even while understanding the strategic reasons they're doing it. I don't see this as "leeching off an undocumented API" as much as demonstrating that iMessage is already in…
The market simply chosing a preference is not anti-competive. iPhone and iMessage is able to compete on it's own merits without competition being artificially hindered.