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.
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.
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.
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.
Plex To Launch a Store For Movies and TV Shows (entertainment.slashdot.org)
Eminem concert (lemmy.world)