Thanks for the hint. The server code isn't open source though. Is there a good reason for that?
nostr:nprofile1qqs80n2hqvjppgqh2c5t2dtl5e2mr7kw4d90u468xwaaenke8r0frgspz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3samnwvaz7tmjv4kxz7fwwdhx7un59eek7cmfv9kqzxthwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mg6k4xa4 has my favorite mobile VPN UX.
You can configure a two hop VPN, with random server selection, it has a notification tile that turns it off and on, which randomizes the server selection.
Meaning you get a new random network level identity with two clicks!
Discussion
According to FOSS ethics you don't need to publish backend code, as the 4 freedoms only apply to code that you ship for other users to be run on their machine.
Anyhow, I'd still recommend to publish all code, including backend.
I've asked what their rational is, maybe it's available somewhere.
Ah, I didn't know about this FOSS principle, thanks. I'd also encourage making all the code available, but I respect their decision.
Agreed. But trust is still involved even all the code is published it doesn't mean that that code is running on the backends and servers
There are secure enclaves that can proof to outside observers which code is running in a machine.
Pretty mind blowing!
Still relies on some trust in the hardware producer at the factory time.