Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #109478
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: RCS chats |
| Date | 2023-11-02 18:56 +0100 |
| Message-ID | <kqi65sFdm1dU9@mid.individual.net> (permalink) |
| References | (5 earlier) <MPG.3fabaa943b8a760b99020c@news.individual.net> <uht4p2$1hppg$1@dont-email.me> <uhu3c4.17v8.1@ID-201911.user.individual.net> <kqfpacF2eb8U2@mid.individual.net> <ui0bu0.604.1@ID-201911.user.individual.net> |
On 2023-11-02 14:32, Frank Slootweg wrote:
> Arno Welzel <usenet@arnowelzel.de> wrote:
>> Frank Slootweg, 2023-11-01 17:54:
>>
>>> Dave Royal <dave@dave123royal.com> wrote:
>> [...]>> There is also the reasonable goal of replacing the ancient SMS
>> facility
>>>> with a more capable and reliable IP-based one.
>>>
>>> Exactly! With all its limitations, RCS provides some additional
>>> functionality compared to the ancient SMS/MMS system, while maintaining
>>> compatibility with it. That's all. Nothing to get worked up about.
>>
>> Is RCS really compatible in the way, the SMS can use the same protocol?
>> Or is it just the messaging apps which support both SMS as well as RCS?
>
> If a messaging app supports RCS, it will use RCS if the other side
> also supports RCS. If not, it will fallback to SMS/MMS (and can/will
> give a warning before doing so).
>
>> Having a universal standard for end-to-end-encrypted messaging which is
>> not controlled by a single company and which defines a minimum set of
>> features like groups or sending text with formatting and attachments
>> like images, audio and video, would be much more useful.
>
> Yes, that would be nice, but is outside the scope of this thread and
> neither SMS/MMS nor RCS have end-to-end-encryption.
RCS has end to end encryption.
<https://support.google.com/messages/thread/229405182/your-rcs-conversations-are-now-fully-end-to-end-encrypted?hl=en>
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
--
Cheers,
Carlos E.R.
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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