Lemm.ee communities locked out of various Lemmy / FV search results, plus image-sharing still broken since June ~9th:
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:
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.
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.