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

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

More about RCS.

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

Contents

  More about RCS. micky <NONONOmisc07@fmguy.com> - 2025-01-02 22:55 -0500
    Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-03 06:58 +0100
      Re: More about RCS. micky <NONONOmisc07@fmguy.com> - 2025-01-03 08:02 -0500
        Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-03 15:25 +0100
          Re: More about RCS. micky <NONONOmisc07@fmguy.com> - 2025-01-03 09:36 -0500
            Re: More about RCS. Frank Slootweg <this@ddress.is.invalid> - 2025-01-03 15:38 +0000
              Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-03 22:27 +0100
                Re: More about RCS. Frank Slootweg <this@ddress.is.invalid> - 2025-01-04 18:41 +0000
            Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-03 18:26 +0100
        Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-03 23:22 +0100
          Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-04 02:55 +0100
            Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-04 09:02 +0100
              Re: More about RCS. Andy Burns <usenet@andyburns.uk> - 2025-01-04 09:59 +0000
              Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-04 13:00 +0100
                Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-04 13:49 +0100
                  Re: More about RCS. micky <NONONOmisc07@fmguy.com> - 2025-01-04 20:52 -0500
            Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-05 12:57 +0100
              Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-05 15:18 +0100
              Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-05 17:26 +0100
                Re: More about RCS. Frank Slootweg <this@ddress.is.invalid> - 2025-01-05 16:31 +0000
              Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-05 17:31 +0100
                Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-05 18:40 +0100
                Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-05 21:59 +0100
                  Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-05 22:19 +0100
                    Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-05 22:30 +0100
                      Re: More about RCS. Frank Slootweg <this@ddress.is.invalid> - 2025-01-06 16:36 +0000
              Re: More about RCS. Chris <ithinkiam@gmail.com> - 2025-01-07 13:42 +0000
                Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-07 15:05 +0100
    Re: More about RCS. Joe Beanfish <joebeanfish@nospam.duh> - 2025-01-03 13:46 +0000
      Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-03 23:25 +0100
        Re: More about RCS. Dave Royal <dave@dave123royal.com> - 2025-01-04 07:52 +0000
          Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-04 13:03 +0100
            Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-04 13:51 +0100
              Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-05 13:01 +0100
                Re: More about RCS. Frank Slootweg <this@ddress.is.invalid> - 2025-01-05 13:14 +0000
                Re: More about RCS. Joe Beanfish <joebeanfish@nospam.duh> - 2025-01-07 13:38 +0000
                  Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-08 10:28 +0100
                  Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-08 13:32 +0100
                    Re: More about RCS. Joe Beanfish <joebeanfish@nospam.duh> - 2025-01-08 13:53 +0000
                    Re: More about RCS. Andy Burns <usenet@andyburns.uk> - 2025-01-08 15:40 +0000
                      Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-08 17:07 +0100
                        Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-08 21:06 +0100
                          Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-10 10:23 +0100
                            Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-10 18:25 +0100
                        Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-10 18:24 +0100
                      Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-08 21:10 +0100
                  Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-10 18:21 +0100
          Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-05 13:00 +0100
        Re: More about RCS. micky <NONONOmisc07@fmguy.com> - 2025-01-04 20:45 -0500
          Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-05 04:05 +0100
            Re: More about RCS. micky <NONONOmisc07@fmguy.com> - 2025-01-05 10:46 -0500
              Re: More about RCS. Frank Slootweg <this@ddress.is.invalid> - 2025-01-05 16:04 +0000
              Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-05 21:45 +0100
          Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-05 13:03 +0100
            Re: More about RCS. micky <NONONOmisc07@fmguy.com> - 2025-07-01 08:19 -0400
    Re: More about RCS. "s|b" <me@privacy.invalid> - 2025-01-04 11:00 +0100
      Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-04 12:21 +0100
        Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-05 13:04 +0100
          Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-05 15:20 +0100
            Re: More about RCS. Frank Slootweg <this@ddress.is.invalid> - 2025-01-05 14:42 +0000
              Re: More about RCS. "s|b" <me@privacy.invalid> - 2025-01-06 20:17 +0100
            Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-05 17:34 +0100
              Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-05 18:46 +0100
                Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-05 21:48 +0100
                  Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-05 22:25 +0100
                    Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-10 18:28 +0100
                      Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-10 20:32 +0100
                        Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-11 12:53 +0100
                          Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-11 15:32 +0100
                            Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-12 16:37 +0100
                      Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-10 22:19 +0100
                        Re: More about RCS. "Carlos E.R." <robin_listas@es.invalid> - 2025-01-10 22:41 +0100
                          Re: More about RCS. Jörg Lorenz <hugybear@gmx.net> - 2025-01-11 07:40 +0100
                            Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-11 12:58 +0100
                        Re: More about RCS. Arno Welzel <usenet@arnowelzel.de> - 2025-01-11 12:56 +0100

Page 3 of 4 — ← Prev page 1 2 [3] 4  Next page →

#146345

On 08.01.25 16:40, Andy Burns wrote:
> Carlos E.R. wrote:
> 
>> Joe Beanfish wrote:
>>>> Arno Welzel wrote:
>>>
>>>> Jörg Lorenz wrote:
>>>>
>>>>> Good to know that we should deactivate Google's wet dream 
>>>>> immediately. ;-)
>>>>
>>>> RCS is a standard protocol and not "Google's wet dream".
>>>
>>> Whose servers do RCS messages pass thru?
>>
>> It is quite difficult to know in each case, there is no trace 
>> information as there is with email.
> 
> A couple of years ago my mobile provider ran their own RCS server, since 
> then, they've (presumably like most others) migrated to using the 
> Jibe/Google servers.

Which is totally unacceptable for many users and also explains partially
Apple's unwillingness to fully adopt RCS.

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

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

#146348

On 2025-01-08 17:07, Jörg Lorenz wrote:
> On 08.01.25 16:40, Andy Burns wrote:
>> Carlos E.R. wrote:
>>
>>> Joe Beanfish wrote:
>>>>> Arno Welzel wrote:
>>>>
>>>>> Jörg Lorenz wrote:
>>>>>
>>>>>> Good to know that we should deactivate Google's wet dream
>>>>>> immediately. ;-)
>>>>>
>>>>> RCS is a standard protocol and not "Google's wet dream".
>>>>
>>>> Whose servers do RCS messages pass thru?
>>>
>>> It is quite difficult to know in each case, there is no trace
>>> information as there is with email.
>>
>> A couple of years ago my mobile provider ran their own RCS server, since
>> then, they've (presumably like most others) migrated to using the
>> Jibe/Google servers.
> 
> Which is totally unacceptable for many users and also explains partially
> Apple's unwillingness to fully adopt RCS.

They can run their own servers. And who cares who runs the servers, 
anyway, when messages are encrypted end to end.

Oh, wait... :-D

-- 
Cheers, Carlos.

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

#146365

On 08.01.25 21:06, Carlos E.R. wrote:
> On 2025-01-08 17:07, Jörg Lorenz wrote:
>> On 08.01.25 16:40, Andy Burns wrote:
>>> Carlos E.R. wrote:
>>>
>>>> Joe Beanfish wrote:
>>>>>> Arno Welzel wrote:
>>>>>
>>>>>> Jörg Lorenz wrote:
>>>>>>
>>>>>>> Good to know that we should deactivate Google's wet dream
>>>>>>> immediately. ;-)
>>>>>>
>>>>>> RCS is a standard protocol and not "Google's wet dream".
>>>>>
>>>>> Whose servers do RCS messages pass thru?
>>>>
>>>> It is quite difficult to know in each case, there is no trace
>>>> information as there is with email.
>>>
>>> A couple of years ago my mobile provider ran their own RCS server, since
>>> then, they've (presumably like most others) migrated to using the
>>> Jibe/Google servers.
>>
>> Which is totally unacceptable for many users and also explains partially
>> Apple's unwillingness to fully adopt RCS.
> 
> They can run their own servers. And who cares who runs the servers,
> anyway, when messages are encrypted end to end.

You do not understand the inferior technolgy used for RCS.


-- 
"Gutta cavat lapidem." (Ovid)

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

#146370

Jörg Lorenz, 2025-01-10 10:23:

[...]
> You do not understand the inferior technolgy used for RCS.

If Apple had invented it, you would call it superior ;-)


-- 
Arno Welzel
https://arnowelzel.de

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

#146369

Jörg Lorenz, 2025-01-08 17:07:

> On 08.01.25 16:40, Andy Burns wrote:
[...]
>> A couple of years ago my mobile provider ran their own RCS server, since 
>> then, they've (presumably like most others) migrated to using the 
>> Jibe/Google servers.
> 
> Which is totally unacceptable for many users and also explains partially
> Apple's unwillingness to fully adopt RCS.

But asking people to use iMessage and Apple services is totally fine?


-- 
Arno Welzel
https://arnowelzel.de

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

#146349

On 2025-01-08 16:40, Andy Burns wrote:
> Carlos E.R. wrote:
> 
>> Joe Beanfish wrote:
>>>> Arno Welzel wrote:
>>>
>>>> Jörg Lorenz wrote:
>>>>
>>>>> Good to know that we should deactivate Google's wet dream 
>>>>> immediately. ;-)
>>>>
>>>> RCS is a standard protocol and not "Google's wet dream".
>>>
>>> Whose servers do RCS messages pass thru?
>>
>> It is quite difficult to know in each case, there is no trace 
>> information as there is with email.
> 
> A couple of years ago my mobile provider ran their own RCS server, since 
> then, they've (presumably like most others) migrated to using the Jibe/ 
> Google servers.
> 

My ISP has their own servers, "Branded as joyn", launched on 2012. For 
android, the box for iPhone is empty.

-- 
Cheers, Carlos.

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

#146368

Joe Beanfish, 2025-01-07 14:38:

> On Sun, 05 Jan 2025 13:01:29 +0100, Arno Welzel wrote:
> 
>> Jörg Lorenz, 2025-01-04 13:51:
>>
>>> On 04.01.25 13:03, Carlos E.R. wrote:
>>>> On 2025-01-04 08:52, Dave Royal wrote:
>>>>> I don't
>>>>>   know - I don't use RCS.
>>>>
>>>> Next time you replace your phone, RCS should be enabled by default :-)
>>>
>>> Good to know that we should deactivate Google's wet dream immediately. ;-)
>>
>> RCS is a standard protocol and not "Google's wet dream".
> 
> Whose servers do RCS messages pass thru?

The servers of the providers. It is *not* a service provided by Google.
Google only added encryption for Android devices, so if the messaging
app on a device *knows* another recipient and the recipient also has
Android, messages can get encrypted, before they get sent.

Also see:

<https://www.gsma.com/solutions-and-impact/technologies/networks/rcs-frequently-asked-questions/>

Quote:

What infrastructure will operators need to deploy to take advantage of RCS?

RCS services are based on the IP-Multimedia Subsystem (IMS), as
specified by the 3GPP and adopted by major industry standardisation
bodies for mobile and fixed networks. Operators may implement their own
IMS solution or can access the services of a hosted solution to provide
a pre-IMS or partial-IMS implementation. The hosted solution may be a
temporary or permanent solution for the operator.


-- 
Arno Welzel
https://arnowelzel.de

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

#146248

Dave Royal, 2025-01-04 08:52:

> Arno Welzel <usenet@arnowelzel.de> Wrote in message:
[...]
>> Yes, but you will see if someone has RCS before you send the message
>> since using the phone number of the recipient the device can check, if
>> the recipient is connected to the RCS network services.
>>
> Might the recipient have seen the message in a notification on the
>  home screen, but not opened the messages app to read it? I don't
>  know - I don't use RCS.

It's the same as with any other app in Android. You get a notification
when a message arrives and how it is displayed depends on your privacy
settings.

In my case I configured my Smartphone so, that I just see that there is
a notification from a specific app, but no content. I have to unlock the
device first to be able to see the notification including text.

Also messages don't count as "read" as long as you do not open them in
the respective app. Just looking at the notification is not enough, even
when the notification also contains some (or all) of the text in the
message.


-- 
Arno Welzel
https://arnowelzel.de

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

#146233

In comp.mobile.android, on Fri, 3 Jan 2025 23:25:31 +0100, Arno Welzel
<usenet@arnowelzel.de> wrote:

>Joe Beanfish, 2025-01-03 14:46:
>
>> On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:
>>> RCS has this cool service.  When you send a text, it shows a little
>>> circle with a check mark in it. When the other party receives the text,
>>> it shows also an overlapping little circle with a check mark. When the
>>> other party READS the text I've sent, it shows both circles in blue.
>>>
>>> HOw cool is that. 
>>>
>> 
>> If the recipient doesn't have RCS, there will be no way to know if
>> they read or not and the circles wouldn't turn blue either way.

>Yes, but you will see if someone has RCS before you send the message
>since using the phone number of the recipient the device can check, if
>the recipient is connected to the RCS network services.

I didn't see any indication in advance or after that he didn't have RCS,
and I'd just about guarantee he read my two texts. And the one today.
I'm the contact for whether he is allowed to salt in advance of the
snow, and we're in a dispute already because he did it a couple weeks
ago without contacting me, and there was no snow. But he'd billed us
2000 dollars.  That's when he started texting me like he was supposed to
for the last 2 years. 

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

#146237

On 2025-01-05 02:45, micky wrote:
> In comp.mobile.android, on Fri, 3 Jan 2025 23:25:31 +0100, Arno Welzel
> <usenet@arnowelzel.de> wrote:
> 
>> Joe Beanfish, 2025-01-03 14:46:
>>
>>> On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:
>>>> RCS has this cool service.  When you send a text, it shows a little
>>>> circle with a check mark in it. When the other party receives the text,
>>>> it shows also an overlapping little circle with a check mark. When the
>>>> other party READS the text I've sent, it shows both circles in blue.
>>>>
>>>> HOw cool is that.
>>>>
>>>
>>> If the recipient doesn't have RCS, there will be no way to know if
>>> they read or not and the circles wouldn't turn blue either way.
> 
>> Yes, but you will see if someone has RCS before you send the message
>> since using the phone number of the recipient the device can check, if
>> the recipient is connected to the RCS network services.
> 
> I didn't see any indication in advance or after that he didn't have RCS,

Look carefully. In the message box before you start typing, there is a 
faint lettering that says RCS or SMS/MMS. RCS inside the box, sms above 
the box. The colour is also slightly different.

The google messages app has that feature.

...

-- 
Cheers, Carlos.

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

#146262

In comp.mobile.android, on Sun, 5 Jan 2025 04:05:56 +0100, "Carlos E.R."
<robin_listas@es.invalid> wrote:

>On 2025-01-05 02:45, micky wrote:
>> In comp.mobile.android, on Fri, 3 Jan 2025 23:25:31 +0100, Arno Welzel
>> <usenet@arnowelzel.de> wrote:
>> 
>>> Joe Beanfish, 2025-01-03 14:46:
>>>
>>>> On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:
>>>>> RCS has this cool service.  When you send a text, it shows a little
>>>>> circle with a check mark in it. When the other party receives the text,
>>>>> it shows also an overlapping little circle with a check mark. When the
>>>>> other party READS the text I've sent, it shows both circles in blue.
>>>>>
>>>>> HOw cool is that.
>>>>>
>>>>
>>>> If the recipient doesn't have RCS, there will be no way to know if
>>>> they read or not and the circles wouldn't turn blue either way.
>> 
>>> Yes, but you will see if someone has RCS before you send the message
>>> since using the phone number of the recipient the device can check, if
>>> the recipient is connected to the RCS network services.
>> 
>> I didn't see any indication in advance or after that he didn't have RCS,
>
>Look carefully. In the message box before you start typing, there is a 
>faint lettering that says RCS or SMS/MMS. RCS inside the box, sms above 
>the box. The colour is also slightly different.

Everyone I texted lately had within the message box "RCS mess...", but
just now I started to text somone else and it has "Text messa...", Also,
the RCS one has a white text area on a grey background and the SMS one
has a grey text area on a white background! So it seems like the
snowplow guy does have RCS but I still have no blue circles so, it's
impossible for me to believe he didn't read my texts yet so that means
it just doesn't work perfectly . One should not be surprised, LOL . 
>
>The google messages app has that feature.
>
>...

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

#146263

micky <NONONOmisc07@fmguy.com> wrote:
[...]
>					      So it seems like the
> snowplow guy does have RCS but I still have no blue circles so, it's
> impossible for me to believe he didn't read my texts yet so that means
> it just doesn't work perfectly . One should not be surprised, LOL . 

  It *does* work 'perfectly', but it can't do the impossible. I.e. it
can force the recipient to *really* read the text. And, as mentioned,
the opposite, the recipient *can* read the text without you knowing it,
either by reading it in the notification area or by turning off the read
check mark facility.

  The only guarantee is the delivery check mark. If that is ticked, the
message arrived at the destination, which is a device, not a person.

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

#146291

On 2025-01-05 16:46, micky wrote:
> In comp.mobile.android, on Sun, 5 Jan 2025 04:05:56 +0100, "Carlos E.R."
> <robin_listas@es.invalid> wrote:
> 
>> On 2025-01-05 02:45, micky wrote:
>>> In comp.mobile.android, on Fri, 3 Jan 2025 23:25:31 +0100, Arno Welzel
>>> <usenet@arnowelzel.de> wrote:
>>>
>>>> Joe Beanfish, 2025-01-03 14:46:
>>>>
>>>>> On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:
>>>>>> RCS has this cool service.  When you send a text, it shows a little
>>>>>> circle with a check mark in it. When the other party receives the text,
>>>>>> it shows also an overlapping little circle with a check mark. When the
>>>>>> other party READS the text I've sent, it shows both circles in blue.
>>>>>>
>>>>>> HOw cool is that.
>>>>>>
>>>>>
>>>>> If the recipient doesn't have RCS, there will be no way to know if
>>>>> they read or not and the circles wouldn't turn blue either way.
>>>
>>>> Yes, but you will see if someone has RCS before you send the message
>>>> since using the phone number of the recipient the device can check, if
>>>> the recipient is connected to the RCS network services.
>>>
>>> I didn't see any indication in advance or after that he didn't have RCS,
>>
>> Look carefully. In the message box before you start typing, there is a
>> faint lettering that says RCS or SMS/MMS. RCS inside the box, sms above
>> the box. The colour is also slightly different.
> 
> Everyone I texted lately had within the message box "RCS mess...", but
> just now I started to text somone else and it has "Text messa...", Also,
> the RCS one has a white text area on a grey background and the SMS one
> has a grey text area on a white background! So it seems like the
> snowplow guy does have RCS but I still have no blue circles so, it's
> impossible for me to believe he didn't read my texts yet so that means
> it just doesn't work perfectly . One should not be surprised, LOL .

There is another feature. Long tap on the message you sent. Then tap the 
three vertical dot menu on the top, and choose "details". A window pop 
up telling the technology used, and the timestamp: sent, received, read.

Of course, the recipient may just disable the timestamping, which is 
rude in this circumstance. You should write in the contract that the 
other parties must enable RCS with timestamping.

Then maybe he has an iphone and the implementation is lacking.


-- 
Cheers, Carlos.

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

#146250

micky, 2025-01-05 02:45:

> In comp.mobile.android, on Fri, 3 Jan 2025 23:25:31 +0100, Arno Welzel
> <usenet@arnowelzel.de> wrote:
> 
>> Joe Beanfish, 2025-01-03 14:46:
>>
>>> On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:
>>>> RCS has this cool service.  When you send a text, it shows a little
>>>> circle with a check mark in it. When the other party receives the text,
>>>> it shows also an overlapping little circle with a check mark. When the
>>>> other party READS the text I've sent, it shows both circles in blue.
>>>>
>>>> HOw cool is that. 
>>>>
>>>
>>> If the recipient doesn't have RCS, there will be no way to know if
>>> they read or not and the circles wouldn't turn blue either way.
> 
>> Yes, but you will see if someone has RCS before you send the message
>> since using the phone number of the recipient the device can check, if
>> the recipient is connected to the RCS network services.
> 
> I didn't see any indication in advance or after that he didn't have RCS,
[...]

In my Google Messages, which is the default for SMS/RCS on Pixel
devices, the input field for the text displays either "Text message" for
simple SMS or "RCS message" when the recipient is able to recieve RCS
messages.


-- 
Arno Welzel
https://arnowelzel.de

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

#149446

In comp.mobile.android, on Sun, 5 Jan 2025 13:03:43 +0100, Arno Welzel
<usenet@arnowelzel.de> wrote:

>micky, 2025-01-05 02:45:
>
>> In comp.mobile.android, on Fri, 3 Jan 2025 23:25:31 +0100, Arno Welzel
>> <usenet@arnowelzel.de> wrote:
>> 
>>> Joe Beanfish, 2025-01-03 14:46:
>>>
>>>> On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:
>>>>> RCS has this cool service.  When you send a text, it shows a little
>>>>> circle with a check mark in it. When the other party receives the text,
>>>>> it shows also an overlapping little circle with a check mark. When the
>>>>> other party READS the text I've sent, it shows both circles in blue.
>>>>>
>>>>> HOw cool is that. 
>>>>>
>>>>
>>>> If the recipient doesn't have RCS, there will be no way to know if
>>>> they read or not and the circles wouldn't turn blue either way.
>> 
>>> Yes, but you will see if someone has RCS before you send the message
>>> since using the phone number of the recipient the device can check, if
>>> the recipient is connected to the RCS network services.
>> 
>> I didn't see any indication in advance or after that he didn't have RCS,
>[...]
>
>In my Google Messages, which is the default for SMS/RCS on Pixel
>devices, the input field for the text displays either "Text message" for
>simple SMS or "RCS message" when the recipient is able to recieve RCS
>messages.

Oh, yeah.  Good to know. 

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

#146169

On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:

> RCS has this cool service.  When you send a text, it shows a little
> circle with a check mark in it. When the other party receives the text,
> it shows also an overlapping little circle with a check mark. When the
> other party READS the text I've sent, it shows both circles in blue.
> 
> HOw cool is that. 

I turned that off, so you won't see anything when you text me. Turned
off the typing indicator as well.

-- 
s|b

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

#146175

On 04.01.25 11:00, s|b wrote:
> On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:
> 
>> RCS has this cool service.  When you send a text, it shows a little
>> circle with a check mark in it. When the other party receives the text,
>> it shows also an overlapping little circle with a check mark. When the
>> other party READS the text I've sent, it shows both circles in blue.
>>
>> HOw cool is that. 
> 
> I turned that off, so you won't see anything when you text me. Turned
> off the typing indicator as well.

Voilà! Same here.


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

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

#146251

Jörg Lorenz, 2025-01-04 12:21:

> On 04.01.25 11:00, s|b wrote:
>> On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:
>>
>>> RCS has this cool service.  When you send a text, it shows a little
>>> circle with a check mark in it. When the other party receives the text,
>>> it shows also an overlapping little circle with a check mark. When the
>>> other party READS the text I've sent, it shows both circles in blue.
>>>
>>> HOw cool is that. 
>>
>> I turned that off, so you won't see anything when you text me. Turned
>> off the typing indicator as well.
> 
> Voilà! Same here.

Well - the typing indicator is understandable. But why disabling RCS
completely? What's wrong with using RCS at all?


-- 
Arno Welzel
https://arnowelzel.de

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

#146258

On 2025-01-05 13:04, Arno Welzel wrote:
> Jörg Lorenz, 2025-01-04 12:21:
> 
>> On 04.01.25 11:00, s|b wrote:
>>> On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:
>>>
>>>> RCS has this cool service.  When you send a text, it shows a little
>>>> circle with a check mark in it. When the other party receives the text,
>>>> it shows also an overlapping little circle with a check mark. When the
>>>> other party READS the text I've sent, it shows both circles in blue.
>>>>
>>>> HOw cool is that.
>>>
>>> I turned that off, so you won't see anything when you text me. Turned
>>> off the typing indicator as well.
>>
>> Voilà! Same here.
> 
> Well - the typing indicator is understandable. But why disabling RCS
> completely? What's wrong with using RCS at all?

Nothing. He just has that mania.

-- 
Cheers, Carlos.

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

#146261

Carlos E.R. <robin_listas@es.invalid> wrote:
> On 2025-01-05 13:04, Arno Welzel wrote:
> > Jörg Lorenz, 2025-01-04 12:21:
> > 
> >> On 04.01.25 11:00, s|b wrote:
> >>> On Thu, 02 Jan 2025 22:55:06 -0500, micky wrote:
> >>>
> >>>> RCS has this cool service.  When you send a text, it shows a little
> >>>> circle with a check mark in it. When the other party receives the text,
> >>>> it shows also an overlapping little circle with a check mark. When the
> >>>> other party READS the text I've sent, it shows both circles in blue.
> >>>>
> >>>> HOw cool is that.
> >>>
> >>> I turned that off, so you won't see anything when you text me. Turned
> >>> off the typing indicator as well.
> >>
> >> Voilà! Same here.
> > 
> > Well - the typing indicator is understandable. But why disabling RCS
> > completely? What's wrong with using RCS at all?
> 
> Nothing. He just has that mania.

  I think 's|b' refers to the read check mark, not RCS itself, as he
says "Turned off the typing indicator as well." If RCS is turned off,
there's no typing indicator to turn off (or on).
> 

 
> -- 
> Cheers, Carlos.

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

Page 3 of 4 — ← Prev page 1 2 [3] 4  Next page →

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

csiph-web