Just a quick update - v0.7.2 should now be released which fixes this issue! Please let me know if you’re still encountering issues with this.

Just a quick update on this - I’ve released v0.7.2 which should improve this issue! Please let me know if you’re still seeing cases where information is pushed off the screen.

Thanks for the video! I think I understand the issue better now and should be able to reproduce it. I’ll keep you updated when the fix rolls out.

Hey there!

Could you open up a new GitHub issue on this and provide some more details/screenshots on the issue? Thanks!

Hey there!

Thanks for bringing this up. I do have plans to support PieFed in the future - I can’t promise when it will happen, but I’m working on laying down the groundwork to better support other APIs (whether it be Lemmy, PieFed, or possibly another platform that shows up in the future).

Doing this will take some time though, as Thunder’s internal logic was (and is currently still) heavily tied to Lemmy’s APIs. The good news is that the upcoming v0.7.0 release will bring us a step closer to this goal. My (optimistic) goal is to have basic support for PieFed and the upcoming Lemmy v1.0 API by the end of the year.

Thanks for the feedback! Could you mention more about your thoughts on the new sidebar/about button on this GitHub issue? https://github.com/thunder-app/thunder/issues/1856

Having this feedback will help me improve the feature further!

Thanks for the feedback! I would appreciate it if you could provide some more thoughts about the new layout in this GitHub issue: https://github.com/thunder-app/thunder/issues/1856

Having a better understanding on the things you like/dislike will allow me to incorporate that feedback and improve the feature 😄

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 😅

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

• Thunder is developed using Flutter which allows for cross platform compatibility (iOS and Android at the moment)
• We have Weblate for translations, if you’d like to help localize Thunder into other languages
• If you don’t know where to start, feel free to look through our existing issues on GitHub or join our Matrix space. I’ll gladly answer any questions you have regarding our codebase!

Done! This should land in the next nightly build

https://github.com/thunder-app/thunder/pull/1808

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).