• viking@infosec.pub
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    3
    ·
    11 months ago

    Sounds like a crappy implementation of the authentication server then, and the sysadmin deserves a paddlin’ for not stripping non-UTF characters (or making sure they work).

    My problem with using emojis as part of the password would rather be that while I might be able to enter them on my personal Android phone using the exact keyboard app I have installed right now, I might find myself struggling on a desktop computer or any other phone that doesn’t have this exact keyboard installed. After all, the graphical representation of the same emoji might look different there, and there is a chance I couldn’t even recognize it.

    So if anything, I’d say use a non-UTF keyboard like Thai or Chinese, but then a standard character in that specific type. Keyboards layout can be installed across devices and are fully standardized, even if the same character looks slightly different.

    • kuneho@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      11 months ago

      also some OSKs put whitespaces after inserting an emoji, some doesn’t. there’s no unified emoji input method yet.

    • lolcatnip@reddthat.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      There’s no such thing as a non-UTF8 character. You mean non-UTF8 bytes? If a system sees those, it should reject the entire input, not try to patch it up.