Comment Re:open source (Score 1) 4
I suppose I could... but patching programs that are actively developed is a pain. Assuming the upstream developers don't accept my patch, I'd have to start maintaining my own version, and I don't IRC enough for it to be worth my while.
Since apple's guidelines (stupidly, imho) tell developers that they should use the system wide settings for proxies, other programs are likely to be affected too. So what I'd like is a global fix that doesn't involve patching other people's software.
It would be cool to have a socks router of sorts, that I could run locally (and then put "localhost" in for the systemwide socks setting), and then I could configure it to route different ports (or even hosts) over different proxies... say, IRC here, port 80 here, except port 80 to this host go here instead. If such a proxy could speak socks5 on the port it listens on, and be able to route out over socks4 (for openssh) as one of it's output methods, that would rock.
Since apple's guidelines (stupidly, imho) tell developers that they should use the system wide settings for proxies, other programs are likely to be affected too. So what I'd like is a global fix that doesn't involve patching other people's software.
It would be cool to have a socks router of sorts, that I could run locally (and then put "localhost" in for the systemwide socks setting), and then I could configure it to route different ports (or even hosts) over different proxies... say, IRC here, port 80 here, except port 80 to this host go here instead. If such a proxy could speak socks5 on the port it listens on, and be able to route out over socks4 (for openssh) as one of it's output methods, that would rock.
