{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreib44zq7ye35vjkftidq2wnlg63oabcdknorc7uawp2k2uzbe5dha4",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3ml36cra47d62"
  },
  "path": "/t/apple-confirms-rcs-e2ee-will-ship-with-ios-26-5/37634#post_3",
  "publishedAt": "2026-05-05T02:24:32.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "Pretty bitter sweet. Obviously encryption is better than no encryption. Though this will likely mean the end of being able to use a GrapheneOS phone without play services always running - at least while telling yourself you’re not giving up anything privacy/security wise.\n\nTo get RCS to work, you need Play Services and Google Messages both installed on your Owner profile. You need to also hand over network, phone, and, SMS permissions, and likely device identifiers to Google (depending on carrier).\n\nIf you intend to know who’s texting you, then you need to provide permission to contacts as well. It would be pretty ridiculous declare contact scopes for each person that you message. I’d have to declare hundreds just to read old Messages.\n\nAt that point, why even bother storing your contacts outside of Google if you’re going to let them see your contacts anyway. Even without signing into an account for Google Messages, they’ll still be able fingerprint you off your phone number, device identifiers, IP addresses etc.\n\nMight as well use Google Voice at that point due to already trusting Google with your contacts, phone, and messages.\n\nAnd just like that, you’re back in the Google ecosystem.",
  "title": "Apple Confirms RCS E2EE Will Ship with iOS 26.5"
}