Hey there!
Could you tell me what version of Thunder you’re using and the instance you’re using? Additionally, does this happen to all images or only a few images on the feed?
If it only happens to a few images on the feed, I would try to increase the time Thunder tries to determine the image dimension size. Here is a quick link to that setting: Thunder Setting: Debug > Feed > Image Dimension Timeout
Is there a way to finally contribute? I’ve got minimal coding expertise but would like to contribute in some way.
Of course! We’re always looking for contributors to help with Thunder regardless of level of experience.
Here’s some general information about Thunder
Done! This should land in the next nightly build
I believe this is expected behaviour! The comment itself was made from a different instance, but the original post was posted in the lemmy.world community.
Glad you figured out the issue!
I’ll take a note here and see if there’s a way to add some notification when this type of situation happens 😅
Does it work if you try to visit the comment from your instance? For example, this is the same comment but on lemmy.world: https://lemmy.world/comment/16079890
Hey! I just tried it myself as well on v0.7.0-1 and it seemed to have worked (navigated to the post and showed comments)
Incidentally, after submitting this post, I tapped the eyeball to view it and nothing happened.
This is a known issue and was fixed recently (but not yet released) See https://github.com/thunder-app/thunder/pull/1797!
Thank you! I’ll definitely try to sprinkle a bit of new features here and there when I can, but the majority of my time will be spent on improving the core app stability and performance 😅
Thanks for the feedback!
I do agree that it feels like there’s wasted space when in landscape mode. It would be helpful if you could also create a GitHub issue on this so that we can better track the issue!
Hey there, thanks for the kind words!
You’re right - at this time, there’s no way to create or reply to private messages just yet. This is something I want to introduce but I’m just currently backed up with other (not as fun but arguably more important) tasks like preparing Thunder for the upcoming Lemmy API changes and app stability/performance improvements 😅
Given that this has been requested a few times already, I might be able to implement a quick version of this just to have it as an option!
Hey there!
The good news is that there’s no outstanding issues or technical limitations preventing this feature from bring implemented!
The main thing is allocating time to implement this in. I’m currently backed up working on some under-the-hood changes for the next version of Lemmy. Once that’s done, I’ll have more time to work on the existing feature requests.
Hey! Sorry for the delay in response. It would be helpful if you could create a new GitHub issue on this so that we can track it better.
This happens since about three or four Thunder updates have passed. Before that it worked fine.
Have you tried clearing app data/cache for Thunder? That might help “reset” things and might resolve the issues you’re facing.
Hey there!
This issue was noted and is already fixed in a nightly TestFlight build. See this GitHub issue for more details.
If you’re not on the TestFlight build, there is still a workaround for this issue by setting Thunder to portrait mode temporarily. Doing this should bring back the back button on the top left!