8
submitted 5 months ago* (last edited 5 months ago) by JohnnyEnzyme@lemm.ee to c/support@lemm.ee

Yes, I'm the very same ~~moron~~ person who accidentally deleted his community, then had it restored by our excellent admin / site-runner a month or two ago. Yup!

Now for today's stupid-idiot complaint:

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, namely:

"https://lemm.ee/api/v3/image_proxy?url="

IIRC my co-mod opened a thread on this stuff around a week ago." And... in the words of the kids? "Shizzle's still broke." I.e., the code still doesn't work, and still breaks every attempt to share images.

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."

For example, one of our biggest communities here on lemm.ee, i.e. "movies" is now totally missing from the results. So, (currently) every time people look for stuff on search engines like that, lemm.ee communities will be invisible to them.

https://lemmyverse.net/communities?query=movies

top 11 comments
sorted by: hot top controversial new old
[-] sunaurus@lemm.ee 3 points 5 months ago

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.

[-] JohnnyEnzyme@lemm.ee 2 points 5 months ago

Thank you!
And please let me know if there's anything I can do to help.

Overall I'm really happy with my community and this instance, just that... shit is frustrating, lol.

[-] sunaurus@lemm.ee 2 points 4 months ago

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

[-] JohnnyEnzyme@lemm.ee 1 points 4 months ago

Tested and confirmed, thank you so much! <3

[-] JohnnyEnzyme@lemm.ee 1 points 4 months ago

Oops.
Worked yesterday, but broken again today. Dang.

[-] sunaurus@lemm.ee 1 points 4 months ago

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

[-] JohnnyEnzyme@lemm.ee 1 points 4 months ago

Certainly.
So then, in WinX' latest Chrome, latest behavior is as described above.

I.e., that the auto-added "image redirect" command that it seems you recently implemented, unfortunately so far seems to break viewing of an image in comment/post as described/exampled above.

Right so-- I had the idea that in case of any more problems going forth, I should then point to an image both in standard Lemmy protocol, but also just as pure web link, just to be sure.

Example post: https://lemm.ee/post/35734760

For example, yesterday I saw pictures and related links below, and today I see blank spaces and just the links themselves, no pics. I.e. same issue I was whining about originally.

https://i.imgur.com/Bo6rw3Q.jpeg

Here's more of the same markup-code, from same post:
https://i.imgur.com/gagmsNw.jpeg

[-] sunaurus@lemm.ee 1 points 4 months ago* (last edited 4 months ago)

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.

[-] JohnnyEnzyme@lemm.ee 1 points 4 months ago

Thank you!
huge sigh of relief

Okay, my host, Sunaurus-- In future, would you say there are any specific do's and don'ts about trying to include image content in posts & comments? Like, should I be doing something more smartly..?

[-] sunaurus@lemm.ee 2 points 4 months ago

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!

[-] JohnnyEnzyme@lemm.ee 1 points 4 months ago

Sounds good to me, and anything we can do to help, please!

Oh, geeze, no apologies necessary on anyone's end, particularly towards our wonderful host's end. We're going to help make the Fediverse work, right? Alrighty then! ^^

this post was submitted on 24 Jun 2024
8 points (90.0% liked)

Support (lemm.ee)

731 readers
8 users here now

lemm.ee Support

You can make a post here if you're looking for support with any issues!

For general discussion about lemm.ee, please post in !meta instead.

founded 1 year ago
MODERATORS