@kiwu doing awesome, how about ya? We are having some coolish days, which are super rare, so I am enjoying them plenty!

@movq Yup, it's been some days here, too.

@movq Haha, you were spot on! It took me a bit to figure this out on my own. I'm actually very surprised to have gotten this wrong. Oh well.

No, I was using an empty hash URL when the feed didn't specify a url metadata. Now I'm correctly falling back to the feed URL.

@lyse Yeah, I noticed that too. I haven’t double-checked my code, though. Maybe it has something to do with selecting the correct URL? I mean, these feeds don’t have any # url = fields, so maybe that’s it?

@lyse Ah, there it is. 😃 Never gets old. 👍

@arne … I still haven’t watched that show. 🤦

@prologic And none of them use Yarn-style threading. I don’t think they’re aware of us, they’re probably using plain twtxt. Other than one hit by @threatcat a few days ago, I’ve seen no traffic from them. 🤔

Hmmm, looks like my twt hash algorithm implementation calculates incorrect values. Might be the tilde in the URL that throws something off. :-? At least yarnd and jenny agree on a different hash.

@bender Hmm, didn't find anything. But you mean a giant bucketload of access_log /home/$USER/logs/access.log if=… where the condition matches the requested path for said user? Yeah, that gets annoying very quickly. :-D