this post was submitted on 31 Oct 2024
15 points (100.0% liked)

Meta (lemm.ee)

3473 readers
1 users here now

lemm.ee Meta

This is a community for discussion about this particular Lemmy instance.

News and updates about lemm.ee will be posted here, so if that's something that interests you, make sure to subscribe!


Rules:


If you're a Discord user, you can also join our Discord server: https://discord.gg/XM9nZwUn9K

Discord is only a back-up channel, [email protected] will always be the main place for lemm.ee communications.


If you need help with anything, please post in !support instead.

founded 2 years ago
MODERATORS
 

Is it just on my end? All other instances i have tried (.world, .ml, sh.itjust.works, db0, even hexbear) are displaying thumbnails correctly. I have tried opening lemm.ee in chrome, changing my dns etc.

Anything else I can try? Any help is appreciated.

Here are the screengrabs for those interested https://imgur.com/a/LGlVI6T

top 4 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 6 days ago* (last edited 6 days ago)

Looks a bit to me that you're using TOR on the phone. I have not checked if Lemm.ee is using cloudflare or a form of CDN to fetch the thumbnails. If some malicious actor is exiting from the same exit node as yourself, its likely that the CDN have temporary blocked the IP address by the CDN being provoked.

To resolve that, refresh the onion relay by clicking 'New Circuit' within the menu or simply close the TOR browser completely (and background tasks), before navigating to the website again to get a new exit node.

Edit: I failed to see you seem to be using chrome in the picture. My bad ^^ Happy new Year Though!

[–] over_clox 2 points 2 months ago

are?

Don't you mean aren't?

[–] [email protected] 2 points 2 months ago

it's not just on your end. I have the same issue, when I'm using a browser. it's working fine when using jerboa though.

[–] [email protected] 2 points 2 months ago

I think it's related to this issue (re: lemm.ee is fetching and caching images (to improve performance) , but often get is throttled (because the Lemmy's cache implementation was not designed to work with larger Lemmy instances ), which results users seeing broken images).