anonymouse
About
- Username
- anonymouse
- Joined
- Visits
- 59
- Last Active
- Roles
- member
- Points
- 1,817
- Badges
- 1
- Posts
- 7,053
Reactions
-
Apple's flavor of RCS won't support Google's end-to-end encryption extension
Our rescue? Don't you mean your rescue, Android users' rescue? Those of us living in the land of blue bubbles don't actually need rescuing at the moment, thank you very much.gatorguy said:
... So don't stake your hopes on Apple coming to our rescue riding a white horse. ...ericthehalfbee said:Apple basically said “fuck you” to Google.
I’ve repeatedly said Apple should counter Google’s shame campaign by announcing they’ll support RCS when Google opens up their RCS APIs for everyone. Including competitors like WhatsApp or Telegram.
Google has their own RCS APIs in Android but Samsung is the only one allowed to use them. Developers have asked and Google has done nothing to allow other Apps to implement RCS via their system and use E2EE.
So Apple did one better and said they’ll work with standards bodies to improve RCS.
Now Google’s hopes of a messaging duopoly are finished.
-
Apple's flavor of RCS won't support Google's end-to-end encryption extension
That's all part of routing messages.auxio said:
So I guess all devices are online and available to receive a message at all times? No? Then you need a server to store those encrypted messages, images, videos, etc until the device is available. Maybe even know how to route them to multiple recipients and on different carriers. Oh, and look, Google has a solution for you.anonymouse said:
The "server requirements of E2EE" are basically to route messages. If the devices sending and receiving aren't handling all the encryption/decryption themselves, it's not E2EE.auxio said:
Marketing? So that they look like the hero fighting against big bad Apple and winning. GG also mentioned in the other thread that carriers might be turning to them for the server requirements of E2EE, so that'd be worth a fair bit.Anilu_777 said:I still wonder why Google even cares about this and then why it’s pushing so hard. I don’t trust Google. -
Apple's flavor of RCS won't support Google's end-to-end encryption extension
The "server requirements of E2EE" are basically to route messages. If the devices sending and receiving aren't handling all the encryption/decryption themselves, it's not E2EE.auxio said:
Marketing? So that they look like the hero fighting against big bad Apple and winning. GG also mentioned in the other thread that carriers might be turning to them for the server requirements of E2EE, so that'd be worth a fair bit.Anilu_777 said:I still wonder why Google even cares about this and then why it’s pushing so hard. I don’t trust Google.
-
Apple considers $2B Apple TV+ streaming rights grab for Formula 1
Well, this is a streaming deal. My guess is that Sky would retain the broadcast rights they have now, which likely means you could still watch it on ESPN (in the US), but probably not streamed on ESPN.M68000 said:F1 is available now as it’s own streaming service. I’ve considered getting it. So this “deal” could mean that eventually the only place to get F1 would be on Apple ?? Not sure i like that.
-
Nearly every iPhone 15 & iPhone 15 Pro detail spilled by new leak
Depends on what Titanium alloy they are using. For example, grade 2 Ti alloy is relatively soft but grade 5 and grade 23 (medical grade) are much harder than grade 2.neilm said:Titanium looks great — when it’s new. But its surface hardness is poor, making Ti a scratch magnet. Hardness can be improved by applying a suitable coating, such as the black DLC on my Series 5 Apple Watch, which still looks new. But then, of course, it also looks like any other black finished metal.
