No problem. Though I’ll be locking this post. It really generated lots of reports and drama in the comments section.

Your post is locked for rule 5, OP.

Just as a side note: Accounts not on the instance of the community (in this case lemmy.world) will have problems receiving and resolving reports.

This is a known issue and will be supposedly fixed in Lemmy v0.20.0

99.9% / 0% / 0.1%

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.

Which most likely is written in much more detail than you ever could do.

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

what the fuck

I use rust btw.

I mean, all cmake does is run some commands for you. You not understanding cmake errors (mostly) means you don’t understand the errors given to you by the C/C++ compiler.

FlyingSquid seems to have alot of accounts on different instances

Well, I haven’t really started building it yet. I do plan on using Leptos for an upcoming project I have.

Oh no, I dare not belittle CSS. I haven’t even done any real website development yet. It was all just Rust and Python backends.

So just new CSS?

ironically

I agree.