Maybe the better thing to concentrate on is why you felt like that comment was necessary. You didn't seem to have a goal behind it, other than drawing more attention. It's really not relevant to the discussion or the post. So why post it? It felt like your intention was just to talk shit about a random person, and maybe you should think about that.

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

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.

Again, you're still arguing from the standpoint that I'm making fun of her natural eyebrows.

Which I'm not.

You're attacking appearances. How one dresses or applies makeup doesn't matter in the context of the conversation. These are are matters of personal taste. Why do we need to know your thoughts on this?

I'm making fun of her shallow decision making and poor choices.

Not really, though. You're just talking about how someone's personal taste doesn't align with your personal taste. This is like arguing about favorite colors. It's a weak position to argue as it's entirely subjective. It actively undermines any other argument you might be trying to make.

Of all the things to mention, and you're focused on eyebrows? You sound extremely biased because of this weak argument. It gives the impression that you share this same quality of being shallow. It serves as a potential indicator that you might be unable to pick out relevant detail in a conversation, which also makes you seem like a waste of time to communicate with.

If you're arguing another point this is detracting from that point. If you're not arguing another point, then this insipid opinion is irrelevant to the discussion.

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.

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.

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.