Path: ...!3.eu.feeder.erje.net!feeder.erje.net!news.szaf.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Andy Burns Newsgroups: comp.mobile.android Subject: Re: More about RCS. Date: Wed, 8 Jan 2025 15:40:25 +0000 Lines: 21 Message-ID: References: <2mkn4lxahs.ln2@Telcontar.valinor> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: individual.net lflIsfRcequMQ04vLfuKXgFTMUhlzblgX5NhY5w/hgI1zFqJ6K Cancel-Lock: sha1:H6VrvHe1sMfy6IH15ELbvDkdQZ0= sha256:fHGQX9oHAf0FxGoxGLaxDBeK4m0ptKvXLLL6i2zf0N0= User-Agent: Mozilla Thunderbird Content-Language: en-GB In-Reply-To: Bytes: 1664 Carlos E.R. wrote: > Joe Beanfish wrote: >>> Arno Welzel wrote: >> >>> Jörg Lorenz wrote: >>> >>>> 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. A couple of years ago my mobile provider ran their own RCS server, since then, they've (presumably like most others) migrated to using the Jibe/Google servers.