your link shows a \ before each underscore in the visible text for me in both comments, like this https://en.wikipedia.org/wiki/File:Blue\_stop\_sign\_-\_hawaii\_-\_oct\_2015.jpg and hovering or clicking the link replaces that \ with %5C, so the entire thing tries linking to https://en.wikipedia.org/wiki/File:Blue%5C_stop%5C_sign%5C_-%5C_hawaii%5C_-%5C_oct%5C_2015.jpg. clicking 'source' on those comments shows just the \ before each underscore
no idea what's causing it, super weird to have the same bug messing with links that reddit does
The underscore is used to underline text in Markdown. If you want to display a real underscore like this: _, you have to escape it with a backslash. Some clients apparently interpret this rule even in plain links, and some don't. If we use real Markdown links this should not happen.
As you put it, the web version renders & includes the backslashes, causing your link to break on lemmy.world, running the website itself in Firefox on Windows 10.
Your fixed link and mine look exactly the same here on kbin. Both link to the image correctly.
So I'm not sure where the error lies.
Kbin does not like to link to URLs that end in a filename.
EG: https://en.wikipedia.org/wiki/File:Blue\_stop\_sign\_-\_hawaii\_-\_oct\_2015.jpg
It ignores the link text [Blue Stop Sign] completely and just posts the link.
your link shows a \ before each underscore in the visible text for me in both comments, like this
https://en.wikipedia.org/wiki/File:Blue\_stop\_sign\_-\_hawaii\_-\_oct\_2015.jpgand hovering or clicking the link replaces that \ with %5C, so the entire thing tries linking tohttps://en.wikipedia.org/wiki/File:Blue%5C_stop%5C_sign%5C_-%5C_hawaii%5C_-%5C_oct%5C_2015.jpg. clicking 'source' on those comments shows just the \ before each underscoreno idea what's causing it, super weird to have the same bug messing with links that reddit does
The underscore is used to underline text in Markdown. If you want to display a real underscore like this: _, you have to escape it with a backslash. Some clients apparently interpret this rule even in plain links, and some don't. If we use real Markdown links this should not happen.
https://files.catbox.moe/g9ulrf.jpg
It's likely a kbin bug (or an app if you used one to make the comment), since the slashes are there even on the website directly.
As you put it, the web version renders & includes the backslashes, causing your link to break on lemmy.world, running the website itself in Firefox on Windows 10.