QuantumBadger / QuantumBadger/RedReader
Use SOCKS5 for Tor rather than HTTP proxy
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 527
- Avg merge
- 20d 10h
- Merged PRs (30d)
- 3
Description
its been this way for a long time. i use the alpha version but the regular does the same. I'm pretty sure the rest of the traffic does get sent over for, but perhaps in a weird way:
would it not be better to have it using orbots socks5?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file, test, or entry point. Start by locating how RedReader configures its Tor/Orbot proxy and determine whether traffic currently uses HTTP or SOCKS5. Done means the Tor connection uses Orbot's SOCKS5 proxy without breaking normal traffic, with coverage for the proxy behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java
- Domain
- mobile-dev, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100