darklightxi
Thanks for the report, this is definitely a weird one. I’ve created a PR with a fix for this issue here: https://github.com/thunder-app/thunder/pull/1572!
For some additional context: Thunder automatically performs encoding on URLs. However, in this specific scenario, the URL was partially encoded (the brackets were encoded, but the non-ASCII characters were left behind). This partial encoding caused Thunder to incorrectly encode the already encoded brackets (%28 and %29)
Hey! Sorry for the delay in response. It would be helpful if you could create a new GitHub issue on this so that we can track it better.
This happens since about three or four Thunder updates have passed. Before that it worked fine.
Have you tried clearing app data/cache for Thunder? That might help “reset” things and might resolve the issues you’re facing.
Hey! Thanks for reporting this and sorry for the delay in response.
Unfortunately, its quite difficult to implement local-only notifications because of how restricitve Android is with regards to background tasks. The notifications feature is heavily dependent on the specific OS version that you have (different manufacturers do different things to help with power saving, but as a result, breaks/restricts background tasks from running)
The only thing I can suggest is to turn off battery optimizations for Thunder. After that, disable and re-enable notifications in the settings. If you go to Settings -> Debug, you should also see an option to test out notifications to see if Thunder can trigger them.
If none of that works, please let me know (ideally on Matrix) and I can help troubleshoot further!
Thanks for mentioning this, there will be a fix out for this shortly! This is the related PR: https://github.com/thunder-app/thunder/pull/1536
Just circling back to this - there was a potential fix for this issue in this PR: https://github.com/thunder-app/thunder/pull/1524
This potential fix was released in v0.5.0 of Thunder. If possible, please let me know if you’re still encountering this issue on the latest version. Thanks!
I know this was posted a while ago, but I do have an update on this issue. This bug was only affecting instances running on 0.19.4 and higher that had image proxying enabled (e.g., lemm.ee)
Fortunately, this issue should now be resolved with v0.5.0 of Thunder! If you’re interested in the details, check out the following GitHub discussion: https://github.com/thunder-app/thunder/issues/1448
Just providing a quick update on this - v0.5.0 fixes one of the two issues mentioned in the markdown report (table alignment not being respected)
The other markdown issue is not yet released, but should be fairly easy to fix! (just need to take some time to make sure the fix doesn’t break anything else). If all looks good there, then this fix will be released as part of a nightly build soon!
