Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Arno Welzel <usenet@arnowelzel.de>
Newsgroups: comp.mobile.android
Subject: Re: For those using Google messages with RCS with iPhone owners...
Date: Sun, 6 Jul 2025 12:59:45 +0200
Lines: 19
Message-ID: <mcv38vF7rf1U5@mid.individual.net>
References: <1042bom$28bd$1@nnrp.usenet.blueworldhosting.com> <mck3rmFd2etU2@mid.individual.net> <mcnlv5FnbiU4@mid.individual.net> <mcnm0kFnbiU5@mid.individual.net> <mcq5prFdi5fU2@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Trace: individual.net 1duhVpKneiK5wo+4oEe1FQGxv9ti/8YXpZK9/X11sY0EYnbmAl
Cancel-Lock: sha1:t/iiEQ/xXTWYN0YSRNUYMr3g8po= sha256:poGrl2RBZgUUOJAry/bEZ+KGsxL9pG5+ZGsDD1m4z7Q=
Content-Language: en-US, de-DE
In-Reply-To: <mcq5prFdi5fU2@mid.individual.net>
Xref: csiph.com comp.mobile.android:149644

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