(#2tjsjuq) @prologic Oh, was I? I don't recall any of that. But who knows. ;-)

(#e24exeq) @prologic 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.

(#2tjsjuq) @lyse I _think_ you were the one that originally came up with this `BUIDL` thing. Was it always suppose to be the commit timestamp? 🤔

(#e24exeq) @lyse What if they see traffic again at some point? 🤔 How do you fetch feeds again? You fork/exec out to the Python `twtxt` client right? 🤔

…kra) @lyse Since some time ago I automated the same feature in `yarnd`; I haven't really noticed when it happens. But I went and had a look just now, looks like it "just works"™ and no-one notices 🤣 …

Righto, it's time for a rotation into archive feeds again.

I just cleared my following list. Kicked out all the 26 feeds that have not been updated for two years or more. This will reduce a bit of useless traffic.

(#2kcxgrq) @prologic I figured, yep.

(#2tjsjuq) @prologic Does one need a build timestamp anyway? That's an enemy to reproducible builds. Maybe just use the commit timestamp? That would work at least for official releases. It would be off for dirty working directories during development, though: `git show -s --pretty=format:%cI`

(#2kcxgrq) @lyse Yeah but only 20 or so are actually active 🤣