Path: ...!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 will no longer send SMSs with six digit codes for
 verification
Date: Wed, 5 Mar 2025 03:48:09 +0100
Lines: 57
Message-ID: <9kqk9lx6m3.ln2@Telcontar.valinor>
References: <803e9lxp44.ln2@Telcontar.valinor>
 <1begjrynfhjra$.dlg@v.nguard.lh> <k8cg9lx8uf.ln2@Telcontar.valinor>
 <1bfu5iribmwb4$.dlg@v.nguard.lh> <vq4hce.l64.1@ID-201911.user.individual.net>
 <vq6a3h$1p9sb$1@dont-email.me> <l8nlfkd5cizd.dlg@v.nguard.lh>
 <96uj9lxjvi.ln2@Telcontar.valinor> <17fmpgc4tfncj$.dlg@v.nguard.lh>
 <vq7rjj.47s.1@ID-201911.user.individual.net> <hncfhd611fab.dlg@v.nguard.lh>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: individual.net wZZb/vq0BpMCgGI6IpytggixvQAonwArLPMFM1k27W27Sd8snc
X-Orig-Path: Telcontar.valinor!not-for-mail
Cancel-Lock: sha1:vq+q2q495Q+tFxeIwhL0qbvx6LA= sha256:1/HeJiXgCX2le/DZ0AgLhsMiUrC4PXQ6ajzk4/+jNmU=
User-Agent: Mozilla Thunderbird
Content-Language: es-ES, en-CA
In-Reply-To: <hncfhd611fab.dlg@v.nguard.lh>
Bytes: 3709

On 2025-03-05 02:45, VanguardLH wrote:
> Frank Slootweg <this@ddress.is.invalid> wrote:
> 
>> VanguardLH <V@nguard.lh> wrote:
>> [...]
>>
>>> Not relevant to my statement of having to wait for SMS messages (text or
>>> QR image content) nor there is no guaranteed delivery of SMS messages.
>>>
>>> To where is the SMS message sent?  To the phone.  Okay, I'll see an SMS
>>> message with a QR image.  Then what?  Do SMS apps have embedded scanning
>>> of the content of SMS messages to then use an embedded QR decoder to
>>> show the text embedded in the image (which obviates the whole point of
>>> supposedly securing the text string in an image) that I then have to
>>> copy/paste into some web prompt?
>>
>>    AFAICT, "an SMS message with a QR image" is a figment of your
>> imagination!
>>
>>    I think such a thing is not mentioned anywhere and not even implied
>> anywhere.
> 
> The delivery mechanism is defined where?
> 
>>    The referenced articles mention that *use* of a code in an SMS message
>> will be replaced by *use* of a QR code, but that does not mean that the
>> QR code is *in* an SMS message. (I think that would be obvious, because
>> an SMS message is too small to hold a QR code, not to mention that it
>> can only hold character data, not binary data.)
> 
> I figured it could be MMS (Multimedia Messaging) instead of SMS (Short
> Message Service).  MMS can be used to send pictures.  I have automatic
> downloads of MMS disabled in my messaging apps.
> 
> However, upon some further reading, Google Prompts looks to use
> notifications instead of SMS/MMS messages.  Maybe.
> 
>>    So perhaps it's best to come up with an actual quote from the
>> referenced articles, which leads you to your assumption, instead of
>> going on and on about something which is very likely a straw man / red
>> herring.
> 
> That's the crux of the problem: there are no details on how QR images by
> whatever delivery mechanism are to get decoded into strings by the user
> to input into a waiting field.  All of us are just guessing for now what
> are the possibilities.

You are imagining it wrong. You try to login on your computer; the 
computer displays a picture, the phone takes a photo. There are no SMS 
involved, no conversions, no fields to complete. Just point and shoot, 
done. Instantly.

Same as currently done to login to wasap on the computer. The same 
system. Known and tested.

-- 
Cheers, Carlos.