Moving over
What it takes
Keep Brave for browsing. When the thing you are routing is a shell or a transfer, the route belongs on the connection.
You already route deliberately. One window at a time.
A private window with Tor is the right idea with the wrong granularity: it is one route for one window. Vandle makes the route a property of the connection, so two sessions in the same window can leave through different exits.
Credit where it is due
Brave blocks by default, ships a Tor window nobody else does, and takes the position that the network path is the user's business. That is the same position Vandle starts from.
What changes
Four things you get that you did not have.
- A route per connection, not per window: two sessions side by side can take two different paths.
- The exit address shown on the running session, so you can see where you are actually coming from.
- A tunnelled route that needs no open inbound port on the far side.
- The same routing model on a shell, a file transfer and a desktop, not only on a page.
Side by side
Brave and Vandle
| Aspect | Brave | Vandle |
|---|---|---|
| Routing | Per window, Tor or direct | Per connection, any configured route |
| Visibility | You know which window it is | Active route and exit address on the session |
| Scope | Web pages | Every protocol Vandle speaks |
| Blocking | Built-in, excellent | Not a browser feature set; keep Brave for the web |
And the rest of it
Four more protocols came along
Replacing one tool gets you five. Whatever else that machine speaks is already a row on the same record - and every one of them takes the route you assigned.
Web
Real browsing, properly routed
SSH
A terminal that keeps up
SFTP
Two remote panes, no detour
WebDAV
The other half of file transfer
RDP
Desktops on a native surface
Local
Your own machine, in the same list
Also compared