this post was submitted on 09 Aug 2023
208 points (100.0% liked)
chapotraphouse
13519 readers
1160 users here now
Banned? DM Wmill to appeal.
No anti-nautilism posts. See: Eco-fascism Primer
Gossip posts go in c/gossip. Don't post low-hanging fruit here after it gets removed from c/gossip
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
yeah, that's gotta be the problem - I pointed out in a lemmygrad thread yesterday that hexbear had a similar problem in the first year or so of the site that specifically affected the hexbear logo emoji when it appeared in the site tagline (it became fucking massive, like 3000x3000)
our beautiful admins might have to rework svg/vector based emojis or even contribute something upstream to have unified resizing
is also massive lol
It looks normal on hexbear on either pc or mobile, but this is what other instances see lol.
It definitely makes us look even more unhinged to others. Dropping massive Ppb and I'm Vegan images lmao
I was thinking earlier about how powerful it makes us that we can't see downvotes, like we could be in a thread getting -50 on every comment and just keep chugging away without a care. This makes it even better.
Removing downvotes has been a blessing in several ways.
It also helps that like 20 people jump in with and shit, so downvoting it all is annoying and time consuming for anyone who wants to.
damn this rules
Yeah, it's better like this. It should be bigger on hexbear too
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.