this post was submitted on 28 Sep 2024
17 points (100.0% liked)

Thunder App

2814 readers
19 users here now

An open-source, cross-platform Lemmy client for iOS and Android.

This community is intended to discuss features and feature suggestions for Thunder; as well as friendly, respectful talks about Lemmy in general.

Please use the GitHub repository linked below to submit bug reports, so keeping track of them is easier, and make sure to search first if you already can find an issue for your report.

If there are any developers who would like to contribute, feel free to reach out on GitHub!

General Links
Website: Link
GitHub Repository: Link
Matrix Space: Link

Android Releases
IzzyOnDroid: Link
Google Play: Link

iOS Releases
Apple App Store: Link
TestFlight Beta: Link

Related Communities
Nightly Community: Link

founded 1 year ago
MODERATORS
 

The image link in question:

Screenshot of web UI of this post:

top 2 comments
sorted by: hot top controversial new old
[โ€“] SatyrSack@feddit.org 8 points 1 month ago

It works fine if you replace all the non-ASCII characters. Still a bug, but knowing this may help find a way to fix it.

![](https://upload.wikimedia.org/wikipedia/commons/4/44/Tra%C5%A5_u_osady_Luh_%28u_Bezpr%C3%A1v%C3%AD%29_1.jpg)

[โ€“] darklightxi@lemmy.world 5 points 1 month ago

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)