Thanks again for all the updates!

In that sense we would like to know from developers of Lemmy clients and frontends if their projects are ready for 0.19, as we are planning to release it within the next weeks.

Thunder is ready to go!

Thanks for the question - this is a feature that is currently being worked on and should hopefully be available in the next general release for any lemmy instances running 0.19.0 and above. The main delay here was waiting for lemmy to natively support blocking instances.

If you’d like to keep track of the on-going progress for this feature (and general support for lemmy 0.19.x), see this GitHub issue!

Hey there! Comment navigation should be available on the latest general releases on Google Play and App Store (it was introduced in a previous version v0.2.2+15). It could be possible that you had that option disabled (Settings -> General -> Comments -> “Enable Comment Navigation Buttons”)

The releases on GitHub contain the latest nightly builds of Thunder, which are updated more frequently but are more prone to bugs since they are more “experimental” in nature. I hope this clarifies some of the questions!

Working on this project is all about learning (at least for me), so I like to explore different avenues for creating something without necessarily copying another existing app. Rather, I’d like to think that Thunder combines some of the cool and interesting features scattered across all the other apps into one place.

I’ve personally used Apollo, so you’ll see some hints of Apollo’s UI even here (swipe gestures is one of them) 😅 If you have some feature or idea that would be nice to have in Thunder, you’re always free to open up a new issue on GitHub!

Hey there! As others have already mentioned, options to vote, save and reply to comments using the long-press menu are currently available in the nightly builds and will eventually come to the general builds.

If you are not on the nightly build, you can also enable comment action buttons which will allow you to reply to comments without the use of swipe gestures. To enable this, go to Settings -> General -> Comments and find “Show Comment Button Actions”. Let me know if you need any more help or have any further questions!

Hey there! Could you provide some more information on this? It would be appreciated if you could create a new GitHub issue on this and add some more details about what you’re experiencing (e.g., long time for searches to appear, profile posts taking too long to load, how frequently you encounter this issue, etc.)

We can then use that information to further track down the issue and potentially resolve it!

I don’t think this was mentioned yet in a GitHub issue but feel free to create one for this! It would be good if you could also provide some ideas on where to place this and how it should look like. Thanks!

Hey there! We do have a existing GitHub issue on this but we haven’t been able to get around to it just yet due to other priorities. If you would like this issue to be prioritized, feel free to give the issue a thumbs up so that we know!

Here’s the GitHub issue. Let me know if you have any other questions!

Hey there! There should be a setting which enables this function. The setting is under Feed in Settings -> General and is called “Mark Read After Viewing Media”

Let me know if you can’t find that option or if you have any other questions!

Thanks for the kind words, we really appreciate them!

We’re still hard at work to make even more improvements to Thunder as a whole, with a greater focus now on improving general performance and stability of the app. Thunder is still a project that all of us contributors (including me) work on during our spare time, so its nice to hear that others are using and enjoying Thunder 😄

I believe Jerboa also has this character limit as mentioned in this PR. It seems like they truncate the password to take the first 60 characters if it’s too long. This is what Thunder also follows as of right now, except it’s shown explicitly to the user in the login modal

I think that check must be bypassed for admin passwords, or it was instituted after I created programming.dev

That could be a possibility - we can do some tests to verify if that’s the case. I found this related issue which might indicate that all auth flows through the same logic.

Even if that was the limit, it still should be enforced by the backend on login, not on the frontend

Unfortunately, that might not be the case. Dessalines mentioned in this comment that the backend doesn’t truncate overly long passwords, and throws an error instead. Although, as you mentioned, this might be bypassed for admin users.

Either way, I think we can take a deeper look at this and verify this information! Feel free to create a new issue for this on GitHub if you’re able to so that we can track this issue better.

Hey there, like others have mentioned, I think this is a limitation on lemmy’s end which limits the password length up to 60 characters.

This is the source code for lemmy’s backend if you’re curious. If you think this is not the case, feel free to create a new issue on GitHub and we can take a further look into this! Let me know if you need any more clarification :D

I can go ahead and talk about Flutter as that’s what I’m familiar with (from my limited experience).

For some context, I’m the main maintainer for Thunder, which is built purely with Flutter/Dart. I can also only speak on behalf of iOS/Android as we’re only focusing on targeting those platforms at this time.

There will undoubtedly always be some compromises when using Flutter as compared to their native counterparts. However, if your app only ever deals with handling UI and logic that is platform agnostic, then I would say that Flutter is fairly good. It makes it really easy to support both platforms and removes the need to re-write logic for each supported platform. This means you can get everything to behave pretty much the same regardless of the platform.

The moment your app needs to tie into platform specific features, it’s a mixed bag. You can either find packages that suit your needs, or write your own logic to bridge that gap. When trying to find packages, you often need to check if it supports the platforms you’re supporting as not all of them will. You also have to see how well maintained they are since most packages are from third parties and not from the Flutter team themselves. I haven’t dealt with having to write custom logic to tie into platform specific features so I can’t comment too much on that.

Hope this helps!

Thanks for the feedback!

One bit of feedback on it though is that the “spring” animation (I can’t remember the proper name for it) when reaching the top and bottom of a page still persists and is a little jarring, so being able to remove that would be welcome too!

Did you mean the overscrolling effects which stretch out the text when you reach the top/bottom? Or did you mean a different effect? It would be helpful if you could create a GitHub issue on this and provide some images/videos to show exactly what you mean!

Hey there! Instance blocking is something that I do want to introduce into the app, but the main blocker at the moment is waiting for lemmy to support it natively. Having lemmy officially support instance blocking will make things run much smoother than us trying to hack a way to do it within the app.

Fortunately, it seems like lemmy is working on that feature, and it should hopefully come soon! This is the related link to the lemmy issue: https://github.com/LemmyNet/lemmy/pull/3869

If you’d like to track this issue (for Thunder) on GitHub, here is the link: https://github.com/thunder-app/thunder/issues/701

Hey there, thanks for the feedback! I use iOS personally, so I try to ensure that the experience on there works well and is fluent :D

As MentalEdge mentioned, there is still on-going development on Thunder (not specific to the image viewer, but on other parts of the app). To help keep track of these suggestions, feel free to create new issues on GitHub. This will help us organize the feedback and be able to prioritize properly. If you’re not sure how to do that, let me know and I might be able to make them for you when I have the chance!

Here is the created issue if you would like to keep track of it! https://github.com/thunder-app/thunder/issues/744

Feel free to add in any more information (or correct any assumptions that I have made)

Ahh, no worries! I can do it then

Just an update, here is the PR which should resolve this issue: https://github.com/thunder-app/thunder/pull/743