35 ms·

Nonsense. For my purposes I don't need nonascii domains. Feel free to use unicorn characters in your address bar, but I'd much rather have it special cased in

Nonsense. For my purposes I don't need nonascii domains. Feel free to use unicorn characters in your address bar, but I'd much rather have it special cased in mine. My security shouldn't suffer just because it's such hard to solve it universally. We don't need a universal solution.

realityking 10y ago
America first! Or, in this case, English first! There's an argument to be made that we should not solve problems in a fashion that only benefits English (or English and other European languages). Generally when that happens the speakers of those languages - which are still the dominant group in internet standardization - loose all interest in fixing the problem for everyone else. The internet is on the way to becoming a truly global medium, if it isn't there already. We need to stop designing for English first.
- MosesKing 10y ago
  Fixing the problem is a matter of locale. Fixing it for me doesn't preclude non English speakers from having their own solution. How is that English first?
- Jare 10y ago
  We need to think things through and take security seriously, before we cause more serious problems. We have all seen semi-broken characters and weird symbols appearing in text (due to fonts, codepages, encodings, or plain bad handling of unicode strings) for decades now, and have mostly shrugged it off, accepting that maybe someone else is seeing more appropriate text thanks to that. But security is not the place for such cavalier attitudes. I'll gladly give up my Ñ's and É's and Ç's in domains and other global identification services, in exchange for knowing that It Will Just Work, always, everywhere, safely. And once the "very smart people that really figure things out" have a solution that works with more extensive cultural/linguistic features, by all means put it in place.

35 ms·

Nonsense. For my purposes I don't need nonascii domains. Feel free to use unicorn characters in your address bar, but I'd much rather have it special cased in

by MosesKing 10y ago

realityking 10y ago
America first! Or, in this case, English first! There's an argument to be made that we should not solve problems in a fashion that only benefits English (or English and other European languages). Generally when that happens the speakers of those languages - which are still the dominant group in internet standardization - loose all interest in fixing the problem for everyone else. The internet is on the way to becoming a truly global medium, if it isn't there already. We need to stop designing for English first.
- MosesKing 10y ago
  Fixing the problem is a matter of locale. Fixing it for me doesn't preclude non English speakers from having their own solution. How is that English first?
- Jare 10y ago
  We need to think things through and take security seriously, before we cause more serious problems. We have all seen semi-broken characters and weird symbols appearing in text (due to fonts, codepages, encodings, or plain bad handling of unicode strings) for decades now, and have mostly shrugged it off, accepting that maybe someone else is seeing more appropriate text thanks to that. But security is not the place for such cavalier attitudes. I'll gladly give up my Ñ's and É's and Ç's in domains and other global identification services, in exchange for knowing that It Will Just Work, always, everywhere, safely. And once the "very smart people that really figure things out" have a solution that works with more extensive cultural/linguistic features, by all means put it in place.