News for hackers. Stuff that matters.
Re:Google Is Battling a Russian Spammer Over the Use of the ... by NamTaf on Wednesday February 01, 2017 @09:00AM (#13540723)
That doesn't really help, though, because now you ask eg: a Cyrillic speaker to use Latin characters in place of their own characters that are different but simply look the same. That's like us expecting Germans to use B instead of ß (I know it's not a close example, but it's the first that came to mind for me) even though ß translates to a 'ss' sound, which is nothing like a B sound. so 'heißt' goes from 'heisst' to 'heibt'.

Enforcing all of one subset makes more sense to me, though even that's not foolproof because the above example uses both B and ß in the same language. But at least it'll reduce the attack surface, I guess.

Re:Google Is Battling a Russian Spammer Over the Use of the ... by SeanLuke on Wednesday February 01, 2017 @09:34AM (#13540971)
I don't see what the problem is. For example, you could do this: create a string->"final string" hash function, where heißt and heibt both hash to the same final string (let's say it's HEIBT). You're only allowed to register final strings. If I create a company called heißt.com, then going to heibt.com (or HeIbT.com, hêìbŤ.com, or whatever) will also go to that same domain. A company can use heißt.com if it likes, or hêìbŤ.com, or whatever it prefers. But a spammer can't create a lookalike string. Why wouldn't this work?
Re:Google Is Battling a Russian Spammer Over the Use of the ... by 3pt14159 on Wednesday February 01, 2017 @10:28AM (#13541401)
It would work, and it is exactly what I recommended. He just didn't understand what I was asking for.
Re:Google Is Battling a Russian Spammer Over the Use of the ... by toufka on Wednesday February 01, 2017 @10:49AM (#13541587)
So like a lexical DNS service for figuring out DNS names.

A Domain Name Name Service - DNNS!