You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tying VPNs to different Modes means that when a Mode is activated, the system switches to the VPN tied to that Mode. This is useful for automatically switching VPNs for different scenarios. Here are some example use cases:
Work Wi-Fi blocks the use of Mullvad VPN, so when the Work Mode is activated, the system automatically switches to ProtonVPN
School Wi-Fi blocks the use of any VPN, so when the School Mode is activated, all VPNs are automatically disabled
If no Mode is active, the system defaults to Mullvad VPN to be used as a fast VPN for general use
When the Sleep Mode is activated, the system switches to Orbot as no speed-intensive tasks (like video streaming) would be done during sleep.
When the Entertainment Mode is activated, the system switches to Wireguard as the VPN to be able to access a home media server to securely watch media.
Users can customize the functionality to their liking.
The reason I am suggesting tying them to Modes is because it provides a more robust implementation than creating a custom solution for VPN scheduling or trying to tie VPNs to specific Wi-Fi networks.
This not only creates a faster way to switch between VPNs, but it also helps automate workflows. For example, the Entertainment Mode disables notifications to prevent interruptions, but instead of manually switching between VPNs each time, the user automatically has it done when the mode is enabled, since Wireguard and that Mode go hand in hand in this scenario.
The text was updated successfully, but these errors were encountered:
Tying VPNs to different Modes means that when a Mode is activated, the system switches to the VPN tied to that Mode. This is useful for automatically switching VPNs for different scenarios. Here are some example use cases:
Work
Mode is activated, the system automatically switches to ProtonVPNSchool
Mode is activated, all VPNs are automatically disabledSleep
Mode is activated, the system switches to Orbot as no speed-intensive tasks (like video streaming) would be done during sleep.Entertainment
Mode is activated, the system switches to Wireguard as the VPN to be able to access a home media server to securely watch media.Users can customize the functionality to their liking.
The reason I am suggesting tying them to Modes is because it provides a more robust implementation than creating a custom solution for VPN scheduling or trying to tie VPNs to specific Wi-Fi networks.
This not only creates a faster way to switch between VPNs, but it also helps automate workflows. For example, the
Entertainment
Mode disables notifications to prevent interruptions, but instead of manually switching between VPNs each time, the user automatically has it done when the mode is enabled, since Wireguard and that Mode go hand in hand in this scenario.The text was updated successfully, but these errors were encountered: