twtxt.net), I'm going to be deleting 235 accounts today: https://gist.mills.io/prologic/0381c79977384051bb0b4afc89b4893d
I just dropped another 124 useless accounts 🥳 
@movq@www.uninformativ.de I did indeed edit a Twt just now 🤣 probably from this thread IIRC (typo) 😅
@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 🤣
@prologic From the DOM? That can’t be right. 😳😳😳
@prologic It always fetches the canonical feed URL and, when it can’t find the latest twt hash (that it saw in the previous run) it traverses the archived feeds until it does find it. Something along those lines.
I just got one such notification:
Date: Tue, 07 May 2024 15:56:01 +0200
From: me@pinguin
To: me@pinguin
Subject: [regularly] jenny
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/1 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/2 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/3 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/4 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Fetching archived feed https://twtxt.net/user/prologic/twtxt.txt/5 (configured as prologic, https://twtxt.net/user/prologic/twtxt.txt)
Now, your feed did not get archived, as far as I can tell. So why am I getting this then? Have you edited a twt just now? That would explain it. 😅
Or maybe someone added some janky javascript into the codebase I can’t find 🤔
@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!
@lyse@lyse.isobeef.org Fair enough, I mean I have the same sets of problems too.
@prologic Strip it from what? From requests being sent to the server? That’s always been the case, afaik. 🤔
~/go/bin to your $PATH, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:
@movq@www.uninformativ.de Noice 👌
@movq@www.uninformativ.de Oh, and then it switches to the new active feed? 🤔
@movq@www.uninformativ.de It appears to strip the #fragment 🤦♂️
@prologic Huh? What does that look like in Chrome? 🤔 (I only have Chromium.)
👋 Okay folks, let’s startup the Yarn.social calls again.
Agenda:
Anything we want to talk about. Twtxt, Yarn, self hosting, cool stuff you’ve been working on. chit-chat, whatever 😅
@prologic My client tells me when it fetches archived feeds. That’s all.
~/go/bin to your $PATH, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:
@prologic Ah, yes, that’s better! 👍
~/go/bin to your $PATH, at least I did. I’m not sure what to do about it, though. 🤔 This doesn’t really belong into Yarn’s setup guide and it’s mentioned as one of the first things in the Arch wiki, for example, but still … To newcomers this might look a bit like a broken build process:
@movq@www.uninformativ.de Fixed 👌
yarnd setup look like to anyone? 🤔 Let's say it exists, and it helps you setup a Yarn pod in seconds. What does it do? Of course I'd have to split out yarnd itself into yarnd run to actually run the server/daemon part.
@lyse@lyse.isobeef.org Anyway fixed 👌
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 🤬
yarnd setup look like to anyone? 🤔 Let's say it exists, and it helps you setup a Yarn pod in seconds. What does it do? Of course I'd have to split out yarnd itself into yarnd run to actually run the server/daemon part.
@prologic@twtxt.net Oh, was I? I don’t recall any of that. But who knows. ;-)
@movq@www.uninformativ.de Wut?! 🧐 How do you get notified? 🤔
New at #APA: “If you become a monster, the fight is not worth it”: An interview with Dr. Ba https://blog.apaonline.org/2024/05/07/if-you-become-a-monster-the-fight-is-not-worth-it-an-interview-with-dr-ba/
@prologic@twtxt.net I won’t see any activity again, unless somebody else I follow interacts with them. Yep, fetching the feeds still happens with a patched version of the original twtxt client. tt is just a viewer of the database contents.
(Hmmm, I think I could add the time of the last twt to the output of jenny -l. 🤔 Currently it only shows the last successful retrieval time.)
@prologic Every now and then, I get a notification about Yarn feeds getting archived/rotated. 😅 Appears to work without issues. 👍