Hi, just looked into this and it's now fixed on the beta (version 1.0.82). I just published it so it may take an hour or so from the time of this post.
I've added an option under settings (as of 1.0.81) to turn off Image Preloading which should help a bit. Part of the problem is that the files Lemmy serves as a 'thumbnail url' are actually the full sized image and the only resize option available to developers is specifying a thumbnail resize value which resizes it with raw pixel sampling so it can look pretty pixelated.
Thanks I will take a look! 2 questions:Which post view are you using? Asking because the list views load only thumbnails whereas full width is the full image. And which version is this? Asking because some improvements were made if you're on the beta.
Just posted 1.0.80 (should be live 1 hour from the time of this post), going to run some tests today and hopefully move this version into release tomorrow.
changelog:
Improved the comment navigator to no longer be stuck to the top of the screen
Fixed markdown previews on longer comments
Fixed sorting changes not taking affect on the post lists
Fixed always show comment bar
Fixed the bottom nav drawer on the profile pages
Commenting on a post no longer takes you to a single thread view, instead returns you to where you were
Fixed a bug where comments would be duplicated on loading subsequent pages
If the inbox is empty there is now a button to view the full inbox
1.0.82 Changelog:
Adds text colour customization
Improvements to image preloading and adding setting to control it
Thank you for diving into this. I suspect it's how they're generating the thumbnail as well. Until it changes upstream I've increased the thumbnail size so it gets downscaled locally and is a bit more clear. Not the best solution but better than un-readable thumbnails.
Yeah I think something is still messed up too. It gets into the messed up state on Connect when it makes an API call with what it thinks is a valid authorization token but it gets back a "signed out" result. Things should be a bit better on the latest beta version for what it's worth (although API issues are beyond what Connect can do).
As others have said this is fixed with signing out and back in. Connect didn't have good handling for this case, where you're signed in successfully but then the server invalidates the credentials. Will be fixed in the future!
Good idea!