This could help avoiding the maximum connection limit of [freenode](http://freenode.net/) and [OFTC](http://www.oftc.net/oftc/) if [tor](https://www.torproject.org/) is installed (even if this looks suspicious).
I cannot get other reasons why this could be good into my head right now.
See also the [SASL issue](https://github.com/znc/znc/issues/185) #185 (for [freenode](http://freenode.net/) over [tor](https://www.torproject.org/)).
<!-- github-sync-id:5196649 -->
Why were BOTH issues closed? I understand one of the two was duplicate but DarthGandalf closed both of them meaning neither are now active. The lack of HTTP/SOCKS proxy is really something worth working on. Please, reopen one of these two entries.
Why were BOTH issues closed? I understand one of the two was duplicate but DarthGandalf closed both of them meaning neither are now active. The lack of HTTP/SOCKS proxy is really something worth working on. Please, reopen one of these two entries.
<!-- github-comment-id:7399817 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This could help avoiding the maximum connection limit of freenode and OFTC if tor is installed (even if this looks suspicious).
I cannot get other reasons why this could be good into my head right now.
See also the SASL issue #185 (for freenode over tor).
Duplicate of #143
Why were BOTH issues closed? I understand one of the two was duplicate but DarthGandalf closed both of them meaning neither are now active. The lack of HTTP/SOCKS proxy is really something worth working on. Please, reopen one of these two entries.
uh... they aren't both closed
That issue is open...