I just realized something that’s completely fucked up.
$ curl -qssL https://twtxt.net/ | grep -E 'In-reply-to' | head
<a href="https://twtxt.net/conv/2tjsjuq?p=1#rlsxhsq" title="Show conversation for #2tjsjuq">In-reply-to</a>
<a href="https://twtxt.net/conv/bghmkra?p=1#dfnrbyq" title="Show conversation for #bghmkra">In-reply-to</a>
<a href="https://twtxt.net/conv/e24exeq?p=1#itft6wa" title="Show conversation for #e24exeq">In-reply-to</a>
For some reason the latest version of Chrome is stripped #fragment
(s) from the HTML body being served.
da fuq?! When did this change, in what version? Did we (W3C and the community) agree that this behavior should change?! 😱 Fark’n hell Google™ Chrome 🤬
@prologic Huh? What does that look like in Chrome? 🤔 (I only have Chromium.)
@movq@www.uninformativ.de It appears to strip the #fragment
🤦♂️
@prologic Strip it from what? From requests being sent to the server? That’s always been the case, afaik. 🤔
@movq@www.uninformativ.de No it’s stripping it from the DOM. The server is sending a document with fragments in the URI(s) of links that are ‘Inreply-to” links (for context). Chrome is stripping them!
Or maybe someone added some janky javascript into the codebase I can’t find 🤔
@prologic From the DOM? That can’t be right. 😳😳😳
@movq@www.uninformativ.de I know right 😅 This can’t be true, I must be over reacting and something else is fucked up with some code somewhere 🤣
I think I found the bug 🐛