Two words. Status Symbol, just like having “Sent from my iPhone” as the footer of a persons email.why does anyone care about a blue bubble??? I miss why this is an issue...
Two words. Status Symbol, just like having “Sent from my iPhone” as the footer of a persons email.why does anyone care about a blue bubble??? I miss why this is an issue...
Nope. RCS is making SMS better, it is not solving it. RCS Apple is going to implement is missing E2EE.You guys are already getting RCS. Which you would THINk would end this debate. Nope, we are still talking about blue bubbles literally almost 2 months later.
That's really far fetched. Is this the case in US? If so, then it's really sad. All I can say - in the EU, there's no such thing you are talking about.It is not about YOU seeing the colors or not. It's about some perceived notion that iPhone users think that they are better than Android users and Android users hate the idea of us knowing they use anything non-android. Android users are literally making themselve victims of a situation that in YOUR WORDS is likely an American Android vs iMessage thing...not a rest of the world thing.
Android bros want the blue bubbles while simultaneously saying that only Apple users care about the bubbles lmfao. Even with RCS coming, they are not happy.Why? They will roll out RCS support and then will not have to waste any time or devs to work on an app for their competitor.
Unless the carriers adopt Apple’s proposals for E2EE (which I’d give *maybe* a 50/50 chance, at least in the US, given how thoroughly they’re tied to both their own monetization of telemetry and to 3 letter agency data collection) RCS isnt solving the key thing iMessage doesWhy? They will roll out RCS support and then will not have to waste any time or devs to work on an app for their competitor.
Nope. RCS is making SMS better, it is not solving it. RCS Apple is going to implement is missing E2EE.
And this reverse-engineered iMessage approach supported E2EE and was running locally on the device (no middle man, no data exposure to 3rd party). So I know it is hard to swallow for some, but this Beeper thing was actually more privacy friendly and more secure than what Apple is preparing with RCS or what Apple customers have now (totally insecure SMS).
Not far fetchd'd at all. I honestly have never realized Green vs Blue biubbles was still a thing in 2023.That's really far fetched. Is this the case in US? If so, then it's really sad. All I can say - in the EU, there's no such thing you are talking about.
Which is what? Because most users wanting iMessage are not wanting it for the security. They want blue bubbles (but then deny it lol) so they can stop being bullied.RCS isnt solving the key thing iMessage does
If you can send iMessages without your identity being verified and it is linked only to your phone number (which can easily be spoofed, you can read about it), then you can theoretically intercept data. I’m not saying that’s the case but it was probably possible. And who knows whether it wasn’t actively used.Why is that a security problem? iMessage has always only guaranteed E2EE, it’s a messaging protocol not an identity provider backed by verified positive ID
No, you could not intercept data.If you can send iMessages without your identity being verified and it is linked only to your phone number (which can easily be spoofed, you can read about it), then you can theoretically intercept data. I’m not saying that’s the case but it was probably possible. And who knows whether it wasn’t actively used.
You *literally* cut off the part where I answered that, which is impressive given the whole post was 2 sentences longWhich is what? Because most users wanting iMessage are not wanting it for the security. They want blue bubbles (but then deny it lol) so they can stop being bullied.
They want to send high quality videos and images vs compressed with SMS
and they want to be able to group chat with no issues.
So what is RCS still not going to solve that they need iMessage?
That’s a complete misunderstanding about what E2EE solvesIf you can send iMessages without your identity being verified and it is linked only to your phone number (which can easily be spoofed, you can read about it), then you can theoretically intercept data. I’m not saying that’s the case but it was probably possible. And who knows whether it wasn’t actively used.
Only a matter of time before the EU decides iMessage is a gatekeeper and as such forces Apple to open it to competitors. After usb c and the imminent ‘side loading’ (more commonly known as downloading) another embarrassment is coming for Apple.good. shut it down.
iMessage is not a reason for platform switch. The entire apple ecosystem is the reason and how apple has crafted it, the user experience etc.Well, it is part of the Apple's ecosystem lock-in. It is not cross-platform intentionally and everyone knows iMessage is one of the reasons Apple customers are not considering to switch to other platform. So no, comparison to two different operating system is - again - very wrong. Messaging platform is not comparable to RHEL and Windows.
I was using your “if apple “ start to the hypothesis. Creating a separate app is not the apple way. I’ve seen posts start in MR “if apple cared about privacy they would block google….”. Loads of nonsense they are.Totally true. And you know why they did not do that? Because it would be much more natural and easy for people to use another messaging app that way. If it was separate it would be easy to differentiate between SMS and another messaging platform. There would not be any "green" and "blue" bubbles. There would only be iMessage separate app which is not cross-platform and therefore it would be inferior to other alternative apps like Whatsapp, Telegram or Signal which are cross-platform. But integration to the default SMS app is the major part of Apple's game. With this move many US customers know just one messaging app and it is de facto standard for them. They don't know the technical side behind all of this, they just know "blue good, green bad. Green Android. Android bad.".
I agree with this one as well.
How do you know that?No, you could not intercept data.
Intercepting data and breaking through E2EE and having possibility to send messages without Apple ID to another Apple IDs is completely different territory.
Unless the carriers adopt Apple’s proposals for E2EE (which I’d give *maybe* a 50/50 chance, at least in the US, given how thoroughly they’re tied to both their own monetization of telemetry and to 3 letter agency data collection) RCS isnt solving the key thing iMessage does
She's a 28 year old woman which makes it even funnier because the posts read like a 16 year old boy. Lmao.No, you could not intercept data.
Intercepting data and breaking through E2EE and having possibility to send messages without Apple ID to another Apple IDs is completely different territory.
First thing is very serious security issue and the second one (the case which happened) is just annoyance, because it allows more spamming in the iMessage platform.
I was simply pointing out RCS isnt a replacement. There are free replacements. Outside the US they represent the majority of mess agingAnd? Apple is not obligated to solve a telecom’s problem, and they certainly have no obligation to accept Google’s RCS fork as a charity move. I pay a premium because I want to curb data collection and therefore use iOS. Apple also has no obligation (nor would it make any business sense) to provide android users with free perks that I pay to receive. Are you willing to PAY to use iMessage? If not, then you can’t have it.
Because I know what E2EE is and how it works. And I know Beeper guys did not find security hole in the Apple's E2EE implementation.How do you know that?
Anybody using the app could send and receive iMessages by only providing a phone number, no additional authentication was needed. How can you be sure that someone using a spoofing SIM card (using the same phone number as of an existing iMessage user) wouldn't be able to send/receive messages simultaneously with the genuine iMessage user? Usually iMessages can be received on multiple devices at the same time, so the spoofing number is yet another device pretending to be a user that it isn't. That has nothing to do with E2E which only guarantees encryption between the two parties but doesn't guarantee their identity which is exactly the concern I am raising.
I did not cut your answer out. I simply asked what else is needed from iMessage in Apple's flavor of RCS? Because the average Android user does not even know what RCS is.And if you think users dont care about E2EE I’ll point out that WhatsApp and Signal both use signal’s E2EE protocol, which is *vastly* more widely used than RCS or iMessage, and Meta just announced E2EE for messenger because it’s been such a demanded feature that they defied the very public pressure from the FBI and others to roll it ou
An already started conversation has already had a key exchange, spoofing a SIM card doesnt allow for intercepting that on its own, the keys are on the endpoints. For new conversations (or rotated keys depending on Apple’s implementation) you’re still only verifying control of the endpoint, not identityHow do you know that?
Anybody using the app could send and receive iMessages by only providing a phone number, no additional authentication was needed. How can you be sure that someone using a spoofing SIM card (using the same phone number as of an existing iMessage user) wouldn't be able to send/receive messages simultaneously with the genuine iMessage user? Usually iMessages can be received on multiple devices at the same time, so the spoofing number is yet another device pretending to be a user that it isn't. That has nothing to do with E2E which only guarantees encryption between the two parties but doesn't guarantee their identity which is exactly the concern I am raising.
Not so sure about that https://www.patentlyapple.com/2023/...gh-to-warrant-gatekeeper-status-regulati.htmlOnly a matter of time before the EU decides iMessage is a gatekeeper and as such forces Apple to open it to competitors. After usb c and the imminent ‘side loading’ (more commonly known as downloading) another embarrassment is coming for Apple.
That’s a complete misunderstanding about what E2EE solves
Because I know what E2EE is and how it works. And I know Beeper guys did not find security hole in the Apple's E2EE implementation.
And what I’m saying is that’s not a security flaw, it’s literally an expected part of such a protocol.You're both missing the point. I'm not saying there's a hole in the E2EE. I'm saying there's a possible identity concern in the iMessage protocol because the only "authentication" it seems to have required is a valid phone number that can be spoofed. Identity concerns are also security concerns. If someone on the other end says "I'm your wife" and you don't have means to validate that's indeed your wife, it doesn't matter if your communication is encrypted end-to-end, there's already an authentication issue. Authentication is also part of security.
iOS does allow side loading. I pay the $99 yearly developer fee to do it. I have two side loaded apps on my iPhone, one being a modified YouTube app that allows me to hide Shorts. I also pay for YT Premium, which doesn’t allow that, so I use the mod.It’s ironically androids ability to side load and pirate apps that is why there is less paid app adoption.
I wonder what it would like if iOS allows side loading