I’ll take one of each, please.

I don’t care what you say, the Apple store circa 2001 is iconic and definitely has that “lickability” factor that Jobs loved so much about the original OS X’s Aqua UI.

When did code reviews become this weird?

my experience is such that people don’t get these sweeping bans for having opinions. They get them for acting like sociopathic aggressive individuals.

And based on what I’m seeing when I check folks’ profiles reiterating the same story… Yep it checks out more often than not. There’s no discourse on the internet when it consists of calling people slurs in a weird barrage of insults. Those are the people who get banned here or there.

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.

For now. Google is locking down certificates in Android 14 which absolutely cannot be changed even by devs (barring exploits, which will be patched because this is Alphabet’s bread and butter on the line).

Google has put into place infrastructure to lock apps down as well with its App Bundles to replace APKs. And, wouldn’t you know it, they just so happen to rely on Google to be functional and even built! Custom made for your device and configuration and account. What a coincidence that you can’t rip that off your device and widely share it without massive workarounds. And even then, with Google clamping down on CAs….

People best become acquainted with ROMs again. Providing, of course, that Android doesn’t start employing anti-root tactics like Apple does which essentially eliminates the possibility of almost everybody actually owning their devices.