yarn.meff.me @<lyse https://lyse.isobeef.org/twtxt.txt> "(#sqsa46q) @itsericwoodward No worries, all good, mate! We all have to start somewhere. Other software requests my feed several orders of magnitude more often. I can confirm, the `User-Agent` header appears to be fixed. \o/ Two other things I noticed, though: 1. There's now an `OPTIONS` request for my feed coming from something that claims to be Firefox, pointing to your feed URL in the query. No clue what this is about. In any case, it's rejected with a `405 Method Not Allowed`. 2. Not that these few requests bother me at all, but you might wanna implement caching next with either the `If-Modified-Since` or `If-None-Match` request headers. This way, if the feed hasn't changed, the web server can reply with a `304 Not Modified` and no body at all, saving unnecessary traffic. But again, this is really not an issue for me at all. I just wanted to make sure you're aware of it, that's all. It might be even already on your agenda. Or you might decide to never do anything about it, which is also fine for me. :-)"

Yarn

Recent twts in reply to #5ayx72q

(#7w2liya) @lyse@lyse.isobeef.org Yeah, those are my bad.

A couple of weeks ago, I added CORS support, which is the source of the OPTIONS call. What I didn’t do was store the result so it stops trying to make further attempts. I’ll get that in tomorrow.

As for the “If-Modified-Since” header, the server-based component of TwtStrm should be sending that (along with its user-agent tag and my user info). I wasn’t sure if that could be sent with CORS requests, so I’ll need to look into that a bit more.

Thanks, I appreciate the feedback!

#5ayx72q