↳
In-reply-to
»
Correct, @bender. Since the very beginning, my twtxt flow is very flawed. But it turns out to be an advantage for this sort of problem. :-) I still use the official (but patched)
⤋ Read More
twtxt
client by buckket to actually fetch and fill the cache. I think one of of the patches played around with the error reporting. This way, any problems with fetching or parsing feeds show up immediately. Once I think, I've seen enough errors, I unsubscribe.
Let me take this opportunity to recommend something to @bmallred@staystrong.run: https://staystrong.run/user/bmallred/twtxt.txt returned 200 but no Last-Modified header - can’t cache content
:-)
Another modification I made is to actually cache it anyways. Otherwise, tt
wouldn’t show anything. I implemented that for some other feed that doesn’t exist anymore.