Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #109304 > unrolled thread
| Started by | Stan Brown <the_stan_brown@fastmail.fm> |
|---|---|
| First post | 2023-10-28 11:10 -0700 |
| Last post | 2023-11-01 09:54 +0100 |
| Articles | 20 on this page of 95 — 11 participants |
Back to article view | Back to comp.mobile.android
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 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
| From | Stan Brown <the_stan_brown@fastmail.fm> |
|---|---|
| Date | 2023-10-31 12:12 -0700 |
| Message-ID | <MPG.3faaf182bf77432c99020a@news.individual.net> |
| In reply to | #109393 |
On Mon, 30 Oct 2023 16:49:33 -0400, Wally J wrote: > Stan Brown <the_stan_brown@fastmail.fm> wrote > > > Thanks to all who responded. It sounds like RCS Chats has advantages > > for some people, but those don't apply to how I use messaging. I'm in > > the US and only message people in the US, and both data and messaging > > are free and unlimited with my plan. > > Hi Stan, > > This is an FYI to let you know of another possible similar solution... > <https://home.pulsesms.app/overview/> > Thank you for the information. But since nobody has mentioned any feature of RCS Chats that I would actually use, I don't think I need to try out alternative ways of getting similar functionality. :-) -- Stan Brown, Tehachapi, California, USA https://BrownMath.com/ Shikata ga nai...
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-10-31 21:44 +0100 |
| Message-ID | <kqd79vFc40dU1@mid.individual.net> |
| In reply to | #109410 |
On 2023-10-31 20:12, Stan Brown wrote:
> On Mon, 30 Oct 2023 16:49:33 -0400, Wally J wrote:
>> Stan Brown <the_stan_brown@fastmail.fm> wrote
>>
>>> Thanks to all who responded. It sounds like RCS Chats has advantages
>>> for some people, but those don't apply to how I use messaging. I'm in
>>> the US and only message people in the US, and both data and messaging
>>> are free and unlimited with my plan.
>>
>> Hi Stan,
>>
>> This is an FYI to let you know of another possible similar solution...
>> <https://home.pulsesms.app/overview/>
>>
>
> Thank you for the information. But since nobody has mentioned any
> feature of RCS Chats that I would actually use, I don't think I need
> to try out alternative ways of getting similar functionality. :-)
I understand that new Android phones ship with RCS activated by default.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Stan Brown <the_stan_brown@fastmail.fm> |
|---|---|
| Date | 2023-11-01 01:22 -0700 |
| Message-ID | <MPG.3fabaa943b8a760b99020c@news.individual.net> |
| In reply to | #109412 |
On Tue, 31 Oct 2023 21:44:47 +0100, Carlos E. R. wrote: > > On 2023-10-31 20:12, Stan Brown wrote: > > On Mon, 30 Oct 2023 16:49:33 -0400, Wally J wrote: > >> Stan Brown <the_stan_brown@fastmail.fm> wrote > >> > >>> Thanks to all who responded. It sounds like RCS Chats has advantages > >>> for some people, but those don't apply to how I use messaging. I'm in > >>> the US and only message people in the US, and both data and messaging > >>> are free and unlimited with my plan. > >> > >> Hi Stan, > >> > >> This is an FYI to let you know of another possible similar solution... > >> <https://home.pulsesms.app/overview/> > >> > > > > Thank you for the information. But since nobody has mentioned any > > feature of RCS Chats that I would actually use, I don't think I need > > to try out alternative ways of getting similar functionality. :-) > > I understand that new Android phones ship with RCS activated by default. Not just new phones. After I dismissed Google's nag to enable RCS chats, I got a notification that RCS Chats enabled is now the default. Fortunately the notification linked to the appropriate setting, so I was able to turn it off. Out of curiosity, does anyone know why Google is being so aggressive about promoting RCS Chats? How will they make money off of it? -- Stan Brown, Tehachapi, California, USA https://BrownMath.com/ Shikata ga nai...
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-01 08:42 +0000 |
| Message-ID | <kqehb6Foa06U1@mid.individual.net> |
| In reply to | #109422 |
Stan Brown wrote: > does anyone know why Google is being so aggressive about promoting > RCS Chats? They acquired Jibe Mobile for their RCS platform, presumably so that Android has an equivalent to Apple's iMessage. Everyone seems to fawn over iMessage but be critical of RCS ... > How will they make money off of it? Maybe they don't see it as a specific service to make money from, but just one part of the overall android phones offer?
[toc] | [prev] | [next] | [standalone]
| From | Jörg Lorenz <hugybear@gmx.net> |
|---|---|
| Date | 2023-11-01 10:01 +0100 |
| Message-ID | <uht456$v9f2$3@solani.org> |
| In reply to | #109425 |
Am 01.11.23 um 09:42 schrieb Andy Burns: > Stan Brown wrote: > >> does anyone know why Google is being so aggressive about promoting >> RCS Chats? > > They acquired Jibe Mobile for their RCS platform, presumably so that > Android has an equivalent to Apple's iMessage. > > Everyone seems to fawn over iMessage but be critical of RCS ... Reasons being quit simple: RCS is a privacy nightmare compared to the end-to-end encryption of iMessage and it is lacking a couple of functionalities iMessage has for years. -- Alea icacta est
[toc] | [prev] | [next] | [standalone]
| From | Jörg Lorenz <hugybear@gmx.net> |
|---|---|
| Date | 2023-11-01 09:58 +0100 |
| Message-ID | <uht40c$v9f1$3@solani.org> |
| In reply to | #109422 |
Am 01.11.23 um 09:22 schrieb Stan Brown: > Out of curiosity, does anyone know why Google is being > so aggressive about promoting RCS Chats? How will they > make money off of it? Google is frustrated because they never got a foothold in the messenger/social media market the fastest growing market. Every attempt failed. And the worst is that Apple has iMessage which is the Gold Standard and Android users have to use third party apps like Whats App, Signal, Telegram or Threema. Google is missing a lot of money. -- Alea icacta est
[toc] | [prev] | [next] | [standalone]
| From | Dave Royal<dave@dave123royal.com> |
|---|---|
| Date | 2023-11-01 09:12 +0000 |
| Message-ID | <uht4p2$1hppg$1@dont-email.me> |
| In reply to | #109422 |
On 1 Nov 2023 01:22:18 -0700 Stan Brown wrote: >Out of curiosity, does anyone know why Google is being >so aggressive about promoting RCS Chats? How will they >make money off of it? The unavailability of iMessages on Android prevents iOS users switching to Android devices. Peer pressure among children makes Android phones less attractive - search for 'iphone blue bubbles' if you don't know about that. Google want to persuade, if posible, or force - using anti-monolopy legislation - Apple to allow iMessage to interwork with Android devices. They therefore need to establish a similar messaging facility among Android users so that Apple's refusal to cooperate is seen as anti-competitive. There is also the reasonable goal of replacing the ancient SMS facility with a more capable and reliable IP-based one. -- (Remove numerics from email address)
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2023-11-01 16:54 +0000 |
| Message-ID | <uhu3c4.17v8.1@ID-201911.user.individual.net> |
| In reply to | #109432 |
Dave Royal <dave@dave123royal.com> wrote: > On 1 Nov 2023 01:22:18 -0700 Stan Brown wrote: > > >Out of curiosity, does anyone know why Google is being > >so aggressive about promoting RCS Chats? How will they > >make money off of it? > > The unavailability of iMessages on Android prevents iOS users switching to > Android devices. Peer pressure among children makes Android phones less > attractive - search for 'iphone blue bubbles' if you don't know about > that. > > Google want to persuade, if posible, or force - using anti-monolopy > legislation - Apple to allow iMessage to interwork with Android devices. > They therefore need to establish a similar messaging facility among > Android users so that Apple's refusal to cooperate is seen as > anti-competitive. In the EU, such legislation is already in the making. Not only for Apple (iMessage), but also for WhatsApp and other commercial IM platforms, i.e. also for Google. > 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.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-01 19:11 +0100 |
| Message-ID | <kqfiluFu39U2@mid.individual.net> |
| In reply to | #109438 |
On 2023-11-01 17:54, Frank Slootweg wrote:
> Dave Royal <dave@dave123royal.com> wrote:
>> On 1 Nov 2023 01:22:18 -0700 Stan Brown wrote:
>>
>>> Out of curiosity, does anyone know why Google is being
>>> so aggressive about promoting RCS Chats? How will they
>>> make money off of it?
>>
>> The unavailability of iMessages on Android prevents iOS users switching to
>> Android devices. Peer pressure among children makes Android phones less
>> attractive - search for 'iphone blue bubbles' if you don't know about
>> that.
>>
>> Google want to persuade, if posible, or force - using anti-monolopy
>> legislation - Apple to allow iMessage to interwork with Android devices.
>> They therefore need to establish a similar messaging facility among
>> Android users so that Apple's refusal to cooperate is seen as
>> anti-competitive.
>
> In the EU, such legislation is already in the making. Not only for
> Apple (iMessage), but also for WhatsApp and other commercial IM
> platforms, i.e. also for Google.
>
Interesting.
>> 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.
Yes, that's the whole point.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2023-11-01 21:04 +0100 |
| Message-ID | <kqfpacF2eb8U2@mid.individual.net> |
| In reply to | #109438 |
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? 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. XMPP with OMEMO is an open standard and does not rely on the infrastructure of one single provider. But unfortunately there no mandatory set of XMPP extension protocols (XEP) which clients must implement - so you never now, which of the extended features of your client will be supported by others. Also XMPP requires a user account (JID) and you can not just use your phone number to set it up. Some see this as a privacy measure, but this also keeps many people from using it, as they already are used to much simpler setup like WhatsApp or Signal: just install it, confirm the account creation and you are ready to go. And even better: you will see all your contacts immediately and don't have to ask everybody about his or her JID before you can contact them. Therefore XMPP also sticks with a small group of ethusiasts who do not need more than more or less plain text messaging and it will never get as popular as WhatsApp, Signal etc.. -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-01 20:30 +0000 |
| Message-ID | <kqfqqvF2j43U1@mid.individual.net> |
| In reply to | #109445 |
Arno Welzel wrote: > 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? There's no compatibility as such, but RCS-capable messaging apps will send over RCS by preference, and fall back to SMS when recipients aren't reachable on RCS > 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. There's a recent standard for that <https://messaginglayersecurity.rocks> if it takes off, it could get imessage/telegram/signal/whatsapp speaking to each other > XMPP with OMEMO is an open standard and does not rely on the > infrastructure of one single provider. > > But unfortunately there no mandatory set of XMPP extension protocols > (XEP) which clients must implement - so you never now, which of the > extended features of your client will be supported by others. Google have killed several XMPP products, probably not keen to put a toe back in that water
[toc] | [prev] | [next] | [standalone]
| From | Dave Royal<dave@dave123royal.com> |
|---|---|
| Date | 2023-11-01 20:56 +0000 |
| Message-ID | <uhue1p$1pj4g$1@dont-email.me> |
| In reply to | #109445 |
On 1 Nov 2023 21:04:29 +0100 Arno Welzel 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? > The protocols are not compatible. AIUI the Android messaging app will use RCS if it can, and fall back to SMS (while it exists) for plain text messages. Much like iMessage. I don't see any disadvantage in anyone (who usually has mobile data) enabling it unless they have a particular reason to use SMS. >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. > >XMPP with OMEMO is an open standard and does not rely on the >infrastructure of one single provider. > >But unfortunately there no mandatory set of XMPP extension protocols >(XEP) which clients must implement - so you never now, which of the >extended features of your client will be supported by others. > >Also XMPP requires a user account (JID) and you can not just use your >phone number to set it up. Some see this as a privacy measure, but this >also keeps many people from using it, as they already are used to much >simpler setup like WhatsApp or Signal: just install it, confirm the >account creation and you are ready to go. And even better: you will see >all your contacts immediately and don't have to ask everybody about his >or her JID before you can contact them. > >Therefore XMPP also sticks with a small group of ethusiasts who do not >need more than more or less plain text messaging and it will never get >as popular as WhatsApp, Signal etc.. > Yes, XMPP and its later extensions could have developed into a messaging standard. But neither Apple nor Google were or are interested in cross-platform standards - unless perhaps it's their own. Google's current enthusiam for RCS isn't for the benefit of mankind. In fact Google sabotaged XMPP by adopting the Jabber IM protocol in Google Chat as a way of gaining users, and then dropping it https://talk.maemo.org/showthread.php?t=90116 Much as they did with Google Reader and RSS. XMPP was built into the Sailfish mobile OS which I used until a couple of years ago. I have an account, er, somewhere. -- (Remove numerics from email address)
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-01 23:09 +0100 |
| Message-ID | <kqg0k2Fu39U4@mid.individual.net> |
| In reply to | #109449 |
On 2023-11-01 21:56, Dave Royal wrote:
> On 1 Nov 2023 21:04:29 +0100 Arno Welzel 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?
>>
> The protocols are not compatible. AIUI the Android messaging app will use
> RCS if it can, and fall back to SMS (while it exists) for plain text
> messages. Much like iMessage. I don't see any disadvantage in anyone (who
> usually has mobile data) enabling it unless they have a particular reason
> to use SMS.
AFAIK, all apps doing RCS fall back to SMS transparently when RCS is not
available. There must be some design for this in the RCS protocol.
>
>> 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.
Well, AFAIK SMS has no encryption at all. It is a design from the 90's.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2023-11-02 17:30 +0100 |
| Message-ID | <kqi14cFjga2U2@mid.individual.net> |
| In reply to | #109451 |
Carlos E. R., 2023-11-01 23:09: > On 2023-11-01 21:56, Dave Royal wrote: [...] >> The protocols are not compatible. AIUI the Android messaging app will use >> RCS if it can, and fall back to SMS (while it exists) for plain text >> messages. Much like iMessage. I don't see any disadvantage in anyone (who >> usually has mobile data) enabling it unless they have a particular reason >> to use SMS. > > AFAIK, all apps doing RCS fall back to SMS transparently when RCS is not > available. There must be some design for this in the RCS protocol. Well - if a client does not have RCS it may just not be reachable this way. At least a RCS server needs to confirm it a message can be delivered or not. And if the server denies the delivery, because there is no RCS client for the given target number available, then the sender knows, that he has to use SMS. >>> 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. > > Well, AFAIK SMS has no encryption at all. It is a design from the 90's. Exactly. Therefore we should implement this in a current standard. But of course governments don't want an offical standard where they can not read the messages of the users if they want to - either to "protect the children" or to "watch criminals". -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-02 18:53 +0100 |
| Message-ID | <kqi61aFdm1dU8@mid.individual.net> |
| In reply to | #109471 |
On 2023-11-02 17:30, Arno Welzel wrote:
> Carlos E. R., 2023-11-01 23:09:
>
>> On 2023-11-01 21:56, Dave Royal wrote:
> [...]
>>> The protocols are not compatible. AIUI the Android messaging app will use
>>> RCS if it can, and fall back to SMS (while it exists) for plain text
>>> messages. Much like iMessage. I don't see any disadvantage in anyone (who
>>> usually has mobile data) enabling it unless they have a particular reason
>>> to use SMS.
>>
>> AFAIK, all apps doing RCS fall back to SMS transparently when RCS is not
>> available. There must be some design for this in the RCS protocol.
>
> Well - if a client does not have RCS it may just not be reachable this
> way. At least a RCS server needs to confirm it a message can be
> delivered or not. And if the server denies the delivery, because there
> is no RCS client for the given target number available, then the sender
> knows, that he has to use SMS.
Yes.
In fact, the tool tells before sending whether RCS is available.
>
>>>> 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.
>>
>> Well, AFAIK SMS has no encryption at all. It is a design from the 90's.
>
> Exactly. Therefore we should implement this in a current standard. But
> of course governments don't want an offical standard where they can not
> read the messages of the users if they want to - either to "protect the
> children" or to "watch criminals".
And that standard is RCS :-D
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2023-11-03 19:24 +0100 |
| Message-ID | <kqks62F6hhkU4@mid.individual.net> |
| In reply to | #109477 |
Carlos E. R., 2023-11-02 18:53: > On 2023-11-02 17:30, Arno Welzel wrote: [...] >> Exactly. Therefore we should implement this in a current standard. But >> of course governments don't want an offical standard where they can not >> read the messages of the users if they want to - either to "protect the >> children" or to "watch criminals". > > And that standard is RCS :-D Is the encryption really end-to-end without any way to intercept by any government officials? -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2023-11-03 18:54 +0000 |
| Message-ID | <kqktv8F6jc8U2@mid.individual.net> |
| In reply to | #109521 |
Arno Welzel wrote: > Is the encryption really end-to-end without any way to intercept by any > government officials? In order to answer that, first provide a list of the types of encryption your government can crack ...
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2023-11-03 22:59 +0100 |
| Message-ID | <kql8p6F8kn7U1@mid.individual.net> |
| In reply to | #109526 |
Andy Burns, 2023-11-03 19:54: > Arno Welzel wrote: > >> Is the encryption really end-to-end without any way to intercept by any >> government officials? > > In order to answer that, first provide a list of the types of encryption > your government can crack ... This is not needed if there is an interface to intercept on the devices or a second key which allows to decrypt the traffic. -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2023-11-03 23:01 +0100 |
| Message-ID | <kql8ugF7jo1U2@mid.individual.net> |
| In reply to | #109521 |
On 2023-11-03 19:24, Arno Welzel wrote:
> Carlos E. R., 2023-11-02 18:53:
>
>> On 2023-11-02 17:30, Arno Welzel wrote:
> [...]
>>> Exactly. Therefore we should implement this in a current standard. But
>>> of course governments don't want an offical standard where they can not
>>> read the messages of the users if they want to - either to "protect the
>>> children" or to "watch criminals".
>>
>> And that standard is RCS :-D
>
> Is the encryption really end-to-end without any way to intercept by any
> government officials?
Is there any messaging _service_ that can not be intercepted by governments?
Possibly PGP email.
--
Cheers,
Carlos E.R.
[toc] | [prev] | [next] | [standalone]
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Date | 2023-11-05 19:21 +0100 |
| Message-ID | <kqq4p4F87crU3@mid.individual.net> |
| In reply to | #109531 |
Carlos E. R., 2023-11-03 23:01: > On 2023-11-03 19:24, Arno Welzel wrote: >> Carlos E. R., 2023-11-02 18:53: >> >>> On 2023-11-02 17:30, Arno Welzel wrote: >> [...] >>>> Exactly. Therefore we should implement this in a current standard. But >>>> of course governments don't want an offical standard where they can not >>>> read the messages of the users if they want to - either to "protect the >>>> children" or to "watch criminals". >>> >>> And that standard is RCS :-D >> >> Is the encryption really end-to-end without any way to intercept by any >> government officials? > > > Is there any messaging _service_ that can not be intercepted by governments? Signal, Threema -- Arno Welzel https://arnowelzel.de
[toc] | [prev] | [next] | [standalone]
Page 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
Back to top | Article view | comp.mobile.android
csiph-web