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


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

RCS chats

Started byStan Brown <the_stan_brown@fastmail.fm>
First post2023-10-28 11:10 -0700
Last post2023-11-01 09:54 +0100
Articles 20 on this page of 95 — 11 participants

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


Contents

  RCS chats Stan Brown <the_stan_brown@fastmail.fm> - 2023-10-28 11:10 -0700
    Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-10-28 19:22 +0100
    Re: RCS chats Bob Henson <bob.henson@outlook.com> - 2023-10-28 19:50 +0100
      Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-28 23:16 +0200
        Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-10-29 07:04 +0000
          Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 08:10 +0100
    Re: RCS chats KenW                                        <ken1943@invalid.net> - 2023-10-28 13:43 -0600
    Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-28 23:11 +0200
    Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 08:00 +0100
      Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-29 12:54 +0100
        Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 16:05 +0100
          Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-29 20:09 +0100
            Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 21:34 +0100
              Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-30 19:12 +0100
                Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-10-30 18:34 +0000
                  Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-31 09:59 +0100
                Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-31 02:51 +0100
                  Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-31 14:49 +0100
                    Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-31 16:53 +0100
            Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-10-30 15:26 +0000
              Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-30 19:18 +0100
              Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 09:52 +0100
                Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-01 16:27 +0000
            Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-01 08:40 +0100
              Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 09:48 +0100
              Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-01 14:11 +0100
                Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-01 20:46 +0100
                  Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-01 20:53 +0100
                    Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-02 07:47 +0100
                      Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 10:57 +0100
                        Re: RCS chats Adrian <bulleid@ku.gro.lioff> - 2023-11-02 14:33 +0000
                          Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 16:08 +0000
                          Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:21 +0100
                    Re: RCS chats Bob Henson <bob.henson@outlook.com> - 2023-11-02 09:16 +0000
                      Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 11:04 +0100
                      Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-11-02 10:05 +0000
                        Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 11:25 +0100
                        Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 19:18 +0100
                    Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-02 14:15 +0100
                      Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:32 +0100
                        Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 19:20 +0100
                          Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-03 22:58 +0100
                  Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 13:21 +0000
                    Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-02 17:21 +0100
                      Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 16:44 +0000
                        Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:50 +0100
                      Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 19:21 +0100
                    Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:45 +0100
                      Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 18:18 +0000
                        Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 19:35 +0100
                          Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 20:01 +0000
        Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 16:13 +0100
        Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 16:19 +0100
      Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-01 08:37 +0100
        Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 09:50 +0100
          Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-01 13:28 +0100
    Re: RCS chats Stan Brown <the_stan_brown@fastmail.fm> - 2023-10-29 09:49 -0700
      Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-29 20:14 +0100
        Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-10-29 21:37 +0100
      Re: RCS chats Wally J <walterjones@invalid.nospam> - 2023-10-30 16:49 -0400
        Re: RCS chats Stan Brown <the_stan_brown@fastmail.fm> - 2023-10-31 12:12 -0700
          Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-10-31 21:44 +0100
            Re: RCS chats Stan Brown <the_stan_brown@fastmail.fm> - 2023-11-01 01:22 -0700
              Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-01 08:42 +0000
                Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 10:01 +0100
              Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 09:58 +0100
              Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-11-01 09:12 +0000
                Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-01 16:54 +0000
                  Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-01 19:11 +0100
                  Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-01 21:04 +0100
                    Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-01 20:30 +0000
                    Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-11-01 20:56 +0000
                      Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-01 23:09 +0100
                        Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-02 17:30 +0100
                          Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:53 +0100
                            Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 19:24 +0100
                              Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-03 18:54 +0000
                                Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 22:59 +0100
                              Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-03 23:01 +0100
                                Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-05 19:21 +0100
                          Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-02 18:14 +0000
                            Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 19:24 +0100
                              Re: RCS chats Arno Welzel <usenet@arnowelzel.de> - 2023-11-03 19:25 +0100
                    Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 13:32 +0000
                      Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-02 13:50 +0000
                        Re: RCS chats Frank Slootweg <this@ddress.is.invalid> - 2023-11-02 14:17 +0000
                      Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-02 18:56 +0100
                Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-11-08 20:13 +0000
                  Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-09 09:57 +0000
                    Re: RCS chats Dave Royal<dave@dave123royal.com> - 2023-11-09 15:48 +0000
                      Re: RCS chats Andy Burns <usenet@andyburns.uk> - 2023-11-09 16:59 +0000
                      Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 20:29 +0100
              Re: RCS chats "Carlos E. R." <robin_listas@es.invalid> - 2023-11-01 14:16 +0100
              Re: RCS chats Stan Brown <the_stan_brown@fastmail.fm> - 2023-11-01 10:52 -0700
            Re: RCS chats Jörg Lorenz <hugybear@gmx.net> - 2023-11-01 09:54 +0100

Page 1 of 5  [1] 2 3 4 5  Next page →


#109304 — RCS chats

FromStan Brown <the_stan_brown@fastmail.fm>
Date2023-10-28 11:10 -0700
SubjectRCS chats
Message-ID<MPG.3fa6ee6f5cfd6e9b9901f9@news.individual.net>
Samsung Galaxy A54, Android 13

I use the Google Messaging app. It's started nagging me 
to enable RCS Chats. I did some googling, but the 
articles all seem to be either the nuts and bolts of 
enabling/disabling, or glowing but vague praises of how 
wonderful RCS Chats is.

Potential cons:

1. Doesn't work for iPhones. (The family and friends I 
frequently text with all have iPhones.)

2. Businesses can send long messages, big files, and 
videos, and learn whether I ever opened them.

Has anyone here actually enabled RCS Chats, and if so 
could you mention one or two reasons why I might want 
to?

-- 
Stan Brown, Tehachapi, California, USA         
https://BrownMath.com/
Shikata ga nai...

[toc] | [next] | [standalone]


#109305

FromAndy Burns <usenet@andyburns.uk>
Date2023-10-28 19:22 +0100
Message-ID<kq51qvFk5beU1@mid.individual.net>
In reply to#109304
Stan Brown wrote:

> 1. Doesn't work for iPhones. (The family and friends I
> frequently text with all have iPhones.)

Just reverts to SMS (or MMS I guess, I never send those due to £££)

> 2. Businesses can send long messages, big files, and
> videos, and learn whether I ever opened them.

You can turn off read receipt (and typing indicators)

> Has anyone here actually enabled RCS Chats, and if so
> could you mention one or two reasons why I might want
> to?

Yes, my network used to provide RCS via their own servers, they have 
recently bounced users over to Google/jibe's servers, can't comment yet 
if the reliability has changed.

I don't do WhatsApp (and trying to convince friends to use 
Signal/Telegram would be an uphill struggle) so the ability to sent free 
picture messages to at least my android-using contacts is handy.

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


#109306

FromBob Henson <bob.henson@outlook.com>
Date2023-10-28 19:50 +0100
Message-ID<174zzfw4caxi1$.1migkpgkg4sea.dlg@40tude.net>
In reply to#109304
Stan Brown wrote:

> Samsung Galaxy A54, Android 13
> 
> I use the Google Messaging app. It's started nagging me 
> to enable RCS Chats. I did some googling, but the 
> articles all seem to be either the nuts and bolts of 
> enabling/disabling, or glowing but vague praises of how 
> wonderful RCS Chats is.
> 
> Potential cons:
> 
> 1. Doesn't work for iPhones. (The family and friends I 
> frequently text with all have iPhones.)
> 
> 2. Businesses can send long messages, big files, and 
> videos, and learn whether I ever opened them.
> 
> Has anyone here actually enabled RCS Chats, and if so 
> could you mention one or two reasons why I might want 
> to?

If it is enabled and you accidentally go over the SMS limit, or add
something that isn't allowed in SMS, it sends it as an MMS and costs a
mint. There may be a way to prevent that now, but I couldn't find one at
the time it first appeared. I found another app that only does SMS
(Spamhound) and which enables blocking of commercial and other spam. I'm
sure there are others which are SMS only. 


-- 
Bob
Tetbury, Gloucestershire, England

Can you be a closet claustrophobic?

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


#109311

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-10-28 23:16 +0200
Message-ID<kq5c1tF4a7cU9@mid.individual.net>
In reply to#109306
On 2023-10-28 20:50, Bob Henson wrote:
> Stan Brown wrote:
> 
>> Samsung Galaxy A54, Android 13
>>
>> I use the Google Messaging app. It's started nagging me
>> to enable RCS Chats. I did some googling, but the
>> articles all seem to be either the nuts and bolts of
>> enabling/disabling, or glowing but vague praises of how
>> wonderful RCS Chats is.
>>
>> Potential cons:
>>
>> 1. Doesn't work for iPhones. (The family and friends I
>> frequently text with all have iPhones.)
>>
>> 2. Businesses can send long messages, big files, and
>> videos, and learn whether I ever opened them.
>>
>> Has anyone here actually enabled RCS Chats, and if so
>> could you mention one or two reasons why I might want
>> to?
> 
> If it is enabled and you accidentally go over the SMS limit, or add
> something that isn't allowed in SMS, it sends it as an MMS and costs a
> mint. There may be a way to prevent that now, but I couldn't find one at
> the time it first appeared. I found another app that only does SMS
> (Spamhound) and which enables blocking of commercial and other spam. I'm
> sure there are others which are SMS only.

It was common for apps to tell you when the current message would be 
sent as MMS.

-- 
Cheers,
        Carlos E.R.

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


#109315

FromAndy Burns <usenet@andyburns.uk>
Date2023-10-29 07:04 +0000
Message-ID<kq6eg5Ftb1cU1@mid.individual.net>
In reply to#109311
Carlos E. R. wrote:

> It was common for apps to tell you when the current message would be 
> sent as MMS.

I do remember an issue around the android 4.x era where the stock 
messaging app would 'promote' an SMS message sent to multiple recipients 
into an MMS message for group chat.

But google hadn't realised that SMS and MMS were/are charged very 
differently in some countries (e.g. the UK) they must have got plenty of 
complaints as it was soon reversed.

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


#109316

FromJörg Lorenz <hugybear@gmx.net>
Date2023-10-29 08:10 +0100
Message-ID<uhl0ha$3otg1$1@dont-email.me>
In reply to#109315
Am 29.10.23 um 08:04 schrieb Andy Burns:
> Carlos E. R. wrote:
> 
>> It was common for apps to tell you when the current message would be
>> sent as MMS.
> 
> I do remember an issue around the android 4.x era where the stock
> messaging app would 'promote' an SMS message sent to multiple recipients
> into an MMS message for group chat.
> 
> But google hadn't realised that SMS and MMS were/are charged very
> differently in some countries (e.g. the UK) they must have got plenty of
> complaints as it was soon reversed.

Because of cost and quality issues MMS never reached a relevant market 
share in Europe. In some countries like Switzerland for instance 
MMS-services were ceased a while ago.

-- 
Gutta cavat lapidem (Ovid)

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


#109308

FromKenW <ken1943@invalid.net>
Date2023-10-28 13:43 -0600
Message-ID<31pqjitik7lg9n5e5qq3teltl9ec4kullh@4ax.com>
In reply to#109304
On Sat, 28 Oct 2023 11:10:28 -0700, Stan Brown
<the_stan_brown@fastmail.fm> wrote:

>Samsung Galaxy A54, Android 13
>
>I use the Google Messaging app. It's started nagging me 
>to enable RCS Chats. I did some googling, but the 
>articles all seem to be either the nuts and bolts of 
>enabling/disabling, or glowing but vague praises of how 
>wonderful RCS Chats is.
>
>Potential cons:
>
>1. Doesn't work for iPhones. (The family and friends I 
>frequently text with all have iPhones.)
>
>2. Businesses can send long messages, big files, and 
>videos, and learn whether I ever opened them.
>
>Has anyone here actually enabled RCS Chats, and if so 
>could you mention one or two reasons why I might want 
>to?

Don't forget Google saves every message. That is why I went back to
original messaging app.


KenW

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


#109310

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-10-28 23:11 +0200
Message-ID<kq5bo7F4a7bU2@mid.individual.net>
In reply to#109304
On 2023-10-28 20:10, Stan Brown wrote:
> Samsung Galaxy A54, Android 13
> 
> I use the Google Messaging app. It's started nagging me
> to enable RCS Chats. I did some googling, but the
> articles all seem to be either the nuts and bolts of
> enabling/disabling, or glowing but vague praises of how
> wonderful RCS Chats is.
> 
> Potential cons:
> 
> 1. Doesn't work for iPhones. (The family and friends I
> frequently text with all have iPhones.)

Doesn't matter. If RCS is not available, the tool will use the previous 
method.


> 2. Businesses can send long messages, big files, and
> videos, and learn whether I ever opened them.

I've never been sent anything "big". I don't know about they knowing if 
you opened the message or files. I'll have to find out about that.

The feature exists in email since decades, but many clients ask you 
before sending that information back (configurable). Windows perhaps 
sends it silently.

WhatsApp, for instance, behaves by default that way (for every message). 
No big deal, you can disable it.

> 
> Has anyone here actually enabled RCS Chats, and if so
> could you mention one or two reasons why I might want
> to?

I enabled it soon after I learned about it.

It has features that have been there since ages for other messaging 
apps, like WhatsApp. I have not seen anything bad about it. The worst 
that I heard is that it will not get enough users to matter.

For me, it has one very important feature: sending a message to my 
relatives across the pond costs me money, as much as an euro per 
message. But sending via RCS is free. If you live in NA and only message 
people in NA, it will not matter to you.

-- 
Cheers,
        Carlos E.R.

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


#109314

FromJörg Lorenz <hugybear@gmx.net>
Date2023-10-29 08:00 +0100
Message-ID<uhkvv4$3oglq$4@dont-email.me>
In reply to#109304
Am 28.10.23 um 20:10 schrieb Stan Brown:
> Samsung Galaxy A54, Android 13
> 
> I use the Google Messaging app. It's started nagging me
> to enable RCS Chats. I did some googling, but the
> articles all seem to be either the nuts and bolts of
> enabling/disabling, or glowing but vague praises of how
> wonderful RCS Chats is.
> 
> Potential cons:
> 
> 1. Doesn't work for iPhones. (The family and friends I
> frequently text with all have iPhones.)
> 
> 2. Businesses can send long messages, big files, and
> videos, and learn whether I ever opened them.
> 
> Has anyone here actually enabled RCS Chats, and if so
> could you mention one or two reasons why I might want
> to?

You summarize it: RCS is a very old Nokia development.
Nobody needs it and almost 50% of mobiles in the field cannot receive or 
send it. Privacy is abusive and it is a project of a frustrated 
Google-company that missed out the instant messaging market completely.

It is so simple: Nobody needs it.

-- 
Gutta cavat lapidem (Ovid)

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


#109324

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-10-29 12:54 +0100
Message-ID<kq6vgbF4a7cU10@mid.individual.net>
In reply to#109314
On 2023-10-29 08:00, Jörg Lorenz wrote:
> Am 28.10.23 um 20:10 schrieb Stan Brown:
>> Samsung Galaxy A54, Android 13
>>
>> I use the Google Messaging app. It's started nagging me
>> to enable RCS Chats. I did some googling, but the
>> articles all seem to be either the nuts and bolts of
>> enabling/disabling, or glowing but vague praises of how
>> wonderful RCS Chats is.
>>
>> Potential cons:
>>
>> 1. Doesn't work for iPhones. (The family and friends I
>> frequently text with all have iPhones.)
>>
>> 2. Businesses can send long messages, big files, and
>> videos, and learn whether I ever opened them.
>>
>> Has anyone here actually enabled RCS Chats, and if so
>> could you mention one or two reasons why I might want
>> to?
> 
> You summarize it: RCS is a very old Nokia development.
> Nobody needs it and almost 50% of mobiles in the field cannot receive or 
> send it. Privacy is abusive and it is a project of a frustrated 
> Google-company that missed out the instant messaging market completely.
> 
> It is so simple: Nobody needs it.
> 


Stan: don't listen to him.

-- 
Cheers,
        Carlos E.R.

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


#109333

FromJörg Lorenz <hugybear@gmx.net>
Date2023-10-29 16:05 +0100
Message-ID<uhlsbl$3tsms$4@dont-email.me>
In reply to#109324
Am 29.10.23 um 12:54 schrieb Carlos E. R.:
> On 2023-10-29 08:00, Jörg Lorenz wrote:
>> You summarize it: RCS is a very old Nokia development.
>> Nobody needs it and almost 50% of mobiles in the field cannot receive or
>> send it. Privacy is abusive and it is a project of a frustrated
>> Google-company that missed out the instant messaging market completely.
>>
>> It is so simple: Nobody needs it.
>>
> 
> 
> Stan: don't listen to him.

Carlos: Learn to face the facts! Nobody needs RCS.
*RCS is a gimp*. If someone wants to enjoy privacy RCS is the hell. And 
if someone wants to chat even WhatsApp is the better solution.

-- 
Gutta cavat lapidem (Ovid)

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


#109343

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-10-29 20:09 +0100
Message-ID<kq7p07F4a7bU4@mid.individual.net>
In reply to#109333
On 2023-10-29 16:05, Jörg Lorenz wrote:
> Am 29.10.23 um 12:54 schrieb Carlos E. R.:
>> On 2023-10-29 08:00, Jörg Lorenz wrote:
>>> You summarize it: RCS is a very old Nokia development.
>>> Nobody needs it and almost 50% of mobiles in the field cannot receive or
>>> send it. Privacy is abusive and it is a project of a frustrated
>>> Google-company that missed out the instant messaging market completely.
>>>
>>> It is so simple: Nobody needs it.
>>>
>>
>>
>> Stan: don't listen to him.
> 
> Carlos: Learn to face the facts! Nobody needs RCS.

I do, that's a fact, so you got your facts wrong.

You have claimed that many times, your ideas were debunked by several 
posters, but you insist in your false claims.

So your facts are just your personal opinions.

-- 
Cheers,
        Carlos E.R.

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


#109347

FromJörg Lorenz <hugybear@gmx.net>
Date2023-10-29 21:34 +0100
Message-ID<uhmfko$22sf$1@dont-email.me>
In reply to#109343
Am 29.10.23 um 20:09 schrieb Carlos E. R.:
> On 2023-10-29 16:05, Jörg Lorenz wrote:
>> Am 29.10.23 um 12:54 schrieb Carlos E. R.:
>>> On 2023-10-29 08:00, Jörg Lorenz wrote:
>>>> You summarize it: RCS is a very old Nokia development.
>>>> Nobody needs it and almost 50% of mobiles in the field cannot receive or
>>>> send it. Privacy is abusive and it is a project of a frustrated
>>>> Google-company that missed out the instant messaging market completely.
>>>>
>>>> It is so simple: Nobody needs it.
>>>>
>>>
>>>
>>> Stan: don't listen to him.
>>
>> Carlos: Learn to face the facts! Nobody needs RCS.
> 
> I do, that's a fact, so you got your facts wrong.
> 
> You have claimed that many times, your ideas were debunked by several
> posters, but you insist in your false claims.
> 
> So your facts are just your personal opinions.

Google supports RCS on Android devices with its Android SMS app
Messages. In April 2018, it was reported that Google would be
transferring the team that was working on its Google Allo messaging
service to work on a wider RCS implementation.[19][20][21] In June 2019,
Google announced that it would begin to deploy RCS on an opt-in basis
via the Messages app, with service compliant with the Universal Profile
and hosted by Google rather than the user's carrier. The rollout of this
functionality began in France and the United Kingdom.[19][20] Google
initially branded RCS functionality under the generic term "chat
features"; in February 2023 Google began to replace references to "chat"
with "RCS".[7]

In response to concerns over the lack of end-to-end encryption in RCS,
Google stated that it would only retain message data in transit until it
is delivered to the recipient.

Wikipedia: https://en.wikipedia.org/wiki/Rich_Communication_Services

*Nobody needs it*!


-- 
Gutta cavat lapidem (Ovid)

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


#109386

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-10-30 19:12 +0100
Message-ID<kqaa0uFccrrU3@mid.individual.net>
In reply to#109347
On 2023-10-29 21:34, Jörg Lorenz wrote:
> Am 29.10.23 um 20:09 schrieb Carlos E. R.:
>> On 2023-10-29 16:05, Jörg Lorenz wrote:
>>> Am 29.10.23 um 12:54 schrieb Carlos E. R.:
>>>> On 2023-10-29 08:00, Jörg Lorenz wrote:
>>>>> You summarize it: RCS is a very old Nokia development.
>>>>> Nobody needs it and almost 50% of mobiles in the field cannot 
>>>>> receive or
>>>>> send it. Privacy is abusive and it is a project of a frustrated
>>>>> Google-company that missed out the instant messaging market 
>>>>> completely.
>>>>>
>>>>> It is so simple: Nobody needs it.
>>>>>
>>>>
>>>>
>>>> Stan: don't listen to him.
>>>
>>> Carlos: Learn to face the facts! Nobody needs RCS.
>>
>> I do, that's a fact, so you got your facts wrong.
>>
>> You have claimed that many times, your ideas were debunked by several
>> posters, but you insist in your false claims.
>>
>> So your facts are just your personal opinions.
> 
> Google supports RCS on Android devices with its Android SMS app
> Messages. In April 2018, it was reported that Google would be
> transferring the team that was working on its Google Allo messaging
> service to work on a wider RCS implementation.[19][20][21] In June 2019,
> Google announced that it would begin to deploy RCS on an opt-in basis
> via the Messages app, with service compliant with the Universal Profile
> and hosted by Google rather than the user's carrier. The rollout of this
> functionality began in France and the United Kingdom.[19][20] Google
> initially branded RCS functionality under the generic term "chat
> features"; in February 2023 Google began to replace references to "chat"
> with "RCS".[7]
> 
> In response to concerns over the lack of end-to-end encryption in RCS,
> Google stated that it would only retain message data in transit until it
> is delivered to the recipient.

So what? :-D

Without RCS, the default messaging app doesn't ever encrypt anything. 
SMSs are sent in the clear.

And we are talking of the default messaging application.


> 
> Wikipedia: https://en.wikipedia.org/wiki/Rich_Communication_Services
> 
> *Nobody needs it*!
> 
> 

-- 
Cheers,
        Carlos E.R.

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


#109388

FromDave Royal<dave@dave123royal.com>
Date2023-10-30 18:34 +0000
Message-ID<uhot0i$j0rm$1@dont-email.me>
In reply to#109386
On 30 Oct 2023 19:12:46 +0100 Carlos E. R. wrote:
>On 2023-10-29 21:34, Jörg Lorenz wrote:
>> Am 29.10.23 um 20:09 schrieb Carlos E. R.:
>>> On 2023-10-29 16:05, Jörg Lorenz wrote:
>>>> Am 29.10.23 um 12:54 schrieb Carlos E. R.:
>>>>> On 2023-10-29 08:00, Jörg Lorenz wrote:
>>>>>> You summarize it: RCS is a very old Nokia development.
>>>>>> Nobody needs it and almost 50% of mobiles in the field cannot 
>>>>>> receive or
>>>>>> send it. Privacy is abusive and it is a project of a frustrated
>>>>>> Google-company that missed out the instant messaging market 
>>>>>> completely.
>>>>>>
>>>>>> It is so simple: Nobody needs it.
>>>>>>
>>>>>
>>>>>
>>>>> Stan: don't listen to him.
>>>>
>>>> Carlos: Learn to face the facts! Nobody needs RCS.
>>>
>>> I do, that's a fact, so you got your facts wrong.
>>>
>>> You have claimed that many times, your ideas were debunked by several
>>> posters, but you insist in your false claims.
>>>
>>> So your facts are just your personal opinions.
>> 
>> Google supports RCS on Android devices with its Android SMS app
>> Messages. In April 2018, it was reported that Google would be
>> transferring the team that was working on its Google Allo messaging
>> service to work on a wider RCS implementation.[19][20][21] In June 2019,
>> Google announced that it would begin to deploy RCS on an opt-in basis
>> via the Messages app, with service compliant with the Universal Profile
>> and hosted by Google rather than the user's carrier. The rollout of this
>> functionality began in France and the United Kingdom.[19][20] Google
>> initially branded RCS functionality under the generic term "chat
>> features"; in February 2023 Google began to replace references to "chat"
>> with "RCS".[7]
>> 
>> In response to concerns over the lack of end-to-end encryption in RCS,
>> Google stated that it would only retain message data in transit until it
>> is delivered to the recipient.
>
>So what? :-D
>
>Without RCS, the default messaging app doesn't ever encrypt anything. 
>SMSs are sent in the clear.
>
>And we are talking of the default messaging application.
>

"Never argue with a fool, for he is doing the same."
(Les Barker.)


-- 
(Remove numerics from email address)

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


#109403

FromJörg Lorenz <hugybear@gmx.net>
Date2023-10-31 09:59 +0100
Message-ID<uhqfl3$utpc$3@dont-email.me>
In reply to#109388
On 30.10.23 19:34, Dave Royal wrote:
> "Never argue with a fool, for he is doing the same."
> (Les Barker.)

That's why I can easily abstain from talking to you, Troll.

-- 
Gutta cavat lapidem (Ovid)

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


#109396

FromJörg Lorenz <hugybear@gmx.net>
Date2023-10-31 02:51 +0100
Message-ID<uhpmjc$n827$1@dont-email.me>
In reply to#109386
Am 30.10.23 um 19:12 schrieb Carlos E. R.:
> On 2023-10-29 21:34, Jörg Lorenz wrote:
>> Google supports RCS on Android devices with its Android SMS app
>> Messages. In April 2018, it was reported that Google would be
>> transferring the team that was working on its Google Allo messaging
>> service to work on a wider RCS implementation.[19][20][21] In June 2019,
>> Google announced that it would begin to deploy RCS on an opt-in basis
>> via the Messages app, with service compliant with the Universal Profile
>> and hosted by Google rather than the user's carrier. The rollout of this
>> functionality began in France and the United Kingdom.[19][20] Google
>> initially branded RCS functionality under the generic term "chat
>> features"; in February 2023 Google began to replace references to "chat"
>> with "RCS".[7]
>>
>> In response to concerns over the lack of end-to-end encryption in RCS,
>> Google stated that it would only retain message data in transit until it
>> is delivered to the recipient.
> 
> So what? :-D
> 
> Without RCS, the default messaging app doesn't ever encrypt anything.
> SMSs are sent in the clear.

That is OT and everybody knows it.

> And we are talking of the default messaging application.

Who cares? RCS is a gimp.

-- 
Gutta cavat lapidem (Ovid)

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


#109404

From"Carlos E. R." <robin_listas@es.invalid>
Date2023-10-31 14:49 +0100
Message-ID<kqcf06FccrqU1@mid.individual.net>
In reply to#109396
On 2023-10-31 02:51, Jörg Lorenz wrote:
> Am 30.10.23 um 19:12 schrieb Carlos E. R.:
>> On 2023-10-29 21:34, Jörg Lorenz wrote:
>>> Google supports RCS on Android devices with its Android SMS app
>>> Messages. In April 2018, it was reported that Google would be
>>> transferring the team that was working on its Google Allo messaging
>>> service to work on a wider RCS implementation.[19][20][21] In June 2019,
>>> Google announced that it would begin to deploy RCS on an opt-in basis
>>> via the Messages app, with service compliant with the Universal Profile
>>> and hosted by Google rather than the user's carrier. The rollout of this
>>> functionality began in France and the United Kingdom.[19][20] Google
>>> initially branded RCS functionality under the generic term "chat
>>> features"; in February 2023 Google began to replace references to "chat"
>>> with "RCS".[7]
>>>
>>> In response to concerns over the lack of end-to-end encryption in RCS,
>>> Google stated that it would only retain message data in transit until it
>>> is delivered to the recipient.
>>
>> So what? :-D
>>
>> Without RCS, the default messaging app doesn't ever encrypt anything.
>> SMSs are sent in the clear.
> 
> That is OT and everybody knows it.

LOL!  That's a new one. Not accepted :-P

> 
>> And we are talking of the default messaging application.
> 
> Who cares? RCS is a gimp.
> 

-- 
Cheers,
        Carlos E.R.

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


#109405

FromJörg Lorenz <hugybear@gmx.net>
Date2023-10-31 16:53 +0100
Message-ID<uhr7tv$uc09$3@solani.org>
In reply to#109404
Am 31.10.23 um 14:49 schrieb Carlos E. R.:
> On 2023-10-31 02:51, Jörg Lorenz wrote:
>> Am 30.10.23 um 19:12 schrieb Carlos E. R.:
>>> And we are talking of the default messaging application.
>>
>> Who cares? RCS is a gimp.

And one day you will be alone and lonely in your RCS-bubble.

-- 
Alea icacta est

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


#109378

FromFrank Slootweg <this@ddress.is.invalid>
Date2023-10-30 15:26 +0000
Message-ID<uholf3.i04.1@ID-201911.user.individual.net>
In reply to#109343
Carlos E. R. <robin_listas@es.invalid> wrote:
> On 2023-10-29 16:05, Jörg Lorenz wrote:
> > Am 29.10.23 um 12:54 schrieb Carlos E. R.:
> >> On 2023-10-29 08:00, Jörg Lorenz wrote:
> >>> You summarize it: RCS is a very old Nokia development.
> >>> Nobody needs it and almost 50% of mobiles in the field cannot receive or
> >>> send it. Privacy is abusive and it is a project of a frustrated
> >>> Google-company that missed out the instant messaging market completely.
> >>>
> >>> It is so simple: Nobody needs it.
> >>
> >> Stan: don't listen to him.
> > 
> > Carlos: Learn to face the facts! Nobody needs RCS.
> 
> I do, that's a fact, so you got your facts wrong.
> 
> You have claimed that many times, your ideas were debunked by several 
> posters, but you insist in your false claims.
> 
> So your facts are just your personal opinions.

  Don't be so hard on poor Jörg! He can't help it that he has no display
or/and no eyes or/and no <deleted>, can he!?

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


Page 1 of 5  [1] 2 3 4 5  Next page →

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


csiph-web