How should we handle Proton's misleading marketing?

Encounter5729: > The fix is nice, but I still question why this occured in the first place. You had time to fix it. The fix requires having the control of the Wireguard implementation. We are currently using Wireguard-go, but trying to fix this on Wireguard-go wasn’t feasible for us, especially because we took the decision of moving to Rust-based implementation on top of Boringtun. The upcoming codebase offers us all the control we needed to implement proper kill switch and a whole set of future functionalities, consistent across all platforms. jonah: > Which essentially comes down to: there’s no reason the packet tunnel exposed to the OS using Apple’s API is the same as the actual tunnel to Proton’s servers that the app uses. The Proton client could(?) switch WireGuard tunnels without tearing down the tunnel macOS sees, I believe. This is correct. It’s what we will be able to do with our new codebase, but wasn’t feasible to do with Wireguard-go.