your link shows a \ before each underscore in the visible text for me in both comments, like this https://lemmy.kya.moe/imgproxy?src=en.wikipedia.org%2fwiki/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.
Perhaps this would not happen if you insist on linking the image like this. Sure, it takes a little bit, but since the rendering of the underscores is put after including them in a hyperlink, I suspect going the extra mile makes it more reliable.
Either way, on web (Firefox in Windows 10), the fixed link works as desired, while the original is borked. And the hyperlink behind text one… Well, you’ll see.
I lived in Hawai’i for three years and remember blue stop signs, but not green. Green road signs in Hawai’i would fail to stand out for 3/4 of the year and defeat their purpose.
It could possibly be a stop sign from Ko Olina on O’ahu, but I never spent enough time there to actually absorb the color of their road signs.
Also, for those wondering about the inevitable followup question, a stop sign has to be placed by a local or state government to be enforceable, and is required to follow the exact standard specifications. Tickets have been thrown out due to stop signs being a slightly wrong shade of red, so blue or green are definitely out.
If it’s private property it could be anything. Maybe it’s a golf course or something plant related. Maybe it’s somewhere plant or tree related. Maybe it’s just camouflage to keep the visual noise down.
According to wikkipedia:
Blue and green stop signs are sometimes used on private property in Hawaii.
But they only have a picture of a blue one and not a green.
https://lemmy.kya.moe/imgproxy?src=en.wikipedia.org%2fwiki/File:Blue\_stop\_sign\_-\_hawaii\_-\_oct\_2015.jpg
So my guess is photoshop.
Fixed link: https://lemmy.kya.moe/imgproxy?src=en.wikipedia.org%2fwiki/File:Blue_stop_sign_-_hawaii_-_oct_2015.jpg
How did you get those back slashes there? I thought it was only happening in reddit.
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://lemmy.kya.moe/imgproxy?src=en.wikipedia.org%2fwiki/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://lemmy.kya.moe/imgproxy?src=en.wikipedia.org%2fwiki/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://lemmy.kya.moe/imgproxy?src=files.catbox.moe%2fg9ulrf.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.
Your fixed link is broken for me on Jerboa
Perhaps this would not happen if you insist on linking the image like this. Sure, it takes a little bit, but since the rendering of the underscores is put after including them in a hyperlink, I suspect going the extra mile makes it more reliable.
Either way, on web (Firefox in Windows 10), the fixed link works as desired, while the original is borked. And the hyperlink behind text one… Well, you’ll see.
On sync, his fixed one was fixed and the first one was broken
deleted by creator
I lived in Hawai’i for three years and remember blue stop signs, but not green. Green road signs in Hawai’i would fail to stand out for 3/4 of the year and defeat their purpose.
It could possibly be a stop sign from Ko Olina on O’ahu, but I never spent enough time there to actually absorb the color of their road signs.
Also, for those wondering about the inevitable followup question, a stop sign has to be placed by a local or state government to be enforceable, and is required to follow the exact standard specifications. Tickets have been thrown out due to stop signs being a slightly wrong shade of red, so blue or green are definitely out.
If it’s private property it could be anything. Maybe it’s a golf course or something plant related. Maybe it’s somewhere plant or tree related. Maybe it’s just camouflage to keep the visual noise down.
We have it similarly in Germany but I’m not sure about the colors