Hey everyone, its been a while but it's finally time for another Thunder release. As always, there have been many improvements, additions, changes and fixes in this release which should make for a ...
Hey everyone, its been a while but it's finally time for another Thunder release. As always, there have been many improvements, additions, changes and fixes in this release which should make for a even better Thunder experience. If you have any suggestions or feedback, feel free to discuss it in the Thunder community or on GitHub.
A quick reminder: if you are using the Google Play version or App Store version, please note that it may take a bit of time before you receive the update. Now onto the update notes. This update brings a few major features:
đ New Features
Instance and community modlogs are now available in Thunder. To access the instance modlog, tap on the triple dot button located on the top app bar and select "Modlog" when viewing general feeds (Subscribed/Local/All). To access a community modlog, navigate to the given community and find "Modlog" in the extended actions.
Mod reports are now available to view and resolve within Thunder via the drawer. If you are a moderator or admin of a community/instance, you should see a new "Reports" option under the general feeds. Only post and comment reports are available at this time. Private message reports will come in a future update.
The user feed has been fully re-worked to provide a better experience similar to the general/community feeds. This means that you can now change the sorting when viewing a user feed, and use the FAB for additional actions.
An instance explorer has been added into the Search page. This allows you to explore communities, posts and comments for the current instance.
Thunder now has an in-app changelog for updates. It is turned on by default, but can be toggled off in the settings. This changelog should help you keep track of what additions, changes, and fixes have been added in upcoming versions.
âš General
Improvements to markdown rendering. Spoiler markdown detection has been improved, and there is now initial/experimental support for subscript and superscript markdown tags. Markdown quick actions when creating posts/comments will be added in the near future.
You can now customize the user/community name format and style across Thunder! This is accessible through Settings -> Appearance -> Theming. You can adjust the font weight, colour, and format for both user and community names.
Improved UI/UX for long press actions, and additional customization options including customizable feed dividers and navigation bar labels.
And much much more. I can't go through all the changes in the changelog, but for those who are curious, feel free to check out the full changelog below.
I would just like to thank everyone for the continued support and contributions. Thunder is still a project that I can only work on the side, and knowing that others enjoy it drives me to continue working on it!
Any chance that gestures become with haptic feedback
I believe there is already haptic feedback for the gesture actions (upvote/downvote/save/mark as read/reply). If you don't have them, double check and see if your system settings has vibrations enabled! If that doesn't work, I would suggest opening up a new issue on GitHub with more details so that we can reproduce the issue.
also to be able to change their colors, eg red for downvote green for upvote
I don't believe this has been requested before. Please open a new issue on GitHub for this so that we can better track it đ
Hmm, unfortunately I donât have an Android device to test with so I wonât be able to reproduce the issue on my end. Iâll ping @[email protected] to see if he can reproduce this!
I'm afraid I'm a bit far from this GitHub area so cannot help with opening up an issue
Thatâs alright! Iâve created it for you here. Let me know if the description matches what you were expecting!
It might be a device/version dependent issue - perhaps related to permissions
Could you let me know what device and Android version youâre currently using? Also, could you double check that vibrations permissions are enabled for Thunder? Thanks!
Hey, just chiming in here to say that I do get haptic feedback on my physical device (Pixel 8 Pro) when using swipe gestures on both posts and comments.
Make sure this setting "Touch feedback" is turned up.
If you're still having issues, you're welcome to open a GitHub issue (or ask someone here to do it for you), but it will likely be hard for us to investigate if we can't reproduce. :-(
Hi thanks for your input. I too get haptic feedback when turning on the touch feedback (which in my case I have it turned off) but I get haptic feedback at every touch gesture whenever I use the phone and not only in Thunder.
On the other hand while I have touch feedback off, I do get haptic feedback in Voyager app. So the app needs to trigger the haptic feedback.
That's great, I'm glad to hear the haptic feedback in Thunder works when the system setting is turned on.
To be honest, it feels like the right behavior for Thunder to respect the system setting. I personally keep "Touch feedback" turned down, because I do not like haptic feedback, and I'm glad Thunder and other apps respect that. I tried Voyager, and you're right, it seems to override that setting, which doesn't seem like a good thing to do. :)
Let me know your thoughts, and whether it's an acceptable solution that users will need to enable haptics in system settings in order for it to work in Thunder. Thanks!
Thanks for your time replying. Personally I keep system's haptic feedback turned off since I fin it annoying for every action I do to get it.
I prefer the way Voyager has it eg for confirmation when replying, voting etc. But as I say, it's my personal preference. đ
I'm glad we found the root cause of the issue. I'd also like to chime in here to say that I think it makes the most sense for Thunder to respect the system settings. I know that I would also get frustrated if it were the opposite. For example, if I had system haptics off but an app was not respecting the system settings.
@[email protected]
This may be a dumb question, but are there per app settings that can be set to turn on/off haptics? If so, this may be the best course of action to take!
In Voyager there is a setting to turn on-off haptic feedback. So in my case the device-system haptic is off but I get feedback when I turn on the setting in Voyager. Hope I'm clear what I mean...đ