I hear what you’re saying, but that is exactly why Discord is shit for official communities like in the meme. There’s no reason why an open source project should rely on Discord for troubleshooting and feature requests and enthusiasm. Discord was meant for things like video games and friend chats, not instances where data discovery is paramount to growing the community.

There is a reason thar Discord communities trend toward toxic, and it is the insular weirdness that the platform enables and reinforces. Forums make much more sense for projects. Discord ends up with a bunch of no lifers ruining the communities. Been through it far too often with things like genre appreciation groups to open source projects. Reminds me of being a kid and encountering the, frankly, losers chasing people out of IRC.

This is literally the reason Apple changes the bubble color. iMessage is encrypted by default and uses normal data instead of MMS. That’s the indicator.

This entire spiel about bubble color envy is ridiculous. Features are the separation. The media will whip things up with their sample size of a handful of cherry picked anecdotes. But almost every teen has an iPhone and uses iMessage in the USA. Apple has over 80% of that market.

What Google wants is for Apple to implement Google’s proprietary RCS implementation, not RCS proper. Because RCS proper lacks a lot of features that people take for granted with iMessage. That is presumably one reason Google forked it and requires it to run through their proprietary middleware.

Edit: Don’t get me wrong. I would love for an open standard to overtake the proprietary bits from both Apple and Google. But Google is disingenuous here. They are complaining because, despite their efforts, they can’t crack the market. Teens aren’t bitting for Android. iMessage has network effect going on, so Google is trying to crack that open since they can’t get a compelling overall product and ecosystem for a valuable demographic.

I’d rather there be open standards. But that means Google RCS has to change as well.

deleted by creator

I’m so happy to see someone else is finally talking about this. RCS, as implemented by Google, is distinct from the actual open RCS standard. Google added a proprietary middle layer which is how they get features working which RCS doesn’t support.

And that proprietary middle layer (Jibe being part of it) is why there aren’t a million third party RCS clients out there. Google must give API access. They are gatekeepers. And they only share keys with strategic partners (Samsung being one of them, telcos with their own app like Verizon used to have being another).

But in the end Google did what Google does best: fragmented a product. And now Google holds the leash for RCS proper. I bet Apple isn’t too keen to route all customer data through Google servers even when encrypted. Because it’s another piece that Apple doesn’t control.