@bender@twtxt.net That broken mention might have the same cause as the other issue you mentioned. Changed URL and all that. 🤔
There might be a bug in jenny that causes it to re-fetch archived feeds on every run. Probably happens on edits/deletes. I’ll look into it soon-ish.
@sorenpeter@darch.dk I like that. It pretty much matches what I already had in mind. (The implications of part two of point 0 are obviously controversial and I don’t know if we can ever agree on that. 😅)
@quark@ferengi.one Oh dear. 😅 I’m one of the first around here, though. 🤪
Time to put up the christmas decoration, I guess. 🤷✨
@quark@ferengi.one At some point, Yarn must have fetched the feed and used the correct URL (otherwise it wouldn’t have gotten the correct hash). And at that point, it should have updated the uri
field for this twt in its database, I guess? Disclaimer: I know nothing about the internals of Yarn. 😅
@quark@ferengi.one That’s confusion on Yarn’s part, I’d say.
Yarn’s API says that twt comes from the URL http://twtxt.prismdragon.net/twtxt.txt – but when using that URL for hashing, I get the hash bjs6aua
instead of mowsvgq
. That’s not the correct hash, so jenny says the twt could not be found.
Inspecting the feed using jenny -D …
yields the correct hash. When looking at the raw feed, we can see:
# nick = gallowsgryph
# description = Green living and permaculture enthusiast, writer, otherkin, weird.
# url = http://prismdragon.net/twtxt.txt
# url = https://dreamwidth.org/gallowsgryph/
# avatar = http://prismdragon.net/img/gallows.png#20241025
So it’s a different URL. When I use http://prismdragon.net/twtxt.txt for hashing, I get the correct hash.
I think it could be yarnd’s avatar caching. That’s why my avatar
field has a #20240102
at the end: To trick yarnd into reloading it.
My first PC as a kid had an amber monitor, so this feels right at home:
https://www.youtube.com/watch?v=PeuH0YmWkI4
💛