{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicsd3rw3jbu2anpnyjsrngqpglbqir5zszhyjknfynfcd6dpimsca",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mmjnad2q3cg2"
  },
  "path": "/t/is-the-best-sms-app-a-closed-source-one-with-permissions-revoked/38080#post_8",
  "publishedAt": "2026-05-23T13:03:26.000Z",
  "site": "https://discuss.privacyguides.net",
  "tags": [
    "messaging repo",
    "Twitter/X",
    "(click for more details)"
  ],
  "textContent": "Aflame-Blighted:\n\n> I know it’s not high on their priority list, but hopefully it gets a revamp one day.\n\nThey are actually currently in the process of a full rewrite to Kotlin/Compose. There’s a couple places you can keep an eye on, but mainly just the issues and pull requests in the messaging repo. They just merged their first PR yesterday, but obviously be patient they’ll probably announce it on their Twitter/X and in their forum when it’s ready.\n\nTo add to this they do have future plans to add RCS E2EE as stated on their Twitter/X:\n\n> We’re open to collaboration but it’s not clear in what way we could work together. We do plan to make an SMS/MMS/RCS app supporting MLS end-to-end encryption for RCS compatible with Google Messages and future iOS MLS support. That would not be a Signal alternative/competitor.\n\nOff-topic (click for more details)",
  "title": "Is the best SMS app a closed source one with permissions revoked?"
}