• Encryption comes to RCS at last on iPhones.

    From Carlos E.R.@21:1/5 to All on Mon Mar 17 19:40:26 2025
    XPost: misc.phone.mobile.iphone

    <https://gizmodo.com/apple-will-fully-encrypt-rcs-messages-between-androids-and-iphones-2000576303>


    *Apple Will Fully Encrypt RCS Messages Between Androids and iPhones*
    Texting a Green Bubble will feel as native as engaging another iPhone
    user on iMessage.

    By Florence Ion Published March 14, 2025

    It’s been less than a year since iPhones were granted the ability to
    send messages to Green Bubbles unfettered, and only now is proper
    end-to-end encryption making an appearance. Better late than never. The
    GSM Association announced new specifications for RCS, requiring it to be end-to-end encrypted (E2EE) based on a protocol called the Messaging
    Layer Security (MLS). The organization laid out the plan in a press
    release, citing the need to provide users with “the highest level of
    privacy and security.”

    The new specifications will use RCS Universal Profile 3.0, a
    cross-platform encryption protocol that will make it easier for iPhones
    and Android devices to identify each other. The profile allows for
    richer deep linking, better audio codec for voice messaging between
    parties, and ease of unsubscribing from a subscription text thread. The protocol will continue to support the rest of the high-resolution
    messaging capabilities introduced in the initial rollout of the RCS
    protocol, including tap-backs, read receipts, typing indicators, group messaging, and the ability to send photos without dialing down the quality.

    On Apple’s end, the company confirmed that it would support end-to-end encrypted RCS messaging and extend it to iOS, iPadOS, macOS, and watchOS
    in future software updates. “End-to-end encryption is a powerful privacy
    and security technology that iMessage has supported since the beginning,
    and now we are pleased to have helped lead a cross-industry effort to
    bring end-to-end encryption to the RCS Universal Profile published by
    the GSMA,” Apple spokesperson Shane Bauer told The Verge. As for
    Google’s side of things, Android users already have E2EE between them by default for RCS texts.


    (... continues on the link)


    What the article does not clarify is whether Android will also implement
    this (Google uses its own encryption method), and so what will happen to
    cross platform messages.


    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Carlos E.R. on Mon Mar 17 20:34:40 2025
    XPost: misc.phone.mobile.iphone

    On Mon, 17 Mar 2025 19:40:26 +0100, Carlos E.R. wrote :

    Texting a Green Bubble will feel as native as engaging another iPhone
    user on iMessage.

    While this is welcome news, my instant reaction was "OMG", Apple was
    forced, finally, to make their iPhone begin to work in the real world.

    This is going to fundamentally impact Apple's strategy of never testing the iPhone in the real world (which is one reason why iOS is so damn buggy).

    But more than the impact of having to test an iPhone with other phones,
    Apple is slowly being forced to do what's right for its customer base.

    No wonder Federighi said there's nothing that terrifies him more than Apple actually working in the real world when he was asked about this long ago.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Carlos E.R. on Mon Mar 17 21:32:22 2025
    XPost: misc.phone.mobile.iphone

    On 17.03.25 19:40, Carlos E.R. wrote:
    As for
    Google’s side of things, Android users already have E2EE between them by default for RCS texts.

    This is simply wrong.

    What the article does not clarify is whether Android will also implement
    this (Google uses its own encryption method), and so what will happen to cross platform messages.

    They will not because Apple will not apply a proprietary encryption
    under Google's control.

    One basic and very important thing will stay: The green Android bubbles
    on an iPhone will nourish the inferiority complex of Android users even
    more.


    --
    "Roma locuta, causa finita." (Augustinus)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alan@21:1/5 to Marion on Mon Mar 17 13:43:32 2025
    XPost: misc.phone.mobile.iphone

    On 2025-03-17 13:34, Marion wrote:
    On Mon, 17 Mar 2025 19:40:26 +0100, Carlos E.R. wrote :

    Texting a Green Bubble will feel as native as engaging another iPhone
    user on iMessage.

    While this is welcome news, my instant reaction was "OMG", Apple was
    forced, finally, to make their iPhone begin to work in the real world.

    "Forced"?

    By whom?


    This is going to fundamentally impact Apple's strategy of never testing the iPhone in the real world (which is one reason why iOS is so damn buggy).

    Look: more assertions for the "man" who claims he only states facts.

    :-)


    But more than the impact of having to test an iPhone with other phones,
    Apple is slowly being forced to do what's right for its customer base.
    No wonder Federighi said there's nothing that terrifies him more
    than Apple
    actually working in the real world when he was asked about this long ago.

    Apple never had a problem with the concept of RCS...

    ...but didn't want its encryption to be controlled by one company.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Carlos E.R. on Tue Mar 18 06:58:18 2025
    XPost: misc.phone.mobile.iphone

    On 17.03.25 19:40, Carlos E.R. wrote:
    <https://gizmodo.com/apple-will-fully-encrypt-rcs-messages-between-androids-and-iphones-2000576303>


    *Apple Will Fully Encrypt RCS Messages Between Androids and iPhones*
    Texting a Green Bubble will feel as native as engaging another iPhone
    user on iMessage.

    What Androidcentral says.

    "Encrypted RCS messages between platforms are coming, but this won't end
    the messaging wars"

    https://www.androidcentral.com/apps-software/encrypted-rcs-messages-between-platforms-are-coming-but-this-wont-end-the-messaging-wars?

    IMHO they understand much better what is going on.


    --
    "Roma locuta, causa finita." (Augustinus)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to badgolferman on Tue Mar 18 06:27:15 2025
    XPost: misc.phone.mobile.iphone

    On Tue, 18 Mar 2025 01:32:00 -0000 (UTC), badgolferman wrote :


    Google's side of things, Android users already have E2EE between them by >>> default for RCS texts.

    This is simply wrong.

    Are you sure?
    https://support.google.com/messages/answer/10252671?hl=en

    Hi badgolferman (and knowledgeable Android users like Andy & Carlos),

    I don't keep up on RCS since it does nothing for me that I can't get with WhatsApp (grandkids are sending me videos from iPhones all day, every day).

    And when I last asked Andy what he pined for in RCS, it was "net-based"
    texting (SMS/MMS) because of how they're charged for texts in the UK.

    In the US, most of us have unlimited everything, so we can text long videos
    all day every day between Android & iOS users, so I don't need RCS.

    However... it's still good to be kept informed. So I read the original
    article and I read your article and it seems that this is a summary:

    1. Your article says if you use the Google Messages app on Android (which I
    do not use) & if everyone you text is using it, then indeed, it's E2EE.

    2. The OP's article seems to say iPhones will scramble (on the device)
    their messages to Android RCS users (using RCS universal profile 3.0 which utilizes Messaging Layer Security (MLS) protocol), where the unscrambling
    will be done on the Android users' device, with nobody being able to read
    it in between.

    Both Google & Apple have confirmed support for RCS Universal Profile 3.0
    and E2EE, but both need to integrate it (apparently) into their platforms.

    The key is both have work to do since it's apparently a new standard.
    Also every messaging app has to do some work to incorporate the two things.

    RCS Universal Profile 3.0 added standardized end-to-end encryption (E2EE).
    MLS (Messaging Layer Security) is the specific cryptographic protocol.

    In summary, I could very well be wrong because I have no need for the encryption but I do have a fuzzy video problem & others have the data cost.

    So I'm trying to understand how this new agreement fixes these two issues:
    1. Fuzzy video
    2. Cost for messages

    While MMS is handled by the cellular carrier, RCS is handled by the
    cellular data plan, so when both phones are using RCS, then the video will
    be sent via the carrier cellular (or Wi-Fi) data plans using modern codecs.

    Presumably the cost for people like Andy will be in their data plan?
    And presumably fuzzy baby videos for people like me will go away because
    RCS data presumably has much larger carrier (or Wi-Fi) bandwidth so videos won't be drastically shrunk like they were with MMS?

    Is this quick assessment of those two articles anywhere near accurate yet?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Marion on Tue Mar 18 07:25:55 2025
    XPost: misc.phone.mobile.iphone

    Marion wrote:

    when I last asked Andy what he pined for in RCS, it was "net-based"
    texting (SMS/MMS) because of how they're charged for texts in the UK.

    Since apple implemented RCS, I haven't 'hounded' my iPhone-using friends
    to upgrade/enable it, but they do seem to be doing it.

    If the RCS 3.0 protocol exists, there's no reason for Google to stick
    with their proprietary encryption, so it feels like once apple and
    google have been through a round of upgrades, we will get
    interoperability (which we already have) with encryption (which we
    don't) ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Tue Mar 18 12:12:16 2025
    XPost: misc.phone.mobile.iphone

    Carlos E.R., 2025-03-17 19:40:

    <https://gizmodo.com/apple-will-fully-encrypt-rcs-messages-between-androids-and-iphones-2000576303>
    [...]
    What the article does not clarify is whether Android will also implement
    this (Google uses its own encryption method), and so what will happen to cross platform messages.

    Since MLS will become part of RCS, Google would be stupid not to
    implement it. In fact when MLS is implemented, there is no need to keep
    the proprietary solution in place - maybe just as a fall back for old
    devices.


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Tue Mar 18 12:15:54 2025
    XPost: misc.phone.mobile.iphone

    Jörg Lorenz, 2025-03-17 21:32:

    On 17.03.25 19:40, Carlos E.R. wrote:
    As for
    Google’s side of things, Android users already have E2EE between them by >> default for RCS texts.

    This is simply wrong.

    No, this is correct. When you communicate with other Google users, E2EE
    is default for RCS.

    However Googles E2EE in RCS is a properietary solution yet. But I
    assume, that Google will adopt MLS as well and hopefully this will soon
    be the common standard.

    What the article does not clarify is whether Android will also implement
    this (Google uses its own encryption method), and so what will happen to
    cross platform messages.

    They will not because Apple will not apply a proprietary encryption
    under Google's control.

    You confused some things here: the question was, if *Google* will
    implement MLS as well. And I don't see any reasone, why Google should
    not change to MLS. MLS makes their proprietary solution obsolete.

    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Arno Welzel on Tue Mar 18 13:31:30 2025
    XPost: misc.phone.mobile.iphone

    On Tue, 18 Mar 2025 12:15:54 +0100, Arno Welzel wrote :


    You confused some things here: the question was, if *Google* will
    implement MLS as well. And I don't see any reason, why Google should
    not change to MLS. MLS makes their proprietary solution obsolete.

    Joerg is a moron. You're correct about Google MLS adoption, Arno.

    Google is already on record for saying they'll implement the new MLS.
    <https://daringfireball.net/#:~:text=%E2%80%9CWe're%20excited%20to%20have,implement%20and%20extend%20this%20important>
    "Weve always been committed to providing a secure messaging experience,
    and Google Messages users have had end-to-end encrypted (E2EE) RCS
    messaging for years," Google spokesperson Ed Fernandez told The Verge.
    "We're excited to have this updated specification from GSMA and work
    as quickly as possible with the mobile ecosystem to implement and
    extend this important user protection to cross-platform RCS messaging."

    Did I mention Joerg is an idiot yet? It's not worth responding to him.
    Or to Alan Baker. They don't have the capacity to understand, or learn.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Arno Welzel on Tue Mar 18 13:44:52 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    On Tue, 18 Mar 2025 12:12:16 +0100, Arno Welzel wrote :


    What the article does not clarify is whether Android will also implement
    this (Google uses its own encryption method), and so what will happen to
    cross platform messages.

    Since MLS will become part of RCS, Google would be stupid not to
    implement it. In fact when MLS is implemented, there is no need to keep
    the proprietary solution in place - maybe just as a fall back for old devices.

    Google is already on record for adopting MLS the same time Apple does.
    What's interesting though is how it will work when the Internet sucks.

    Nothing can happen until the two *devices* exchange the keys, right?

    Apparently the fallback will be two-fold if there is no Internet:
    a. Queue the message for a while, and, if necessary...
    b. Eventually fall back to SMS/MMS

    But the fallback will be *different* depending on WHO is offline!

    I use the last known good version of PulseSMS so I don't have RCS, but apparently those with Google Messages have to set an option to get that.
    Automatically resend as SMS/MMS = on/off
    So if the sender is offline, then it will queue or fallback to SMS/MMS.

    But if the recipient is offline, then the carrier's RCS infrastructure
    (or Google's Jibe platform) will store the message until the recipient goes back online (or until the RCS carrier's expiry time has elapsed).

    But wait! How can the RCS infrastructure store a message if keys haven't
    been exchanged? It turns out keys are exchanged the FIRST time the two
    people communicate. So the keys are already stored on each device.

    But wait. That's not all. They keys aren't kept forever, it turns out!
    They're refreshed on some schedule I haven't been able to figure out yet.

    The refresh seems to happen on 'context' changes, such as
    a. Users adding or removing participants from a group conversation.
    b. Periodic key rotations for enhanced security.
    c. Detection of potential security vulnerabilities.
    etc.

    The plot thickens...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Andy Burns on Tue Mar 18 13:17:45 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    On Tue, 18 Mar 2025 07:25:55 +0000, Andy Burns wrote :


    when I last asked Andy what he pined for in RCS, it was "net-based"
    texting (SMS/MMS) because of how they're charged for texts in the UK.

    Since apple implemented RCS, I haven't 'hounded' my iPhone-using friends
    to upgrade/enable it, but they do seem to be doing it.

    Thanks. You are the first person to describe to me WHY you wanted RCS more
    than a year or so ago, as I didn't see what it did that PulseSMS didn't do.
    <https://home.pulsesms.app/overview/>
    Even the iOS messages app doesn't do anything that PulseSMS doesn't do (although to do it requires an account on a server just like with iOS).

    The main difference, I think, once this is implemented, is we'll have LOTS
    of messaging apps that can handle RCS/MMS while iOS will still have only 1.

    It looks like when the new RCS/MLS stuff is included by both Apple and the Android messaging apps, then our new terminology can be SMS/MMS/RCS/MLS
    (or maybe just SMS/MMS/RCS since the MLS is just the protocol being used).

    Apparently the (future) flow is thus for Android to iOS (RCS/MLS):
    1. The user composes a message in their chosen messaging app.
    2. The app determines if the recipient (iOS user) supports RCS/MLS.
    3. The Android device and the iOS device perform the MLS key exchange
    to establish shared secret keys. This happens after the RCS/MLS
    status is determined and before the message is encrypted.
    4. The message is encrypted end-to-end using MLS on the Android device.
    5. The encrypted message is sent from the Android device to the T-Mobile
    RCS infrastructure or to Jibe's RCS hub, depending on carrier setup.
    6. T-Mobile or Jibe routes the RCS/MLS message to Apple's iMessage servers.
    7. Apple's servers receive the RCS/MLS message.
    8. The Apple servers then route the message to the destination iOS device.
    9. The iOS device receives the encrypted message.
    10. The iOS device decrypts the message using MLS.
    11. The decrypted message is displayed in the iOS messaging app.

    It's almost the same flow from iOS to Android (RCS/MLS):
    1. The user composes a message in the iOS messaging app.
    2. The iOS device determines if the Android recipient supports RCS/MLS.
    3. The iOS device and the Android device perform the MLS key exchange
    to establish shared secret keys.
    4. The message is encrypted end-to-end using MLS on the iOS device.
    5. The encrypted message is sent to Apple's iMessage servers.
    6. Apple's servers route the RCS/MLS message to the T-Mobile
    RCS infrastructure or to Jibe's RCS hub.
    7. T-Mobile or Jibe routes the RCS/MLS message to the Android device.
    8. The Android device receives the encrypted message.
    9. The Android device decrypts the message using MLS.
    10. The decrypted message is displayed in the Android messaging app.

    Notice that iOS handles things at the OS level while Android initially
    handles things more at the app level, but both interact with the OS.

    For example, Google Messages performs checks to see if the recipient's
    phone number is registered for RCS while Apple's iMessage system will be responsible for checking if a recipient is RCS-capable.

    Also, key exchange will, apparently,l be done slightly differently, again mainly because for Android most of the heavy lifting is done by the app,
    while for iOS, apparently, the security stuff is handled in the OS.

    Android to Android is simpler as there's no Apple server involved.
    1. The Android user composes a message in their chosen messaging app.
    2. The app determines if the Android recipient supports RCS/MLS.
    3. The two Android devices perform the MLS key exchange to establish
    shared secret keys.
    4. The message is encrypted end-to-end using MLS on the sender's device.
    5. The encrypted message is sent to the carrier's RCS infrastructure
    or Jibe's RCS hub.
    6. The carrier/Jibe routes the message to the recipient's Android device.
    7. The recipient's Android device decrypts the message using MLS.
    8. The decrypted message is displayed in the recipient's messaging app.

    Note that for Android-to-Android, the message stays within the RCS network.
    But for iOS to iOS, the RCS/MLS flowchart is more complicated I think.

    1. The iOS user composes a message in the messaging app.
    2. The iOS device determines if the iOS recipient supports RCS/MLS.
    3. The two iOS devices perform the MLS key exchange.
    4. The message is encrypted end-to-end using MLS.
    5. The encrypted message is sent to Apple's iMessage servers.
    6. Apple's servers route the message to the recipient's iOS device.
    7. The recipient's iOS device decrypts the message.
    8. The decrypted message is displayed.

    But if iMessage is being used:
    If both iOS users are on iMessage, the process is similar to the
    RCS/MLS process above, but it uses Apple's proprietary encryption
    and key exchange instead.

    If the RCS 3.0 protocol exists, there's no reason for Google to stick
    with their proprietary encryption, so it feels like once apple and
    google have been through a round of upgrades, we will get
    interoperability (which we already have) with encryption (which we
    don't) ...

    Google is already on record for ditching the current system, I think:
    <https://www.msn.com/en-us/news/technology/apple-sharing-rcs-encryption-with-android-users/ar-AA1AWeK3>
    <https://www.zdnet.com/article/why-apples-rcs-encryption-move-is-a-privacy-game-changer-for-your-texts/>
    "Google also confirmed to The Verge that it would support
    the new standard, making it the first time both Apple
    and Google did so at the same time."

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Marion on Tue Mar 18 18:20:50 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    Marion wrote:

    What's interesting though is how it will work when the Internet sucks.

    Nothing can happen until the two devices exchange the keys, right?

    Does the internet suck sufficiently to stop you logging in to amazon,
    that needs a key exchange ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Arno Welzel on Tue Mar 18 22:25:56 2025
    XPost: misc.phone.mobile.iphone

    On 18.03.25 12:15, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-17 21:32:

    On 17.03.25 19:40, Carlos E.R. wrote:
    As for
    Google’s side of things, Android users already have E2EE between them by >>> default for RCS texts.

    This is simply wrong.

    No, this is correct. When you communicate with other Google users, E2EE
    is default for RCS.

    Bullshit. The encryption is broken up at network borders.

    You confused some things here: the question was, if *Google* will
    implement MLS as well. And I don't see any reasone, why Google should
    not change to MLS. MLS makes their proprietary solution obsolete.

    Who cares? You do not understand what the core of the whole story is.
    Apple users simply do not want to use RCS. With or without enryption.
    It is an inferior service with absolutely no added value.


    --
    "Roma locuta, causa finita." (Augustinus)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Arno Welzel on Tue Mar 18 22:31:52 2025
    XPost: misc.phone.mobile.iphone

    On 18.03.25 12:15, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-17 21:32:

    On 17.03.25 19:40, Carlos E.R. wrote:
    As for
    Google’s side of things, Android users already have E2EE between them by >>> default for RCS texts.

    This is simply wrong.

    No, this is correct. When you communicate with other Google users, E2EE
    is default for RCS.

    BTW: Almost nobody trusts Google.


    --
    "Roma locuta, causa finita." (Augustinus)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to All on Tue Mar 18 23:11:06 2025
    XPost: misc.phone.mobile.iphone

    On 2025-03-18 22:25, Jörg Lorenz wrote:
    On 18.03.25 12:15, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-17 21:32:

    On 17.03.25 19:40, Carlos E.R. wrote:
    As for
    Google’s side of things, Android users already have E2EE between them by >>>> default for RCS texts.

    This is simply wrong.

    No, this is correct. When you communicate with other Google users, E2EE
    is default for RCS.

    Bullshit. The encryption is broken up at network borders.

    You confused some things here: the question was, if *Google* will
    implement MLS as well. And I don't see any reasone, why Google should
    not change to MLS. MLS makes their proprietary solution obsolete.

    Who cares? You do not understand what the core of the whole story is.
    Apple users simply do not want to use RCS. With or without enryption.
    It is an inferior service with absolutely no added value.

    ROTFL!

    I have a Swiss friend who told me how a friend of his using an iphone is
    very happy now because she now has RCS and can exchange messages with
    photos and videos with friends of hers that may or may not have an iphone.

    I forget why it has to be rcs. He told the history, but I do not
    remember it. Maybe they don't have WhatsApp, which the Swiss authorities
    are against :-p

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Carlos E.R. on Wed Mar 19 02:08:31 2025
    XPost: misc.phone.mobile.iphone

    On 18.03.25 23:11, Carlos E.R. wrote:
    On 2025-03-18 22:25, Jörg Lorenz wrote:
    On 18.03.25 12:15, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-17 21:32:

    On 17.03.25 19:40, Carlos E.R. wrote:
    As for
    Google’s side of things, Android users already have E2EE between them by
    default for RCS texts.

    This is simply wrong.

    No, this is correct. When you communicate with other Google users, E2EE
    is default for RCS.

    Bullshit. The encryption is broken up at network borders.

    You confused some things here: the question was, if *Google* will
    implement MLS as well. And I don't see any reasone, why Google should
    not change to MLS. MLS makes their proprietary solution obsolete.

    Who cares? You do not understand what the core of the whole story is.
    Apple users simply do not want to use RCS. With or without enryption.
    It is an inferior service with absolutely no added value.

    ROTFL!

    I have a Swiss friend who told me how a friend of his using an iphone is
    very happy now because she now has RCS and can exchange messages with
    photos and videos with friends of hers that may or may not have an iphone.

    For this purpose a selection of messengers exist for many years which
    are more versatile and much more trustworthy.

    I forget why it has to be rcs. He told the history, but I do not
    remember it. Maybe they don't have WhatsApp, which the Swiss authorities
    are against :-p

    More nonsense.


    --
    "Roma locuta, causa finita." (Augustinus)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Andy Burns on Wed Mar 19 02:38:45 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    On Tue, 18 Mar 2025 18:20:50 +0000, Andy Burns wrote :


    What's interesting though is how it will work when the Internet sucks.

    Nothing can happen until the two devices exchange the keys, right?

    Does the internet suck sufficiently to stop you logging in to amazon,
    that needs a key exchange ...

    I'm not sure I understand the question, but I was just trying to figure out
    how RCS/MLS works, in terms of what happens if one or both are offline.

    But after searching for how RCS/MLS works, I found they have a queuing mechanism, a key exchange store mechanism, & a fallback to SMS/MMS
    mechanism. This, of course, is to be expected. I just didn't know it.

    Now I do. (At least to a level useful to me on a flaky connection.)

    Since I'm across the pond from you, I don't pay extra for anything, as we typically get unlimited everything for about $25/month per device, so my
    only need for RCS/MLS is to get clear non-blurry media from iPhones.

    Personally, even as I'm a privacy guy, I don't care about encryption.
    But it would be nice to be able to communicate with iPhone users.
    Without having to use WhatsApp (which is better in all ways than Messages).

    So I'll install an RCS/MLS capable messenger on Android when they arrive.

    The problem for me is I really love the functionality of the last known
    good version of PulseSMS; which doesn't support RCS.

    When there's a non-Google messenger for Android that supports RCS/MLS,
    that's the one I'll test out, as I've tested all the free SMS/MMS apps.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to All on Wed Mar 19 11:07:40 2025
    XPost: misc.phone.mobile.iphone

    On 2025-03-19 02:08, Jörg Lorenz wrote:
    On 18.03.25 23:11, Carlos E.R. wrote:
    On 2025-03-18 22:25, Jörg Lorenz wrote:
    On 18.03.25 12:15, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-17 21:32:

    On 17.03.25 19:40, Carlos E.R. wrote:
    As for
    Google’s side of things, Android users already have E2EE between them by
    default for RCS texts.

    This is simply wrong.

    No, this is correct. When you communicate with other Google users, E2EE >>>> is default for RCS.

    Bullshit. The encryption is broken up at network borders.

    You confused some things here: the question was, if *Google* will
    implement MLS as well. And I don't see any reasone, why Google should
    not change to MLS. MLS makes their proprietary solution obsolete.

    Who cares? You do not understand what the core of the whole story is.
    Apple users simply do not want to use RCS. With or without enryption.
    It is an inferior service with absolutely no added value.

    ROTFL!

    I have a Swiss friend who told me how a friend of his using an iphone is
    very happy now because she now has RCS and can exchange messages with
    photos and videos with friends of hers that may or may not have an iphone.

    For this purpose a selection of messengers exist for many years which
    are more versatile and much more trustworthy.

    For some reason, this person can not use them. One reason is that she
    has to find out which messenger the other side is using; being several,
    it becomes more useful to use RCS which everybody has.


    I forget why it has to be rcs. He told the history, but I do not
    remember it. Maybe they don't have WhatsApp, which the Swiss authorities
    are against :-p

    More nonsense.

    Whatsapp is forbidden for the Swiss military. And also other
    institutions. This is a known fact.

    Hello human, I'm an AI chatbot powered by GPT-4o mini. Ask me anything!

    Why is whatsapp banned for the Swiss military?

    WhatsApp is banned for the Swiss military mainly for security and data protection reasons. Swiss authorities have expressed concerns about
    information security and privacy in messaging applications that do not
    meet the security standards required for handling sensitive information.

    Given that the military handles confidential and strategic data, the use
    of communication channels that offer a higher level of security and
    control over information is preferred. This is part of a broader effort
    to protect the integrity of military operations and national
    information. If you have further questions on this topic or would like
    to know more, I would be happy to help!

    Translated with DeepL.com (free version)


    They prefer Threema, but it is payware, so not everybody has it.


    It is simply a fact, it is a person I know about by another person who
    is totally sold on RCS, and is Swiss. >:-P



    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Carlos E.R. on Wed Mar 19 10:32:24 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    Carlos E.R. wrote:

    Marion wrote:

    Since I'm across the pond from you, I don't pay extra for anything, as we
    typically get unlimited everything for about $25/month per device

    $25 for everything?
    Unlimited calls+texts with a fixed block of e.g. 20GB data is pretty
    cheap here (around £10/month), but unlimited data was expensive (e.g.
    upwards of £40/month)

    Now there are a handful offering unlimited everything for £15/month.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Marion on Wed Mar 19 11:20:43 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    On 2025-03-19 03:38, Marion wrote:
    On Tue, 18 Mar 2025 18:20:50 +0000, Andy Burns wrote :


    What's interesting though is how it will work when the Internet sucks.

    Nothing can happen until the two devices exchange the keys, right?

    Does the internet suck sufficiently to stop you logging in to amazon,
    that needs a key exchange ...

    I'm not sure I understand the question, but I was just trying to figure out how RCS/MLS works, in terms of what happens if one or both are offline.

    But after searching for how RCS/MLS works, I found they have a queuing mechanism, a key exchange store mechanism, & a fallback to SMS/MMS
    mechanism. This, of course, is to be expected. I just didn't know it.

    Now I do. (At least to a level useful to me on a flaky connection.)

    Since I'm across the pond from you, I don't pay extra for anything, as we typically get unlimited everything for about $25/month per device, so my
    only need for RCS/MLS is to get clear non-blurry media from iPhones.

    $25 for everything?

    August-September 2023 I needed to purchase a prepaid SIM card for a
    month in Canada. I don't remember what I paid at Bell Canada, I think it
    was about $50, and it did NOT include phone calls to Europe. Other
    cheaper providers in the mall had the same limitation, no phone calls to
    Europe included.

    Prior to that SIM card I had a prepaid card bought on Amazon Spain from T-mobile, and it was problematic. Also no phone calls to Europe,
    something that a traveller needs.


    Personally, even as I'm a privacy guy, I don't care about encryption.
    But it would be nice to be able to communicate with iPhone users.
    Without having to use WhatsApp (which is better in all ways than Messages).

    So I'll install an RCS/MLS capable messenger on Android when they arrive.

    The problem for me is I really love the functionality of the last known
    good version of PulseSMS; which doesn't support RCS.

    When there's a non-Google messenger for Android that supports RCS/MLS,
    that's the one I'll test out, as I've tested all the free SMS/MMS apps.

    Why would anybody write a messenger to compete with the system one made
    by Google, that has all the features? I understand you don't want it,
    but crossplatform RCS exists for about a year and you have not found any
    other messenger yet.

    Maybe Samsung could write one, but AFAIK they gave up.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Carlos E.R. on Wed Mar 19 17:07:53 2025
    XPost: misc.phone.mobile.iphone

    On 19.03.25 11:07, Carlos E.R. wrote:
    On 2025-03-19 02:08, Jörg Lorenz wrote:
    On 18.03.25 23:11, Carlos E.R. wrote:
    I forget why it has to be rcs. He told the history, but I do not
    remember it. Maybe they don't have WhatsApp, which the Swiss authorities >>> are against :-p

    More nonsense.

    Whatsapp is forbidden for the Swiss military. And also other
    institutions. This is a known fact.

    RCS is forbidden as well. Your counter party is obviously not member of
    a security related service.

    BTW: You look very childish. Really. And you must be a bored old man.


    --
    "Roma locuta, causa finita." (Augustinus)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Andy Burns on Wed Mar 19 15:58:51 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    On Wed, 19 Mar 2025 10:32:24 +0000, Andy Burns wrote :


    Since I'm across the pond from you, I don't pay extra for anything, as we >>> typically get unlimited everything for about $25/month per device

    $25 for everything?
    Unlimited calls+texts with a fixed block of e.g. 20GB data is pretty
    cheap here (around L10/month), but unlimited data was expensive (e.g.
    upwards of L40/month)

    Now there are a handful offering unlimited everything for �15/month.

    I think Andy pays less than I do given neither of us needs "unlimited" data anyway. I use a few GB per month, but I could limit that if I wanted to.
    So I really only "need" about 1GB/month as does my wife. Usually even less.

    The kids are a different story, as all of you with kids already know.

    I used to have "limited data" of 4GB/month (which was more than enough)
    until T-Mobile merged with Sprint and apparently, to even out all their inconsistent plans, they gave EVERYONE a freebie of unlimited data for the
    same price that they were already paying for whatever plan they were on.

    As far as I know, EVERYONE on T-Mobile (postpaid) in the USA got this.
    So I'm kind of "grandfathered" into that plan which is why I keep it even
    as my kids have long since moved out of the house & have their own kids.

    But I just looked up T-Mobile's CURRENT family plan for four people:
    "Essentials Saver Family Plan: $100/month for four lines.
    Includes unlimited talk, text, and data with 50GB of premium data"
    <https://www.whistleout.com/CellPhones/Guides/best-t-mobile-family-plans>

    Of course, there is about $20 in taxes added to that so it's $120/month. Premium data appears to be "prioritized data" when I looked it up.

    Back to my $100 plan, I get free roaming in the USA and Europe with it.

    Since I'm a stickler for the details, to more completely answer Carlos' question, not everything is unlimited. For example, the hotspot/tethering
    is limited to 5GB/month and when I travel, mostly to Germany, phone calls
    are 25 cents per minute but I still get free data & text when traveling.

    That $100 turns into $120 with taxes, which I think is a rather expensive
    plan for the USA, is it not? I don't know. I haven't looked in years.

    What are other people paying for a 4-line plan?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Java Jive@21:1/5 to Andy Burns on Wed Mar 19 16:55:45 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    On 2025-03-19 10:32, Andy Burns wrote:
    Carlos E.R. wrote:

    Marion wrote:

    Since I'm across the pond from you, I don't pay extra for anything,
    as we
    typically get unlimited everything for about $25/month per device

    $25 for everything?
    Unlimited calls+texts with a fixed block of e.g. 20GB data is  pretty
    cheap here (around £10/month), but unlimited data was expensive (e.g. upwards of £40/month)

    Now there are a handful offering unlimited everything for £15/month.

    Yes, for example iDMobile, £15pm for unlimited data, minutes, & texts.
    As landlines are pretty useless around here, this is my broadband
    connection, using their SIM in a USB stick in my router.

    If 120GB, unlimited calls and texts, would do, I could go as low as £10pm.

    --

    Fake news kills!

    I may be contacted via the contact address given on my website:
    www.macfh.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Nick Cine@21:1/5 to Tweed on Wed Mar 19 11:48:05 2025
    XPost: uk.telecom.mobile, misc.phone.mobile.iphone

    On Wed, 19 Mar 2025 17:30:39 -0000 (UTC), Tweed wrote:

    According to my bill:
    Magenta Military $90 (3 lines) unlimited voice/text/data
    Equipment Fees $51.67 (2 iPhone 15)
    Netflix Standard $0.00
    -------------------
    Monthly Bill $141.67 taxes included


    What's all this with multiple lines? Is this a common US thing? I looked at t-mobile USA and the minimum they seemed to want to sell was 4 lines. What does the single person do?

    Melting pot economics.

    In the USA, you're supposed to find an immigrant wife and adopt her kids
    from her ex who never gave a damn, and that's where the number came from.

    There are lots of immigrant wives looking for husbands, so that's not the problem, but with the deportations going on, they're even more desperate.

    In the liberal states, you can even find a few immigrant men to "marry".
    You need them to have a phone when they're working in the picking fields.

    You do things different over there?

    Pretty soon, Canada and Greenland will be part of the USA so that they too
    can adopt immigrant wives and their kids so as to achieve 4-line status.

    If you marry an immigrant man though, I'm not sure what they pick in the
    fields above and beyond. Snowballs? (What grows in Canada/Greenland?)

    Who wants them anyway?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Tweed on Wed Mar 19 18:09:55 2025
    XPost: uk.telecom.mobile, misc.phone.mobile.iphone

    On Wed, 19 Mar 2025 17:53:12 -0000 (UTC), Tweed wrote :


    https://www.t-mobile.com/cell-phone-plans


    Ah ok. $50 plus taxes and fees (how much does that add?) for 50 Gb data
    seems expensive. What happens when you�ve used the 50 Gb �premium� data? Do you get a very slow connection?
    I pay the equivalent of $19 in the UK for 50 Gb data and free European
    (note European, not just EU) roaming with Vodafone. Call and texts are unlimited. There are cheaper providers with various trade offs, eg poor
    rural coverage or a congested network.

    My bill is $100 plus $20 taxes and fees in a VERY high tax state.
    So expect the maximum to be %20.

    I don't know if badgolferman's state is a high-tax state, but likely the
    taxes and fees are somewhat lower than %20 (which is highway robbery).

    As for "premium data", I think it's just a way for T-Mobile to eke out differentiation, since "regular data" is (as far as I know) fast enough.

    It's just a priority thing anyway, as far as I know, meaning "if" the tower gets congested, then (and only then) does the premium data kick in.

    In my experience, "regular data" is fast enough but it's been a long while since I last ran those speed tests that badgolferman & I ran loooong ago.
    <https://i.postimg.cc/4dDhFK5F/speedtest01.jpg> *125Mbps*
    <https://i.postimg.cc/vT68k3BW/speedtest02.jpg> *181Mbps*
    <https://i.postimg.cc/pdXF4Mtz/speedtest03.jpg> *125Mbps* to *181Mbps*
    <https://i.postimg.cc/gcsyc4Vn/speedtest04.jpg> *82Mbps* & -88dBM
    <https://i.postimg.cc/mggy315q/speedtest05.jpg> *254Mbps*
    <https://i.postimg.cc/43KvqkZQ/speedtest06.jpg> *255Mbps*
    <https://i.postimg.cc/zf9w1tGZ/speedtest07.jpg> *255Mbps*
    <https://i.postimg.cc/Bb3xjjFm/speedtest08.jpg> *255Mbps*
    <https://i.postimg.cc/GhZKX0vZ/speedtest09.jpg> *130Mbps*
    <https://i.postimg.cc/28yZdQJR/speedtest10.jpg> *81Mbps*
    <https://i.postimg.cc/ydnDcxy8/speedtest11.jpg> *79Mbps* to *81Mbps*
    <https://i.postimg.cc/5y063Jsq/speedtest12.jpg> *96Mbps* to *109Mbps*
    <https://i.postimg.cc/fbNyPmHb/speedtest13.jpg> *109Mbps*
    <https://i.postimg.cc/5tSyWyGS/speedtest14.jpg> *88Mbps* to *102Mbps*
    <https://i.postimg.cc/C5vgmtRd/speedtest15.jpg> *130Mbps* to *255Mbps*
    <https://i.postimg.cc/W3GgYJtZ/speedtest16.jpg> *125Mbps* to *181Mbps*
    <https://i.postimg.cc/nVs0Smw8/speedtest17.jpg> *54Mbps*
    <https://i.postimg.cc/N0fx62rz/speedtest18.jpg> *60Mbps* & -85dBm
    <https://i.postimg.cc/qR4BcjfM/speedtest19.jpg> Ookla test log results
    <https://i.postimg.cc/66L724vh/speedtest20.jpg> Meteor test log results
    <https://i.postimg.cc/vTfn0HB6/speedtest21.jpg> Speed tests over time
    <https://i.postimg.cc/SsXCzGbd/speedtest22.jpg> T-mo 377, 414, 443 Mbps
    <https://i.postimg.cc/tTLPdVXj/speedtest23.jpg> T-mo 419 & 390 Mbps 5G UC
    <https://i.postimg.cc/BvnxJ0hd/speedtest24.jpg> T-mo RSRP -91 to -96 dBm
    <https://i.postimg.cc/x17ChVzf/speedtest25.jpg> Verizon femtocell setup
    <https://i.postimg.cc/dtFnFCrX/speedtest26.jpg> WISP AC PRISM uses GPS

    That was *years* ago, where presumably it's much faster now since T-Mobile
    has been beefing up their 5GHz speeds since those slow days of long ago.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Carlos E.R. on Thu Mar 20 03:32:27 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    On Wed, 19 Mar 2025 11:07:40 +0100, Carlos E.R. wrote :


    I have a Swiss friend who told me how a friend of his using an iphone is >>> very happy now because she now has RCS and can exchange messages with
    photos and videos with friends of hers that may or may not have an iphone. >>
    For this purpose a selection of messengers exist for many years which
    are more versatile and much more trustworthy.

    For some reason, this person can not use them. One reason is that she
    has to find out which messenger the other side is using; being several,
    it becomes more useful to use RCS which everybody has.

    Hi Carlos,
    I'll agree with anyone who makes a sensibly logical statement and disagree
    with that same person if they don't, where I understand your friend's predicament since I have the same problem, only less so than she does.

    In my situation, there are only family members who have iPhones (generally
    the girls have iPhones and the boys have Android) where the girls are also
    not technically astute (neither are some of the boys) which adds an element
    of frustration to the mix when they're on an iPhone because they don't tend
    to seek out working solutions outside the Apple ecosystem, as it's foreign
    to them to think how do so something when Apple doesn't tell them how.

    As far as I know, Tim Cook said the answer to the question of why can't
    iPhone users communicate with the real world when he famously quipped
    *Buy your Mom an iPhone!*

    Notice this is bona fide proof that Apple had no intention of ever working
    in the real world when that statement comes from the very top of Apple.
    *Tim Cook says 'buy your mom an iPhone' when asked about RCS*
    <https://www.androidauthority.com/tim-cook-rcs-iphone-3206620/>

    It's clear that Apple products aren't ever tested in the real world.
    "Google's SVP of Android Hiroshi Lockheimer has responded to
    the Apple CEO's comments about RCS. He says people shouldn't
    have to buy their moms new iPhones just to send photos & videos."

    The sad part is Apple doesn't care about even its own customers.
    The only thing Apple cares about is to lock them into their system.

    Apple's strategy is the iPhone is a dumb terminal which is a slave to
    Cupertino servers to the point that if you don't constantly log into
    Apple's mothership server farm (it nags you 10X a day!) Apple bricks them.
    (Ask me how I know this fact.)

    Note: The Apple trolls don't know that the iPad is logging into Apple
    servers 10X a day because they actually log in; I do not. So I know.

    Back to your friend's problem, there are only two "good" solutions:
    a. She has to find a VOIP messenger that all her friends are using
    b. Or, she has to ask all her friends to buy her an iPhone :)

    I have the same problem she has, but we've solved it using WhatsApp.

    I don't like that I have to have a WA dialer just to keep my contacts out
    of WhatsApp's hands (although they're hashed), but I do it for the video!

    I presume when Apple and Google make their future joint announcement that
    they simultaneously support RCS with encryption, we'll all be happier.

    RCS is one more step for Apple to be forced to work in the real world.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richmond@21:1/5 to Marion on Fri Mar 21 14:41:01 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    Marion <[email protected]> writes:

    On Tue, 18 Mar 2025 12:12:16 +0100, Arno Welzel wrote :


    What the article does not clarify is whether Android will also
    implement this (Google uses its own encryption method), and so what
    will happen to cross platform messages.
    Since MLS will become part of RCS, Google would be stupid not to
    implement it. In fact when MLS is implemented, there is no need to keep
    the proprietary solution in place - maybe just as a fall back for old
    devices.

    Google is already on record for adopting MLS the same time Apple does.
    What's interesting though is how it will work when the Internet sucks.

    Nothing can happen until the two *devices* exchange the keys, right?

    Apparently the fallback will be two-fold if there is no Internet:
    a. Queue the message for a while, and, if necessary... b. Eventually
    fall back to SMS/MMS

    But the fallback will be *different* depending on WHO is offline!

    I use the last known good version of PulseSMS so I don't have RCS, but apparently those with Google Messages have to set an option to get that. Automatically resend as SMS/MMS = on/off

    With Google Messages, if you send a message by RCS and you see it has
    not been delivered or read, because the ticks have not lit up, you can
    tap the message and then you get an option to switch to SMS. I think you
    used to be able to hold down the send button, but that seems to have
    changed.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to All on Sat Mar 22 15:05:47 2025
    XPost: misc.phone.mobile.iphone

    On 2025-03-19 17:07, Jörg Lorenz wrote:
    On 19.03.25 11:07, Carlos E.R. wrote:
    On 2025-03-19 02:08, Jörg Lorenz wrote:
    On 18.03.25 23:11, Carlos E.R. wrote:
    I forget why it has to be rcs. He told the history, but I do not
    remember it. Maybe they don't have WhatsApp, which the Swiss authorities >>>> are against :-p

    More nonsense.

    Whatsapp is forbidden for the Swiss military. And also other
    institutions. This is a known fact.

    RCS is forbidden as well. Your counter party is obviously not member of
    a security related service.

    Care to provide a link supporting this?


    BTW: You look very childish. Really. And you must be a bored old man.

    LOL.

    Personal attacks, you too?

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Marion on Sat Mar 22 15:05:38 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    On 2025-03-20 04:32, Marion wrote:
    On Wed, 19 Mar 2025 11:07:40 +0100, Carlos E.R. wrote :

    ...


    Back to your friend's problem, there are only two "good" solutions:
    a. She has to find a VOIP messenger that all her friends are using
    b. Or, she has to ask all her friends to buy her an iPhone :)

    I have the same problem she has, but we've solved it using WhatsApp.

    She solved it by using RCS. I don't remember why WhatsApp would not do,
    so I can not add her reasoning to the conversation. Maybe her
    correspondents do not have it, maybe some do some don't. But everybody
    has RCS, or can enable it. Maybe she uses MMS in case RCS fails, but I
    heard MMS is disabled in Switzerland (all or some companies I dunno).

    https://news.ycombinator.com/item?id=30270472

    ...

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Carlos E.R. on Sat Mar 22 19:16:30 2025
    XPost: misc.phone.mobile.iphone, uk.telecom.mobile

    On Sat, 22 Mar 2025 15:05:38 +0100, Carlos E.R. wrote :


    She solved it by using RCS.

    Yup. That's how Andy solved his MMS cost problem, even as WhatsApp is how I solved the blurry video problem. Both methods require the iPhone owner to
    wake up and turn on their brain (which is hard for herd animals to do).

    What's interesting in terms of Apple's long sordid history of not caring
    about its devices working in the real world, is that "something" changed at Apple HQ in Cupertino to make Apple, all of a sudden, care about interoperability.

    It's not that Apple cared to work in they real world since almost
    everything Apple does not work in the real world - so it's something else.

    But what? After all these years of NOT working in the real world...
    What made Apple finally decide for its messaging to work in the real world?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Carlos E.R. on Mon Mar 24 11:14:40 2025
    XPost: misc.phone.mobile.iphone

    On 22.03.25 15:05, Carlos E.R. wrote:
    On 2025-03-19 17:07, Jörg Lorenz wrote:
    On 19.03.25 11:07, Carlos E.R. wrote:
    On 2025-03-19 02:08, Jörg Lorenz wrote:
    On 18.03.25 23:11, Carlos E.R. wrote:
    I forget why it has to be rcs. He told the history, but I do not
    remember it. Maybe they don't have WhatsApp, which the Swiss authorities >>>>> are against :-p

    More nonsense.

    Whatsapp is forbidden for the Swiss military. And also other
    institutions. This is a known fact.

    RCS is forbidden as well. Your counter party is obviously not member of
    a security related service.

    Care to provide a link supporting this?

    Yes. BTW: Swisscom the market leader with a market share of 60% still
    does not offer RCS at all for iPhone users. Salt the smallest network
    operator does. My Pixel is running on their network.



    --
    "De gustibus non est disputandum."

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to All on Mon Mar 24 14:31:18 2025
    XPost: misc.phone.mobile.iphone

    On 2025-03-24 11:14, Jörg Lorenz wrote:
    On 22.03.25 15:05, Carlos E.R. wrote:
    On 2025-03-19 17:07, Jörg Lorenz wrote:
    On 19.03.25 11:07, Carlos E.R. wrote:
    On 2025-03-19 02:08, Jörg Lorenz wrote:
    On 18.03.25 23:11, Carlos E.R. wrote:
    I forget why it has to be rcs. He told the history, but I do not
    remember it. Maybe they don't have WhatsApp, which the Swiss authorities >>>>>> are against :-p

    More nonsense.

    Whatsapp is forbidden for the Swiss military. And also other
    institutions. This is a known fact.

    RCS is forbidden as well. Your counter party is obviously not member of
    a security related service.

    Care to provide a link supporting this?

    Yes. BTW: Swisscom the market leader with a market share of 60% still
    does not offer RCS at all for iPhone users. Salt the smallest network operator does. My Pixel is running on their network.

    I don't see the link. You said "RCS is forbidden as well", which is
    different of "not supported".

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Carlos E.R. on Mon Mar 24 21:40:19 2025
    XPost: misc.phone.mobile.iphone

    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is
    different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody
    wants it. It is an inferior and insecure service. Full stop.

    --
    "Roma locuta, causa finita." (Augustinus)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Carlos E.R. on Tue Mar 25 17:14:48 2025
    XPost: misc.phone.mobile.iphone

    On 25.03.25 14:12, Carlos E.R. wrote:
    On 2025-03-24 21:40, Jörg Lorenz wrote:
    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is
    different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody
    wants it. It is an inferior and insecure service. Full stop.


    So, you back out. RCS is not forbidden in Switzerland. Thank you.

    It isn't. Nobody said that. Learn to read und in particular to understand.

    As for your other saying, millions of RCS users worldwide contradict you.

    Compared to messengers it is almost nil.



    --
    "Roma locuta, causa finita." (Augustinus)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to All on Tue Mar 25 17:21:08 2025
    XPost: misc.phone.mobile.iphone

    On 25.03.25 17:14, Jörg Lorenz wrote:
    On 25.03.25 14:12, Carlos E.R. wrote:
    On 2025-03-24 21:40, Jörg Lorenz wrote:
    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is
    different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody >>> wants it. It is an inferior and insecure service. Full stop.


    So, you back out. RCS is not forbidden in Switzerland. Thank you.

    It isn't. Nobody said that. Learn to read und in particular to understand.

    As for your other saying, millions of RCS users worldwide contradict you.

    Compared to messengers it is almost nil.

    BTW: Think about what would have happened to the amateurs of the
    Trump-regime if they had used RCS instead of Signal for the discussion
    of military mission details against the Huhti-rebels.

    Even Signal is not acceptable for classified information exchange let
    alone such a crap like RCS.

    --
    "Roma locuta, causa finita." (Augustinus)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to All on Tue Mar 25 19:47:04 2025
    XPost: misc.phone.mobile.iphone

    On 2025-03-25 17:14, Jörg Lorenz wrote:
    On 25.03.25 14:12, Carlos E.R. wrote:
    On 2025-03-24 21:40, Jörg Lorenz wrote:
    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is
    different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody >>> wants it. It is an inferior and insecure service. Full stop.


    So, you back out. RCS is not forbidden in Switzerland. Thank you.

    It isn't. Nobody said that. Learn to read und in particular to understand.

    You did.

    «RCS is forbidden as well. Your counter party is obviously not member of
    a security related service.»

    Message-ID: <vreq4q$4c8u$[email protected]>



    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Wed Mar 26 14:10:15 2025
    XPost: misc.phone.mobile.iphone

    Jörg Lorenz, 2025-03-24 21:40:

    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is
    different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody wants it. It is an inferior and insecure service. Full stop.

    E-Mail is also insecure and still used world wide nevertheless.


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Arno Welzel on Wed Mar 26 15:36:30 2025
    XPost: misc.phone.mobile.iphone

    On 26.03.25 14:10, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-24 21:40:

    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is
    different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody
    wants it. It is an inferior and insecure service. Full stop.

    E-Mail is also insecure and still used world wide nevertheless.

    Asymmetric encryption for e-mail exists.
    OpenPGP und S/MIME are much more powerful than anything these messengers
    offer.

    --
    "De gustibus non est disputandum."

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Thu Mar 27 10:32:09 2025
    XPost: misc.phone.mobile.iphone

    Jörg Lorenz, 2025-03-26 15:36:

    On 26.03.25 14:10, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-24 21:40:

    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is
    different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody >>> wants it. It is an inferior and insecure service. Full stop.

    E-Mail is also insecure and still used world wide nevertheless.

    Asymmetric encryption for e-mail exists.
    OpenPGP und S/MIME are much more powerful than anything these messengers offer.

    Yes, but both are not used widely used since encryption is optional for
    e-mail and not mandatory.

    Besides that PGP and S/MIME both had vulnerabilities:
    <https://efail.de/>


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Arno Welzel on Fri Mar 28 15:01:23 2025
    XPost: misc.phone.mobile.iphone

    On 2025-03-27 10:32, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-26 15:36:

    On 26.03.25 14:10, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-24 21:40:

    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is
    different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody >>>> wants it. It is an inferior and insecure service. Full stop.

    E-Mail is also insecure and still used world wide nevertheless.

    Asymmetric encryption for e-mail exists.
    OpenPGP und S/MIME are much more powerful than anything these messengers
    offer.

    Yes, but both are not used widely used since encryption is optional for e-mail and not mandatory.

    Normal people find it difficult to use. I have only succeeded using it
    it with computer geeks, not with lawyers or banks.



    Besides that PGP and S/MIME both had vulnerabilities:
    <https://efail.de/>

    Hum.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?J=C3=B6rg_Lorenz?=@21:1/5 to Carlos E.R. on Fri Mar 28 17:22:45 2025
    XPost: misc.phone.mobile.iphone

    On 28.03.25 15:01, Carlos E.R. wrote:
    On 2025-03-27 10:32, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-26 15:36:

    On 26.03.25 14:10, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-24 21:40:

    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is >>>>>> different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody >>>>> wants it. It is an inferior and insecure service. Full stop.

    E-Mail is also insecure and still used world wide nevertheless.

    Asymmetric encryption for e-mail exists.
    OpenPGP und S/MIME are much more powerful than anything these messengers >>> offer.

    Yes, but both are not used widely used since encryption is optional for
    e-mail and not mandatory.

    Normal people find it difficult to use. I have only succeeded using it
    it with computer geeks, not with lawyers or banks.

    That is the bitter truth.


    --
    "Roma locuta, causa finita." (Augustinus)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Carlos E.R. on Fri Mar 28 18:31:56 2025
    XPost: misc.phone.mobile.iphone

    Carlos E.R. <[email protected]d> wrote:
    On 2025-03-27 10:32, Arno Welzel wrote:
    J�rg Lorenz, 2025-03-26 15:36:

    On 26.03.25 14:10, Arno Welzel wrote:
    J�rg Lorenz, 2025-03-24 21:40:

    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is >>>>> different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody >>>> wants it. It is an inferior and insecure service. Full stop.

    E-Mail is also insecure and still used world wide nevertheless.

    Asymmetric encryption for e-mail exists.
    OpenPGP und S/MIME are much more powerful than anything these messengers >> offer.

    Yes, but both are not used widely used since encryption is optional for e-mail and not mandatory.

    Normal people find it difficult to use. I have only succeeded using it
    it with computer geeks, not with lawyers or banks.

    Just attach the .eml file in a WhatsApp message! :-)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Frank Slootweg on Fri Mar 28 20:46:58 2025
    XPost: misc.phone.mobile.iphone

    On 2025-03-28 19:31, Frank Slootweg wrote:
    Carlos E.R. <[email protected]d> wrote:
    On 2025-03-27 10:32, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-26 15:36:

    On 26.03.25 14:10, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-24 21:40:

    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is >>>>>>> different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody >>>>>> wants it. It is an inferior and insecure service. Full stop.

    E-Mail is also insecure and still used world wide nevertheless.

    Asymmetric encryption for e-mail exists.
    OpenPGP und S/MIME are much more powerful than anything these messengers >>>> offer.

    Yes, but both are not used widely used since encryption is optional for
    e-mail and not mandatory.

    Normal people find it difficult to use. I have only succeeded using it
    it with computer geeks, not with lawyers or banks.

    Just attach the .eml file in a WhatsApp message! :-)

    Hum! No idea if whatsapp encrypts attachments. Not all email clients do.


    Reminds me of a different issue: whatsapp backups. By default, they are
    not encrypted. I tried to enable encryption for a month or so, but most
    days it failed. In the end, I had to disable it.

    There is a court case here where the accused deletes everything
    periodically, so the court is now trying to get access to the backups.
    Yes, both Google and Whatsapp have promised to help.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Carlos E.R. on Fri Mar 28 20:13:24 2025
    XPost: misc.phone.mobile.iphone

    Carlos E.R. <[email protected]d> wrote:
    On 2025-03-28 19:31, Frank Slootweg wrote:
    Carlos E.R. <[email protected]d> wrote:
    On 2025-03-27 10:32, Arno Welzel wrote:
    J�rg Lorenz, 2025-03-26 15:36:

    On 26.03.25 14:10, Arno Welzel wrote:
    J�rg Lorenz, 2025-03-24 21:40:

    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is >>>>>>> different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody
    wants it. It is an inferior and insecure service. Full stop.

    E-Mail is also insecure and still used world wide nevertheless.

    Asymmetric encryption for e-mail exists.
    OpenPGP und S/MIME are much more powerful than anything these messengers >>>> offer.

    Yes, but both are not used widely used since encryption is optional for >>> e-mail and not mandatory.

    Normal people find it difficult to use. I have only succeeded using it
    it with computer geeks, not with lawyers or banks.

    Just attach the .eml file in a WhatsApp message! :-)

    Hum! No idea if whatsapp encrypts attachments. Not all email clients do.

    A WhatsApp message is end-to-end encrypted, including any attachments,
    media, etc.. So the sender and recipient can see the .eml file in the
    clear, but no-one else can.

    BTW, of course my 'suggestion' was in jest.

    Reminds me of a different issue: whatsapp backups. By default, they are
    not encrypted. I tried to enable encryption for a month or so, but most
    days it failed. In the end, I had to disable it.

    I think that's a general issue of one's Google Account storage. Is it encrypted or not? I encrypt my Google Drive backup, but don't know about
    the other parts, i.e. WhatsApp backup, Gmail, others.

    There is a court case here where the accused deletes everything
    periodically, so the court is now trying to get access to the backups.
    Yes, both Google and Whatsapp have promised to help.

    Interesting. Keep us posted.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Frank Slootweg on Fri Mar 28 21:41:52 2025
    XPost: misc.phone.mobile.iphone

    On 2025-03-28 21:13, Frank Slootweg wrote:
    Carlos E.R. <[email protected]d> wrote:
    On 2025-03-28 19:31, Frank Slootweg wrote:
    Carlos E.R. <[email protected]d> wrote:
    On 2025-03-27 10:32, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-26 15:36:

    On 26.03.25 14:10, Arno Welzel wrote:
    Jörg Lorenz, 2025-03-24 21:40:

    On 24.03.25 14:31, Carlos E.R. wrote:
    I don't see the link. You said "RCS is forbidden as well", which is >>>>>>>>> different of "not supported".

    I repeat it for you and Arlen: Nobody needs RCS and in particular nobody
    wants it. It is an inferior and insecure service. Full stop.

    E-Mail is also insecure and still used world wide nevertheless.

    Asymmetric encryption for e-mail exists.
    OpenPGP und S/MIME are much more powerful than anything these messengers >>>>>> offer.

    Yes, but both are not used widely used since encryption is optional for >>>>> e-mail and not mandatory.

    Normal people find it difficult to use. I have only succeeded using it >>>> it with computer geeks, not with lawyers or banks.

    Just attach the .eml file in a WhatsApp message! :-)

    Hum! No idea if whatsapp encrypts attachments. Not all email clients do.

    A WhatsApp message is end-to-end encrypted, including any attachments, media, etc.. So the sender and recipient can see the .eml file in the
    clear, but no-one else can.

    BTW, of course my 'suggestion' was in jest.

    Of course. :-)

    But for practical purposes, for plain Joe, whatsap is safer than email
    (cof, cof).


    Reminds me of a different issue: whatsapp backups. By default, they are
    not encrypted. I tried to enable encryption for a month or so, but most
    days it failed. In the end, I had to disable it.

    I think that's a general issue of one's Google Account storage. Is it encrypted or not? I encrypt my Google Drive backup, but don't know about
    the other parts, i.e. WhatsApp backup, Gmail, others.

    There is a court case here where the accused deletes everything
    periodically, so the court is now trying to get access to the backups.
    Yes, both Google and Whatsapp have promised to help.

    Interesting. Keep us posted.

    The whole of Spain is waiting :-)

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)