@Profpatsch @jdlh @hongminhee @liaizon @Edent @north ..and on the database level (in my case Postgres) I use a non-deterministic und-u-ks-level1 collation, which should take care of NFC vs NFD vs NFKC vs NFKD and ignore differences in casing and accents
headcr4sh@corteximplant.com
@headcr4sh@corteximplant.com
Posts
-
@hongminhee @liaizon @Edent @north @Profpatsch (1/3) -
@hongminhee @liaizon @Edent @north @Profpatsch (1/3)@Profpatsch @jdlh @hongminhee @liaizon @Edent @north
Yeah, my approach here is to use UTS#39, which is explicitly made with the intent of getting around the problem of confusables. I chose HighlyRestrictive for now since it still allows for things such as "지호Park", without maybe going into questionable territory.
In addition I have checks in place to only allow characters from the unicode classes alphabetical and numerical. So no random emoji, but you can have something like "二十五" as your username (which falls IIRC under the numeric class)(moved accounts recently, not on @aumetra anymore :P)
-
haii!haii!
im baaaack on .com, wassup