| Deutsch English Français Italiano |
|
<gp1kokxobv.ln2@Telcontar.valinor> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!news.mixmin.net!news.swapon.de!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 is preparing to replace RCS with MLS Date: Sat, 10 Aug 2024 14:07:44 +0200 Lines: 39 Message-ID: <gp1kokxobv.ln2@Telcontar.valinor> References: <leto4eFasrbU6@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> <v81p3k$mhc$1@nnrp.usenet.blueworldhosting.com> <lgk8tbF63ivU3@mid.individual.net> <v83gr9$2g47$1@nnrp.usenet.blueworldhosting.com> <lhf688F92a1U1@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net iJ6CLYizCEmUvbNASypt8wRuRqruxwZSJBCIULiU3lr/Z4212Y X-Orig-Path: Telcontar.valinor!not-for-mail Cancel-Lock: sha1:VhkR5DLGEcLxmpZmaUHMCy/hUWA= sha256:PxnE55kDz+zENUWlzqnjqkAA/3nt8cPK2Rwh/4o5j9E= User-Agent: Mozilla Thunderbird Content-Language: es-ES, en-CA In-Reply-To: <lhf688F92a1U1@mid.individual.net> Bytes: 3278 On 2024-08-06 19:53, Arno Welzel wrote: > Andrew, 2024-07-27 21:12: > > [...] >> Let's just leave it at that, as people can disagree on philosophy as long >> as they don't disagree on the facts. >> >> For every thousand times you unlock your phone, I unlock mine once. > > Which is no problem for me at all. Unlocking take way less than a second > for me. It's more or less not much more hassle than just picking up the > phone and turning it on. In fact the display already turns on as soon as > I pick it up so the remaining action to unlock it is really quick. > >> I consider my method efficient and your method inefficient. > > I consider your method as not relevant for most people. Most people use > their phones to store private data on them. And this data needs to be > protected. And people do not only acces their data once or twice a day. Store or access. Like accessing a banking app. Like making fast payments. It is a thing millions of people do pretty often. > > I use my phone also for my professional job which means I some days I it > *many* times and *alway* I *must* access protected data. Decrypting a > encrypted container only once a day and then leaving it vulnerable for > the whole day would not be an option. > >> As long as we agree on the facts, that's all that matters. > > Yes, I agree that your method is easier for you. But this does not mean > anything. > -- Cheers, Carlos.