

Hey!
Thanks for reporting this. Could you also make a GitHub issue on this with some reproducible steps so that I can troubleshoot it? (e.g., the instance you’re on, the link you tap on that causes the issue, etc.)
Hey!
Thanks for reporting this. Could you also make a GitHub issue on this with some reproducible steps so that I can troubleshoot it? (e.g., the instance you’re on, the link you tap on that causes the issue, etc.)
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!
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!
Hey there, fellow Flutter dev! 👋
Thanks for tagging me in this and bringing this to my attention! I’ll take a look at this issue on my end as well and apply some fixes to it.
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!
Thanks for checking this!
If possible, I would suggest creating a new GitHub issue with some more details on the bug (e.g., instance, version, reproducible steps, etc.) This helps us better keep track of all the issues/feature requests so they don’t get lost.
user avatar is hidden for all accounts that don’t have a custom profile picture set, but shown for those who do have one
I would also suggest creating a feature request for this on our GitHub!
Hmm, that’s not expected. This should only happen for users who don’t have a profile picture. Are you noticing this for all users?
In the example picture, neither of us actually have a profile picture, so it defaults to the first letter!
Hey there, thanks for the report!
If you are able to submit a new GitHub issue for this, that would be helpful as it allows us to keep track of these easier.
Hey there, thanks for the report!
If you are able to submit a new GitHub issue for this, that would be helpful as it allows us to keep track of these easier.
Hey again! Thanks for the report - it would be helpful if you could submit this as an issue on GitHub so that we can track it better.
While I do try to keep track of issues and feature requests submitted here, it often gets lost if there’s no associated GitHub issue 😅
Hey there, thanks for the report!
This is a known issue and has been fixed (but not yet released) See here: https://github.com/thunder-app/thunder/pull/1738
Hey!
If you’re specifically talking about marking private messages as read, you’ll have to use the latest nightly build (v0.7.0-1) in order to do it as it was just added recently.
If you’re running v0.6.1, it won’t be possible to mark an individual message as read unfortunately 😅