(#tuizh4q) @prologic@twtxt.net

philosophical reasons […] design decision

That I can understand (though to the extent that I understand it, I think I disagree with it 😄). I was asking more about the technical barriers @mutefall@twtxt.net mentioned.

responses are provided from the cache

I see, so we’re taking about an architectural limitation in Yarn, rather than twtxt. Still, I know cache invalidation is famously hard, but surely an intentional page load from a user trying to view a feed that isn’t (fully) cached is about the best signal you could get to fetch that data from the origin? 🤔