It has been fixed for German though.

It’s not you, I see it too.

But… What is this? I’ve never heard about bread pudding and on the photo it doesn’t look very appealing to be honest.

I’d love to try though. Would you mind sharing your recipe @OP?

But that’s not what the, want.

What they want is a “Share”-option for an entire community I sted of only sharing posts or comments.

I think this is a very reasonable request.

@OP: are you on GitHub and can you create a feature request?

Thanks! I now see me question was useless… Sorry… I did read “load” not “upload”. When I tested uploading a larger image file (2.44 MiB) I got a HTTP timeout error.

I agree that these upload errors are probably due to large filesize. We should find out whether there is a maximum file size on Lemmy in general, whether it’s instance specific or if it’s actually a problem with Jerboa.

Edit: Looks like the root cause is not Jerboa but Lemmy:

https://github.com/LemmyNet/lemmy/issues/3349

Maybe let the Lemmy people sort this out first and then we’ll find a way to communicate the actual upload limit to Jerboa users.

Could you please link to a post affected by this?

Yes you’re right but this wasn’t exactly intended.

Lemmy 0.18 introduced API breaking changes namely because it switched from WebSocket to HTTP as transfer protocol. They also dropped captcha support in 0.18 which is the reason why lemmy.world and other bigger instances are waiting for 0.18.1 to re-introduce captcha support.

This is more than weird. Jerboa dropped support for instances < 0.18 a few releases ago. I think 0.0.34-alpha was the last version that supported 0.17.4.

This is nothing new: Jerboa doesn’t support instances < 0.18.

Yes this is possible since 0.0.36-alpha but be aware that that version introduced some other issues that need to be fixed quickly.

I’m trying to make is that jerboa might not be as ready as we think for being a lemmy client.

I’m one of those random guys who try to improve things submitting a PR now and then fucking up things in the progress and trying to fix them again.

What I want to say is: I think you might be right saying Jerboa might not be as ready as many think. It started as a side project of one of the two guys who develop Lemmy full time. Dessalines even writes in Jerboa’s README that people can submit issues but he will most likely not be able to work on them.

Now Lemmy exploded: A lot of people started contributing to Jerboa (including me) with vastly varying skill levels (me definitely on the lower end), there’s no clear route the app will go in the future, no or little standards we can use as orientation.

And actually I’m not surprised at all that Jerboa might not be ready because this app went from “Just a little side project with 150 stars on GitHub on June 3” to “Probably most popular Lemmy client with 787 stars on June 27”. This has been less than four weeks. I don’t think any project is able to adapt to this influx of requests, changes, attention in this short time.

Yes, this problem is known and a GitHub issue exists.

https://github.com/dessalines/jerboa/issues/888

This should be fixed soon

Unfortunately it is not. There’s still a problem with the viewmodels but a major rework has been merged last night and a new version should release soon ™