this post was submitted on 09 Aug 2023
208 points (100.0% liked)
chapotraphouse
13816 readers
635 users here now
Banned? DM Wmill to appeal.
No anti-nautilism posts. See: Eco-fascism Primer
Slop posts go in c/slop. Don't post low-hanging fruit here.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yes, you are on the right track.
What actually happened is, for the migration back to upstream lemmy, our devs developed and contributed the custom emoji feature, so that we could keep them, but since we were uploading them through the UI not baking them into the app when it was built as static assets, they had to go into pictrs (the image backend), which doesn't support SVGs yet. So as part of our migration we converted all SVG emotes back to PNG (apparently at a pretty substantial resolution).
They render correctly on our side because the UI recognizes that they are a local custom emoji and applies different CSS than we do for other embedded images, but as currently written, there is no simple way to differentiate a federated emoji from any other embedded image, so when federated, our emoji get rendered as just any image, at whatever size the file is. We will likely contribute a fix for this upstream, though resizing all of our emotes to a consistent size would also do the trick, and may be undertaken as a stopgap in the mean time.