You're viewing a single thread.
Fun. What app is that?
Avelon, it’s a lemmy iOS app.
Software dev here.
Client app have little to no knowledge about server limit.
Usually the limit is set at various places in the server. Even the server app itself does not know it's file size limit most of the time.
Anyway the screenshot is still worthy of the topics.
Still though if the limit is blocking a single image from being uploaded it's going to be pretty small. I can WhatsApp a 4K image because it'll do down sampling to 720p, it seems odd that the same tactic wouldn't be implemented here.
Resize without resampling is not resource intensive and appear not as good as resampling.
Still server has to
- Accept file (needs bandwidth and storage space)
- Resize (needs storage, RAM and CPU)
- Clean up (needs CPU)
I don't know lemmy has this feature or not. Even if not, as Lemmy server get mature this feature might get implemented. Server might allow admin toggling this feature.
Recent attack on Lemmy servers with CSAM made server admins to completely turn off the image upload. That could also be the case here.
No hard feelings, I hope! I love the app, the screenshot was just too good to pass up! :)
Not the avelon dev. Just a nobody software dev.
Just sharing my exp.
Even the server app itself does not know it's file size limit most of the time.
The fuck are you talking about? It's likely an ENV variable or config variable that literally HAS to be accessible to any file upload in order to even return this error message. Quit making shit up.
quit making shit up
Here is the faq related to what I am talking about.
https://www.cyberciti.biz/faq/linux-unix-bsd-nginx-413-request-entity-too-large/
Server (application) does not know the site upload limit because it was set by reverse proxy. Any of them could reply with http 413 status and client will just show you the message like screenshot.