Run wowlet via torsocks or torify - wowlet will detect this and switch to onion nodes
Run wowlet via Tails
Run wowlet via Whonix
wowlet is meant as an easy-to-use program for beginners who want a reasonable level of on-chain privacy. It is not meant to be 'as anal' as e.g. Monero when it comes to privacy.
even for a 'beginner program' the protection provided by wowlet is pretty good, as it comes embedded with Tor - all third-party integrations (forum feed, market rates, suhwow, etc) are fetched over Tor.
So I'm not really motivated to support going fully over Tor by default. It will make things a lot slower, more annoying, and this is just not what I have envisioned for wowlet.
Use CLI. Use Tails. Use Whonix. use LD_PRELOAD via torify/torsocks. You have special requirements. wowlet is for the masses.
Hey, there are 3 ways to achieve what you want:
- Run wowlet via `torsocks` or `torify` - wowlet will detect this and switch to onion nodes
- Run wowlet via Tails
- Run wowlet via Whonix
wowlet is meant as an easy-to-use program for beginners who want a reasonable level of on-chain privacy. It is not meant to be 'as anal' as e.g. Monero when it comes to privacy.
even for a 'beginner program' the protection provided by wowlet is pretty good, as it comes embedded with Tor - all third-party integrations (forum feed, market rates, suhwow, etc) are fetched over Tor.
So I'm not really motivated to support going fully over Tor by default. It will make things a lot slower, more annoying, and this is just not what I have envisioned for wowlet.
Use CLI. Use Tails. Use Whonix. use `LD_PRELOAD` via torify/torsocks. You have special requirements. wowlet is for the masses.
I'm already running whonix so the suggestion wasn't targeted at me :)
How about adding some onion nodes to the default websocket list?
It'd enable users to choose them out of the box without actively adding custom ones.
-hound
Hi!
Thanks for the input :)
I'm already running whonix so the suggestion wasn't targeted at me :)
How about adding some onion nodes to the default websocket list?
It'd enable users to choose them out of the box without actively adding custom ones.
-hound
unfortunately this is quite a big change (read: requires multiple days of programming) to change the 'architecture' of how the networking/node code work within wowlet. And like previously mentioned this is not something I support.
unfortunately this is quite a big change (read: requires multiple days of programming) to change the 'architecture' of how the networking/node code work within wowlet. And like previously mentioned this is not something I support.
Pretty much title.
When first starting wowlet, the node used should be an onion node. If all of them shall fail, use a clearnet one!
-hound
Hey, there are 3 ways to achieve what you want:
torsocks
ortorify
- wowlet will detect this and switch to onion nodeswowlet is meant as an easy-to-use program for beginners who want a reasonable level of on-chain privacy. It is not meant to be 'as anal' as e.g. Monero when it comes to privacy.
even for a 'beginner program' the protection provided by wowlet is pretty good, as it comes embedded with Tor - all third-party integrations (forum feed, market rates, suhwow, etc) are fetched over Tor.
So I'm not really motivated to support going fully over Tor by default. It will make things a lot slower, more annoying, and this is just not what I have envisioned for wowlet.
Use CLI. Use Tails. Use Whonix. use
LD_PRELOAD
via torify/torsocks. You have special requirements. wowlet is for the masses.Hi!
Thanks for the input :)
I'm already running whonix so the suggestion wasn't targeted at me :)
How about adding some onion nodes to the default websocket list?
It'd enable users to choose them out of the box without actively adding custom ones.
-hound
unfortunately this is quite a big change (read: requires multiple days of programming) to change the 'architecture' of how the networking/node code work within wowlet. And like previously mentioned this is not something I support.
Alright no problem :)
aight :) sorry