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?
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.