movq

www.uninformativ.de

No description provided.

Recent twts from movq
In-reply-to » Simplified twtxt - I want to suggest some dogmas or commandments for twtxt, from where we can work our way back to how to implement different feature like replies/treads:

@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. 😅)

⤋ Read More
In-reply-to » @movq, having an issue fetching a twtxt context. I am getting:

@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. 😅

⤋ Read More
In-reply-to » @movq, having an issue fetching a twtxt context. I am getting:

@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.

⤋ Read More