I'm sorry but I have accents in my name and your choice is not smart. Probably will have a hard time getting to your site, might even think it's a mistake. The guy that used the normal s did the right thing, you have the equivalent of a novelty domain with an emoji on it.
What the hell, how can you be so colonial you think it is normal to deny someone the right to their name just because it doesn't come from that one language you ever bothered to learn?
Like I said, my own language has accents and my own name has accents. I value practicality and being available, if I'm taking the time to create a website and host it. I would think the OP would be familiar with the fact that every single website in their country, even when the brands have accents in their names, do not use them in their URLs. Their choice is a novelty one. I'm not sure why you're getting offended over something that is purely practical and that affects me personally and I still do the practical thing.
Not dumbing down your own culture to submit to the outdated limitation of the American Standard Code for Information Interchange is not a novelty. Forgoing your language is not practicality.
It's normal to expect technology to evolve to be usuable by all rather than expect people changing to conform to technology. People should fight for that more often.
Even us, users of IDN domains, still submit to the outdated and always present ASCII. Punycode is, after all, still ASCII and "real" UTF-8 characters are rarely and exceptionally seen in DNS.
It may be debated that with introduction of punycode, support for real accent and non ASCII characters was hindered.
https://pi.cr.yp.to/ experimented with UTF-8 in domain names before punycode and this will rarely ever work in the future, purely because now we have a half-solved problem with punycode and no one will bother to implement UTF-8 domains - it's would be ambiguous.
I'd rather get my website seen if I'm putting work into it than have a novelty URL that much less people will navigate to and will be harder to verbally communicate, and fill in online forms that assume ascii, just for some idealogical fight against internet standards.
I don't think the person - who also has non-ascii characters in their name - is saying we should deny people the right to their name. Just that only certain characters should be in URLs.
I'm not picking a side; you just seem to have supremely misinterpreted their position.
I would argue that this is a pragmatic argument, not a colonial one. If you see 你好.com written on a billboard, are you likely to be able to visit that site by typing it in on your computer? Unless you have a Chinese keyboard installed (and also know what those characters mean), you simply cannot visit that site, whether or not you are a xenophobe. Nihao.com, on the other hand, is more or less universal accessible.
On the other hand, because of domain restrictions and other such nonsense Chinese websites will often use numbers that sound like words when spoken out loud rather than actual words for their domains.
Imagine being forced to only register 1337-code domains because some other country doesn't have Latin key caps on their keyboards.
Not understanding the local writing system or language does suck for foreigners, but most people in the world aren't foreigners in the country they live in.
Why should countries almost exclusively using the Arabic script be forced to switch between Latin and their normal way of writing because they want to edit the URL between writing comments? Why shouldn't people native in the 120+ languages using Devanagari be able to register domains?
Pragmatically speaking, the lack of proper language support in many non-Latin websites had led to a significant amount of them using images for labels rather than text, making Google/Bing/Baidu Translate worthless for navigating them. If you know what 你好.com is supposed to provide or sell to you, you can find it in a search engine and manually picture-check the domain if you want to be sure; the burden of being available to people outside your target demographic shouldn't fall on you just because a tiny slither of your user base doesn't understand your writing system, but you can opt into making it easier for them to find your website regardless.
Some years ago I had the weird idea of localized domain names. Some mechanism like rel=canonical, that would indicate first that two domain names in different scripts are the same and second indicates the preferred displayed domain name according to the locale of the user. So sesamstraße.example could be displayed as is for de-DE and de-AT, but as sesamstrasse.example for de-CH, assuming both domain names are registered and indicate sameness. With that at least for the main locale of a domain the users do have the minimal courtesy of having the domain displayed right and for other locales there exists an ASCII compatibility display.
But of course giving websites control over the display of their domain name is a major security headache. No idea what kind of stuff would be possible and how it would interact with TLS.
This is probably a reasonable way to handle sesamstraße.example, but how do we manage if skroutz.gr wishes to become σκρουτζ.com? Do we grant them scrooge.com in a non-Greek locale, as Skroutz is the Greek transliteration of Scrooge, or do they get stuck with the letter-for-letter skroutz.com? Will I go to a different site depending on my locale if I type scrooge.com?
What happens when someone registers θεν.com and someone else gets δεν.com, since both transliterate into ASCII as then.com?
That was why I thought that for the reason to work the entity has already have to have registered both (or more) domain names and both domains must, possible in DNS records, indicate their respective equivalence. So no automatic translation, but definitive opt-in by the domain owners.
I had a similar non-related idea for web browsers. Currently domains are mainly lowercase on the web, so we could use a HTTP header to specify the correct capitalization.
capitalization: HarryPotter.Hogwarts.UK
Of course we'd have a lot of lookalike domain problems, like we have with IDN now (:
On the other hand: If you're Chinese and don't know what nihao means, would you not rather be able to simply go to 你好.com? (Chinese might be not the best example here because pinyin is very widespread, but that's not the case for every language)
If you can't type 你好.com you're simply not the website's intended audience.
Some around here have argued that allowing filenames with spaces was a bad idea. I disagree, but the rationale is not "colonial", it's a matter of practical limitations and whether we should modify our behavior to make the system simpler or try to conform the system to our ludicrously messy standards and, as a consequence, make them more complex and therefor fragile.
The standards do have limitations anyway. For instance, you cannot have an underscore in a hostname on the internet. You can have one in a CNAME, technically, but most CAs will not sign a certificate for any name with an underscore.
Yes, I agree. I hoped for the domain with s to be forgotten by the owner. It impossible to use this domain with š if I don't own the other one, that's why I don't use the domain under national TLD and instead use .eu for personal email and website.
It's weird that Google prefers the IDN variant under national TLD instead of the non-IDN variant with an IDN counterpart under .eu.
Another interesting phenomenon is that chromium detects suspicious activity and informs the user if he meant to go to š.tld when visiting s.tld. Or vice-versa, depending on which site he opened first I think. It's nice how the browser detects different ownership - this does not happen for other TLDs where I own both domains.
