iMessage uses it’s own protocols and shit that are proprietary, and uses the standard sms protocol as a fallback. Android can use something called RCS which catches up feature wise, but doesn’t play nice with apple.
It’s to create an illusion of exclusivity and therefore social pressure to use an apple device.
This isn’t technically wrong, but to be clear, iMessage is closed source. No one can play nice with Apple, in that regard.
RCS on the other hand is a more open standard that anyone is free to implement and use. It just doesn’t come with end-to-end encryption as a part of the standard.
I mean it’s just a gsm standard with some extra features. Realistically you could probably (relatively) easily figure it out and code it yourself like beeper mini did with iMessage but I don’t think gsm or Google is going to change the standard to stop you.
Google doesn’t own the RCS protocol. This is like saying they own the SMTP protocol because they provide Gmail. They are just one company that has implemented the protocol in their default text message app. They built end-to-end encryption into their implementation, which is currently closed source. I’m guessing this is what you’re referring to.
Anyone can implement RCS. It may cost you some money and some time, but it is possible. That’s the difference I was originally trying to highlight.
No. I’m sorry. You can’t just say it and make it true. Please show me how Google owns RCS or prevents other developers from implementing it within their own apps.
All using Google Messages. Yep I’m sure. Samsung skins the app but it’s all Google Messages. 3rd party apps arenct supported. I’ll use RCS when there’s FOSS on Android for RCS.
why is that even a thing lol
iMessage uses it’s own protocols and shit that are proprietary, and uses the standard sms protocol as a fallback. Android can use something called RCS which catches up feature wise, but doesn’t play nice with apple.
It’s to create an illusion of exclusivity and therefore social pressure to use an apple device.
This isn’t technically wrong, but to be clear, iMessage is closed source. No one can play nice with Apple, in that regard.
RCS on the other hand is a more open standard that anyone is free to implement and use. It just doesn’t come with end-to-end encryption as a part of the standard.
Nope, RCS isn’t. It’s still not opened up for 3rd party Android apps.
I mean it’s just a gsm standard with some extra features. Realistically you could probably (relatively) easily figure it out and code it yourself like beeper mini did with iMessage but I don’t think gsm or Google is going to change the standard to stop you.
…no, you can’t. I’ve seen people try. Google says they will open the RCS protocol to 3rd parties… soon?
Google doesn’t own the RCS protocol. This is like saying they own the SMTP protocol because they provide Gmail. They are just one company that has implemented the protocol in their default text message app. They built end-to-end encryption into their implementation, which is currently closed source. I’m guessing this is what you’re referring to.
Anyone can implement RCS. It may cost you some money and some time, but it is possible. That’s the difference I was originally trying to highlight.
No, anyone cannot. That’s why I said it wasn’t really open. 3rd party android apps can’t use RCS. I would need to use Google’s Messages app.
No. I’m sorry. You can’t just say it and make it true. Please show me how Google owns RCS or prevents other developers from implementing it within their own apps.
That’s their rcs protocol. It’s the one with the features. Without the features is easy, the features are what make it difficult.
It’s a gated standard.
Are you sure about that?
https://en.m.wikipedia.org/wiki/Rich_Communication_Services
Yes, and your source says nothing to the contrary.
All using Google Messages. Yep I’m sure. Samsung skins the app but it’s all Google Messages. 3rd party apps arenct supported. I’ll use RCS when there’s FOSS on Android for RCS.
because iMessage uses texting as a fall back