There is a character encoding called punycode which is used for non-latin domains (e.g. cyrillic, or just random unicode domains). There is nothing that prevents people from creating pods on such domains. Actually there are some pods which use unicode domain names already (see: https://свидетеливилли.рф/).
It works totally fine, but it renders the domain in it’s fallback look
xn--..., instead of its unicode representation. So it would be great to actually fix our UI to show these domains in their pretty unicode representation.
But it raises a few questions.
If we support punycoded domains, then why don’t we support punycoded usernames? If we have to convert punycode to a pretty look, then why not converting usernames at the same time? IMO this feature makes diaspora more friendly for non-latin native writers and I think many people would love it to have non-latin diaspora IDs
We currently support hyphen as a part of user IDs, though our sign up page doesn’t allow to post it. So this is purely frontend-level issue.
We have to do the same conversion on user input, not only at rendering. Because if a user sees
микола@діаспора.укрas a diaspora ID then they will enter it to the search input and as a mention ID. So we have to make our frontend to punycode the ID before posting it to the backend.
Nobody has every layout available at their keyboard, so if someone has a unicode diaspora ID, it will be hard to type it for people who don’t have this chars available (e.g. when typing a mention). So possibly we need to make it configurable, e.g. have a little button somewhere at the current page which disables punycode rendering and shows fallback instead.