No it’s definitely higher on Lemmy.world. I uploaded the same image from there successfully (6.6mb). The limit seems to be on the resolution itself. I just exported the same image in the same resolution (4032x3024) but downscaled to 1.4mb and I’m still getting the too big error on programming.dev
I think 1MB is too low for a good user experience. Having to first have to first downscale images taken from the phone is a big point of friction for mobile users.
Perhaps pict-rs, Lemmy’s image hosting backend, could auto downscale image uploads and only fail if the input was egregiously large to preserve upload bandwidth and avoid DDoSing. Would still be another added workload for the server.
Perhaps down scaling would be best done on the client side, then the resulting effect would be more transparent to the user before submission. Could that be done in easily in JS? Then that could help save storage and egress expenses for hosting funded only by donations.
I believe the limit is 1MB on all instances by default so should be what our current limit is as well
No it’s definitely higher on Lemmy.world. I uploaded the same image from there successfully (6.6mb). The limit seems to be on the resolution itself. I just exported the same image in the same resolution (4032x3024) but downscaled to 1.4mb and I’m still getting the too big error on programming.dev
Edit: I could swear your comment said 2mb.
yeah lemmy.world probably overrided the default limit with something higher. We havent done so yet so will still be on the default
I think 1MB is too low for a good user experience. Having to first have to first downscale images taken from the phone is a big point of friction for mobile users.
You can upload images to third party sites and post the link instead.
Perhaps pict-rs, Lemmy’s image hosting backend, could auto downscale image uploads and only fail if the input was egregiously large to preserve upload bandwidth and avoid DDoSing. Would still be another added workload for the server.
Perhaps down scaling would be best done on the client side, then the resulting effect would be more transparent to the user before submission. Could that be done in easily in JS? Then that could help save storage and egress expenses for hosting funded only by donations.