I see YouTube videos linked, and I remember being on this site before YouTube existed. I don’t think it has changed all that much, though.

I think you might be thinking of Cruise?

https://gizmodo.com/cruise-robotaxi-human-assistance-kyle-vogt-1850997279

I think this is true, but I also grew up without Internet or social media so maybe things were more regional as opposed to this larger shared culture those things have enabled. So that may be part of it?

Yeah, this really all feels like the carriers have dropped the ball.

Google is the only one that allows “End to end” encryption.

Allowing and implementing are not the same things. They implemented encryption in their RCS services. They don’t allow everyone to use their service, but they built and own it so that’s their right, I guess.

And practically speaking google controls the standard, they have over 800 million users out of the total possible 1.2 billion.

Can you elaborate here? How do they control the standard? Specifically, I’m not asking about their implementation of RCS, because of course they control that, but their implementation is not the same thing as the standard itself.

It might not be a monopolistic standard in theory but it is in practice

It’s widely understood that it’s difficult to implement a competent web browser. That’s why there are only a handful of browser choices. This doesn’t make HTTP a monopolistic protocol.

Saying the RCS standard is a monopolistic standard makes zero sense to me, even in practice. We are quite literally discussing another vendor entering the market. If you run a telecom and want to implement RCS, you are able to do so. If you are a phone manufacturer you are free to implement RCS in your software stack. None of this is easy, but it’s possible and so this isn’t a monopoly situation as far as I understand it. Google wanted to compete with iMessage so they built a competitor on a proprietary but open global standard, the standard which is meant to replace SMS and MMS messaging.

I’ll take that as a win!

RCS is a proprietary standard, but it is not owned or controlled by Google. They just happen to be one of the first major corporations to embrace and implement the standard.

Wow, I don’t see many Ray Stevens references. My brothers and I really enjoyed “the streak” growing up.

This was my interpretation as well. I frequently have weird abstract dreams, where I’m often not present or not involved, and the dreams sometimes don’t involve people at all. The ones without people are weird and hard to explain. I assumed that’s what the lower left panel is trying to show.

This would be awesome, but I just don’t see it happening this way. They have to work with the copyright holders who set those kinds of terms and who have the majority of the leverage in negotiating those terms. Unfortunately, I don’t see any reason this kind of deal would be made.

The business model is to force consumers to purchase and repurchase the same content over and over. Changing only the format, or distribution method, or platform of consumption. This kind of deal would undercut that business model.

What have you explained? That RCS is not stewarded by the IETF? That’s not the crux of the issue. My original claim was that RCS was more open than iMessage and that RCS is not owned or controlled by Google. Tell me where I’m wrong, and back it up with good sources. Or not. Whatever you’re feeling like.

https://www.gsma.com/futurenetworks/wp-content/uploads/2019/10/RCC.07-v11.0.pdf

The specification exists. It’s not free as in beer. This is really beside the point. Google implemented an RCS messaging client. Your cellular carriers implement the RCS endpoints the clients use.

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.

https://time.com/5404475/history-tipping-american-restaurants-civil-war/

After the Constitution was amended in the wake of the Civil War, slavery was ended as an institution but those who were freed from bondage were still limited in their choices. Many who did not end up sharecropping worked in menial positions, such as servants, waiters, barbers and railroad porters. These were pretty much the only occupations available to them. For restaurant workers and railroad porters, there was a catch: many employers would not actually pay these workers, under the condition that guests would offer a small tip instead.

“These industries demanded the right to basically continue slavery with a $0 wage and tip,” Jayaraman says.

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.

Are you sure about that?

In early 2020, it was estimated that RCS was available from 88 operators in 59 countries with approximately 390 million users per month.

https://en.m.wikipedia.org/wiki/Rich_Communication_Services

but doesn’t play nice with apple.

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.