Earlier quoted context omitted.
Yeah, not the point. The point is to prove that it's possible and relatively simple, and the only reason Apple operates this way is to lock people into the ecosystem.
Running the iMessage service for a billion iPhone users can't be cheap. Opening up the API and running it for the entire rest of the world for free is a non-starter. No company on earth is that generous, let alone Apple.
Beeper Mini is back
101–110 of 1001 posts
Re: Beeper Mini is back
#102These 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…
I think they are rightly calling out that iMessage as part of Apple's moat building is both bad for their customers and people their customers interact with. And while I agree with you, and I won't be using the service, I think from their POV it is the correct messaging.
IMessage is a much much much better experience. It's not at all bad for their customers. It's a huge plus of that system over Android and other platforms that still try to piggyback off SMS or haphazardly support RCS.
Re: Beeper Mini is back
#103Re: Beeper Mini is back
#104I wish things had more interoperability, but Apple is under no obligation to implement it or be okay with it. And honestly, I believe them when they say that this is a security/privacy risk; even if it does serve their anticompetitive tendencies.
Re: Beeper Mini is back
#105As an Apple customer, I applaud their tenacity. Every time Beeper's protocol hacks are fixed, Messages gets more secure.
By what metric? Arguably, users are less secure since "fixing" Messages (i.e. breaking Beeper) means Apple and Android users lose a secure communication channel. Beeper isn't "hacking" Messages... they've implemented the protocol.
I personally won't waste my time trying to be an early adopter of this. I suspect the upcoming RCS support will be the only "apple native" way to have non-shit tier messaging between android and iOS, and Apple will keep breaking Beeper if they can.
Re: Beeper Mini is back
#106I'm trying to understand what the target of this hacky iMessage spin-off of Beeper is. The whole idea of subscription-based monetization. Rather no way of Apple not patching quickly, dealing with this as soon as it raises attention.
But maybe that was the intent of a hack they found? A clever marketing strategy, to gain some rapid traction with the controversy, highlighting their project?
Re: Beeper Mini is back
#107These 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…
When did HN get so anti-consumer, anti- hacker , anti-freedom, pro-proprietary? Them taking the fight with Apple should be applauded. A walled down proprietary message platform only a few can use is stupid to fight in favor of.
The original kid who reversed: Great hacking, I think we can all applaud. This is a for-profit (VC funded?) company charging users by piggy backing off of servers they don’t own or pay for (and using apple binary blobs?).
If they used the protocol they reverse engineered on their own servers that’d be completely different. But that wouldn’t be profitable for them.
Re: Beeper Mini is back
#108These 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…
They’re highlighting the closed nature of Apple’s messaging system more effectively than anyone has in a long time. I support them in doing that.
Re: Beeper Mini is back
#109These 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…
Devil’s advocate: does Beeper opens up iMessage to spam bots?
Re: Beeper Mini is back
#110Earlier quoted context omitted.
No. Apple given their scale and position in the market should be forced to operate and interoperate with an open standard for messaging. iMessage should no longer allowed to be proprietary and stay part of Apple.
> Apple given their scale and position in the market should be forced to operate and interoperate with an open standard for messaging. You mean like SMS and MMS right now, and RCS next year? https://9to5mac.com/2023/11/16/apple-rcs-coming-to-iphone/