# I am the Watcher. I am your guide through this vast new twtiverse.
# 
# Usage:
#     https://watcher.sour.is/api/plain/users              View list of users and latest twt date.
#     https://watcher.sour.is/api/plain/twt                View all twts.
#     https://watcher.sour.is/api/plain/mentions?uri=:uri  View all mentions for uri.
#     https://watcher.sour.is/api/plain/conv/:hash         View all twts for a conversation subject.
# 
# Options:
#     uri     Filter to show a specific users twts.
#     offset  Start index for quey.
#     limit   Count of items to return (going back in time).
# 
# twt range = 1 25
# self = https://watcher.sour.is/conv/7gwktxq
prologic
twtxt.net
View Thread
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
twtxt.net
View Thread
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 🤬
movq
www.uninformativ.de
View Thread
@prologic Huh? What does that look like in Chrome? 🤔 (I only have Chromium.)
movq
www.uninformativ.de
View Thread
@prologic Huh? What does that look like in Chrome? 🤔 (I only have Chromium.)
movq
www.uninformativ.de
View Thread
@prologic Huh? What does that look like in Chrome? 🤔 (I only have Chromium.)
movq
www.uninformativ.de
View Thread
@prologic Huh? What does that look like in Chrome? 🤔 (I only have Chromium.)
prologic
twtxt.net
View Thread
@movq It appears to strip the #fragment 🤦‍♂️
prologic
twtxt.net
View Thread
@movq It appears to strip the #fragment 🤦‍♂️
prologic
twtxt.net
View Thread
@movq It appears to strip the #rafgment 🤦‍♂️
movq
www.uninformativ.de
View Thread
@prologic Strip it from what? From requests being sent to the server? That’s always been the case, afaik. 🤔
movq
www.uninformativ.de
View Thread
@prologic Strip it from what? From requests being sent to the server? That’s always been the case, afaik. 🤔
movq
www.uninformativ.de
View Thread
@prologic Strip it from what? From requests being sent to the server? That’s always been the case, afaik. 🤔
movq
www.uninformativ.de
View Thread
@prologic Strip it from what? From requests being sent to the server? That’s always been the case, afaik. 🤔
prologic
twtxt.net
View Thread
@movq 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!
prologic
twtxt.net
View Thread
@movq 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!
prologic
twtxt.net
View Thread
Or maybe someone added some janky javascript into the codebase I can't find 🤔
prologic
twtxt.net
View Thread
Or maybe someone added some janky javascript into the codebase I can't find 🤔
movq
www.uninformativ.de
View Thread
@prologic From the DOM? That can’t be right. 😳😳😳
movq
www.uninformativ.de
View Thread
@prologic From the DOM? That can’t be right. 😳😳😳
movq
www.uninformativ.de
View Thread
@prologic From the DOM? That can’t be right. 😳😳😳
movq
www.uninformativ.de
View Thread
@prologic From the DOM? That can’t be right. 😳😳😳
prologic
twtxt.net
View Thread
@movq I know right 😅 This can't be true, I must be over reacting and something else is fucked up with some code somewhere 🤣
prologic
twtxt.net
View Thread
@movq I know right 😅 This can't be true, I must be over reacting and something else is fucked up with some code somewhere 🤣
prologic
twtxt.net
View Thread
I _think_ I found the bug 🐛
prologic
twtxt.net
View Thread
I _think_ I found the bug 🐛