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: Mon, 7 Jul 2025 13:28:22 +0200
Lines: 17
Message-ID: <md1pakFlmo7U1@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> <mcv38vF7rf1U5@mid.individual.net> <mcvr46FbkutU4@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Trace: individual.net qHrB8k47xVSJD5ejlV5ONAvTfVciO//olu3Mkg5czHhfFMZLWU
Cancel-Lock: sha1:KlcaUEmoQxW1a+Y9CpYiO+eM/m8= sha256:gHsUIyO2ANFFUrnXdHg7w8kdYhwM5oWZiAofqG+smtw=
Content-Language: en-US, de-DE
In-Reply-To: <mcvr46FbkutU4@mid.individual.net>
Xref: csiph.com comp.mobile.android:149663

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