by "TheHondaBro" (wwaveform)
Published 02/01/2017 at 11:28
No Tags
STARS: 4
Or is it really just stumped by basic punctuation?
"jasmits" (jasmits)
02/01/2017 at 11:30, STARS: 3
It had one a long time ago and never fully recovered
"WilliamsSW" (williamssw)
02/01/2017 at 11:33, STARS: 1
Why can’t it be both?
"Wacko" (wacko--)
02/01/2017 at 11:34, STARS: 2
no it’s a Birth defect
"E90M3" (e90m3)
02/01/2017 at 11:34, STARS: 1
It’s the HTML code for a single quote aka an apostrophe.
"RamblinRover Luxury-Yacht" (ramblininexile)
02/01/2017 at 11:34, STARS: 3
It has a malignant growth in its percent-encoding center - it’s pressing on a blood vessel.
"Matt Nichelson" (whoismatt)
02/01/2017 at 11:46, STARS: 1
Haha I broke Kinja.
"Urambo Tauro" (urambotauro)
02/01/2017 at 11:46, STARS: 1
Huh. I guess it depends on the character: ( link )
"Blunion05 drives a pink S2000 (USER WAS BANNED FOR THIS POST)" (6speedhaven)
02/01/2017 at 12:10, STARS: 2
I didn't ever find out why that happens like that but it's possible it has something to do with the way punctuation characters might be stored?
"RamblinRover Luxury-Yacht" (ramblininexile)
02/01/2017 at 12:53, STARS: 2
The funny character substitutions are the way that punctuation is modified to fit in a URL. A URL can’t have apostrophes in it. What is supposed to happen is that a website either percent-encodes things for making a link or deletes naughty characters, and just stores a string for the title of the post somewhere. What has happened here is that Kinja is taking the title of a post sometimes randomly and running it through percent-encoding. That... isn’t supposed to happen. Something is *very* wrong for it to be doing that.