

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.)
deleted by creator
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
Yeah, that seems odd. If you go to the web UI, does it show you’re subscribed to that community? I’m trying to see if the subscription issue is Lemmy-related or Thunder-related 🙃
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!
Huh. I did that in my recording!
Oops, I didn’t see that part 😅 That’s definitely weird then, I’m not able to reproduce the problem on my end. My best guess is that there’s maybe an error that’s causing this to not work (e.g., maybe a clash when it tries to save that community with another already saved community)
I can add in more error messages in the next nightly build to get a better understanding of what the underlying issue is!
A last ditch resort that you can try (totally up to you of course) is to reset the local database Thunder Setting: Debug > Reset Preferences and Data > Delete Local Database. Doing this will remove any logged in accounts that you have and also other app-only data with the exception of preferences (e.g., favourites, existing drafts).
Thanks for the video! I completely forgot you could favourite a community from the overflow menu there 😅
I just tried it from the overflow menu and was able to get it to work, although there seems to be another bug where the state doesn’t update until you refresh the community.
Can you try this to see if it works?
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 😅
Hey! I just tried it myself and it looks favouriting does work, but there’s an issue where it takes a few seconds to apply.
Can you try favouriting the community and waiting a few seconds to see if it updates properly? I’ll try to apply a fix for this in the next nightly!
Edit: Created a PR to fix this issue: https://github.com/thunder-app/thunder/pull/1802
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!
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 😅