Conversation

Notices

1. バツ子（痛いの痛いの飛んでけ;; (shmibs@tomo.airen-no-jikken.icu)'s status on Saturday, 04-Jun-2022 05:12:26 JST バツ子（痛いの痛いの飛んでけ;;

   in reply to

   • opal :pochiko:
   • Infected Moomin
   • zxcvfadsf
   @wowaname @Moon @zxcvfadsf every time i search for a jp word the top results are all chinese, because unicode ._.
   • opal :pochiko: (wowaname@anime.website)'s status on Saturday, 04-Jun-2022 05:12:28 JST opal :pochiko:

     in reply to

     • opal :pochiko:
     • Infected Moomin
     • zxcvfadsf
     @zxcvfadsf @Moon i18n is a necessary evil and unicode does a passable job at making it work
   • opal :pochiko: (wowaname@anime.website)'s status on Saturday, 04-Jun-2022 05:12:31 JST opal :pochiko:

     in reply to

     • Infected Moomin
     • zxcvfadsf
     @zxcvfadsf @Moon no it wasnt, chill out
   • zxcvfadsf (zxcvfadsf@shitposter.club)'s status on Saturday, 04-Jun-2022 05:12:45 JST zxcvfadsf

     in reply to

     • Infected Moomin

     @Moon unicode was a mistake

   • Infected Moomin (moon@shitposter.club)'s status on Saturday, 04-Jun-2022 05:12:47 JST Infected Moomin
     You would think that there would be an available JavaScript library for detecting Unicode homograph attacks, but I can't seem to find one. Right now I'm just detecting if any non-ascii characters are in a string and warning the user.