For some reason thunder isn't able to open this image for me
this post was submitted on 20 Dec 2025
33 points (97.1% liked)
Thunder App
3847 readers
4 users here now
An open-source, cross-platform Lemmy client for iOS and Android.
This community is intended to discuss features and feature suggestions for Thunder; as well as friendly, respectful talks about Lemmy in general.
Please use the GitHub repository linked below to submit bug reports, so keeping track of them is easier, and make sure to search first if you already can find an issue for your report.
If there are any developers who would like to contribute, feel free to reach out on GitHub!
General Links
Website: Link
GitHub Repository: Link
Matrix Space: Link
Android Releases
IzzyOnDroid: Link
Google Play: Link
iOS Releases
Apple App Store: Link
TestFlight Beta: Link
Related Communities
Nightly Community: Link
founded 2 years ago
MODERATORS
I added the wrong image at first, and had to edit the post. That could be why.
Maybe this will work?
Maybe not. Uploading images seems finnicky for me right now.
EDIT: New issue. I can see the image in this comment in a web browser but not in the app.
Hey, just wanted to let you know that there should be a fix coming soon for this issue with v0.8.2! If the issue still persists afterwards, feel free to create a new GitHub issue.
For some more context, the reason why the image isn't loading properly is because it's using .avif format (instead of the more typical .jpeg or .png) which Thunder did not account for.
Awesome, thanks! ☺️
Voyager can.
Zero for two for Thunder, eh.
There were many small things like this which made me not use Thunder.
They all have tradeoffs and will appeal to different people 🤷🏻♂️ personally the voyager ui is not for me, but I hope it serves you well as a client :)
Yeah the Thunder UI looks better than Voyager's. But when the UI doesn't work. 🤷♂️
Sync is the most beautiful UI out there, but sadly it's abandoned.
I also have this issue on Summit, though the lines don't show up in saved photos. I assumed it was a bug in the image rendering libraries.
Hey there!
Thanks for the report - I'm unable to reproduce this issue locally on my device so it would be great if you could possibly submit a new GitHub issue on this with additional details.