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


Groups > comp.mobile.android > #109473

Re: RCS chats

From "Carlos E. R." <robin_listas@es.invalid>
Newsgroups comp.mobile.android
Subject Re: RCS chats
Date 2023-11-02 18:21 +0100
Message-ID <kqi454Fdm1dU5@mid.individual.net> (permalink)
References (7 earlier) <kqfo9gF2eb8U1@mid.individual.net> <kqfoltFu39U3@mid.individual.net> <uhvgmp$224nk$1@dont-email.me> <kqha4eFdm1eU1@mid.individual.net> <L34j9vE8M7QlFwdY@ku.gro.lloiff>

Show all headers | View raw


On 2023-11-02 15:33, Adrian wrote:
> In message <kqha4eFdm1eU1@mid.individual.net>, Carlos E. R. 
> <robin_listas@es.invalid> writes
>> On 2023-11-02 07:47, Jörg Lorenz wrote:
>>> Am 01.11.23 um 20:53 schrieb Carlos E. R.:
>>>> On 2023-11-01 20:46, Arno Welzel wrote:
>>>>> Carlos E. R., 2023-11-01 14:11:
>>>>>
>>>>>> On 2023-11-01 08:40, Arno Welzel wrote:
>>>>> [...]
>>>>>>> Can you send messages using RCS
>>>>>>> to people with an Apple iPhone?
>>>>>>
>>>>>> I don't care, I don't have many people in my circle with those.
>>>>>
>>>>> Ok - then go ahead an just use it. But this won't change the fact, 
>>>>> that
>>>>> RCS in general is not very widespread.
>>>>
>>>> That's not a problem, as long as the people I connect to activate it.
>>>> And it is gaining users, anyway. WhatsApp didn't have many users at the
>>>> start, either.
>>>>
>>>> I don't see why some people are against it and get kind of angry about
>>>> it. Why does it matter to them to want it to fail? Perhaps these people
>>>> have Apple shares?
>>>  The issue being functionality and privacy.
>>
>> Functionality? What functionality problem has it?
>>
>> Privacy? It replaces SMS, which has none.
>>
> 
> I don't have a dog in this fight.
> 
> There are two sides to privacy.  One is being unable to read a message, 
> the other is who can see who is communicating with who.  With SMS, who 
> apart from the Telcos can see who is sending/receiving ? 

The protocol was broken way long ago. It is radio, so with the right 
equipment you can tune in and capture the bits. And then read it. IIRC, 
there is some encryption for the radio part, but telcos "forgot" about 
it and left the demo mode on. Or used the demo key, they didn't create 
their own key. Then, IIRC, the rest of the path is not encrypted. In 
theory, only telco staff could read it.

Aside from that, others can subvert the system and send you an SMS 
claiming it is from your bank, and no way to know.

RCS is better. I'm not saying perfect, I haven't that kind of knowledge, 
I just say better.

<https://www.google.com/search?client=firefox-b-e&q=is+RCs+encrypted%3F>

About 436,000 results (0.33 seconds)
RCS is the modern industry standard for dynamic and secure messaging. 
And now, all of your RCS conversations in Messages by Google are 
end-to-end encrypted, including group chats, which keeps them private 
between you and the people you're messaging.Aug 8, 2023

Your RCS conversations are now fully end-to-end encrypted
Google Support
https://support.google.com › messages › thread › your-rc...
<https://support.google.com/messages/thread/229405182/your-rcs-conversations-are-now-fully-end-to-end-encrypted?hl=en>


> With other 
> services, who can see who is sending/receiving ?  Some may (rightly or 
> wrongly), trust the Telco, but may not trust that messaging services 
> operator (e.g. some won't touch whatsapp with a barge pole).

If I had industrial secrets at the job, I would not wasap about the job 
things :-D

Not because the Chinese would see it, but because the USAians would see 
it :-p


But for the common Joe Public, it doesn't matter.


-- 
Cheers,
        Carlos E.R.

Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

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

csiph-web