I think it’s not really on your side, most likely either just something wrong on kbin.social itself, OR a side-effect of the measures lemmy.world implemented against kbin.social recently.

They are basically local-only communities on lemmy.world at this point, unfortunately. There is no federation to any other instance for any lemmy.world user posts on those communities.

You haven’t been doing anything wrong from your side - we have just been experiencing some growing pains with a new Lemmy feature (image proxying).

It’s a bit unfortunate that these problems cropped up, but ultimately we will benefit from this new feature, as it will help solve several issues with Lemmy image hosting overall. So I hope you can forgive the issues and trust that the end result is worth it!

Ahh I see the issue & have fixed that example post now.

Basically, I had already fixed the root cause which was breaking the images, but there was a period while I was working on the fix during which some images posted would remain in a broken state. I don’t unfortunately have a fast way of automatically detecting and fixing those broken images unfortunately, but I can fix them one by one manually.

Having said that, any new images posted now are not getting broken. I’ll see what I can do about the broken ones, maybe I can find some way to automate fixing them.

Hey, I’m not seeing any issues at the moment, can you share more details about what is broken for you currently?

I’ve made a few PRs to hopefully improve the image situation, these are all running on lemm.ee as of now as well, so hopefully it’s better now!

https://github.com/LemmyNet/lemmy/pull/4871

https://github.com/LemmyNet/lemmy/pull/4875

https://github.com/LemmyNet/lemmy/pull/4874

The maximum file size limit for images hosted directly on lemm.ee servers is always visible in the sidebar of our front page. The limit stands at 500kb per image currently.

Additionally, It’s also possible to post images larger than 500kb, they just have to be hosted externally. The markdown for this is ![alt text](image url)

I’ve made some experimental changes, please let me know if you notice any difference

I’ve implemented a workaround for the imgur rate limiting now!

I’ve changed the logic now to no longer proxy imgur images, so their rate limits should no longer affect us!

Thank you, that’s super useful, I will try to investigate what was going on with that request

Hey, I don’t actually see anything abnormal in terms of metrics. What continent are you connecting from (if you don’t mind sharing)?

Do you know around what time it got slow for you?

Hey!

Around June 9th I found that I could no longer display images in comments & posts. The specific problem seemed to stem from some broken code that was being auto-added

This is most likely due to the imgur rate limiter which is blocking our server (Basically our server is trying to request too many images from imgur). I have a plan to bypass our image proxying for a handful of known image-hosts, such as imgur, but haven’t been able to implement this yet. But it’s coming soon!

In general I intend to keep image proxying enabled for most other sites, though, because it allows protecting the privacy of lemm.ee users, as well as ensures slightly faster page load times compared to always making users fetch images directly from their original host.

But sadly, there’s more. Namely, it seems that lemm.ee communities are no longer showing up in one of the significant FV search engines, i.e. “lemmyverse.net.”

This requires fixing on the lemmyverse.net side - they currently only have support for older Lemmy versions, but I believe it’s only a matter of time before this gets fixed.

It’s not really a bug, it’s just a case where app developers need to update their code to support a small change in the Lemmy API. More details here: https://lemm.ee/post/34259050/12479585

It’s occasionally breaking for us due to imgur rate limiting the lemm.ee server. I am planning to disable proxying for a few well known image hosting sites (including imgur) soon - it requires some additional development, but I think I’ll be able to do it in the next few days. Sorry for the inconvenience!

Hey, this post is quite old, actually you can find the latest info in the sidebar of our front page:

• Image uploads are enabled 4 weeks after account creation
• Image upload limit is 500kb per image

Hey! Thanks for the report.

I think the first issue is not something I can help with - probably the Connect app needs to fix something on their side.

For the second issue, see my comment here: https://lemm.ee/post/34118135/12479638

I have identified two reasons for broken thumbnails right now:

1. For some, the source website is simply not allowing our server to download the image (mostly due to server issues on the remote side)
2. For others, it seems that some types of URLs are breaking thumbnail generation. I think I found the bug here and will try to submit a fix soon.

That’s definitely not intentional - it’s a custom error message which we have just for lemm.ee, not a standard Lemmy error, and it seems I need to tweak it a bit for it to work correctly in 0.19.4. Thanks for reporting this!

Yes, lemm.ee has all the standard Lemmy features. However, the format for this request has changed, and it seems the app has not been updated yet.

For technical context: your app is trying to use the singular post_id field when marking posts as read. This field was marked as deprecated several releases ago, as it was replaced by a post_ids array field, in order to enable marking multiple posts as read at the same time. The deprecated post_id field has been removed in Lemmy 0.19.4.