Thank you for the detailed response and for the additional information! As you mentioned and have likely seen, it’s been difficult for me to properly reproduce this issue on my end (given that I don’t have access to a physical Android device, and it seems to be working as expected on iOS devices)

I have just released a nightly build of Thunder v0.6.0-1 that might have a potential fix for the issue but I’ll have to confirm with others to see if the potential fix actually resolves the issue. If you are okay with running a nightly (and perhaps less stable build) of Thunder to test it, that would be greatly appreciated!

Side note: If you do plan to run the nightly build and are worried about losing your settings/information, you can always export the setting/database configuration and re-import it when you install a fresh version. This can be found under Settings -> General -> Import/Export Settings

Edit: This is the link to the nightly version: https://lemmy.world/post/21791907

Thanks for highlighting that feature, and I’m glad you find it useful! It’s a super simple addition, but one that adds some value to know how active a specific user has been.

If you do have any additional statistics you would like to see, feel free to create a feature request for it on our GitHub.

As a sidenote, I’m a bit concerned about your battery there 😰

Though it still lacks the mod actions

Are you referring to mod actions for comments? If so, that is something I’ll be working on next!

and reports don’t have the name of the reporter.

For this, it would be good if you could submit a new feature request on GitHub to make it easier to track.

Thanks! Keep up the great work on Tesseract

This is being worked on for Thunder. It’s currently in draft stages but should hopefully land soon to a nightly build!

If you’d like to see it in action, or provide any feedback on it while it’s being worked on, feel free to check out the corresponding pull request: https://github.com/thunder-app/thunder/pull/1156

I hope that solved your issue!

The next nightly version will also change the label from “Hide” to “Blur” to make it clearer: https://github.com/thunder-app/thunder/pull/1158

Hey there, I just came across this so I wanted to check out what the issue is (and maybe resolve it)!

I believe there are two options - one is to hide NSFW posts (General -> Feed), and the other one is to blur the NSFW posts (Appearance -> Posts -> General Settings).

I think there is one issue where if you have NSFW posts hidden, and the feed is mostly NSFW posts, then the feed will infinitely load because it tries to fetch posts without NSFW tags. Double check and see if this might be the issue. If not, then feel free to open a new issue on GitHub with more information and I can take a look at it

it should be “blur” posts, not hide!

I agree with you here - I’ll change it to blur!

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!

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!