This PR was made while investigating a request to update the limit to allow 7680x4320px pictures. Such a change would make ImageMagick's consumption up to 485MB per picture at maximum size (from the already-high current value 300MB). I don't think that's reasonable, but we could consider it in the future if we move away from ImageMagick to something more tractable.

I'd like to see larger image sizes supported. The memory consumption isn't an issue for me.

Honestly, I'd also like larger video file size too. I think it would be great to target videos of 60 seconds or less and natively support image sizes of modern phones.

The memory consumption isn't an issue for me.

It may be for a lot of admins, though.

The memory consumption isn't an issue for me.

It may be for a lot of admins, though.

I don't disagree. I wish we had data.

I have users quitting because the UX around uploading photos isn't that great and mobile phone native images sizes are growing faster than we seem to want to support. ivory goes a long way here in mobile UX and handling iOS images according to mastodon dimensions, but i don't think that's a better solution than increasing ram requirements by a tiny amount.

Costs me more time/money in responding to the issues than just paying for more resources and supporting modern image sizes.

I'd be happy to run with this patch and report back on any numbers/graphs that may be helpful

This pull request has merge conflicts that must be resolved before it can be merged.

I believe this accomplished a variation on this idea - 9bda933 - closing this one because the JS file doesn't exist anymore, but we should rebase/reopen if we want to track the even higher size bump still?