-
Notifications
You must be signed in to change notification settings - Fork 49
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
Add More Connection Options #4
Comments
Perhaps I2P/i2pd support could be an option too for the future. |
I would also like to request more options. My country actively blocks tor and the only way I can connect is by requesting bridges from tor. I'd like to have an ability to enter said bridges and also it would be nice to have a feature to use a proxy. As of right now I literally can't even try to use this wallet at all. |
Thanks for the feedback. I will look into adding support for bridges.
You can connect to nodes and sync your wallet without Tor if you click the Tor icon in the statusbar and select "Route all traffic over Tor, except traffic to node". Some wallet functionality that depends on the websocket onion service will not work, however. |
Regarding Tor bridges:
|
Just tested and you can use Feather wallet with I2P by following this guide: http://a6oqn7gevseuek3akchgzzjkf5qkh5pdj56jjlqtuynsj2krg7wq.b32.i2p/ |
One of the reasons I prefer Feather over other wallets is because I can trust that it won't send private information out without Tor. If you're going to allow Tor to be bypassed, then:
In general, I think more functionality is good --- but we should intentionally raise the barrier of entry to let a user bypass Tor. Consider the UX that TAILs uses for the "Unsafe Browser" (used only for bypassing captive portals), for example |
User may want don't use Tor and may use proxy but it's not possible. That feature would be useful
The text was updated successfully, but these errors were encountered: