Then add a "this domain may not be what it appears/may be trying to impersonate another domain" bubble just above/below it too.
-
-
-
Btw, firefox & chrome are dealing with the problem quite nicely imho. They don't allow mixing languages.
-
the problem being discussed in this thread is, it's possible to make lookalikes without mixing languages. see also https://www.xudongz.com/blog/2017/idn-phishing/ …
-
In fairness browsers do know your locale and language, and there is scope in the standard to indicate what languages you understand
-
Yes, Chrome used to refuse to display non-latin domains decoded unless I told it I understood relevant langs. Very annoying.
-
List of langs you accept is a huge fingerprint. And many ppl, myself included understand scripts/single words but not langs.
End of conversation
New conversation -
-
-
Unicode support in domains is a worthy goal, but don't say that solving confusable glyphs is "trivial", as if everyone's just dumb.
-
Sorry it's not quite 140 chars trivial. And it's not a matter of dumb but misplaced priorities.
End of conversation
New conversation -
-
-
In particular, I believe registrars already check for script transitions. But "еріс" does not contain one. It's all Cyrillic.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Vietnamese uses one script -- Latin -- but with a lot more glyphs, easily confusable with English glyphs.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You say it's "trivial" without having considered a lot of languages, then. Standard written Japanese uses multiple scripts.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.