@robinadams : OTOH, if you click on a search result, Google could also send your browser to a runtime generated webpage, like Google Transate does.

For example, if I enter (I've replaced // by Unicode ⧸⧸ to prevent Mastodon from shortening the URLs and hiding "https://"):

🔗 https:⧸⧸www.security.nl/posting/929685/FCC+verbiedt+verkoop+van+nieuwe+routers+van+buitenlandse+fabrikanten+in+VS

into

🔗 https:⧸⧸translate.google.com/?sl=nl&tl=en&op=websites

the eventual URL turns into:

🔗 https:⧸⧸www-security-nl.translate.goog/posting/929685/FCC+verbiedt+verkoop+van+nieuwe+routers+van+buitenlandse+fabrikanten+in+VS?_x_tr_sl=en&_x_tr_tl=nl&_x_tr_hl=en&_x_tr_pto=wapp

In case of AI manipulation, such a link could read, for example,

🔗 https:⧸⧸www-security-nl.ai.goog/posting/929685/FCC+verbiedt+verkoop+van+nieuwe+routers+van+buitenlandse+fabrikanten+in+VS

Nomalizing this will result in even more people to fall for #phishing (replacing dots by dashes). The only thing reasonably trustworthy, the domain name of a website, becomes even more messy.

Apart from the fact that Google may charge websites for this "service" and/or insert their own ads.

@petealexharris @grammasaurus @SteveRudolfi

#DVsucks #GoogleIsEvil #LetsEncryptIsEvil #TLSisBroken #httpsIsBroken #E2EE #E2EEisBroken #DomainNamesSuck