Live data from Hacker News

Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

theverge.com

61–70 of 105 posts

Re: Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

#61
post #59

Earlier quoted context omitted.

> It kind of is. They replaced the standard messaging app with a proprietary alternative, and then othered and ostracized users of non-Apple platforms who tried to use the standard. Nope. SMS and MMS were still present, and as they were at the time iMessage was introduced, the only global messaging standard. Apple has also commited to bring another standard to the platform in RCS. The notion that iMessage is a standa…

> Nope. Well, yeah. > SMS and MMS were still present, I never said otherwise. But they made iMessage the default and gave it priority. > Apple has also commited to bring another standard to the platform in RCS. Too little too late. > The notion that iMessage is a standard is wrong. In the US it's a de facto standard. People get punished if they use SMS/MMS/RCS.

[deleted]

Re: Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

#62
post #59

Earlier quoted context omitted.

> It kind of is. They replaced the standard messaging app with a proprietary alternative, and then othered and ostracized users of non-Apple platforms who tried to use the standard. Nope. SMS and MMS were still present, and as they were at the time iMessage was introduced, the only global messaging standard. Apple has also commited to bring another standard to the platform in RCS. The notion that iMessage is a standa…

> Nope. Well, yeah. > SMS and MMS were still present, I never said otherwise. But they made iMessage the default and gave it priority. > Apple has also commited to bring another standard to the platform in RCS. Too little too late. > The notion that iMessage is a standard is wrong. In the US it's a de facto standard. People get punished if they use SMS/MMS/RCS.

[deleted]

Re: Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

#63

I've asked this 3 times across the various threads on this, and have yet to get a 100% confirmed "you are right" answer because I don't know the specifics and I haven't come into anybody who has taken the time to research the answer: When you log in to iMessage and the various underlying protocols/services, you do it with an Apple ID. Is that Apple ID tied in a one-to-many (but you need at least one) fashion of regis…

Spoofs masquerade using confirmed serial numbers. In the case of Hackintoshes you manually repeat activation until you get a valid serial number; I don't know what Beeper's implementation does.

So Apple can maintain this database but they still have the problem of proving that a serial number attestation, sending all the right information, is from that actual hardware and not a spoof of the hardware.

Without intensely protected cryptography like the T1/T2 enclaves, there is nothing legitimate hardware can send that can't be mimicked once the protocol is reversed. Maintaining a stricter database of unsold and destroyed products can only slow down activation, not stop it.

That means Apple would have to use other means to determine whether an attestation is valid like number of sign-ins, locations, the user trying to sign in, etc. If it enforces any of these, it will lock out and anger more legitimate users than it will block Hackintoshes and Android iMessage clients.

Hopefully that makes sense. Apologies if this is a repeat of previous answers.

Re: Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

#64

Earlier quoted context omitted.

What law do you think Apple is breaking by preventing beeper usage?

None. I didn't imply I thought they were breaking any law. I think Apple might try to sue Beeper though.

Seems easier to just break Beeper's implementation a few times. No one wants to use a messaging service that works sometimes.

Re: Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

#65
post #64

Earlier quoted context omitted.

None. I didn't imply I thought they were breaking any law. I think Apple might try to sue Beeper though.

Seems easier to just break Beeper's implementation a few times. No one wants to use a messaging service that works sometimes.

I wonder how long they can keep that up for though.

Re: Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

#66
post #59

Earlier quoted context omitted.

> It kind of is. They replaced the standard messaging app with a proprietary alternative, and then othered and ostracized users of non-Apple platforms who tried to use the standard. Nope. SMS and MMS were still present, and as they were at the time iMessage was introduced, the only global messaging standard. Apple has also commited to bring another standard to the platform in RCS. The notion that iMessage is a standa…

> Nope. Well, yeah. > SMS and MMS were still present, I never said otherwise. But they made iMessage the default and gave it priority. > Apple has also commited to bring another standard to the platform in RCS. Too little too late. > The notion that iMessage is a standard is wrong. In the US it's a de facto standard. People get punished if they use SMS/MMS/RCS.

> Well, yeah.

You said > "They replaced the standard messaging app with a proprietary alternative"

Nope. SMS and MMS.

> Too little to late.

Thanks. I thought you were here in bad faith, now I know you are.

> In the US it's a de facto standard. People get punished if they use SMS/MMS/RCS.

Good grief! Beeper isn't the answer. A few months ago it was all about how anti-competitive Apple were because no RCS. Now RCS it "too little to late"? Why are you all so damned incapable of using alternatives? This is as self-inflicted "problem".

Re: Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

#67
post #66

Earlier quoted context omitted.

> Nope. Well, yeah. > SMS and MMS were still present, I never said otherwise. But they made iMessage the default and gave it priority. > Apple has also commited to bring another standard to the platform in RCS. Too little too late. > The notion that iMessage is a standard is wrong. In the US it's a de facto standard. People get punished if they use SMS/MMS/RCS.

> Well, yeah. You said > "They replaced the standard messaging app with a proprietary alternative " Nope. SMS and MMS. > Too little to late. Thanks. I thought you were here in bad faith, now I know you are. > In the US it's a de facto standard. People get punished if they use SMS/MMS/RCS. Good grief! Beeper isn't the answer. A few months ago it was all about how anti-competitive Apple were because no RCS. Now RCS it…

> Nope. SMS and MMS.

This is simply incorrect. iMessage is the default for iPhones.

> Thanks. I thought you were here in bad faith, now I know you are.

I'm not here in bad faith at all. Adding RCS support won't do much to fix the division apples has caused between iPhone users and other phone users.

> Good grief! Beeper isn't the answer.

It's definitely a step in the right direction. Forcing Apple to be more open with iMessage is a good thing for consumers.

> A few months ago it was all about how anti-competitive Apple were because no RCS. Now RCS it "too little to late"?

They should have been using RCS from the start and cooperated with and contributed to the standard. Now, yeah it's pretty late and won't fix the problem they have caused.

> Whay are you all so damned incapable of using alternatives? This is as self-inflicted "problem".

Because in the US Apple users insist on using iMessage.

Re: Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

#68
post #66

Earlier quoted context omitted.

> Well, yeah. You said > "They replaced the standard messaging app with a proprietary alternative " Nope. SMS and MMS. > Too little to late. Thanks. I thought you were here in bad faith, now I know you are. > In the US it's a de facto standard. People get punished if they use SMS/MMS/RCS. Good grief! Beeper isn't the answer. A few months ago it was all about how anti-competitive Apple were because no RCS. Now RCS it…

> Nope. SMS and MMS. This is simply incorrect. iMessage is the default for iPhones. > Thanks. I thought you were here in bad faith, now I know you are. I'm not here in bad faith at all. Adding RCS support won't do much to fix the division apples has caused between iPhone users and other phone users. > Good grief! Beeper isn't the answer. It's definitely a step in the right direction. Forcing Apple to be more open wit…

> This is simply incorrect. iMessage is the default for iPhones.

You're an Android user, right? Suffice to say that you are wrong. Messages.app, not iMessage is the default. It is designed to handle SMS, MMS and Apple iMessage service. iMessage exists for Apple-to-Apple messaging and for those iPhone customers that choose not to have a carrier messaging plan. This is not an opinion.

> I'm not here in bad faith at all. Adding RCS support won't do much to fix the division apples has caused between iPhone users and other phone users.

What? That is certainly a take. I can't say anymore for fear of causing offence. In all sincerity and candor - you really do come across as someone with a chip on their shoulder.

> It's definitely a step in the right direction. Forcing Apple to be more open with iMessage is a good thing for consumers.

> They should have been using RCS from the start and cooperated with and contributed to the standard. Now, yeah it's pretty late and won't fix the problem they have caused.

So RCS will "fix" most of the "problems they have caused" here. What's more the main barrier, as ever, has been carrier adoption. Google only really started to push for RCS after miserably failing to deliver a coherent messaging platform strategy and releasing Google Messages in 2019. Whats more, their suposedly "open" E2EE RCS implementation is only available for Pixel and Samsung users. The carrier RCS landscape is a mess globally, with little to no use outside of US carriers, who have either switched to Google (privacy concerns) or have recently (last 5 years) added support for Universal Profile. By the way, the GSMA are a carrier-only body. Neither Google nor Apple were involved in the creation of RCS. Not that it matters as adoption by GSMA members has been, if I'm being generous, laughably slow. Google are involved by virtue of their acquisition of Jibe. Remind me, who is responsible for this problem?

> Because in the US Apple users insist on using iMessage.

Why is that? See above...

Edit: The issue I, and it seems many others have with Beepers approach is the commercialisation of someone else's property. Like it or not, de facto or not, iMessages is a private API. Hacking it for kicks is fine. Commercialising it is not. Bragging about to one one the big tech firms is going to end in tears. The merits of iMessages being open are obvious, but it's seems to be a market in which Apple doesn't want to be in. The service exists for customers of Apple's products and is directly tied to hardware ownership.

Re: Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

#69
post #68

Earlier quoted context omitted.

> Nope. SMS and MMS. This is simply incorrect. iMessage is the default for iPhones. > Thanks. I thought you were here in bad faith, now I know you are. I'm not here in bad faith at all. Adding RCS support won't do much to fix the division apples has caused between iPhone users and other phone users. > Good grief! Beeper isn't the answer. It's definitely a step in the right direction. Forcing Apple to be more open wit…

> This is simply incorrect. iMessage is the default for iPhones. You're an Android user, right? Suffice to say that you are wrong. Messages.app, not iMessage is the default. It is designed to handle SMS, MMS and Apple iMessage service. iMessage exists for Apple-to-Apple messaging and for those iPhone customers that choose not to have a carrier messaging plan. This is not an opinion. > I'm not here in bad faith at all…

> Messages.app, not iMessage is the default.

This is semantics and you know it.

> iMessage exists for Apple-to-Apple messaging

There we go. iMessage is the default for Apple phones contacting other phones.

Given that iPhones are a majority in the US, iMessage is the default for most phones in the US.

> What? That is certainly a take.

I don't see how. I think it's perfectly rational. I'm surprsied you disagree so strongly to be hoenst.

> you really do come across as someone with a chip on their shoulder.

*shrug*

I feel the same way about you.

> So RCS will "fix" most of the "problems they have caused" here.

No, it really won't. It certainly won't do anything to fix the silly blue/green bubble divide they caused.

> What's more the main barrier, as ever, has been carrier adoption.

It doesn't really matter if carriers adopt something that the manufacturer of most phoens in the US does not support.

> Google only really started to push for RCS after miserably failing to deliver a coherent messaging platform strategy and releasing Google Messages in 2019.

OK, but that's almost half a decade ago now.

> Whats more, their suposedly "open" E2EE RCS implementation is only available for Pixel and Samsung users.v

Another reason Apple should have been contributing to and working on the RCS standard instead of alienating anyone who didn't want to buy their hardware.

Honestly they should have been investigated for antitrust violations.

> Why is that?

Because iMessage is the default for apple phones and most phones in the US are Apple phones.

Re: Apple responds to the Beeper iMessage saga: 'We took steps to protect our users'

#70
post #68

Earlier quoted context omitted.

> This is simply incorrect. iMessage is the default for iPhones. You're an Android user, right? Suffice to say that you are wrong. Messages.app, not iMessage is the default. It is designed to handle SMS, MMS and Apple iMessage service. iMessage exists for Apple-to-Apple messaging and for those iPhone customers that choose not to have a carrier messaging plan. This is not an opinion. > I'm not here in bad faith at all…

> Messages.app, not iMessage is the default. This is semantics and you know it. > iMessage exists for Apple-to-Apple messaging There we go. iMessage is the default for Apple phones contacting other phones. Given that iPhones are a majority in the US, iMessage is the default for most phones in the US. > What? That is certainly a take. I don't see how. I think it's perfectly rational. I'm surprsied you disagree so stro…

> This is semantics and you know it.

Nope, it's a distiction. And an important one.

> There we go. iMessage is the default for Apple phones contacting other Apple phones.

TFTFY. To contact other phones, use SMS, MMS. Even better, talk to your iPhone friends and agree to use another service. What is wrong with that? Literally the rest of the world managed it.

> I don't see how. I think it's perfectly rational. I'm surprsied you disagree so strongly to be hoenst.

I disagree because every point you have made has be immature or wrong. Or both. blue/green doesn't exist anywhere in the world, and speaking with friends in the US, is a storm in a teacup. You bringing it up leads me to believe that your likely in your early twenties. Some advice; know-one cares outside your little circle.

> No, it really won't. It certainly won't do anything to fix the silly blue/green bubble divide they caused.

You said it, silly, and nor really big bad Apple's fault. They cannot solve for childish responses from people that should know better.

> It doesn't really matter if carriers adopt something that the manufacturer of most phoens in the US does not support.

It really does, if they want said manufacturer to adope their standard.

> OK, but that's almost half a decade ago now.

And it was going nowhere then. It's still not widley used.

> Another reason Apple should have been contributing to and working on the RCS standard instead of alienating anyone who didn't want to buy their hardware.

So Google restricting access to their proprietary implementation of their RCS service is Apples fault for not contributing to a standard that they were unable at the time to contribute to because they were not members of the standard body drafting the standard behind closed doors. That takes some mental hoop jumping. Are you smelling toast?

> Because iMessage is the default for apple phones and most phones in the US are Apple phones.

If that is genuinely the case, why isn't a problem for the rest of the world? Also, I gave you the answer. Google let Android users down. They bungled messaging on the platform massively.

* Reminder to future me. Don't respond. It's a waste of time. see https://xkcd.com/386/

Post reply on HN