How should Miniflux deal with 302 responses for a feed?

[alexpdp7]

Hi,

I used farside.link to read Twitter. farside.link keeps a list of working Nitter instances and redirects to one of them.

Nitter also provides RSS feeds of Twitter. An URL such as https://farside.link/nitter/_user_/rss seems to be useful for this purpose.

However, I have noted that Farside uses 302 redirections, and that Miniflux updates the feed's URL upon receiving a 302. So my feed ends up pointing to a specific Nitter instance. Nitter instances are spotty- they are often blocked by Twitter, or they disappear. As it is not inmmediately easy to track broken feeds, this would mean that feeds could stop working "silently".

It is my understanding that 302 is more like a temporary redirect vs. 301, which is more like a permanent redirection.

Is there a rationale to 302 modifying the feed URL?

Cheers,

Álex