Should someone open a language-specific language server and use the same community name, for example, open source community on thai-language-lemmy.xyz?
Should I create a community with a language on community name, for example, Thai Open Source?
Should someone open a language-specific language server and use the same community name, for example, open source community on thai-language-lemmy.xyz?
Should I create a community with a language on community name, for example, Thai Open Source?
We were talking about this in the Matrix room, to allow the use of non English characters as the name value, it’s not yet there, but maybe you could use a romanization of that as the name and use “การเขียนโปรแกรมภาษารัสท์” as the display name while it gets done?
Romanization makes the most sense overall.
We were discussing the idea of allowing non English characters so that if someone decided to create a language specific instance they could use their native characters in their communities, stepping away of how anglocentric the internet is.
Yeah it’s a tough call. The usefulness of it is obvious, but also in many cases it is so difficult to perform input on certain language even for those who regularly speak and use them. On platforms like Lemmy I will often type in the address manually, like “lemmy.ml/c/coffee” and if I had to instead type “lemmy.ml/c/قهوه” it would be a pain in the ass. I could just have Romanized قهوه as “qahve” and everything would be fine.
So if you’re willing to accept Lemmy being a bit more of a complicated mess then it’s a fine innovation. Many languages would benefit from allowing Unicode characters. And then maybe we can have communities named with emoji…
How about restricting emoji in a community name instead of allowing only Latin alphabet?
Thai-ization of Rust is รัสท์. Romanisation of รัสท์ is Rust.