Remarkably, apparently either the server or the client replace backslashes in Markdown links with forward slashes, which is completely bogus and nonsensical.
This might be true perhaps; but the crux of the matter is that I shouldn’t do more than the traditional human-oriented escaping of the addresses, which relies extensively on plain and friendly backslashes, instead of devilish and time-consuming machine-produced percent-codes.
Browsers would only escape parentheses in the address bar using the percent method until some time in the 2010s so many web users don’t remember it. I agree that there should be an easier way for the writer but at least with a working hyperlink (which can currently only be made with %28 and %29), the experience is smooth for the reader.
Maybe a bot can be made to detect these errors on Lemmy? Another pitfall with Wikipedia links is the m. in mobile URLs that does not redirect to the desktop version (as opposed to the other way around) - a Reddit bot existed for this - so perhaps one can be made with both functions.
Huh, must be a recent development. They also seem to use cookies because clicking “Mobile” or “Desktop” (very last link on each page) has a lasting effect but they’ve been for a long time.
Remarkably, apparently either the server or the client replace backslashes in Markdown links with forward slashes, which is completely bogus and nonsensical.
The correct link is https://en.wikipedia.org/wiki/Racetrack_(game)
Also interesting that you’re the first person to raise this issue after two hours and ten upvotes.
It had a link to search for “racetrack (game)” that then went to the actual article. Seemed weird but I got there and assume others did
You can still make a hyperlink by escaping
()as%28%29.[Racetrack (game)](https://en.wikipedia.org/wiki/Racetrack_%28game%29)Racetrack (game)
This might be true perhaps; but the crux of the matter is that I shouldn’t do more than the traditional human-oriented escaping of the addresses, which relies extensively on plain and friendly backslashes, instead of devilish and time-consuming machine-produced percent-codes.
Browsers would only escape parentheses in the address bar using the percent method until some time in the 2010s so many web users don’t remember it. I agree that there should be an easier way for the writer but at least with a working hyperlink (which can currently only be made with
%28and%29), the experience is smooth for the reader.Maybe a bot can be made to detect these errors on Lemmy? Another pitfall with Wikipedia links is the
m.in mobile URLs that does not redirect to the desktop version (as opposed to the other way around) - a Reddit bot existed for this - so perhaps one can be made with both functions.I’m happy to report that Wikipedia seems to have dropped the ‘m.’ prefix, and finally detects the device capabilities instead.
Huh, must be a recent development. They also seem to use cookies because clicking “Mobile” or “Desktop” (very last link on each page) has a lasting effect but they’ve been for a long time.
Sweet, that was racing fast