

Locking for rule 5.
this account is only used for modding, main account: @asudox@lemmy.asudox.dev
aspe:keyoxide.org:D63IYCGSU4XXB5JSCBBHXXFEHQ


Locking for rule 5.


Locking for rule 5.


Locking for rule 5.


Locking for rule 5.


OP, I’ll be locking your post as it violates rule 5.
OP, I’ll be locking this post as it violates rule 5.


OP, please mark this post as NSFW.


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.


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


If that were to happen, the receiving end wouldn’t know who sent which vote, thus making spamming extremely easy.


GNU Taler


If it means my code won’t panic out of nowhere and cause a disaster for me, I am willing to “take a vacation” for my program to finish compiling.


I use rust btw.
deleted by creator