What was more frustrating for me was the fact that the size limit isn’t reported anywhere (not anywhere obvious, anyway) and that Jerboa did not cleanly handle the error, so I had to eventually retry on desktop to realize it was an image size issue. Neither of these things are lemm.ee’s fault
As a web developer, I can appreciate being hesitant about hosting images, for a brand new service that probably currently exists on just one server somewhere. Text is miniscule when it comes to size, but images can balloon quickly, and I don’t know what the protocol would be (if any) for a Lemmy instance to delete images to reclaim space, in a way that wouldn’t cause problems.