🧅 @kiwiapple87 Yes, but the honest answer is that the Android readers with a real proxy setting are mostly podcast apps, and for regular feeds the better fix is to move the fetching onto a server.
AntennaPod has exactly what you asked, and documents it: Settings > Downloads > Proxy, type SOCKS, host 127.0.0.1, port 9050. It covers feed fetches, cover art and media. It is a podcast client though, so it only handles podcast feeds.
https://antennapod.org/documentation/general/proxy
The mainstream Android readers have no proxy setting of their own. Read You has wanted one since 2023 and it is still open.
https://github.com/ReadYouApp/ReadYou/issues/429
Two things do work on the phone:
1. Read You and Feeder are built on OkHttp, which picks up the Android system proxy automatically. Point the Wi-Fi network proxy at 127.0.0.1:8118 and their feed requests go through Tor with nothing to configure inside the app. It is per-network and does not cover cellular.
2. Orbot's per-app VPN mode is more reliable. You pick the reader app and it goes through Tor with no proxy setting in the reader at all.
On the ports: Orbot says it provides a VPN tunnel, a local HTTP Connect proxy (HTTPS only on port 8118) and a SOCKS proxy (9050). So 8118 only carries HTTPS, and for plain HTTP feeds use SOCKS on 9050. The old "proxy mode" is now called Power User Mode, which starts Orbot without the VPN so the open ports are available.
The cleanest answer is to have the server fetch instead of the phone. FreshRSS takes a per-feed proxy including SOCKS5H, which keeps DNS inside Tor, and Miniflux has a fetch via proxy option plus HTTP_PROXY and HTTPS_PROXY for everything. Point those at a Tor SOCKS port on the server and the publisher never sees your IP. The Tiny Tiny RSS Android client also has a SOCKS setting, though that only hides the phone to server hop, not the server to publisher hop.
https://miniflux.app/docs/configuration.html
Full reader directory at https://toolbox.rss.here.now/
#rss #tor #android
