Thank you for your explanation, Thomas.
I use two file repositories, google drive ( drive.google.com ) and blogspot ( blogger.googleusercontent.com ).
Unfortunately they seems to use very long URL addresses nowadays, longer than older stored files in their repos.
I will try your suggestion an use tiny url mapping.
Thank you.
The sounds like a good work-around. Based on that thread, I don’t know if anything has been changed. (Last link also results in page not found.)
(02-22-2024 04:20 PM)Dave Hicks Wrote: [ -> ]The sounds like a good work-around. Based on that thread, I don’t know if anything has been changed. (Last link also results in page not found.)
Hi David, Thanks for your input.
That link seems to be also "broken" by the hpmuseum system, as it is inserting those same hidden chars ( "%E2%80%8B" ) at the end of its maximum columns per row. In my string, this happens at char "o" in the substring ("...RAK44rb6o" ).
If you copy my original string into the Google browser (that is the one I use to test), it will expose those hidden chars. By manually removing them, the access to the image file will work.
Other way to detect it is to copy that string into a text editor like Notepad or Notepad++, where it will take two righ-arrow key presses to move from the position "o" in the substring "..44rb6ofC.." to the next adjacent char "f", indicating that there is hidden chars there.
Oh sorry, I was referring to the link at the end of the thread in the mybb forum that Thomas linked to.
(02-22-2024 08:00 PM)Dave Hicks Wrote: [ -> ]Oh sorry, I was referring to the link at the end of the thread in the mybb forum that Thomas linked to.
A good illustration of how links expire! It's one difficulty with URL-shorteners. Ideally create a backup on an archive site, which has a better chance of persistence.
In this particular case
Bug #409 Problem with links (filed in 2009, closed/rejected same year)