I have been trying to post an image of my cat for a few days now, and consistently get this error, or one that just says "no value for error." Is this a problem with Jerboa, or with my instance, vlemmy?
Jerboa is a native-android client for Lemmy, built using the native android framework, Jetpack Compose.
Warning: You can submit issues, but between Lemmy and lemmy-ui, I probably won't have too much time to work on them. Learn jetpack compose like I did if you want to help make this app better.
Jerboa is made by Lemmy's developers, and is free, open-source software, meaning no advertising, monetizing, or venture capital, ever. Your donations directly support full-time development of the project.
1Hefs7miXS5ff5Ck5xvmjKjXf5242KzRtK0x400c96c96acbC6E7B3B43B1dc1BB446540a88A0141taVyY6e1xApqKyMVDRVxJ76sPkfZhALLTjRvVKpaAh2pBd4wv9RgYj1tSPrx8wc6iE1uWUfjtQdTmTy2FGMeChGVKPQuVaddr1q858t89l2ym6xmrugjs0af9cslfwvnvsh2xxp6x4dcez7pf5tushkp4wl7zxfhm2djp6gq60dk4cmc7seaza5p3slx0sakjutm
That means that the image you're trying to post is over 100kb. I suggest you converting your image to the webp format in an online converter and compressing it later. If that doesn't work, you're screwed
Oh interesting! Is that the hard limit for lemmy in general? It also might be nice to change the error so that users know to shrink their images.
I appreciate your response!
The limit can be changed, but it's up to the admins of the instance.
Its not strictly a Lemmy error, but in Nginx (or at least for me it was there), which is a service that sits between you and Lemmy and redirects traffic. But yeah, the frontend could still handle it better and at least give a better error message
Jerboa throws this specific error message a little too often, I think error handling needs some work.