Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #123078
| Path | csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail |
|---|---|
| From | "Carlos E. R." <robin_listas@es.invalid> |
| Newsgroups | comp.mobile.android |
| Subject | Re: Google improves Google Messages |
| Date | Fri, 8 Dec 2023 19:16:34 +0100 |
| Lines | 80 |
| Message-ID | <kth4s2FjcbcU2@mid.individual.net> (permalink) |
| References | <kt4fkaFmoueU1@mid.individual.net> <uklev4$3iibb$1@dont-email.me> <kt7761FgisjU2@mid.individual.net> <ukme59$159rp$1@paganini.bofh.team> <kt8sh6Ftug5U4@mid.individual.net> <ukq9b3.jd4.1@ID-201911.user.individual.net> <ktc5j9F4np7U4@mid.individual.net> <ukt4ac.mro.1@ID-201911.user.individual.net> <ktgie7FcvgcU1@mid.individual.net> <ukvbaf.8a4.1@ID-201911.user.individual.net> <ktgnqdFcvgfU2@mid.individual.net> <ukvhed.mr0.1@ID-201911.user.individual.net> <kth0qjFikeqU1@mid.individual.net> <ukvp5a.qvc.1@ID-201911.user.individual.net> |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=UTF-8; format=flowed |
| Content-Transfer-Encoding | 7bit |
| X-Trace | individual.net BpVizZMXOMI0bOn4WOJBkwgklDAduJchNdtm4P0GlsH9VqJ2C2 |
| Cancel-Lock | sha1:qU5r+JmrnoR3hFTpk9mLqWnfFKc= sha256:DpeyH1p6JOhEbgO6YHvcqu7kHgc7hW5leE/q3WMrflU= |
| User-Agent | Mozilla Thunderbird |
| Content-Language | en-CA, es-ANY |
| In-Reply-To | <ukvp5a.qvc.1@ID-201911.user.individual.net> |
| Xref | csiph.com comp.mobile.android:123078 |
Show key headers only | View raw
On 2023-12-08 19:01, Frank Slootweg wrote:
> Carlos E. R. <robin_listas@es.invalid> wrote:
>> On 2023-12-08 16:49, Frank Slootweg wrote:
>>> Carlos E. R. <robin_listas@es.invalid> wrote:
>>>> On 2023-12-08 15:04, Frank Slootweg wrote:
>>>>> Carlos E. R. <robin_listas@es.invalid> wrote:
>>>>>> On 2023-12-07 18:53, Frank Slootweg wrote:
...
>>>>> So I can not select RCS and have no idea if the recipient can handle
>>>>> RCS or not.
>>>>
>>>> Well, your phone is three years old, I think you said, and Samsung
>>>> switched to the google app 2 years ago.
>>>
>>> Phil said "a couple of years", not two, and without a reference, so
>>> for the time being we have to take his word for it, together with the
>>> vague period.
>>
>> A couple of years is two years :-)
>
> [...]
>
>> 2 Two partners in a romantic or sexual relationship.
>
> If that's not thread drift, I don't know *what* is! :-)
:-)
>
> [...]
>
>>> Anyway, as I said, my phone is fully updated with Samsung 'Software
>>> update's (now Android 13) and 'Google Play system update's, but the
>>> Messages app is *still* Samsung's not Google's. So there for no *forced*
>>> update/switch from Samsung Messages to Google Messages. AJL reported the
>>> same for his Samsung Galaxy S10+ phone.
>>
>> I never mentioned a forced update, not to a different app.
>>
>> I talked about google updating its own app, and having a default of
>> "enabled".
>
> No, of course you didn't a forced update, but not being forced, means
> the proliferation will be (more) limited.
Probably all new phones come with the Google Messages tool, including
big vendors like Samsung.
Google did not make RCS active by default, they waited, to see how
things went. Now they are pushing harder. So it will gain traction even
in the USA :-)
>>>>> So things are not as ideal as we would like. OTOH, a sender with RCS
>>>>> capability can always *try* if the recipient can handle RCS.
>>>>
>>>> The google messages tool tells instantly, before typing, if it is RCS.
>>>
>>> But what if the recipients phone is RCS-*capable*, but the recipient
>>> has not *enabled* RCS? Does the sender then get any kind of yes/no (RCS)
>>> indication, *before* sending the message,
>>
>> We get "SMS".
>
> It would be nice if the sender's app could/would determine that the
> recipients app is RCS-able but not RCS-enabled, but perhaps that's not
> tecnically possible or allowed.
There is no much point, except to nag the other party to activate RCS :-D
Maybe not even possible by the protocol used. It is an almost real time
query, I tested it.
--
Cheers,
Carlos E.R.
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Google improves Google Messages "Carlos E. R." <robin_listas@es.invalid> - 2023-12-08 14:01 +0100
Re: Google improves Google Messages Frank Slootweg <this@ddress.is.invalid> - 2023-12-08 14:04 +0000
Re: Google improves Google Messages "Carlos E. R." <robin_listas@es.invalid> - 2023-12-08 15:33 +0100
Re: Google improves Google Messages Frank Slootweg <this@ddress.is.invalid> - 2023-12-08 15:49 +0000
Re: Google improves Google Messages "Carlos E. R." <robin_listas@es.invalid> - 2023-12-08 18:07 +0100
Re: Google improves Google Messages AJL <noemail@none.com> - 2023-12-08 10:28 -0700
Re: Google improves Google Messages Frank Slootweg <this@ddress.is.invalid> - 2023-12-08 18:01 +0000
Re: Google improves Google Messages "Carlos E. R." <robin_listas@es.invalid> - 2023-12-08 19:16 +0100
Re: Google improves Google Messages Phil <philusenet1458@gmx.com> - 2023-12-09 13:58 +0000
Re: Google improves Google Messages "Carlos E. R." <robin_listas@es.invalid> - 2023-12-09 17:03 +0100
csiph-web