Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.mobile.android > #149489 > unrolled thread

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

Started byMarion <marion@facts.com>
First post2025-07-02 04:15 +0000
Last post2025-07-07 15:27 +0100
Articles 8 on this page of 28 — 9 participants

Back to article view | Back to comp.mobile.android

Contents

  For those using Google messages with RCS with iPhone owners... Marion <marion@facts.com> - 2025-07-02 04:15 +0000
    Re: For those using Google messages with RCS with iPhone owners... Andy Burns <usenet@andyburns.uk> - 2025-07-02 08:02 +0100
      Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-02 12:45 +0200
        Re: For those using Google messages with RCS with iPhone owners... Marion <marion@facts.com> - 2025-07-02 17:41 +0000
        Re: For those using Google messages with RCS with iPhone owners... Stan Brown <someone@example.com> - 2025-07-05 08:59 -0700
          Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-05 20:04 +0200
      Re: For those using Google messages with RCS with iPhone owners... "s|b" <me@privacy.invalid> - 2025-07-02 16:11 +0200
        Re: For those using Google messages with RCS with iPhone owners... Yusuf Khan <yusuf.khan.nospam@ptcl.net.pk> - 2025-07-02 22:43 +0500
          Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-02 20:16 +0200
            Re: For those using Google messages with RCS with iPhone owners... Yusuf Khan <yusuf.khan.nospam@ptcl.net.pk> - 2025-07-03 00:04 +0500
              Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-02 22:57 +0200
                Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-03 00:18 +0200
              Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:36 +0200
          Re: For those using Google messages with RCS with iPhone owners... Andy Burns <usenet@andyburns.uk> - 2025-07-03 00:17 +0100
          Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:33 +0200
      Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:29 +0200
        Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-03 17:30 +0200
          Re: For those using Google messages with RCS with iPhone owners... "Carlos E.R." <robin_listas@es.invalid> - 2025-07-03 20:08 +0200
            Re: For those using Google messages with RCS with iPhone owners... Frank Slootweg <this@ddress.is.invalid> - 2025-07-03 19:42 +0000
              Re: For those using Google messages with RCS with iPhone owners... micky <NONONOmisc07@fmguy.com> - 2025-07-03 21:23 -0400
              Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-06 12:58 +0200
          Re: For those using Google messages with RCS with iPhone owners... "s|b" <me@privacy.invalid> - 2025-07-04 16:12 +0200
            Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-06 12:59 +0200
              Re: For those using Google messages with RCS with iPhone owners... Marion <marion@facts.com> - 2025-07-06 13:52 +0000
              Re: For those using Google messages with RCS with iPhone owners... "s|b" <me@privacy.invalid> - 2025-07-06 19:46 +0200
                Re: For those using Google messages with RCS with iPhone owners... Arno Welzel <usenet@arnowelzel.de> - 2025-07-07 13:28 +0200
                  Re: For those using Google messages with RCS with iPhone owners... Marion <marion@facts.com> - 2025-07-07 14:18 +0000
                    Re: For those using Google messages with RCS with iPhone owners... Andy Burns <usenet@andyburns.uk> - 2025-07-07 15:27 +0100

Page 2 of 2 — ← Prev page 1 [2]

#149643

FromArno Welzel <usenet@arnowelzel.de>
Date2025-07-06 12:58 +0200
Message-ID<mcv376F7rf1U4@mid.individual.net>
In reply to#149584
Frank Slootweg, 2025-07-03 21:42:

> Carlos E.R. <robin_listas@es.invalid> 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

[toc] | [prev] | [next] | [standalone]

#149604

From"s|b" <me@privacy.invalid>
Date2025-07-04 16:12 +0200
Message-ID<mcq5prFdi5fU2@mid.individual.net>
In reply to#149570
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

[toc] | [prev] | [next] | [standalone]

#149644

FromArno Welzel <usenet@arnowelzel.de>
Date2025-07-06 12:59 +0200
Message-ID<mcv38vF7rf1U5@mid.individual.net>
In reply to#149604
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

[toc] | [prev] | [next] | [standalone]

#149648

FromMarion <marion@facts.com>
Date2025-07-06 13:52 +0000
Message-ID<104dv20$19fh$1@nnrp.usenet.blueworldhosting.com>
In reply to#149644
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)

[toc] | [prev] | [next] | [standalone]

#149654

From"s|b" <me@privacy.invalid>
Date2025-07-06 19:46 +0200
Message-ID<mcvr46FbkutU4@mid.individual.net>
In reply to#149644
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

[toc] | [prev] | [next] | [standalone]

#149663

FromArno Welzel <usenet@arnowelzel.de>
Date2025-07-07 13:28 +0200
Message-ID<md1pakFlmo7U1@mid.individual.net>
In reply to#149654
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

[toc] | [prev] | [next] | [standalone]

#149669

FromMarion <marion@facts.com>
Date2025-07-07 14:18 +0000
Message-ID<104gkv7$fpb$1@nnrp.usenet.blueworldhosting.com>
In reply to#149663
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?

[toc] | [prev] | [next] | [standalone]

#149670

FromAndy Burns <usenet@andyburns.uk>
Date2025-07-07 15:27 +0100
Message-ID<md23qfFmcfeU3@mid.individual.net>
In reply to#149669
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.

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | comp.mobile.android

csiph-web