Sujet : Re: More about RCS.
De : joebeanfish (at) *nospam* nospam.duh (Joe Beanfish)
Groupes : comp.mobile.androidDate : 08. Jan 2025, 14:53:12
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vlm008$2po8r$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9
User-Agent : Pan/0.146 (Hic habitat felicitas; 8107378 git@gitlab.gnome.org:GNOME/pan.git)
On Wed, 08 Jan 2025 13:32:48 +0100, Carlos E.R. wrote:
On 2025-01-07 14:38, Joe Beanfish wrote:
On Sun, 05 Jan 2025 13:01:29 +0100, Arno Welzel wrote:
Jörg Lorenz, 2025-01-04 13:51:
>
On 04.01.25 13:03, Carlos E.R. wrote:
On 2025-01-04 08:52, Dave Royal wrote:
I don't
know - I don't use RCS.
>
Next time you replace your phone, RCS should be enabled by default :-)
>
Good to know that we should deactivate Google's wet dream immediately. ;-)
>
RCS is a standard protocol and not "Google's wet dream".
Whose servers do RCS messages pass thru?
It is quite difficult to know in each case, there is no trace
information as there is with email.
You can read here:
<https://en.wikipedia.org/wiki/Rich_Communication_Services>
Basically, it depends on whether your provider supports it directly, or
not. If not, then it is via Google servers. Look at the "Interconnection
and hubs" section in the above link.
There is also a large table of providers ("Commercial deployments").
Under Adoption it largely answers the question with
"In 2023, T-Mobile and AT&T agreed to use Google Jibe to implement RCS
services, and in 2024 Verizon agreed to use Google Jibe."
So, by and large, google servers.