some of the functionality does overlap. But when I originally built it, I wanted the extension and the backend to work together, without needing to handle them separately. Both the extension and the backend can provide more fine-grained control, and it can automatically detect the multiple requests made by the current page and automatically add them to the proxy, so I don't have to configure them one by one.
Of course, right now I'm trying to keep as much of the system running locally as possible, and that also makes it easier for me to modify the system myself to match my personal needs.
That's why I asked whether anyone else has this kind of need and wanted to hear what people think.
I mainly wanted to discuss it with everyone. I built something that I personally think is quite useful, and originally I was thinking about cleaning it up and open-sourcing it, but is that really necessary?
What about this can't be resolved by a PAC-file?
some of the functionality does overlap. But when I originally built it, I wanted the extension and the backend to work together, without needing to handle them separately. Both the extension and the backend can provide more fine-grained control, and it can automatically detect the multiple requests made by the current page and automatically add them to the proxy, so I don't have to configure them one by one.
Of course, right now I'm trying to keep as much of the system running locally as possible, and that also makes it easier for me to modify the system myself to match my personal needs.
That's why I asked whether anyone else has this kind of need and wanted to hear what people think.
I mainly wanted to discuss it with everyone. I built something that I personally think is quite useful, and originally I was thinking about cleaning it up and open-sourcing it, but is that really necessary?
[dead]
smokevpn.com solves this problems.
I mainly want the entire system to run locally, and to be able to switch between different VPNs locally and manage them in a more fine-grained way.