[technology taskforce] [At-Large] Ars Technica : Google is messing with the address bar again—new experiment hides URL path

[Alan Greenberg]

This may require more thought, but at first 
glance, I am not sure I agree with you Maureen.

One of the things about phishing URLs is that 
they often contain parts of the faked URL 
embedded in the fully qualified address - either 
as higher than the 2nd level domaon name, or in 
the page identifier. So to the unskilled eye, it 
"looks" like it is going to a safe place. But the 
core site it is going to is not at all related to 
the place the user may think it is going to. By 
showing only the base URL, that may be avoided.

So blah.scammer.com/BankofAmerica.com would only show the scamming URL.

I am curious as to how bankofamerica.com.blah.scammer.com would be displayed.

Alan

At 2020-06-16 12:15 PM, Maureen Hilyard wrote:
>James
>One of the things that we are trying to engender 
>among our end-users in our capacity-building 
>activities is to raise their awareness of where 
>they are getting information from and where they 
>are landing when they want information. And 
>checking before they click is an important rule. 
>Just being given a short URL is defeating the 
>whole point of our trying to encourage 
>responsible user practice and behaviour. More of 
>an issue for newer less experienced users in developing countries.
>
>Maureen
>
>On Tue, Jun 16, 2020 at 6:03 AM James Gannon 
><<mailto:james at cyberinvasion.net>james at cyberinvasion.net> wrote:
>I haven’t actually chatted with the chrome dev 
>team about this before, their goal is actually 
>to increase user experience, quantitative user 
>data shows most people have no idea what a URL 
>is anymore beyond potentially I go to 
><http://x.com>x.com, beyond the tld many users 
>have little to no idea of the functionality of “the rest”
>
>Sent from my iPhone
>
>>On 16 Jun 2020, at 07:47, Holly Raiche 
>><<mailto:h.raiche at internode.on.net>h.raiche at internode.on.net> wrote:
>>
>> If we are supposed to be looking after end 
>>users, why aren’t we outraged that we can’t 
>>see the full URL - particularly since Google is 
>>most likely trying to   hide how pervasive it is in everyone’s lives
>>
>>Holly
>>
>>>On Jun 16, 2020, at 2:48 PM, Jonathan Zuck 
>>><<mailto:JZuck at innovatorsnetwork.org>JZuck at innovatorsnetwork.org> wrote:
>>>
>>>Another nail...
>>>
>>>Jonathan Zuck
>>>Executive Director
>>>Innovators Network Foundation
>>><http://www.innovatorsnetwork.org/>www.InnovatorsNetwork.org
>>>
>>>
>>>----------
>>>From: At-Large 
>>><<mailto:at-large-bounces at atlarge-lists.icann.org>at-large-bounces at atlarge-lists.icann.org> 
>>>on behalf of Dev Anand Teelucksingh <<mailto:devtee at gmail.com>devtee at gmail.com>
>>>Sent: Monday, June 15, 2020 6:48:06 PM
>>>To: Technology Taskforce WG 
>>><<mailto:ttf at atlarge-lists.icann.org>ttf at atlarge-lists.icann.org>; 
>>>At-Large Worldwide 
>>><<mailto:at-large at atlarge-lists.icann.org>at-large at atlarge-lists.icann.org>
>>>Subject: [At-Large] Ars Technica : Google is 
>>>messing with the address bar again—new experiment hides URL path
>>>
>>>"It looks like Google is trying to mess with 
>>>the URL bar again. As spotted by 
>>><https://www.androidpolice.com/2020/06/12/google-resumes-its-senseless-attack-on-the-url-bar-hides-full-addresses-on-chrome-canary/>Android 
>>>Police, new flags in the developer versions of 
>>>the popular browser now want to hide the URL 
>>>path. So for an article like this one, instead 
>>>of 
>>>"<https://arstechnica.com/gadgets/2020/06/google-is-messing-with-the-address-bar-again-new-experiment-hides-url-path/,>https://arstechnica.com/gadgets/2020/06/google-is-messing-with-the-address-bar-again-new-experiment-hides-url-path/," 
>>>the address bar would show "<http://arstechnica.com/>arstechnica.com."
>>>
>>>
>>>https://arstechnica.com/gadgets/2020/06/google-is-messing-with-the-address-bar-again-new-experiment-hides-url-path/
>>>
>>>
>>>_______________________________________________
>>>At-Large mailing list
>>><mailto:At-Large at atlarge-lists.icann.org>At-Large at atlarge-lists.icann.org
>>>https://atlarge-lists.icann.org/mailman/listinfo/at-large
>>>
>>>At-Large Official Site: <http://atlarge.icann.org>http://atlarge.icann.org
>>>_______________________________________________
>>>By submitting your personal data, you consent 
>>>to the processing of your personal data for 
>>>purposes of subscribing to this mailing list 
>>>accordance with the ICANN Privacy Policy 
>>>(<https://www.icann.org/privacy/policy>https://www.icann.org/privacy/policy) 
>>>and the website Terms of Service 
>>>(<https://www.icann.org/privacy/tos>https://www.icann.org/privacy/tos). 
>>>You can visit the Mailman link above to change 
>>>your membership status or configuration, 
>>>including unsubscribing, setting digest-style 
>>>delivery or disabling delivery altogether (e.g., for a vacation), and so on.
>>
>>_______________________________________________
>>ttf mailing list
>><mailto:ttf at atlarge-lists.icann.org>ttf at atlarge-lists.icann.org
>>https://mm.icann.org/mailman/listinfo/ttf
>>
>>_______________________________________________
>>By submitting your personal data, you consent 
>>to the processing of your personal data for 
>>purposes of subscribing to this mailing list 
>>accordance with the ICANN Privacy Policy 
>>(<https://www.icann.org/privacy/policy>https://www.icann.org/privacy/policy) 
>>and the website Terms of Service 
>>(<https://www.icann.org/privacy/tos>https://www.icann.org/privacy/tos). 
>>You can visit the Mailman link above to change 
>>your membership status or configuration, 
>>including unsubscribing, setting digest-style 
>>delivery or disabling delivery altogether (e.g., for a vacation), and so on.
>_______________________________________________
>At-Large mailing list
><mailto:At-Large at atlarge-lists.icann.org>At-Large at atlarge-lists.icann.org
>https://atlarge-lists.icann.org/mailman/listinfo/at-large
>
>At-Large Official Site: <http://atlarge.icann.org>http://atlarge.icann.org
>_______________________________________________
>By submitting your personal data, you consent to 
>the processing of your personal data for 
>purposes of subscribing to this mailing list 
>accordance with the ICANN Privacy Policy 
>(<https://www.icann.org/privacy/policy>https://www.icann.org/privacy/policy) 
>and the website Terms of Service 
>(<https://www.icann.org/privacy/tos>https://www.icann.org/privacy/tos). 
>You can visit the Mailman link above to change 
>your membership status or configuration, 
>including unsubscribing, setting digest-style 
>delivery or disabling delivery altogether (e.g., for a vacation), and so on.
>
>_______________________________________________
>At-Large mailing list
>At-Large at atlarge-lists.icann.org
>https://atlarge-lists.icann.org/mailman/listinfo/at-large
>
>At-Large Official Site: http://atlarge.icann.org
>_______________________________________________
>By submitting your personal data, you consent to 
>the processing of your personal data for 
>purposes of subscribing to this mailing list 
>accordance with the ICANN Privacy Policy 
>(https://www.icann.org/privacy/policy) and the 
>website Terms of Service 
>(https://www.icann.org/privacy/tos). You can 
>visit the Mailman link above to change your 
>membership status or configuration, including 
>unsubscribing, setting digest-style delivery or 
>disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/ttf/attachments/20200616/9cca3167/attachment-0001.html>