this post was submitted on 13 Aug 2025
480 points (99.0% liked)

Microblog Memes

11539 readers
2605 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

RULES:

  1. Your post must be a screen capture of a microblog-type post that includes the UI of the site it came from, preferably also including the avatar and username of the original poster. Including relevant comments made to the original post is encouraged.
  2. Your post, included comments, or your title/comment should include some kind of commentary or remark on the subject of the screen capture. Your title must include at least one word relevant to your post.
  3. You are encouraged to provide a link back to the source of your screen capture in the body of your post.
  4. Current politics and news are allowed, but discouraged. There MUST be some kind of human commentary/reaction included (either by the original poster or you). Just news articles or headlines will be deleted.
  5. Doctored posts/images and AI are allowed, but discouraged. You MUST indicate this in your post (even if you didn't originally know). If an image is found to be fabricated or edited in any way and it is not properly labeled, it will be deleted.
  6. Absolutely no NSFL content.
  7. Be nice. Don't take anything personally. Take political debates to the appropriate communities. Take personal disagreements & arguments to private messages.
  8. No advertising, brand promotion, or guerrilla marketing.

RELATED COMMUNITIES:

founded 2 years ago
MODERATORS
ReadyUser31@lemmy.world
aeronmelon@lemmy.world
needanke@feddit.org
480
Twenty-eighth amendment (aussie.zone)
submitted 9 months ago by maniacalmanicmania@aussie.zone to c/microblogmemes@lemmy.world
35 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] moseschrute@lemmy.world 3 points 9 months ago* (last edited 9 months ago) (1 children)

So I actually kinda know what I'm talking about, but not really:

  • Lemmy uses pictrs to handle image uploads
    • I know from experience that pictrs will fail on gif upload if max width is greater than PICTRS_MEDIA_ANIMATION_MAX_WIDTH and same for height and (I think) animation frame count
    • It's less clear to me if static images get auto compressed on upload. Looks like pictrs implemented this a couple years ago, but I'm not sure if this is automatic behavior or has to be turned on by Lemmy admins.
    • I haven't messed around with limits for image dimensions other than the settings for animated media, but I'm planning on testing this on my instance soon.
  • Lemmy API image upload
    • 0.19.x has all images uploaded via the same API endpoint. So I think any image uploaded should be subject to the same dimension and size limits.
    • In the upcoming Lemmy v1 release, this might change as I believe they will have different upload endpoints for avatar, banner, post, etc. Avatars, for example, might be subject to smaller dimension limits. This is all subject to change as Lemmy v1 is not released yet.
  • Lemmy API getting the image upload limit settings
    • 0.19.x does not expose the image upload limits via the API. So whatever, for example, lemmy.world set's their limits to, there isn't an easy way for a Lemmy frontend to look up those limits.
    • In the upcoming Lemmy v1 release, I believe they are planning on adding a way to look up these limits via the API.
  • Other limits
    • Lemmy imposes it's own rate limits on how many images you can upload/time period. I wanna say the default is roughly 6 images/hour, but I might be totally wrong there.
    • I'm also curious how many sever admins leave the default settings, or change them.

TL;DR, what does this all mean?

  • Uploading gifs is always going to be a little annoying as they don't auto compress. As a server admin, I just set the dimension limits higher so users encounter errors on fewer images
  • Non animated images, I'm guessing are automatically compressed on upload. Otherwise I suspect many more people would be complaining about failed uploads. But I'm working on verifying this

Just to be extra safe – and also here’s why I know all this – I've chosen to auto compress images on upload in my own Lemmy/PieFed frontend to 1mb and 1000 max width/height, whichever comes first. I'm actively testing these settings.

[–] flamingos@feddit.uk 1 points 9 months ago (1 children)

It’s less clear to me if static images get auto compressed on upload. Looks like pictrs implemented this a couple years ago, but I’m not sure if this is automatic behavior or has to be turned on by Lemmy admins.

Non animated images, I’m guessing are automatically compressed on upload. Otherwise I suspect many more people would be complaining about failed uploads. But I’m working on verifying this

There does seem to be options in pictrs to compress images by format, I'd assume that having these unset (default) would mean no compression happens. I think the reason there isn't any complaining about image uploads happening is because, by default, they don't have constraints applied to them. Only animation (256x256 dimension limit) and video (max 20 MiB file size) have constraints put on them in pictrs by default, though there is a 20 MiB upload limit set in nginx.

Lemmy imposes it’s own rate limits on how many images you can upload/time period. I wanna say the default is roughly 6 images/hour, but I might be totally wrong there.
I’m also curious how many sever admins leave the default settings, or change them.

feddit.uk has its set to 2 every 5 minutes. I think a previous admin set that, but it seems sensible enough.

[–] moseschrute@lemmy.world 2 points 9 months ago

Thanks! I think I’m just going to upload progressively larger images to my instance and see where uploads fail lol.