this is a minor, super low-priority request!

I like using the built-in beemojis. On desktop, they are easy-to-use and they show up in-line like any other emoji. However, on mobile, the beemojis are impossible to access, and when i see them in comments, they expand to their actual size:

Now, the access to the beemojis may be specific to my lemmy app (Sync), so that might be an unsolvable problem. But the sizing issue seems like it is related to the way beehaw implements the custom emojis, so I am wondering if that is a quick fix. It seems like they are just a set of image files stored on the server, and so using the emojis is just pasting a link to one of these image files. Is there a way for beehaw admin to set like a “max width” or something that might make the beemojis look better on mobile?

  • Powderhorn@beehaw.orgEnglish
    3·
    18 days ago

    I’m ambivalent about Sync, but before the server upgrade, it was one of the only games in town still supporting the 0.18.4 we were on. Now that we’re up to 0.19.11, I’m certainly considering other clients, and while that may solve your issue, I know no one likes shopping around.

  • Chris Remington@beehaw.orgM
    3·
    18 days ago

    Making a beemoji to view it with Mlem (iOS app) bee blep emoji

    EDIT: The beemoji looks perfectly fine with Mlem. So, this is probably a Sync problem.

    • coyotino [he/him]@beehaw.orgOPEnglish
      2·
      18 days ago

      good to know. thanks Chris! I’ll explore alternatives on Android. As Pete pointed out, Sync might not be the best Lemmy Android app anymore, so I am overdue for an upgrade.

        • coyotino [he/him]@beehaw.orgOPEnglish
          3·
          14 days ago

          So far have not found a new one. Tried boost, and it has the same issue. But I still have a few more to try!

          Edit: Voyager for Lemmy seems to fix this issue, so I think that is what I am going with.

          Edit2: I’m dumb, I have not tried Voyager. The app that is working for me is called Summit. Voyager may also solve this issue, but I cannot confirm.