Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Oh really? What about eMail, Html, Postscript, Pdf, Json, Xml?

Apple doesn't vote for better - it just votes for proprietary. But I forgot to mention, that there is already a law being created that addresses exactly this scenario. So Signal/WhatsApp/Younameit but be able to communicate with each other.
Btw - MS DOS was never a standard, it was just an OS ...
That EU law doesn‘t ensure the big players communicate with eachother, it ensures that big players have to provide a way for other, lower userbase apps to tie into their chat network. Probably means that your tiny chat app XYZ hooks into iMessage, whereas the other big players like WhatsApp are in no way forced to actually hook into other big player platforms because they can stand on their own and profit from platform lock-in.

Also, Signal doesn‘t fall under the criteria to open up (userbase too tiny).
 
Let me explain it to you. RCS would NOT replace your "precious" imessage. It would just replace the fallback from SMS to RCS when you text your android friends. This would give you end to end encrypted messaging (as opposed to the wide open texts running throught the carriers servers righr now), full size file transfer (think full size videos and photos as opposed to the totally wrecked and small photos you can only send right now), and lastly, typing indicators and delivered and read indicators (similar to how imessage works). It would greatly enhance your experience texting with Android friends.

Maybe when carriers actually replace SMS with RCS that will happen. Currently, they show no interest in doing that. Most have abandoned their own RCS plans and just outsourced it all to Google using their own proprietary "iMessage-like" service based on RCS that runs in parallel with SMS in the various default messengers opening up users to business advertising (spam) that exists outside of FCC regulation.
 
Last edited:
  • Like
Reactions: Unregistered 4U
There’s no money in it for carriers to support RCS and they’d actually lose money as they build out the infrastructure.
Yeah that part I don’t believe. I’m not sure what country you live in but in the USA carriers will nickel and dime you with bogus charges. They’ll even make it look like it’s some sort of government fee and tack it onto your bill. You can bet if this crap goes through they’ll be in “RCS administration messaging fee” on your bill. Of course the cool thing will be it won’t be an optional charge or based on if you actually use RCS.
 
Yeah that part I don’t believe. I’m not sure what country you live in but in the USA carriers will nickel and dime you with bogus charges. They’ll even make it look like it’s some sort of government fee and tack it onto your bill. You can bet if this crap goes through they’ll be in “RCS administration messaging fee” on your bill. Of course the cool thing will be it won’t be an optional charge or based on if you actually use RCS.
The carrier’s current usage of SMS and MMS are very small file sizes, that’s why images and videos look like crap. The reason why they haven’t updated their infrastructure is they’re making a killing doing nothing. Spending ANYTHING AT ALL would be losing money (as that’s money they’re NOT spending now to update their infrastructure).

They could…
Spend the money to roll out the infrastructure and raise fees to adjust for it… for which those fees would have to be in place for awhile to offset the infrastructure cost.

OR

Do absolutely nothing and continue to cart load after load of money to the bank… and STILL raise prices every now and again.

The second one is low effort almost free money, which is what they’re doing. Anything other than that would be an effort that’s, in their view, really not required… the money’s ALREADY coming in. :) There’s very little value in the USA or anywhere in doing anything other than “sitting on their hands and collecting the fees”. It MIGHT be different if enabling RCS would bring new business, new users, but it’s not (which is why they’re handwaving and letting Google do… whatever it’s doing!)
 
SMS where realy expencive (10+ years ago) practically everywhere, but strangely only in the US and in a few other limited circumstances users have decided to use imessage and not a cross platform app.
Has I said cross platform tools are used in a healthy society.
Don't overestimate the intelligence of the US iPhone users :)
I think to some of us it doesn't matter, but when I sent to send a PDF to an Android user
I was like, what the hell!
 
Seeing people, including full grown adults, caring about what type of phone that their peers have is silly to the highest degree. I myself call it disgusting.

I drive a Toyota. But my friend drives a Hyundai. Big freaking deal.

These phones, like cars, are mere tools. They’re dead, lifeless tools that allow us to communicate with one another. That’s all they are. Which tool that someone else uses is of no importance to me, and it shouldn’t be of any importance to anyone else either.
I don't care which phones people use, I just feel bad for android users :)
 
Apple should adopt RCS
I don't care which phones people use, I just feel bad for android users :)
Ah. Well, fair enough I guess. It’s all just a matter of opinion anyway.

My last phone was an Android and it was the best phone I’ve ever owned. Different strokes for different folks. I do recommend trying one sometime though.
 
Let me explain it to you. RCS would NOT replace your "precious" imessage. It would just replace the fallback from SMS to RCS when you text your android friends. This would give you end to end encrypted messaging (as opposed to the wide open texts running throught the carriers servers righr now), full size file transfer (think full size videos and photos as opposed to the totally wrecked and small photos you can only send right now), and lastly, typing indicators and delivered and read indicators (similar to how imessage works). It would greatly enhance your experience texting with Android friends.
Adopting RCS as the fall back will not grant end to end encryption. That's not a feature of RCS. That's a feature of google messaging. RCS as a fall back would be an improvement, but google messages is it's own messaging network that's integrated with texts on google phones. And that's not the only thing beyond RCS features that google has implemented. Most messages don't rely on the carrier's messaging frameworks to get to where they are going. you can't get end to end encryption without a root of trust. For iMessage, it's apple. For google message it's google.
 
  • Like
Reactions: visualseed
Yes. Go to various parties and get togethers, you'll have cases like a significant majority are iOS users. Others are mostly Android users. One of the groups I hang out with, we're split 50/50 down the middle.
1C6BA2CE-2223-462E-8692-8DBC0C662D98.jpeg

The Android users at the party. 😀
 
This is just posturing from Google/Android to proactevely combat the meme-y image of "green bubbles" being associated with poor phones/people etc.

In fact I hope Apple adopts RCS to replace/add to SMS and keeps the bubbles green to distinguish when a message is not sent via the iMessage service.

What then?
 


Google has urged Apple to adopt Rich Communication Services (RCS) in its Messages app in a "lyric explainer video" for Drake's "Texts Go Green."

General-Apps-Messages.jpg

RCS is designed to replace SMS messaging and touts support for higher resolution photos and videos, audio messages, bigger file size, improved encryption, and more. Google has advocated the new communications protocol for several years.

Google's senior vice president of Android, Hiroshi Lockheimer, has repeatedly tried to persuade Apple to adopt support for RCS, and now, a video posted on the official Android Twitter account once again urges Apple to support RCS.



The video seeks to explain the meaning behind a song called "Texts Go Green," the third track on Drake's latest album, "Honestly, Nevermind," which explains the need to move on from a toxic relationship. The title is a reference to how when an iPhone user is blocked, they no longer see their messages sent as blue iMessage bubbles and send green SMS bubbles instead. "If only some super talented engineering team at Apple would fix this," the video says.

Apple is the last major RCS holdout, as U.S. carriers that include Verizon, AT&T, and T-Mobile have adopted RCS support for Android devices. Apple has not commented on whether it plans to add RCS support in the future, so the company's position is still unknown.

Article Link: Sarcastic Android 'Lyric Explainer Video' Urges Apple to Adopt RCS in Messages
i'll take imessage on windows instead of rcs please
 
Do people in the US still actually predominantly use texts? Here in Oz we use pretty much every app but texts for messaging.

We also don't care if zuckerface reads our messages. If he wants to see my c*ck pics, that's his problem.


View attachment 2021728
Yes most plans even the low end plans have unlimited texts and minutes. There’s even no frills unlimited minutes/text/data plans. So there’s no main reason to download extra apps. You just select text instead of call from your contacts no worrying about if they have the right app.
Now if you want to get more involved then you get apps.
 
Some people are just weird. RCS is better than SMS, Apple should adopt it as a fallback for communication on Android as it allows better features than SMS currently provides. It supports higher resolution photos and videos, audio messages, bigger file sizes, better encryption, improved group chat, and more.

RCS as is, does not offer E2E encryption but Google's version offers E2E encryption and all major carriers in the US as of 2021 have adopted Google messages as the default messaging app.

All Three Major U.S. Carriers and Google Adopt Rich Communication Services, But No Sign of Apple Interest


When RCS sees a complete Android rollout, text messages on Android phones will be end-to-end encrypted. ‌iPhone‌ to ‌iPhone‌ communications are end-to-end encrypted thanks to iMessage, but with this change, texts between Android users and ‌iPhone‌ users will be less secure because of Apple's decision to continue to use SMS over RCS.

Hiroshi Lockheimer, senior vice president of Android, told The Verge that Android vs. ‌iPhone‌ messaging security will become an important discussion with the wider adoption of RCS. "The fallback messaging experience on the other platform will not have encryption if it's still SMS," he said. "I think that that is a pretty interesting dynamic and I would hope that as everyone focuses on security and privacy it becomes an important part of the discussion."

Starting with Galaxy S22, Samsung has switched to google messages as the default. If you want your messages to be E2E encrypted, there is no reason not to urge Apple to support RCS fallback. All carries are defaulting to Google messaging app as the default.
 
Starting with Galaxy S22, Samsung has switched to google messages as the default. If you want your messages to be E2E encrypted, there is no reason not to urge Apple to support RCS fallback. All carries are defaulting to Google messaging app as the default.
I mean… if you want your messages to be E2E encrypted, use Signal. Or Telegram. Or WhatsApp. or (12 other messaging apps). Or, I guess Google. Now, the question is, does Google’s solution offer anything special that the other ones don’t. The Google logo? For some people I’m sure that’s enough of a difference.
 
  • Like
Reactions: CarlJ
I mean… if you want your messages to be E2E encrypted, use Signal. Or Telegram. Or WhatsApp. or (12 other messaging apps). Or, I guess Google. Now, the question is, does Google’s solution offer anything special that the other ones don’t. The Google logo? For some people I’m sure that’s enough of a difference.
The only true E2E app in that list is Signal. Telegram has to be turned on because it's not on by default and they just recently gave away user data even though they made the promise they wouldn't do this, even with non E2E messages, so they're off the table. WhatsApp is Facebook so they can't be trusted at their word. And Google is self-explanatory. They can tout privacy all day long but have been shown time and time again to go against the very things they promised they wouldn't do.
 
Some people are just weird. RCS is better than SMS, Apple should adopt it as a fallback for communication on Android as it allows better features than SMS currently provides. It supports higher resolution photos and videos, audio messages, bigger file sizes, better encryption, improved group chat, and more.

RCS as is, does not offer E2E encryption but Google's version offers E2E encryption and all major carriers in the US as of 2021 have adopted Google messages as the default messaging app.
All the major carriers are in favor of RCS because it's designed to put money in their pockets. Google is in favor of RCS because they see it as a weapon against Apple.

Quoting from the Wikipedia page for RCS:

RCS Business Messaging (RBM) is the B2C (A2P in telecoms terminology) version of RCS. This is supposed to be an answer to third-party messaging apps (or OTTs) absorbing mobile operators' messaging traffic and associated revenues. While RCS is designed to win back Person-to-Person (P2P) traffic, RBM is intended to retain and grow this A2P traffic.[25][26] RCS offers "rich" features similar to those of messaging apps, but delivered (in theory) via the preloaded SMS messaging app - for example Google Messages or Samsung Messages. By making these features available in a B2C setting, RBM is expected to attract marketing and customer service spend from enterprises, thanks to improved customer engagement and interactive features that facilitate new use cases.[27][28] This was the primary reason for the development of RCS by the GSMA.​

RCS was developed to benefit the carriers, not the customers.
 
The only true E2E app in that list is Signal. Telegram has to be turned on because it's not on by default and they just recently gave away user data even though they made the promise they wouldn't do this, even with non E2E messages, so they're off the table. WhatsApp is Facebook so they can't be trusted at their word. And Google is self-explanatory. They can tout privacy all day long but have been shown time and time again to go against the very things they promised they wouldn't do.
We cannot believe Apple too. So, that leaves only Signal as the option, according to you.
 
We cannot believe Apple too. So, that leaves only Signal as the option, according to you.
Apple is off that list, because if you store your messages in the cloud, Apple can see them and hand over your text messages. There is no situation with Signal that they can do this. So yes, Apple is not on the list, according to me.
 
  • Like
Reactions: Beautyspin
That EU law doesn‘t ensure the big players communicate with eachother, it ensures that big players have to provide a way for other, lower userbase apps to tie into their chat network. Probably means that your tiny chat app XYZ hooks into iMessage, whereas the other big players like WhatsApp are in no way forced to actually hook into other big player platforms because they can stand on their own and profit from platform lock-in.

Also, Signal doesn‘t fall under the criteria to open up (userbase too tiny).
I didn‘t have a close look at the ongoing legislation. But it is about interoperability. So if one person uses messenger A and another person uses messenger B, those persons should be able to communicate.
This requires a standard communication protocol, lime XAMPP or RCS.
 
Simply? Why don't you just simply install the app clients for the service you wish you use? That way you can maintain state, authentication credentials, and contact lists separately to their respective networks instead of convoluting a relatively simple messenger with undue complexity. What you are asking for would require a universal contact list managed at the system level to even work and I'm not sure a single third-party service, much less Apple, would got for that.
No it wouldn't.

Here's how it works today when I want to send a message to mobile user +123 456789. Let's assume I have an iPhone with iMessage and that I've turned SMS on as a backup.

1. I go to iMessage and send the message to +123 456789 (either listed in my Contacts or manually input; either way works).

2A: The number is registered to iMessage and online. The message gets sent via Apple's proprietary protocol.

2B: The number is registered to iMessage and offline. After timing out the message is sent via SMS protocol.

2C: The number is not registered to iMessage. The message gets sent via SMS protocol.

Here's how it'd work in the hypothetical example I gave:

1. Nothing changes.

2A: Nothing changes.

2B: (Probably) nothing changes. (Debatable, but let's assume that.)

2C: iMessage passes the +123 456789 destination, a little meta data, and the message to an authorized message sending app/protocol registered to Apple's API (let's call this "WhatzzApp handler" for example), and "WhatzzApp" tries to send the message using its protocol. If successful, it returns a "sent" to iMessage for onscreen display. If unsuccessful/timeout, "not sent" back to iMessage to try the next registered messaging sending app (if registered). Loop, repeat.

Then you can do everything basic from Apple's iMessage UI, which obviously improves the experience for Apple's own users. If Apple wants another color code for these API handled message bubbles, fine, go for it. And for something fancy (like N-way audio or video chats) you'll probably still have to go to the individual app. But for sending a message, or picture, or video clip to another person, this'd be the way iMessage could do it.

Apple could set certain reasonable *mutual* requirements to play. For example, end-to-end encryption.

Again, what's wrong with this? This is how messaging apps like Pidgin/Adium have worked for 20+ years: with protocol handlers (plugins). Why isn't Apple improving the messaging experience for its users in this way? It sure seems like it could, and quite easily.
 
I didn‘t have a close look at the ongoing legislation. But it is about interoperability. So if one person uses messenger A and another person uses messenger B, those persons should be able to communicate.
This requires a standard communication protocol, lime XAMPP or RCS.
Like I said, the only thing companies are required to do is provide a way for smaller companies to tie into your network. There is no definition of a standard, it can also be proprietary. No one is forced to interoperate with anyone, the law only forces the big players to open up so smaller companies can interoperate and compete.

This wont help anyone getting Meta and co. to interoperate, because they aren‘t forced to (they are just forced to provide the tools to allow others to interoperate with them). It‘s another token example of 50+ years old tech illiterates making laws for the EU.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.