Oddbean new post about | logout
 nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tch2deau Why is #Amethyst now bypassing Orbot entirely, even when configured to use it? Orbot deactivated and I can still use Amethyst?  
 Amethyst has built-in Tor now. It will use it, if it needs to.  
 If I configure Amethyst to use Orbot, that is what I want, not for it to pull off an internal bypass. If it can't use orbot, or it is deactivated, it should not connect at all 
 If you configure it to use Orbot but Orbot is not there, it will use its internal Tor instead of crashing. No one wants to see a client that can't load anything.  
 Sure, but if I want it to use Orbot, specifically, then it's on me that Orbot is available. This was the only way of knowing that Amethyst was actually using Tor. Now, I have no guarantees that Tor is being used. 

If you make a setting, and I say Orbot only, don't assume I want a bypass. Make that a separate, opt-in choice. It is not a given.  
 That was not a good way of knowing if Amethyst was using Tor or not because so much of what the app does does not show up on the screen. Just because the feed is empty doesn't mean that Amethyst is only using Tor. 

You can use something like  https://www.rethinkdns.com/ to monitor connections that apps make, including Amethyst. Both form using internal Tor and Orbot.  
 On this point as well, I've blocked Amethyst from using mobile and wifi data entirely, and yet, it bypasses those restrictions as well? What is it leaning on internally that it bypasses this block?