Could you please try to resolve the conflicts @printfuck ? Let us know if you face any difficulty

I fixed all the linting hints, but it's still waiting for the Docker builds. Is there something I missed?

Don't worry about the Docker builds. It looks good. I will test 👍🏻

@printfuck I have made a few changes; please have a look

This looks good to me.

Ok, let's merge and please test a bit more if you can

I am wandering whether we should allow normal users to use this feature, or only admins.
Furthermore, I forgot that we will have to deal with cache differences between the users, just like we do when providing a username/password to retrieve a feed.

I agree. Unless
(1) the proxy servers are known to the users (e.g. published in a wiki for the given instance of freshrss) and are only available to the instance,
(2) or the users are running the proxy servers themselves, limiting access to the specific freshrss instance,
this feature will only ever be useful for admins.

I don't understand the cache thing as of now. After reading the code multiple times, I didn't get why there is need for a cache.