Ok, it seems that the option of activating Tor for .onion relays is the bare minimum we should do.
The question is now, as a project, do we want to offer more privacy straight out of the box or not.
I am leaning towards also using Tor for:
1. Relays gathered from the Outbox model that are not in the user's relay list.
2. All relays that require Auth (no IP-Pubkey link)
3. All DM relays
By default.
More ideas are welcome.
Configurability is key. What if the user is inside a network that offers transparent .onion resolution and routing? Never assume that .onion has to enable in-app Tor automatically, better allow the user to choose.
Then he can just turn Orbot off.
Applauses for this guy. Native onion relays are a next level cypherpunk move.
Anonymity loves company, thus privacy ought to be the default.
I can very much recommend this paper
https://www.freehaven.net/anonbib/cache/usability:weis2006.pdf
It was an integral paper to Wasabi 2.0 & Wabisabi research
Vitor, enable Snowflake brigdes if you want to make Amethyst privacy-friendly. Snowflake is perfect for circumventing censorship.
Good ideas.
