• For those using Google messages with RCS with iPhone owners...

    From Marion@21:1/5 to All on Wed Jul 2 04:15:19 2025
    Is this of any interest to you? https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/

    Google is finally starting to roll out the ability for Android users to
    edit RCS messages sent to iPhones, a feature previously unavailable cross-platform.

    Made possible by the new Universal Profile 3.0 specification, users can long-press a sent message to edit and resend it within a 15-minute window.

    The feature is in limited testing and isn't perfect yet, as edited texts currently appear as a new message on iPhones and iPhones can't edit
    messages sent to Android devices.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Marion on Wed Jul 2 08:02:08 2025
    Marion wrote:

    https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/

    Google is finally starting to roll out the ability for Android users to
    edit RCS messages sent to iPhones, a feature previously unavailable cross-platform.
    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Andy Burns on Wed Jul 2 12:45:54 2025
    On 2025-07-02 09:02, Andy Burns wrote:
    Marion wrote:

    https://www.androidauthority.com/google-messages-edit-messages-sent-
    to-iphones-3573055/

    Google is finally starting to roll out the ability for Android users to
    edit RCS messages sent to iPhones, a feature previously unavailable
    cross-platform.
    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...


    Arguably it is better to edit a typo than sending another post with the correction. But the app should warn the recipient that the post has been edited, and maybe mark the edit.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From s|b@21:1/5 to Andy Burns on Wed Jul 2 16:11:38 2025
    On Wed, 2 Jul 2025 08:02:08 +0100, Andy Burns wrote:

    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    Signal has this feature. It was quite useful when I mistakenly sent a
    message to the wrong person and to correct typos.

    --
    s|b

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marion@21:1/5 to Carlos E.R. on Wed Jul 2 17:41:38 2025
    On Wed, 2 Jul 2025 12:45:54 +0200, Carlos E.R. wrote :


    https://www.androidauthority.com/google-messages-edit-messages-sent-
    to-iphones-3573055/

    Google is finally starting to roll out the ability for Android users to
    edit RCS messages sent to iPhones, a feature previously unavailable
    cross-platform.
    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...


    Arguably it is better to edit a typo than sending another post with the correction. But the app should warn the recipient that the post has been edited, and maybe mark the edit.

    I will agree with anyone who makes a logical argument, where I'm agreeing
    with both s|b and Carlos in this case, where I think it's a useful feature.

    You're the one SENDING the text.
    Why can't YOU edit it (for a short while).

    We've had this in Google Mail for many years now, haven't we?
    It's useful. Very useful.

    Of course, if the other person already RECEIVED (and read) the message, and perhaps even started RESPONDING to that message, then we may have an issue.

    But I'd rather fix a typo any day of the weak...
    ... week...

    :)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Yusuf Khan@21:1/5 to All on Wed Jul 2 22:43:01 2025
    On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:

    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    Signal has this feature. It was quite useful when I mistakenly sent a
    message to the wrong person and to correct typos.

    My E-mail has it too I think.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Yusuf Khan on Wed Jul 2 20:16:17 2025
    On 2025-07-02 19:43, Yusuf Khan wrote:
    On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:

    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    Signal has this feature. It was quite useful when I mistakenly sent a
    message to the wrong person and to correct typos.

    My E-mail has it too I think.

    The only way to do this in email is to not send the email when the user
    clicks send, but wait. Once an email is actually sent, the recipient has
    a copy that can not be altered by the sender.

    You might have an edit mail feature if both parties are using the same
    mail platform with complying (specific) client software.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Yusuf Khan@21:1/5 to Carlos E.R. on Thu Jul 3 00:04:50 2025
    On Wed, 2 Jul 2025 20:16:17 +0200, Carlos E.R. wrote:

    On 2025-07-02 19:43, Yusuf Khan wrote:
    On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:

    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    Signal has this feature. It was quite useful when I mistakenly sent a
    message to the wrong person and to correct typos.

    My E-mail has it too I think.

    The only way to do this in email is to not send the email when the user clicks send, but wait. Once an email is actually sent, the recipient has
    a copy that can not be altered by the sender.

    You might have an edit mail feature if both parties are using the same
    mail platform with complying (specific) client software.

    https://news.itsfoss.com/protonmail-undo-send/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Yusuf Khan on Wed Jul 2 22:57:07 2025
    On 2025-07-02 21:04, Yusuf Khan wrote:
    On Wed, 2 Jul 2025 20:16:17 +0200, Carlos E.R. wrote:

    On 2025-07-02 19:43, Yusuf Khan wrote:
    On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:

    Editing or rescinding *anything* after pressing send is a do-not-want >>>>> feature in any messaging/email app ...

    Signal has this feature. It was quite useful when I mistakenly sent a
    message to the wrong person and to correct typos.

    My E-mail has it too I think.

    The only way to do this in email is to not send the email when the user
    clicks send, but wait. Once an email is actually sent, the recipient has
    a copy that can not be altered by the sender.

    You might have an edit mail feature if both parties are using the same
    mail platform with complying (specific) client software.

    https://news.itsfoss.com/protonmail-undo-send/

    It does what I said: they delay the actual sending for 10 seconds, so
    during that time you can abort the operation. Once actually sent, you
    can not do anything to it.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stefan Ram@21:1/5 to Carlos E.R. on Wed Jul 2 21:17:03 2025
    "Carlos E.R." <[email protected]d> wrote or quoted:
    It does what I said: they delay the actual sending for 10 seconds, so
    during that time you can abort the operation. Once actually sent, you
    can not do anything to it.

    I used to have this account where, before I sent out a transfer,
    I would double-check every single detail. I'd go over each digit,
    line it up with the original, once from the start and once from the
    end, then break it down into groups of three, then four. After
    minutes of sweating it out, I'd finally hit "Submit Transfer!". -
    Then this popped up: "You have entered the following information.
    Please verify that all details are correct before proceeding.".
    (Since I couldn't be sure the info on the screen actually matched
    what I'd just checked, I'd have to start all over from scratch . . .)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Stefan Ram on Thu Jul 3 00:18:27 2025
    On 2025-07-02 23:17, Stefan Ram wrote:
    "Carlos E.R." <[email protected]d> wrote or quoted:
    It does what I said: they delay the actual sending for 10 seconds, so
    during that time you can abort the operation. Once actually sent, you
    can not do anything to it.

    I used to have this account where, before I sent out a transfer,
    I would double-check every single detail. I'd go over each digit,
    line it up with the original, once from the start and once from the
    end, then break it down into groups of three, then four. After
    minutes of sweating it out, I'd finally hit "Submit Transfer!". -
    Then this popped up: "You have entered the following information.
    Please verify that all details are correct before proceeding.".
    (Since I couldn't be sure the info on the screen actually matched
    what I'd just checked, I'd have to start all over from scratch . . .)



    I know that feeling.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Yusuf Khan on Thu Jul 3 00:17:38 2025
    Yusuf Khan wrote:

    s|b wrote:

    Signal has this feature. It was quite useful when I mistakenly sent a
    message to the wrong person and to correct typos.

    My E-mail has it too I think.

    Microsoft thinks that their email has it (it does if both the sender and receiver use microsoft) but if the receiver uses a real email system
    then how is the unwanted message getting recalled?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Thu Jul 3 17:30:29 2025
    Arno Welzel, 2025-07-03 17:29:

    Andy Burns, 2025-07-02 09:02:

    Marion wrote:

    https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/

    Google is finally starting to roll out the ability for Android users to
    edit RCS messages sent to iPhones, a feature previously unavailable
    cross-platform.
    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    So upditing a tipo is not wanted?

    So updating a typo is not wanted? Instead it is better to re-send the
    same message again?


    --
    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 Thu Jul 3 17:33:28 2025
    Yusuf Khan, 2025-07-02 19:43:

    On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:

    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    Signal has this feature. It was quite useful when I mistakenly sent a
    message to the wrong person and to correct typos.

    My E-mail has it too I think.

    E-mail itself - no.

    An e-mail which was sent *and* fetched from the mailbox by the recipient
    can not be changed. This is not implemented in SMTP. But some
    proprietary solutions like Microsoft Outlook support revoking sent
    messages when you use their proprietary infrastructure - but the both
    the sender and recipient have to be in the same infrastructure then.

    --
    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 Thu Jul 3 17:36:00 2025
    Yusuf Khan, 2025-07-02 21:04:

    On Wed, 2 Jul 2025 20:16:17 +0200, Carlos E.R. wrote:

    On 2025-07-02 19:43, Yusuf Khan wrote:
    On Wed, 02 Jul 2025 16:11:38 +0200, s|b wrote:

    Editing or rescinding *anything* after pressing send is a do-not-want >>>>> feature in any messaging/email app ...

    Signal has this feature. It was quite useful when I mistakenly sent a
    message to the wrong person and to correct typos.

    My E-mail has it too I think.

    The only way to do this in email is to not send the email when the user
    clicks send, but wait. Once an email is actually sent, the recipient has
    a copy that can not be altered by the sender.

    You might have an edit mail feature if both parties are using the same
    mail platform with complying (specific) client software.

    https://news.itsfoss.com/protonmail-undo-send/

    This is not "undo" - it only allows to stop the transmission if you accidentally hit the "send" button, quote:

    "You don’t need to explicitly change settings to enable this feature.
    Undo Send is automatically enabled for all ProtonMail users with a
    default timer delay of 10 seconds.

    When you hit the send button, you’ll see an “undo” button and if you hit it, the email will not be sent and the composer window will reopen. You
    can make the changes and send the edited mail again."

    But if you finally sent the e-mail, it's done. You can not "undo" that.


    --
    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 Thu Jul 3 20:08:43 2025
    On 2025-07-03 17:30, Arno Welzel wrote:
    Arno Welzel, 2025-07-03 17:29:

    Andy Burns, 2025-07-02 09:02:

    Marion wrote:

    https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/

    Google is finally starting to roll out the ability for Android users to >>>> edit RCS messages sent to iPhones, a feature previously unavailable
    cross-platform.
    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    So upditing a tipo is not wanted?

    So updating a typo is not wanted? Instead it is better to re-send the
    same message again?

    X'-D

    upditing actually exists, I googled :-D

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Frank Slootweg@21:1/5 to Carlos E.R. on Thu Jul 3 19:42:44 2025
    Carlos E.R. <[email protected]d> wrote:
    On 2025-07-03 17:30, Arno Welzel wrote:
    Arno Welzel, 2025-07-03 17:29:

    Andy Burns, 2025-07-02 09:02:

    Marion wrote:

    https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/

    Google is finally starting to roll out the ability for Android users to >>>> edit RCS messages sent to iPhones, a feature previously unavailable
    cross-platform.
    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    So upditing a tipo is not wanted?

    So updating a typo is not wanted? Instead it is better to re-send the
    same message again?

    X'-D

    upditing actually exists, I googled :-D

    Even better: Googling 'upditing' gives results without an AI summary.
    Way to make AI shut up! :-)

    Also: Google Translate (English to Dutch) gives the same result for 'updating' and 'upditing' (no, it doesn't say "Did you nean: updating").

    So 'upditing' it is!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Thu Jul 3 17:29:41 2025
    Andy Burns, 2025-07-02 09:02:

    Marion wrote:

    https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/

    Google is finally starting to roll out the ability for Android users to
    edit RCS messages sent to iPhones, a feature previously unavailable
    cross-platform.
    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    So upditing a tipo is not wanted?


    --
    Arno Welzel
    https://arnowelzel.de

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From micky@21:1/5 to [email protected] on Thu Jul 3 21:23:14 2025
    In comp.mobile.android, on 3 Jul 2025 19:42:44 GMT, Frank Slootweg <[email protected]d> wrote:

    Carlos E.R. <[email protected]d> wrote:
    On 2025-07-03 17:30, Arno Welzel wrote:
    Arno Welzel, 2025-07-03 17:29:

    Andy Burns, 2025-07-02 09:02:

    Marion wrote:

    https://www.androidauthority.com/google-messages-edit-messages-sent-to-iphones-3573055/

    Google is finally starting to roll out the ability for Android users to >> >>>> edit RCS messages sent to iPhones, a feature previously unavailable
    cross-platform.
    Editing or rescinding *anything* after pressing send is a do-not-want
    feature in any messaging/email app ...

    So upditing a tipo is not wanted?

    So updating a typo is not wanted? Instead it is better to re-send the
    same message again?

    X'-D

    upditing actually exists, I googled :-D

    Even better: Googling 'upditing' gives results without an AI summary.
    Way to make AI shut up! :-)

    Also: Google Translate (English to Dutch) gives the same result for
    'updating' and 'upditing' (no, it doesn't say "Did you nean: updating").

    So 'upditing' it is!

    I thought upditing was diting a girl who made more money than I did.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From s|b@21:1/5 to Arno Welzel on Fri Jul 4 16:12:14 2025
    On Thu, 3 Jul 2025 17:30:29 +0200, Arno Welzel wrote:

    So updating a typo is not wanted? Instead it is better to re-send the
    same message again?

    Should have superseded. ;-)

    (Yeah, I know it's not really supported anymore.)

    --
    s|b

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Stan Brown@21:1/5 to Carlos E.R. on Sat Jul 5 08:59:45 2025
    On Wed, 2 Jul 2025 12:45:54 +0200, Carlos E.R. wrote:
    Arguably it is better to edit a typo than sending another post with the correction. But the app should warn the recipient that the post has been edited, and maybe mark the edit.


    The published article mentions that the "editing" is done by sending
    a new message, containing the entire original as corrected, with an
    asterisk at the top that (my words) the recipient is supposed to
    _guess_ means "here's version 2 of my message".

    --
    After using my real address in 37 years of Usenet articles,
    I am now reluctantly posting a fake address because of the
    large number of sites scraping Usenet articles without
    permission and putting them on their own pretend forum sites.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Carlos E.R.@21:1/5 to Stan Brown on Sat Jul 5 20:04:24 2025
    On 2025-07-05 17:59, Stan Brown wrote:
    On Wed, 2 Jul 2025 12:45:54 +0200, Carlos E.R. wrote:
    Arguably it is better to edit a typo than sending another post with the
    correction. But the app should warn the recipient that the post has been
    edited, and maybe mark the edit.


    The published article mentions that the "editing" is done by sending
    a new message, containing the entire original as corrected, with an
    asterisk at the top that (my words) the recipient is supposed to
    _guess_ means "here's version 2 of my message".

    Ok, I suppose that otherwise they would have to create a language for
    sending edits. Sending the message again is easier. The client software
    just has to recognize it as an edit and only display the latest version.

    A rogue client software could send an edit an hour or a day later.

    The client software might show the user both versions with a tap.

    --
    Cheers, Carlos.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Sun Jul 6 12:58:48 2025
    Frank Slootweg, 2025-07-03 21:42:

    Carlos E.R. <[email protected]d> wrote:
    [...]
    upditing actually exists, I googled :-D

    Even better: Googling 'upditing' gives results without an AI summary.
    Way to make AI shut up! :-)

    Also: Google Translate (English to Dutch) gives the same result for 'updating' and 'upditing' (no, it doesn't say "Did you nean: updating").

    So 'upditing' it is!

    No, see here:

    <https://dictionary.cambridge.org/us/spellcheck/english/?q=upditing>



    --
    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 Sun Jul 6 12:59:45 2025
    s|b, 2025-07-04 16:12:

    On Thu, 3 Jul 2025 17:30:29 +0200, Arno Welzel wrote:

    So updating a typo is not wanted? Instead it is better to re-send the
    same message again?

    Should have superseded. ;-)

    (Yeah, I know it's not really supported anymore.)

    Superseding is exactly what happens, when an RCS message is "updated".
    The receiver will get a new message which replaces the old one, so it
    looks like the existing message was updated.


    --
    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 Sun Jul 6 13:52:01 2025
    On Sun, 6 Jul 2025 12:59:45 +0200, Arno Welzel wrote :


    Superseding is exactly what happens, when an RCS message is "updated".
    The receiver will get a new message which replaces the old one, so it
    looks like the existing message was updated.

    I've been reading all responses with interest, where it seems from the
    combined experience of all of us, there are (at least) 3 update mechanisms.

    1. The kind Gmail uses (i.e., the original isn't sent right away)
    2. Both are sent (the original is sent, but the fix is also sent)
    3. The original is replaced (as Arno describes above)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From s|b@21:1/5 to Arno Welzel on Sun Jul 6 19:46:50 2025
    On Sun, 6 Jul 2025 12:59:45 +0200, Arno Welzel wrote:

    Superseding is exactly what happens, when an RCS message is "updated".
    The receiver will get a new message which replaces the old one, so it
    looks like the existing message was updated.

    I was actually talking about Usenet. (-;

    --
    s|b

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Arno Welzel@21:1/5 to All on Mon Jul 7 13:28:22 2025
    s|b, 2025-07-06 19:46:

    On Sun, 6 Jul 2025 12:59:45 +0200, Arno Welzel wrote:

    Superseding is exactly what happens, when an RCS message is "updated".
    The receiver will get a new message which replaces the old one, so it
    looks like the existing message was updated.

    I was actually talking about Usenet. (-;

    Yes - and the same mechanism applies to RCS as well - the old message
    gets replaced by a new one.


    --
    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 Mon Jul 7 14:18:15 2025
    On Mon, 7 Jul 2025 13:28:22 +0200, Arno Welzel wrote :


    Superseding is exactly what happens, when an RCS message is "updated".
    The receiver will get a new message which replaces the old one, so it
    looks like the existing message was updated.

    I was actually talking about Usenet. (-;

    Yes - and the same mechanism applies to RCS as well - the old message
    gets replaced by a new one.

    I seem to remember a "cancel" mechanism of Usenet in the olden days.
    Does it still exist?

    If you made a boo boo, you could cancel an article, fix it, & then resend.
    Is that correct?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Marion on Mon Jul 7 15:27:26 2025
    Marion wrote:

    I seem to remember a "cancel" mechanism of Usenet in the olden days.
    Does it still exist?

    If you made a boo boo, you could cancel an article, fix it, & then resend.

    Yesbut ...

    In those days propagation delays were higher, so there was more time to
    send out the cancel, now you probably haven't got time. Plenty of
    servers implement a cryptographic cancel-lock (see headers) others
    ignore cancels.

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