I tried:
- socks proxy
- socks proxy+vpn Mode (for the app only)
- vpn Mode (for the app only)
And in all of them, even though Orbot was not connected, I could read and write nostr event. That's what's I was complaining.
Now misteryously it went back to work as intended: no Tor connection, amethyst stops working.
I Attribute it to a GrapheneOS update
GrapheneOS doesn't change anything with Orbot or VPNs, they aren't bundled in the OS. Most likely Amethyst's Tor implementation is leaky and it needs to prevent falling back to non-Tor if the setting is active. A split tunnelling VPN mode also won't make a difference if it isn't taking your OS VPN slot. The app needs to make an effort to reject it.
Go to Amethyst and generate a new npub, turn off Tor in Orbot and enable Tor in Amethyst. It will still let you post even when it should refuse to connect. This is on the latest build of GrapheneOS. I also have recordings of me turning on Tor when I don't have Orbot installed and it allowing users to post.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z anyway someone can help? Would be open to trying to figure it out.
Does the post have relay icons when you post without Tor?
If your post has no icons is because you have no connection. Amethyst doesn't warn you when there's no connection.
Yes, there was multiple on each video. You can see them under the profile picture if that's what you mean.
Ok, I found 1 issue and I'll make a pull request to fix it
It wasn't recreating the http client when you turned the proxy on or off in amethyst so if you turned it on it was using the http client without the proxy until the app was killed
That's great! I haven't had time to check the issue so thank you for finding the root cause. When I am not busy I'll make sure to check it out.
