Path: ...!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: Andrew <andrew@spam.net>
Newsgroups: comp.mobile.android
Subject: Re: Google is preparing to replace RCS with MLS
Date: Sat, 27 Jul 2024 03:21:24 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <v81p3k$mhc$1@nnrp.usenet.blueworldhosting.com>
References: <leto4eFasrbU6@mid.individual.net> <lf06e6Fr6k6U2@mid.individual.net> <lf0rt7Fmm0pU8@mid.individual.net> <v6fhmo$2t3q$1@nnrp.usenet.blueworldhosting.com> <lf1u3tF4e6pU1@mid.individual.net> <v6hg7d$26q0$1@nnrp.usenet.blueworldhosting.com> <lf2vdvF9ct8U1@mid.individual.net> <v6hint$2u54$1@nnrp.usenet.blueworldhosting.com> <ado7mkxb4o.ln2@Telcontar.valinor> <v6s8ak$1v1p$1@nnrp.usenet.blueworldhosting.com> <lfi1tuFi7p8U1@mid.individual.net> <v736m6$2a82$1@nnrp.usenet.blueworldhosting.com> <lg20eeFkfqU1@mid.individual.net> <v7goff$163n$1@nnrp.usenet.blueworldhosting.com> <lg4b64FbavdU3@mid.individual.net> <v7j3kt$1t9s$1@nnrp.usenet.blueworldhosting.com> <lg95eqF3eteU1@mid.individual.net> <v7op3l$c3q$1@nnrp.usenet.blueworldhosting.com> <lghtbaFpls7U2@mid.individual.net> <v80fn2$2nqsm$3@dont-email.me> <lgi05rFpls7U6@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 27 Jul 2024 03:21:24 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="23084"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: NewsTap/5.5 (iPad)
Cancel-Lock: sha1:1C8ShneNgc6OGgt/g72R3DNJI0k= sha256:/d6EAPOexL0wrON6ImorffVLAiLuIiBSLjJ5ZvsPZRY=
	sha1:rRREKwqOyOXJi7VXBfG6t0XZoeE= sha256:oMMIdxHKKqLiyoPCYcoZUsbOKUCTKGH8IrAiZAenzbg=
X-Face: VQ}*Ueh[4uTOa]Md([|$jb%rw~ksq}bzqA;z-.*8JM`4+zL[`N\ORHCI80}]}$]$e5]/i#v  qdYsE`yh@ZL3L{H:So{yN)b=AZJtpaP98ch_4W}
Bytes: 3341
Lines: 33

Arno Welzel wrote on Fri, 26 Jul 2024 18:11:41 +0200 :

> Yes - and especially when considering that an encrypted container also
> requires some kind of password or key to be useful. If the encryption
> would happen automatically without and interaction, the data would be
> completely unprotected if some other person gets access to the phone.

You don't get it, and that's OK because efficiency isn't your thing.

HINT: How many times do you unlock your phone just to use it, versus how
many times you unlock your encrypted containers?

Think about that.

It's a hundred to one. Maybe five hundred to a thousand to one.

The fact efficiency isn't in your thought process is why you think
unlocking your phone a thousand times a day is something you enjoy.

Me?

I unlock when I need to unlock. Which is once a week, if that.

If you don't understand the concept by now, you never will.
So we may as well give up.

You'll never convince me that unlocking a phone a thousand times is more
efficient than unlocking it once - when you need your data unlocked.

And I'm never going to convince you that NOT unlocking your phone a
thousand times is more efficient than unlocking it once - when you need to.

If you don't get it by now, you never will. And that's OK.
Some people enjoy being inefficient. It makes them feel better.