17
[WIP][v1.64.0] admin/mod update
(lemmy.world)
Community to discuss Summit, an open-source Lemmy reader for Android.
App (Play Store): https://play.google.com/store/apps/details?id=com.idunnololz.summit
APK: https://github.com/idunnololz/summit-for-lemmy/releases
Source: https://github.com/idunnololz/summit
Support the app
Website: https://summit.idunnololz.com/
I can't reproduce this issue on my end. This might be some sort of weird thumbnail error. I've seen these before where the thumbnail generated by Lemmy is of bad quality. The quality then changes later on, but the client has already cached the old thumbnail. I'm not 100% sure what a good fix would be.
Happens to me too
Can you link the post where it happened? Thank you.
Could it be that the thumbnail is being loaded from cache instead of the proper asset? I guess it might be possible to put some cache rules in place to alleviate that.
There are cache rules in place already. Its just that the images are cached for up to a day. Actually can you check to see if you can still reproduce the bug? The cache should be invalid by now so you should see the correct image if my hypothesis is correct.
Just checked again, the issue is still present.
This is very weird. Can I ask which Android device you are using? I tested this on three different devices across accounts on 4 different instances but I am unable to reproduce anything.
I'm running a Pixel 7 Pro with Android 15.
Let me know if you need me to drop a breakpoint, I work with Android dev so this would not be hard for me
Sorry for the late reply, been busy. Honestly, I wouldn't even know where to drop the breakpoint. There are a dozen possible issues here. One thing I should check though is your settings. If you can, can you please export your settings and DM me?
To export settings go to: Settings > Import & export settings > Export settings > Copy to clipboard. Then you can paste the settings to me in a DM. I don't think I need your "database" info so feel free to uncheck that.
Fwiw, it seems like the issue is no longer present now, so maybe it was a backend issue. Let me know if you still want those settings, but reproduction might be impossible at this point.