Path: ...!npeer.as286.net!npeer-ng0.as286.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Frank Slootweg Newsgroups: comp.mobile.android Subject: Re: More about RCS. Date: 5 Jan 2025 16:04:20 GMT Organization: NOYB Lines: 15 Message-ID: References: X-Trace: individual.net Z2NmXRoDN7H0xq3rlQPIbAYDIHSkKdntACuZhccVWF+fX1iOTw X-Orig-Path: not-for-mail Cancel-Lock: sha1:yNlr5Z/qAqJjIXgisi/KaGC0+9Y= sha256:D3FKAOUB46unOy4bjva9ahLcJYojeSXXak9V5qagxlw= User-Agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (CYGWIN_NT-10.0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2 Bytes: 1697 micky wrote: [...] > So it seems like the > snowplow guy does have RCS but I still have no blue circles so, it's > impossible for me to believe he didn't read my texts yet so that means > it just doesn't work perfectly . One should not be surprised, LOL . It *does* work 'perfectly', but it can't do the impossible. I.e. it can force the recipient to *really* read the text. And, as mentioned, the opposite, the recipient *can* read the text without you knowing it, either by reading it in the notification area or by turning off the read check mark facility. The only guarantee is the delivery check mark. If that is ticked, the message arrived at the destination, which is a device, not a person.