Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it easier to determine if Tor is being used or not #58

Open
ArrayBolt3 opened this issue Nov 13, 2024 · 0 comments
Open

Make it easier to determine if Tor is being used or not #58

ArrayBolt3 opened this issue Nov 13, 2024 · 0 comments

Comments

@ArrayBolt3
Copy link

Feature Request

Is your feature request related to a problem? Please describe.
Looking at the source code of this tool, I can see that it does support connecting to archive.is over Tor. However, the documentation in README.md is unclear, and I don't have a very good understanding of Go, so I can't tell under what circumstances Tor is used. There's also no switch that I can use to say "only use Tor, error out if Tor doesn't work, don't try to use normal HTTP(S)". As such, it's very difficult for a user without a decent understanding of Go to tell for sure whether Tor will be used. I tried using Wireshark to see what IPs were being contacted when using the archive.is CLI utility, and it appeared to be accessing my local Tor proxy, but also accessing the archive.ph website directly without Tor.

Describe the solution you'd like
Add a command-line argument to the archive.is CLI utility (and possibly in the internal Go API also) that allows forcing the use of Tor. (--force-tor might be a good name for the CLI argument.)

Describe alternatives you've considered
It might help to clarify the documentation in README.md, stating clearly when Tor is used and what the user can do to influence Tor's usage. This wouldn't allow a user to force the use of Tor and forbid the use of fallback methods however.

Teachability, Documentation, Adoption, Migration Strategy
./archive.is --force-tor https://example.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant