Because URLs are usually in ASCII. That was a standard. Check RFC 1738 and 3986. Now, you can use percent encoding, but why use that. It just complicates things.
You won't get non latin usernames anytime soon. But you can change the display name using non latin charactets
Yeah, tell them that when they were trying to deanonymize tor users
No. It's for privacy. If they don't support anonymous payments, there's literally no reason to host a .onion site just to fool people. I'd say that's a big red flag from a "privacy respecting" company.
I said:
I couldn't care less as long as the language is good.
Why wouldn't I care if the language is bad in my opinion?
Sure. It is open source, but the development is done by Apple engineers. I also would like to state that Go has trackers in it. I also don't really care what the creator of a language is. Homophobe, sexist, racist or other similar stuff, I couldn't care less as long as the language is good.
Yeah who cares. They got caught tracking and that is still a fact.
Oh great. Now I'm losing hope in this project even more.
No, not at all. They both are made for different purposes.
view more: next ›
Using ASCII in URLs is simple and is less error prone than "supporting" unicode via percent encoding. It is also just a convention to use ASCII for usernames in many platforms. ASCII is also supported out of the box in major OSes while some unicode characters might not. What about impersonation? And what about people trying to type in the username of someone that uses unicode? It is not logical to use unicode in this case.