Are you talking about the “xn—“ domain name? Because FYI that’s just a punycode domain. It’s pretty commonly used for non-ascii domains. en.wikipedia.org/wiki/Punycode
The article itself is only available over Tor or I2P anyways though.
Comment on Proton’s Lumo AI chatbot: not end-to-end encrypted, not open source
EncryptKeeper@lemmy.world 11 hours agoNo chance anyone’s clicking on that link
Are you talking about the “xn—“ domain name? Because FYI that’s just a punycode domain. It’s pretty commonly used for non-ascii domains. en.wikipedia.org/wiki/Punycode
The article itself is only available over Tor or I2P anyways though.
Yes lol.
You still think it’s sketchy?
I’ve explained that it’s perfectly normal, that it’s just someone who wants to use Unicode in their domain name (in this case because they probably speak a non-ascii based language), and most good web clients should be showing that link as the Unicode characters. Firefox for example shows that as the proper Unicode directly.
It literally is just a way for non-english speakers to have a domain name in their native language.
People are usually aware enough to know that seeing Unicode characters in a URL looks wrong even if they don’t know why. Pair that with Punycode’s reputation for being abused by malicious actors and some clients not even showing the Unicode, and you have a link few are going to want to click on.
nymnympseudonym@lemmy.world 8 hours ago
How about this one
discuss.privacyguides.net/t/…/24456
EncryptKeeper@lemmy.world 8 hours ago
Better URL, sensationalist post that doesn’t mean a whole lot